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 580 - timestamp from nd2 file not read correctly
timestamp from nd2 file not read correctly
Status: RESOLVED MOVED
Product: Fiji
Classification: Unclassified
Component: Bio-Formats
unspecified
PC Windows
: P5 normal
Assigned To: Melissa Linkert
Depends on:
Blocks:
 
Reported: 2013-03-27 08:23 CDT by Karin.Mitosch
Modified: 2013-07-03 18:47 CDT
1 user (show)

See Also:


Attachments
metadata of an nd2 file (tab separated values) (85.59 KB, application/vnd.ms-excel)
2013-03-27 08:23 CDT, Karin.Mitosch

Description Karin.Mitosch 2013-03-27 08:23:13 CDT
Created attachment 95
metadata of an nd2 file (tab separated values)

The timestamp from .nd2 files (Nikon specific files) appearing in the metadata are read wrongly into Fiji. The seconds, minutes and hours are combined such that 2 hours, 10 minutes and 3 seconds (reported from Nikon software) would appear as the number: 1213 (120 minutes + 10 minutes + 3 seconds, see timestamp#14 in attached metadata file).

Using ImageJ 1.47n5
Comment 1 Melissa Linkert 2013-03-27 15:51:52 CDT
That is the expected behavior.  The timestamps are stored in seconds within the file, and many people rely upon the timestamps being in seconds for various macros to work.
Comment 2 Karin.Mitosch 2013-03-27 17:02:35 CDT
(In reply to comment #1)
> That is the expected behavior.  The timestamps are stored in seconds within
> the file, and many people rely upon the timestamps being in seconds for
> various macros to work.

The timestamps are clearly not in seconds. For the example I have given (2 hours, 10 minutes and 3 seconds), I would expect 2*3600 + 10*60 + 3 = 7803 seconds. Instead the timestamp given by Fiji is 1213. The timestamp is a weird combination of hours, minutes and seconds. Another example: 10 minutes and 5 seconds are for example shown as timestamp 15 in Fiji.
Comment 3 Melissa Linkert 2013-07-03 18:47:26 CDT
Moved to http://trac.openmicroscopy.org.uk/ome/ticket/11224 as this is not a Fiji bug.