Difference between revisions of "User:Inorton"
From NAMIC Wiki
| Line 14: | Line 14: | ||
*Better transform handling in the registration code: should sort out any hierarchies for cross-registration (ie, want to register to something that is already inside another transform) | *Better transform handling in the registration code: should sort out any hierarchies for cross-registration (ie, want to register to something that is already inside another transform) | ||
| − | |||
*Put models inside appropriate transform after generation | *Put models inside appropriate transform after generation | ||
| + | *Editing volume inside of transform - don't want to have to move volumes out every time to change labelmaps in a complex scene. | ||
| + | *Slice intersections in 3D viewer, ie lines/gray/highlight/etc. at the intersection point (helps with depth perception). In Slicer3 this is only supported in 2d widgets. | ||
| − | + | ====DTI==== | |
*Tract (hyperstreamline) intersection with MR planes (highlighted with color change, ring, etc.) | *Tract (hyperstreamline) intersection with MR planes (highlighted with color change, ring, etc.) | ||
| − | + | *FiberBundle editing!!! | |
| − | * | ||
===Thoughts=== | ===Thoughts=== | ||
Revision as of 04:29, 20 October 2010
Isaiah Norton, Golby Lab, Department of Neurosurgery
contact: inorton @bwh d-t harvard d0t edu
Contents
Slicer Notes
Things that aren't fleshed-out enough to go into Mantis, or if I can't fully reproduce yet, can't share the data right now, etc..
Bugs
- Can't load high-res MEMPRAGE MRI from MGH for AG case in Slicer3. workaround: loaded fine in slicer2, then saved as nrrd.
Feature Wishes
- Better transform handling in the registration code: should sort out any hierarchies for cross-registration (ie, want to register to something that is already inside another transform)
- Put models inside appropriate transform after generation
- Editing volume inside of transform - don't want to have to move volumes out every time to change labelmaps in a complex scene.
- Slice intersections in 3D viewer, ie lines/gray/highlight/etc. at the intersection point (helps with depth perception). In Slicer3 this is only supported in 2d widgets.
DTI
- Tract (hyperstreamline) intersection with MR planes (highlighted with color change, ring, etc.)
- FiberBundle editing!!!
Thoughts
How-to-do-this
- [LoadBrainPointsIntoSlicer]
Slicer4
Internal Coding
- http://www.slicer.org/slicerWiki/index.php/Slicer4:Developers
- http://www.slicer.org/slicerWiki/index.php/Slicer4:QtPort
- http://www.slicer.org/slicerWiki/index.php/Slicer4:QtPort/Tutorials
- http://www.na-mic.org/Wiki/index.php/QtAugust2010
External links
- http://techbase.kde.org/Policies/Binary_Compatibility_Issues_With_C++#Using_a_d-Pointer
- http://en.wikipedia.org/wiki/Opaque_pointer
Other Notes
SuperBuilding Slicer3 on Windows 7
Slicer3 with WrapITK for Python ITK wrapping
