1 / 7

DAQ and related issues

DAQ and related issues. Gérald Grenier The University of Iowa. DCT upgrade Final Design Review April 11, 2003. Overview. DAQ lives in ''dataflow'' where Tagged Containers (TC) are exchanged. Contains data. Identity. 2 issues : Configuring the boards.

scout
Download Presentation

DAQ and related issues

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. DAQ and related issues Gérald Grenier The University of Iowa DCT upgrade Final Design Review April 11, 2003

  2. Overview DAQ lives in ''dataflow'' where Tagged Containers (TC) are exchanged. Contains data. Identity 2 issues : Configuring the boards. data flow : UNIX file (preferably TC) --> ROM --> trigger boards Feature EXtracting (FEX) the data. data flow : trigger boards --> ROM --> UNIX file (TC only) 3 milestones :1) DAQ in joint DCH/DCT teststands. due for May 2) DAQ in IR2 with 2 DCTs, new as a parasite spectator. due for June 3) Shutdown old trigger. due for fall

  3. Milestone 1: joint DCH/DCT prerequisites FEXed data TC ready (In progress). First version of FEX code ready (In progress). ZPD: Dataflow requests FEX time < 100 ms. Preliminary tests : FEX done in 93 ms without BLT FEX. No byte swapping effects taken into account --> firmware-software optimization. Will drop TSF input mask data after commissioning. Might keep only a sample of the events. TSF: FEX code should be 95% identical to old one.

  4. Milestone 1: joint DCH/DCT prerequisites (2) A way (firmware, flat file, configTC) to configure boards (not started). Ability to run with an incomplete crate: needs an automatic board detection (done). Ability to configure the slot to DCH sector map (done with flat file configuration). Optional but extremely useful: an application that does something with the data (not started).

  5. Milestone 2: parasite in IR2 prerequisites Optimized version of FEX ready (in progress). ConfigTC ready and registered in database (not started). Configuration online code ready (in progress). Ability to have 2 versions of the same data (TSF) use of data TC with same content but different identities (in progress). Include new DCT crate in dataflow system (not started). Put new DCT data in database (TC to digi conversion) (not started). Can be delayed : digi to TC conversion.

  6. Milestone 3: shutdown old DCT prerequisites • Ability to correctly simulate new trigger in Monte Carlo production • simulation program ready (in progress). • configure data in database and configTC created on the fly (not started). • Monitoring new trigger (not started). • Adapt OEP/L3 to the new trigger (not started).

  7. Conclusion • L1Accept Feature EXtraction well on track for first milestone. Tight schedule for second milestone. • Board's configuration, to meet June deadline: Definition of configure data URGENTLY needed. TC to digi conversion needs manpower. • Fall deadline : Biggest needs in offline software.

More Related