<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Thanks. It would not have taken so long if I had not made that typo, and if I were a bit more mentally agile.<br>
<br>
Slicer is now built on my machine, and I am about to test it on some files. One thing puzzles me - when I Load Data and ask to select a file (or directory) it takes an awfully long time for any files to appear - anything from 30 sec to more than a minute.
Is this normal?<br>
<br>
Gib<br>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div style="direction: ltr;" id="divRpF910522"><font color="#000000" face="Tahoma" size="2"><b>From:</b> Steve Pieper [pieper@isomics.com]<br>
<b>Sent:</b> Thursday, 18 September 2014 11:10 a.m.<br>
<b>To:</b> Gib Bogle<br>
<b>Cc:</b> Matt McCormick; Bradley Lowekamp; slicer-devel@bwh.harvard.edu; community@itk.org<br>
<b>Subject:</b> Re: [slicer-devel] BigTIFF<br>
</font><br>
</div>
<div></div>
<div>
<div dir="ltr">Hi Gib -
<div><br>
</div>
<div>Way to see it through! those vtk*Python and vtk*PythonD should be autogenerated and not manually edited so maybe you are already there?</div>
<div><br>
</div>
<div>-Steve</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Sep 17, 2014 at 6:35 PM, Gib Bogle <span dir="ltr">
<<a href="mailto:g.bogle@auckland.ac.nz" target="_blank">g.bogle@auckland.ac.nz</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
Yay! The vtkITK project built OK. That doesn't mean what I did is right, of course. There are two more projects to go, vtkITKPython, and vtkITKPythonD.<br>
<span class="">________________________________________<br>
From: Matt McCormick [<a href="mailto:matt.mccormick@kitware.com" target="_blank">matt.mccormick@kitware.com</a>]<br>
</span>Sent: Thursday, 18 September 2014 9:05 a.m.<br>
<div class="HOEnZb">
<div class="h5">To: Gib Bogle<br>
Cc: Bradley Lowekamp; Steve Pieper; <a href="mailto:slicer-devel@bwh.harvard.edu" target="_blank">
slicer-devel@bwh.harvard.edu</a>; <a href="mailto:community@itk.org" target="_blank">
community@itk.org</a><br>
Subject: Re: [slicer-devel] BigTIFF<br>
<br>
OK, thanks for the information<br>
<br>
Does changing the content on line 161 from<br>
<br>
itk::ImportImageContainer< unsigned long, type >::Pointer<br>
<br>
to<br>
<br>
image2##typeN::PixelContainer<br>
<br>
or at least<br>
<br>
itk::ImportImageContainer< itk::SizeValueType, type >::Pointer<br>
<br>
fix the issue?<br>
<br>
Thanks,<br>
Matt<br>
<br>
On Wed, Sep 17, 2014 at 4:32 PM, Gib Bogle <<a href="mailto:g.bogle@auckland.ac.nz" target="_blank">g.bogle@auckland.ac.nz</a>> wrote:<br>
> Yes Matt. That's my line 179 too. The error message is confusing because vtkITKExecuteDataFromFile is a complex macro. It does things that I do not have a good grasp of. Every occurrence of vtkITKExecuteDataFromFile gives a similar error, and there
are similar macros in other files that also give the same type of error. It is all somehow related to 'unsigned __int64', and I didn't get this error before when I was building (without knowing it) with ITK_USE_64BITS_IDS off.<br>
><br>
> It is not clear to me who would be best equipped to address this - ITK, VTK or Slicer experts.<br>
><br>
> I appreciate your attention to it very much!<br>
> Gib<br>
> ________________________________________<br>
> From: Matt McCormick [<a href="mailto:matt.mccormick@kitware.com" target="_blank">matt.mccormick@kitware.com</a>]<br>
> Sent: Thursday, 18 September 2014 5:06 a.m.<br>
> To: Gib Bogle<br>
> Cc: Bradley Lowekamp; Steve Pieper; <a href="mailto:slicer-devel@bwh.harvard.edu" target="_blank">
slicer-devel@bwh.harvard.edu</a>; <a href="mailto:community@itk.org" target="_blank">
community@itk.org</a><br>
> Subject: Re: [slicer-devel] BigTIFF<br>
><br>
>> 3>C:\Slicer\Libs\vtkITK\vtkITKArchetypeImageSeriesScalarReader.cxx(179)<br>
><br>
> Is this with the latest version of Slicer?<br>
><br>
> My line 179 says<br>
><br>
> vtkITKExecuteDataFromFile(VTK_DOUBLE, double);<br>
><br>
> Thanks,<br>
> Matt<br>
><br>
> On Wed, Sep 17, 2014 at 12:02 PM, Gib Bogle <<a href="mailto:g.bogle@auckland.ac.nz" target="_blank">g.bogle@auckland.ac.nz</a>> wrote:<br>
>> Hi Matt,<br>
>> I don't know what to look for to see what is causing this error in the vtkITK build. Should vtkITK know about ITK_USE_64BITS_IDS?<br>
>> thanks<br>
>> Gib<br>
>> ________________________________________<br>
>> From: Matt McCormick [<a href="mailto:matt.mccormick@kitware.com" target="_blank">matt.mccormick@kitware.com</a>]<br>
>> Sent: Thursday, 18 September 2014 3:55 a.m.<br>
>> To: Gib Bogle<br>
>> Cc: Bradley Lowekamp; Steve Pieper; <a href="mailto:slicer-devel@bwh.harvard.edu" target="_blank">
slicer-devel@bwh.harvard.edu</a>; <a href="mailto:community@itk.org" target="_blank">
community@itk.org</a><br>
>> Subject: Re: [slicer-devel] BigTIFF<br>
>><br>
>> Hi Gib,<br>
>><br>
>> Getting the builds states to propagate and follow how the get set can<br>
>> be tricky. A few pointers on where to look for the status:<br>
>><br>
>> 1) CMakeCache.txt (this file contains the build settings that CMake<br>
>> recognized from your input when you run CMake)<br>
>> 2) ITKConfig.cmake (this file will exist in the build tree or the<br>
>> install tree, and it contains CMake varables that may be used by other<br>
>> projects building against ITK)<br>
>> 3) itkConfigure.h (this is a header that has configured preprocessor<br>
>> definitions used when building)<br>
>><br>
>> HTH,<br>
>> Matt<br>
>><br>
>><br>
>><br>
>> On Wed, Sep 17, 2014 at 3:35 AM, Gib Bogle <<a href="mailto:g.bogle@auckland.ac.nz" target="_blank">g.bogle@auckland.ac.nz</a>> wrote:<br>
>>> Hi Bradley, Matt and Steve,<br>
>>><br>
>>> Now for the embarrassing confession. In External_ITK4.cmake I turned<br>
>>> ITKV3_COMPATIBILITY off and ITK_USE_64BITS_IDS on as suggested, but when I<br>
>>> finally checked what the code that is being built was using (with #if<br>
>>> defined ...) I discovered that both ITKV3_COMPATIBILITY and<br>
>>> ITK_USE_64BITS_IDS were off. How can this be?<br>
>>><br>
>>> It's easy, all it takes is a typo:<br>
>>> -DITK_USE_64_BITS_IDS:BOOL=ON<br>
>>> That typo has cost me a couple of days, and caused annoyance to a few<br>
>>> people, I suspect.<br>
>>><br>
>>> Unfortunately... now Slicer's vtkITK does not build. There are very many<br>
>>> errors like this:<br>
>>><br>
>>> 3>------ Build started: Project: vtkITK, Configuration: Release x64 ------<br>
>>> 3>Build started 17/09/2014 7:25:52 p.m..<br>
>>> 3>InitializeBuildStatus:<br>
>>> 3> Touching "vtkITK.dir\Release\vtkITK.unsuccessfulbuild".<br>
>>> 3>CustomBuild:<br>
>>> 3> Building Custom Rule C:/Slicer/Libs/vtkITK/CMakeLists.txt<br>
>>> 3> CMake does not need to re-run because<br>
>>> C:\s\b\Slicer-build\Libs\vtkITK\CMakeFiles\generate.stamp is up-to-date.<br>
>>> 3>ClCompile:<br>
>>> 3> vtkITKNumericTraits.cxx<br>
>>> 3> vtkITKArchetypeDiffusionTensorImageReaderFile.cxx<br>
>>> 3> vtkITKArchetypeImageSeriesReader.cxx<br>
>>> 3> vtkITKArchetypeImageSeriesScalarReader.cxx<br>
>>> 3> vtkITKArchetypeImageSeriesVectorReaderFile.cxx<br>
>>> 3> vtkITKArchetypeImageSeriesVectorReaderSeries.cxx<br>
>>> 3> vtkITKImageWriter.cxx<br>
>>> 3> vtkITKGradientAnisotropicDiffusionImageFilter.cxx<br>
>>> 3> vtkITKDistanceTransform.cxx<br>
>>> 3>C:\Slicer\Libs\vtkITK\vtkITKArchetypeImageSeriesScalarReader.cxx(179):<br>
>>> error C2679: binary '=' : no operator found which takes a right-hand operand<br>
>>> of type 'itk::ImportImageContainer<TElementIdentifier,TElement> *' (or there<br>
>>> is no acceptable conversion)<br>
>>> 3> with<br>
>>> 3> [<br>
>>> 3> TElementIdentifier=unsigned __int64,<br>
>>> 3> TElement=double<br>
>>> 3> ]<br>
>>> 3> c:\s\b\itkv4\modules\core\common\include\itkSmartPointer.h(124):<br>
>>> could be 'itk::SmartPointer<TObjectType><br>
>>> &itk::SmartPointer<TObjectType>::operator =(const<br>
>>> itk::SmartPointer<TObjectType> &)'<br>
>>> 3> with<br>
>>> 3> [<br>
>>> 3> TObjectType=itk::ImportImageContainer<unsigned long,double><br>
>>> 3> ]<br>
>>> 3> c:\s\b\itkv4\modules\core\common\include\itkSmartPointer.h(128):<br>
>>> or 'itk::SmartPointer<TObjectType><br>
>>> &itk::SmartPointer<TObjectType>::operator<br>
>>> =(itk::ImportImageContainer<TElementIdentifier,TElement> *)'<br>
>>> 3> with<br>
>>> 3> [<br>
>>> 3> TObjectType=itk::ImportImageContainer<unsigned long,double>,<br>
>>> 3> TElementIdentifier=unsigned long,<br>
>>> 3> TElement=double<br>
>>> 3> ]<br>
>>> 3> while trying to match the argument list<br>
>>> '(itk::SmartPointer<TObjectType>,<br>
>>> itk::ImportImageContainer<TElementIdentifier,TElement> *)'<br>
>>> 3> with<br>
>>> 3> [<br>
>>> 3> TObjectType=itk::ImportImageContainer<unsigned long,double><br>
>>> 3> ]<br>
>>> 3> and<br>
>>> 3> [<br>
>>> 3> TElementIdentifier=unsigned __int64,<br>
>>> 3> TElement=double<br>
>>> 3> ]<br>
>>><br>
>>> I presume these are related to the use of 64-bit integers.<br>
>>><br>
>>> Over to you guys :)<br>
>>><br>
>>> Gib<br>
>>> ________________________________<br>
>>> From: Bradley Lowekamp [<a href="mailto:blowekamp@mail.nih.gov" target="_blank">blowekamp@mail.nih.gov</a>]<br>
>>> Sent: Tuesday, 16 September 2014 12:45 a.m.<br>
>>> To: Steve Pieper<br>
>>> Cc: Gib Bogle; <a href="mailto:slicer-devel@bwh.harvard.edu" target="_blank">
slicer-devel@bwh.harvard.edu</a><br>
>>> Subject: Re: [slicer-devel] BigTIFF<br>
>>><br>
>>> Hello,<br>
>>><br>
>>> For you slicer build did you also remove the ITKV3_COMPATIBILITY flag here:<br>
>>> <a href="https://github.com/Slicer/Slicer/blob/master/SuperBuild/External_ITKv4.cmake#L48" target="_blank">
https://github.com/Slicer/Slicer/blob/master/SuperBuild/External_ITKv4.cmake#L48</a><br>
>>><br>
>>> To test for ITK big tiff compatibility, I'd recommend getting python 2.7<br>
>>> 64-bits then installing SimpleITK (i.e pip install SimpleITK), and try to<br>
>>> read and write files like these there. More information about getting<br>
>>> started is here[1].<br>
>>><br>
>>> You should be a able to generate a image with:<br>
>>><br>
>>> import SimpleITK as sitk<br>
>>> img = sitk.Image( [1250,1250,1250], sitk.sitkUInt8)<br>
>>> img += 10<br>
>>> stats = sitk.StatisticsImageFilter()<br>
>>> stats.Execute(img)<br>
>>> print stats<br>
>>><br>
>>> This should give you basic access to ITK in python to interactively<br>
>>> experiment with options with these large images. I have been able to load<br>
>>> large images with the binaries of SimpleITK on windows 64-bits. I don't know<br>
>>> if I have tried big tiff though.<br>
>>><br>
>>> A simular test could be done with C++ and ITK directly, but I think<br>
>>> SimpleITK in python may be quicker for experimentation.<br>
>>><br>
>>> Brad<br>
>>><br>
>>> [1] <a href="http://www.itk.org/Wiki/SimpleITK/GettingStarted" target="_blank">
http://www.itk.org/Wiki/SimpleITK/GettingStarted</a><br>
>>> [2]<br>
>>> <a href="http://www.itk.org/SimpleITKDoxygen/html/namespaceitk_1_1simple.html#a838017f46860e8a7bc8a9ebc7f3dbfee" target="_blank">
http://www.itk.org/SimpleITKDoxygen/html/namespaceitk_1_1simple.html#a838017f46860e8a7bc8a9ebc7f3dbfee</a><br>
>>><br>
>>> On Sep 15, 2014, at 7:37 AM, Steve Pieper <<a href="mailto:pieper@isomics.com" target="_blank">pieper@isomics.com</a>> wrote:<br>
>>><br>
>>> Hi Gib -<br>
>>><br>
>>> Are you testing only on windows? What we would often try to do for this<br>
>>> kind of debugging is to create a small example that other people can test on<br>
>>> their configurations. Slicer has a mechanism called a Self Test [1] to<br>
>>> allow easy replication and debugging across multiple platforms. It's ideal<br>
>>> if we can hone it down to something like what is described as a 'sscce' [2].<br>
>>> The self tests will typically download some data from a public web site, run<br>
>>> some operations, and then print something out saying if it passed or failed<br>
>>> (or it may crash). Since it's possible to make a small data file that<br>
>>> expands into a giant tiff image it should be pretty tractable to pose this<br>
>>> issue in the form of a self test.<br>
>>><br>
>>> Best,<br>
>>> Steve<br>
>>><br>
>>><br>
>>> [1]<br>
>>> <a href="http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/Tutorials/SelfTestModule" target="_blank">
http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/Tutorials/SelfTestModule</a><br>
>>><br>
>>> [2] <a href="http://sscce.org/" target="_blank">http://sscce.org/</a><br>
>>><br>
>>> On Mon, Sep 15, 2014 at 2:21 AM, Gib Bogle <<a href="mailto:g.bogle@auckland.ac.nz" target="_blank">g.bogle@auckland.ac.nz</a>> wrote:<br>
>>>><br>
>>>> Hi J-C,<br>
>>>><br>
>>>> Some more info about Slicer with big tiff files.<br>
>>>><br>
>>>> 1250x1250x1250 = 1,953,125,000 bytes loads and displays correctly<br>
>>>> 1300x1300x1300 = 2,197,000,000 bytes loads but does not display anything<br>
>>>> 1650x1650x1650 = 4,492,125,000 bytes fails to load (crashes reading page<br>
>>>> 72)<br>
>>>><br>
>>>> All suggestions will be gratefully received.<br>
>>>><br>
>>>> Cheers<br>
>>>> Gib<br>
>>>> ________________________________<br>
>>>> From: Jean-Christophe Fillion-Robin [<a href="mailto:jchris.fillionr@kitware.com" target="_blank">jchris.fillionr@kitware.com</a>]<br>
>>>> Sent: Sunday, 14 September 2014 8:32 p.m.<br>
>>>> To: Gib Bogle<br>
>>>> Cc: Steve Pieper; <a href="mailto:slicer-devel@bwh.harvard.edu" target="_blank">
slicer-devel@bwh.harvard.edu</a><br>
>>>> Subject: Re: [slicer-devel] BigTIFF<br>
>>>><br>
>>>> Hi Gib,<br>
>>>><br>
>>>> What do you mean by "reinstalled" ? You should not have to install Slicer<br>
>>>> to be able to execute it from the build directory.<br>
>>>><br>
>>>> After building with "Slicer_BUILD_BRAINSTOOLS" turned off the option<br>
>>>> "ITK_USE_64_BITS_IDS" added to the ITKv4 external project, it should work<br>
>>>> out.<br>
>>>><br>
>>>> When done building, make sure to start the Slicer launcher:<br>
>>>><br>
>>>> C:/path/to/project/Slicer-Superbuild/Slicer-build/Slicer.exe<br>
>>>><br>
>>>> and not the Slicer executable:<br>
>>>><br>
>>>><br>
>>>> C:/path/to/project/Slicer-Superbuild/Slicer-build/bin/Release/SlicerApp-real.exe<br>
>>>><br>
>>>><br>
>>>> By using the launcher, you ensure that the PATH are properly setup and the<br>
>>>> expected libraries are loaded.<br>
>>>><br>
>>>><br>
>>>> Hth<br>
>>>> Jc<br>
>>>><br>
>>>><br>
>>>> On Sat, Sep 13, 2014 at 11:49 PM, Gib Bogle <<a href="mailto:g.bogle@auckland.ac.nz" target="_blank">g.bogle@auckland.ac.nz</a>><br>
>>>> wrote:<br>
>>>>><br>
>>>>> I hope I understand correctly. I added the line as shown to<br>
>>>>> C:\Slicer\SuperBuild\External_ITKv4.cmake:<br>
>>>>> ...<br>
>>>>> # ZLIB<br>
>>>>> -DITK_USE_SYSTEM_ZLIB:BOOL=ON<br>
>>>>> -DZLIB_ROOT:PATH=${ZLIB_ROOT}<br>
>>>>> -DZLIB_INCLUDE_DIR:PATH=${ZLIB_INCLUDE_DIR}<br>
>>>>> -DZLIB_LIBRARY:FILEPATH=${ZLIB_LIBRARY}<br>
>>>>> # Big TIFF<br>
>>>>> -DITK_USE_64_BITS_IDS:BOOL=ON<br>
>>>>> ...<br>
>>>>><br>
>>>>> I then did ALL_BUILD in the root of the build directory (C:\s\b). I<br>
>>>>> presume this is the "superbuild". I then redid ALL_BUILD in<br>
>>>>> C:\s\b\Slicer-build, and ITKv4-build, and reinstalled. The program still<br>
>>>>> crashes with the big tiff. Is there somewhere I can check in the project<br>
>>>>> configuration files to see if setting ITK_USE_64_BITS_IDS actually took<br>
>>>>> effect?<br>
>>>>><br>
>>>>> Thanks<br>
>>>>> Gib<br>
>>>>> ________________________________<br>
>>>>> From: Steve Pieper [<a href="mailto:pieper@isomics.com" target="_blank">pieper@isomics.com</a>]<br>
>>>>> Sent: Sunday, 14 September 2014 1:36 p.m.<br>
>>>>><br>
>>>>> To: Gib Bogle<br>
>>>>> Cc: <a href="mailto:slicer-devel@bwh.harvard.edu" target="_blank">slicer-devel@bwh.harvard.edu</a><br>
>>>>> Subject: Re: [slicer-devel] BigTIFF<br>
>>>>><br>
>>>>> Hey Gib -<br>
>>>>><br>
>>>>> Sounds like progress - the ITK_USE_64_BITS_IDS should be set to ON in the<br>
>>>>> ITK build process [1] during the superbuild. I don't think much else was<br>
>>>>> required except turning off the IKTv3 parts.<br>
>>>>><br>
>>>>> [1]<br>
>>>>> <a href="https://github.com/Slicer/Slicer/blob/master/SuperBuild/External_ITKv4.cmake#L32-L68" target="_blank">
https://github.com/Slicer/Slicer/blob/master/SuperBuild/External_ITKv4.cmake#L32-L68</a><br>
>>>>><br>
>>>>> -Steve<br>
>>>>><br>
>>>>> p.s. I hear the ABs beat the Boks recently in a close match (we don't get<br>
>>>>> it on TV). So the Jo'berg game should be a great rematch!<br>
>>>>><br>
>>>>> On Sat, Sep 13, 2014 at 9:11 PM, Gib Bogle <<a href="mailto:g.bogle@auckland.ac.nz" target="_blank">g.bogle@auckland.ac.nz</a>><br>
>>>>> wrote:<br>
>>>>>><br>
>>>>>> You did warn me.<br>
>>>>>><br>
>>>>>> Here is the list of options not ticked:<br>
>>>>>><br>
>>>>>> Slicer_BUILD_BRAINSTOOLS<br>
>>>>>> _LEGACY_CLI<br>
>>>>>> _LandmarkRegistration<br>
>>>>>> _TESTING_EXTENSIONS<br>
>>>>>> _UPDATE_TRANSLATION<br>
>>>>>> _USE_GIT_PROTOCOL<br>
>>>>>> _OpenIGTLink<br>
>>>>>> _PYTHONQT_WITH_OPENSSL<br>
>>>>>> _PYTHONQT_WITH_TCL<br>
>>>>>> _QtTesting<br>
>>>>>> _SimpleITK<br>
>>>>>> _VTK_DEBUG_LINKS<br>
>>>>>> Slicer_WITH_LIBRARY_VERSION<br>
>>>>>><br>
>>>>>> USE_BRAINS*<br>
>>>>>> USE_ConvertBetweenFileFormats<br>
>>>>>> USE_DWIConvert<br>
>>>>>> USE_DebugImageViewer<br>
>>>>>> USE_GTRACT<br>
>>>>>> USE_ICCDEF<br>
>>>>>> USE_ImageCalculator<br>
>>>>>> USE_ReferenceAtlas<br>
>>>>>><br>
>>>>>> -------<br>
>>>>>><br>
>>>>>> Progress! Process Monitor showed me that the exit code was C0000139,<br>
>>>>>> which means a DLL was not found. I then realized that I have different<br>
>>>>>> occurrences of many of the DLLs on my disk (QT, ITK and VTK) and this<br>
>>>>>> prompted me to look more carefully at the PATH environment variable. I just<br>
>>>>>> tested with all the new paths at the start of the PATH string, and Slicer<br>
>>>>>> starts successfully! I can load a tiff! But ... it still crashes when I<br>
>>>>>> attempt to load a 4 GB tiff.<br>
>>>>>><br>
>>>>>> I am now wondering (belatedly!) about the way I tried to build with big<br>
>>>>>> tiff capability. I guessed, and added the entry ITK_USE_64BITS_IDS as<br>
>>>>>> 'bool'. It appears ticked in Ungrouped Entries. I really should have asked<br>
>>>>>> for directions before doing this - now I'm wondering if that switch actually<br>
>>>>>> had any effect. Is that the right thing to do, and if not, what is?<br>
>>>>>><br>
>>>>>> Thanks<br>
>>>>>> Gib<br>
>>>>>> ________________________________<br>
>>>>>> From: Steve Pieper [<a href="mailto:pieper@isomics.com" target="_blank">pieper@isomics.com</a>]<br>
>>>>>> Sent: Sunday, 14 September 2014 10:02 a.m.<br>
>>>>>><br>
>>>>>> To: Gib Bogle<br>
>>>>>> Cc: <a href="mailto:slicer-devel@bwh.harvard.edu" target="_blank">slicer-devel@bwh.harvard.edu</a><br>
>>>>>> Subject: Re: [slicer-devel] BigTIFF<br>
>>>>>><br>
>>>>>> Yes, well, don't say I didn't warn you! ; )<br>
>>>>>><br>
>>>>>> You do need loadable modules and you probably do want python (a lot of<br>
>>>>>> core stuff is in python, like the editor).<br>
>>>>>><br>
>>>>>> BRAINSTools should be off for now, since it needs ITKv3.<br>
>>>>>><br>
>>>>>> I'm not sure either what to do next, but I suggest maybe trying the<br>
>>>>>> Process Monitor from microsoft (sysinternals) and see what it was doing when<br>
>>>>>> it exited. But that may be a longshot.<br>
>>>>>><br>
>>>>>> -Steve<br>
>>>>>><br>
>>>>>> On Sat, Sep 13, 2014 at 4:39 PM, Gib Bogle <<a href="mailto:g.bogle@auckland.ac.nz" target="_blank">g.bogle@auckland.ac.nz</a>><br>
>>>>>> wrote:<br>
>>>>>>><br>
>>>>>>> Hi Steve,<br>
>>>>>>><br>
>>>>>>> That was an interesting exercise. I managed to build Slicer without<br>
>>>>>>> Qtloadablemodules. As you might expect, it was not much use. The program<br>
>>>>>>> started up but without any capabilities, just an empty shell. (I'm a bit<br>
>>>>>>> handicapped by not knowing anything about how Slicer is constructed.) So I<br>
>>>>>>> built it again, this time selecting most things except BRAINTools. The<br>
>>>>>>> build took a long time, partly because I turned on the Python option, which<br>
>>>>>>> I don't need. This time there were no errors, except for a couple of<br>
>>>>>>> occasions where the attempt to create a directory failed - this was because<br>
>>>>>>> the directory already existed, and was easily solved by deleting the<br>
>>>>>>> directory and building again. I installed everything that wanted to be<br>
>>>>>>> installed, and modified the environment variables to suit.<br>
>>>>>>><br>
>>>>>>> My sense of satisfaction was short-lived, however. When Slicer is<br>
>>>>>>> invoked the Acknowledgements screen flashes up briefly then the program<br>
>>>>>>> exits. There are no error messages. Dependency Walker shows that all the<br>
>>>>>>> DLLs are being found. I am assuming that BRAINTools is not needed (not<br>
>>>>>>> knowing what it is).<br>
>>>>>>><br>
>>>>>>> I sense that I must be close to getting it working, but I'm not sure<br>
>>>>>>> what to do next.<br>
>>>>>>><br>
>>>>>>> Cheers<br>
>>>>>>> Gib<br>
>>>>>>> ________________________________<br>
>>>>>>> From: Steve Pieper [<a href="mailto:pieper@isomics.com" target="_blank">pieper@isomics.com</a>]<br>
>>>>>>> Sent: Sunday, 14 September 2014 12:36 a.m.<br>
>>>>>>><br>
>>>>>>> To: Gib Bogle<br>
>>>>>>> Cc: <a href="mailto:slicer-devel@bwh.harvard.edu" target="_blank">slicer-devel@bwh.harvard.edu</a><br>
>>>>>>> Subject: Re: [slicer-devel] BigTIFF<br>
>>>>>>><br>
>>>>>>> Hi Gib -<br>
>>>>>>><br>
>>>>>>> A lot of the building goes on in parallel so you need to review the<br>
>>>>>>> whole build log to see what is going on. I'm guessing ITK didn't build<br>
>>>>>>> correctly. Typically I do a Control-A Control-C in the visual studio output<br>
>>>>>>> window and then paste it into a text editor to look for issues. Definitely<br>
>>>>>>> you don't want to be editing any of the visual studio files, since they are<br>
>>>>>>> generated by cmake every configure -- much better to sort out what is going<br>
>>>>>>> on at the cmake flag level.<br>
>>>>>>><br>
>>>>>>> Best,<br>
>>>>>>> Steve<br>
>>>>>>><br>
>>>>>>> On Fri, Sep 12, 2014 at 9:27 PM, Gib Bogle <<a href="mailto:g.bogle@auckland.ac.nz" target="_blank">g.bogle@auckland.ac.nz</a>><br>
>>>>>>> wrote:<br>
>>>>>>>><br>
>>>>>>>> Looking at the Project Properties for qSlicerBaseQTCore I notice<br>
>>>>>>>> something odd. Here is a snippet from the list of Linker > Input ><br>
>>>>>>>> Additional Dependencies:<br>
>>>>>>>><br>
>>>>>>>> ...<br>
>>>>>>>> C:\s\b\ITKv4-build\lib\Release\itktiff-4.6.lib<br>
>>>>>>>> C:\s\b\ITKv4-build\lib\Release\itkjpeg-4.6.lib<br>
>>>>>>>> C:\s\b\ITKv4-build\lib\Release\ITKIOMRC-4.6.lib<br>
>>>>>>>> C:\s\b\ITKv4-build\lib\Release\ITKIOImageBase-4.6.lib<br>
>>>>>>>> C:\s\b\VTKv5-build\bin\Release\vtkInfovis.lib<br>
>>>>>>>> C:\s\b\VTKv5-build\bin\Release\vtkWidgets.lib<br>
>>>>>>>> C:\s\b\VTKv5-build\bin\Release\vtkVolumeRendering.lib<br>
>>>>>>>> ..\..\lib\Slicer-4.3\Release\FreeSurfer.lib<br>
>>>>>>>> ITKCommon.lib<br>
>>>>>>>> C:\Qt64\4.8.1\lib\QtOpenGL4.lib<br>
>>>>>>>> ...<br>
>>>>>>>><br>
>>>>>>>> For some reason ITKCommon.lib is treated differently from all the<br>
>>>>>>>> other (at first sight) ITK libraries. Any ideas about how I might fix this?<br>
>>>>>>>> If I edit the linker configuration for qSlicerBaseQTCore to point correctly<br>
>>>>>>>> to the ITKCommon library it builds OK, but I'd rather not have to do this<br>
>>>>>>>> 40+ times.<br>
>>>>>>>><br>
>>>>>>>> Thanks again<br>
>>>>>>>> Gib<br>
>>>>>>>> ________________________________<br>
>>>>>>>> From: <a href="mailto:slicer-devel-bounces@bwh.harvard.edu" target="_blank">
slicer-devel-bounces@bwh.harvard.edu</a><br>
>>>>>>>> [<a href="mailto:slicer-devel-bounces@bwh.harvard.edu" target="_blank">slicer-devel-bounces@bwh.harvard.edu</a>] on behalf of Gib Bogle<br>
>>>>>>>> [<a href="mailto:g.bogle@auckland.ac.nz" target="_blank">g.bogle@auckland.ac.nz</a>]<br>
>>>>>>>> Sent: Saturday, 13 September 2014 12:59 p.m.<br>
>>>>>>>><br>
>>>>>>>> To: Steve Pieper<br>
>>>>>>>> Cc: <a href="mailto:slicer-devel@bwh.harvard.edu" target="_blank">slicer-devel@bwh.harvard.edu</a><br>
>>>>>>>> Subject: Re: [slicer-devel] BigTIFF<br>
>>>>>>>><br>
>>>>>>>> Hi Steve,<br>
>>>>>>>><br>
>>>>>>>> All goes well until the point where the qSlicer*.lib get made. The<br>
>>>>>>>> first error, while building qSlicerBaseQTCore.lib, is:<br>
>>>>>>>><br>
>>>>>>>> LINK : fatal error LNK1181: cannot open input file 'ITKCommon.lib'<br>
>>>>>>>><br>
>>>>>>>> I don't know how to interpret this. I am guessing that it wants to<br>
>>>>>>>> link the ITK library that was just built, i.e.:<br>
>>>>>>>> \s\b\ITKv4-build\lib\Release\ITKCommon-4.6.lib<br>
>>>>>>>> This is the first of about 40 such link errors.<br>
>>>>>>>><br>
>>>>>>>> I'm not sure if ITK really needed to be built, since it is already<br>
>>>>>>>> installed (64-bit) on my system, but I didn't see any option for skipping<br>
>>>>>>>> that step (same for VTK). Is an INSTALL step for ITK needed? Should I set<br>
>>>>>>>> ITK_DIR appropriately?<br>
>>>>>>>><br>
>>>>>>>> Thanks<br>
>>>>>>>> Gib<br>
>>>>>>>> ________________________________<br>
>>>>>>>> From: Steve Pieper [<a href="mailto:pieper@isomics.com" target="_blank">pieper@isomics.com</a>]<br>
>>>>>>>> Sent: Saturday, 13 September 2014 9:02 a.m.<br>
>>>>>>>> To: Gib Bogle<br>
>>>>>>>> Cc: <a href="mailto:slicer-devel@bwh.harvard.edu" target="_blank">slicer-devel@bwh.harvard.edu</a><br>
>>>>>>>> Subject: Re: [slicer-devel] BigTIFF<br>
>>>>>>>><br>
>>>>>>>> Hi Gib -<br>
>>>>>>>><br>
>>>>>>>> I'd give a qualified 'yes' answer. Technically what you propose is<br>
>>>>>>>> quite reasonable, and would be workable. But if you haven't built a big<br>
>>>>>>>> package on windows before there are quite a few prerequites (qt, cmake, git,<br>
>>>>>>>> visual studio...) and odd things can go wrong if it isn't all done just<br>
>>>>>>>> right. That said, slicer is actually quite well supported on windows,<br>
>>>>>>>> better, IMHO, than many cross-platform systems. But windows is really the<br>
>>>>>>>> trickiest platform in my experience.<br>
>>>>>>>><br>
>>>>>>>> -Steve<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> On Fri, Sep 12, 2014 at 4:32 PM, Gib Bogle <<a href="mailto:g.bogle@auckland.ac.nz" target="_blank">g.bogle@auckland.ac.nz</a>><br>
>>>>>>>> wrote:<br>
>>>>>>>>><br>
>>>>>>>>> Hi Steve,<br>
>>>>>>>>><br>
>>>>>>>>> Do you think I would be able to build Slicer myself, with<br>
>>>>>>>>> ITK_USE_64BITS_IDS and leaving out BRAINSTools and anything else that<br>
>>>>>>>>> depends on either ITKDeprecated or ITKV3Compatibility? My need at this<br>
>>>>>>>>> point is simply for a 3D viewer that can handle big images.<br>
>>>>>>>>><br>
>>>>>>>>> Thanks<br>
>>>>>>>>> Gib<br>
>>>>>>>>> ________________________________<br>
>>>>>>>>> From: Gib Bogle<br>
>>>>>>>>> Sent: Wednesday, 10 September 2014 10:34 a.m.<br>
>>>>>>>>> To: Jean-Christophe Fillion-Robin; Steve Pieper<br>
>>>>>>>>> Cc: <a href="mailto:slicer-devel@bwh.harvard.edu" target="_blank">slicer-devel@bwh.harvard.edu</a><br>
>>>>>>>>> Subject: RE: [slicer-devel] BigTIFF<br>
>>>>>>>>><br>
>>>>>>>>> Hi Jean-Christophe,<br>
>>>>>>>>><br>
>>>>>>>>> Any idea when 4.5 will enter the world?<br>
>>>>>>>>><br>
>>>>>>>>> Cheers<br>
>>>>>>>>> Gib<br>
>>>>>>>>> ________________________________<br>
>>>>>>>>> From: <a href="mailto:slicer-devel-bounces@bwh.harvard.edu" target="_blank">
slicer-devel-bounces@bwh.harvard.edu</a><br>
>>>>>>>>> [<a href="mailto:slicer-devel-bounces@bwh.harvard.edu" target="_blank">slicer-devel-bounces@bwh.harvard.edu</a>] on behalf of Jean-Christophe<br>
>>>>>>>>> Fillion-Robin [<a href="mailto:jchris.fillionr@kitware.com" target="_blank">jchris.fillionr@kitware.com</a>]<br>
>>>>>>>>> Sent: Wednesday, 10 September 2014 10:31 a.m.<br>
>>>>>>>>> To: Steve Pieper<br>
>>>>>>>>> Cc: <a href="mailto:slicer-devel@bwh.harvard.edu" target="_blank">slicer-devel@bwh.harvard.edu</a><br>
>>>>>>>>> Subject: Re: [slicer-devel] BigTIFF<br>
>>>>>>>>><br>
>>>>>>>>> Hi Folks,<br>
>>>>>>>>><br>
>>>>>>>>> Thanks to Brad Lowekamp, Slicer core (r23663) does NOT depend on<br>
>>>>>>>>> either ITKDeprecated or ITKV3Compatibility.<br>
>>>>>>>>><br>
>>>>>>>>> That said, BRAINSTools and some extensions are still depending on<br>
>>>>>>>>> these module. All details are captured here:<br>
>>>>>>>>><br>
>>>>>>>>> <a href="http://na-mic.org/Mantis/view.php?id=3825#c12486" target="_blank">
http://na-mic.org/Mantis/view.php?id=3825#c12486</a><br>
>>>>>>>>><br>
>>>>>>>>> Note also that this will NOT be addressed for Slicer 4.4 release. The<br>
>>>>>>>>> enabling of ITK_USE_64BITS_IDS that will allow BigTiff to be loaded is<br>
>>>>>>>>> planned for 4.5.<br>
>>>>>>>>><br>
>>>>>>>>> Thanks<br>
>>>>>>>>> Jc<br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>> On Fri, Sep 5, 2014 at 10:26 AM, Steve Pieper <<a href="mailto:pieper@isomics.com" target="_blank">pieper@isomics.com</a>><br>
>>>>>>>>> wrote:<br>
>>>>>>>>>><br>
>>>>>>>>>> Hi Matt -<br>
>>>>>>>>>><br>
>>>>>>>>>> Thanks, that's helpful.<br>
>>>>>>>>>><br>
>>>>>>>>>> I suspect that for slicer, the only real issues will be in vtkITK,<br>
>>>>>>>>>> which includes all the file IO adapters. But I think it will be pretty<br>
>>>>>>>>>> straightforward.<br>
>>>>>>>>>><br>
>>>>>>>>>> But there's no reason to start that until we know that BRAINSTools<br>
>>>>>>>>>> will work - right now at least some of them depend on ITKDeprecated.<br>
>>>>>>>>>><br>
>>>>>>>>>> -Steve<br>
>>>>>>>>>><br>
>>>>>>>>>><br>
>>>>>>>>>> On Fri, Sep 5, 2014 at 10:06 AM, Matt McCormick<br>
>>>>>>>>>> <<a href="mailto:matt.mccormick@kitware.com" target="_blank">matt.mccormick@kitware.com</a>> wrote:<br>
>>>>>>>>>>><br>
>>>>>>>>>>> Here is what the process would look like:<br>
>>>>>>>>>>><br>
>>>>>>>>>>> 0) Start with a clean software quality dashboard.<br>
>>>>>>>>>>> 1) Set ITKV3_COMPATIBILITY to OFF in<br>
>>>>>>>>>>> Superbuild/External_ITKv4.cmake<br>
>>>>>>>>>>> 2) Rebuild and encounter errors and test failures.<br>
>>>>>>>>>>> 3) Fix the errors with the help of the ITK migration guide [1] and<br>
>>>>>>>>>>> the<br>
>>>>>>>>>>> ITK mailing list [2]. They usually fairly strait forward changes<br>
>>>>>>>>>>> (minor modifications to the API, etc).<br>
>>>>>>>>>>> 4) Set ITK_USE_64BITS_IDS to ON.<br>
>>>>>>>>>>> 5) Profit.<br>
>>>>>>>>>>><br>
>>>>>>>>>>> HTH,<br>
>>>>>>>>>>> Matt<br>
>>>>>>>>>>><br>
>>>>>>>>>>> [1] <a href="http://itk.org/migrationv4/" target="_blank">http://itk.org/migrationv4/</a><br>
>>>>>>>>>>><br>
>>>>>>>>>>> [2] <a href="http://www.itk.org/ITK/help/mailing.html" target="_blank">
http://www.itk.org/ITK/help/mailing.html</a><br>
>>>>>>>>>>><br>
>>>>>>>>>>> On Thu, Sep 4, 2014 at 4:52 PM, Steve Pieper <<a href="mailto:pieper@isomics.com" target="_blank">pieper@isomics.com</a>><br>
>>>>>>>>>>> wrote:<br>
>>>>>>>>>>> > Yes, agreed it's a good goal and I believe the expertise exists,<br>
>>>>>>>>>>> > but it's<br>
>>>>>>>>>>> > looking like there's a fair amount of code to retrofit.<br>
>>>>>>>>>>> ><br>
>>>>>>>>>>> > Maybe Hans, Brad, Matt or others could provide some idea just<br>
>>>>>>>>>>> > what is<br>
>>>>>>>>>>> > involved?<br>
>>>>>>>>>>> ><br>
>>>>>>>>>>> > -Steve<br>
>>>>>>>>>>> ><br>
>>>>>>>>>>> ><br>
>>>>>>>>>>> ><br>
>>>>>>>>>>> > On Thu, Sep 4, 2014 at 4:50 PM, Gib Bogle<br>
>>>>>>>>>>> > <<a href="mailto:g.bogle@auckland.ac.nz" target="_blank">g.bogle@auckland.ac.nz</a>> wrote:<br>
>>>>>>>>>>> >><br>
>>>>>>>>>>> >> :( I imagine that people are increasingly working with very<br>
>>>>>>>>>>> >> large<br>
>>>>>>>>>>> >> datasets, so the number of people who would like to have this<br>
>>>>>>>>>>> >> capability<br>
>>>>>>>>>>> >> will grow. I, alas, am not an ITK expert.<br>
>>>>>>>>>>> >> ________________________________<br>
>>>>>>>>>>> >> From: Steve Pieper [<a href="mailto:pieper@isomics.com" target="_blank">pieper@isomics.com</a>]<br>
>>>>>>>>>>> >> Sent: Friday, 5 September 2014 8:42 a.m.<br>
>>>>>>>>>>> >><br>
>>>>>>>>>>> >> To: Gib Bogle<br>
>>>>>>>>>>> >> Cc: Bradley Lowekamp; <a href="mailto:slicer-devel@bwh.harvard.edu" target="_blank">
slicer-devel@bwh.harvard.edu</a><br>
>>>>>>>>>>> >> Subject: Re: [slicer-devel] BigTIFF<br>
>>>>>>>>>>> >><br>
>>>>>>>>>>> >> Alas the build where I enabled 64 bit id's failed to even<br>
>>>>>>>>>>> >> configure<br>
>>>>>>>>>>> >> properly. Lots of key code depends on the ITKDeprecated module,<br>
>>>>>>>>>>> >> like vtkITK<br>
>>>>>>>>>>> >> and various components of BRAINSTools. So I would say some ITK<br>
>>>>>>>>>>> >> experts are<br>
>>>>>>>>>>> >> going to need to dig in before this mode can be enabled.<br>
>>>>>>>>>>> >><br>
>>>>>>>>>>> >> -Steve<br>
>>>>>>>>>>> >><br>
>>>>>>>>>>> >><br>
>>>>>>>>>>> >> On Thu, Sep 4, 2014 at 4:08 PM, Gib Bogle<br>
>>>>>>>>>>> >> <<a href="mailto:g.bogle@auckland.ac.nz" target="_blank">g.bogle@auckland.ac.nz</a>> wrote:<br>
>>>>>>>>>>> >>><br>
>>>>>>>>>>> >>> I await the results with interest...<br>
>>>>>>>>>>> >>> ________________________________<br>
>>>>>>>>>>> >>> From: <a href="mailto:slicer-devel-bounces@bwh.harvard.edu" target="_blank">
slicer-devel-bounces@bwh.harvard.edu</a><br>
>>>>>>>>>>> >>> [<a href="mailto:slicer-devel-bounces@bwh.harvard.edu" target="_blank">slicer-devel-bounces@bwh.harvard.edu</a>] on behalf of Steve<br>
>>>>>>>>>>> >>> Pieper<br>
>>>>>>>>>>> >>> [<a href="mailto:pieper@isomics.com" target="_blank">pieper@isomics.com</a>]<br>
>>>>>>>>>>> >>> Sent: Friday, 5 September 2014 1:32 a.m.<br>
>>>>>>>>>>> >>> To: Bradley Lowekamp<br>
>>>>>>>>>>> >>><br>
>>>>>>>>>>> >>> Cc: <a href="mailto:slicer-devel@bwh.harvard.edu" target="_blank">
slicer-devel@bwh.harvard.edu</a><br>
>>>>>>>>>>> >>> Subject: Re: [slicer-devel] BigTIFF<br>
>>>>>>>>>>> >>><br>
>>>>>>>>>>> >>> Makes sense, thanks for clarifying Brad. Jc recently moved out<br>
>>>>>>>>>>> >>> a lot of<br>
>>>>>>>>>>> >>> legacy CLI code - perhaps those were the main places<br>
>>>>>>>>>>> >>> ITKV3_COMPATIBILITY was<br>
>>>>>>>>>>> >>> required? I kicked off a build to see what will happen.<br>
>>>>>>>>>>> >>><br>
>>>>>>>>>>> >>> -Steve<br>
>>>>>>>>>>> >>><br>
>>>>>>>>>>> >>><br>
>>>>>>>>>>> >>> On Thu, Sep 4, 2014 at 8:36 AM, Bradley Lowekamp<br>
>>>>>>>>>>> >>> <<a href="mailto:blowekamp@mail.nih.gov" target="_blank">blowekamp@mail.nih.gov</a>><br>
>>>>>>>>>>> >>> wrote:<br>
>>>>>>>>>>> >>>><br>
>>>>>>>>>>> >>>> Steve,<br>
>>>>>>>>>>> >>>><br>
>>>>>>>>>>> >>>> Yes, this is certainly an issue with how ITK has been<br>
>>>>>>>>>>> >>>> configured in<br>
>>>>>>>>>>> >>>> Slicer.<br>
>>>>>>>>>>> >>>><br>
>>>>>>>>>>> >>>> To turn on the 64-bit IDs for windows 64, ITKV3_COMPATIBILITY<br>
>>>>>>>>>>> >>>> needs to<br>
>>>>>>>>>>> >>>> be disabled, and then the ITKDeprecated module can no longer<br>
>>>>>>>>>>> >>>> be used. I have<br>
>>>>>>>>>>> >>>> brought these issue up before and offered assistance but no<br>
>>>>>>>>>>> >>>> one wanted to<br>
>>>>>>>>>>> >>>> champion changing these configuration flags.<br>
>>>>>>>>>>> >>>><br>
>>>>>>>>>>> >>>> Brad<br>
>>>>>>>>>>> >>>><br>
>>>>>>>>>>> >>>> On Sep 3, 2014, at 6:30 PM, Steve Pieper <<a href="mailto:pieper@isomics.com" target="_blank">pieper@isomics.com</a>><br>
>>>>>>>>>>> >>>> wrote:<br>
>>>>>>>>>>> >>>><br>
>>>>>>>>>>> >>>> Hi Brad -<br>
>>>>>>>>>>> >>>><br>
>>>>>>>>>>> >>>> Right, this is not tiff specific but is ITK specific. I was<br>
>>>>>>>>>>> >>>> able to<br>
>>>>>>>>>>> >>>> create a 1650^3 volume (of doubles) in VTK, save with slicer's<br>
>>>>>>>>>>> >>>> vtkNRRDWriter<br>
>>>>>>>>>>> >>>> and reload with vtkNRRDReader. Could not read the same file<br>
>>>>>>>>>>> >>>> with ITK's NRRD<br>
>>>>>>>>>>> >>>> reader. This was all on a slicer current trunk build with<br>
>>>>>>>>>>> >>>> default options<br>
>>>>>>>>>>> >>>> on win7 64bit.<br>
>>>>>>>>>>> >>>><br>
>>>>>>>>>>> >>>> So are we out of luck enabling 64bit IDs or is it just<br>
>>>>>>>>>>> >>>> something nobody<br>
>>>>>>>>>>> >>>> has tried?<br>
>>>>>>>>>>> >>>><br>
>>>>>>>>>>> >>>> -Steve<br>
>>>>>>>>>>> >>>><br>
>>>>>>>>>>> >>>><br>
>>>>>>>>>>> >>>> On Wed, Sep 3, 2014 at 11:17 AM, Bradley Lowekamp<br>
>>>>>>>>>>> >>>> <<a href="mailto:blowekamp@mail.nih.gov" target="_blank">blowekamp@mail.nih.gov</a>> wrote:<br>
>>>>>>>>>>> >>>>><br>
>>>>>>>>>>> >>>>> Steve,<br>
>>>>>>>>>>> >>>>><br>
>>>>>>>>>>> >>>>> Can you usr/load any image greater that 2GB into Slicer on<br>
>>>>>>>>>>> >>>>> windows 64?<br>
>>>>>>>>>>> >>>>><br>
>>>>>>>>>>> >>>>> There should be some image source filters in the<br>
>>>>>>>>>>> >>>>> SimpleFilters modules<br>
>>>>>>>>>>> >>>>> to generate images. I don't think this issue is tiff<br>
>>>>>>>>>>> >>>>> specific.<br>
>>>>>>>>>>> >>>>><br>
>>>>>>>>>>> >>>>> Bread<br>
>>>>>>>>>>> >>>>><br>
>>>>>>>>>>> >>>>> On Sep 3, 2014, at 11:03 AM, Steve Pieper<br>
>>>>>>>>>>> >>>>> <<a href="mailto:pieper@isomics.com" target="_blank">pieper@isomics.com</a>> wrote:<br>
>>>>>>>>>>> >>>>><br>
>>>>>>>>>>> >>>>> I was able to replicate the crash - Thanks for the data, Gib!<br>
>>>>>>>>>>> >>>>><br>
>>>>>>>>>>> >>>>> I happens in the itk tiff reader. I created a bug report and<br>
>>>>>>>>>>> >>>>> pasted in<br>
>>>>>>>>>>> >>>>> a stack trace and put a link to the data.<br>
>>>>>>>>>>> >>>>><br>
>>>>>>>>>>> >>>>> <a href="http://na-mic.org/Bug/view.php?id=3825" target="_blank">
http://na-mic.org/Bug/view.php?id=3825</a><br>
>>>>>>>>>>> >>>>><br>
>>>>>>>>>>> >>>>> -Steve<br>
>>>>>>>>>>> >>>>><br>
>>>>>>>>>>> >>>>><br>
>>>>>>>>>>> >>>>> On Tue, Sep 2, 2014 at 5:24 PM, Bradley Lowekamp<br>
>>>>>>>>>>> >>>>> <<a href="mailto:blowekamp@mail.nih.gov" target="_blank">blowekamp@mail.nih.gov</a>> wrote:<br>
>>>>>>>>>>> >>>>>><br>
>>>>>>>>>>> >>>>>> Matt, I was just about to point that out.<br>
>>>>>>>>>>> >>>>>><br>
>>>>>>>>>>> >>>>>> The other things is the compatibility flag:<br>
>>>>>>>>>>> >>>>>><br>
>>>>>>>>>>> >>>>>><br>
>>>>>>>>>>> >>>>>> <a href="https://github.com/Slicer/Slicer/blob/master/SuperBuild/External_ITKv4.cmake#L48" target="_blank">
https://github.com/Slicer/Slicer/blob/master/SuperBuild/External_ITKv4.cmake#L48</a><br>
>>>>>>>>>>> >>>>>><br>
>>>>>>>>>>> >>>>>> I think the prevents the 64-bit IDs being used. That is it's<br>
>>>>>>>>>>> >>>>>> still<br>
>>>>>>>>>>> >>>>>> long not long long, so that it's "compatible" with ITKv3.<br>
>>>>>>>>>>> >>>>>><br>
>>>>>>>>>>> >>>>>><br>
>>>>>>>>>>> >>>>>> <a href="https://github.com/InsightSoftwareConsortium/ITK/blob/master/Modules/Core/Common/include/itkIntTypes.h#L122" target="_blank">
https://github.com/InsightSoftwareConsortium/ITK/blob/master/Modules/Core/Common/include/itkIntTypes.h#L122</a><br>
>>>>>>>>>>> >>>>>><br>
>>>>>>>>>>> >>>>>> Brad<br>
>>>>>>>>>>> >>>>>><br>
>>>>>>>>>>> >>>>>> On Sep 2, 2014, at 5:15 PM, Steve Pieper<br>
>>>>>>>>>>> >>>>>> <<a href="mailto:pieper@isomics.com" target="_blank">pieper@isomics.com</a>> wrote:<br>
>>>>>>>>>>> >>>>>><br>
>>>>>>>>>>> >>>>>> Thanks Matt - that looks logical! Let's see if we can<br>
>>>>>>>>>>> >>>>>> replicate the<br>
>>>>>>>>>>> >>>>>> issue and then we can see if that has any side effects.<br>
>>>>>>>>>>> >>>>>><br>
>>>>>>>>>>> >>>>>><br>
>>>>>>>>>>> >>>>>> On Tue, Sep 2, 2014 at 4:44 PM, Matt McCormick<br>
>>>>>>>>>>> >>>>>> <<a href="mailto:matt.mccormick@kitware.com" target="_blank">matt.mccormick@kitware.com</a>> wrote:<br>
>>>>>>>>>>> >>>>>>><br>
>>>>>>>>>>> >>>>>>> Here is an untested patch that may fix the problem:<br>
>>>>>>>>>>> >>>>>>><br>
>>>>>>>>>>> >>>>>>><br>
>>>>>>>>>>> >>>>>>><br>
>>>>>>>>>>> >>>>>>> <a href="https://github.com/thewtex/Slicer/commit/24d571c970d012015a95ac6063e3b0a3fede96fb" target="_blank">
https://github.com/thewtex/Slicer/commit/24d571c970d012015a95ac6063e3b0a3fede96fb</a><br>
>>>>>>>>>>> >>>>>>><br>
>>>>>>>>>>> >>>>>>> On Tue, Sep 2, 2014 at 4:42 PM, Gib Bogle<br>
>>>>>>>>>>> >>>>>>> <<a href="mailto:g.bogle@auckland.ac.nz" target="_blank">g.bogle@auckland.ac.nz</a>><br>
>>>>>>>>>>> >>>>>>> wrote:<br>
>>>>>>>>>>> >>>>>>> > I have to do something else for a while now. I'll get<br>
>>>>>>>>>>> >>>>>>> > back to this<br>
>>>>>>>>>>> >>>>>>> > later.<br>
>>>>>>>>>>> >>>>>>> > ________________________________<br>
>>>>>>>>>>> >>>>>>> > From: Steve Pieper [<a href="mailto:pieper@isomics.com" target="_blank">pieper@isomics.com</a>]<br>
>>>>>>>>>>> >>>>>>> > Sent: Wednesday, 3 September 2014 8:41 a.m.<br>
>>>>>>>>>>> >>>>>>> ><br>
>>>>>>>>>>> >>>>>>> > To: Gib Bogle<br>
>>>>>>>>>>> >>>>>>> > Cc: Bradley Lowekamp; <a href="mailto:slicer-devel@bwh.harvard.edu" target="_blank">
slicer-devel@bwh.harvard.edu</a><br>
>>>>>>>>>>> >>>>>>> > Subject: Re: [slicer-devel] BigTIFF<br>
>>>>>>>>>>> >>>>>>> ><br>
>>>>>>>>>>> >>>>>>> > Sure, if that works that's fine. Or maybe Brad knows how<br>
>>>>>>>>>>> >>>>>>> > to<br>
>>>>>>>>>>> >>>>>>> > generate a big<br>
>>>>>>>>>>> >>>>>>> > file with SimpleITK. Or a statically linked executable<br>
>>>>>>>>>>> >>>>>>> > for any<br>
>>>>>>>>>>> >>>>>>> > standard<br>
>>>>>>>>>>> >>>>>>> > platform should be fine too.<br>
>>>>>>>>>>> >>>>>>> ><br>
>>>>>>>>>>> >>>>>>> ><br>
>>>>>>>>>>> >>>>>>> > On Tue, Sep 2, 2014 at 4:40 PM, Gib Bogle<br>
>>>>>>>>>>> >>>>>>> > <<a href="mailto:g.bogle@auckland.ac.nz" target="_blank">g.bogle@auckland.ac.nz</a>><br>
>>>>>>>>>>> >>>>>>> > wrote:<br>
>>>>>>>>>>> >>>>>>> >><br>
>>>>>>>>>>> >>>>>>> >> On second thoughts a very simple image will compress to<br>
>>>>>>>>>>> >>>>>>> >> a<br>
>>>>>>>>>>> >>>>>>> >> reasonable size.<br>
>>>>>>>>>>> >>>>>>> >> Slicer seems to handle the compression modes used by ITK<br>
>>>>>>>>>>> >>>>>>> >> without<br>
>>>>>>>>>>> >>>>>>> >> problems.<br>
>>>>>>>>>>> >>>>>>> >> ________________________________<br>
>>>>>>>>>>> >>>>>>> >> From: Steve Pieper [<a href="mailto:pieper@isomics.com" target="_blank">pieper@isomics.com</a>]<br>
>>>>>>>>>>> >>>>>>> >> Sent: Wednesday, 3 September 2014 8:31 a.m.<br>
>>>>>>>>>>> >>>>>>> >> To: Gib Bogle<br>
>>>>>>>>>>> >>>>>>> >> Cc: Bradley Lowekamp; <a href="mailto:slicer-devel@bwh.harvard.edu" target="_blank">
slicer-devel@bwh.harvard.edu</a><br>
>>>>>>>>>>> >>>>>>> >> Subject: Re: [slicer-devel] BigTIFF<br>
>>>>>>>>>>> >>>>>>> >><br>
>>>>>>>>>>> >>>>>>> >> Hi -<br>
>>>>>>>>>>> >>>>>>> >><br>
>>>>>>>>>>> >>>>>>> >> Is there an easy way to generate a big tiff like this,<br>
>>>>>>>>>>> >>>>>>> >> for example<br>
>>>>>>>>>>> >>>>>>> >> with a<br>
>>>>>>>>>>> >>>>>>> >> few lines of SimpleITK code? (Easier than trying to<br>
>>>>>>>>>>> >>>>>>> >> transfer a<br>
>>>>>>>>>>> >>>>>>> >> 4.5GB file<br>
>>>>>>>>>>> >>>>>>> >> from NZ).<br>
>>>>>>>>>>> >>>>>>> >><br>
>>>>>>>>>>> >>>>>>> >> -Steve<br>
>>>>>>>>>>> >>>>>>> >><br>
>>>>>>>>>>> >>>>>>> >><br>
>>>>>>>>>>> >>>>>>> >> On Tue, Sep 2, 2014 at 4:26 PM, Gib Bogle<br>
>>>>>>>>>>> >>>>>>> >> <<a href="mailto:g.bogle@auckland.ac.nz" target="_blank">g.bogle@auckland.ac.nz</a>><br>
>>>>>>>>>>> >>>>>>> >> wrote:<br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >>> Hi Brad,<br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >>> I installed Slicer-4.3.1 64-bit version on Windows 7.<br>
>>>>>>>>>>> >>>>>>> >>> I can load<br>
>>>>>>>>>>> >>>>>>> >>> a tiff<br>
>>>>>>>>>>> >>>>>>> >>> file that is about 1 GB (grey-scale 1000x1000x1000),<br>
>>>>>>>>>>> >>>>>>> >>> but a couple<br>
>>>>>>>>>>> >>>>>>> >>> of bigger<br>
>>>>>>>>>>> >>>>>>> >>> files fail. When I try to open a file that is about<br>
>>>>>>>>>>> >>>>>>> >>> 4.5 GB<br>
>>>>>>>>>>> >>>>>>> >>> (actually when I<br>
>>>>>>>>>>> >>>>>>> >>> try to add data to the scene) the program crashes<br>
>>>>>>>>>>> >>>>>>> >>> immediately,<br>
>>>>>>>>>>> >>>>>>> >>> exception<br>
>>>>>>>>>>> >>>>>>> >>> code c0000005. The result with an image of about half<br>
>>>>>>>>>>> >>>>>>> >>> this size<br>
>>>>>>>>>>> >>>>>>> >>> is the<br>
>>>>>>>>>>> >>>>>>> >>> same. Sometimes the behaviour is slightly different -<br>
>>>>>>>>>>> >>>>>>> >>> I see the<br>
>>>>>>>>>>> >>>>>>> >>> "Loading..." popup, but it's stuck on 15% and the<br>
>>>>>>>>>>> >>>>>>> >>> windows greys<br>
>>>>>>>>>>> >>>>>>> >>> out.<br>
>>>>>>>>>>> >>>>>>> >>> Nothing happens after that, until I click the x button<br>
>>>>>>>>>>> >>>>>>> >>> on the<br>
>>>>>>>>>>> >>>>>>> >>> popup, and the<br>
>>>>>>>>>>> >>>>>>> >>> program crashes.<br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >>> These files were all written with ITK. The reason I<br>
>>>>>>>>>>> >>>>>>> >>> installed<br>
>>>>>>>>>>> >>>>>>> >>> Slicer is<br>
>>>>>>>>>>> >>>>>>> >>> simply to be able to view big files - Irfanview is very<br>
>>>>>>>>>>> >>>>>>> >>> good but<br>
>>>>>>>>>>> >>>>>>> >>> BigTIFFs<br>
>>>>>>>>>>> >>>>>>> >>> are not enabled.<br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >>> Is it a case of having to build Slicer myself, with<br>
>>>>>>>>>>> >>>>>>> >>> different<br>
>>>>>>>>>>> >>>>>>> >>> build<br>
>>>>>>>>>>> >>>>>>> >>> options?<br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >>> Thanks<br>
>>>>>>>>>>> >>>>>>> >>> Gib<br>
>>>>>>>>>>> >>>>>>> >>> ________________________________<br>
>>>>>>>>>>> >>>>>>> >>> From: Bradley Lowekamp [<a href="mailto:blowekamp@mail.nih.gov" target="_blank">blowekamp@mail.nih.gov</a>]<br>
>>>>>>>>>>> >>>>>>> >>> Sent: Wednesday, 3 September 2014 1:00 a.m.<br>
>>>>>>>>>>> >>>>>>> >>> To: Gib Bogle<br>
>>>>>>>>>>> >>>>>>> >>> Cc: <a href="mailto:slicer-devel@bwh.harvard.edu" target="_blank">
slicer-devel@bwh.harvard.edu</a><br>
>>>>>>>>>>> >>>>>>> >>> Subject: Re: [slicer-devel] BigTIFF<br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >>> Hello,<br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >>> I believe Slicer is using ITK's libtiff library 4.0.3,<br>
>>>>>>>>>>> >>>>>>> >>> and the<br>
>>>>>>>>>>> >>>>>>> >>> associated<br>
>>>>>>>>>>> >>>>>>> >>> ITK ImageIO. This should support BigTIFFs. Could you<br>
>>>>>>>>>>> >>>>>>> >>> please<br>
>>>>>>>>>>> >>>>>>> >>> provide more<br>
>>>>>>>>>>> >>>>>>> >>> detail about your issue?<br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >>> Brad<br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >>> On Sep 1, 2014, at 5:14 PM, Gib Bogle<br>
>>>>>>>>>>> >>>>>>> >>> <<a href="mailto:g.bogle@auckland.ac.nz" target="_blank">g.bogle@auckland.ac.nz</a>><br>
>>>>>>>>>>> >>>>>>> >>> wrote:<br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >>> Hi,<br>
>>>>>>>>>>> >>>>>>> >>> It seems that Slicer (the Windows version, anyway) does<br>
>>>>>>>>>>> >>>>>>> >>> not<br>
>>>>>>>>>>> >>>>>>> >>> handle<br>
>>>>>>>>>>> >>>>>>> >>> BigTIFFs. Is there a plan to add this capability?<br>
>>>>>>>>>>> >>>>>>> >>> Thanks<br>
>>>>>>>>>>> >>>>>>> >>> Gib<br>
>>>>>>>>>>> >>>>>>> >>> _______________________________________________<br>
>>>>>>>>>>> >>>>>>> >>> slicer-devel mailing list<br>
>>>>>>>>>>> >>>>>>> >>> <a href="mailto:slicer-devel@bwh.harvard.edu" target="_blank">
slicer-devel@bwh.harvard.edu</a><br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >>> <a href="http://massmail.spl.harvard.edu/mailman/listinfo/slicer-devel" target="_blank">
http://massmail.spl.harvard.edu/mailman/listinfo/slicer-devel</a><br>
>>>>>>>>>>> >>>>>>> >>> To unsubscribe: send email to<br>
>>>>>>>>>>> >>>>>>> >>> <a href="mailto:slicer-devel-request@massmail.spl.harvard.edu" target="_blank">
slicer-devel-request@massmail.spl.harvard.edu</a> with<br>
>>>>>>>>>>> >>>>>>> >>> unsubscribe as<br>
>>>>>>>>>>> >>>>>>> >>> the<br>
>>>>>>>>>>> >>>>>>> >>> subject<br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >>> <a href="http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/FAQ" target="_blank">
http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/FAQ</a><br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >>> The information in this e-mail is intended only for the<br>
>>>>>>>>>>> >>>>>>> >>> person to<br>
>>>>>>>>>>> >>>>>>> >>> whom it<br>
>>>>>>>>>>> >>>>>>> >>> is<br>
>>>>>>>>>>> >>>>>>> >>> addressed. If you believe this e-mail was sent to you<br>
>>>>>>>>>>> >>>>>>> >>> in error<br>
>>>>>>>>>>> >>>>>>> >>> and the<br>
>>>>>>>>>>> >>>>>>> >>> e-mail<br>
>>>>>>>>>>> >>>>>>> >>> contains patient information, please contact the<br>
>>>>>>>>>>> >>>>>>> >>> Partners<br>
>>>>>>>>>>> >>>>>>> >>> Compliance<br>
>>>>>>>>>>> >>>>>>> >>> HelpLine at<br>
>>>>>>>>>>> >>>>>>> >>> <a href="http://www.partners.org/complianceline" target="_blank">
http://www.partners.org/complianceline</a> . If the e-mail<br>
>>>>>>>>>>> >>>>>>> >>> was sent<br>
>>>>>>>>>>> >>>>>>> >>> to you in<br>
>>>>>>>>>>> >>>>>>> >>> error<br>
>>>>>>>>>>> >>>>>>> >>> but does not contain patient information, please<br>
>>>>>>>>>>> >>>>>>> >>> contact the<br>
>>>>>>>>>>> >>>>>>> >>> sender and<br>
>>>>>>>>>>> >>>>>>> >>> properly<br>
>>>>>>>>>>> >>>>>>> >>> dispose of the e-mail.<br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >>> _______________________________________________<br>
>>>>>>>>>>> >>>>>>> >>> slicer-devel mailing list<br>
>>>>>>>>>>> >>>>>>> >>> <a href="mailto:slicer-devel@bwh.harvard.edu" target="_blank">
slicer-devel@bwh.harvard.edu</a><br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >>> <a href="http://massmail.spl.harvard.edu/mailman/listinfo/slicer-devel" target="_blank">
http://massmail.spl.harvard.edu/mailman/listinfo/slicer-devel</a><br>
>>>>>>>>>>> >>>>>>> >>> To unsubscribe: send email to<br>
>>>>>>>>>>> >>>>>>> >>> <a href="mailto:slicer-devel-request@massmail.spl.harvard.edu" target="_blank">
slicer-devel-request@massmail.spl.harvard.edu</a> with<br>
>>>>>>>>>>> >>>>>>> >>> unsubscribe as<br>
>>>>>>>>>>> >>>>>>> >>> the<br>
>>>>>>>>>>> >>>>>>> >>> subject<br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >>> <a href="http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/FAQ" target="_blank">
http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/FAQ</a><br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >>> The information in this e-mail is intended only for the<br>
>>>>>>>>>>> >>>>>>> >>> person to<br>
>>>>>>>>>>> >>>>>>> >>> whom it<br>
>>>>>>>>>>> >>>>>>> >>> is<br>
>>>>>>>>>>> >>>>>>> >>> addressed. If you believe this e-mail was sent to you<br>
>>>>>>>>>>> >>>>>>> >>> in error<br>
>>>>>>>>>>> >>>>>>> >>> and the<br>
>>>>>>>>>>> >>>>>>> >>> e-mail<br>
>>>>>>>>>>> >>>>>>> >>> contains patient information, please contact the<br>
>>>>>>>>>>> >>>>>>> >>> Partners<br>
>>>>>>>>>>> >>>>>>> >>> Compliance<br>
>>>>>>>>>>> >>>>>>> >>> HelpLine at<br>
>>>>>>>>>>> >>>>>>> >>> <a href="http://www.partners.org/complianceline" target="_blank">
http://www.partners.org/complianceline</a> . If the e-mail<br>
>>>>>>>>>>> >>>>>>> >>> was sent<br>
>>>>>>>>>>> >>>>>>> >>> to you in<br>
>>>>>>>>>>> >>>>>>> >>> error<br>
>>>>>>>>>>> >>>>>>> >>> but does not contain patient information, please<br>
>>>>>>>>>>> >>>>>>> >>> contact the<br>
>>>>>>>>>>> >>>>>>> >>> sender and<br>
>>>>>>>>>>> >>>>>>> >>> properly<br>
>>>>>>>>>>> >>>>>>> >>> dispose of the e-mail.<br>
>>>>>>>>>>> >>>>>>> >>><br>
>>>>>>>>>>> >>>>>>> >><br>
>>>>>>>>>>> >>>>>>> ><br>
>>>>>>>>>>> >>>>>>> ><br>
>>>>>>>>>>> >>>>>>> > _______________________________________________<br>
>>>>>>>>>>> >>>>>>> > slicer-devel mailing list<br>
>>>>>>>>>>> >>>>>>> > <a href="mailto:slicer-devel@bwh.harvard.edu" target="_blank">
slicer-devel@bwh.harvard.edu</a><br>
>>>>>>>>>>> >>>>>>> ><br>
>>>>>>>>>>> >>>>>>> > <a href="http://massmail.spl.harvard.edu/mailman/listinfo/slicer-devel" target="_blank">
http://massmail.spl.harvard.edu/mailman/listinfo/slicer-devel</a><br>
>>>>>>>>>>> >>>>>>> > To unsubscribe: send email to<br>
>>>>>>>>>>> >>>>>>> > <a href="mailto:slicer-devel-request@massmail.spl.harvard.edu" target="_blank">
slicer-devel-request@massmail.spl.harvard.edu</a><br>
>>>>>>>>>>> >>>>>>> > with unsubscribe as the subject<br>
>>>>>>>>>>> >>>>>>> ><br>
>>>>>>>>>>> >>>>>>> ><br>
>>>>>>>>>>> >>>>>>> > <a href="http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/FAQ" target="_blank">
http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/FAQ</a><br>
>>>>>>>>>>> >>>>>>> ><br>
>>>>>>>>>>> >>>>>>> ><br>
>>>>>>>>>>> >>>>>>> > The information in this e-mail is intended only for the<br>
>>>>>>>>>>> >>>>>>> > person to<br>
>>>>>>>>>>> >>>>>>> > whom it is<br>
>>>>>>>>>>> >>>>>>> > addressed. If you believe this e-mail was sent to you in<br>
>>>>>>>>>>> >>>>>>> > error and<br>
>>>>>>>>>>> >>>>>>> > the<br>
>>>>>>>>>>> >>>>>>> > e-mail<br>
>>>>>>>>>>> >>>>>>> > contains patient information, please contact the Partners<br>
>>>>>>>>>>> >>>>>>> > Compliance<br>
>>>>>>>>>>> >>>>>>> > HelpLine at<br>
>>>>>>>>>>> >>>>>>> > <a href="http://www.partners.org/complianceline" target="_blank">
http://www.partners.org/complianceline</a> . If the e-mail<br>
>>>>>>>>>>> >>>>>>> > was sent to<br>
>>>>>>>>>>> >>>>>>> > you in<br>
>>>>>>>>>>> >>>>>>> > error<br>
>>>>>>>>>>> >>>>>>> > but does not contain patient information, please contact<br>
>>>>>>>>>>> >>>>>>> > the sender<br>
>>>>>>>>>>> >>>>>>> > and<br>
>>>>>>>>>>> >>>>>>> > properly<br>
>>>>>>>>>>> >>>>>>> > dispose of the e-mail.<br>
>>>>>>>>>>> >>>>>>> ><br>
>>>>>>>>>>> >>>>>><br>
>>>>>>>>>>> >>>>>><br>
>>>>>>>>>>> >>>>>> _______________________________________________<br>
>>>>>>>>>>> >>>>>> slicer-devel mailing list<br>
>>>>>>>>>>> >>>>>> <a href="mailto:slicer-devel@bwh.harvard.edu" target="_blank">
slicer-devel@bwh.harvard.edu</a><br>
>>>>>>>>>>> >>>>>><br>
>>>>>>>>>>> >>>>>> <a href="http://massmail.spl.harvard.edu/mailman/listinfo/slicer-devel" target="_blank">
http://massmail.spl.harvard.edu/mailman/listinfo/slicer-devel</a><br>
>>>>>>>>>>> >>>>>> To unsubscribe: send email to<br>
>>>>>>>>>>> >>>>>> <a href="mailto:slicer-devel-request@massmail.spl.harvard.edu" target="_blank">
slicer-devel-request@massmail.spl.harvard.edu</a> with<br>
>>>>>>>>>>> >>>>>> unsubscribe as the<br>
>>>>>>>>>>> >>>>>> subject<br>
>>>>>>>>>>> >>>>>><br>
>>>>>>>>>>> >>>>>><br>
>>>>>>>>>>> >>>>>> <a href="http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/FAQ" target="_blank">
http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/FAQ</a><br>
>>>>>>>>>>> >>>>>><br>
>>>>>>>>>>> >>>>>><br>
>>>>>>>>>>> >>>>>> The information in this e-mail is intended only for the<br>
>>>>>>>>>>> >>>>>> person to whom<br>
>>>>>>>>>>> >>>>>> it is<br>
>>>>>>>>>>> >>>>>> addressed. If you believe this e-mail was sent to you in<br>
>>>>>>>>>>> >>>>>> error and the<br>
>>>>>>>>>>> >>>>>> e-mail<br>
>>>>>>>>>>> >>>>>> contains patient information, please contact the Partners<br>
>>>>>>>>>>> >>>>>> Compliance<br>
>>>>>>>>>>> >>>>>> HelpLine at<br>
>>>>>>>>>>> >>>>>> <a href="http://www.partners.org/complianceline" target="_blank">
http://www.partners.org/complianceline</a> . If the e-mail was<br>
>>>>>>>>>>> >>>>>> sent to you<br>
>>>>>>>>>>> >>>>>> in error<br>
>>>>>>>>>>> >>>>>> but does not contain patient information, please contact the<br>
>>>>>>>>>>> >>>>>> sender<br>
>>>>>>>>>>> >>>>>> and properly<br>
>>>>>>>>>>> >>>>>> dispose of the e-mail.<br>
>>>>>>>>>>> >>>>>><br>
>>>>>>>>>>> >>>>>><br>
>>>>>>>>>>> >>>>><br>
>>>>>>>>>>> >>>>><br>
>>>>>>>>>>> >>>><br>
>>>>>>>>>>> >>>><br>
>>>>>>>>>>> >>><br>
>>>>>>>>>>> >><br>
>>>>>>>>>>> ><br>
>>>>>>>>>>> ><br>
>>>>>>>>>>> > _______________________________________________<br>
>>>>>>>>>>> > slicer-devel mailing list<br>
>>>>>>>>>>> > <a href="mailto:slicer-devel@bwh.harvard.edu" target="_blank">slicer-devel@bwh.harvard.edu</a><br>
>>>>>>>>>>> > <a href="http://massmail.spl.harvard.edu/mailman/listinfo/slicer-devel" target="_blank">
http://massmail.spl.harvard.edu/mailman/listinfo/slicer-devel</a><br>
>>>>>>>>>>> > To unsubscribe: send email to<br>
>>>>>>>>>>> > <a href="mailto:slicer-devel-request@massmail.spl.harvard.edu" target="_blank">
slicer-devel-request@massmail.spl.harvard.edu</a><br>
>>>>>>>>>>> > with unsubscribe as the subject<br>
>>>>>>>>>>> ><br>
>>>>>>>>>>> > <a href="http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/FAQ" target="_blank">
http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/FAQ</a><br>
>>>>>>>>>>> ><br>
>>>>>>>>>>> ><br>
>>>>>>>>>>> > The information in this e-mail is intended only for the person to<br>
>>>>>>>>>>> > whom it is<br>
>>>>>>>>>>> > addressed. If you believe this e-mail was sent to you in error<br>
>>>>>>>>>>> > and the<br>
>>>>>>>>>>> > e-mail<br>
>>>>>>>>>>> > contains patient information, please contact the Partners<br>
>>>>>>>>>>> > Compliance<br>
>>>>>>>>>>> > HelpLine at<br>
>>>>>>>>>>> > <a href="http://www.partners.org/complianceline" target="_blank">http://www.partners.org/complianceline</a> . If the e-mail was sent<br>
>>>>>>>>>>> > to you in<br>
>>>>>>>>>>> > error<br>
>>>>>>>>>>> > but does not contain patient information, please contact the<br>
>>>>>>>>>>> > sender and<br>
>>>>>>>>>>> > properly<br>
>>>>>>>>>>> > dispose of the e-mail.<br>
>>>>>>>>>>> ><br>
>>>>>>>>>><br>
>>>>>>>>>><br>
>>>>>>>>>><br>
>>>>>>>>>> _______________________________________________<br>
>>>>>>>>>> slicer-devel mailing list<br>
>>>>>>>>>> <a href="mailto:slicer-devel@bwh.harvard.edu" target="_blank">slicer-devel@bwh.harvard.edu</a><br>
>>>>>>>>>> <a href="http://massmail.spl.harvard.edu/mailman/listinfo/slicer-devel" target="_blank">
http://massmail.spl.harvard.edu/mailman/listinfo/slicer-devel</a><br>
>>>>>>>>>> To unsubscribe: send email to<br>
>>>>>>>>>> <a href="mailto:slicer-devel-request@massmail.spl.harvard.edu" target="_blank">
slicer-devel-request@massmail.spl.harvard.edu</a> with unsubscribe as the<br>
>>>>>>>>>> subject<br>
>>>>>>>>>><br>
>>>>>>>>>> <a href="http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/FAQ" target="_blank">
http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/FAQ</a><br>
>>>>>>>>>><br>
>>>>>>>>>><br>
>>>>>>>>>> The information in this e-mail is intended only for the person to<br>
>>>>>>>>>> whom it is<br>
>>>>>>>>>> addressed. If you believe this e-mail was sent to you in error and<br>
>>>>>>>>>> the e-mail<br>
>>>>>>>>>> contains patient information, please contact the Partners Compliance<br>
>>>>>>>>>> HelpLine at<br>
>>>>>>>>>> <a href="http://www.partners.org/complianceline" target="_blank">http://www.partners.org/complianceline</a> . If the e-mail was sent to<br>
>>>>>>>>>> you in error<br>
>>>>>>>>>> but does not contain patient information, please contact the sender<br>
>>>>>>>>>> and properly<br>
>>>>>>>>>> dispose of the e-mail.<br>
>>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>> --<br>
>>>>>>>>> +1 919 869 8849<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>><br>
>>>>>><br>
>>>>><br>
>>>>><br>
>>>>> _______________________________________________<br>
>>>>> slicer-devel mailing list<br>
>>>>> <a href="mailto:slicer-devel@bwh.harvard.edu" target="_blank">slicer-devel@bwh.harvard.edu</a><br>
>>>>> <a href="http://massmail.spl.harvard.edu/mailman/listinfo/slicer-devel" target="_blank">
http://massmail.spl.harvard.edu/mailman/listinfo/slicer-devel</a><br>
>>>>> To unsubscribe: send email to<br>
>>>>> <a href="mailto:slicer-devel-request@massmail.spl.harvard.edu" target="_blank">
slicer-devel-request@massmail.spl.harvard.edu</a> with unsubscribe as the<br>
>>>>> subject<br>
>>>>><br>
>>>>> <a href="http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/FAQ" target="_blank">
http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/FAQ</a><br>
>>>>><br>
>>>>><br>
>>>>> The information in this e-mail is intended only for the person to whom it<br>
>>>>> is<br>
>>>>> addressed. If you believe this e-mail was sent to you in error and the<br>
>>>>> e-mail<br>
>>>>> contains patient information, please contact the Partners Compliance<br>
>>>>> HelpLine at<br>
>>>>> <a href="http://www.partners.org/complianceline" target="_blank">http://www.partners.org/complianceline</a> . If the e-mail was sent to you in<br>
>>>>> error<br>
>>>>> but does not contain patient information, please contact the sender and<br>
>>>>> properly<br>
>>>>> dispose of the e-mail.<br>
>>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>> --<br>
>>>> +1 919 869 8849<br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> slicer-devel mailing list<br>
>>> <a href="mailto:slicer-devel@bwh.harvard.edu" target="_blank">slicer-devel@bwh.harvard.edu</a><br>
>>> <a href="http://massmail.spl.harvard.edu/mailman/listinfo/slicer-devel" target="_blank">
http://massmail.spl.harvard.edu/mailman/listinfo/slicer-devel</a><br>
>>> To unsubscribe: send email to <a href="mailto:slicer-devel-request@massmail.spl.harvard.edu" target="_blank">
slicer-devel-request@massmail.spl.harvard.edu</a><br>
>>> with unsubscribe as the subject<br>
>>> <a href="http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/FAQ" target="_blank">
http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/FAQ</a><br>
>>><br>
>>><br>
>>> The information in this e-mail is intended only for the person to whom it is<br>
>>> addressed. If you believe this e-mail was sent to you in error and the<br>
>>> e-mail<br>
>>> contains patient information, please contact the Partners Compliance<br>
>>> HelpLine at<br>
>>> <a href="http://www.partners.org/complianceline" target="_blank">http://www.partners.org/complianceline</a> . If the e-mail was sent to you in<br>
>>> error<br>
>>> but does not contain patient information, please contact the sender and<br>
>>> properly<br>
>>> dispose of the e-mail.<br>
>>><br>
>>><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</body>
</html>