Problem report for Slicer 4.11.0-2020-03-11 linux-amd64: [please describe expected and actual behavior]
I have a set of .fcsv files that have very similar and long names and I would like to rename each file to a shorter name when I load more than one file into Slicer, similar to how you can rename volume files in the load data window by checking the Show Options box.
Can you rename them after you added them to the scene, for example in Data module?
More to the point, if the input file has a ‘.’ in its prefix, Slicer truncates the file name and discards the part of prefix after the ‘.’. So we can’t distinguish which one is which once it is loaded into the scene.
So F.ab.fcsv, and F.aa.fcsv would be both shown as F in the data module after load.
Thanks for reporting, fixed now.
I’m having the same problem again with the current preview of Slicer 4.11.0-2020-06-30 linux-amd64 truncating file names after “.” when importing segmentations and labelmaps.
Just to clarify, there is no regression (loading of markups fiducials from .fcsv files still works correctly), but you have found that everything is considered to be part of the extension after the first dot for other file extensions. Probably we just used the overly simplistic file extension detection mechanism at a few more places. It should be no problem to fix those, too. As general advice, do not routinely use “.” character inside filenames because that character is reserved for separating file name from extension and may cause problems or inconveniences at various places (not just in Slicer).
Which file extensions do you have problem with and what did you choose in “Description” column when you loaded them?
The file extensions are .seg.nrrd or .nrrd and the error occurs when the Description is ‘Segmentation’ or ‘volume’
I did not name the original files, but in the future I’ll rename files that include ‘.’ at the start of all projects!
Thank you for your help!
It is really uphill battle. People seem to want to convey all the information in their experiment as part of the filename, and then we are stuck. How is this for a filename?
B6;129P2-Il2tm1Hor/J (a knock out mice experiment).
Nice! Fortunately, this one is not even a valid filename, so there is no temptation to use it. Eventually people learn the more subtle rules and best practices, too. We just have to make sure Slicer is as good in accepting complicated filenames as most other software, so that users they don’t think that something is wrong with Slicer.
A fix has been submitted for correctly loading all remaining nodes types (segmentations, models, markups, color tables, sequences, and volume rendering presets) when there are multiple “.” characters in the filename.