1. Development of the PAU 1 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Development of the Pattern Awareness Unit (PAU) for the LCLS Fast Feedback System Kukhee Kim for Fast Feedback Team Oct. 13, 2010 Controls Department SLAC National Accelerator Laboratory

2. Development of the PAU 2 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Contents Fast Feedback System Motivation of Pattern Aware Operation Pattern Awareness Unit Purpose Implementation Details PAU operation timeline: time slots Real Implementation in the LCLS Summary

3. Development of the PAU 3 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Fast Feedback System

4. Development of the PAU 4 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Fast Feedback (contd) Pattern Aware Control Pattern-based 120Hz operation Control Magnet and RF based on Timing Pattern Utilize FNET Isolated network: no competing network traffic, reliable data transport FCOM protocol: new efficient protocol for FNET, IP multicasting New fast feedback replaces MATLAB codes (slow and non-pattern aware feedback)

5. Development of the PAU 5 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Motivation (1) Increase beam rate 60Hz to 120Hz beam runs on same AC phase @ 60Hz two different AC phases @ 120Hz Other power line noise sources are expected LCLS-II Facility for Advanced Accelerator Experimental Test (FACET) any other which shares SLAC main power line will make additional variations Pattern a set of same variation on the power line reflected on the timing/event patterns pattern: a combination of time slots and beam operation information for entire SLAC facility

6. Development of the PAU 6 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Pattern and Beam characteristics Non Pattern Awareness (ALL patterns): Step Changes occurred on control parameters Pattern Awareness (for pattern D1) Smooth changes occurred Pattern Awareness (for pattern D2) Pattern Awareness (for pattern D3)

7. Development of the PAU 7 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Motivation (2) Non-Pattern Aware Feedback feedback loop has to compensate the step change between the pattern but, single feedback loop is not suitable for cure step raise and fall To compensate the variation between the patterns mobilize separated feedback loops for each different patterns each feedback loop does not experience step change beam characteristics in different patterns can be converge to a desired value smoothly Pattern Aware Operation for actuators: RF and Magnets To build generic Software Solution for the pattern required operation PAU can be utilize any pattern required application

8. Development of the PAU 8 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Schematic of Fast Feedback System Actuator (Pattern Awareness) Remark *3)

9. Development of the PAU 9 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Pattern Awareness Unit (PAU) Pattern Recognition tightly bind with the EVR wake up by the fiducial interrupt 360Hz rate pattern matching beam code and time slot 5 x 32bits exclusion mask and 5 x 32bits inclusion mask = total 320bits information Advanced Pattern Matching to implement set value to the actuator Current Pattern Matching for getting data from fast feedback controller Drive data pull function data pull from FCOM data slot Drive data push function execution local regulation loop for RF system *1) configuration type I send I&Q data to PACs (Pase Amplitude Controller) for RF system implement DAC value for Magnet system *2) configuration type II

10. Development of the PAU 10 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Configuration Type I (RF system) Remark *1)

11. Development of the PAU 11 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Configuration Type II (Magnet System) Remark *2)

12. Development of the PAU 12 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Processing Flow (1) Fiducial Thread wake up @360Hz fiducial interrupt proceed pattern matchings advance pattern matching for set value (to prepare next beam pulse) current pattern matching for getting data Queuing pattern matching information to the UltraHighPriority Callback Thread The queuing need to be delayed by the high-resolution timer to allow accurate adjustable time delay to waiting data from the fast feedback controller utilize the high-reolution timer on the CPU board: sub nano-second resolution

13. Development of the PAU 13 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Processing Flow (2) UltraHighPriority Callback Thread Waiting message from the fiducial thread/high resolution timer Proceed MUXes in the linked list MUX corresponds to a physical quantity: B_des (set value for magnet strength), P_des (phase), and A_des (amplitude) A PAU is shared by multiple MUXes which requires same pattern matchings. A PAU handles multiple MUXes (in the linked list) To save pattern matching for the individual quantity Linked list

14. Development of the PAU 14 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Processing Flow (3) UltraHighPriority Callback Thread (contd) Proceed the user pull function with the current pattern matching result Pull data from matched FCOM data slot: fast feedback mode *3) Schematic for fast feedback Pull data from matched data slot PV: static offset mode *4) Static offset mode Proceed the user push function with the advanced pattern matching result Push data into DAC: maget Execute the local regulation loop/Push data to the PAC via network: RF system Proceed the PAU diagnostics Measure execution time House keeping

15. Development of the PAU 15 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Time line for interlaced mode IQ conversion Queuing Sending Data Send data to PAC Fiducial function Woke-up by arriving packets, But, there no Push mechanism! Time Slot Pattern Local Feedback Pattern matching for current time slot And latch it for Diag. and for pull ACT Pattern matching for advanced time slot (Two Patterns 60Hz + 60Hz = 120Hz)

16. Development of the PAU 16 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Time slot operation with slow feedback when turned off fast feedback backward compatibility (non-pattern aware feedback + pattern aware operation) Static offset mode Actuator (Pattern Awareness) Master set value Operator Set Value Remark *4)

17. Development of the PAU 17 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Diagnostics Command line debugging tools various commands to show up: PAU internal variables, statistics, and measurements Diag. Function provides snap shot information for statistics and measurements via epics PVs A part of PAU diag. panelA part of MUX diag. panel

18. Development of the PAU 18 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Implementation in LCLS RF system PAU0: Laser loop in IN20 (1 station, 2 associations, 3 muxes) laser_mux_pdes_2856MHz laser_mux_pdes_119MHz PAU1: Feedback for IN20 (6 stations, 6 associations, 12 muxes) each station has 2 muxes: PDES and ADES gun, l0a, l0b, tcav0, l1s, l1x PAU2: Feedback for LI24 (7 stations, 9 associations, 18 muxes) Virtual (abstraction layer): l2 abstraction, l3 abstraction Physical stations: l2ref, tcav3, 24_1, 24_2, 24_3, s29, s30 Magnet system PAU0: Control correctors in LTU0 area (1 corrector, 1 mux) xcor_548 PAU1: Control correctors in LTU1 area (3 correctors, 3 muxes) xcor_488, ycor_493, ycor_593 laser_mux_ades Association #1 for 2845MHz representation Association #2 for 119Mhz representation

19. Development of the PAU 19 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Real-Time Performance Measurement PAU diagnostics provides measurement data about the performance Real-Time Performance from self diagnostic information Pattern matching in Fiducial: ISR delay: user pull function: user push function: self-diagnostics and house keeping: Example) RF PAU1 which has 12 muxes Pattern matching is proceeded at every fiducial 360Hz Waking up delay for the high-resolution timer including FCOM data getting/getting data from PV for each 12 muxes including RF local regulation loops + I&Q conversion + queuing data info sending queue to PAC Fiducial -2 Fiducial Fiducial 0 Beam Matched pattern to prepare next beam Fiducial Interval Settle time: worst case for magnet Real-Time Deadline Margin Adjustable delay by high-resolution timer PAU execution time + overhead

20. Development of the PAU 20 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Summary(1) Pattern aware operation has been test with the PAU successfully injection linac only waiting ready of hardware for downstream Back ward compatibility allow to use MATLAB (slow, non-pattern aware) feedback instead of the fast feedback Static offset mode Extensibility There is no limit to create PAUs and MUXes: implemented with linked list Only limit is number of high-resolution timer: first four PAUs will have the timer, after then do not have, thus always 0 delay for remaining PAUs.

21. Development of the PAU 21 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Summary (2) Real-time performance Considering priority order for each thread for the PAU: fiducial, UltraHigh callback, and FCOM/udpComm communication threads The PAU has been operated in the production last 3 months without any problem

22. Development of the PAU 22 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Appendix

23. Development of the PAU 23 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Timeline for non-interlaced mode IQ conversion Queuing Sending Data Send data to PAC Fiducial function Woke-up by arriving packets, But, there no Push mechanism! Time Slot Pattern Local Feedback Pattern matching for current time slot And latch it for Diag. and for pull ACT Pattern matching for advanced time slot (Single Pattern 120Hz)

24. Development of the PAU 24 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Functional Diagram & Interfaces Modular Design: User register functions

25. Development of the PAU 25 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Configuration Utilize iocsh command Utilize string identifier to recognize user defined functions and variables: epics registry Human readable No re-compile for re-configuration createPau("pau0", 2, "PAU for feedback") createPau("pau1", 2, "PAU for Laser") createMux("pau0", "ACCL:LI21:180:L1X_PDES", "l1xPhasePush", "l1xPhasePull", "L1X Phase") createMux("pau0", "ACCL:LI21:180:L1X_ADES", "l1xAmplPush", "l1xAmplPull", "L1X Amplitude") makeAssociation("ACCL:LI21:180:L1X_PDES", "ACCL:LI21:180:L1X_ADES") Name of PAU Pipeline index Description PAU nameMUX nameUser defined Data Push function User defined Data Pull function Description MUX name epicsRegisterFunction(l1xPhasePush); epicsRegisterFunction(l1xPhasePull); epicsRegisterFunction(l1xAmplPush); epicsRegisterFunction(l1xPhasePull); function(l1xPhasePush) function(l1xPhasePull) function(l1xAmplPush) function(l1xAmplPull) st.cmd Source Code DBD file *5) association

26. Development of the PAU 26 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 Configuration (contd) MUX for Amplitude MUX for Phase Local Feedback Loop for Amplitude Local Feedback Loop for Phase Conversion for AP2IQ I Q Association Remark *5) Association Processing requires two physical quantities Conversion from Phase&Amplitude to I&Q Need to make relation between two MUXes: phase and amplitude Syntax: makeAssociation(mux name 1, mux name 2)

27. Development of the PAU 27 Controls Kukhee Kim Fall 2010 EPICS Collaboration Meeting Oct 13, 2010 EVR Fiducial function & APIs PAU/Mux Object & APIs Registry for Data Pull Registry for Data Push Default Data Pull (FCOM) User defined Data Pull UdpComm RF Local Feedback AP2IQ conversion Send Data via IP multicasting User defined Data Push FCOM interface UdpComm (UdpCommListener)