Actions

Bug #1335

open

No date present in output image header

Status:
In Progress
Priority:
Immediate
Start date:
11/22/2019
Due date:
11/22/2019 (over 2 years late)
% Done:

100%

Estimated time:
2.00 h
Spent time:

Description

In some cases Swarp does not include any date information (MJD-OBS or DATE-OBS) in the header of the output image, even though it is present in each of the individual input image.

Actions #1

Updated by Herve Bouyabout 2 years ago

A sample of 3 DECam images, associated weight files and external headers (from scamp) and default.swarp are available on morpho in:

/raid/hbouy/debug_swarp/1335


Actions #2

Updated by Emmanuel Bertinabout 2 years ago

• % Done changed from 0 to 10
• Estimated time set to 2.00 h

Actually SWarp does not output such keyword by default. But it can certainly be done. Merging images from different epochs will lead to an output DATE-OBS (or MJD-OBS) taken from the earliest exposure.
Note that the epoch of the middle of the new "virtual" exposure won't be MJD-OBS + EXPTIME / 2.0, so it will be of limited use for general usage. But I get your point and I will implement this.

Actions #3

Updated by Emmanuel Bertinabout 2 years ago

• Status changed from New to In Progress
Actions #4

Updated by Herve Bouyabout 2 years ago

Emmanuel Bertin wrote:

Actually SWarp does not output such keyword by default. But it can certainly be done. Merging images from different epochs will lead to an output DATE-OBS (or MJD-OBS) taken from the earliest exposure.

But in the case of these images, no MJD-OBS is present in the coadd even though the individual input images each had an MJD-OBS in their header.

Note that the epoch of the middle of the new "virtual" exposure won't be MJD-OBS + EXPTIME / 2.0, so it will be of limited use for general usage. But I get your point and I will implement this.

Actions #5

Updated by Emmanuel Bertinabout 2 years ago

• % Done changed from 10 to 100
Actions

Also available in: Atom PDF