Difference between revisions of "Slicer/Features/Modules"
From NAMIC Wiki
(New page: == December 13, 2007 == * David Gobbi: Option to turn off modules for OR * Steve Pieper: Needs refactoring so it will be as flexible as Slicer 2 (runtime). Slicer 3 is cMake based (pre-co...) |
|||
| Line 1: | Line 1: | ||
| + | =Title= | ||
| + | =Names= | ||
| + | *session leader | ||
| + | |||
| + | *participants | ||
| + | |||
| + | =Technology/Function description= | ||
| + | |||
| + | =Discussion= | ||
== December 13, 2007 == | == December 13, 2007 == | ||
* David Gobbi: Option to turn off modules for OR | * David Gobbi: Option to turn off modules for OR | ||
| Line 15: | Line 24: | ||
* Steve A: Can a module bring in any library? | * Steve A: Can a module bring in any library? | ||
* Steve P: Yes. The base can't depend on Matlab, but a module can. | * Steve P: Yes. The base can't depend on Matlab, but a module can. | ||
| − | * | + | * Steve P: Static modules are restrictive, because you can't extend for ex. for full VTK/ITK library if you have a limited one compiled in. |
| + | * S Barre: Start up time? | ||
| + | * Steve P: Might not be affected. | ||
| + | |||
| + | == Liver RF == | ||
| + | * Slicing class (orthogonal) | ||
| + | * RT imaging class / image source | ||
| + | * | ||
| + | |||
| + | =Potential application in IGT= | ||
| + | |||
| + | =Which part is already in Slicer= | ||
| + | |||
| + | =What is not= | ||
| + | |||
| + | =Who among us will take leading role?= | ||
| + | |||
| + | =Links= | ||
Revision as of 17:05, 13 December 2007
Home < Slicer < Features < ModulesContents
Title
Names
- session leader
- participants
Technology/Function description
Discussion
December 13, 2007
- David Gobbi: Option to turn off modules for OR
- Steve Pieper: Needs refactoring so it will be as flexible as Slicer 2 (runtime). Slicer 3 is cMake based (pre-compilation). I would prefer run-time dynamic. This would allow distributing modules independent of the base.
- Louis Ibanez: The benefit would be a standard Slicer for everybody. How about testing?
- Peter Kazanzides: It's the user's responsibility to make it sure it was tested before going to OR
- David: and turn off the loading of modules at startup.
- Louis: Versioning?
- Steve Aylward: It's useful to have this versioning, for ex. VTK/ITK.
- Steve P.: The nightly build should build the modules also, and test them together.
- Csaba Csoma: So we all agree that dynamic modules is a good thing. Question: what is module, what is basic functionality?
- Steve P: Base Features vs. Modules. Csaba's right, we should make for ex. Diffusion Imaging modular, because it's pretty specific.
- Noby Hata: There are classes that can go only to base, like tracker?
- Steve P: Theoretically we can make it generic enough. Should the concept of tracker be a base, or just the transform?
- Steve A: Can a module bring in any library?
- Steve P: Yes. The base can't depend on Matlab, but a module can.
- Steve P: Static modules are restrictive, because you can't extend for ex. for full VTK/ITK library if you have a limited one compiled in.
- S Barre: Start up time?
- Steve P: Might not be affected.
Liver RF
- Slicing class (orthogonal)
- RT imaging class / image source
