-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File names ending with space #75
Comments
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 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? |
I don't think the disappearing issue is related to the spaces. |
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. |
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: |
@andreped and I were able to reproduce this issue. For an image with space at the end of the filename (e.g., |
Using this artifact https://github.com/AICAN-Research/FAST-Pathology/actions/runs/4808864433.
There is an issue with the files having a filename ending with a space such as "something .vsi". When saving the results of the models, the last space is ignored and consequently, the results cannot then be loaded.
error: unable to open file: name = ... , errno = 2, error message = 'No such file or directory'.
The text was updated successfully, but these errors were encountered: