Hi,
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?
-Steve
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.
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.
Ditto
@stephan When you have a chance, could you associate the 3d-slicer-extension GitHub topic so that it is listed here: https://github.com/topics/3d-slicer-extension
done
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.
Hi Stephan,
My name is Tom. I am an electrophysiology fellow at the International Clinical Research Center (Brno, Czech Republic) and Medical University of Silesia (Katowice, Poland).
Thank you for your contribution and development of the reader for cardiac EP maps.
We are planning to initiate the radiosurgery clinical study designed for patients with VT. Thus, I am looking for a solution to merge EP maps with CT scans for procedure planning. Thus, I would like to ask if your reader can be used to integrate Ensite Velocity maps with CT.
I will be grateful for the information.
Kind regards,
Tom
Hi Tom,
thank you for your note and for your interest in the EA map reader. The plug-in is being overhauled right now (since some python-related changes in Slicer 4.11 stopped from working properly), so please bear with me for a couple more weeks. In general, Ensite Velocity maps can be read (although testing has been limited so far)
I’ll let you know when the plug-in is working again. Thank you for your patience.
Stephan
Thank you Stephan. I am looking forward to hearing from you.
Yours,
Tomasz
Let us know if we can help with anything. If you send the repository URL and a test data set then we may be able to fix Python2/3 API differences.
Dear Stephan,
Would very much appreciated to have access to the EA map reader, in particular for NavX maps.
Are you planning to share it again?
We debugged the reader to make it work with Slicer 4.11 / Python 3.
Also, an accompanying publication has been submitted and is currently under review.
The extension can be found at
Just download the EAMapReader-Slicer-4.11.zip file and install the extension from file.
Also, see the Readme file
Thank you for sharing this. Would you consider polishing up this module a bit and submitting to the extension manager? We could also distribute this module as part of SlicerHeart extension, thereby saving some administration and maintenance efforts.
Hi. This extension is not working. At least not on my Mac.
This is a notification.
Failed to copy directory /Applications/Slicer.app/Contents/Extensions-29402/EAMapReader/EAMapReader-Slicer-4.11/Slicer.app/Contents/Extensions-29402/EAMapReader into directory /Applications/Slicer.app/Contents/Extensions-29402/EAMapReader-XXXXXX
Do you have any sugestion.
Thank you, very much.
It seems that you missed the installation step of dragging the Slicer application to your Applications folder. See https://slicer.readthedocs.io/en/latest/user_guide/getting_started.html#mac.