SLAC Controls Evolution - DESY - MPY-Group

Recommendations

Info

Summary We hope to base all of our hardware on developments from the community or those commercially available. Integration with the existing SLC system is a critical step to allow <strong>SLAC</strong> operators to use the existing tools while we are adopting and modifying replacements. We are using standard EPICS tools for core development and engineering interfaces. We are adopting all we can from the community and we will use our resources to extend them as we can. January 2005 Ron Chestnut ronc@slac.stanford.edu
LCLS Software Tasks – Standardize/Acquire Data Archiving to support all phases of the project Operator Display Tools / Synoptic, Plots, Waveform, Image Alarm Management Electronic Log High Level Application Support: Matlab, XAL, Python Control System Configuration Tools Relational Database Management in all project aspects January 2005 Ron Chestnut ronc@slac.stanford.edu
Page 1 and 2: Outline January 2005 SLAC Controls
Page 3 and 4: The SLC Applications Model based Ad
Page 5 and 6: The PEP-II Upgrade Project started
Page 7 and 8: PEP-II e + e - Collider January 200
Page 9 and 10: What is NOT in EPICS for PEP-II Sta
Page 11 and 12: Current EPICS Integration EPICS has
Page 13 and 14: Linac Coherent Light Source Project
Page 15 and 16: The World’s First Hard X-ray X La
Page 17 and 18: Upstream linac RG Gun L0 Ti:Sa lase
Page 19 and 20: Personnel - Resources Ctl. Elec. En
Page 21 and 22: LCLS contributing labs Injector and
Page 23 and 24: LCLS Control System Goals Provide a
Page 25 and 26: Global Hardware - Timing Boards 476
Page 27 and 28: Functional Requirements Maximum Lin
Page 29 and 30: Three kinds of front-end support Tr
Page 31 and 32: Client Tools Display Manager EDM Ar
Page 33: Hardware Direction - Buy/Steal/Make
Page 37: Conclusion LCLS is providing the op

SLAC Controls Evolution - DESY - MPY-Group

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?