View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0003317||Slicer4||Core: Usability||public||2013-08-23 10:52||2018-04-21 17:39|
|Target Version||Fixed in Version|
|Summary||0003317: Volume filename is reset and volume is modified when not needed|
1) load MRHead
|Tags||No tags attached.|
I suggest to bump up priority this ticket: saving a project becomes very time consuming after DICOM data has been consolidated in a local directory as nrrd files. All volumes are written back on disk in their entirety -- every time! This also messes up time stamps and creates chances of data corruption (and wears on SSDs etc..)
@nick_slizer if you rename the volume node before saving then the filename will match that and subsequent saves won't re-save the file if the volume node hasn't changed.
What circumstance leads to the volumes being written back each time?
Thanks for tips. I found the problem, sort of.
First, I couldn't actually reproduce the scenario of the OP, so maybe this ticket is altogether invalid as of now?
Second, I should have checked the log files and MRML files: for some reason, the file name of a cropped volume had been corrupted, but only in its VolumeArchetypeStorage node, not in the Volume node. The corruption consists of a doubling of the ".nrrd" suffix, so that the file got named "X.nrrd.nrrd" instead of "X.nnrd". I fixed that in a text editor and voila the problem has gone away.
The problem was actually flagged in the Data module when I hovered the mouse over the volume X and it also lit up the error icon in the lower right corner (but it turns to "red" usually, need to change my habits).
I played with the Crop module to see whether I could tease it into doubling the suffix, but didn't succeed. Renaming the volume didn't work for me either, thus detour over text editor.
@fedorov, can you see if this is still an issue for you? If not this can be closed.
@nick_slizer thanks for testing. There had been an issue with doubled extensions like that but I'd thought it was resolved. Maybe the issue you saw came from an earlier build or something.
|2013-08-23 10:52||fedorov||New Issue|
|2013-08-23 10:52||fedorov||Status||new => assigned|
|2013-08-23 10:52||fedorov||Assigned To||=> pieper|
|2018-04-12 15:12||nick_slizer||Note Added: 0015667|
|2018-04-12 15:32||pieper||Note Added: 0015668|
|2018-04-21 12:26||nick_slizer||Note Added: 0015675|
|2018-04-21 15:58||pieper||Status||assigned => resolved|
|2018-04-21 15:58||pieper||Resolution||open => fixed|
|2018-04-21 15:58||pieper||Note Added: 0015676|
|2018-04-21 17:39||fedorov||Status||resolved => closed|