340 likes | 348 Views
LSA Core overview. 6 / 11 / 200 7 Wojciech Śliwiński (AB-CO-AP) on behalf of LSA team. Agenda. LSA – operations view LHC driven extensions. Operations data flow. Generation – initial Settings. Parameters definition. Trim – Settings modification. Optics import.
E N D
LSA Core overview 6 / 11 / 2007 Wojciech Śliwiński (AB-CO-AP) on behalf of LSA team
Agenda • LSA – operations view • LHC driven extensions LSA Core @ LHCCWG – Wojciech Śliwiński
Operations data flow Generation – initial Settings Parameters definition Trim – Settings modification Optics import Exploitation – drive Settings Devices DB LSA Core @ LHCCWG – Wojciech Śliwiński
Optics • All optics in the LSA database • Layout, Twiss, Strengths • Imported from few sources • Layout database • MAD • Data model common for all accelerators (LHC, SPS, LEIR) • Information about all Devices (FESA & non-FESA) LSA Core @ LHCCWG – Wojciech Śliwiński
Optics Display LSA Core @ LHCCWG – Wojciech Śliwiński
Parameters definition • Manual from SQL scripts • e.g. Power Converter currents • Imported from MAD (Knobs - physics parameters) • e.g. Momentum, Tune, Chromaticity • Using GUI application for FESA properties • e.g. BI settings, Collimators LSA Core @ LHCCWG – Wojciech Śliwiński
Settings (1) • Setting – function/scalar value of a parameter for a given context • Operational settingsfor all parameters (physics to hardware) • Settings of external parameters (e.g. current) are the ones sent to equipment • Settings can be retrieved,trimmed and sent to equipment LSA Core @ LHCCWG – Wojciech Śliwiński
Settings (2) targetValue Parameter Setting correctionValue Context • Setting holds a target and a correction value • Target values are calculated using the optics(Generation) • Correction values are entered by an operator or calculatedby a tool (SPS Autotrim) LSA Core @ LHCCWG – Wojciech Śliwiński
Setting Viewer LSA Core @ LHCCWG – Wojciech Śliwiński
Settings (3) • Modify / Reload / Rollback / Copy functionality + history of all changes • General access point to all devices/properties (FESA, MUGEF, FGC, GM) • Context independent (not multiplexed) parameters(e.g. thresholds) have uniquesetting LSA Core @ LHCCWG – Wojciech Śliwiński
Settings (4) • Categories: • Functions(magnet strength, PC current) • Discrete(constant value per context, thresholds) • Includes also settings for FESA devices • Actual (function snapshot at given moment - LHC) • Critical(protected settings for critical devices) LSA Core @ LHCCWG – Wojciech Śliwiński
Machine Critical Settings (MCS) • Aimed for the most critical and potentiallydangerous devices/settings • Complementary to the RBAC • Second layer of security • Based on a digital signature scheme • To ensure data integrity • Verified on the front-end level (FESA) LSA Core @ LHCCWG – Wojciech Śliwiński
Settings Generation • Management & scheduling of context types: • SuperCycle(Type) • Cycle(Type) • BeamProcess(Type) • Generation of initial settingsbased on optics • Generates top level (physics) parameters settings • Propagates the settings down the parameter hierarchy • Support forfunctions, discrete & actual settings LSA Core @ LHCCWG – Wojciech Śliwiński
Context type management LSA Core @ LHCCWG – Wojciech Śliwiński
New SuperCycle generation LSA Core @ LHCCWG – Wojciech Śliwiński
Actual settings generation LSA Core @ LHCCWG – Wojciech Śliwiński
Trim (1) Trim (timestamp) TrimEntry newValue Context Parameter • Coherent modification ofsettings value • Propagation of changes from source to dependent parameters • Supported value types: Functions & Scalars LSA Core @ LHCCWG – Wojciech Śliwiński
Trim (2) • Saves the changed settings and sends them (external ones) to the hardware • All trims are arichived (history)and can be reverted and rolled back LSA Core @ LHCCWG – Wojciech Śliwiński
Trim GUI LSA Core @ LHCCWG – Wojciech Śliwiński
Trim history LSA Core @ LHCCWG – Wojciech Śliwiński
Trim (3) • Settings Copy • Done as a trim operation - coherent copy • From one context to another • Cycle copy • BeamProces copy • Previous settings saved in trim history • Can copy complete parameter systems • e.g. all TUNE parametrs LSA Core @ LHCCWG – Wojciech Śliwiński
Settings Manager - Cycle copy LSA Core @ LHCCWG – Wojciech Śliwiński
Settings Manager - BeamProcess copy LSA Core @ LHCCWG – Wojciech Śliwiński
Trim (4) • Make Rules • Incorporation Rules • Link Rules From Physics to Hardware Parameters LSA Core @ LHCCWG – Wojciech Śliwiński
Trim – MakeRule • MakeRule allows to compute the parameter value from itssources • MakeRule is associated to the relation between two parameter types (e.g. K I) • A trim can be made on a high level parameter and be automatically propagated LSA Core @ LHCCWG – Wojciech Śliwiński
Trim – Incorporation Rule Incorporation rule trim • Incorporation Rule merges a change on a parameter value • Ensures continuity of functions within the SuperCycle • Propagates change from one BeamProcess to its neighbours • Rule is defined for BeamProcessType LSA Core @ LHCCWG – Wojciech Śliwiński
Trim – Link Rule SPS Ring • Link rules compute the link between two beam-in parts of the SuperCycle • Settings for the part of the SuperCyclewithout beam • Physics parameters only exist when there is beam, hardware parameters (e.g. current) are always there • Used only for hardware parameters (e.g. current). LSA Core @ LHCCWG – Wojciech Śliwiński
Exploitation (Equipment access) • Sending settings to the hardware • Driving MUGEF, LEIR, LHC Power Converter • Generic drive for FESA devices • Implemented transactions for MUGEF • Transactions for FESA and FGC to be implemented • Reporting of failures • Generic tools to access any type of device LSA Core @ LHCCWG – Wojciech Śliwiński
Equipment Control • Read/Write of any properties (including FESA) • Custom commands LSA Core @ LHCCWG – Wojciech Śliwiński
Generic Measurement LSA Core @ LHCCWG – Wojciech Śliwiński
Agenda • LSA – operations view • LHC driven extensions LSA Core @ LHCCWG – Wojciech Śliwiński
LHC - non-cycling machine LHC is different from SPS – there are no cycles Sequence of processes (i.e. injection, ramp, squeeze, physics) executed asynchronously Length of some of these processes is unknown in advance e.g. physics LSA Core @ LHCCWG – Wojciech Śliwiński
HyperCycle • Organizes LHC operations • Ordered sequence of SuperCycles • Orders SuperCycles to be played in LHC • Mixture of normal and actualSuperCycles • e.g. injection, ramp, squeeze • Only oneSuperCycle within Hypercycleactive • Normal or actual LSA Core @ LHCCWG – Wojciech Śliwiński
Actual Settings • When lenght of some processes is unknown in advance • Created as snapshot of a function at a given point in time • Creation point: START, END, BETWEEN • Discrete setting taken from function at a given time • Enables discrete trim – time independent • Incorporation of the changes • Incorporated back to the source SuperCycle function • Incorporated forward to the next SuperCycle function LSA Core @ LHCCWG – Wojciech Śliwiński