[Insight-developers] PythonFFTImageFilter : marvin.jouy.inra.fr

[Luis Ibanez]

Hi Gaetan,

Actually, You were right in your assumption.   :-)

The practice during a code freeze used to be that CVS write
access was restricted to a couple of developer.

In this release, however, we are experimenting with a
democratization of the CVS repository. In this experiment,
no CVS write access has been removed from any developer.

In this way, all of them are still able to commit bug
fixes if necessary.


The process is working great so far. It illustrates a
great sense of community among the developers.


   Thanks a lot for committing the fix !


      Luis



----------------------
Gaëtan Lehmann wrote:
> 
> Le 23 juil. 08 à 17:11, Luis Ibanez a écrit :
> 
>>
>> Hi Gaetan,
>>
>>
>> Yes, we are in a code freeze,
>> but the commit of this image is intended to fix a test.
>>
>>
>> What we must avoid during the code freeze is:
>>
>>    adding functionalities, and/or adding new files.
> 
> 
> I thought that code freeze means that only a few developers still have  
> write access to the cvs repository, to prepare the release — I see  that 
> I was wrong :-)
> I have committed the fix.
> 
> Gaëtan
> 
> 
>>
>>
>>
>> During the Code Freeze we welcome any effort intended to:
>>
>>   a) fix bugs
>>   b) increase code coverage
>>   c) fix memory problems (which is actually like (a)).
>>
>>
>>
>> Please feel free to commit the updated image baseline
>> at your convenience.
>>
>>
>>     Thanks
>>
>>
>>         Luis
>>
>>
>> ---------------------
>> Gaëtan Lehmann wrote:
>>
>>> Hi Luis,
>>> Le 23 juil. 08 à 16:23, Luis Ibanez a écrit :
>>>
>>>>
>>>> Hi Gaetan,
>>>>
>>>> Thanks a lot for tracking this problem.
>>>>
>>>> Unless you have a reason to think that the new image is incorrect,
>>>> could you please update the baseline image in CVS ?
>>>>
>>> Sure — but aren't we in code freeze currently?
>>>
>>>> Please let us know if you think that there is a better way
>>>> to address this problem.
>>>>
>>>>
>>>>  Thanks
>>>>
>>>>
>>>>     Luis
>>>>
>>>>
>>>>
>>>> ----------------------
>>>> Gaëtan Lehmann wrote:
>>>>
>>>>> Hi Luis,
>>>>> I'm looking at that failed test. The first broken test appeared  
>>>>> on  may 23th:
>>>>> http://www.cdash.org/CDash/viewTest.php?onlyfailed&buildid=82917 
>>>>> <http://www.cdash.org/CDash/viewTest.php?onlyfailed&buildid=82917  >
>>>>> and seems related to:
>>>>> http://public.kitware.com/cgi-bin/viewcvs.cgi/Code/Algorithms/itkVnlFFTComplexConjugateToRealImageFilter.txx?root=Insight&view=log#rev1.11 
>>>>>   
>>>>> <http://public.kitware.com/cgi-bin/viewcvs.cgi/Code/Algorithms/itkVnlFFTComplexConjugateToRealImageFilter.txx?root=Insight&view=log#rev1.11  
>>>>> >
>>>>> http://public.kitware.com/cgi-bin/viewcvs.cgi/Code/Algorithms/itkVnlFFTRealToComplexConjugateImageFilter.txx?root=Insight&view=log#rev1.11 
>>>>>   
>>>>> <http://public.kitware.com/cgi-bin/viewcvs.cgi/Code/Algorithms/itkVnlFFTRealToComplexConjugateImageFilter.txx?root=Insight&view=log#rev1.11  
>>>>> >
>>>>> http://www.itk.org/Bug/view.php?id=6453
>>>>> WrapITK seems to have a test that ITK was missing. Updating the   
>>>>> baseline image Wrapping/WrapITK/images/ 
>>>>> FFTImageFilterImaginary.png  with the one produced by the test  
>>>>> seems like the right way to go.
>>>>> Regards,
>>>>> Gaëtan
>>>>> Le 15 juil. 08 à 20:08, Luis Ibanez a écrit :
>>>>>
>>>>>>
>>>>>> Hi Gaetan,
>>>>>>
>>>>>> We are wondering if you could help us track why the
>>>>>> PythonFFTImageFilter test is failing in  marvin.jouy.inra.fr
>>>>>>
>>>>>>
>>>>>> Thanks for any hint,
>>>>>>
>>>>>>
>>>>>>    Luis
>>>>>>
>>>>>>
>>>>> -- 
>>>>> Gaëtan Lehmann
>>>>> Biologie du Développement et de la Reproduction
>>>>> INRA de Jouy-en-Josas (France)
>>>>> tel: +33 1 34 65 29 66    fax: 01 34 65 29 09
>>>>> http://voxel.jouy.inra.fr  http://www.mandriva.org
>>>>> http://www.itk.org  http://www.clavier-dvorak.org
> 
>