Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Story Points:3
-
Epic Link:
-
Sprint:TSSW Sprint - Jan 18 - Feb 1, TSSW Sprint - Feb 1 - Feb 15
-
Team:Telescope and Site
-
Urgent?:No
Description
ASC has a well-defined API to control the vendor software with several dozen commands and queries. Some of these internal commands, such as the ones to measure the positions of telescope components, will be directly invoked by SAL commands. Others, like the flag to visit SMRs in a randomized order, it makes more sense to have these be set in a config file and may otherwise be hidden from SAL. This task is to work through the API and figure out which calls can be exclusively managed through the CSC config file
Attachments
Activity
LGTM
Sorry, I accidentally approved the wrong ticket.
Exploratory ticket to investigate the interface between CSC and vendor provided code for the alignment system. Looks good.
Identified 7 T2SA commands that shouldn't need to be invoked directly by SAL:
SET_RANDOMIZE_POINTS (visit SMRs in random order)
SET_2FACE_TOL (Tracker can measure most points in two orientations, which should produce theoretically produce identical results. This is the tolerance for discrepancy between the two)
SET_DRIFT_TOL (How much 'drift' from expected position do we allow before we have to re-orient the position of the tracker relative to M1M3)
SET_LS_TOL (least squares tolerance)
SET_NUM_SAMPLES (number of repeated measurements of the same point, on the same visit, that are averaged together for improved precision)
SET_NUM_ITERATIONS (number of times we revisit each SMR. total number of measurements will be NUM_SAMPLES * NUM_ITERATIONS)
SET_POWER_LOCK (enable or disable the tracker using its built-in camera to quickly find SMRs. We don't yet know how well this will work in the actual telescope with numerous reflective surfaces that might confuse the camera)
I believe these can be set by CSC config file only.