Loading...

Xporter

XML

Word

Printable

Details

Type: Feature
Priority: Not Assigned
Fix Version/s: PI10
Component/s: None
Labels:
- MCCS_firmware
- Team_MCCS

ARTs:

Obs Mgt & Controls
Acceptance criteria:
Hide

Define key concerns (interfaces, multiple TPMs, timing)

define and document systemic tests using AAVS code & hardware, involving off-line data processing

Schedule and execute initial tests using AAVS2 system on site
Show
Define key concerns (interfaces, multiple TPMs, timing) define and document systemic tests using AAVS code & hardware, involving off-line data processing Schedule and execute initial tests using AAVS2 system on site
Feature Points:
1
Initial Size:
1.5
WSJF:
26
Epic Link:
LFAA Development and MVP Integration
Agile Teams:

Team_MCCS
Due Sprint:
Sprint 4
Story Point Burn-up:
Overdue:
Outcomes:

Hide

1. Define key concerns (interfaces, multiple TPMs, timing)
-------------------------------------------------------------
The process of testing the TPM firmware began by obtaining time on the AAVS platform (MCCS-426) through which it was necessary to present a case for why the array was needed and what tests were to be run. The tests proposed were based upon the concerns which we wanted to understand and address.

2. Define and document systemic tests using AAVS code & hardware, involving off-line data processing
---------------------------------------------------------------------------------------------------------------
The testing that has been conducted on AAVS has been documented on: https://confluence.skatelescope.org/pages/viewpage.action?pageId=138646570. This confluence page also provides links to the software repositories where the commits of the code and configurations are held in Gitlab and Bitbucket.

Existing test scripts were reviewed (MCCS-430) in order to determine what, if anything, needed to be revised to conduct the tests on AAVS. Where necessary code was updated for use on AAVS2 to support the testing (MCCS-427).

3. Schedule and execute initial tests using AAVS2 system on site
---------------------------------------------------------------------
A comprehensive series of tests were conducted using AAVS and these are detailed in the below named Jira tickets.
MCCS-428 (Reconfigure AAVS2 network to support 40G interfaces...)
MCCS-429 (regression testing with new firmware)
MCCS-431 (Galaxy transit comparative test offline - realtime beamformer)

Show
1. Define key concerns (interfaces, multiple TPMs, timing) ------------------------------------------------------------- The process of testing the TPM firmware began by obtaining time on the AAVS platform (MCCS-426) through which it was necessary to present a case for why the array was needed and what tests were to be run. The tests proposed were based upon the concerns which we wanted to understand and address. 2. Define and document systemic tests using AAVS code & hardware, involving off-line data processing --------------------------------------------------------------------------------------------------------------- The testing that has been conducted on AAVS has been documented on: https://confluence.skatelescope.org/pages/viewpage.action?pageId=138646570 . This confluence page also provides links to the software repositories where the commits of the code and configurations are held in Gitlab and Bitbucket. Existing test scripts were reviewed (MCCS-430) in order to determine what, if anything, needed to be revised to conduct the tests on AAVS. Where necessary code was updated for use on AAVS2 to support the testing (MCCS-427). 3. Schedule and execute initial tests using AAVS2 system on site --------------------------------------------------------------------- A comprehensive series of tests were conducted using AAVS and these are detailed in the below named Jira tickets. MCCS-428 (Reconfigure AAVS2 network to support 40G interfaces...) MCCS-429 (regression testing with new firmware) MCCS-431 (Galaxy transit comparative test offline - realtime beamformer)
Resolved PI.Sprint:
10.5

Feature Checklist:

Stories Completed, Integrated, Outcomes Reviewed, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO

Demos:
- OMC_ART_SystemDemo_5
Requirement Status:

PI22 - UNCOVERED
Labels_MIRO:
MCCS_firmware Team_MCCS
Goals_MIRO:
SPO-1006

Description

Porting of the firmware code from TPM 1.2 to TPM 1.6 required modifications on the TPM 1.2 code in order to have an aligned code base between the two version. The modified code should be field tested on AAVS1 to establish a proven baseline from which further development can start.

Major difference between the new code and current AAVS1 code is the use of 40G interface instead of 4x10G split interfaces. The 40G should be verified with specific tests and as part of the nominal firmware in AAVS1 to confirm correct operation with a station of 16 TPMs.

To verify the new firmware functionality, tests should be done with the existing AAVS code, on the site system, using the commisioning observations done (by ICRAR/MarcinS.)

The tests to be carried out should be decided, these might include automatic tests (to be developed) and manual test through observations. Comparison data should be identified or captured.

The deployment should be agreed with ICRAR, including access to the hardware, schedule of observations and tests

Attachments

Issue Links

mentioned in: Page Loading...; Page Loading...; Page Loading...

Structure

Activity

People

Assignee:: Mohile, Vivek

Reporter:: Braddock, Ralph

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Feature Progress

Story Point Burn-up: (100.00%)

Feature Estimate: 1.0

	Issues	Story Points
To Do	0	0.0
In Progress	0	0.0
Complete	6	10.0
Total	6	10.0

Dates

Created:: 16/Feb/21 12:56 PM

Updated:: 15/Apr/24 9:49 AM

Resolved:: 24/May/21 5:55 AM

Initiate on-sky verification of firmware port by deployment on AAVS1