IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Opened 18 years ago

Last modified 18 years ago

#1129 assigned defect

output headers for pswarp (cmf and image) are poorly constructed

Reported by: eugene Owned by: Paul Price
Priority: high Milestone:
Component: pswarp Version: unspecified
Severity: normal Keywords:
Cc:

Description

Created an attachment (id=120)
example output pswarp fits image header

There are a variety of problems with the output cmf and image headers from pswarp, at least for the simulation suite. Attached are an example image header and example cmf header from a simtest warp run.

The output headers for the cmf files from pswarp are missing various metadata present in the output headers of the image file. A few problems with the output cmf header:

  • missing NAXIS1,NAXIS2 (these are not present even before the call to psFitsWriteBlank).
  • missing astrometry WCS keywords (present in image output header)
  • output TRIMSEC is nan:nan,nan:nan

In addition, both cmf and image headers suffer from the following problems:

  • basic header keywords are kept in the HIERARCH format, and are thus not compatible with the source camera format.
  • output BIASSEC is not set

Attachments (3)

sample.fits.hdr (7.0 KB ) - added by eugene 18 years ago.
example output pswarp fits image header
sample.cmf.hdr (5.8 KB ) - added by eugene 18 years ago.
output pswarp sample cmf header
input.fits.hdr (3.5 KB ) - added by eugene 18 years ago.
input image header

Download all attachments as: .zip

Change History (4)

by eugene, 18 years ago

Attachment: sample.fits.hdr added

example output pswarp fits image header

by eugene, 18 years ago

Attachment: sample.cmf.hdr added

output pswarp sample cmf header

by eugene, 18 years ago

Attachment: input.fits.hdr added

input image header

comment:1 by Paul Price, 18 years ago

Status: newassigned

The first three may be the result of recent changes to how files are written. I will investigate.

The last two (HIERARCH and BIASSEC) have always been the case:

  • The "_SIMTEST-SKYCELL" camera (derived from SIMTEST) uses a format that puts every concept into the header, with a keyword named after itself. Since DVO cannot read HIERARCH, a subset of concepts (listed in SKYCELLS in the system configuration) have their names changed.
  • The images have no bias section, hence it is not set.
Note: See TracTickets for help on using tickets.