| Cache/bug in loading files |
Mar 29, 2022 03:10 PM
by Jeremy@Resoundant
by Jeremy@Resoundant
I have observed a bug (or possibly an unexpected cache) using radiant where underlying dicom files are changing.
To produce the bug, say you have a valid file "my_dicom.dcm".
1) Load it in Radiant, then close Radiant.
2) Using a tool (eg. pydicom) to modify this, such as adding or modifying a tag.
3) Re-load Radiant with this dicom: you will see it is unchanged from 1.
4) rename the file, "my_dicom2.dcm" and load in radiant. The change will be present.
This leads me to believe radiant it caching, which is unexpected between opens.
To produce the bug, say you have a valid file "my_dicom.dcm".
1) Load it in Radiant, then close Radiant.
2) Using a tool (eg. pydicom) to modify this, such as adding or modifying a tag.
3) Re-load Radiant with this dicom: you will see it is unchanged from 1.
4) rename the file, "my_dicom2.dcm" and load in radiant. The change will be present.
This leads me to believe radiant it caching, which is unexpected between opens.
Mar 30, 2022 09:25 PM
by
by
You're probably not closing RadiAnt process, only one of its windows.
In such case, the file is loaded from cache and manual edits will not be detected by RadiAnt.
After RadiAnt process is terminated, there is no way images can be cached from a previous session.
In such case, the file is loaded from cache and manual edits will not be detected by RadiAnt.
After RadiAnt process is terminated, there is no way images can be cached from a previous session.