How do we tackle the extended requirements?

How do we tackle the extended requirements?HWC and Beam Commissioning?PIC1 PM Analysis

PM Workshop, Adriaan Rijllart

Extending the PMA systemOutlineSimple PM system dataflow viewKnown systems with PM requirementsThree step PM analysisSoftware triggerLinking requirements, source code and resultsImplementation extensionsRecapitulation


PM system dataflow view, one-step analysisQPSPICPCLHCRaw data filesSystemsResult dataLoggingAlarmsOthersystemsPM viewerPM analyserData basesPM serverStarting point in 2005


Summary of systems with PM requirementsAnalyses well advancedLegend:y - produces datan - no data? - not know yetBut all need PMA!


Sheet1

Summary of PCR Post Mortem Data Requirements

SystemTransient RecorderLoggingAlarmsExternal TriggerInternal TriggerExpert Data

Access SystemOOPOOP

Aperture KickersPOPPOP

Beam DumpPOP?PPPO

Beam Current MonitorsPPPPOO

Beam Feedback SystemsP?PPOO

Beam Loss MonitorsPPPPPP

Beam Position MonitorsPPPPOO

Beam Profile MonitorsPPPPOO

CollimatorsOPPOOO

Cooling and VentilationOPPOOP

CryogenicsOPPOOP

Cryostat Instrumentation?PP?OO

InflectorPOPPOP

Power ConvertersPPPPOP

RF Power & Low-LevelPPPPOP

Reference Magnet SignalsP?PPOO

Transverse DampersPOPPOP

Radiation MonitorsPPPPOO

VacuumOPPOOO

Electrical NetworkPOP?OP

Energy Extraction SwitchesPPP?PP

Machine ProtectionOPPOP?

Quench ProtectionPPP?PP

Sheet2




CollimatorsOPPOOO

VacuumOPPOOOPO

Cooling and VentilationOPPOOP

CryogenicsOPPOOP


Access SystemOOPOOP











Beam DumpPOP?PP


InflectorPOPPOP




Sheet3



Access SystemOPPOOP

Cooling and VentilationOPPOOPP

CryogenicsOPPOOPO


Beam DumpPOP?PP







CollimatorsOPPOOO

InflectorPOPPOP





VacuumOPPOOO






Sheet4


SystemFrequencyDepthFrequencyDepth

Energy Extraction Switches1 Hz600s

Beam Feedback Systems10 Hz10s

Reference Magnet Signals250 Hz10s

Electrical Network

Beam Dump1 GHz2 turns

Aperture Kickers1 GHz20 turns

Inflector1 GHz20 turns

Transverse Dampers40 MHz1000 turns

Quench Protection100 Hz6s1 Hz60 sTails of current leads

Beam Loss Monitors100 Hz10 s1 Hz10 min

Beam Current Monitors40 Mhz1000 turns11 Khz?

Beam Position Monitors40 MHz1000 turns50 Hz20 s

Beam Profile Monitors

Power Converters1 kHz20s

RF Power & Low-Level11 kHz1s

Radiation Monitors

Sheet5

SystemTransient RecorderLoggingAlarms

Beam Dumpyny

Beam Loss Monitorsyyy

Energy Extraction SwitchesyyyProtection

Machine Protectionnyy

Quench Protectionyyy

Aperture Kickersyny

Beam Feedback Systemsy?y

Collimators?yy

InflectorynyAct on Beam

Power Convertersyyy

RF Power & Low-Levelyyy

Transverse Dampersyny

Vacuumnyy

Beam Current Monitorsyyy

Beam Position MonitorsyyyMonitors

Beam Profile Monitorsyyy

Cryostat Instrumentation?yy

Access Systemnyy

Cooling and VentilationnyyServices

Cryogenicsnyy

Electrical Networkyny

Sheet6

System

Beam Dump

Beam Loss Monitors

Energy Extraction Switches

Machine Protection

Quench Protection

Aperture Kickers

Beam Feedback Systems

Collimators

Inflector

Power Converters

RF Power & Low-Level

Transverse Dampers

Vacuum

Beam Current Monitors

Beam Position Monitors

Beam Profile Monitors

Cryostat Instrumentation

Access System

Cooling and Ventilation

Cryogenics

Electrical Network

PM data flow, two-step analysisLoggingAlarmssecond analysisData basesMeas.SDDSQPS viewerResult 1PM system, evolution during 2006HWC viewerPIC-PMAQPS-PMAPC viewerResult 2PC-PMAPIC viewerClear advantage to introduce 2nd step analysis.


Architecture of PMA system, three-step including triggerIndividual system analysisLogical system analysisLogical systemconclusionMagnetsystemSDDSloggingadditionalresultsRaw dataResult data 1Analysis triggerResult data 2Logical system conclusionDFBSCLinkStand. cellCryo circuits


Architecture of PMA, extended to beam data analysisLogical system conclusionMagnetsystemSDDSloggingDFBSCLinkStand. cellCryo circuitsBeam systemsIndividual system analysisLogical system analysisDirection of extension


Why a trigger module?Individual system analysisSDDSloggingRaw dataAnalysis triggerIndividual System analysis modules dealing with logging data need to know when to startIndividual System analysis modules dealing with SDDS data could detect when to start by itself or rely on the trigger moduleLogical system analysis modules combining logging and SDDS data need trigger module or would need to communicate with Individual System modulesManual triggers could be given by an operator through the trigger moduleIf all analysis modules rely on the trigger module this can also fulfill the task of monitoring the analysis processReasons:


PMA Software triggerCRYOVACTriggerSystem Activity System flag Analysis ResultBLMSummaryPCQPSPICBPMXPOCConfigPMADomainUser levelViews09:12:04.255 PC error09:12:04.360 BLM threshold crossingmessages


Manual triggertimeAlarmPM triggerManual triggerParbritrary unitsanalysis intervalLogged signal


Linking requirements, source code, docs and results PMA_homeQPSPCQPS_req1.1QPS_prog1.1QPS_doc1.1QPS_res1.1PC_req1.1PC_req1.2PC_prog1.1PC_prog1.2PC_doc1.1PC_doc1.2PC_res1.1PC_res1.2Program_description.docText, XML or DB transferExcel fileWord fileLabVIEW source


Different ways to implement mathematical analysisclear all

kr = 1*1;ki = 1*1;phi = 1*pi/4;

xmax = 15;xmin = -4;delx = 0.1;

x = [ 0:delx:xmax];x2 = [xmin:delx:xmax];

#include #include #include

static int red = 0;static int green = 0;static int blue = 0;

void setupcolor(char *str);

int main(int argc, char *argv[]) { FILE *pngout = {0}; gdImagePtr img; int fgcol, bgcol; char *str = NULL;

LabVIEW diagramFormula nodeMATLAB scriptC code in LabVIEWThere are at least 4 ways to implement mathematical analysis in LabVIEW


LabVIEW mathematical analysis librariesMain palette600 available functions


Does LabVIEW analysis scale?LabVIEW compiled code compares to C for memory use and speedHowever the Graphical User Interface (GUI) can slow down the execution, but sub program blocks dont need to show their GUIFor tracing and debugging purposes all sub programs can show their GUI on user requestLabVIEW code can run entirely without GUI using the technique of virtual display, for execution on a head-less linux serverTests should be done how many QPS or PIC modules we can run on one computer before a slowdown is noticed


Recap of How do we tackle the extended requirementsThree-step analysis gives best data reduction and processing for the problems to be solvedSoftware trigger module gives flexibility for automatic and manual triggeringExtension to beam related equipment has been shownLinking documentation of requirements (xls, doc) to source code, to code description and to results using a reference systemAnalysis implementation can integrate LabVIEW diagrams, formula nodes, MATLAB scripts and C codeA scaling test, running many analysis modules in parallel, needs to be done to determine what is the limit of one computer


Documents

How do we tackle the extended requirements?