[Vv] VV information

[David Sarrut]

Hello,

some information about our last thoughts on VV

- correction of memory leak is on the way. But slightly more difficult than
expected.

- we plan to have a (major ?) code consolidation regarding how vv load
images and manage memory. This will be discussed and planned in 2 weeks from
here. The main goal is to avoid image data copy between ITK and VTK, and
avoid high memory consumption when "splitting" images (from 4D to 3D+t or 3D
to 2D+t). Any comments welcome.

- Joel & I made some modification to allow speed up compilation
when developing. First you can compile vv without any other unneeded
libraries (say OFF in cmake). Second, you can change manually the
vv/CMakeLists.txt at the bottom and comments any or all the AutoTool, they
won't be compiled anymore when doing "make vv" (do not forget to specify the
target 'vv' here). FYI : the AutoTools are kind of "static" plugins.

- the dashboard has been moved (thank Joel !) to the cluster of creatis.
Joel can you send the URL please ? What is interesting is that we try to
compile vv against the future ITKv4. For the moment it does not compile
because of file missing related to GDCM. Any ideas ?

David

-- 
David Sarrut, Phd
Chargé de recherche CNRS
Centre de lutte contre le cancer Léon Bérard
28 rue Laënnec, 69373 Lyon cedex 08
Laboratoire CREATIS-LRMN UMR CNRS 5220, Inserm U 630
Tel : 04 78 78 51 51 / 06 74 72 05 42
http://www.creatis.insa-lyon.fr/rio
_________________________________
 "2 + 2 = 5,  for extremely large values of 2"
_________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.creatis.insa-lyon.fr/pipermail/vv/attachments/20101015/57d2349c/attachment.html>