[Insight-developers] Direction Validation and Testing

[Bill Lorensen]

Kent,

Thanks for the reminder about your earlier article. It is a great
start on a revived effort. I look forward to your help on this
important issue.

Bill

On Mon, Apr 6, 2009 at 5:43 PM, kent williams
<norman-k-williams at uiowa.edu> wrote:
> I would point you at the IJ article I wrote to try and grapple with the
> problem 4 1/2 years ago:
>
> http://www.insight-journal.org/browse/publication/62
>
> Not because it's the last word on the subject -- more like it's the first
> word on the subject.
>
> I can help out on some of these issues.  We at Iowa have beat up on this
> stuff extensively, because it's extremely important to our ongoing
> development.  It's probably the single most time-consuming issue in our
> research -- all of the grad students seem to get new code working for their
> particular corpus of data, only to see it lose its mind when confronted with
> foreign data with e.g. non-zero origins or strange orientations...
>
>
>
> On 4/6/09 1:34 PM, "Bill Lorensen" <bill.lorensen at gmail.com> wrote:
>
>> Folks,
>>
>> As you can see from recent activity on the list (and the slicer3
>> developers' list) there are lots of questions regarding the handling
>> of direction cosines (orientations) in itk. We need a rigorous
>> approach to document, validate and test the directions, origins and
>> spacing of our images, readers, writers and algorithms.
>>
>> Since I am to blame for the current implementation of directions in
>> ITK, I will set up a wiki page (TBA) that will address this important
>> issue.
>>
>> Some of the issues we have to address:
>>
>> 1) Better documentation of the ITK coordinate system, directions,
>> origin and spacing.
>> 2) For each ITK readers/writers (aka ImageIO) represent  coordinate
>> system, directions, origin and spacing.
>> 3) A repository of VALIDATED test data with known meta data:
>> coordinate system, directions, origin and spacing.
>> 4) A methodology to validate and test the meta data. This methodology
>> must include 3rd party (non-ITK) validation of the data.
>>
>> and other concerns I am sure.
>>
>> Products of this effort should include:
>>
>> 1) Unambiguous documentation of ITK's  coordinate system, directions,
>> origin and spacing.
>> 2) An Insight Journal publication summarizing and documenting this effort.
>> 3) Updates to the Insight Users Manual to describe the results.
>>
>> Let's discuss this for a few days on the list before I set up the wiki page.
>>
>> Bill
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ITK FAQ at:
>> http://www.itk.org/Wiki/ITK_FAQ
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.itk.org/mailman/listinfo/insight-developers
>
>
>
> Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged.  If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited.  Please reply to the sender that you have received the message in error, then delete it.  Thank you.
>
>