Software Release Notes for Build "2013C"

Release Date: September 12, 2013
Release Name: 2013C
General Description:

Telescope Operator Overview Information

  • Pending synchronous Preset and Offset commands can now be 'released' to help in error recovery. When a pending synchronous Preset or Offset is released it executes as an asynchronous operation and must be within the co-pointing limit. If a Preset that is waiting for PCS target processing is released, it executes as a side "both" target. This only affects a single operation. Note that 'pending' means not yet active. The 'release' operation also always clears the PCS semaphores, so if a (active) Preset is waiting on the PCS to synchronize guide acquisitions, the waiting Preset should be allowed to continue.

Support Astronomer Overview Information

  • The PMC actuator telemetry streams have been redefined. Instead of 160 streams, there are now just 20, with eight actuators per stream. Each actuator is a telemetry component in its stream, with the same data as before. The 160 actuators are grouped in the streams by actuator number, so the first stream contains actuators 101 - 108, the second 109 - 116 etc. The reorganization was done to reduce memory requirements and avoid 'Command thread creation failed' errors.
  • The IIF 'Accept' BinocularControl check boxes on the IIFGUI control page have been changed to 'Ignore' check boxes, with the corresponding inversion of meaning.
  • The IIF now supports a new 'pseudo-monocular' mode. This mode is selected on the IIFGUI Control page, and allows binocular operations when one instrument is not working. It also supports 'symbiotic' observing by a passive instrument. The 'active' instrument has complete control of the telescope with Presets and Offsets; Presets are ignored from the 'passive' instrument and Offsets from the passive instrument are always handled as binocular asynchronous. Due to implementation limitations, LBC cannot be the active instrument.
  • PCS: Generalized the setEquatorialTarget() (Preset) to accommodate COORD_AZALT and COORD_GALACTIC coordinate types.
  • PCS: Generalized the offsetTelescopeEquatorial() (Offset) to accommodate COORD_AZALT and COORD_GALACTIC coordinate types. Only absolute offsets in these two new coordinate systems are supported at this time. Note that offsets done in COORD_RADEC can still be performed as "relative" or "absolute".
  • PCS: MODE_STATIC is now supported. In particular, this mode is needed for AZ/ALT targets. This is special case functionality where the telescope will slew to an AZ/ALT location and HOLD. However, the command will work for any supported coordinate reference frame (RA/DEC and GALL/GALB).
  • PCS: Modified the functionality of the PCS setTargetOffset() and setNSTargetOffset() commands which are really Presets with embedded Offsets. The modified functionality is to NOT assume the Offsets will be synchronized.
  • PCS: IT 3372 was addressed in that only the Preset (base target) portion of a synchronized binocular Preset which contains an embedded Offset is synchronized.

The Details

New Functionality Tests that need to be performed with the Telescope

  • none

Patches to the Release

  • none

Known Bugs

  • none.

Release Overview

  • none

IIF list of Public Data Dictionary Variables

Operating System, System Configuration, TCS and Hardware Computers

TCS Servers / Workstations

  • none.

jet computer, DSP, FPGA

  • A new copy of the CPU system board (Adlink cPCI-6880) that has been running jet for the past couple years was purchased and installed. A new rear transition module was purchased with the board, but not installed and remains a spare on the mountain, along with the original system board.

Networks

  • none.

PLCs

  • A new Allen Bradley Controllogix CPU (L72) was installed on the ECS and put into service during the summer. This CPU uses firmware V19.15, so all versions of RSLogix must be at least at V19.
  • Two Controllogix HART modules were installed to support the new Rotork valve actuators for the ICS project and the various thermocouples and pressure transducers. An OF8H output module for the Rotork actuators was installed in Rack8/S3 and an IF16H input module was installed for the field devices. Additionally, for the two safety valves CV0432 and CV0433, an IB16I input and OB16E output modules were installed in Rack8 to support feedback from the safety valves and command output.
  • The lower shutter door encoders are fed off a Controllogix DeviceNet bridge (Rack8 Slot2), in service but not used since earlier in the year. These are now the primary shutter door encoders. The upper shutter door encoder positions, SD1001_POSITION and SD1002_POSITION, will be zeroed out until the new DeviceNet encoders are installed and operational.
  • The logic for controlling the new ICS valves remains partly in the "InstrumentCooling" routine as before (pump handling was largely untouched) with the remainder operating in a 1000ms periodic task. All the servo functions are in the periodic task, with error checking and handling left in the InstrumentCooling routine.

TCS Subsystems and GUIs, and significant configuration files

AGw control server

  • none.
    • AGW7 and AGW8 configuration additions (pending AIP ...)
    • AGW1, AGW2 UMAC firmware updated (Homing patch 20130516)
    • AGW3, AGW4 UMAC firmware (pending Homing patch)
    • AGW7, AGW7 UMAC firmware (pending Homing patch)

azcamserver and controller computers

  • The new Software 5.1, and preparations for PEPSI.
    • azcamserver Ver.5.1 (not BETA) tested and is in Use now (in 2013B was Ver. 4.6 "AzCamServer")
    • azcamserver spare running Ver.5.1.BETA under Win 7 is parked and unused now (in 2013B was Ver. 4.6 "AzCamServer")
    • agw1-cam running Ver.5.1 under Win 7 (was Ver.10.28 under Win XP)
    • agw2-cam running Ver.5.1 under Win 7 (was 2 separate "Shuttle Box" computers with Ver.4.0 under Win XP)
    • mods1-cam running Ver.5.1 under Win 7 (was Ver.10.24 under Win 7)
    • mods2-cam running Ver.5.1 under Win 7 (newly added computer)
    • agw3-cam Ver.5.1 under Win 7 (was Server Ver.2.4 under Win XP)
    • agw4-cam now Server Ver.2.4 under Win XP
    • agw7-cam now Server Ver. 2.4 ?
    • agw8-cam now Server Ver. 2.4 ?

AOS - Adaptive Optics

  • none

ECS - Enclosure Control

  • The ICS changes made during the summer shutdown did not radically effect the ECS subsystem. CV0424 and CV0425 valve actuators are still controlled either via manual or automatic mode from the ECS GUI, with temperature control also via automatic or manual modes.
  • Safety valves were installed (CV0432 and CV0433, SX and DX, respectively) for each of the modulating valves. Their control is automatic and cannot be directly controlled via the ECS GUI. The safety valve may be closed by commanding manual valve control and setting a modulating valve position of 10.0% or less. Commanding the modulating valt to open above 10.0% will cause the safety valve will return to it's full-open state.
  • A number of new alarms have been added, all of which can be cleared on the Valves page in the ECS GUI. Note that in two instances, ICS will also turn off the pumps (coolant temperature exceeds 35C or a failure detected on the hot-side output temperature sensor) and trigger an alarm on the "Pumps" page. In this case, the alarm for the pumps will also need to be cleared in addition the valve alarm.
  • The dome dewpoint and ambient temperature sensors are now monitored for failures. A failure in either sensor will trigger an alarm in the ECS and force both modulating valves (and their respective safety valves) to the fully closed position.
  • Data from temperature sensors TT0430-TT0433 and PT0410, PT0412, PT0415 and PT0417 have been added to ECS telemetry.
  • The "deadband" text box was removed from the ECS GUI, as the deadband is no longer supported in the PLC.
  • The 16-bit upper shutter door encoders were removed, so the shutter doors are now using the lower encoders, a pair of 32-bit DeviceNet encoders. The encoder counts from shutters fully closed to fully open has been modified in both the PLC and the ECS GUI. The shutter drives double their velocity in approximately the middle half of shutter door travel.
  • IT #4683 once again provides scrolling in the ECS alarm window. The ECS GUI will not, however, cache past alarms, as it relies on state changes. For reviewing previous alarms, refer to the TCS event or log files.
  • IT #4516 is also addressed, through both the ICS rework and more specific alarm messages in the ECS GUI.

ENV - Environmental Sensors

  • ENV Version 1.17
    • Improve status reporting by converting fprintf() to SYSLOG and events, and add a dynamic debug configuration variable.
    • Add weather timestamp to telemetry.
    • Remove anemometer reading code since this is now the responsibility of the AOS.
    • Add severity indicator for master GUI.
    • Clean up a 'long' in the SMT weather class.
    • Change sampling rate for LBT weather from 10 to 1 seconds.
    • Change reflective memory timestamps from 'int' to 'long'.

IIF - Instrument Interface

  • IIF Version 8.22
    • Add reflective memory variables S_FrontRotReady and S_DirectRotReady. This will allow an instrument to easily check rotator status.
    • Change accept binocular control to ignore binocular control and allow both sides to ignore at the same time.
    • Allow pending synchronous Preset and Offset commands to be 'released' to help in error recovery. When a pending synchronous Preset or Offset is 'released' it executes as an asynchronous operation and must be within the co-pointing limit. If a Preset that is waiting for PCS target processing is released, it executes as a side "both" target. This only affects a single operation.
    • Add pseudo-monocular mode to a particular side. This is also to aid in error recovery. pseudo-monocular mode means SYNCPRESET and SYNCOFFSET BinocularControl commands are ignored (and return a warning), and a side of 'both' is converted to the active side. The ICE interface issues two synchronous Presets or Offsets, one for each side, when it gets a Preset/Offset from the active side (instead of issuing commands to both sides in the command handler). If there is a pending synchronous Preset or Offset when the mode is activated it will be 'released'. When the mode is reverted, full synchronous operation is enabled. The main use for this mode is to avoid authorizing a broken side as 'none' which will stop operations on the working side.
    • Allow null strings to mean 'default' or 'none' in some StrToXX() methods. This allows instruments to use an empty string to get default behavior in some cases.
    • Make the interface case insensitive. This applies to command parameters, instrument names, focal stations and side names. Internally instrument names and command parameters (i.e., things like mode name) are converted to upper case while focal stations and sides are converted to lower case.
    • Add new command SetGuidingHotspot for PEPSI.
    • Add severity indicator for master GUI.
    • Add parameter value range checking. Check for nan, inf, and value ranges where appropriate. Reject the command (with an event) if any of the range checks fail.
    • Deprecate COORD_FOCAL_MM.
    • Allow AZALT and GALACTIC coordinate systems.
    • New public DD variables.
    • Add non-sidereal information to the Position class, and remove the NonSidereal object from the Preset command. NOTE: this will require a small coding change and rebuilding in the LBC.
    • Support MODE_STATIC since ARGOS wants it. In binocular operation only allow STATIC for side 'both'.
    • Disallow target proper motion unless coordinate system is RADEC.
    • Change waitForElevation() to use IIF reflective memory variable elOnSource instead of 'tracking' state and objectPositionError less than 100 arc-seconds.
    • For STATIC preset mode use new MCS reflective memory onPosition variables.
    • Add additional external data dictionary names for PCS AZ/ALT variables.
    • Add data dictionary variables for LBC, MODS, and LUCIFER.
    • Reject relative offsets in AZALT and GALACTIC coordinate systems since they are not yet supported.
    • Reinstate checks for command side vs. instrument side that got broken when pseudo-monocular was added. (A left side instrument must not be allowed to send a right side command.)
    • Extend pseudo-monocular mode to support matched pair instruments.
    • Allow 5 micro-radians beyond nominal limits in target range checking.
    • Clear PCS semaphores if passive side pseudo-monocular command fails.
    • Always clear PCS semaphores on CANCELSYNC*, RELEASE*, and MONOCULAR BinocularControl operations to improve chance of error recovery.

  • IIFGUI Version 4.4
    • Change accept binocular control to ignore binocular control.
    • Add controls for setting pseudo-monocular mode.
    • Add controls for releasing pending synchronous commands.

GCS - Guiding Control

  • GCS Version 2.13
    • Correct (per Doug Miller) position rounding when finding the subapp position.
    • Add the RMS value of the found spot centroids when using the dynamic reconstructor to the image header.
    • Added Primary Mirror Zernikes to WFS FITS header to verify IT #4599, per Doug Miller.
    • Added config files for PEPSIPFU, PEPSIPOL, AGW7, AGW8.
    • Added severity indicator DD name for master GUI.
      gcs.side[].severity
    • Added "AGWUnitAIPPFU" unit and slection for AIP_PepsiPfu case.
    • Extended time tracing.
    • Updated GCS config files to match "AzCam" changes.
    • Added GCS config file for MODS2.
    • Added DD refmem name for PEPSIPFU "GuideCam":
      gcs.side[].GuideCam.rotAngleOffs
    • Added a set of G.S. related DD refmem variables:
      gcs.side[].AGW.probeRotationDir
      gcs.side[].GuideCam.GS_ALT
      gcs.side[].GuideCam.GS_AZ
      gcs.side[].GuideCam.GS_MAGN
      gcs.side[].GuideCam.GS_COLOR
      gcs.side[].GuideCam.GS_OFFX_MM
      gcs.side[].GuideCam.GS_OFFY_MM
      gcs.side[].GuideCam.GS_OFFX_PIX
      gcs.side[].GuideCam.GS_OFFY_PIX
      gcs.side[].GuideCam.GS_OFF_MM
      gcs.side[].GuideCam.GS_OFF_ASEC
    • Added DD refmem names to extent a lenght of GCS status messages.
      gcs.side[].statusMsg
      gcs.side[].AGW.statusMsg
      gcs.side[].GuideCam.statusMsg
      gcs.side[].WFSCam.statusMsg
    • Corrected "bad" sources rejection logic as partial fix for IT #4549 ("Hot pixels").
    • Extended Guide FITS header.
    • Extended logging for G.S. selection and "HotSpot".
    • Added to GCS "detection only" for AZALT coordinate presets. (Not used yet)
    • Switched to Source Extractor v.2.8.6 (previously used v.2.5.0)

LSS - Logging and Events

  • LSS Version 3.10
    • Remove 'running' DD variable.
    • Convert 'bit' DD types to 'bool'.
    • Use new accepting incoming RPCs global flag.
    • Add severity indicator for master GUI.

  • LSSGUI Version 2.3
    • Use new accepting incoming RPC flag to indicate problem with RPCs.
    • Change event display widgets to limit the number of lines (1000000) that will be saved. When a new line is added above the limit, the oldest line is discarded. IssueTrak 4727.

MCS / mcstemp - Mount Control (MCSPU version 744)

  • Altered MCSPU::syncPos to log when the LOG_ALL_SYNCPOS_DATA.d() variable (in mcspu.conf) changes state. Also, when it goes from true to false (recording to not recording) synpos closes the file.
  • The MCSPU Parser class has been enhanced with new scanning methods. None are used in MCSPU, though, so it should have no effect.
  • Changed the TelemAxis class "execute" loop so that, if the time of the current telemetry record is <= the time of the last telemetry record, it doesn't send it. This was done because the telemetry software throws an exception if you give it a record with a duplicate time, which, because of sampling issues, the MCSPU was doing once in a while. This affects AZ axis and EL axis telemetry only.
  • Added MJDTime::julianDay(), MJDTime::mjdUT() and MJDTime::ut() which are used in the new position server (see below).
  • Added a laserOffSource signal (kind of like the pre-existing on-source signals) so that ARGOS could tell when the telescope is not pointing where it is commanded to point. Unlike on-source, this signal is meaningful when in HOLDING mode and TRACKING mode. This variable is accessed through the Data Dictionary or through the position server.
  • ARGOS_ERROR_LIMIT_ASEC and ARGOS_TIME_TOLERANCE_SEC were added to the mcspu.conf file. These are used by MCSPU::checkLaserOffsource and determine the time and angle tolerances that make the laserOffSource signal change state.
  • The existing PositionServer class was modified to transmit the timestamp of the requested position record in MJD instead of MJD-TAI. The data record that it sends to client was also to contain the laserOffSource flag.
  • In MCSPU Servo::timeLag() was added, which is used in the simulation mode only to simulate a servo following error at high accelerations and velocities. This helped debug the PositionServer? changes.
  • Altered ScrWin? ::restartPositionServer to have the name ScrWin? ::positionServer and to take a numeric argument (0 or 1). This is the command in the Engineering Interface which allows the telescope operator to control the position server.
  • PositionServer? ::getMessage() which gets a message from the client has been changed to use select so that it won't hang if the client dies.
  • Fixed a bug in Server::atomicPosition() in the simulation branch of the method. This bug only affected simulation mode.
  • Added RPC callable method MCSPU:rslewtoholdwrap method to the MCSPU for PCS to use. This accepts rotator slewtohold commands which have arguments outside the normal -90 to 450 deg. range. It simply wraps the argument into legal range by adding or subtracting 360 and then proceeds.
  • Fixed a bug in simulation mode only that was in slewToHold. Giving it a slewToHold to the position that it was already tracking, made it stay in tracking mode instead of switching to hold mode.
  • Added the onPosition flag to the Data Dictionary for AZ/EL. It is similar to the on-source signal. It is true whenever the AZ/EL encoders are at the position commanded by the current polynomial. This is different from the pre-existing on-source signal because that relates only to tracking state. onPosition is active during tracking and holding state. (In Holding state MCSPU sends polynomials to the DSP which have zero acceleration and zero velocity.)
  • Added azOnlyOnPosition and elOnlyOnPosition to the Data Dictionary. These indicate (like the on-position flag above) when the telescope is at the commanded position regardless of whether that is a tracking position or a holding position.
  • Added allOnPosition and sideOnPosition to the Data Dictionary. These are generated in the MCS (as opposed to the MCSPU, where the other onPosition signals are generated). They are used by the IIF to implement STATIC mode moves.
  • Events were created to log changes in the states of the various on-position variables.

OSS - Optical Support

  • OSS Version 3.2
    • Save tertiary focal station commanded positions in reflective memory.
    • Rename existing swing arm telemetry stream to 'static' and add 'dynamic' telemetry stream. The rates are controlled by configuration variables. static is collected all the time at a low rate. dynamic is only collected when a swing arm is being moved.
    • Add slow/fast rate control to dynamic balance telemetry. The rates are controlled by configuration variables. The slow rate is also gated by being at zenith, and the fast rate takes effect only when the system is pumping.
    • Add dynamic balance 'remaining moments' to telemetry and save for GUI.
    • Remove 'running' DD variable.
    • Add severity indicator for master GUI.
    • Change 'unsigned int' to 'size_t' in preparation for 64 bit Linux.
    • Update DX tertiary home offset, and tertiary focal station positions for both sides per Bob Meeks.
    • Add side name and component name for all CommandReturn error results (IssueTrak 4784).
    • Update oss.conf with new LFBG tertiary focal station position per John Hill.

  • OSSGUI Version 3.1
    • Update secondary and tertiary position edit boxes with commanded positions instead of actual positions.
    • Display dynamic balance 'remaining moments'.
    • Change 'unsigned int' to 'size_t' in preparation for 64 bit Linux.

PCS - Pointing Control

  • PCS Version 6.26a/b
    • The solution to the problem with PCS internals (semaphores) with regard to the updateGuideOrigin() (pointing correction) was improved.

  • PCS Version 6.26
    • The instrument-demanded rotator trajectories are now stored in telemetry for LBC and LINC/PATHFINDER.
      • LBC receives their trajectories as (timestamp, theta) in units of (JD TAI, radians), but the telemetry is stored as (MJD UTC, degrees).
      • LINC/PATHFINDER can potentially use up to a second-order polynomial for the rotator trajectory. As such, LINC receives their trajectories as (timestamp, position, velocity, acceleration) in units of (MJD UTC, radians, radians/s, radians/s/s), but the telemetry is stored as (MJD UTC, degrees, degrees/s, degrees/s/s).
      • Telemetry files are named as yyyymmddtttt.pcs.[sx|dx].[lbc|linc]rotatordemand.h5.
    • A problem with PCS internals (semaphores) was addressed; the problem the GCS to be in a wait state before it could begin guiding. This was particularly an issue for synchronized Presets where the SX and DX instruments both use the GCS AGWs.
    • A fix was implemented to ensure the reference point for the telescope orientation to be that of the base target (Preset target) after an offset has been performed.
    • Generalized the setEquatorialTarget() (Preset) to accommodate COORD_AZALT and COORD_GALACTIC coordinate types. The code was modified such that regardless of the coordinate system used to define the target (COORD_RADEC, COORD_AZALT, or COORD_GALACTIC), the coordinates of the remaining two systems will be computed upon ingest. Note: the Galactic l/b computed from RA/Dec on ingest are represented as if they were catalog coordinates with proper motion reported separately. These so-called preset coordinates are stored in new data dictionary items as described below. All computations are actually done in equatorial coordinates. There are also "achieved" data dictionary items defined for all three coordinate systems; the achieved coordinates include the proper motion correction.
    • Generalized the offsetTelescopeEquatorial() (Offset) to accommodate COORD_AZALT and COORD_GALACTIC coordinate types. Only absolute offsets in these two new coordinate systems are supported at this time. Note that offsets done in COORD_RADEC can still be performed as "relative" or "absolute".
    • Generalized the computeKFPCoordinates() and getKFPCoordinates() functions to support guide/reference stars whose coordinates can be provided as COORD_RADEC, COORD_GALACTIC, and COORD_AZALT.
      • The updateGuideOrigin() and applyGuideCorrection() will accept AZALT updates from GCS for PEPSIPFU. The computeKFPCoordinates() will provide predicted guide star coordinates in AZALT; the values are effectively zero as the guide star is the target.
    • Comment on the support of AZ/ALT coordinate specification of the target or offset. The instrument specified azimuth values are positive only (0 to 2pi). When converting RA/Dec or L/B to AZ/ALT, the AZ value is normalized to the range 0 to 2pi. The AZ/ALT values are in the reference frame of the telescope; North is 0 and azimuth increases to the East (clockwise).
    • Modified the startTracking() routines to accommodate MODE_STATIC. In particular, this mode is needed for AZ/ALT targets. This is special case functionality where the telescope will slew to an AZ/ALT location and HOLD. However, the command will work for any supported coordinate reference frame (RA/DEC and GALL/GALB).
    • Modified the functionality of the PCS setTargetOffset() and setNSTargetOffset() commands which are really Presets with embedded Offsets. If the synchronization flag were set for the Presets, then the command assumed there were going also to be synchronized Offsets. The modified functionality is to NOT assume the Offsets will be synchronized. This addresses IT 3372.
    • The "offset" commands have been protected from the Instrument software mistakenly issuing a CLEARPRESET command in binocular mode followed by an offset request. Issuing the CLEARPRESET is an inappropriate request before an offset request as the PCS uses the current target information and the newly requested offset to verify the co-pointing limit. The CLEARPRESET deletes the current target information. The PCS now issues an error as soon as it receives the offset request.
    • Added the original PSF range balance tip/tilt requests to the PCS "trajectories" telemetry stream. This stream also contains the PCS computed tip/tilt demands which have been stored in the PSF reference frame (units=arcseconds, sign differences and the PCS tip being a PSF tilt has been taken into account so analysis of this telemetry stream allows one to compare PCS tip to PSF tip without confusion).
    • New Data Dictionary Items (some of which are in support of ARGOS)
Private Public
pcs.side[].preset.target_AZ.Radians  
pcs.side[].preset.target_ALT.Radians  
pcs.side[].preset.target_AZ.AZString S_PresetTargetAZDMS
pcs.side[].preset.target_ALT.ALTString S_PresetTargetALTDMS
pcs.side[].preset.target_L.Degrees S_PresetTargetGALLDeg
pcs.side[].preset.target_B.Degrees S_PresetTargetGALBDeg
pcs.side[].pointingStatus.achieved.achieved_AZ.Radians S_AchievedAZ
pcs.side[].pointingStatus.achieved.achieved_ALT.Radians S_AchievedALT
pcs.side[].pointingStatus.achieved.achieved_AZ.AZString S_AchievedAZDMS
pcs.side[].pointingStatus.achieved.achieved_ALT.ALTString S_AchievedALTDMS
pcs.side[].pointingStatus.achieved.achieved_L.Degrees S_AchievedGALLDeg
pcs.side[].pointingStatus.achieved.achieved_B.Degrees S_AchievedGALBDeg
pcs.mount.achieved.achieved_AZ.Radians MountAchievedAZ
pcs.mount.achieved.achieved_ALT.Radians MountAchievedALT
pcs.mount.achieved.achieved_AZ.AZString MountAchievedAZDMS
pcs.mount.achieved.achieved_ALT.ALTString MountAchievedALTDMS

  • PCSGUI
    • PCSGUI Version 1.5
      • The PCS tips/tilts displayed on the Optics panel of the PCSGUI display zero values when there is no target set. This addresses the issue of the user seeing very large values when, for example, an instrument has been authorized. In this case, there is no target set, and the large tip/tilt values are not actually sent from the PCS to the PSF.
      • Added another decimal place to the tip/tilt values by request.
      • Removed the "compromise" information from the Optics Panel as it was not general and was confusing the interpretation.
      • Fixed PCSGUI due to MCS data dictionary items changing from datatype INT to BOOL. The switch statement had too many cases for mcs.sideOnSource.

Pointing Kernel / Pointing Kernel tools

  • none.

PMC - Primary Mirror Cell

  • PMC Version 5.27
    • Change Actuator telemetry to put eight actuators in a stream instead of one. This helps with memory size and also seems to waste less space in the hdf5 files.
    • Rework the Actuator thread loop timing so it gets much closer to the requested value. It is now running at 4 Hz when previously it was around 3 Hz.
    • Clean up telemetry events in all threads.
    • Add severity indicators for use by the master GUI.
    • Clean up 'long' types in several places.
    • Remove 'int' casts on timestamps in preparation for 64 bit Linux.

  • PMCGUI Version 6.3
    • Update online documentation.

PSF - Point Spread Function

  • PSF Version 6.3
    • Add severity indicator for the master GUI.
    • Remove 'int' casts on timestamps in preparation for 64 bit Linux.

TCS GUI

  • TCSGUI Version 2.2
    • Protect against illegal/unknown syslogserver computer names.

WX - Weather Station

  • The weather station has been ported to Linux. It pulls its data from the data dictionary now, so ultimately it still relies on the original Windows weather station server running. The Windows machine that displayed the weather station GUI, however, no longer needs to be remoted into since the new weather station GUI runs on the TCS cluster. The new Linux based version incorporates the original weather station info as well as the sky quality monitor and AllSky camera image and time lapse display.

FACSUM - Facility Summary

* The Facility Summary GUI pulls together many important pieces of observation status into a single unified presentation. It is intended to give a high level overview of the main activities occurring during observation as well as a subset of weather information (including the AllSky images).

TCS Common Software

commandreturn - client command status returns

  • none.

commandsequencer - client/subsystem command handling

  • none.

core - foundation routines

  • Clean up SYSLOG messages in Configuration class.
  • Support NAN and INF through argument lists.

datadictionary - reflective memory and event support

  • none.

eventhandler - event handling

  • none.

networkconfig - subsystem management

  • Stop writing TCSSYSLOG-lock file in syslogserver. Use System::isRunning() in netconfig to detect a running syslogserver.
  • Roll the syslog file at 00:00 local time so it matches the LSS rolling the events file.

reflectivememory - global shared memory

  • none.

rpc - communication protocol

  • Make accepting incoming RPCs flag available as a global variable.

setvalue - reflective memory access

  • none

tcs_config - tcs configuration

  • none.

TCS Tools

DDEditor - Data Dictionary Editor

  • none.

DDBrowser - Data Dictionary Browser

  • none.

DDViewer - Data Dictionary Viewer

  • none.

Event Editor

  • none.

Telemetry

Collector

  • none

Instruments and Environmental Sensors

DIMM - Differential Image Motion Monitor

  • none

IRTC - Infrared Test Camera

  • IRTC Version 3.9
    • Add new IIF command SetGuidingHotspot.
    • Make IRC commands case insensitive.
    • Display possible choices for an ambiguous IRC command request.

  • IRTC Version 3.10
    • Properly support AZ/ALT coordinates for SetStars, SetTarget, and GetKFPCoordinates commands.
    • Properly support GALACTIC coordinates for SetStars, SetTarget, and GetKFPCoordinates commands.

LBC - LBT Binocular Camera

LBTO Weather Station - 3DWGUI

  • none.

MAT - Mount Axilliary Telescope

  • none.

All Sky Monitor

  • none.

-- MicheleDeLaPena - 26 Aug 2013
Topic revision: r23 - 18 Oct 2013, ChrisBiddick
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback