!!+ Software Test Activity 2009

Here follows a few notes about the organization of LBT-AdOpt software tests.

You may also look at the related Gannt chart.

AO - Supervisor standalone tests

Engineering tests w/ low level interfaces

All lab tests are performed by using the low level interfaces which are part of the AO Supervisor software and which will be delivered at the telescope. The software tests for these components are thus included in the tests related to hardware subsystems.

  • Base functionalities: low level software interfaces for all the hardware controllers are tested
  • Extended tests: Coordination of various tasks from the low level GUIs is tested
led-blue Milestone: All AO System components are operable from the low level interfaces vie the related hardware controllers.

Standalone Tests w/ Arbitrators

  • WFS Arbitrator
    1. Verification of operational scripts driven by the FSM.
    2. Verification of the functionality of the FSM, including the error recovery procedures.
    3. Source acquisition with realistic seeing-limited fiber
Test activity target A: The WFS is operable from the WFS Control GUI through the WFS Arbitrator

  • AdSec Arbitrator
    1. Verification of operational scripts driven by the FSM.
    2. Verification of the functionality of the FSM, including the error recovery procedures.
Test activity target B: The AdSec is operable from the AdSec Control GUI through the AdSec Arbitrator.

  • Manual operation of WFS and AdSec Arbitrators
    1. System calibration (int. matrix acquisition etc).
    2. Diagnostic data recording (frames, slopes, commands from AdSec) @ 100 Hz (baseline)
    3. Diagnostic data recording (frames, slopes, commands from AdSec) @ 500 Hz (goal)
    4. System setup and AO loop closed.
Test activity target C: All AO System operations listed above can be performed by two skilled operators using WFS and AdSec Arbitrators GUIs.

  • AO Arbitrator
    All tests performed manually at the previous steps will be repeated from the AO Arbitrator GUI, by issuing the defined set of commands (for a list of commands see below in AOS section).
Test activity target D: The AO System can be operated from the AO Arbitrator GUI.

led-blue Milestone: targets A,B,C,D successfully completed.

AO Supervisor / AOS

This section refers to tests which are performed by using the AOS only (no need for other TCS subsystems running)

  • SIngle command tests from command line UI The following commands will be tested by TCS command calls implemented in a very simple client program. Corresponding actions in the AO Supervisor will be checked by various diagnostic tools. In this phase the functionality of AOS-GUI can also be tested.
    1. StartObs
    2. PresetFlat
    3. PresetAO
    4. AcquireRefAO
    5. CheckRefAO
    6. StartAO
    7. OffsetXY
    8. OffsetZ
    9. CorrectModes
    10. Stop
    11. Pause
    12. Resume
    13. Terminate

  • Offload modes mechanism
    1. Test with simulated modal error vector
led-blue Milestone: The AO System can be operated from the character oriented AOS test program

IIF/IRTC tests

  • IRTC standalone
    1. Image acquisition test
    2. Motor control and overall operation test

  • IIF/IRTC - TCS Installation general test
    Test the correct installation of required TCS subsystems
led-blue Milestone: the IRTC can be operated via TCS

AO Supervisor / AOS / TCS tests

  • Hexapod control. Uses the upgraded version of OSS to control the hexapod position from calibration procedures.

    led-blue Milestone: Calibration procedure can be performed controlling the hexapod via OSS.

  • Seeing Limited mode test. Uses the IRC to operate the IRTC in a simulated Seeing Limted mode

    led-blue Milestone: A simulated observation in seeing limited mode can be performed.

  • Full AO mode test Uses the IRC to operate the IRTC in a simulated full AO test.

    led-blue Milestone: A simulated observation in full AO mode can be performed.

  • Offload modes full test (tip-tilt only). Uses "forced" modal error vector to test the offload modes mechanism up to the hexapod motion

    led-blue Milestone: The mode offload mechanism is verified up to the hexapod motion.

AO ARBITRATOR TEST PLAN

AO Arbitrator command Issued from Expected result Test result
Power on Adsec Adopt Control GUI Adsec is powered on and initialized with default flat shape OK
Power on WFS Adopt Control GUI WFS is powered on and initialized with default IRTC setup. OK
Power off Adsec Adopt Control GUI Adsec mirror is put in "rest" position and safely powered of. OK
Power off WFS Adopt Control GUI WFS is powered off. OK
Set ENGINEERING mode Adopt Control GUI AOArbitrator in service state "ENGINEERING" OK
Set STANDALONE mode Adopt Control GUI AOArbitrator in service state "STANDALONE" OK
Start observation AOS GUI AOArbitrator in service state "OBSERVATION" and SeeingLmtd state. OK
Terminate observation AOS GUI AOArbitrator in service state "STANDALONE" OK
PresetFlatAO irc

Adsec selects the specified flat shape or, if no particular shape is specified, selects the default flat shape.
AOArbitrator in SeeingLmtd state

OK
PresetAO irc

Reference star information is used to do a preliminary selection of AO parameters
(reference star is loaded with irc SetReference command)
AO parameters are shown in the AOS GUI.
WFS is prepared for source acquisition. A setup is loaded dependent on instrumen
AOArbitrator in ReadyToAcquire state.

OK. PCS bug in focal plane coordinates.
CheckRefAO irc WFS checks reference star position in the technical camera and offsets are computed.
Offsets are shown in the AOS GUI
AOArbitrator remains in ReadyToAcquire state.
OK
AcquireRefAO irc WFS acquires the reference star using the acquisiton camera
AO parameters are refined using the measured magnitude and seeing
AOS GUI shows thenew AO parameters.
Adsec is prepared for AO loop.
AOArbitrator in RefAcquired state.
OK
ModifyAO irc AO parameters modified as specified in the command parameters.
WFS and Adsec are re-initialized as needed
AOS GUI shows the new AO parameters.
AOArbitrator in RefAcquired state.
 
StartAO irc AO loop is closed
AOArbitrator in LoopClosed state
OK
PauseAO irc AO loop is paused
AOArbitrator in LoopPaused state
OK
ResumeAO irc Light levels are checked in the WFS camera.
AO loop is resumed
AOArbitrator in LoopClosed state
OK
StopAO irc AO loop is opened.
AOArbitrator in SeeingLmtd state.
OK
OffsetXY irc WFS applies XY offset.
If in closed loop, PSF on technical camera and/or IRTC shows the same displacement.
AOArbitrator remains in current state (LoopClosed or LoopSuspended).
OK
OffsetZ irc

WFS applies Z offset
If in closed loop, PSF on technical camera and/or IRTC shows the same displacement.
AOArbitrator remains in current state ( LoopClosed or LoopSuspended).

OK



15 CorrectModes
Expected result:

Mode Offloading test


Check that:

1. Modes are computed by the AdSec software
2. AOS gives the necessary commands to the PCS
3. Hexapod is moved to correct for tip/tilt offsets.

ERROR CONDITIONS TO CHECK

1. AcquireRef command with the calibration lamp turned off (simulating cloudy conditions, or wrong PresetAO star coordinates). The following AcquireRef command must fail with an error of "Star not found".
2. ResumeAO command without light on the WFS camera. Command must fail and go back to PauseAO.
3. OffsetXY command in closed loop with too large offsets. Command must fail and not apply the offsets.
Topic revision: r13 - 27 Nov 2009, LucaFini
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