Difference between revisions of "Developer Meetings/20130709"

From Slicer Wiki
Jump to: navigation, search
m (Text replacement - "slicerWiki/index.php" to "wiki")
 
(11 intermediate revisions by 3 users not shown)
Line 7: Line 7:
 
* 4D Data support
 
* 4D Data support
 
** [https://www.assembla.com/spaces/slicerrt/wiki/Slicer_4D_data_representation_and_use_cases notes from Kevin]
 
** [https://www.assembla.com/spaces/slicerrt/wiki/Slicer_4D_data_representation_and_use_cases notes from Kevin]
** [http://wiki.slicer.org/slicerWiki/index.php/Documentation/Nightly#Work_in_Progress MultiVolume Importer/Explorer]
+
** [http://wiki.slicer.org/wiki/Documentation/Nightly#Work_in_Progress MultiVolume Importer/Explorer]
 
* Numpy windows build patch from Lichen: https://github.com/llcmgh/python-cmake-buildsystem/compare/fix_numpy
 
* Numpy windows build patch from Lichen: https://github.com/llcmgh/python-cmake-buildsystem/compare/fix_numpy
 
* SimpleFilters from Brad:
 
* SimpleFilters from Brad:
Line 23: Line 23:
 
* <del>Check with Matt what is the agenda for ITK 4.4.1 ?</del>
 
* <del>Check with Matt what is the agenda for ITK 4.4.1 ?</del>
 
* After talking with Matt, we will compile list of fixes that we would like to see in 4.4.1 :)
 
* After talking with Matt, we will compile list of fixes that we would like to see in 4.4.1 :)
** Ideally the following commit should be included: VisualStudio fix for VNL + [https://github.com/Kitware/ITK/commit/df6614403b19139c3831762d443c3390a29ad5e3 df66144] BUG: ImageSeriesWriter + GDCMImageIO loses info
+
** List of fixes documented in the following email thread on the ITK devel list. See http://www.itk.org/pipermail/insight-developers/2013-July/022922.html
 +
* For reference - See http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=22163
  
 
* Integrate Commit [https://github.com/Kitware/ITK/commit/2ffb32de2f890e2052eee57ee6f36d10471d8c0c 2ffb32de] into ITK ?
 
* Integrate Commit [https://github.com/Kitware/ITK/commit/2ffb32de2f890e2052eee57ee6f36d10471d8c0c 2ffb32de] into ITK ?
Line 29: Line 30:
 
** Now a show stopper for the release.
 
** Now a show stopper for the release.
 
** If Brad has time, he will integrate
 
** If Brad has time, he will integrate
 +
 +
* SimpleFilters from Brad:
 +
** Jc: Create a repository on Slicer github organization where the Json file of SimpleITK will be imported using git subtree. That way, it will be possible to keep track of the file while maintaining a set of patches specific to Slicer.
 +
** Brad: Add the json file and update the current topic
 +
 +
* Markups module
 +
** Topic will be available for review soon (please comment on unsquashed topic)
 +
** Unsquashed topic: https://github.com/naucoin/Slicer/commits/Markups
 +
** Squashed topic: https://github.com/naucoin/Slicer/commits/Markups-Squashed-2013-07-09
 +
 +
* 4D Data support
 +
** Discuss the [https://www.assembla.com/spaces/slicerrt/wiki/Slicer_4D_data_representation_and_use_cases different approach]. Seems the consensus is to make use of the ParameterHierarchyNode and tune performance accordingly.

Latest revision as of 17:04, 21 November 2019

Home < Developer Meetings < 20130709

To discuss


Conclusion

  • Integrate Commit 2ffb32de into ITK ?
    • Known issues: Not tested + Breaking multi threading in SimpleITK
    • Now a show stopper for the release.
    • If Brad has time, he will integrate
  • SimpleFilters from Brad:
    • Jc: Create a repository on Slicer github organization where the Json file of SimpleITK will be imported using git subtree. That way, it will be possible to keep track of the file while maintaining a set of patches specific to Slicer.
    • Brad: Add the json file and update the current topic
  • 4D Data support
    • Discuss the different approach. Seems the consensus is to make use of the ParameterHierarchyNode and tune performance accordingly.