Release Date: May 05, 2014
Generic Release Name: 2014B
Telescope Operator Overview Information
Items on the OSSGUI that used to be cyan are now green.
Support Astronomer Overview Information
PCS: The LBC Guiding was corrected such that the initial guide update issued by LBC is still (0, 0) even after the guiding gain factor is applied.
New Functionality Tests that need to be performed with the Telescope
PCS: Test LBC guiding to ensure the initial guide update of (0, 0) issued by LBC at the start of every new exposure is still interpreted as (0, 0) in the PCS even after the guiding gain factor is computed.
Modified the LBC guiding routine (setCentroid) as John noted to me during the 2014A testing that the LBC (0,0) guide updates were no longer (0,0), but rather had become very small values. A small bug was introduced when the scaling routine was implemented (TCS Build 2012F). The PCS guiding routine for LBC takes guide corrections (delta values) in radians. This is in contrast to the PCS guiding routines used by the GCS which take guide updates (absolute values) in millimeters. In addition, since LBC does not tell the PCS the coordinates of its "guide star", PCS assumes the guide star is the target. When the scaling function was implemented to compute a gain value, a delta value (centroid - hotspot distance) was being computed for LBC unnecessarily as LBC was already providing the delta value; this meant a small non-zero value was being subtracted from the guide update. Also, when computing the actual guide correction (absolute value) to be provided to the pointing kernel, the same small non-zero was being added to the guide correction. In both instances, the small non-zero value should have been defined to be zero.
Saving the initial SFP coordinates requested by GCS in data dictionary variables. These are the coordinates GCS uses to perform the acquisition. These variables are in testing for the computation of the SFP2CCD coordinates for non-sidereal targets.
New data dictionary items: pcs.side[0|1].pointingStatus.guider.acqPredicted_[X|Y]
PATCH on 2014A: A deficiency was discovered in the implementation for non-sidereal targets. If the observer specifies coordinates on the surface of a target body, there are additional values put into the output ephemeris table by default: (A) target surface location and (B) indicator to denote if the location is illuminated by any portion of the sun's disk. This information is not documented in the JPL Horizons manual, but it is present in the output file! The PCS was modified to parse the ephemeris text line appropriately when this information is present.
Add side and owner (subsystem name) to a result created from an event. This adds back missing information from cleaned up events that no longer have a side or subsystem name (for improved event log appearance).