Opened 17 years ago
Closed 17 years ago
#1201 closed defect (fixed)
inconsistent 'tzero' field in Images.dat dvo file
| Reported by: | beaumont | Owned by: | Paul Price |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | concepts | Version: | current |
| Severity: | normal | Keywords: | |
| Cc: |
Description
For a catdir of megacam exposures, the Images.dat file has tzero values for the PHU and CCD images which are inconsistent with one another. For a given exposure (exp time ~2s), the PHU entry has a tzero value 32 units(seconds?) higher than the CCD entries.
Change History (3)
comment:1 by , 17 years ago
| Component: | DVO → Ohana |
|---|
comment:2 by , 17 years ago
| Component: | Ohana → ppImage |
|---|---|
| Owner: | changed from to |
| Priority: | normal → high |
| Status: | new → assigned |
comment:3 by , 17 years ago
| Component: | ppImage → concepts |
|---|---|
| Resolution: | → fixed |
| Status: | assigned → closed |
This was due to an asymmetry in the parse and format time functions in pmConceptStandard.c when the time is specified by MJD (or JD).
Because of the possibility of leap seconds, we assume that MJD (and JD) are in TAI; this wasn't reflected in the parse time function. Reworked the concepts write functions to print warnings if the time systems differ.
Fixed in r23432 on trunk.
Note:
See TracTickets
for help on using tickets.
this is an error in the creation of the smf files: the PHU and EXT have different values of MJD-OBS.