exptime set to zero while TimeTotExtent is correct

Bug #328549 reported by Alberto
2
Affects Status Importance Assigned to Milestone
VirGO
Fix Released
Medium
Unassigned

Bug Description

I tried with both UVES and SOFI *RAW* data, e.g.:

UVES.2002-03-12T04:45:20.314
ONTT.2003-07-09T23:51:09.229 (SOFI)

and in both cases the Exptime is 0, while the TimeTotExtent reports the correct value.

Changed in virgo:
importance: Undecided → Medium
milestone: none → 1.4.3
status: New → Fix Committed
Changed in virgo:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.