[Insight-users] Convert Zeiss .zvi files

[Curtis Rueden]

Hi Darren,

I'm a little puzzled by the farsight build wiki.  It appears to be nothing
> more than an ITK build, so what's special about "farsight" that it should be
> identified as something more than Insight (ITK)?
>

FARSIGHT is an effort to provide an image analysis toolkit for microscopy,
based on ITK. There is an (incomplete) list of modules included in FARSIGHT
listed at:

  http://www.farsight-toolkit.org/wiki/Table_of_Contents

It is still very early days for FARSIGHT, with the SVN repository just
opening up in recent weeks, so everything is still pretty rough around the
edges.

Badri Roysam, the head of the project, can comment further on goals and
directions if you are interested.

As for OSX, there are no build instructions (most of the linux instructions
> might apply, but actually it's a lot more complicated because OSX can an
> rpath nightmare when it comes to shared libs).  I think the entire farsight
> build wiki could be replaced, for OSX, with a one line MacPorts command:
>
> sudo port install InsightToolkit
>
> This will probably do everything at all stages identified on this wiki
> thread:
>

As far as compililng ITK, yes, if the MacPorts version of ITK includes the
CableSWIG stuff with WrapITK. (My understanding is that FARSIGHT needs that
for its Python interface.)

There are still more instructions to be written on compiling FARSIGHT
itself, once all the dependencies are set up.

http://farsight-toolkit.org/wiki/FARSIGHT_Tutorials/Building_Software
>
> The MacPorts system will take care of all the dependencies (cmake, python,
> cableswig).  Please see this ITK wiki page for more details:
> http://www.vtk.org/Wiki/ITK_MacPorts_Package_Maintainers
>
> Moreover, _please_ link to that page from the farsight tutorial on the
> build process, it might save everyone a lot of time and headaches (because I
> know just how painful it was to put it all together in MacPorts).
>

Noted on the Building_Software page.

If you need to develop ITK using macports, that might be done too, but it
> requires a little bit of tweaking on the macports installation process.  The
> macports installation uses several phases and a developer could stop after
> the build phase.  At that point, you have a complete source tree and a
> separate build tree.  So you could try this:
>
> sudo port build InsightToolkit
>
> Then go look in the build tree, under /opt/local/var/macports/build/
>

Cool; I saw this note on the ITK_MacPorts_Package_Maintainers page too, so
hopefully people who care will notice that.

-Curtis

On Wed, Jun 24, 2009 at 3:08 PM, Darren Weber
<darren.weber.lists at gmail.com>wrote:

>
> I'm a little puzzled by the farsight build wiki.  It appears to be nothing
> more than an ITK build, so what's special about "farsight" that it should be
> identified as something more than Insight (ITK)?
>
> As for OSX, there are no build instructions (most of the linux instructions
> might apply, but actually it's a lot more complicated because OSX can an
> rpath nightmare when it comes to shared libs).  I think the entire farsight
> build wiki could be replaced, for OSX, with a one line MacPorts command:
>
> sudo port install InsightToolkit
>
> This will probably do everything at all stages identified on this wiki
> thread:
> http://farsight-toolkit.org/wiki/FARSIGHT_Tutorials/Building_Software
>
> The MacPorts system will take care of all the dependencies (cmake, python,
> cableswig).  Please see this ITK wiki page for more details:
> http://www.vtk.org/Wiki/ITK_MacPorts_Package_Maintainers
>
> Moreover, _please_ link to that page from the farsight tutorial on the
> build process, it might save everyone a lot of time and headaches (because I
> know just how painful it was to put it all together in MacPorts).
>
> If you need to develop ITK using macports, that might be done too, but it
> requires a little bit of tweaking on the macports installation process.  The
> macports installation uses several phases and a developer could stop after
> the build phase.  At that point, you have a complete source tree and a
> separate build tree.  So you could try this:
>
> sudo port build InsightToolkit
>
> Then go look in the build tree, under /opt/local/var/macports/build/
>
> Take care,
> Darren
>
>
>
>
>
> On Wed, Jun 24, 2009 at 11:55 AM, Curtis Rueden <ctrueden at wisc.edu> wrote:
>
>> Hi Darren,
>>
>> What's the latest on this project?  Is there a wiki how-to on this?
>>>
>>
>> The project is currently under active development. Currently, the plugin
>> works with ITK 3.12 on Mac OS X and Linux. Soon it will compile with Visual
>> Studio on Windows as well (pending a commit from me -- and thanks to Alex
>> Gouaillard for his help tracking down some Windows issues).
>>
>> There are a number of improvements I am in the process of making,
>> including support for RGB and vector images, and dimensions beyond 3D. I
>> would also like to make the build easier to do, as much as possible at
>> least.
>>
>> You can access the code by checking out the LOCI Software codebase from
>> SVN:
>>
>>   https://skyking.microscopy.wisc.edu/svn/java/trunk
>>
>> The relevant components are in components/native/bf-cpp and
>> components/native/itk-plugin. See the readme.txt files for details. Please
>> note that as of this writing, the skyking server is down due to a
>> large-scale power outage on the UW-Madison campus (some construction mishap,
>> I think).
>>
>> There is also a preliminary set of wiki pages on how to compile the plugin
>> on the FARSIGHT wiki at:
>>
>>
>> http://farsight-toolkit.org/wiki/FARSIGHT_Tutorials/Building_Software/Bio-Formats
>>
>> Note that you do not actually need to build FARSIGHT to use the ITK plugin
>> as is (the wiki pages are written with the idea that the plugin will be used
>> within FARSIGHT, but there is no requirement to do so). The plugin is merely
>> an ITK ImageIO plugin, and should work with any code that uses
>> itkImageFileReader.
>>
>> Lastly, a bug introduced in ITK CVS five weeks ago (which should be fixed
>> soon) will prevent the plugin from working properly with image data beyond
>> 2D in certain cases.
>>
>> I will keep the list posted on my progress.
>>
>> -Curtis
>>
>> On Wed, Jun 24, 2009 at 1:48 PM, Darren Weber <
>> darren.weber.lists at gmail.com> wrote:
>>
>>>
>>>> Curtis is working on making bioformats usable from ITK
>>>
>>>
>>>
>>> What's the latest on this project?  Is there a wiki how-to on this?
>>>
>>> Thanks,
>>> Darren
>>>
>>>
>>> _____________________________________
>>> 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-users
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.itk.org/pipermail/insight-users/attachments/20090629/13044549/attachment-0001.htm>