1. Jan 7, 2002E. Gallas/Trigger Db1 Trigger Lists and L2 Releases Elizabeth Gallas, Jeremy Simmons (Fermilab - Computing Division) See my Trigger Working Page http://www-d0.fnal.gov/~gallas/trig/trigger.html Special TriggerDb/L2 meeting February 26, 2002

2. Trigger Database Design Trigger List tl_name/tl_version Trigger Name tn_name/tn_version 1N1N L1 Script l1s_name/l1s_version L3 Script l3s_name/l3s_version L2 Script l2s_name/l2s_version NEOTERM And/Or Term 1 N1 1 1 1 1 1 1 L2 Filter ‘Term’ t_name/t_version 1 N2 L2 Tool ‘Term’ t_name/t_version 1 1 N2f N2t 1 N2ft L2 Object O_name/O_version (set of parameters, types, defaults, min, max) Based on (L3 same as L2 structure except no preprocessor) L2 Preprocessor pp_name/pp_version 1 Npp A ‘Term’ is a tool or filter with a distinct set of parameter = value pairs

3. Trigger Database Design Trigger List tl_name/tl_version Trigger Name tn_name/tn_version 1N1N L1 Script l1s_name/l1s_version L3 Script l3s_name/l3s_version L2 Script l2s_name/l2s_version NEOTERM And/Or Term 1 N1 1 1 1 1 1 1 L2 Filter ‘Term’ t_name/t_version 1 N2 L2 Tool ‘Term’ t_name/t_version 1 1 N2f N2t 1 N2ft L2 Object O_name/O_version (set of parameters, types, defaults, min, max) Based on ‘Release Version’ p11.01.00 or pseudoversion L2 Preprocessor pp_name/pp_version 1 Npp

4. Jan 7, 2002E. Gallas/Trigger Db4 Proposal for L2 releases (1) For any release you must decide if any of the triggers in the current trigger list must change –IF YES: Create new trigdb: objects (parameter definitions) and associate those with the new release pseudoversion Create new trigdb: terms (tools, then filters) Create new trigdb: l2 preprocessors, associate w/filters Create new trigdb: l2 scripts Create new trigdb: triggers Create new trigger list Run the xml generator (release pseudoversions added) Run COORSIM then L2 trigger simulator for verification Before run time –transfer xml to online system, –adjust prescale files (now about 6 files with 50+ trigs) –download new L2 executable –Change L2 online release resource file first line might contain full release version: p11.03.00 second line might contain corresponding release pseudoversion in trigger database

5. Jan 7, 2002E. Gallas/Trigger Db5 Proposal for L2 releases (2) At run time –COOR inputs many files including: xml file, L2 online release resource file? –xml file could contain release pseudo version that COOR could check against the L2 online release in resource file –COOR download includes download to L1,L2,L3,COMICS,EPICS,1553 …. –Download to L2 could add the release version from the resource file COOR reports many things to Run Summary Db (the first point of contact when doing analysis): –BY RUN number: triglist name/version, start/end times, configuration type, l3_type, prescales, all dynamically assigned bit numbers to bit names, Solenoid and Toroid state, current, polarity, comics runtype, store number, shifter name, run comments, … –now being added: good/bad runs assessments –could add L2 online release version, and L3 online release version