NOTICE! This is a static HTML version of a legacy Fiji BugZilla bug.

The Fiji project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Bug 746 - .dm3 files not imported correctly using text file
.dm3 files not imported correctly using text file
Status: NEW
Product: Fiji
Classification: Unclassified
Component: TrakEM2
unspecified
PC Windows
: P5 normal
Assigned To: Albert Cardona
Depends on:
Blocks:
 
Reported: 2014-05-08 13:30 CDT by ngdias
Modified: 2014-05-09 06:42 CDT
1 user (show)

See Also:

Description ngdias 2014-05-08 13:30:17 CDT
I have a test dataset 5x7 of .dm3 files making a 2D mosaic. These were taken with a Jeol TEM. If I drag the entire dataset into TrakEM2 I get all images in without any problems. However, if I use a text file for the import, I only get 2 in, and those 2 are black and white. If I convert the dm3. files to .tif and import these instead with a text file, all is well.

I think this is *somewhat* related to http://fiji.sc/bugzilla/﷒0﷓

I also have other datasets of .dm3 files acquired with a 3View and those import correctly, either way.

I make all text import files the same way, using a script.

I'm sending 4 sample files:
https://dl.dropboxusercontent.com/u/5200940/Jeol_17.zip

The .txt used to import the files that are not working

Jeol_16.dm3, imports in B/W (using a text file) and gives this log error when clicking on it:
Cannot regenerate mipmaps for patch Jeol_16.dm3 z=1.0 #12

Jeol_17.dm3, doesn't import at all using a text file;

Gatan_10.dm3, part of a dataset that can be imported either way successfully.

*somewhat* related to http://fiji.sc/bugzilla/﷒1