RUN 2B L1CAL MEETING MINUTES 8 April, 2004 Present o Fermilab: D.Adams, S.Rapisarda, A.Stone o MSU: M.Abolins, D.Edmunds, P.Laurens o Nevis: H.Evans, J.Mitrevski o Rice: P.Padley o Saclay: D.Calvet Fermilab: TWG (S.Rapisarda) ------------- o report available of TWG web page o Working on software interface: esp. new trigger parts o Filtering: tuning this o Final System - working on spec's for 32-channel board MSU: ADF (D.Edmunds) -------- o Dan working on power sequencing DC-to-DC converter o Checking availability of new parts o Placement of parts on layout o Monitoring TT Et's from ADF: done on ADF or TAB? - we need to firm up how this will be done - this should be discussed at a meeting in the near future o Tests to do in integration - look at signals on cables from BLS system with scope (see below) Saclay: SCLD/ADF (D.Calvet) ---------------- o SCLD - Dan has reviewed Denis' schematics: seems to be ok . has all required functionality . ==> ready for layout - layout has started today ! o Received 2nd ADF v.1 at Saclay - basic checks look ok - firmware cleaned up --> easier to port to a different simulator (than ModelSim) UIC: Cabling (A.Stone) ------------ o No feedback so far on Alan/Mario's proposal o Dan suggests making models of the new proposed cables - note: we only have one example of this cable so far - need more o Alan will look into getting some of this cable to test - also need to get connectors - start mech. design of bulkhead, etc. Nevis: TAB/GAB (J.Mitrevski) -------------- o TAB/GAB prototype tests - testing of GAB prototype continues - have successfully transfered data from TAB to GAB - next step 2 TAB --> GAB data transmission Online Software (P.Laurens) --------------- o Philippe is concentrating mainly on the ADF work Verifying L1Cal Readiness (H.Evans) ------------------------- o see talk posted off agenda page o Main Questions to answer A) Will the operation of L1Cal IIb perturb data taking? B) How will we know that the data taken with the new trigger will not be worse than the current data? o Plan to address these points follows - discussion is included after each point 1) Operations and Stability - need to be able to run the test system w/out interfering w/ physics data taking a) crashes/deadtime............................meas in test system b) reliable downloading.........................use in test system c) monitoring tools..............................software in place d) parameter determination.......................software in place e) unpacking & reco work well................data from test system 2) Trigger Quality a) trigger definitions (l1,L2,L3).........in place well beforehand - filter coeff's thresholds, and/or terms, trigger list b) good est's of rates and eff's.......pred w/ MC - verify w/ data 1. define triggers 2. derive TT response using splitter data --> correct MC model 3. model TAB algorithms w/ MC (deterministic) 4. Model and/or & trig. list w/ MC --> rates & eff's o Things to do - identify people/groups for all tasks above - start regular test-system running w/ split data as soon as possible . probably after ADF v.2 is ready ************************************************** Please send a list of what you/your group is currently planning to do in this area to Hal as soon as possible **************************************************