[Vv] vv day
Simon Rit
simon.rit at creatis.insa-lyon.fr
Wed Sep 29 14:01:52 CEST 2010
Sounds like a good initiative!
I'm not sure what you have in mind but it would be nice to have:
- a major code clean up. Remove everything that is unused and
reorganize large code files in a readable way.
- fix of memory leaks, try to do ShadowCopy instead of DeepCopy (see
change of Joel which I have removed because it was causing rigid
registration crashes)
- organize rendering in a supportable way to avoid useless renders.
About Kumar's email:
- point 1: there is no solution, if you want two images to be fused,
there has to be some blending... (cf my previous answer to Kumar). The
only thing that could be done is to have some transparent colors on
the fusion image.
Kumar, what do you mean by "The interplay between the Base image
Window/Level and overlay Window/Level is also not appropriate" ? For
fusion, they are separated. For image overlay, we could do the same
thing...
- point 3: I agree, we should be able to disable all options to have a light vv.
Cheers,
Simon
On Wed, Sep 29, 2010 at 12:45 PM, Dr.KUMAR RAJAMANI
<k_rajamani at cb.amrita.edu> wrote:
> Dear Joel, David
> Glad to hear about the code sprint
>
> The issues that matter most
>
> 1. The Display Window in VV is not perfect,
> Especially so in the Overlay/Fusion Mode
> The display is not bright and the the colormaps do not also
> address the brightness aspects
> There should be provision for non-linear correction of Window/Levels
> (Example Gamma Correction)
> There could be a widget to graphically control the Window/Level and also
> the mapping of intensity levels
>
> The interplay between the Base image Window/Level and overlay Window/Level
> is also not appropriate
>
> 2. There could be tool to draw ROI in a image
> ROI tools would add lot of value for VV tool
>
> 3. Registration Codes are now made mandatory in the current cvs version
> This could be made optional in the CMAKE files,
> Then only those interested need to recompile ITK with the flags
>
> If I get more thoughts I shall share them in subsequent emails
>
> Warm Regards
> Kumar
>
>
>
> From: Jo?l Schaerer <joel.schaerer at gmail.com>
> To: "vv at creatis.insa-lyon.fr" <vv at creatis.insa-lyon.fr>, Gauthier
> BOUILHOL <gauthier.bouilhol at gmail.com>, Loic Grevillot
> <loic.grevillot at gmail.com>, Louise Grezes-Besset
> <louise.grezesbesset at gmail.com>
> Subject: [Vv] vv day!
> Message-ID: <4CA30557.6060102 at gmail.com>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> Hi all,
>
> With David we have scheduled to work on vv on Tuesday, October 5th in the manner
> of a "code sprint": we block the day to try to improve vv as much as possible!
> You are of course welcome to join us, but could you please tell us what are the
> issues that matter the most to you? This way we can set up a list of priorities
> and avoid wasting our time :)
>
> Thanks,
>
> joel
>
> --
> Jo?l Schaerer, PhD
> Post-doctoral researcher
>
> Centre de lutte contre le cancer L?on B?rard
> Service de radioth?rapie
> 28 rue La?nnec
> 69373 LYON CEDEX 08
>
> Tel: 04 78 78 51 50
> 06 26 65 29 54
>
> http://www.creatis.insa-lyon.fr/rio
> http://www.creatis.insa-lyon.fr/rio/vv
>
>
>
> ------------------------------
>
> _______________________________________________
> vv mailing list
> vv at creatis.insa-lyon.fr
> http://www.creatis.insa-lyon.fr/mailman/listinfo/vv
>
>
> End of vv Digest, Vol 7, Issue 11
> *********************************
>
More information about the vv
mailing list