Release Date: Nov 25, 2011
Generic Release Name: BP14
Public Release Name: "Binocular Observing" release 14
General Description: 2nd release of non-sidereal presets with hot spot drift guiding
Telescope Operator Overview Information
GCS now allows for a drifting hotspot in closed loop guiding by asking PCS in every cycle where the Guidestar SFP should be and translating this into a pixel drift, IT #2853 this new feature can be turned off by setting GCSL/R.driftingHotspot to false in gcs.conf (this will be checked in every guide cycle) if it turned out to be faulty.
GCS configuration scheme has been completely overhauled which affects location and names of AGW configuration files. Please see the Commissioning Wiki entries for AGWStages and RunningGCS to get a full description of the new system.
The IIFGUI has a new 'Status' form that shows subsystem activity for PresetTelescope and OffsetPointing commands.
Support Astronomer Overview Information
PCS implemented two new methods, enableRBTipTilt() and applyRBTipTilt(), in support of the PSFs to provide the PCS with the tip/tilt requests which accomplish range balancing. The enableRBTipTilt() is intended for testing only; it enables/disables use of the PSF tip/tilt requests. The applyRBTipTilt() method is the routine invoked by the PSFs to deliver their tip/tilt requests to the PCS.
New Reflective Memory variables
pcs.side[0|1].optics.[tip|tilt]RB - PSF tip/tilt request to the PCS to accomplish range balancing (arcseconds)
pcs.useRBValues - Indicator to use or reject the PSF tip/tilt requests (Currently must use the pcsclient to enable/disable the PSF requests.)
New PresetTelescope modes are supported for AO. They allow for transitioning to adaptive mode from modes other than ACTIVE, and if the AO loop is opened, the fallback will be to the simpler mode. ADAPTIVExxx can be used as aliases for ADAPTIVExxx_ACTIVE.
Support subsystem activity messages for Preset and Offset commands.
Remove PCS setGuidingSubsystem() calls as unneeded.
Make general changeMode event and remove specific events (i.e. trackMode, etc.).
Add cancelPreset event when a Preset is canceled.
Create method to generate 'friendly' mode names.
Support complex adaptive modes (IssueTrak 3738). Adaptive mode can now be reached from TRACK, GUIDE, or ACTIVE, instead of just ACTIVE. If the adaptive loop is opened, the fallback will be to the starting mode.
updated the AGW configuration files' WFS_redefine_hex_z settings as requested in IT# 3743
autoSelectAGW() & setNewInstrument() do not return a warning state anymore if a FS/instrument combination has a NOAGW definition explicitly set, they still return a warning if it couldn't find a definition
updated the AGW configuration files' WFS_redefine_hex_z settings as requested in IT# 3762 - which contradict some in #3743
adding guidecam_maxExposure back into OSU_L.cfg as described in IT #3765
added WFS_lenslet_rotation settings to AIP_R.cfg and AIP_IRTC_R.cfg (IT #3777)
copied the AGW1_IRTC config files from the mountain and updated them in SVN (IT #3775)
split the configuration files into public and private, private is where they used to be, public ones are in ~telescope/TCS/Configuration/GCS/
moved the rotator definition from public into private config file and adapted WFS references to match this change
moved the onAxis position definition from public into private config file
converting agw-control machine name to IP and keep it internally to avoid numerous DNS lookups with oacontrol calls (IT #3772)
updated WFS_pupil_dir_x/y to +1 in AO_IRTC_L.cfg as requested in IT #3775
added AGW status info to show up in GUI that indicates initialization of probe, guide and WFS cams, so it shows in which state the GCS might hang if it does
Wavelength for all non-sidereal targets is as requested if within the valid range (0.3 - 15.0 microns). Otherwise, the wavelength is set to the value in the PCSInstrument.conf file for the specific instrument. Formerly, the default wavelength for non-sidereal targets was 0.55 microns, but the wavelength should not be treated specially just for non-sidereal targets.
Modified the updatePointingReference (absorb functionality) to handle non-sidereal targets and any binocular targets properly.
Modified the examination of the command return object from the PSF adjustPointing() method.
Implemented two new methods, enableRBTipTilt() and applyRBTipTilt(), in support of the PSFs to provide the PCS with the tip/tilt requests which accomplish range balancing. The enableRBTipTilt() is intended for testing only; it enables/disables use of the PSF tip/tilt requests. The applyRBTipTilt() method is the routine invoked by the PSFs to deliver their tip/tilt requests to the PCS.
New Reflective Memory variables
pcs.side[0|1].optics.[tip|tilt]RB - PSF tip/tilt request to the PCS to accomplish range balancing (arcseconds)
pcs.useRBValues - Indicator to use or reject the PSF tip/tilt requests
Ensure that regardless of when the PCS is started with respect to the MCSPU ("before" or "after" where "after" is typical), the PCS obtains the error codes for the four telescope axes as necessary.
Fixed a subtle bug which was revealed when using the Left, Rear, Bent Gregorian rotator. If the RPC communication with the MCSPU were to return an RPCERROR unexpectedly, instead of returning the rotator error code string of ten characters, actions performed on the RPCERROR string could crash the PCS. Patched on the mountain in BP13.
Fixed a bug in the linear interpolation routine which computes the target RA from the non-sidereal ephemeris. Specifically, the fix addresses the RA transition boundary 0<->23:59:59.
Fixed a bug in the binocular algorithm when neither telescope side is locked and one telescope roll is just less then pi and the other telescope roll is just greater than -pi.
Includes the patch to turn on the appropriate rotator indexing in order to generate rotator trajectories for the Left, Back, Bent Gregorian focal station. This change was checked into the BP13 branch and trunk.