problem in opening series with LOCI plug-in

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

problem in opening series with LOCI plug-in

Berra Erkosar
Dear imagej users,
I am using Leica confocals and working with series containing around 50
slices and 3 channels. I have been using the LOCI plug-in in order to open
my files in stacks but now I have two .lei files which cause
"NullPointerException" and I cannot open the files. I tried other plugins
(which I was disliked) I was using in the past such  as Leica TIFF sequence
but or SP Splitter but they either do not recognize different channels or
give the same error saying the format is unrecognized.

I updated my imagej, I re-downloaded the LOCI but it still stays the same. I
can still open other lei files so I guess my problem is on these two
files...
Does anybody have any idea what can be the source of the problem? And rr can
I fix it?

Thank you

Berra
Reply | Threaded
Open this post in threaded view
|

Re: problem in opening series with LOCI plug-in

ctrueden
Hi Berra,

Best would be to send the files to the Bio-Formats team for us to debug.
I'll send you contact information off-list. Are you using the latest trunk
build of loci_tools.jar?

-Curtis

On Wed, Sep 23, 2009 at 7:49 AM, Berra Erkosar <[hidden email]> wrote:

> Dear imagej users,
> I am using Leica confocals and working with series containing around 50
> slices and 3 channels. I have been using the LOCI plug-in in order to open
> my files in stacks but now I have two .lei files which cause
> "NullPointerException" and I cannot open the files. I tried other plugins
> (which I was disliked) I was using in the past such  as Leica TIFF sequence
> but or SP Splitter but they either do not recognize different channels or
> give the same error saying the format is unrecognized.
>
> I updated my imagej, I re-downloaded the LOCI but it still stays the same.
> I
> can still open other lei files so I guess my problem is on these two
> files...
> Does anybody have any idea what can be the source of the problem? And rr
> can
> I fix it?
>
> Thank you
>
> Berra
>