1 / 20

Test infrastructure 2

Test infrastructure 2. D. Teyssier, ESAC On behalf of the AIV/ILT team. Overview. CUS script and uplink parameters - status Test procedures - status Test operations Test logging Analysis teams Communication and reporting during FM-ILT. FM-ILT CUS. Uplink for FM ILT.

brandi
Télécharger la présentation

Test infrastructure 2

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Test infrastructure 2 D. Teyssier, ESAC On behalf of the AIV/ILT team

  2. Overview • CUS script and uplink parameters - status • Test procedures - status • Test operations • Test logging • Analysis teams • Communication and reporting during FM-ILT Test infrastructure 2

  3. FM-ILT CUS Uplink for FM ILT • All tests coded in CUS, in the same fashion as the AOTs • CUS gets its elementary instrument commands from the MIB • Instead of Observing modes, ILT CUS consists of Test modes • Test mode sequences reflect the FM-ILT detailed test plan, and are defined in agreement with calibration use case requirement (when applicable) • Use of configuration tables (equivalent of AOT’s calibration tables). Common approach with AOT tables • Re-use of ILT CUS for AOTs (instrument configuration, tuning, load calibration, etc) and for IST at Astrium. IST codes are validated in ILT • CUS scripts include an internal check of effective packet/data-rate • Exception: beam measurements not done via CUS – use of dedicated software via SCOE Test infrastructure 2

  4. FM-ILT CUS CUS inputs and CUS script description • Test-mode inputs in agreement with HSPOT front-end • Band • LO frequency • HRS resolution mode • Integration time • Other inputs specific to test-mode • CUS script content • The commands contained in a given CUS scripts are described in the “CUS scripts for HIFI FM tests” document • All uplink parameters associated to the scripts is also available and described in the “HIFI Uplink parameters for ILT and AOT” document. Test infrastructure 2

  5. FM-ILT CUS: status Test infrastructure 2

  6. FM-ILT CUS: status Test infrastructure 2

  7. FM-ILT CUS: status Test infrastructure 2

  8. FM-ILT CUS: status Test infrastructure 2

  9. FM-ILT CUS: status Test infrastructure 2

  10. FM-ILT test procedures Test sequence definition • The detailed test plan is translated into a detailed test sequence making use of CUS script calls with adequate input parameters (“HIFI ILT Integration and Functional Test Procedures”) • This document is the operational reference for the operator sitting at the test console. • It contains the list of monitoring applications (HK, RTA, QLA, etc) to be started up for a given test • It contains the list of parameters/results to check for the success/failure verdict and the go/no-go criteria • It indicates the possible inter-dependence of tests within a sequence • It is used as on-line test log for future reporting • This document is however expected to evolve as we update/upgrade the sequences. It will be the main input for IST and PV procedures Test infrastructure 2

  11. FM-ILT test procedures Test sequence example HK screens to be used QLA to be used CUS scripts Pass/fail criteria Test infrastructure 2

  12. FM-ILT test procedure: status Test infrastructure 2

  13. FM-ILT test procedure: status Test infrastructure 2

  14. FM-ILT test procedure: status Test infrastructure 2

  15. FM-ILT test: communication Test logging and information sharing • Beside the on-line log on the test sequence, a web-based electronic log is available and filled in by the operators and the test engineers. It is visible from the outer world • In addition, a Wiki page has been set up in order to: • Gather all common information on the test campaign, setup, uplink and analysis scripts, etc • Offer a forum for interactive discussion • Offer a repository for test results (test status, comments, plots, etc) • It uses the “wiki” concepts, i.e. everybody that’s registered and logged on can contribute on any page. • The Wiki pages also host the dedicated test team pages where more specific information can be shared between a test engineer (team leader) and the scientists forming his/her team. • It can be used to manage the tasks of a team (e.g. assign a list of ObsIDs to be analysed by a given person) and ensure complete visibility of the analysis status Test infrastructure 2

  16. FM-ILT test: communication Example of electronic log entry Test infrastructure 2

  17. FM-ILT test: communication Analysis “topical” teams Test infrastructure 2

  18. FM-ILT test: communication Example of Wiki pages: front page Test infrastructure 2

  19. FM-ILT test: communication Example of Wiki pages: Test overview Test infrastructure 2

  20. FM-ILT test: communication Test reports and inputs to other teams • Rudimentary reports will be built up on-line in the forms of the Wiki inputs • The test engineers should produce regular reports digesting the results of sub- or complete test campaign • The outputs of some teams are input to some others and should be fed into e.g. configuration tables for the uplink (e.g. frequency-dependent diplexer settings) in an organized manner. The CUS writer will monitor progress and new inputs from the Wiki entries. • Improvised and regular meetings/telecon will occur often Test infrastructure 2

More Related