Difference between revisions of "Developer Meetings/20130226"
From Slicer Wiki
m (Text replacement - "slicerWiki/index.php" to "wiki") |
|||
| (11 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | __TOC__ | |
| − | |||
| − | |||
| − | =Listing of Modules= | + | == To discuss == |
| − | <gallery widths=" | + | |
| − | Image:CoreModules-2013-02-21.png| Should we remove from or add to anything in this list? Also, wizards is empty and should be removed | + | === Changes proposed by Csaba === |
| − | Image:Informatics-2013-02-21.png| Is something missing? | + | * Opacity and slice intersection visibility of models in a hierarchy - See http://slicer-devel.65872.n3.nabble.com/Opacity-and-slice-intersection-visibility-of-models-in-a-hierarchy-tt4027732.html |
| − | Image:Registration-2013-02-21.png|Where does Resample belong? Its here, its under converters, its under diffusion. We might want to introduce a resample toplevel category and add some organization about what resample should be used when. | + | |
| − | Image:Segmentation-2013-02-21.png| Editor is listed here and under core modules. Is this a good idea? | + | ===Module reorganization=== |
| − | Image:Quantification-2013-02-21.png|Is anything missing | + | ====Introduction==== |
| − | Image:| | + | The listing of modules should be organized from the vantage point of an '''early stage end user'''. Power users know what module they want and usually look in the alphabetic listing. Developer oriented tools should not be prominent and should not crowd the listings. Developers should be directed as much as possible to the wiki as a start point. |
| − | Image:| | + | |
| − | Image:| | + | *We should reorganize the listing of modules in such a way that each category has only one choice per category/subcategory presented initially and everything else is under a tab called "Advanced". This is consistent with the way modules in Slicer should be organized. |
| − | Image:| | + | *We should come up with guidance for developers on how to organize extensions. In some cases it makes sense for them to be in their own category and some cases, individual modules should be spread out to existing categories. Modules derived from extensions should have the extension acronym inside the module name. As a general rule, extension derived modules should be under the "advanced" section of a category so that the top level is not "messed up" |
| − | Image:| | + | |
| − | Image:| | + | ====Listing of Modules==== |
| − | Image:| | + | <gallery widths="300px" perrow="3" caption="Slicer 4 Module Reorganization 2013-02-26"> |
| − | Image:| | + | Image:CoreModules-2013-02-21.png| Core Modules: Should we remove from or add to anything in this list? Also, wizards is empty and should be removed |
| + | Image:Informatics-2013-02-21.png| Informatics: Is something missing? | ||
| + | Image:Registration-2013-02-21.png|Registration: Where does Resample belong? Its here, its under converters, its under diffusion. We might want to introduce a resample toplevel category and add some organization about what resample should be used when. | ||
| + | Image:Segmentation-2013-02-21.png| Segmentation: Editor is listed here and under core modules. Is this a good idea? | ||
| + | Image:Quantification-2013-02-21.png|Quantification: Is anything missing | ||
| + | Image:Diffusion-2013-02-21.png|Diffusion: Interactive seeding should be promoted to the top level of this category | ||
| + | Image:IGT-2013-02-21.png|IGT: this is where all the igt extensions should land | ||
| + | Image:Filtering-2013-02-21.png|Filtering: This category should get reviewed. I think that one each, but with documentation aimed at end users, should be enough. | ||
| + | Image:SurfaceModels-2013-02-21.png|Surface Models: Is this the best name for this category? We need ICP registration. Its a must. | ||
| + | Image:Converters-2013-02-21.png|Converters: Is this where the resampling tools belong? Does the Dicom converter belong here or into the Informatics category or both? | ||
| + | Image:Endoscopy-2013-02-21.png|Endoscopy: This one is lonely | ||
| + | Image:Utilities-2013-02-21.png|Utilities: Should be converted to extensions, I would think. I am not quite sure about the Brains utilities. Perhaps Hans can chime in. | ||
| + | Image:DevelopersTools-2013-02-21.png|Developers tools: Is there a good reason not to turn this into an extension? Most people will not need this. Should performance test be moved to the testing category? | ||
| + | Image:Legacy-2013-02-21.png|Legacy: Should be turned into an extension. Demian, how about otsu, is the module used for DTI estimation or is ITK accessed directly? http://www.slicer.org/wiki/Documentation/Labs/DeprecatedModules | ||
| + | Image:Tests-2013-02-21.png|Testing: Utilities, testing, developers tools should all be reviewed and reorganized together. As a guiding principle, the presentation should target end users. Developers should be directed to the developer page on the wiki. | ||
| + | Image:WorkInProgress-2013-02-21.png|Work in progress: the current modules should be moved elsewhere. The category should be removed. All work in progress should happen through extensions | ||
</gallery> | </gallery> | ||
| + | |||
| + | ===Attaching units to image data=== | ||
| + | * This issue comes up in PET processing when we need to store SUV corrected volume. | ||
| + | * Is there a similar issue for RT data? | ||
| + | |||
| + | = Conclusion = | ||
| + | |||
| + | * Csaba presented the proposed improvement for opacity and slice intersection visibility of models in a hierarchy. And we all agree it made sens. For reference: http://slicer-devel.65872.n3.nabble.com/Opacity-and-slice-intersection-visibility-of-models-in-a-hierarchy-tt4027732.html | ||
| + | |||
| + | * Julien mentioned that at some point he will be working on adding "unit" awareness application wide | ||
| + | |||
| + | * Reviewed modules re-organization proposed by Ron | ||
| + | ** Wizard category will be removed + ChangeTracker will be added to Quantification | ||
| + | ** Endoscopy -> will be moved into extension | ||
| + | ** Testing + Developer tools: Hidden by default. It will be possible to show "DeveloperTools / Testing" by enabling it from the settings. | ||
| + | ** Resample category: We probably need to discuss further | ||
| + | ** Editor in both segmentation and core modules - What should we do instead ? | ||
| + | ** Filtering: We need to come up with a clear plan | ||
| + | ** Surface Models: ICP. It shouldn't be to hard to create the associated extension. | ||
| + | ** Multivolume: It seems creating a "Multivolume" category makes sens. | ||
| + | ** Deprecated / Legacy: Let's refine which module belong to this extension. See http://www.slicer.org/wiki/Documentation/Labs/DeprecatedModules | ||
| + | *** Discussed concept of meta-extension (similar to what is done in ubuntu for example) ... it is just an extension that specify a list of other extensions that should be installed. It would give us flexibility. | ||
Latest revision as of 17:00, 21 November 2019
Home < Developer Meetings < 20130226Contents
To discuss
Changes proposed by Csaba
- Opacity and slice intersection visibility of models in a hierarchy - See http://slicer-devel.65872.n3.nabble.com/Opacity-and-slice-intersection-visibility-of-models-in-a-hierarchy-tt4027732.html
Module reorganization
Introduction
The listing of modules should be organized from the vantage point of an early stage end user. Power users know what module they want and usually look in the alphabetic listing. Developer oriented tools should not be prominent and should not crowd the listings. Developers should be directed as much as possible to the wiki as a start point.
- We should reorganize the listing of modules in such a way that each category has only one choice per category/subcategory presented initially and everything else is under a tab called "Advanced". This is consistent with the way modules in Slicer should be organized.
- We should come up with guidance for developers on how to organize extensions. In some cases it makes sense for them to be in their own category and some cases, individual modules should be spread out to existing categories. Modules derived from extensions should have the extension acronym inside the module name. As a general rule, extension derived modules should be under the "advanced" section of a category so that the top level is not "messed up"
Listing of Modules
- Slicer 4 Module Reorganization 2013-02-26
Core Modules: Should we remove from or add to anything in this list? Also, wizards is empty and should be removed
Informatics: Is something missing?
Registration: Where does Resample belong? Its here, its under converters, its under diffusion. We might want to introduce a resample toplevel category and add some organization about what resample should be used when.
Segmentation: Editor is listed here and under core modules. Is this a good idea?
Quantification: Is anything missing
Diffusion: Interactive seeding should be promoted to the top level of this category
IGT: this is where all the igt extensions should land
Filtering: This category should get reviewed. I think that one each, but with documentation aimed at end users, should be enough.
Surface Models: Is this the best name for this category? We need ICP registration. Its a must.
Converters: Is this where the resampling tools belong? Does the Dicom converter belong here or into the Informatics category or both?
Endoscopy: This one is lonely
Utilities: Should be converted to extensions, I would think. I am not quite sure about the Brains utilities. Perhaps Hans can chime in.
Developers tools: Is there a good reason not to turn this into an extension? Most people will not need this. Should performance test be moved to the testing category?
Legacy: Should be turned into an extension. Demian, how about otsu, is the module used for DTI estimation or is ITK accessed directly? http://www.slicer.org/wiki/Documentation/Labs/DeprecatedModules
Testing: Utilities, testing, developers tools should all be reviewed and reorganized together. As a guiding principle, the presentation should target end users. Developers should be directed to the developer page on the wiki.
Work in progress: the current modules should be moved elsewhere. The category should be removed. All work in progress should happen through extensions
Attaching units to image data
- This issue comes up in PET processing when we need to store SUV corrected volume.
- Is there a similar issue for RT data?
Conclusion
- Csaba presented the proposed improvement for opacity and slice intersection visibility of models in a hierarchy. And we all agree it made sens. For reference: http://slicer-devel.65872.n3.nabble.com/Opacity-and-slice-intersection-visibility-of-models-in-a-hierarchy-tt4027732.html
- Julien mentioned that at some point he will be working on adding "unit" awareness application wide
- Reviewed modules re-organization proposed by Ron
- Wizard category will be removed + ChangeTracker will be added to Quantification
- Endoscopy -> will be moved into extension
- Testing + Developer tools: Hidden by default. It will be possible to show "DeveloperTools / Testing" by enabling it from the settings.
- Resample category: We probably need to discuss further
- Editor in both segmentation and core modules - What should we do instead ?
- Filtering: We need to come up with a clear plan
- Surface Models: ICP. It shouldn't be to hard to create the associated extension.
- Multivolume: It seems creating a "Multivolume" category makes sens.
- Deprecated / Legacy: Let's refine which module belong to this extension. See http://www.slicer.org/wiki/Documentation/Labs/DeprecatedModules
- Discussed concept of meta-extension (similar to what is done in ubuntu for example) ... it is just an extension that specify a list of other extensions that should be installed. It would give us flexibility.
