Difference between revisions of "Developer Meetings/20170606"
From Slicer Wiki
| Line 20: | Line 20: | ||
= Conclusion = | = Conclusion = | ||
| + | * Home for SEM spec: | ||
| + | ** Slicer/SlicerExecutionModel-specfication makes sense | ||
| + | ** In future, could also have a yaml/json version of the spec | ||
| + | |||
| + | * EMSegment to git: | ||
| + | ** Makes sense. | ||
| + | ** to speed up download, could also use shallow clone ? Look like specifying a commit will not work, a branch name need to be used | ||
| + | |||
| + | * DICOM | ||
Revision as of 14:26, 6 June 2017
Home < Developer Meetings < 20170606 |
If you would like to list your topic here, create a wiki account and edit this page You can join the hangout using http://bit.ly/slicer-hangout-kw. |
Update
- Update of VTK: good progress. Talked with David Gobbi to indentify the best strategy to add support for Hierarchy file now required for wrapping
- EMSegment:
- Transition to git: History has been converted (include complete history)
- Slicer will be update to use https://github.com/Slicer/SlicerEMSegment
To Discuss
- SlicerExecutionModel specification home
- GithubPage associated with SlicerExecutionModel repository (or new repo named SlicerExecutionModel-specification)
- Add support for "executables" tag and addition to existing "executable" tage:
executable path="Foo" type="cpp|python"
- CLI parameters are accessible in Slicer thanks to function named SetParameterDefaultValue/GetParameterDefaultValue (doc / parameter parsing): possible improvement of the documentation or a more explicit name?
- Adding DICOM application settings panel.
Conclusion
- Home for SEM spec:
- Slicer/SlicerExecutionModel-specfication makes sense
- In future, could also have a yaml/json version of the spec
- EMSegment to git:
- Makes sense.
- to speed up download, could also use shallow clone ? Look like specifying a commit will not work, a branch name need to be used
- DICOM
