André Pedersen

@ajr82 You are probably referring to importing the segmentation TIFF to QuPath using this script, right? https://github.com/andreped/NoCodeSeg/blob/main/source/importPyramidalTIFF.groovy If I remember correctly, I have updated this script locally, but have probably...

@ajr82 I just tested inference with FP now and I reproduced the issue. I also found that: 1) the folder structure has changed in the new version of FP and...

@ajr82 I also opened an Issue on the NoCodeSeg repo to track this issue. You can also reply there if it is related to interacting with MIB and QuPath: https://github.com/andreped/NoCodeSeg/issues/12

@ajr82 import of predictions on full WSI from MIB into QuPath is working fine with the other script in NoCodeSeg?

> Although full WSI annotations are much faster and easier. @ajr82 Full-WSI prediction is absolutely the way to go! It is also easier to maintain and more streamlined, especially when...

@ajr82 Just fixed the path-thingy in NoCodeSeg to be compatible with the latest release of FastPathology: https://github.com/andreped/NoCodeSeg/commit/9714fb170beeb28958d4d51cb6bb934bd4935635 @smistad also fixed the formatting issue, such that all generated segmentations from FP...

@ajr82 For testing the updated NoCodeSeg script, could you use the nightly release of FastPathology? It is available from here: https://github.com/smistad/FAST/actions/runs/2866558364 --- EDIT: Oh, nevermind! That is of course the...

@ajr82 Hello! Just letting you know that this has been fixed in the latest artifact, which will be made available as a release soon. See this thread for some information...

@ajr82 I'm closing this issue for now. If you are having any problems related to this, please, reopen. For other issues, make a new issue. And of course, please, report...

@pr4deepr I believe @muskmelonxy's issue is related to him using AMD processors, which we have not have time to properly test and develop against. In theory it should work, but...