Developer Meetings/20120515

Attendees: Alex, Chris, Jc, Julien, Nicole, Steve

To discuss

• Fix release date
  • Slicer 4.1.1:
    • Freeze: NA - Release date: June 1st
  • Slicer 4.2
    • Freeze: August 1st - Release date: August 20
• Before next week meeting:
  • Define all issues (bug and feature) associated with target 4.2
  • Which issues/feature should we expect for 4.2 ?
  • Every developer should make sure the issue assigned to him will be resolved 3 weeks before release date (August 1st)
• Road map is forming: http://na-mic.org/Mantis/roadmap_page.php
  • VS2010: Slicer 4.2.0 ? http://www.na-mic.org/Bug/view.php?id=2002
  • ITKv4: Slicer 4.3.0 ? http://na-mic.org/Mantis/view.php?id=2007
  • Qt 4.8.1: Slicer 4.3.0 ? See http://www.na-mic.org/Bug/view.php?id=2046
• Let's think about Slicer 4.4
• Transition to git ? Slicer 4.3.0 ?

• Volume_streaming_and_MRML

= Volume streaming and MRML

From Laurent:

Hello,

I've seen Andriy is using vtkMRMLDiffusionWeightedImageNode to store several volumes in his 4D module.
I would like to use it with the same purpose, but with streaming volumes.

The major difference is I don't know number of volumes I will receive. I looked at the vtkMRMLDiffusionWeightedImageNode and, when we call SetNumberOfGradient, it seems, it's reseting BValue array and gradient array. 

If I understood it, we use gradient array to store our ImageData. 

My first thought has been, when I  receive a volume, increase the value of NumberOfGradients, then, add the new volume in the gradient array.
However, if SetNumberOfGradient is reseting these arrays, this will erase my previous volumes store in it.

I still can copy them before, then SetNumberOfGradient, then put them in the array (with the new size) and add my new volume at the end, but this is not efficient at all (especially when number of volumes is increasing).

Please, could you let me know if I misunderstood something. If not, is there any workaround ?

Thank you.

Conclusion

• Discussed release date for 4.1.1 and 4.2
  • 4.1.1
    • Planned for June 1st. No feature freeze is expected.
    • It will consist in creating a branch of 4.1 and integrating tweaks mainly related to extensions support. Related issues are listed here.
  • 4.2
    • Need to clearly define which features and bug fixes we want to integrate. As of today, the list is here.
    • No special release will be done for RSNA (November). The plan will be to use 4.2.
    • As of today, all issues labelled "crash" have been targeted for 4.2.
    • TBD: Before *NEXT* Tuesday, developers are expected to review issue assigned to them and targeted for 4.2. If you believe an issue can't be resolved by mid-August / beginning of September, please let me know.

• Discussed update of DCMTK
  • Integration of DCMTK RT components/classes into official repository will be done at project week.

• Discussed VS2010 Support
  • Currently targeted for 4.2.0
  • Issue #2002

• Discussed ITKv4 Support
  • Currently targeted for 4.3.0
  • Issue #2007

• Discussed Qt 4.8.1 Support
  • Currently targeted for 4.3.0
  • Issue #2046

• Discussed transition to Git
  • Will definitively happen before the end of they year
  • Probably for 4.3.0
  • Issue #2059
  • Before doing so, testing data will be moved into Midas. See #2060

• Discussed directory layout of scripted module in Slicer4
  • Scripted module will be moved into dedicated directory. Will be similar to scripted extension
  • Issue: #2058

• Discussed the layout of extensions
  • As of today, it will always be assumed a CMakeLists.txt will be available at the top level of your extension