Request for addstar-compatible .cmf files as output of ppSub+psphot

[Michael Wood-Vasey]

The Transient Classification Server has been planning on using DVO to associate stationary transient events. In order to do this, we need for the .cmf files from ppSub+psphot to result in files that can be loaded into a DVO database using addstar. Currently, at least in the July 7 data release, .cmf files produced in the diff stage have an EXTTYPE=IMAGE and so are passed over by addstar. In addition the EXTNAME and EXTHEAD aren't set right.

But perhaps more substantially, there is no astrometric information in the header of the diff.cmf files. The RA and Dec are recorded individually for the detections, but there's no general WCS given.

What is the currently expected behavior and future planned behavior for ppSub+psphot?

Lack of diff.cmf files that can be loaded into addstar is currently limiting the Transient Classification Server analysis of the MD images from June.

[Michael Wood-Vasey]

Hmmm... after further exploration, as far as I can tell 'addstar' expects the astrometric information to be in the primary header. The diff+psphot output only has it in the header of the binary table, which does seem like where it should be. I must be misunderstanding something.

[Michael Wood-Vasey]

Oh, I see. The EXTHEAD keyword specifies which extension contains the header information for an extension. I set this up right and addstar works now on diff.cmf files. So in summary I had to

sethead filename.cmf,1 EXTTYPE='PS1_V2' EXTHEAD='SkyChip.psf' EXTNAME='SkyChip.psf'