-
Notifications
You must be signed in to change notification settings - Fork 5
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
Comments
Is there any data in the carto export? Usually, the log writes out the number of vertices and triangles found in the model, etc. Importing CARTO 3 map: 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? |
It just occurred to me that there might be another reason (and the readme file is somewhat outdated or even misleading here) The readme file has just been updated to reflect this. |
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 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. 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. |
What is supposed to happen after importing the CARTO zip? I get a "done" message but then nothing else.
The text was updated successfully, but these errors were encountered: