1 / 9

eFEX PDR

eFEX PDR. Scope Actions Schedule. Introduction. eFEX PDR was held 12 Feb Reviewers Stefano (chair), Sam (Tile Cal), Wade (Hub module), Uli (L1Topo + jFEX), Richard (Test module), Jim+DavidS (physics), Maurice (ROD), Stefan Hass (CTP + CERN electronics group), Hucheng Chen ( LAr )

judson
Download Presentation

eFEX PDR

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. eFEX PDR Scope Actions Schedule

  2. Introduction • eFEX PDR was held 12 Feb • Reviewers • Stefano (chair), Sam (Tile Cal), Wade (Hub module), Uli (L1Topo + jFEX), Richard (Test module), Jim+DavidS (physics), Maurice (ROD), Stefan Hass (CTP + CERN electronics group), Hucheng Chen (LAr) • Bruce, Rainer, David & David as ex-officio members • Many thanks to all involved • Outcome: • project was approved, • a few minor design changes were suggested and agreed • actions were identified, to be pursued by eFEX design team & wider L1Calo group

  3. Scope • Update the conceptual design • Verify design meets physics requirements • Check whether any open issues appear from the viewpoint of the design, on the overall ATLAS Trigger architecture, that should be brought to the attention of a wider community • Check specifications is sufficiently defined to proceed to prototype • Check whether the specifications of the interfaces are sufficiently defined to proceed to the preliminary neighbouring components • Review cost, schedule and organisation • Not reviewed: production-related issues, e.g., final engineered design, detailed cost estimates, production schedule.

  4. Requirements External to L1Calo • Identified 1 requirement that proposed L1Calo system imposes on external systems: • L1Calo expects upstream systems (LDPS, L1Calo PPr and eventually TileDPS) to record the incoming data to DAQ. • Needs to be formalised with those groups (eFEX doesn’t have capacity to transmit a copy of all received data)

  5. Actions for L1Calo (1)(beyond eFEX Engineering Team) • Simulation studies are needed to establish • baseline algorithms for the eFEX for seeding candidates, measuring their ET and applying hadronic vetos. • No. TOBs that eFEX must handle • TOB-merging functionality required of the eFEX, e.g.: • disambiguation of EM and Tau candidates; • prioritisation of TOBs (including sorting, although suspect precluded by latency); • prescaling • overflow handling & flagging • any need for the eFEX to compute multiplicities. • The physics groups should be questioned to establish the lowest required thresholds for EM & Tau candidates

  6. Actions for L1Calo (2)(beyond eFEX Engineering Team) • A Review of L1topo is required, to establish the constraints it places on the design of the FEXs and the Optical Plant: • How many L1topo boards are needed to accept one copy of all the inputs from the FEXs plus Muon system? • How does each L1Topo Processor FPGA on a L1Topo board get the inputs it needs? • If more than one L1Topo board is needed, how will the topo algorithms be divided? • How will multiplicity triggers be implemented in L1Topo? • What is the maximum number of TOBs that can actually be accessed in a topoalgorithm? • How many copies of inputs does all this imply?

  7. Actions for L1Calo (3)(beyond eFEX Engineering Team) • Plan for the transition from the CP/JEP-based trigger to the new system should be documented • Handling of environment data to DCS and ATCA Shelf Controller – coherent scheme needed • Mapping of ECAL and HCAL fibres into MTP sockets: is segregation required? • (Optical plant issue) • Feasibility of common RTM design for the eFEX and jFEX should be investigated • Consider renaming L1Calo ROD (which also carries near real-time signals in Run 4)

  8. Actions for eFEX Engineering Team • Check all proposed data formats with interfacing systems • Change design to allow handling of over-lapping readout time frames • Established need (or not) for playback memories on all inputs • Amend buffering requirement on Readout path to 6s & assess impact • Document plan B for FPGA configuration, should System ACE IP prove unobtainable • Inform ATLAS electronics group of power (cooling) requirements • And many other helpful recommendations of more local impact….

  9. Schedule • First draft of report imminent, for circulation amongst reviewers • Most pressing issues raised are the physics questions • Aim for first answers in summer – allows hardware changes to be incorporated in prototype

More Related