1. HWC Review – Sequencer Vito Baggiolini AB/CO, with the team: Carlos Castillo, Daniele Raffo, Roman Gorbonosov

2. HWC Review 12-Jul-07 2 Vito Baggiolini AB/CO Outline The sequencer today How to prepare for sector 45 A sequence editor Conclusions

3. HWC Review 12-Jul-07 3 Vito Baggiolini AB/CO

4. HWC Review 12-Jul-07 4 Vito Baggiolini AB/CO LHC Functional Layout DB (Oracle) LSA DB (Oracle) Set of Circuits Infos on Circuits PC operational data Test plan (tests done / to be done) Test outcome (success/failure) MTF DB (EDMS) Sequencer Journals, PM-Analysis (files) [ upload every 2h ] Circuit Info, PC Info [ changes copied once / day ] [ created after each test ] [ after each test ] [ before each test ] Context and Data Flow

5. HWC Review 12-Jul-07 5 Vito Baggiolini AB/CO Sequencer in Sector 78 Sequencer tool –Functionality as required –Continuously improved during HWC Sequences (HWC tests) –Progress (c.f. Markus’ talk) Sequencer used only for a minority of the tests. Why? –Experts wanted to do test the first time manually –Requirements on sequences still changing, not easy to modify sequences (CO specialist needed) –Is functionality missing in sequencer / sequences? What can we do to increase the use of the sequencer? How to best prepare for Sector 45?

6. HWC Review 12-Jul-07 6 Vito Baggiolini AB/CO

7. HWC Review 12-Jul-07 7 Vito Baggiolini AB/CO

8. HWC Review 12-Jul-07 8 Vito Baggiolini AB/CO Automation in Sequences In existing sequences –Manual interactions with other systems (“please ask expert to do/verify … ”)  direct interactions with equipment, where possible. –Simple analysis of measurements  not too complex, sequencer should drive tests, PMA should do analysis. –…–… New sequences –PC Config (c.f. David) –Your input needed On-the-fly sequences for unforeseen or ad-hoc tasks  Sequence Editor. …

9. HWC Review 12-Jul-07 9 Vito Baggiolini AB/CO How to Improve Efficiency Optimized scheduling of tests (?) –De-couple test execution from (off-line) data analysis by experts –Relax the conditions (succession of tests) enforced by test plan?  Policy? Rules? More flexibility in modifying/adapting sequences ?  Policy? Technical modifications in the sequences / sequencer (?) –More parallelization inside the sequencer? Possible, but makes sequences more complex  necessary? –Ergonomic improvements (we know of some)  more feedback, please. Better training/documentation?  User manual is on Wiki. Miscellaneous –Should sequencer write PC parameters tuned during tests back into LSA DB?

10. HWC Review 12-Jul-07 10 Vito Baggiolini AB/CO Many “small” improvements planned Better interactions with PMA to get data –More reliable –More than one PMA file; possibility to refuse files –Links to real PM data files in addition to images Automatic copy to MTF + verification of upload –First implementation done, to be tested Some ergonomic improvements, some bugfixes Small modifications in the existing sequences –Better error messages, better popup texts –Adjust / remove timeouts –Homogenize similar sequences

11. HWC Review 12-Jul-07 11 Vito Baggiolini AB/CO Sequence Editor A sequence editor instead of a “generic cycle editor” –More general purpose –we need to develop it anyway Purpose: –enable operators & HWC experts to create / modify sequences –no need for a CO specialist anymore Policy? –Who can change which sequences, and when? –What restrictions (pre-conditions) for running free sequences? After a given test in the HWC test plan? –…–…

12. HWC Review 12-Jul-07 12 Vito Baggiolini AB/CO Well defined requirements soon, please! Decisions needed –On policy (editing, flexibility in test plans, etc) –On priorities (what functionality to implement first)  Revive the regular SACEC meetings Responsibles –Sequences  Markus, Antonio –Sequencer tool  Vito Circuits and time needed for testing!

13. HWC Review 12-Jul-07 13 Vito Baggiolini AB/CO HWC Sequence Template Get test + circuit information from DB Connect to devices + prepare circuit [ free steps ] Switch circuit off Book keeping: Test outcome, send MTF data, etc. PLEP, sinus, state changes,… Waits, popup windows,… Slow/fast power aborts, discharge/quench requests,… Collect PMA data, … With values hard-coded or from LSA DB Initalization Finalization Actual Test

14. HWC Review 12-Jul-07 14 Vito Baggiolini AB/CO Sketch of Sequence Editor GUI Initialization Finalization PLEP to I_MIN_OP Popup “Please check X” Wait 200sec PLEP to 300A at 1A/s Slow Power Abort Wait for PMA data PLEP Wait SPA FPA Popup PMA Set stateWait state Sinus Comment Sequence:“Palette of commands”:

15. HWC Review 12-Jul-07 15 Vito Baggiolini AB/CO PLEP to I_MIN_OP Popup “Please check X” Wait 200sec PLEP to 300A at 1A/s Slow Power Abort Wait for PMA data Sequence Editor: add a PLEP Initalization Finalization Wait SPA FPA Popup PMA Set stateWait state Sinus Comment PLEP cursor

16. HWC Review 12-Jul-07 16 Vito Baggiolini AB/CO PLEP to I_MIN_OP Popup “Please check X” PLEP to 200A at 10A/s Wait 200sec PLEP to 300A at 5A/s Slow Power Abort Wait for PMA data Sketch of Sequence Editor Initialization Finalization Wait SPA FPA Popup PMA Set stateWait state Sinus Comment PLEP to 200A at 10A/s PLEP

17. HWC Review 12-Jul-07 17 Vito Baggiolini AB/CO Conclusion Globally the sequencer worked well… ….but was used only for minority of tests A 1 st version of a sequence editor will be ready for Sector 45 We are ready to implement other new functionality  please provide clear requirements soon!

18. HWC Review 12-Jul-07 18 Vito Baggiolini AB/CO

19. HWC Review 12-Jul-07 19 Vito Baggiolini AB/CO Parallelism One HWC team  one sequencer  several running sequences in parallel One running sequence  one circuit (now)  several circuits (possible, but more complex sequences)