Difference between revisions of "Dissemination:Workshop May 26"
From NAMIC Wiki
m (Update from Wiki) |
m (Update from Wiki) |
||
| Line 1: | Line 1: | ||
| − | + | Feedback from Users about clinical use cases, and feature requests for Slicer: | |
| − | + | Steve et al, please divide this list into two separate lists- one for Slicer development and one for tutorial/training development (e.g. the functionality is already there, just needs to be taught). | |
| − | + | # Streamline process of MaskStat/Cast for Scalar Volumes (rewrite VolumeMath) | |
| + | # Compute FA along fiber | ||
| + | # Telegraphing markers along orthogonal views (Brains feature) | ||
| + | # Analyze step editor (can save set of steps for future use) | ||
| + | # Distortion correction of DWI (do it and be able to preview/verify it) - might belong in the pre-slicer space | ||
| + | # Segmentation: missing the ability to backup (undo) | ||
| + | # Keyboard shortcuts should be made available in tutorial | ||
| + | # Synchronization of the three planes when you draw | ||
| + | # Lots of interest in incorporating Brains Editor functionality in Slicer which is already being explored as a collaboration (nca@unm.edu, vincent_magnotta@uiowa.edu) | ||
| + | # DTIStudio (S. Mori) program at JHU is worth looking at | ||
| + | # Unify UI: EMSeg seeding is done using C-LMB, while in most other modules Fiducials feature is used for this (press P). | ||
| + | # Fiducial feature appears only in 3D window. | ||
| + | # Registration GUI needs to be made more uniform | ||
| + | # NIfTI readers needed in ITK (format experts to possibly contact: John Ashburner at Dartmouth) | ||
| + | # fmri module: discrepancy between 0 indexed (in the configuration parameters) vs. 1 indexed slices (in slicer) | ||
| + | # fmri: can we load statistical maps (tmaps) from SPM and threshold it in Slicer? Note that t values can be positive/negative. Typically colorscales (cool/hot) are used. Slicer is most likely to be used for visualization/registration of these tmaps. | ||
| + | # fmri: While displaying a tmap, the t-value should show up in the window, not the scaled value. | ||
| + | # fmri: want to be able to click on a blob, and get stats on it (SPM gives max and eigenvectors of cluster). | ||
| + | # visualization of fmri: be able to show Brodman areas | ||
| + | # visualization: how to visualize aggregate data from multiple subjects | ||
| + | # add information about slicer contact info to the tutorial slides | ||
| − | + | == ''From Dartmouth Users:'' == | |
| − | |||
| − | |||
| − | + | ==== Slicer: Suggestions for Features/Functionality ==== | |
| − | + | # would be to have friendly data output format, e.g., deposit volume measures in an excel spreadsheet with ID | |
| + | # "loop" modules for processing multiple subjects in the same way | ||
| + | # Paint function for volumetrics | ||
| + | # Lesions to normal tissue, visualizations that would be helpful, tools used in structure tracing, features from other programs that are desireable. | ||
| + | # group data? | ||
| + | # more streamlined as far as memory and processing to prevent crashes | ||
| + | # the website specifies the minimum requirements for the computer system, but we would like you to specify "recommended" specs as well | ||
| + | # time series analysis - SPM & Slicer | ||
| + | # shrink wrap (from Alice) | ||
| + | #* [John MacDonald prefers brush system below to this feature - it doesn't work well] | ||
| + | # macros | ||
| + | # scripting language | ||
| + | # group data? | ||
| + | # header checking (automatic parameters) | ||
| + | # coronal scrolling | ||
| + | # output animations as mp4, avi | ||
| + | # option to browse and mark all 3 planes to update the others OR lock any one of the planes | ||
| + | # T1 and T2 on the same time (2 registers) -- to get one volume | ||
| + | # bump margins -- automatically changes the overlap for structures next to each other | ||
| + | # Add manual "paint-brush" editor, with | ||
| + | #* Various sized "brushes" (typically circles, smallest is 1-pixel); these are bi-modal: default mode paints, alt-mode erases. Brush size selected by function or number keys. | ||
| + | #* Brushes should be adjustably translucent; painted color should also be adjustably translucent | ||
| + | #* Modal paint-to-ROI, paint over ROI switch [probably multi paint overlays required to avoid conflicts; eg, if I start tracing lesions I create a lesion overlay space that does not conflict with other overlays; but another time I access an automated model overlay to edit] | ||
| + | #* Modal intensity-capture: a) capture all under brush, b) capture only between threshhold levels | ||
| + | #* Auto-smoothing command key/button | ||
| + | #* Command to auto-close current ROI color, if fully encircled | ||
| + | #* 3-D model build option for visualisation | ||
| + | #* Calculations of ROI areas, dimensions, overall volumes step in tabed text format. | ||
| + | #* Fine brush doubles as drawing tool??? | ||
| + | #* Hide/show toggle | ||
| + | #* Requires _large_ interpolated views | ||
| + | #* Ideally, user-definable presets of color groups with names, intensity approximations (later ability to correlate with other objects?). | ||
| + | #* Output options: analyze file if bitmapped overlays, open-GL views and/or quicktime movie, built-in screen/window captures? | ||
| + | #* Outer fringe stuff | ||
| + | #*# ability to segment everyother slice and iterpolate slices in between? | ||
| + | #* Questions: | ||
| + | #*# Is there a need to differentiate a "mask" from an ROI? | ||
| + | # Is there a way to do skull-stripping in Slicer at this point? We probably need in the future. | ||
| + | # Could use function that would normalize image intensity ranges in irregular scans (esp. FLAIRS). | ||
| + | # Would like to be able to place "marks" and see them in all three views | ||
| + | # We presently have a realignment phase where several alignments are made (using Brains); would like to be able to do this in slicer with precision, and set origin point at the same time. Output as analyze files. | ||
| − | + | ==== Dissemination Event: Likes and Improvements/Additions ==== | |
| − | |||
| − | == | + | ===== ''Likes'' ===== |
| − | + | # We thought there would be problems with the different ability levels but they made it really easy for everyone to participate at an advanced level. | |
| + | # RAs from Marty Shenton's lab were very helpful in getting everyone caught up/solving problems | ||
| + | # The slides were extremely helpful, especially with the screen captures so that everyone could see what the menus look like, etc. | ||
| − | == | + | ===== ''Suggestions'' ===== |
| − | + | # Could have been more clear about what we actually needed for the session -- it took 2-3 hours over the workshop that people were getting data, that could have been used for the actual workshop. Need very detailed instructions as to where to put things, in what folder, etc. | |
| − | + | # Would have been nice to have a smaller group -- especially in the future for more advanced workshops, and maybe the advanced workshops could focus on one area (fMRI vs DTI vs structural) | |
| − | # | + | # The feature about bringing your problems and data is desireable, perhaps data with problems so everyone can work through the problem-solving |
| − | + | # "Behind-the-scenes" workshop (soon) to understand what is happening, why certain parameters are chosen | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | # | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 14:06, 18 December 2006
Home < Dissemination:Workshop May 26Feedback from Users about clinical use cases, and feature requests for Slicer:
Steve et al, please divide this list into two separate lists- one for Slicer development and one for tutorial/training development (e.g. the functionality is already there, just needs to be taught).
- Streamline process of MaskStat/Cast for Scalar Volumes (rewrite VolumeMath)
- Compute FA along fiber
- Telegraphing markers along orthogonal views (Brains feature)
- Analyze step editor (can save set of steps for future use)
- Distortion correction of DWI (do it and be able to preview/verify it) - might belong in the pre-slicer space
- Segmentation: missing the ability to backup (undo)
- Keyboard shortcuts should be made available in tutorial
- Synchronization of the three planes when you draw
- Lots of interest in incorporating Brains Editor functionality in Slicer which is already being explored as a collaboration (nca@unm.edu, vincent_magnotta@uiowa.edu)
- DTIStudio (S. Mori) program at JHU is worth looking at
- Unify UI: EMSeg seeding is done using C-LMB, while in most other modules Fiducials feature is used for this (press P).
- Fiducial feature appears only in 3D window.
- Registration GUI needs to be made more uniform
- NIfTI readers needed in ITK (format experts to possibly contact: John Ashburner at Dartmouth)
- fmri module: discrepancy between 0 indexed (in the configuration parameters) vs. 1 indexed slices (in slicer)
- fmri: can we load statistical maps (tmaps) from SPM and threshold it in Slicer? Note that t values can be positive/negative. Typically colorscales (cool/hot) are used. Slicer is most likely to be used for visualization/registration of these tmaps.
- fmri: While displaying a tmap, the t-value should show up in the window, not the scaled value.
- fmri: want to be able to click on a blob, and get stats on it (SPM gives max and eigenvectors of cluster).
- visualization of fmri: be able to show Brodman areas
- visualization: how to visualize aggregate data from multiple subjects
- add information about slicer contact info to the tutorial slides
Contents
From Dartmouth Users:
Slicer: Suggestions for Features/Functionality
- would be to have friendly data output format, e.g., deposit volume measures in an excel spreadsheet with ID
- "loop" modules for processing multiple subjects in the same way
- Paint function for volumetrics
- Lesions to normal tissue, visualizations that would be helpful, tools used in structure tracing, features from other programs that are desireable.
- group data?
- more streamlined as far as memory and processing to prevent crashes
- the website specifies the minimum requirements for the computer system, but we would like you to specify "recommended" specs as well
- time series analysis - SPM & Slicer
- shrink wrap (from Alice)
- [John MacDonald prefers brush system below to this feature - it doesn't work well]
- macros
- scripting language
- group data?
- header checking (automatic parameters)
- coronal scrolling
- output animations as mp4, avi
- option to browse and mark all 3 planes to update the others OR lock any one of the planes
- T1 and T2 on the same time (2 registers) -- to get one volume
- bump margins -- automatically changes the overlap for structures next to each other
- Add manual "paint-brush" editor, with
- Various sized "brushes" (typically circles, smallest is 1-pixel); these are bi-modal: default mode paints, alt-mode erases. Brush size selected by function or number keys.
- Brushes should be adjustably translucent; painted color should also be adjustably translucent
- Modal paint-to-ROI, paint over ROI switch [probably multi paint overlays required to avoid conflicts; eg, if I start tracing lesions I create a lesion overlay space that does not conflict with other overlays; but another time I access an automated model overlay to edit]
- Modal intensity-capture: a) capture all under brush, b) capture only between threshhold levels
- Auto-smoothing command key/button
- Command to auto-close current ROI color, if fully encircled
- 3-D model build option for visualisation
- Calculations of ROI areas, dimensions, overall volumes step in tabed text format.
- Fine brush doubles as drawing tool???
- Hide/show toggle
- Requires _large_ interpolated views
- Ideally, user-definable presets of color groups with names, intensity approximations (later ability to correlate with other objects?).
- Output options: analyze file if bitmapped overlays, open-GL views and/or quicktime movie, built-in screen/window captures?
- Outer fringe stuff
- ability to segment everyother slice and iterpolate slices in between?
- Questions:
- Is there a need to differentiate a "mask" from an ROI?
- Is there a way to do skull-stripping in Slicer at this point? We probably need in the future.
- Could use function that would normalize image intensity ranges in irregular scans (esp. FLAIRS).
- Would like to be able to place "marks" and see them in all three views
- We presently have a realignment phase where several alignments are made (using Brains); would like to be able to do this in slicer with precision, and set origin point at the same time. Output as analyze files.
Dissemination Event: Likes and Improvements/Additions
Likes
- We thought there would be problems with the different ability levels but they made it really easy for everyone to participate at an advanced level.
- RAs from Marty Shenton's lab were very helpful in getting everyone caught up/solving problems
- The slides were extremely helpful, especially with the screen captures so that everyone could see what the menus look like, etc.
Suggestions
- Could have been more clear about what we actually needed for the session -- it took 2-3 hours over the workshop that people were getting data, that could have been used for the actual workshop. Need very detailed instructions as to where to put things, in what folder, etc.
- Would have been nice to have a smaller group -- especially in the future for more advanced workshops, and maybe the advanced workshops could focus on one area (fMRI vs DTI vs structural)
- The feature about bringing your problems and data is desireable, perhaps data with problems so everyone can work through the problem-solving
- "Behind-the-scenes" workshop (soon) to understand what is happening, why certain parameters are chosen
