Failure to open saved scene

Support
1

Hello all ;
When I try to load the slicer format of my saved work, I often get nothing or an error message. My saved work consists fusion images (MRI and PET images) and maybe that is the reason for that. Do you have any suggestions on how to open my saved work properly.
Best Regards

axc
axc1366×768 75.8 KB

2

Do you see more error messages in the application log?

3

Hello Andras :

First of all thanks for the swift reply. I clicked to show details and there was only single error message. Can I check for more of a detailed error in Slicer?

4

@arif You can get the full application log by going to “Help->Report A Bug”. From there the default selection is the current session log, but you can find recent session log files as well. See if you see errors in there. If you replicate in the current session log you can also use “View->Error Log” to filter out other messages to limit it to say errors and warnings.

5

Hi James:
Thanks for pointing out. Recent log file is down below.

Errors:

Error parsing XML in stream at line 39, column 57, byte index 11184: not well-formed (invalid token)
The following modules failed to be instantiated:
   ChangeTracker
loadSourceAsModule - Failed to load file "C:/Users/Yakup/AppData/Local/NA-MIC/Slicer 4.11.20210226/NA-MIC/Extensions-29738/ChangeTracker/lib/Slicer-4.11/qt-scripted-modules/ChangeTracker.py"  as module "ChangeTracker" !
Fail to instantiate module  "ChangeTracker"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "C:\Users\Yakup\AppData\Local\NA-MIC\Slicer 4.11.20210226\lib\Python\Lib\imp.py", line 170, in load_source
    module = _exec(spec, sys.modules[name])
  File "<frozen importlib._bootstrap>", line 618, in _exec
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "C:/Users/Yakup/AppData/Local/NA-MIC/Slicer 4.11.20210226/NA-MIC/Extensions-29738/ChangeTracker/lib/Slicer-4.11/qt-scripted-modules/ChangeTracker.py", line 4, in <module>
    import ChangeTrackerWizard
  File "C:\Users\Yakup\AppData\Local\NA-MIC\Slicer 4.11.20210226\NA-MIC\Extensions-29738\ChangeTracker\lib\Slicer-4.11\qt-scripted-modules\ChangeTrackerWizard\__init__.py", line 2, in <module>
    from ChangeTrackerStep import *
ModuleNotFoundError: No module named 'ChangeTrackerStep'

Warnings:
When loading module  "ChangeTrackerSelfTest" , the dependency "ChangeTracker" failed to be loaded.
libpng warning: iCCP: known incorrect sRGB profile
6

I do not suspect the ChangeTracker module to be the issue of your loading problems. You should try to find in the log where it reports the loading specific errors. To confirm you can uninstall the ChangeTracker extension from the ExtensionsManager and try loading again.

1 Like
7

It seems that this log does not contain the part where you attempt to load the scene file. Could you please attach the complete log file?

1 Like
8

So I have tried to load again and took the log screenshot. There seems to be no more information then what is present in the screenshot, if you have any suggestions on acquiring more information regarding this error I can try them too.

Untitleds
Untitleds1365×423 26.5 KB

9

Can you open the .mrml file in a text editor (for example, Visual Studio Code) and chexk what is in line 25 near the 56th character? If there is nothing obvious then it would be great if you could share that mrml file or at least that line so that we can have a look, too.

10

The .mrml file is below as a link:

(link has been removed due to potentially containing patient information)

Thank you

11

The issue is that the patient name contained special characters that were encoded incorrectly.

If recent Windows10 versions, Slicer uses UTF8 encoding for all special characters, so I don’t know why this could have happened. Could you copy-paste here the content of the “Operating system” line in the log (it is near the very top)?

1 Like
12

Hello Andras

Here is the line that you asked for:

Operating system …: Windows / Professional / (Build 19041, Code Page 65001) - 64-bit

13

This version should already fully support utf-8 encoding. Maybe the input used some unusual encoding that the DICOM importer could not interpret. Is there any chance that you can privately share the DICOM image that you imported? (you can send a private message to me by clicking on my username and then on the message icon)

1 Like
14

I’ve investigated the problem further with the provided dataset and the issue was that the input DICOM files used very unusual (ISO 2022 IR 100) encoding, which Slicer does not support. Strings that are stored using this encoding are imported without decoding and the resulting special characters caused syntax error in the saved scene. The syntax errors can be fixed using a text editor (by removing the special characters), but to prevent such issues in the future, I’ve submitted a fix to CTK: