Skip to content
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

Nothing pops up after importing CARTO case? #3

Open
Jsalas424 opened this issue Nov 28, 2020 · 4 comments
Open

Nothing pops up after importing CARTO case? #3

Jsalas424 opened this issue Nov 28, 2020 · 4 comments

Comments

@Jsalas424
Copy link

What is supposed to happen after importing the CARTO zip? I get a "done" message but then nothing else.
image

@stephan1312
Copy link
Owner

Is there any data in the carto export? Usually, the log writes out the number of vertices and triangles found in the model, etc.
Something like:

Importing CARTO 3 map:
Extracting archive []/Export_Study-1-02_06_2020-20-09-51.zip to []/Temp/Slicer/EAMapReader/20201128_142341_582
Reading 2-Aorta.mesh:
Read 10745 vertices, 10745 vertex normals, and 21486 triangles.
Read 13 sets of scalars: ['Unipolar', 'Bipolar', 'LAT', 'Impedance', 'A1', 'A2', 'A2-A1', 'SCI', 'ICL', 'ACL', 'Force', 'Paso', 'µBi'].
Creating model CARTOmesh_2-Aorta:
Model created.
Reading 2-Aorta_car.txt:
Created markup fiducials CARTOpoints_2-Aorta.
Reading 3-LV.mesh:
Read 6577 vertices, 6577 vertex normals, and 13150 triangles.
Read 13 sets of scalars: ['Unipolar', 'Bipolar', 'LAT', 'Impedance', 'A1', 'A2', 'A2-A1', 'SCI', 'ICL', 'ACL', 'Force', 'Paso', 'µBi'].
Creating model CARTOmesh_3-LV:
Model created.
Reading 3-LV_car.txt:
Created markup fiducials CARTOpoints_3-LV.
Cleaning up temporary files.
Done.

So from the screenshot it looks like no relevant data was found inside the zip. Can you check that there are files named [map name].mesh and [map name]_car.txt in the zip?

@stephan1312
Copy link
Owner

stephan1312 commented Nov 28, 2020

It just occurred to me that there might be another reason (and the readme file is somewhat outdated or even misleading here)
Carto 3 nowadays forces you to choose a password during export. The entire export (also including screenshots and the like) is then zipped into one single file encrypted with this password. Please open this "container" zip which should include (possibly among other files) the actual study zip file. Extract that .zip file out of the "container", using the password chosen at time of export. This zip file, which is not encrypted itself, is the one to import.

The readme file has just been updated to reflect this.

@Jsalas424
Copy link
Author

Thanks for the prompt reply!

CARTO does force you to choose a password (annoying), but I did unzip it with the password and then re-zipped all the files up. Here's what the inner folder looks like:
image

Admittedly I did not turn off HD-coloring before exporting this particular case, but was just testing the plug-in to get familiar with its actions. Is this due to the HD-coloring?

Additionally, this was exported on a CARTO v7, is there any reason to believe this might also be involved?

I can export with HD-coloring off and from a v6 on Monday for further testing!

@stephan1312
Copy link
Owner

stephan1312 commented Nov 29, 2020

This is strange. I see 1-1-1-1-ReLV_LVPaced_car.txt, which contains the actual points as acquired (not the anatomy surface). This should be imported and should create a point cloud in Slicer. The log should print
Reading 1-1-1-1-ReLV_LVPaced_car.txt:
Created markup fiducials CARTOpoints_1-1-1-1-ReLV_LVPaced.
However, I do not see the corresponding 1-1-1-1-ReLV_LVPaced.mesh which contains the triangulated mesh.

Would you mind opening the Python interactor window while before running the import? If some (python related) runtime error occurs it should show there as an error message.
python interactor button

We have just recently transitioned to v7, so I have tested v7 export only briefly. The HD coloring issue no longer exists in v7, and as far as I could see the anatomy (.mesh file) is exported again without a special workaround. However I found some other issues with v7 export which I'll describe in a separate post in case someone would like to tackle them before I get to it.

It might be a good idea to export a case from a v6 workstation with HD coloring off on Monday and see if that works. And then we take it from there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants