>
> |
%META:TOPICINFO{author="BobGarwood" date="1194313660" format="1.0" version="1.1"}%
%META:TOPICPARENT{name="Software.ReleaseNotes_7_7"}%
Release Notes for sdfits Version 1.10 - Released on Wednesday, 14 November 2007
(See all sdfits release notes at Software Report Central.)
- The output SDFITS file now has a SUBREF_STATE column. This is an integer column. It's value indicates the state of the subreflector. This value is only set when the SUBMOTIN keyword in the GO FITS file is equal to "SubNod". That is the motion that is used when the secondary is nodding between 2 positions during a scan. In that case, the value of SUBREF_STATE is equal to 1 when the subreflector is at the first position throughout the integration in question. It is equal to 0 when the subreflector is moving at any sample of subreflector position during that integration. It is equal to -1 when the subreflector is at the second position. For all other types of subreflector motion, including a stationary subreflector, the value of SUBREF_STATE is 1. The SUBMOTIN keyword and "SubNod" motion were added in M&C release 7.6. For all data take prior to that release, SUBREF_STATE has a value of 1. This column is present for all backends filled by sdfits (Spectrometer, Spectral Processor, Zpectrometer, and DCR).
- The accompanying index file (automatically produced by the online sdfits daemon for Spectrometer, Spectral Processor, and Zpectrometer scans) contains a new SUBREF column. This is a copy of the SUBREF_STATE value associated with that index entry. This is the column that is actually used in GBTIDL selection. This required a changed in the index file version number.
- The Zpectrometer output of sdfits incorrectly assumed that there was a single integration in each raw Zpectrometer FITS file. This bug has been fixed.
There is no change here from the previous release.
- The polarization and feed information are not always correct for Ka receiver data. The data as filled is correct for the SIG=1 data. For the SIG=0 (reference) data the polarization and feed switch to the other polarization and feed. This will be fixed in the next release of
sdfits.
- Duplicate scans within the same project sessions still adversely affect the online
sdfits filler. Each time a duplicate scan is seen, all occurrences of that scan number will be written to the online SDFITS file. This results in multiple copies of at least one of those scans (more if there is more than one duplication of the same scan number). This will be fixed in a future release of sdfits.
- The frequency axis in scans observed with the LSFS procedure is wrong for all but the first integration.
- Documentation of
sdfits is incomplete. We plan on documenting exactly how sdfits translates the values found in the raw FITS files to the actual values written to the output SDFITS file. A draft version of this document is now available. sdfits
|