I am a new clinican user to 3dSlicer and it looks great. Is there a way to quickly construct electrode trajectories based on DIXI parameters from post-implant CT/MRI co-ordinates. As well is there a way to view slices orthogonal along the trajectory of a particular electrode apart from the standard coronal, axial and sagital views? The SEEG assistant paper looks abit complicated and doesnt give a detailed step wise guide.
Yes, you can easily create straight or curved trajectories from CT/MRI coordinates (e.g., from a csv file) and reslice the volume along that axis (for example, using SlicerVMTK extension’s Cross-section analysis module).
I would recommend to use the .json file format, because that allows you to specify markup type (points, curve, etc.) and all display properties. But if you store and process your data in Excel then you can save as .csv or .tsv file that you can read into Slicer as a table and import into a markups node.
I managed to import coordinates as markup points and its looking really good.
I want to ask if there is a quick way to centre a markup just by typing in the name of the desired markup point (maybe via some code in pythoninteractor or a filter somewhere). Lets say I have 200 points corresponding with stereo contacts. I want to go to a certain markup for example A5. Is there any quick shortcut way apart from scrolling through the control point table (it shows only around 6 markups at one time) and we have to scroll through to find one I want and click that row? It would be great if there is a filter or a brief code to do that.
sEEG reading is dynamic when we review the iEEG we want to refer back to the MRI alot of times for corresponding contacts.
Thanks for any help.
You could write a Python script that fills in a QTableWidget with the point names and add a filter text box. You can use the study list in DICOMwebBrowser extension as an example (see source code).
Filter&search will be generally useful, so we’ll implement this in Markups module, but we are still in the process of integrating a large markups module feature pack, so we will not be able to get to it for a couple of weeks. If you have some C++ programming experience then you can take on this task and make it available earlier.