lsa overview

1

LSA Overview

06/11/2007

Grzegorz Kruk on behalf of the LSA Team

206/11/2007 LSA @ LHCCWG – Grzegorz Kruk

Agenda

•LSA scope•Key concepts •Architecture•Recent developments

306/11/2007 LSA @ LHCCWG – Grzegorz Kruk

Agenda


4

What is covered by LSA?• Optics

Information about all devices Machine layout Twiss parameters ..

• Settings generation Generation of initial settings based on optics

• Settings management & trim Management of values for all parameters Coherent modifications History of changes and rollback

• Hardware exploitation Equipment control Sending settings to the hardware

• Equipment & beam measurements Equipment monitoring Data concentrators e.g. BLM, BPM

LSA @ LHCCWG – Grzegorz Kruk06/11/2007

5

What is NOT covered by LSA?

•Logging•Fixed displays•Alarms•Software Interlocks•OASIS


6LHC Software Architecture – ICALEPCS 2007 – Grzegorz Kruk

Agenda


06/11/2007

7

Parameter• LSA parameter is

Settable or measurable entity on a device (real or virtual) e.g. LHCBEAM/QPH, MPLH.41994/K, MPLH4199/IREF, FESA fields

(properties)

• Parameters are organized in hierarchies

• Each hierarchy describes relations between parameters

Change of a parameter affects all its dependant parameters

• Roots usually physics parameters

e.g. momentum, tune, chromaticity,…

• Leaves hardware parameters e.g. reference current on power

converters

LSS4_EXT_BUMP/KNOB

MPLH.419994/K MPSH.42198/K

MPLH.419994/I MPSH.42198/I

MPLH4199/IREF MPSH4219/IREF


8

LHC Parameters Space


9

Context

• LSA Super Cycle Defines a series of cycles used to produce beams for known

clients Can be played repeatedly in a cycling machine

• LSA Cycle Defines a lifespan of a beam (from injection to extraction)

including beam out part It corresponds to a timing user e.g. CNGS_PDOT

SPS.USER.CNGS1

• LSA Beam Process Defines a specific process (injection, ramp, extraction...) in

the super cycle for a given accelerator or transfer line (LHC Ring, SPS Ring, TT10,...)


10

Context


11

Setting

• Value of a parameter for a given context (beam process)

It consists of target value and correction value Value of the setting is always a sum of target and correction

Value = Target + Correction

• Settings of all parameters are kept in the database

• Only settings of hardware parameters are sent to the equipment

Context

Parameter SettingTarget

Correction


12

Agenda



13

Architecture - 3-tier approach

• We wanted to deploy the system in 3 physical layers due to:

Central access to the database and to the hardware Central security Caching Reduced network traffic Reduced load on client consoles Scalability Ease of web development

• With a minimal cost of 3-tier architectures Complexity of programming Testing & debugging Deployment


GUI Applications

Business Logic

Hardware Database

Client tier

Server tier

14

Spring Framework• Open source Java enterprise application

framework Labeled as lightweight container Alternative to Enterprise Java Beans (EJB)

• All standard services provided Components orchestration, transactions, remoting, security,

…

• Seamless deployment in 2- and 3-tier mode

• Integration with many 3rd party products

• Very little effort to maintain the infrastructure


15

Applications

DatastoreDevices

JAPC CMW/RDA

JAPC

Spring JDBC

Data Access Object (DAO)

LSA Client API

LSA CORE(Optics, Settings Management, Trim,

Generation, Exploitation)

ParametersConcentration

JAPCCMW/RDA

JAPC RemoteServer - JMS LSA Client implementation

LSA Client APIJAPC API

Spring HTTP Remoting / ProxiesJAPC RemoteClient - JMS

Business Tier (Web Container)

Client Tier

CORBA IIOP

CORBA/IIOP JDBC

HTTPHTTPJMS


16

Architecture principles• Modular

with a clear API

• Layered GUI applications Business logic Database and hardware access

• Distributed Client side

Applications Server side

Business logicDatabase and hardware access


17

Client tier

Server tier

lsa-dbaccess

accsoft-commons-value

lsa-settings

lsa-settings-domain

lsa-exploitation-domain

japc

lsa-exploitation

lsa-trim

lsa-generation

lsa-client

lsa-optics-domain

lsa-app-selection

accsoft-steering-service

japc-ext-cmwrda

Outside projects

Core projects

Non core projects

spring External projects

ojdbc

spring.jarspring-mock.jar

ojdbc14.jarorai18n.jar

cmwOB.jarOBNaming.jarOBUtil.jarrda.jar

servlet servlet.jar

ehcacheehcache.jarcommons-logging.jarcommons-collection.jar

lsa-optics

Apps projectslsa-caching

lsa-fidel

accsoft-security-rba

japc-value

lsa-commons

accsoft-commons-util

japc-ext-remote

18

Data model•The system is highly data-driven

•Single model (database schema) for all machines

SPS, LEIR, LHC,…

•Result of several iterations and fruitful collaboration with CO/DM section

•Rationalized but nevertheless quite complex

~170 tables


19

Generic ApplicationsData model & business logic are common for all

accelerators we can reuse applications

SPSLHC


20

Agenda

•LSA scope •Key concepts •Architecture•Recent developments


21

BLM1 BLM2 BLM3 BLM4 BLM5 BLM6 BLM7 BLM8 BLM9 BLM10 BLM11 BLM99BLM1 BLM2 BLM3 BLM4 BLM5 BLM6 BLM7 BLM8 BLM9 BLM10 BLM11 BLM99BLM1 BLM2 BLM3 BLM4 BLM5 BLM6 BLM7 BLM8 BLM9 BLM10 BLM11 BLM99BLM1 BLM2 BLM3 BLM4 BLM5 BLM6 BLM7 BLM8 BLM9 BLM10 BLM11 BLM99BLM1 BLM2 BLM3 BLM4 BLM5 BLM6 BLM7 BLM8 BLM9 BLM10 BLM11 BLM99BLM1 BLM2 BLM3 BLM4 BLM5 BLM6 BLM7 BLM8 BLM9 BLM10 BLM11 BLM99BLM1 BLM2 BLM3 BLM4 BLM5 BLM6 BLM7 BLM8 BLM9 BLM10 BLM11 BLM99BLM1 BLM2 BLM3 BLM4 BLM5 BLM6 BLM7 BLM8 BLM9 BLM10 BLM11 BLM99

4000 Beam Loss Monitors

BLMsConcentration

Publication

OperatorConsole 1

OperatorConsole 2

LoggingFixed

DisplaysOperatorConsole 3

OperatorConsole 4

…

Broadcasting

Data Concentrators

22

LHC Timing

• All LHC processes (e.g. injection, ramp,...) will be synchronized and triggered using timing events

Sent by the LHC Timing System

• LSA provides service to manage these events

Creation, modification Loading to and unloading from

the Timing System

LSA

Timing module

LHC Timing System

Other modules


23

Security

•Role Based Access Control Created in the frame of th LHC at

FermiLab Software (LAFS) collaboration

•Management of Machine Critical Settings (MCS)


24

Methodical Accelerator Design (MAD-X)

• Simulation and validation of settings changes before applying them to the hardware

• Creation of KNOBS (e.g. bumps)• …


25

Testing• Currently we use unit testing (automated black-

box testing) for business logic and Data Access Objects

• GUI applications are tested manually Logic operating on the database development DB Hardware access usually on a real hardware (or test FGCs)

• Goal setup a testing hardware environment which could be used for a systematic testing (before each release)

Lab FGCs MUGEF (start to be used) – not necessary when MUGEF

replaced by FESA BI would be interesting to have …


lsa overview

Documents