Replies: 1 comment 7 replies
-
There are several things that might be causing the slow runtime, but I think this is one of them. When you create a pyramid from a non-pyramid image, there is no magnification level stored. By default, if no magnification level is provided, I believe FAST assumed it to be 40 (as in x40). In your case, what did you set as magnification? Which resolution would you expect to run your model on? I assume it was trained on a lower magnification plane like 10x? Could you share the corresponding FPL file, and I could have a look? I assume you are following this tutorial (see https://github.com/andreped/NoCodeSeg) or potentially this video (see https://www.youtube.com/watch?v=9dTfUwnL6zY)? |
Beta Was this translation helpful? Give feedback.
-
Hi all.
I'm trying to apply an .onnx model with the Windows build. Initially placed it in the /fastpathology/models folder with an identical named .txt, but didn't find a possiblity to apply it in FASTPathology.
So I downloaded one of the existing colon HE models, and mimicked its structure. Created a title-model and title-fp folder in /fastpathology/datahub, placed my .onnx file in the -model folder and changed PipelineName, Attribute classes and Attribute model in the colon HE pipeline.fpl file and saved it to the -fp folder.
Two warnings in fastpahtology but it seems to be running,
WARNING [16048] Requested magnification level does not exist in image pyramid. Will now try to sample from a lower level and resize. This may increase runtime.
WARNING [16048] Patch size must be a multiple of 16 (TIFF limitation). Adding some overlap (32, 32) to fix.
However it has been running for 5 hours now, with the progress bar still at 0%, but definitly with activity on the GPU. Is this normal during auto-tuning, or should I edit the .fpl file to prevent the warnings and restart?
Beta Was this translation helpful? Give feedback.
All reactions