Developer Meetings/20130709

To discuss

• Release status
  • ITK Version update needed http://na-mic.org/Mantis/view.php?id=2945#c8943
    • What to do about missing CLI buffer reuse patch? See https://github.com/Kitware/ITK/commit/2ffb32de2f890e2052eee57ee6f36d10471d8c0c
• 4D Data support
  • notes from Kevin
  • MultiVolume Importer/Explorer
• Numpy windows build patch from Lichen: https://github.com/llcmgh/python-cmake-buildsystem/compare/fix_numpy
• SimpleFilters from Brad:
  • WIP https://github.com/blowekamp/Slicer/tree/AddSimpleFiltersModule
  • Manage import of json from SimpleITK? Subtree merge? Copy from SimpleITK source dir?
• Pending SimpleITK patches from Brad
  • https://github.com/Slicer/Slicer/pull/51
  • https://github.com/Slicer/Slicer/pull/50
• Markups
  • squashing commits and getting ready to git svn dcommit

Conclusion

• Check with Matt what is the agenda for ITK 4.4.1 ?
• After talking with Matt, we will compile list of fixes that we would like to see in 4.4.1 :)
  • 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 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

• 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 different approach. Seems the consensus is to make use of the ParameterHierarchyNode and tune performance accordingly.