Difference between revisions of "Developer Meetings/20130709"

From Slicer Wiki
Jump to: navigation, search
Line 35: Line 35:
  
 
* Markups module
 
* Markups module
** Topic will be available for review soon
+
** Topic will be available for review soon (please comment on unsquashed topic)
 
** Unsquashed topic: https://github.com/naucoin/Slicer/commits/Markups
 
** 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
 
* 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.
 
** 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.

Revision as of 21:51, 9 July 2013

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.