TCS Software Tests that have been completed.

B35 - Test 1 - Verify the problem of predicting a premature encounter with the end of the rotator cable wrap is fixed.

Test Description: A bug in the Pointing Kernel caused the acceleration term of the rotator polynomial to be overly large and varied a bit wildly. Since the MCSPU computation to predict when the rotator will hit the end of the cable wrap depends upon this value, the "end of cable wrap indicator" was being triggered prematurely.
Test Responsible Party: Instrument Support Astronomer
Original SW Release #: B35
How to perform the test: Force the rotator to travel to near the end of its cable wrap and then start an observation. Ensure the rotator does not stop until ~450 degrees. Forcing the rotator to near the end of the wrap can be done by doing a preset to an object that is about 3 hours east of the meridian and at about 35 deg. declination. This will direct the rotator to an angle just under 90 deg. Then do an rhold and then rslewtohold to 400 deg. After the rotator gets there, give it an rslewtotrack command. This will place it within a couple degrees of 450 and tracking towards the limit.
Required Inputs: TCS up and running. Move the rotator to near the end (but not at the end) of its wrap.
Expected Outputs: The rotator will reach the end of the cable wrap at approximately 450 degrees.
Tester's Name: J. Hill / A. Ceranski
Test Date: 20091125 UT
Passed/Failed: Passed.
Actual Results from running test: Rotator stops correctly at -89:56:12 after making warning messages on MCSPU for 5 minutes. Note that instructions had the wrong limit described for objects North of Zenith.

B34 - Test 1 - Test PresetTelescope and OffsetPointing (in RA/Dec) with LBC.

Test Description: The code which computes the on-demand rotator trajectories for the LBC has been modified to be more robust. It is requested that both presets and large offsets be performed with LBC to ensure there are no rotator trajectory problems.
Test Responsible Party: Support Astronomer
Original SW Release #: B31, Re-released for B34
How to perform the test: Problems have been detected in the past when the LBC performs a PresetTelescope followed by several large OffsetPointing requests. In particular, the first entry of the rotator trajectory (time, angle pairs) was found to be incorrect. It is requested the LBC perform a dither pattern with large offsets in an effort to ensure any problem with the angle in the rotator trajectory can be detected.
Required Inputs: PresetTelescope/OffsetPointing (LBC dither pattern)
Expected Outputs: Rotator trajectory (time, angle pairs) where the trajectory puts the LBC into the proper position and there is no discontinuity in the angular component of the trajectory.
Tester's Name: Marco Pedani
Test Date: 13 October 2009
Passed/Failed: Passed
Actual Results from running test: Michele moved this test to "Completed". Marco tested the new on-demand rotator trajectory generation used by LBC during the LBC technical nights.

B32 - Test 1 - Test XFLIP/YFLIP are properly set for Gregorian instruments at runtime.

Test Description: The XFLIP and YFLIP variables which are part of the affine transform which controls the instrument-to-KFP and guider-to_KFP conversions have been parameterized. They are now included in the PCSInstrument.conf file. All the values have been set to the same default values (true or false) as they were previously hardcoded in the PCS source EXCEPT for the LEFT FRONT BENT Gregorian focal station. Both LUCIFER and IRTCFBG values are now false/false, and the IRTCFBG rotation in the affine transform has been set to 0.0 (as is set for LUCIFER).
Test Responsible Party: Support Astronomer
Original SW Release #: B32
How to perform the test: Issue a PresetTelescope as a Gregorian instrument, in particular LUCIFER. Make sure offsets done in DETXY move in the correct direction.
Required Inputs: PresetTelescope/OffsetPointing (DETXY)
Expected Outputs: When LUCIFER wishes to perform a DETXY offset in +X, LUCIFER should issue an offset coordinate in +X.
Tester's Name: Dave Thompson
Test Date: September 2009
Passed/Failed: Passed
Actual Results from running test:

B31 - Test 2 - Test the "absorb" functionality for RA/Dec coordinates.

NOTE: This test is a subset of test B21 - Test 3.
Test Description: OffsetPointing requests can be done currently in both DET_XY (changing the pointing origin) and in RA/Dec space (dither). When an offset is performed, the new coordinates (pointing origin or RA/Dec) can be saved (aka absorbed) to be used as the new reference coordinate from which subsequent offsets are done. In previous TCS builds, the absorption of the RA/Dec coordinate caused the mount trajectories to glitch and guiding would be lost. This problem should be addressed in this new build.
Test Responsible Party: Support Astronomer
Original SW Release #: B31
How to perform the test: Perform a PresetTelescope in MODE_GUIDE followed by an OffsetPointing done in RA/Dec space (dither). Then request the TCS/PCS perform an UpdatePointingReference of the RA/Dec coordinate.
Required Inputs: Perform a PresetTelescope/OffsetPointing in MODE_GUIDE; then request an UpdatePointingReference of the RA/Dec coordinates.
Expected Outputs: The "base" and "target" RA/Dec values should represent the same values (pcs.side[side].pointingStatus.target.base... and pcs.side[side].pointingStatus.target.target...). Further, there should have been no glitch detected in the mount trajectories and no loss of guiding.
Tester's Name: Dave Thompson
Test Date: Sep 2009
Passed/Failed: Passed
Actual Results from running test:

B30 - Test 3 - Ensure guide stars far off-axis can be acquired as in pre-Build 30 observations.

Test Description: The focal length value used in the PCS/GCS interface to accommodate the radial scaling has been changed modestly. The astronomers should verify far off-axis guide stars are acquired at the same level of accuracy as found in the pre-Build 30 TCS.
Test Responsible Party: Support Astronomer
Original SW Release #: B30
How to perform the test: Issue a PresetTelescope with telescope mode MODE_GUIDE and evaluate (somewhat subjective) the guide star is acquired as well as pre-Build 30.
Required Inputs: Target and off-axis guide star, and telescope mode MODE_GUIDE in the PresetTelescope.
Expected Outputs: Acquisition of the guide star is done to the same accuracy as performed by the pre-Build 30 software.
Tester's Name: Dave Thompson
Test Date: September 2009
Passed/Failed: No longer applicable, not necessary.
Actual Results from running test:

B30 - Test 2 - Ensure tracking (LFBG rotator) recovers after an instrument has completed a ROTATOR_MODE=IDLE and switches to ROTATOR_MODE=POSITION.

Test Description: As described in IssueTrak #2258, the rotator trajectory indicator in PCS was not properly reset after an instrument had issued a PresetTelescope with ROTATOR_IDLE and followed up with a new PresetTelescope with ROTATOR_POSITION.
Test Responsible Party: Support Astronomer
Original SW Release #: B30
How to perform the test: Using the LFBG focal station, issue a PresetTelescope with ROTATOR_IDLE and follow up with a PresetTelescope with ROTATOR_POSITION.
Required Inputs: Two telescope presets with the rotator mode set with a particular option.
Expected Outputs: With the PresetTelescope ROTATOR_IDLE, the rotator will be stationary for the LFBG focal station. Once the next PresetTelescope is issued with ROTATOR_POSITION is issued, the rotator should come out of HOLDING and begin slewing and then tracking.
Tester's Name: M. De La Pena
Test Date: Preparation for Build 33.
Passed/Failed: Passed.
Actual Results from running test: This test was done off-line (i.e., closed dome). It did not require any starlight and is purely functional. Using PCS and the MCSPU simulator, I was able to put the rotator in IDLE mode, specifically for an instrument/focal-station which typically uses the telescope rotator, and slewed to a target. I then changed the mode back to POSITION and did another slew. The software responded correctly and re-engaged the rotator for use.

B30 - Test 1 - Proper motion computation now done for the supplied target and guide star.

Test Description: The PCS now applies the proper motion correction for FK5 coordinates for the target and guide star.
Test Responsible Party: Support Astronomer
Original SW Release #: B30
How to perform the test: Supply target and guide star coordinates with proper motion values in order to allow the PCS to apply the corrections. The corrected values are printed to the SYSLOG for the target (PM CorrRA/PM CorrDec) and for the guide star (PM CorrGSRA/PM CorrGSDec). Objects with large proper motions could be used to ensure the target/guide star coordinates are correctly computed and the objects are acquired. Compare the PCS generated coordinates with those produced by the programs currently used by the LBTO Astronomers to apply the proper motion corrections before the coordinates are supplied to the TCS.
Required Inputs: Proper motion values
Expected Outputs: RA and Dec coordinates corrected for proper motion and acquisition of the object.
Tester's Name: Dave Thompson
Test Date: September 2009
Passed/Failed: Passed
Actual Results from running test:

B28 - Test 1 - Evaluate new workstations with respect to science software.

Test Description: Ensure all of the new workstations have the necessary software installed and working properly to support science operations.
Test Responsible Party: LBTO Astronomer
Original SW Release #: B28
How to perform the test: The Astronomer should invoke and use the science software tools (e.g., ds9, iraf & appropriate packages, idl, etc.) they require to be present on the mountain workstations in order to accomplish their work. The new workstations have the names: lbtmu41 - lbtmu44.
Expected Outputs: Software tools are installed and work and/or a list of tools needed to be installed.
Tester's Name: Norm, Michele, Chris
Test Date: Sep 6th, 2009
Passed/Failed: PASSED
Actual Results from running test: We were able to run IRAF and IDL from each workstation (lbtmu41 - lbtmu44). IRAF worked but it complained about a syntax error ".hushiraf" but it appears to work ok, so IRAF is ready to go. IDL works provided the IDL license server is running on lbtmu41. So IDL is ready to go.

B28 - Test 2 - Evaluate new workstations as a backup for the TO Station.

Test Description: Ensure all of the new workstations have the capability to be used as a substitute TO Station, in the event this is necessary. The new workstations have the names: lbtmu41 - lbtmu44.
Test Responsible Party: LBTO Telescope Operator
Original SW Release #: B28
How to perform the test: The Telescope Operator should logon to each of the new workstations and evaluate whether or not all the appropriate software is installed in order to accomplish their work.
Expected Outputs: Software tools are installed and work and/or a list of tools needed to be installed.
Tester's Name: Norm, Chris, Michele
Test Date: Sep 6th, 2009
Passed/Failed: PASSED
Actual Results from running test: All the TCS services (networkserver, gshmserver, rpcserver) and all the GUIs ran on lbtmu41 - lbtmu44. Thus all the workstations can be used as backup TO stations.

B23-Test 12 - Verify new oacontrol package features with the following changes.

Test Description: Test the following new features of the oa control server.
- stop function
- workaround for XY hysteresis
- error handling for motion commands and home
- status functions
Test Responsible Party: Torsten Leibold and/or Support Astronomer
Original SW Release #: B23
Note: GCS in B28 does not support these new functions of oacontrol yet, so they can't be tested until Torsten had time to add support for them. It will also require some test programs to explicitly test the different functions
How to perform the test:
Required Inputs:
Expected Outputs:
Tester's Name:
Test Date:
Passed/Failed: PARTIALLY PASSED, the outstanding issues are in ITs and a new test will be defined for testing additional capabilities, so the failed or untested parts of this test are deprecated
Actual Results from running test: - stop function untested, will be tested with next release of oacontrol software
- status functions show no readings for temperature and humidity, InformationTechnology issued
- XY movement has been verified
- error handling for motion and homing works

B22-Test 11 - Ensure the "achieved" equatorial coordinates now give the correct answer when offsetting in DETXY.

NOTE: The "achieved" reflective memory variables are slated to become obsolete.  
Instead the instruments should be using the "rotator center" coordinates.  
(pcs.side[0/1].pointingStatus.rotator.rotCenter_[RA/DEC])
Test Responsible Party: LBTO Astronomer or Michele
Original SW Release #: B22
How to perform the test: Go to a target on the sky (RA=LST and DEC=00:00:00). Then execute a DETXY offset of X=3mm (0.33s) and Y=3m (5"). This tests the fixed problem in computation of the equatorial coordinates based upon the readback of the encoders.
Required Inputs: As specified above.
Expected Outputs: achieved_RA.RAString=LST+00:00:00.00, achieved_DEC.DECString=00:00:00.00. The achieved coordinates should NOT change when modifying the pointing origin.
Tester's Name:
Test Date:
Passed/Failed: FAILED
Actual Results from running test: See the achieved coordinates that changed in Test 10 above. JMH
This test moved to "Competed" by Michele.

B22-Test 9 - Verify that the Secondary Mirror in the OSS can be re-Initialized

Test Description: Ensure that the Secondary Mirror can be re-initialized after be set back to 'standby' mode.
Test Responsible Party: John Hill
Original SW Release #: B22
How to perform the test: In the OSS GUI Secondary Mirror window, click 'CloseBrake'. This will place the mirror back in 'standy' mode. This can be verified by looking at the main OSSGUI window under 'Left Secondary Mirror Status'. After this is done, click 'Init' on the Secondary Mirror window. The mirror should initialize normally by releasing the brake and homing. After the procedure is complete, the mirror should be in the 'ready' state.
Required Inputs:The Secondary Mirror is powered on (UMAC, that is)
Expected Outputs:Secondary Mirror re-initializes correctly
Results from running test:
21:22 MST on 02-Apr-2009: Pressed "Close Brakes" and then "Init" for M2 on OSSGUI. Works as advertised except that hexapod continues moving for more than 1 minute after the OSSGUI reports: "oss.side[0].secondary_mirror:[init] command.complete.
Estimated time needed to perform test: 5 minutes.
Passed/Failed: (Yes or No)
Yes

B23-Test 14 - Using the IRC without the IRS.

Test Description: The IRC does not require the IRS for commands that do not use the camera.
Test Responsible Party: Dave Thompson
Original SW Release #: B23
How to perform the test: Exercise IRC commands that do not use the camera and verify they work correctly when the IRS is not running.
Required Inputs: The IRS is NOT running.
Expected Outputs: Non camera IRC commands work correctly.
Results from running test:
Non-IRTC commands sent with irc from IRAF work correctly when IRS is not running. IRTC commands that need IRS correctly report that IRS is not running. Test performed after midnight on 02-Apr-2009 JMH Estimated time needed to perform test: 1 hr.
Passed/Failed: (Yes or No) *Yes*

B23-Test 15 - Ensure the MANUAL/AUTOMATIC modes for the HBS temperature setpoint work properly.

Test Description: Run the ECS and ECSGUI and direct attention to the HBS control tab.
Test Responsible Party: LBTO Astronomer or Engineer
Original SW Release #: B23
How to perform the test: In AUTOMATIC mode, the temperature setpoint will be updated automatically iff the PMCL or PMCR is running. In MANUAL mode, the user can set the setpoint, and it should not be overwritten by any other means.
Required Inputs: Run the PMCL and/or PMCR (as well as the ECS).
Expected Outputs: The HBS temperature setpoint current value known by the ECSPLC will be shown in the display entry.
Results from running test: Temperature control of the HBS. NOTE: The algorithm to update the setpoint value in automatic mode has not been changed (IssueTrak #2003); this will be done once there is closure on what should be done.
Manual mode for oil temperature control from ECS works as advertised. Tested 21:30 MST on 01-Apr-2009 JMH. Passed/Failed: (Yes or No) *Yes*

B23-Test 17 - LBC requested rotator trajectory information in SYSLOG

Test Description: Ensure the first (JD Timestamp, angle) pair for an LBC requested rotator trajectory is printed to the SYSLOG
Test Responsible Party: LBTO Astronomer
Original SW Release #: B23
How to perform the test: LBC must be the authorized instrument on the Left. LBC must then request a rotator trajectory via the IIF GetRotatorTrajectory command. While the LBC instrument will receive the trajectory as a response, the first (JD timestamp, angle) pair will also be written to the SYSLOG.
Required Inputs: GetRotatorTrajectory command
Expected Outputs: Data in the SYSLOG such as - Sample: 0 Time: 2454922.385420011356473 Theta: 2.377171193275075
Tester's Name: Michele and John H
Test Date:
Passed/Failed: PASSED
Actual Results from running test: Information found in the syslog.

B21-Test 3 - Evaluate the updatePointingReference functionality for coordinate types DETXY (pointing origin) and RADEC (on-sky).

NOTE: This test is a superset of B31 - Test 2.
Test Description: Use the updatePointingReference() function via the IRS/IIF interface for updating the base pointing origin coordinates (DETXY) and the base equatorial coordinates (RADEC). The update of each coordinate type must be done as its own invocation of updatePointingReference(). This can be done dome closed.

Test Responsible Party: Dave Thompson or John Hill
Original SW Release #: B21 (Full functional support via IRS/IIF in this build)
How to perform the test: Execute a Preset in at least tracking mode, and then perform pointing offsets specified in coordinate systems DETXY and RADEC.
Required Inputs: Specify an equatorial target for the Preset. Perform pointing offsets where one specifies offsets in the tangent plane in equatorial coordinates for RADEC pointing offsets. Perform pointing offsets where one specifies offsets of the pointing origin (DETXY) which are by default in the tangent plane.
Expected Outputs: Performing offsets in RADEC will cause the telescope to move to the new target. As such, the current target coordinates, pcs.side[side].pointingStatus.target.target_DEC.DECString (corresponding variable for RA), will contain the target+offset(corrected for sky) values. The base coordinates, pcs.side[side].pointingStatus.target.base_DEC.DECstring (ditto for RA), will retain the original Preset target coordinates until an updatePointingReference() is requested. At such time as the update is done, the base coordinates will be reset to the current target coordinates. The only manifestation of a change is in the reflective memory values. The telescope does not move. However, future offsets are performed with respect to the new base values.

The code performs the same functionality for offsets done to the pointing origin. The base pointing origin values, pcs.side[side].pointingStatus.pointingOrigin.base_x (corresponding value for y) will be updated to the current pointing origin values, pcs.side[side].pointingStatus.pointingOrigin.x (ditto for y) when the updatePointingReference() function is invoked on this coordinate type. The telescope does not move. Future offsets are performed with respect to the new base values.
Estimated time needed to perform test: 15 minutes.
Tester's Name:
Test Date:
Actual Results from running test:
Passed/Failed: Moved to completed state by Michele. The test has long since been successful for absorbing the DETXY (aka the pointing origin) position. There was a problem absorbing the RA/DEC coordinates which was tested and solved in item B31 - Test 2.

B18-Test 2 - Evaluate changes to MCSGUI

Test Description: The "Rotators" button in the MCSGUI should turn red if any of the indicators in the rotator Dialog or ANY of its sub-dialogs are red. Red indicates error. If none are red, then any yellow indicators in the rotator dialog or any of its sub-dialogs should cause the top level "rotator" button to be yellow.
Test Responsible Party: Telescope operator
Original SW Release #: B18
How to perform the test: A red indicator can be caused intentionally by turning the lock-out key. A yellow warning indicator can be caused by stopping the PCS from sending polynomials. Otherwise with no problems or warnings present, all the rotator dialogs should have no yellow or red indicators and the "rotators" button in the top level MCSGUI should have a normal gray background with black lettering.
Required Inputs:
Expected Outputs:
Results from running test:
Passed/Failed: (Yes or No) Yes for LFBG on 07-MAR-2009, JMH

B21-Test 4 - verify GCS is still working with updated GUI

Test Description: verify that a preset with GCS is still acquiring a guide star and the GUI visualization is operational. This test can be executed in simulation mode if dome has to be closed or on sky.
Test Responsible Party: Dave Thompson
Original SW Release #: B21
How to perform the test: (for closed dome) enable simulation mode of GCS by editing /lbt/tcs/current/etc/lbt.conf. If the dome is dark you can just GCS.starOverlay to true, which will get an AzCam image from the guide camera and overlays a star on that image. This is the best simulated test possible as it tests the external systems as well. If the dome is too bright and the acquisition image is saturated, set GCS.noAzCam to true, which will create a usable acquisition image. Set GCS.noTCS to true to avoid sending corrections to PSF or PCS. Save lbt.conf and restart GCSL. Call setGSsfp to move the probe on axis (w/o parameters) and set a guide star and then call closeLoop to get the GCS into guide mode. There a randomized failure in the acquisition to simulate that a a guide star was too faint. If this happens, just execute closeLoop again until the guide loop is closed (probability for faint GS is 0.2). The GUI should correctly visualize all steps of the acquisition process and visualization of the guide image in closed loop. Every 4-5 guide images there's an intentional lost GS image in the simulation to show how this condition is visualized.
(on sky) Don't modify lbt.conf or undo previous changes to (GCS.noAGW, .noTCS, .noAzCam and .starOverlay) and restart GCSL if you had to undo anything. Send a real preset through IIF and see if the guide loop can be locked and the steps of the process including the guide images are being correctly visualized in the GUI.
(on sky with star overlay) Follow the description for a closed dark dome.
Required Inputs: a real preset through IIF or setGSsfp/closeLoop commands in simulation mode
Expected Outputs: a closed guide loop if the system didn't simulate a faint GS problem by random (only available in simulation with GCS.noAzCam set)
Results from running test: a slightly moving guide star with a lost guide star every 4-5 images in simulation and a nice guiding performance in the on sky test
Estimated time needed to perform test: 30 minutes including changes to lbt.conf if provided parameters will be able to get a guide star on the camera (on sky)
Passed/Failed: (Yes or No). PASSED

B21-Test 5 - Verify small IIF Offsets do not collimate the mirrors

Test Description: verify that an offset that meets both the time requirement and move size requirement does not collimate the M1 or M2 mirrors. This test can be executed with the dome closed.
Test Responsible Party: John Hill
Original SW Release #: B21
How to perform the test: Send an IIF Offset command within two minutes since the last collimation for a move that is less than 2 arc-seconds. Neither M1 not M2 should be seen to collimate. The time of collimation is displayed on the PSF GUI mirror forms. Change the time and/or distance thresholds on the IIF GUI and check that if either is violated the mirrors are collimated.
Required Inputs: an IIF offset command.
Expected Outputs: M1 and M2 mirrors are/are not collimated based on the thresholds.
Results from running test:
Estimated time needed to perform test: 5 minutes.
Passed/Failed: (Yes or No) Yes 07-MAR-2009 JMH

B21-Test 6 - Verify M3 selector is not moved when M3 is collimated

Test Description: verify that the M3 selector (Rz) axis is not moved as part of a M3 collimation. This test can be executed with the dome closed.
Test Responsible Party: John Hill
Original SW Release #: B21
How to perform the test: Verify the "Enable Rz Collimation" display on the PSF GUI Tertiary Mirror form is set to "Disabled". Manually change the Rz Global Offset value on the same form. Press the Global Offsets "Update" button and verify that the Rz Platform Position does not change. Change the "Enable Rz Collilmation" setting to "Enabled" and press the "Collimate" button. Verify that the Rz Platform Position does change.
Required Inputs: M3 global offsets and "Enable Rz Collimation" setting.
Expected Outputs: M3 Rz is/is not collimated based on the "Enable Rz Collimation" setting.
Results from running test:
Estimated time needed to perform test: 5 minutes.
Passed/Failed: (Yes or No) Yes after 09-Mar-2009 TCS patches

B21-Test 7 - Verify RotateZ command

Test Description: verify that the M3 selector (Rz) axis is moved when an IIF RotateZ command is issued. This test can be executed with the dome closed.
Test Responsible Party: John Hill or Dave Thompson
Original SW Release #: B21
How to perform the test: Send a RotateZ command and verify the M3 Rz position has changed the correct amount on either the OSS or PSF GUIs.
Required Inputs: RotateZ command.
Expected Outputs: M3 Rz is moved.
Results from running test:
Estimated time needed to perform test: 5 minutes.
Passed/Failed: (Yes or No) Yes after 09-Mar-2009 TCS patches

B21-Test 8 - Verify a Preset command does not collimate M1 for horizon

Test Description: verify that the Preset command does not incorrectly calculate the "missing collimation" when the elevation is manually moved to horizon. This test should be done on sky.
Test Responsible Party: John Hill
Original SW Release #: B21
How to perform the test: Have the telescope tracking, guiding and wave front sensing at some reasonable position using an active mode Preset. Manually move the telescope to horizon. Send another active mode Preset and verify that the telescope is still in reasonable collimation.
Required Inputs: IIF Preset commands, guide stars.
Expected Outputs: M1 stays in reasonable collimation.
Results from running test:
Estimated time needed to perform test: 30 minutes.
Passed/Failed: (Yes or No) Yes 07-Mar-2009 JMH

B22-Test 10 - Ensure the patched pointing kernel is being used in conjunction with the computation of the rotator center.

Test Description: The rotator center equatorial coordinates are now being provided via the PCS data dictionary items. In implementing this new functionality, a bug was found, and subsequently patched, in the pointing kernel. This test is to ensure the functioning is executing properly on the mountain; this test can be done closed dome.
Test Responsible Party: LBTO Astronomer or Michele
Original SW Release #: B22
How to perform the test: Go to a target on the sky (RA=LST and DEC=00:00:00). Then execute a DETXY offset of X=3mm (0.33s) and Y=3m (5").
Required Inputs: As specified above.
Expected Outputs: rotCenter_RA.RAString=LST+00:00:00.33, rotCenter_DEC.DECString=-00:00:05.00. Please note the negative sign on the DEC.
Results from running test:
Note that the test as described is not possible with the dome closed, so this was a slightly modifed test with different coordinates that exist in the catalog, plus GCS in starOverlay mode.
21:37 pointto BS9122 GUIDE
22:08:40 offset 5 5 coord="DETXY"
which did: ircOffsetPointing 0. 5. 5. DETXY MOUNT true ABS left Preset Coords 07:30:34.500 +29:51:12.00
RotCenter 07:30:34.884 +29:51:06.99
IIF Achieved 07:30:35.214 +29:51:01.40
Passed/Failed: (Yes or No) Yes on 09-Mar-2009 JMH

B23-Test 17 - Verify that the all-on-source signal is working.

Test Description: verify that All-on-source works when LBC is authorized on the right.
Test Responsible Party: LBTO Astronomer or Engineer
Original SW Release #: B23
How to perform the test: The on source bits can be conveniently watched in the IIF GUI. Authorize "none" on the right side and Lucifer (or IRTC) on the left. Do a preset that causes a slew in AZ and EL and the rotator. Observe the "mount" and "Mount and Rotator" displays in the IIF GUI. Then authorize the LBC on the right and do another preset.
Required Inputs:
Expected Outputs: In both cases the "Mount" display should become "ready" when both AZ and EL are tracking (i.e. at the end of the preset). The "Mount and Rotators" display should become "ready" when the mount is ready and the rotator is also tracking.
Tester's Name: John Hill
Test Date: 26-Oct-2009 UT
Passed/Failed: Passed.
Actual Results from running test: The all-on-source indicator worked as expected. However, the test had an unpleasant side effect on the observations underway at the time. Changing the authorization on the Right side reset the the pointing model on the Left side and changed the telescope pointng. My understanding was that monocular PCS was Left-centric, so it didn't matter what you did to the right side. That seems not to be the case in this instance.

B23-Test 16 - Ensure asynchronous telemetry collection is performing.

Test Description: When the TCS is running, check the status of the telemetry store. Test Responsible Party: Tony Edgin
Original SW Release #: B23
How to perform the test: One the TCS is running, inspect the current set of telemetry sample streams. There should be several new ones from the PMCL, PMCR, PCS and ECS. The PCS and ECS streams should not be empty. Enable PMC telemetry collection. Samples should not be written to the PMC streams as well.
Required Inputs: Run the PMCL and/or PMCR, ECS and PCS.
Expected Outputs: New non-empty streams of telemetry in the data store.
Results from running test: Telemetry is being collected from all streams as expected.
Passed/Failed: (Yes or No) Yes on 31-Mar-2009 TLE

B23-Test 13 - Verify that the Tertiary Mirror in the OSS recognizes that a focal station is selected.

Test Description: After restarting the OSS, a preset should not fail due to the tertiary mirror not recognizing that a focal station is selected. As of now, the subsystem seems to be reflecting the current focal station correctly, but the OSS GUI is not.
Test Responsible Party: John Hill
Original SW Release #: B23
How to perform the test:Perform an authorize while the OSS is running, then stop and restart the OSS. Send a preset. The preset should not fail due to the tertiary mirror not being at a focal station. The OSS should recognize that the current focal station is set in the IIF. The OSSGUI should reflect that fact correctly. The see if it does, run the OSSGUI, open the tertiary miror window and look to see that the correct focal station is shown.
Required Inputs:The Tertiary Mirror is powered on, An 'authorize' has been run.
Expected Outputs:Tertiary mirror does not cause the preset to fail with a 'not at focal station' message.
Estimated time needed to perform test: 5 minutes.
Tester's Name: Paul Grenz
Test Date: 2009-10-09
Passed/Failed: PASSED
Actual Results from running test: The procedure was followed and the OSS reflected the actual focal station as set by the IIF. An authorization was performed, and the OSS GUI reflected the change as well.

B22-Test 1 - Evaluate running GCS as only process on a TCS server

NOTE: B22 - Test 1 may not be a valid test following the changes on the mtn with the deployment of the new servers. 
If issues are seen this test will be reopened at that time.
Test Description: Run GCS as the only process on lbtmu107 for n days and gather timing statistics using the TCSreport.bin tool. Than for the same number of days run GCS along with 1 or more (normal load distribution) subsystems on the same machine. Gather timing statistics again and compare results.
Test Responsible Party: TCS SW support person.
Original SW Release #: N/A but do it during B22 testing.
How to perform the test: Modify the lbt.conf file to make this happen. The GCS should not be started manually by modifying on the TCSGUI the subsystem for which GCS runs on. Stephen, Torsten or any other SW support person can assist in preparing lbt.conf for this test.
Required Inputs: N/A other than modifying lbt.conf.
Expected Outputs: Faster guide cycle time and more consistent cycle times without unexplaned lengthy guide cycle loop times.
Pass criteria: The GCS runs ok in either case. However, the cycle time of the guide loop is expected to get faster and more consistent. Fail criteria: No change is observed regarding the cycle time.
Expected Results from running test: The cycle time of the guide loop is expected to improve (i.e., get faster).
Tester's Name:
Test Date:
Passed/Failed:
Actual Results from running test:

B17-Test 1 - Evaluate the OffsetPointing functionality with move types both relative and absolute and modes DETXY (pointing origin) and RADEC (on-sky).

Test Description: Regression testing of the OffsetPointing with DETXY, and testing of the new functionality of relative offsets in RADEC.
Test Responsible Party: Dave Thompson
Original SW Release #: B17
How to perform the test: Repeat tests as described in IssueTrak 1899 (offset_tests.txt) and develop a similar plan for the relative offsets in RADEC.
Required Inputs:
Expected Outputs:
Tester's Name:
Test Date:
Actual Results from running test: This functionality has been tested closed dome (Dave) and on-sky by Team Lucifer. Was it evaluated to be accomplished successfully? Yes however...* - Dave tells me this test has been done successfully, but quantitative information is needed to verify performance.
Passed/Failed: Passed. Michele moved this test to "Completed" on 22 October 2009. Dave and Doug have discussed this test and determined "We agree that this test is complete and was passed successfully! You should remove it from the test list...immediately!!"

-- NormCushing - 25 Feb 2009
Topic revision: r19 - 25 Jul 2014, DouglasFisher
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