File names ending with space about fast-pathology

[SoroushOskouei]

I don't think the disappearing issue is related to the spaces.
That occurs in filenames without any spaces and also sometimes does not even occur for filenames with spaces.
BUT If the filename has a space at the end of it, the program will crash.
Because when it creates the folder for saving the results, the space at the end will be ignored so it can not find the folder with the name including the space at the end.

[andreped]

This is likely an issue if the filename has a space anywhere, not just at the end.

A fix in FAST was added to handle full paths with space in them, such that FAST POs like fast.WholeSlideImageImporter can read these files, but we have likely not yet added the same fix to FP yet.

After inference, the result will be moved to the Project folder, and as it fails to use this filename, for whatever reason, the result won't be loaded correctly. AFAIK, right after inference, the prediction might actually just disappear from the viewer. Is that correct, @SoroushOskouei?

[SoroushOskouei]

I think when you create a folder that has a name with spaces at the end the OS will ignore them. For example "folder " will be created as "folder". This does not happen if the space is in the middle. That is why FP cannot find it when the space is at the end.

[andreped]

I think when you create a folder that has a name with spaces at the end the OS will ignore them.

That's surprising to me. I just tried on macOS, and I could not reproduce this issue. This I tried outside FP, just on my macbook. Is this a Windows-issue maybe? Or Qt-related?

Could you try just making a folder through the Windows terminal, like so: mkdir "test_dir "? Note the added space " ".

[mhoibo]

@andreped and I were able to reproduce this issue. For an image with space at the end of the filename (e.g., "some_image .svs"), the space is lost inside the Project when making the result directory, and thus after inference, the segmentation vanishes. Result is also not stored, likely because FP was unable to find an existing path to store the result.

@smistad