ACTION ITEMS FOR L1CAL Saclay L1Cal Workshop 4-6 November, 2002 1) Access to 10-bit TT raw energies o Main Question: Is it necessary to record raw TT E's to the standard D0 data stream before they are passed through the digital filter? This data would be collected in special runs or using "full readout" events and would be used to tune digital filter parameters. - Note that 8-bit TT Et's are passed to the TABs and are made available to L3 as part of the standard TAB readout. o The Problem: This (probably) requires adding significant firmware to the TAB receivers/sliding windows chips since they would have to deal with both 8-bit and 10-bit input data. o Issues: - The main issue is whether it is necessary to have 10-bit TT E's and precision readout data available in the same file so that they can be correlated. If this is not necessary then TT data can be recorded locally by the ADFs without having to pass through the TAB in a special mode. - Is it necessary to signal events for 10-bit raw data readout to the ADFs using special L1 qualifiers (separate from the standard "full readout" qualifier)? - Determination of the Digital Filter parameters is logically a 2-step process. i) Determine parameters related to the shape of the analog signal from the BLS. This requires access to all the 10-bit samples (4xBC rate) - but probably doesn't require comparison with precision readout data. ii) Determine normalization to give output in GeV. This requires precision readout to set the scale but can probably be done using the 8-bit output of the Digital Filter since it is just an overall scale factor. o Current thinking: - There doesn't appear to be a compelling reason to transfer 10-bit raw TT E's to the TAB - and implementing this would be a significant burden to the sliding window chip. We need to think more carefully consequences of not having this functionality though. o Action to take / Who is responsible a) Saclay: Study whether 2-step parameter determination as outlined above is possible. b) Nevis: Determine how much of an effort it would be to implement a 10-bit data receiving mode. c) Everyone: Try to think of other studies that would require the simultaneous presence of 10-bit raw data and precision readout data. o Timescale - A decision on this needs to be taken as soon as possible. 2) Cabling the Sytem o Questions - How difficult will it be to re-route the BLS cables so that they fit into the reduced number of racks in the new system? - How many racks should we foresee for the ADFs? o Action to take / Who is responsible a) Saclay/MSU: Come up with a realistic cable map. b) MSU: Look at the current cable mess in MCH1 and determine whether the cable map above is possible. o Timescale - to be determined... 3) Parallel Commissioning with Production Boards o The Issue: In order to maintain momentum and efficiently use engineering resources it may be necessary to commission some fairly substantial fraction of the production L1Cal system while Run IIa is still ongoing. The aim of this commissioning will be to iron out any technical problems not already solved in the pre-production commissioning phase. Calibration and other physics issues are not the point of this exercise. The commissioning requires: - More splitter boards to get enough signals to construct test triggers. - Racks, crates, power supplies, etc. to be placed near the MCH and connected to the rest of D0. o Questions - How much data will we need to do a real test of the system (how many splitters must we build)? - Would it be useful to redesign the splitters to make them easier to mass produce and who would do this? - Where can we get the money to do this? - The necessary number of BLS cables can probably be made from scraps lying around, but this should be checked. - Will the D0 management agree to this o Action to take / Who is responsible - Hal/Darien: check in with Kotcher and the spokes to see if this is an acceptable plan - Everyone: Come up with a list of goals for this test. o Timescale - before the end of the year? 4) Plan for Prototype Integration o The Issue: We should attempt to do the prototype integration this summer using racks and power supplies that are as close as possible to what we will use in the final system. o Action to take / Who is responsible a) MSU: Reserve the necessary hardware for us at Fermilab. b) Saclay: Estimate power requirements for the ADF prototypes. c) Nevis: Estimate power requirements for the TAB and GAB prototypes. o Timescale - hardware: as soon as possible - preliminary power estimates: as soon as practical 5) Output from GAB / Trigger Terms o The Issue: We should make a first description of the trigger terms that will be sent from the GAB to the Trigger Framework. o Action to take / Who is responsible a) Nevis/???: Prepare such a list and simulate it. o Timescale - to be determined... 6) Data Format for Information sent to Cal-Track Match System o The Issue: We need to determine whether what we have proposed to send to the Cal-Track system is optimal for our physics goals. o Action to take / Who is responsible a) ???: Simulate various Cal-Track data schemes. o Timescale - A reasonable proposal for this data format, backed by some study, needs to be made as soon as possible. 7) Next Workshop o Proposal: mid-late spring. Driven by the need to discuss prototype integration issues. o Action to take / Who is responsible a) Everyone: Send preferred dates for this workshop to Hal/Patrick/Maris. o Timescale - Set the date for the workshop before the end of the year.