Difference between revisions of "Developer Meetings/20150113"
From Slicer Wiki
m (Text replacement - "slicerWiki/index.php" to "wiki") |
|||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
== To discuss == | == To discuss == | ||
| + | The following topics are the continuation of discussion from 20141230 meeting. | ||
* DICOM export improvements | * DICOM export improvements | ||
** possible improvements to deal with all types of objects versus just one and ignoring the rest, as well as having to pass information between plugins | ** possible improvements to deal with all types of objects versus just one and ignoring the rest, as well as having to pass information between plugins | ||
* possibility to add multidimen data to slicer superbuild and ask people to migrate their modules to use it in stead of the multivolume module. | * possibility to add multidimen data to slicer superbuild and ask people to migrate their modules to use it in stead of the multivolume module. | ||
* a new PET SUV module and how best to display results (data probe mouse over showing calculation at each voxel vs returning a new volume with the calculation as the image data) | * a new PET SUV module and how best to display results (data probe mouse over showing calculation at each voxel vs returning a new volume with the calculation as the image data) | ||
| + | |||
| + | == Conclusion == | ||
| + | |||
| + | * Discussed Dicom export - Kevin will talk to Csaba to continue the work. | ||
| + | * Discussed integrating multidimen data into slicer superbuild and agreed it is a natural step to do. Kevin to discuss with Andras to get final approval and then will start the integration. | ||
| + | * Discussed PET SUV calculation work in Slicer community. | ||
| + | ** http://www.slicer.org/wiki/Documentation/4.4/Extensions/LongitudinalPETCT | ||
| + | ** http://wiki.slicer.org/wiki/Documentation/Nightly/Modules/dPetBrainQuantification | ||
| + | * Discussed how to work around for extensions that are only built and tested on certain platform (such as windows). | ||
| + | ** Developers should keep in mind to make their code cross-platform but can state that they can only support in certain platform. | ||
| + | ** in extension CMakeLists.txt, check build platform and disable building for other unsupported platforms. | ||
Latest revision as of 17:05, 21 November 2019
Home < Developer Meetings < 20150113To discuss
The following topics are the continuation of discussion from 20141230 meeting.
- DICOM export improvements
- possible improvements to deal with all types of objects versus just one and ignoring the rest, as well as having to pass information between plugins
- possibility to add multidimen data to slicer superbuild and ask people to migrate their modules to use it in stead of the multivolume module.
- a new PET SUV module and how best to display results (data probe mouse over showing calculation at each voxel vs returning a new volume with the calculation as the image data)
Conclusion
- Discussed Dicom export - Kevin will talk to Csaba to continue the work.
- Discussed integrating multidimen data into slicer superbuild and agreed it is a natural step to do. Kevin to discuss with Andras to get final approval and then will start the integration.
- Discussed PET SUV calculation work in Slicer community.
- Discussed how to work around for extensions that are only built and tested on certain platform (such as windows).
- Developers should keep in mind to make their code cross-platform but can state that they can only support in certain platform.
- in extension CMakeLists.txt, check build platform and disable building for other unsupported platforms.
