[Insight-users] How can I take part in quality control

[Zachary Pincus]

Well, heh, there's the rub indeed: I'd love to contribute tests for 
python wrapping, but given that it's broken on my platform, I can't 
really develop or (more importantly) debug any tests on said platform. 
Kind of a catch-22 at this point...

If I can figure out how to get Python working just a little bit on Mac 
OS X, then that might be enough of a wedge for me to start working up 
some solid test cases. Right now the problem seems to be some deep 
magic shared library/linker stuff which is a little out of my league as 
far as debugging.

Zach


On Feb 26, 2004, at 12:50 AM, Luis Ibanez wrote:

>
> Hi Zach,
>
> You are right,
> Python and Tcl are not being extensively tested,
> and sure enough that is a factor that contributes
> to the wrapping being unstable.
>
> The solution is indeed quite simple. You can configure
> tests in python in your local build, and even if they
> are failing, post them to the Dashboard. The Experimental
> section is the place to start.
>
> If the tests show up failing on the Dashboard there
> will be more positive presure for fixing them and
> more information available for keeping track of the
> potential sources of error.
>
> The extensive testing is a self-regulating system,
> what is not tested breaks easily and hardly gets
> noticed. At this point and time, the Toolkit will
> be as good as the users-community will demand from
> it and as much as user's themselves will be willing
> to participate in the maintenance process.
>
> This is a completly transparent process. The code is
> open, the Dashboard is open. Please feel free to
> configure a couple of python test and post experimental
> builds or nightly builds to the Dashboard. As we get
> those fixed we can add your tests to the standard testing
> suite and progressively increase the coverage for Python,
> Tcl and Java.
>
>
>
> Regards,
>
>
>
>   Luis
>
>
>
> ----------------------
> Zachary Pincus wrote:
>> Hello,
>> One thing I've found is that the default test process (e.g. the one 
>> that you can set up with cmake, and that can be configured to report 
>> to the dashboards) does *not* test the python wrappers.
>> At least for me, the wrappers usually build fine and then fail at 
>> runtime. Unfortunately, there are very few python wrapping tests 
>> included with ITK, and none are part of the automated system. (This 
>> in fact might be part of the reason why the wrappers are so often 
>> broken?)
>> I would volunteer to work on some such tests that could be added to 
>> the build process, but unfortunately given that python wrapping is 
>> broken for me, I can't really do much development on tests for them 
>> (no positive control!)
>> Does anyone have any thoughts on this matter?
>> Zach Pincus
>> Department of Biochemistry and Program in Biomedical Informatics
>> Stanford University School of Medicine
>> On Feb 25, 2004, at 3:35 AM, Carlos Phillips wrote:
>>> Hi,
>>> I have been trying to use ITK on my dual G5. The problem is that I 
>>> need python wrapper support and dynamic library support or python 
>>> wrapper support are often broken. I would like to volunteer my 
>>> computer for quality control of builds including python wrappers. 
>>> Would this be useful? If so, how should I proceed?
>>>
>>> Carlos
>>>
>>> _______________________________________________
>>> Insight-users mailing list
>>> Insight-users at itk.org
>>> http://www.itk.org/mailman/listinfo/insight-users
>>>
>
>
>
> _______________________________________________
> Insight-users mailing list
> Insight-users at itk.org
> http://www.itk.org/mailman/listinfo/insight-users
>