[Na-mic-project-week] Introducing two projects to discuss for NA-MIC week

[Fedorov, Andriy Y.,Ph.D.]

> Volumetric Mesh support:

Alexis, great to see that plan!

I wanted to make you aware of 2 groups/extensions that generate unstructured meshes, so perhaps you could coordinate with the corresponding developers:

* https://www.slicer.org/wiki/Documentation/Nightly/Modules/BodyCentricCubicMesh
* https://www.slicer.org/wiki/Documentation/Nightly/Extensions/CleaverExtension

I am not using unstructured meshes, and I have not tried either of the extensions above for a very long time, but I wanted to at least make sure you are aware of those!


On Nov 23, 2016, at 2:50 PM, Alexis Girault <alexis.girault at kitware.com<mailto:alexis.girault at kitware.com>> wrote:

Hi everyone,

I wanted to introduce you to two topics I would like to investigate and discuss during the next conference call and the na-mic week in Boston:

Volumetric Mesh support:
We collaborate on a project which uses finite element meshes to compute light propagation within soft tissues for optical imaging. Their mesh is computed using label map images, and they would like to visualize their output data overlayed above the structural images used for the segmentation without having to resample it within the original volume domain. JC directed me to the interesting work that is still in Slicer 3.6<https://www.slicer.org/wiki/Modules:IA_FEMesh-Documentation-3.6>. The discussion on this topic could be related to the potential wrapping of VTK unstructured grid, to think about where it could fall within the current nodes hierarchy (link with models...), etc...

MatLab tighter integration:
Right now - based on my current understanding of the framework - MatLabBridge allows us to forward commands to a MatLab server and retrieve information, and offers methods to convert data to and from MatLab, but the workspace environment instanciated while processing the given commands is lost (no way to still access the MatLab variables created, to keep using MatLab from the latest state). We would like to investigate a solution that would allow us to keep the MatLab state alive, to visualize the MatLab workspace variables within Slicer (table node?), to directly enter MatLab commands within Slicer (using a custom ctkConsole, like the python console?)

Looking forward to hearing your thoughts and possible interests in those topics.

Best regards,

Alexis Girault
R&D Engineer in Medical Computing
Kitware, Inc.

http://www.kitware.com<http://www.kitware.com/>
(919) 969-6990 x325<tel:(919)+969-6990+x325>
_______________________________________________
Na-mic-project-week mailing list
Na-mic-project-week at public.kitware.com<mailto:Na-mic-project-week at public.kitware.com>
http://public.kitware.com/mailman/listinfo/na-mic-project-week



The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/na-mic-project-week/attachments/20161123/8b0ad1a3/attachment.html>