Summary of Uplink Status

1. Summary of Uplink Status D. Teyssier, ESAC On behalf of the AIV/ILT team

2. Uplink tools: status of CUS scripts • Improved safety/configuration control: • CUS releases go through systematic test-harnesses • first level: purely software – check that scripts can run through in “all” (most) possible calls foreseen in the ILT (some 1200 calls tested) • second level: in combination with real ICU (i.e. OBS and MIB) and backends (parallel setup) on a subset of first level harness scripts – check acceptance of commands, data-rate, timing, real-time packet content (QLA), tuning procedures, etc. • Special content of CUS (LO deliveries: safety tables, LCU patches, cf T. Klein’s talk) checked through complete acceptance procedure – check correct upload to ICU and LCU Summary of Uplink status

3. Uplink tools: status of CUS scripts • Improved safety/configuration control: • Extensive use of parallel setup (ICU CFM2, FCU-TU5, FPU dummy, QM backends-H, QM-chopper, no LO yet). • exercise new TCs and modes (dry run) before use on FM, use of QLA, debug of OBS and MIB • populate database with representative sequences of BBIDs – “real” data for DP-tool preparation • efficient teaching for operators and backup personnel • CUS scripts and the multi-band/-frequency context: • Standard scripts now combined into tcl-based scripts • allow loop on parameters/frequencies • allow un-attended testing (typically at night) for long measurement sequences (e.g. stability) Summary of Uplink status

4. CUS scripts: completeness • CUS script readiness • As of TRR (mid-Aug 06), no scripts to handle LO operations, most tuning scripts missing, no AOT testing • As of today (see also appendix in hands-out) • LOU/LSU operation under control (both configuration tables and commanding scripts/procedures) • Magnet tuning extensively exercised • new (faster) diplexer scan TC implemented • Remaining open items • LO automatic tuning (to be closed this week) • AOT test scripts (procedures and scripts close to completion, to be delivered this week) • peak-up Summary of Uplink status

5. CUS scripts: beyond the ILT • CUS scripts: use for AOT CUS • Since this summer, the AOT CUS backend (resp. V. Ossenkopf) contains the instrument commands used in ILT • scripts used in common for ILT and AOT CUS maintained and configuration controlled under one single CVS directory • AOT CUS always uses most up-to-date knowledge of instrument commanding • Representative overheads for instrument configuration and tuning accounted in HSPOT time estimates • Similarly, ILT CUS handles backend readouts (data-rate) in the fashion planned for AOT: permanent validation Summary of Uplink status

6. CUS scripts: beyond the ILT • CUS scripts: re-use in future phases • Sub-set of current CUS scripts has already been turned into the reference scripts for IST • test procedure for IST close to completion (draft document exists, resp. B. Colleaudin) • Currently, assessment of additional time needed to recover from LO upgrade consequences in IST • Objective is to have scripts allowing quick instrument characterisation at any phase (incl. commissioning and routine) Summary of Uplink status

7. APPENDIX: FM-ILT CUS status Summary of Uplink status

8. APPENDIX: FM-ILT CUS status Summary of Uplink status

9. APPENDIX: FM-ILT CUS status Summary of Uplink status

10. APPENDIX: FM-ILT CUS status Summary of Uplink status

11. APPENDIX: FM-ILT CUS status Summary of Uplink status

12. APPENDIX: FM-ILT CUS status Summary of Uplink status