Developer Meetings/20141125

To discuss

• Integration of Segmentation object support into Slicer core:
  • mailing list discussion
  • Segmentation proposal
• Extensions developer tutorial presented last week at Iowa Slicer/QIICR meeting: http://wiki.na-mic.org/Wiki/index.php/Iowa2014
  • review attendee suggestions
  • is there a Python self-course we could recommend? http://www.na-mic.org/Wiki/index.php/2013_Project_Week_Breakout_Session:Slicer4Python
• Csaba reported issue http://www.na-mic.org/Bug/view.php?id=3894 - probably not annotations - who is the right person to look into it?
  • This was a weird Windows configuration issue, probably due to incorrectly found ini or exe paths. No need to discuss this, but next time if someone bumps into something like this, I can help fixing the issue. - Csaba
• vtkMRMLDoubleArrayNode improvements : http://slicer-devel.65872.n3.nabble.com/vtkMRMLDoubleArrayNode-improvements-tc4032935.html

Conclusion

• #3894: If issue occurs again, print statement or break point could be added to the function qSlicerCoreApplicationPrivate::discoverSlicerHomeDirectory()

• Python self-course:
  • Code academy: http://www.codecademy.com/en/tracks/python
  • Google's Python Class: https://developers.google.com/edu/python/

• Limitation of current implementation:
  • No overlapping contour
  • Only binary object
  • Not possible to store segmentation results
  • Closed surface needed in 3D not possible
  • Display of overlapping contour not possible
  • Different representation of the segmentation information are needed for different application
• Proposal: https://www.assembla.com/spaces/slicerrt/wiki/Segmentation
  • New SegmentationNode that could be derived from vtkMRMLScalarVolumeNode while transistioning
  • SegmentationNode: Can contain up to N segments
  • More details on the proposal page