A modular architecture for high level applications

1
A modular architecturefor high level applications
GUOBAO SHEN May 1st, 2009 EPICS collaboration
meeting, Vancouver
2
Outline

• From accelerator device to beam
• HLA status at NSLS-II
• Modular architecture of HLA
• Narrow API interface
• Online simulation server prototype
• Applications of IRMIS lattice database
• Conclusion

3
From accelerator device to beam

• Accelerator device control
• Control target accelerator hardware device
• Standard model distributed intelligent
  controllers, network, servers
• Software framework EPICS, TANGO,

4
From accelerator device to beam

• Accelerator beam control
• Control target accelerator beam, products of
  accelerator hardware
• Model based controls Tracy, Elegant, XAL, MAD,
• Software framework MMLT, SDDS, XAL,

5
From accelerator device to beam

• HLA environment
• A software platform
• Beam manipulation
• Data processing, data archiving/analysis
• Machine save/restore
• Database related
• Problems of most existing PA environments
• Tie together functions through data or file
  structures
• Difficult to share applications between each
  other
• Duplicated development

6
(No Transcript)
7
(No Transcript)
8
(No Transcript)
9
(No Transcript)
10
Narrow API interface

• Model based control
• Key component of HLA
• Online Model/Simulator
• Key component for model based control
• Online simulation server
• Indispensable for a modular HLA environment
• Generic simulation server is our goal
• Support multi-simulators
• Candidates Tracy-3 Elegant
• An API interface is needed to wrap those
  simulators
• Generic, narrow

11
Narrow API interface

• MMLT is selected
• Closer to our modular architecture
• Rich available applications
• Used by many facilities for many years

12
Narrow API interface

• MMLT Enhancement
• Multi-simulators support

13
Narrow API interface

• MMLT Enhancement
• Directory structure

MMLT ROOT
Applications
EPICS CA
Links
Machine
MML
Tracy (.so)?
Elegant(.so)?
AT
AT
Tracy
Elegant
NSLS2
S.R.
S.R.
14
Narrow API interface

• Application
• Beta plotting using plotfamily
• 
  (b) against AT
• (a) against Tracy-3

15
Narrow API interface

• Application (cont)
• Chromaticity measurement
• (a) against Tracy-3
  (b) against AT

16
Narrow API interface

• Application (cont)
• Beam based alignment
• against AT
  against Tracy-3

X
Y
X
Y
17
(No Transcript)
18
Online simulation server prototype

• Plan for updating simulation server
• A structured data is needed
• Using PVdata structure
• javaIOC will be used for the prototype
• A support should be developed
• Communication protocol
• CA-v3/CA-v4
• Fetching lattice information from IRMIS instead
  of local file
• Dynamic model change

See Marty Kraimers Talk for more informations
about PVdata and javaIOC
19
Applications of IRMIS lattice database

• Use IRMIS for lattice management

See Don Dohans Talk for more information about
IRMIS
20
Applications of IRMIS lattice database

• Fetching lattice information
• Bare lattice
• Installation, and engineering alignment/BBA error
• Machine snapshot

21
Conclusion

• Same architecture for device control and beam
  control
• Device control modular and distributed
  environment
• Beam control need a similar environment
• A modular HLA environment
• Loose coupling, pluggable, distributed, and
  therefore reusable
• Design and prototype of a narrow API interface
• Enhanced MMLT toolkit to support Tracy-3
  Elegant
• Applications tested against Tracy-3 without
  modification
• Prototype of online simulation server
• Plan to use PVdata and CA-v4
• IRMIS related applications