iv3d-users

Text archives Help


[IV3D-USERS] Re: RE: Re: RE: Re: IV3D Question


Chronological Thread 
  • From: tom fogal <tfogal@sci.utah.edu>
  • To: iv3d-users@sci.utah.edu
  • Subject: [IV3D-USERS] Re: RE: Re: RE: Re: IV3D Question
  • Date: Wed, 04 Sep 2013 01:44:24 +0200

Hi Lee,

Thanks for digging into this, and sorry you're hitting issues. I dug into the code && that error message is coming out of libtiff. The difference in behavior that you see is telling, suggesting that a libtiff upgrade or change in the way we compile it is to blame.

Could you send us two TIFFs from this data set, so that we could reproduce the issue locally? That would help us a lot. Section 8.3 of our "Getting Data Into ImageVis3D" [1] has information on how to send data to us.

Thanks again,

-tom

[1] http://ci.sci.utah.edu:8011/devbuilds/GettingDataIntoImageVis3D.pdf

On 08/30/2013 10:55 PM, Anderson, Lee wrote:
I just have tried 3.0.0 and 3.1 on this system and get the error. One of our 
scientists said she had a working version on another system. I logged into 
her system and verified it would open the same files causing this error 
without any issues. Then I installed the version she had (v1.3 x64) on this 
system and the error does not occur.

-Lee



-----Original Message-----
From: James Hughes [mailto:jhughes@sci.utah.edu]
Sent: Friday, August 30, 2013 4:42 PM
To: iv3d-users@sci.utah.edu
Subject: [IV3D-USERS] Re: RE: Re: IV3D Question

Just uploaded the new executable to ornl link you gave me. Hopefully that 
works.

James
On 08/30, Anderson, Lee wrote:
Still having issues with that link. Probably our firewalls here at the lab. 
By the way, I just opened the exact same folder of .tiff files on a system 
running version 1.3 64-bit and do not get that error. So I ruled out the 
.tiff files themselves as a cause.

-Lee


-----Original Message-----
From: James Hughes [mailto:jhughes@sci.utah.edu]
Sent: Friday, August 30, 2013 4:30 PM
To: iv3d-users@sci.utah.edu
Subject: [IV3D-USERS] Re: IV3D Question

Hey Lee,

Try out this download link for a CI dev-build executable:
http://ci.sci.utah.edu:8011/devbuilds/ImageVis3D-x86_64-3.1.0-r2165-2636-294-2208-release.exe.
We're going to be releasing 3.1 soon and this is the executable we will 
likely base it off of. It includes many bug fixes and likely fixes the error 
you are getting as I'm currently running ImageVis3D on a GTX 680 on Windows.

Note that this link doesn't use the normal HTTP port 80. Let us know if you 
have any trouble downloading it.

James

On 08/30, Anderson, Lee wrote:
Good afternoon.

I have installed IV3D on three systems for some of our scientists. They all 
have different video cards, the one I really need to work has an nVidia 
GTX660 with latest drivers. Hopefully you have seen this error before and 
there is a quick fix.


[cid:image001.jpg@01CEA59B.B4BB97F0]

Thank you for your time.

-Lee Anderson
Information Technology Services Division Oak Ridge National
Laboratory
1 Bethel Valley Road
Bldg. 7964K Room 17 MS6430
Oak Ridge, TN 37831
Office - 865-241-6099
Mobile - 865-617-1416
FAX - 865-241-6770
andersonjl@ornl.gov<mailto:andersonjl@ornl.gov>








Archive powered by MHonArc 2.6.16.

Top of page