[Insight-developers] reading 3D tiff (/dcm pair Mevis)

[Bill Lorensen]

Rashindra,

Another thing to look at is the list of tif files that needed changes
after the last upgrade:

http://public.kitware.com/cgi-bin/viewcvs.cgi/Utilities/itktiff/?root=Insight&sortby=rev#dirlist

Any file with a revision other than 1.1 has changes that were required
after the initial import. There are about a dozen of these files.

Bill

On Tue, Sep 23, 2008 at 9:26 AM, Luis Ibanez <luis.ibanez at kitware.com> wrote:
>
> Hi Rashindra,
>
>
>                 Thanks for volunteering !
>
>
> Don't worry, you don't have to do all the TIFF update by yourself.
>
> We will assist you in the process.
>
>
> The first thing you should take a look at, is the process for
> mangling the library symbols.
>
> Please look at the file:
>
>     Insight/Utilities/itktiff/itk_tiff_mangle.h
>
> The mangling of symbols is necessary to make possible to combine
> ITK with other libraries that also include TIFF as a third party
> library (e.g. VTK). If we don't mangle the TIFF symbols, then
> duplicate symbols will be found at link time.
>
> Typically, you can simply start with the current list of mangled
> symbols, and as we test builds of InsightApplications, the linker
> will let us know of any symbols that may be missing.
>
> We should also pay a lot of attention to the following files:
>
>
>    * RELEASE-DATE
>    * README
>    * VERSION
>    * COPYRIGHT**
>
> particularly the last one  :-)
>
>
> The best way to proceed is for you to setup an Experimental
> build from your machine (whether it is Windows, Linux, or Mac),
> and once you can submit regularly from it, then start updating
> the TIFF library in your *local* build, without committing
> any thing yet to the CVS repository.
>
> It will be very helpful if you also have an Experimental build
> of InsightApplications, with USE_VTK enabled, since in this way
> you will be able to monitor the level of compliance in the symbol
> mangling.
>
> Once you get a stable build in your machine, let the other
> developers know by posting email to the Developers mailing list.
>
> At that point we can select a date for you to commit the new
> version of the library, and in the days following that commit
> we will help you get this to work in other platforms. Typically
> we expect to find issues in Borland, 64bits architectures, and
> SunOS.
>
>
> Please let us know if you have any questions,
>
>
>   Thanks
>
>
>      Luis
>
>
> ----------------------------
> Rashindra Manniesing wrote:
>>
>> HI Luis and others,
>>
>> Thanks for your reply. I did not realize that updating 3d-party libs may
>> be
>> a non-trivial task considering the multitude of supported platforms.
>>
>> I would be interested to contribute,
>>
>> Best regards, Rashindra.
>>
>> -----Original Message-----
>> From: Luis Ibanez [mailto:luis.ibanez at kitware.com] Sent: Saturday,
>> September 20, 2008 23:39
>> To: Rashindra Manniesing
>> Cc: insight-developers at itk.org
>> Subject: Re: [Insight-developers] reading 3D tiff (/dcm pair Mevis)
>>
>>
>> Hi Rashindra,
>>
>> Please note that the current version of TIFF in ITK *does*
>> support 3D images by using the multi-frame support.
>>
>> You can save now an 3D itk::Image into a TIFF file, and you will
>> get the slices as the frames into a multi-frame TIFF file.
>>
>>
>>
>> That being said, updating the TIFF (and other) libraries in the
>> Utilities directory is something that we could address in the
>> upcoming releases.
>>
>> We have added your request to the list of items for the 2008-2009
>> roadmap of ITK:
>>
>>    http://www.itk.org/Wiki/ITK_Roadmap_2008_2009
>>
>> Please feel free to add any comments to the TIFF entry.
>> http://www.itk.org/Wiki/ITK_Roadmap_2008_2009#TIFF
>>
>>
>> Just for the record:
>>
>>   Updating 3rd party libraries is easier said than done.
>>
>>   Our previous experience have shown that a typical update
>>   will take about three weeks of effort before the dust settles
>>   down. This is mainly due to the need to get things working in
>>   all the supported platforms.
>>
>>
>>
>>    Regards,
>>
>>
>>
>>       Luis
>>
>>
>> ----------------------------
>> Rashindra Manniesing wrote:
>>
>>> Dear all,
>>>
>>>
>>>
>>> I am interested in extending the itk imageIO factor to support the
>>> (Mevis) dcm/tiff file format (3D).
>>>
>>>
>>>
>>> It seems that the current tiff fileformat only supports 2D files.
>>> However, since ITK uses libtiff, it should be easy to extend to 3D.
>>>
>>>
>>>
>>> My questions:
>>>
>>>
>>>
>>> -          the current libtiff version in itk does not seem to be the
>>> most recent one. Can we expect an update in the near future?
>>>
>>> -          Same question for gdcm
>>>
>>> -          Who is managing these libraries in itk, perhaps we can
>>> communicate directly.
>>>
>>>
>>>
>>>
>>>
>>> A possibility, as single user, is to simply use external libraries
>>> (setting with cmake), but I suppose updating to the latest versions of these
>>> packages would be beneficial for the general audience,
>>>
>>>
>>>
>>> Best regards,
>>>
>>>
>>>
>>> Rashindra Manniesing.
>>>
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Insight-developers mailing list
>>> Insight-developers at itk.org
>>> http://www.itk.org/mailman/listinfo/insight-developers
>>
>>
>>
> _______________________________________________
> Insight-developers mailing list
> Insight-developers at itk.org
> http://www.itk.org/mailman/listinfo/insight-developers
>