Developer Meetings/20120515

Attendees:

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.