110 likes | 248 Vues
SLAC (LCLS) Application Plans. P. Chu for SLAC High-Level Application Team. Overview. Applications will include: Matlab Scripts XAL Apps SEAL – SLAC Eclipse Application Lab Java Eclipse RCP + plug-in. What’s inside a ‘SEAL’?. SEAL is a desktop application suite. SEAL Status.
E N D
SLAC (LCLS) Application Plans P. Chu for SLAC High-Level Application Team
Overview Applications will include: Matlab Scripts XAL Apps SEAL – SLAC Eclipse Application Lab Java Eclipse RCP + plug-in
What’s inside a ‘SEAL’? • SEAL is a desktop application suite
SEAL Status • Beyond “Hello World” stage (but not too far) • CM Log plug-in • XAL work • XAL as a plug-in • Database -> XAL optics file • XAL code separation • Textual display plug-in • XAL online model “application” • Accelerator optics selector plug-in • Online model run control plug-in • Orbit data display plug-in • Screen snapshot plug-in
Data Plotting • Many options: • XAL (Swing-based) plotting package in SWT_AWT bridge • Matlab w/ Java Builder • Other SWT or Swing based package, e.g. CSS? • Writing our own (some day)
Planned Applications/Components • Save/restore/configuration (XAL) • XAL online model for LCLS • AIDA web interface • Linac energy manager (LEM) • Correlation plot • Orbit display/fitting/correction • Matlab feedbacks • Start-to-end simulation (IMPACT + others?)
SEAL Eclipse Progress • Deployment methods • Eclipse IDE trim-down and a launch script to customize the “product” • A “product” built from Eclipse RCP wizard • Workspace management • A “default” workspace for accelerator op • Site-specific preferences saved in workspace • A product with many CSS plug-ins included
View selector Perspective selector SEAL Eclipse Progress (cont.) • “Large” or multiple view applications displayed as Perspective • Single view applications
Online Model Perspective “Launcher” for Other programs Model control Beam-line selector Orbit data plot
CSS within SEAL Data browser archives Data browser config
Summary ( or Confession) • Choosing Eclipse is a HARD decision. • Overall, very steep learning curve. • Maybe lack of good documentation for advanced (out of normal) stuff? • Still not very stable at some “core” level. • “Unconventional” (Java) approach makes it difficult to adopt quickly. • Extra efforts for multi-platform support and not always working. • But, we are not alone – CSS and other collaborations. • Bottom line • no other proven better way. • Eclipse is still pretty good (actually, excellent) for “normal” tasks. • Should have some apps ready for next commissioning run (Jan. 2008).