TCS Software Tests still needing to be performed

Tests already performed and considered Passed.

Test Description Template

B## (use the build number) - Test ## (start with test # 1 and increment for each test for the specific build) - Test Description.

Test Description: description.
- sub description
- sub description
Test Responsible Party: SW developer's name and/or Support Astronomer
Original SW Release #: B##
Note: helpful information
How to perform the test:
Required Inputs:
Expected Outputs:
Tester's Name:
Test Date:
Passed/Failed:
Actual Results from running test:

BP3 - Test 1 - Specification of an Offset in the PresetTelescope command - MONOCULAR mode.

Test Description: The specification of an Offset (RA/Dec or DETXY) is now supported by the PresetTelescope command. The PCS will perform a full acquisition of the main target in order to set properly all PCS/pointing kernel functionality. Once the target is achieved, the PCS will then continue and perform the offset. Since this command does not allow the user to set the MoveType (ABS or REL) or an angle for the Offset, the Offset is done in an ABSOLUTE manner with an angle of zero.
Test Responsible Party: John Hill
Original SW Release #: BP3
Note: The "achieved coordinates" are currently not necessarily reported correctly for an offset done in DETXY. It is still desired to know if the functionality portion of the command works properly.
How to perform the test: Create an OB which specifies both a Target and an Offset - MONOCULAR mode. This test should be done in both RADec and DETXY.
Required Inputs: Specification of a Target and then an Offset.
Expected Outputs: Acquisition of the object at the offset location and all data dictionary values (mapping to FITS keywords) set properly.
Tester's Name:
Test Date:
Passed/Failed:
Actual Results from running test:

BP3 - Test 2 - Specification of a HotSpot in the PresetTelescope command - MONOCULAR mode.

Test Description: The specification of a HotSpot is now supported by the PresetTelescope command. The PCS will perform a full acquisition of the main target in order to set properly all PCS/pointing kernel functionality. Instead of using the default HotSpot (aka Pointing Origin) values documented in the PCSInstrument.conf file (typically 0.0,0.0), the PCS will use the HotSpot values provided as part of the PresetTelescope command.
Test Responsible Party: John Hill
Original SW Release #: BP3
Note: The "achieved coordinates" are currently not reported correctly for non-zero pointing origin values.
How to perform the test: Create an OB which specifies both a Target and a HotSpot - MONOCULAR mode.
Required Inputs: Specification of a Target and a HotSpot.
Expected Outputs: Acquisition of the target such that the light from the target lands on the specified HotSpot location in the detector and all data dictionary values (mapping to FITS keywords) set properly.
Tester's Name:
Test Date:
Passed/Failed:
Actual Results from running test:

BP3 - Test 3 - Specification of an Offset in the PresetTelescope command - BINOCULAR mode, side=BOTH.

Test Description: The specification of an Offset (RA/Dec or DETXY) is now supported by the PresetTelescope command. The PCS will perform a full acquisition of the main target in order to set properly all PCS/pointing kernel functionality. Once the target is achieved, the PCS will then continue to acquire the Offset object. Since this command does not allow the user to set the MoveType (ABS or REL) or an angle for the Offset, the Offset is done in an ABSOLUTE manner with an angle of zero.
Test Responsible Party: John Hill
Original SW Release #: BP3
Note: For the BINOCULAR test, if the same pointing model is used for both sides of the telescope, the achieved coordinates will be the same on both telescope sides. The "achieved coordinates" are currently not necessarily reported correctly for an offset done in DETXY. It is still desired to know if the functionality portion of the command works properly.
How to perform the test: Create an OB which specifies both a Target and an Offset - BINOCULAR mode, side=BOTH. This test should be done in both RADec and DETXY.
Required Inputs: Specification of a Target and then an Offset.
Expected Outputs: Acquisition of the object at the offset location and all data dictionary values (mapping to FITS keywords) set properly.
Tester's Name:
Test Date:
Passed/Failed:
Actual Results from running test:

BP3 - Test 4 - Issue a Synchronized PresetTelescope command in Track mode.

Test Description: Since a synchronized PresetTelescope has both sides of the telescope "unlocked", it would be good to test this binocular functionality (even though the tip/tilts are not being generated at this time for the optical elements) to gain familiarity with the functionality (new BinocularControl command, means to abort the synchronization of the command, and see the new events issued depending upon the circumstances).
Test Responsible Party: John Hill or Support Astronomer
Original SW Release #: BP3
How to perform the test: Generate an OB which includes the BinocularControl command with the Preset synchronization request. The OB needs to include a "left" target and a "right" target Preset. Attempt to perform a "successful" Synchronized Preset initially. As a follow-on, deliberately issue the command with targets in the WARNING and/or ERROR regimes. These regimes are defined in the lbt.conf file and are currently set to: WARNING=+/-5" and ERROR=+/-20" from the compromise mount point.
Required Inputs: Specification of the synchronization, left and right targets.
Expected Outputs: Acquisition of the requested targets.
Tester's Name:
Test Date:
Passed/Failed:
Actual Results from running test:

BP3 - Test 5 - Issue a Synchronized OffsetPointing (RADec) command.

Test Description: Since a synchronized OffsetPointing has both sides of the telescope "unlocked", it would be good to test this binocular functionality (even though the tip/tilts are not being generated at this time for the optical elements) to gain familiarity with the functionality (new BinocularControl command, means to abort the synchronization of the command, and see the new events issued depending upon the circumstances).
Test Responsible Party: John Hill or Support Astronomer
Original SW Release #: BP3
How to perform the test: Generate an OB which includes the BinocularControl command with the Offset (RADec) synchronization request. The OB needs to include a "left" and a "right" offset. Attempt to perform a "successful" Synchronized Offset initially. As a follow-on, deliberately issue the command with offsets in the WARNING and/or ERROR regimes. These regimes are defined in the lbt.conf file and are currently set to: WARNING=+/-5" and ERROR=+/-20" from the compromise mount point.
Required Inputs: Specification of the synchronization, left and right offsets.
Expected Outputs: Acquisition of the requested offsets.
Tester's Name:
Test Date:
Passed/Failed:
Actual Results from running test:

BP3 - Test 6 - Issue a Synchronized PresetTelescope command in Guide mode.

Test Description: Since a synchronized PresetTelescope has both sides of the telescope "unlocked", it would be good to test this binocular functionality (even though the tip/tilts are not being generated at this time for the optical elements) to gain familiarity with the functionality (new BinocularControl command, means to abort the synchronization of the command, and see the new events issued depending upon the circumstances). Further, the pointing correction (rectification of the predicted versus the measured guide star location) is done in a synchronized manner by default. The PCS will wait until it has received the pointing correction from each GCS (L and R) before proceeding with the process.
Test Responsible Party: John Hill or Support Astronomer
Original SW Release #: BP3
How to perform the test: Generate an OB which includes the BinocularControl command with the Preset synchronization request. The OB needs to include a "left" target and a "right" target Preset. Attempt to perform a "successful" Synchronized Preset initially. As a follow-on, deliberately issue the command with targets in the WARNING and/or ERROR regimes. These regimes are defined in the lbt.conf file and are currently set to: WARNING=+/-5" and ERROR=+/-20" from the compromise mount point.
Required Inputs: Specification of the synchronization, left and right targets.
Expected Outputs: Acquisition of the requested targets and guide star(s).
Tester's Name:
Test Date:
Passed/Failed:
Actual Results from running test:

BP11 - Test 1 - Tertiary Shifted Coordinate System test

Test Description: The tertiary mirror selector has a configuration-level shift which can be applied to its coordinate system. This test ensures that the shift is applied correctly, and that the physical focal station positions are unchanged.
Test Responsible Party: Paul Grenz, Andrew Rakich, John Hill
Original SW Release #: BP11
How to perform the test: Run the OSS and OSS GUI 1) Leaving the telescope tracking, stop the OSS swap the configuration file "OSS.conf" for "OSS.conf.old" by exchanging thier names. 2) Restart the OSS and move the selector to a focal station which can image object in tracking mode. 3) Stop the OSS and swap the config files back. 4) Restart The OSS and move to the same focal station.
Required Inputs: Telescope time., Running the telescope in tracking mode fixed on a celestial object.
Expected Outputs: Celestial object should not move when the config files are swapped, even though the positions that the tertiary is reporting are different.
Tester's Name: Paul Grenz and J. Hill
Test Date: 20110516
Passed/Failed: Failed initially but passed after we reversed the signs of the offsets. Offset is ~-17 deg on both sides.
Actual Results from running test: Found some other bugs in OSS along the way.

BP11 - Test 2 - RA/Dec Achieved Coordinates when performing a DETXY offset test

Test Description: When a DETXY offset is performed, the RA/Dec achieved coordinates should not change as the target on the sky has not changed; However, the location where the light from the target is imaged on the focal does change. Ensure the light ends up in the focal plane where requested without changing the RA/Dec values.
Test Responsible Party: Astronomer
Original SW Release #: BP11
How to perform the test: Run the PCS and PCSGUI
1) Perform a Preset in Guide mode.
2) Perform a DETXY Offset to a desired location in the focal plane.
Required Inputs: SKY
Expected Outputs: Make sure the light is imaged in the proper location, and the RA/Dec achieved coordinates displayed on the PCSGUI do not change (there may be a flicker) from the Preset values.
Tester's Name: J. Hill
Test Date: 20110516 06:30UT
Passed/Failed: Passed
Actual Results from running test: Error is OK, star moves as expected.

BP11 - Test 3 - RA/Dec Achieved Coordinates when Adjusting Pointing Origin test

Test Description: When the pointing origin is changed to something other than (0,0), the RA/Dec achieved coordinates should not change as the target on the sky has not changed; However, the location where the light from the target is imaged on the focal does change. Ensure the light ends up in the focal plane where requested without changing the RA/Dec values.
Test Responsible Party: Astronomer
Original SW Release #: BP11
How to perform the test: Run the PCS and PCSGUI
1) Perform a Preset in Track or Guide mode with a Hotspot (Pointing Origin) not equal to (0,0). Rather the hotspot should be set for a specified location in the focal plane.
Required Inputs: SKY
Expected Outputs: Make sure the light is imaged in the proper location, and the RA/Dec achieved coordinates displayed on the PCSGUI do not change (there may be a flicker) from the Preset values.
Tester's Name: J. Hill
Test Date: 20110515 06:30 UT
Passed/Failed: Passed
Actual Results from running test: Error is OK, star moves as expected.