Low ITF verification tests

1. VE.L.ITF.2.1 Basic Health VE:

TC.L.ITF.2.1.1 Power Modes:
All subsystems with hardware (MCCS/CBF): Support entering Low power (Standby) mode on power-on.
All subsystems: Support telescope ON/off/standby, assign/release resources and basic observation commands.
Vulcan: Provide Jupyter NB for the test case with some steps consisting of starting up the telescope, performing a mock observation and shutting down the telescope. This is covered by Vulcan's feature SP-4195

Note:

* Real-time signal displays show the signal processing products. AIV portal and SDP displays will be used.
* Standby mode (Low Power mode) is not supported by all the subsystems yet. No need for Standby mode yet, the test will just measure the power consumption as it is.
* TMC to support power consumption displays, this is not yet available and is a deviation for the AIV scope of work.

TC.L.ITF.2.1.5 Power Interruption:
Failsafe mode is not of priority for AA0.5 removed from the scope of AIV VE tests.

TC.L.ITF.2.1.8 Signal Displays:
What signal displays are currently present to be discussed with DP ART and MCCS and get feedback on them from the SCV team.
This could be covered partly by the AIV portal capability. (TBC)

2. VE.L.ITF.3.3 EMC/EMI VE:

TC.L.ITF.3.3.1 Radiative EMI/EMC:
Vulcan: Provide support to ITF team to write Jupyter NB for the test case with some steps consisting of starting up the telescope, performing a mock observation, monitoring the SPS devices, monitoring the metadata to check for instances of clipping and then finally shutting down the telescope.

Monitoring of metadata to check for instances of clipping - Is this available in MCCS? (TBC)

TC.L.ITF.3.3.2 Conductive RFI and Algorithmic artefacts:
Vulcan: Provide support to ITF team to write Jupyter NB for the test case with some steps consisting of starting up the telescope, performing a mock observation, monitoring the SPS devices, monitoring the metadata to check for instances of clipping and then finally shutting down the telescope.

Team Vulcan to create a LOW ticket for the EMC.EMI test cases.

3. VE.L.ITF.2.2 Telescope Management VE:

TC.L.ITF.2.2.1 Telescope Status Logs:
Check that the system status is logged in the EDA.
Details on specific parameters to be captured and verified are defined in the AIV Portal Specification page: https://confluence.skatelescope.org/display/TDT/LOW+AIV+Portal+Specification
This test case is to be run along with the https://skaoffice.jamacloud.com/perspective.req#/testCases/1004528?projectId=335
Vulcan feature SP-4196

TC.L.ITF.2.2.2 Observation Metadata:
Vulcan: Provide Jupyter NB for the test case with some steps consisting of starting up the telescope, performing a mock observation on a pair of target fields and then finally shutting down the telescope. Scripts should also include the Astronomical Data processing tools that examine the metadata associated with the visibility dataset.
This test can be done along with the TC.L.ITF.2.5.5 Station Beamforming.
TC.L.ITF.2.5.5 Station Beamforming:
Vulcan: Provide Jupyter NB for the test case with some steps consisting of starting up the telescope, performing a mock observation and then finally shutting down the telescope. Scripts should also include analysis of the data and also plotting the autocorrelation spectra.
Vulcan feature SP-4197

To be clarified:
*MCCS and TMC: * Provide means to exchange the Calibration Delays.

4. VE.L.ITF.2.3 Time & Frequency VE:

TC.L.ITF.2.3.3 Time Stamping Accuracy:
Out of scope for PI22
TBD - Test case still needs to be reviewed due to ECP 230134

5. VE.L.ITF.2.5 Station Signal Processing VE:

TC.L.ITF.2.5.1 Digitisation:
Vulcan: Provide Jupyter NB for the test case with some steps consisting of starting up the telescope, performing a mock observation and then finally shutting down the telescope. Scripts should also include analysis of the data and also plotting the data as visual amplitude vs time graph.
Vulcan Feature SP-4198

TC.L.ITF.2.5.2 Coarse Spectral Channelisation & TC.L.ITF.2.5.3 Coarse Channel Spectral leakage:
Vulcan: Provide Jupyter NB for the test case with some steps consisting of starting up the telescope, performing a mock observation and then finally shutting down the telescope. Scripts should also include analysis of the data and also plotting the data as visual amplitude vs time graph.
Test needs to be revisited if the Test Equipment can be optimised. Out of scope for PI22.

TC.L.ITF.2.5.4 Station Calibration Solution:
Vulcan: Provide Jupyter NB for the test case with some steps consisting of starting up the telescope, performing a mock observation and then finally shutting down the telescope.
Quite possibly there's more to this test than what's written in the test case. (TBC)
MCCS to provide calibration coefficients and possibly more. (TBC)
Cannot be run in PI22 due to SP-4051 is not ready.