for a research project I developed a python scripted module that reads data exported from cardiac electroanatomic mapping systems (Ensite Velocity, CARTO 3, and Rhythmia) and creates models in Slicer from it (with the electric data as a scalar overlay).
The code was good enough for what I needed it for, but it is still quite experimental and not ready to be released as it is (e.g. it is not packed/built into an extension but it is rather the raw python file as generated from the Extension Wizard, and no self-test is implemented).
I was wondering if there are other cardiac electrophysiologists out there who would like to use this functionality in Slicer. If so, I would try to get it to a more release-ready shape as soon as I can find some time to spare. Otherwise it will probably end up further down on the to-do list…
Hi @stephan - I’m not currently doing anything with cardiac ep, but I can imagine the code you described being very interesting to people in the field even if it’s not completely packaged up. As far as I know there’s no real standard file format, so having file reader code for the various vendor systems could be handing. Maybe you could just publish a github repository with a clear WIP warning in the readme?
Sounds good. I will do that (probably within the next two weeks) and post updates here.
I fully agree with @pieper’s suggestion. Just make the extension public, even if it is not polished yet, to give others a chance to try it, give feedback, etc.
We have collaborators who use Slicer for EP procedures, with CARTO, they would be probably interested.
It is out there now: https://github.com/stephan1312/SlicerEAMapReader
This looks great @stephan
Just a thought, but if you happen to have any sample data sets to post somewhere that would be great too.
I’ll work on it.
Yes. As noted above we are working in this space as well, but putting images into CARTO.
Being able to get them from CARTO to Slicer would be very helpful.
Feel free to test it. We worked mostly with Rhythmia, so CARTO and Velocity testing has been more limited. I am looking forward to any feedback and improvements. Let me know if you have any questions.
Update: Unfortunately, CARTO import is broken. The extension was developed (and limited testing was done) using sample files exported from a CARTO3 v4 system.
In the current version (CARTO3 v6) export from the work station has been changed and the interesting data (the triangulated mesh of the map) is no longer being exported.
It is unclear whether this change is intentional (might not be, since the files which are now missing from the exported data set are still referred to in other parts of the exported data).
However, preliminary feedback from the manufacturer indicates that they will probably leave it that way.