1. TDAQ status and plans for 2008 Carlos Solans TileCal Valencia meeting 17th December 2007

2. TDAQ status and plans for 2008, 17/12/2007Carlos Solans2 Outline TDAQ status Lab setup Releases and upgrades in 2007 Milestone weeks performance TDAQ plans Plans for 2008 Other tasks not in my plan

3. TDAQ status and plans for 2008, 17/12/2007Carlos Solans3 Lab set-up Computers Trigger and data flow NIM logic sends triggers gated with busy ROD/TTC processes data on trigger, sends busy signal out ROS stores all data to disk ROD/TTC ROS NIM PurposeIFICCERN DAQ afs installation (tical11) afs installation (valtical20) RODLocal HDD (rcc2)Netbooted (valticalrcc1) ROS1 ROBin (valtical23)1 ROBin (valtical13) ROD/TTCROS DAQ Lab computers hierarchy controls trigger busy data Lab TDAQ flow chart

4. TDAQ status and plans for 2008, 17/12/2007Carlos Solans4 Releases and upgrades in 2007 TDAQ releases 01-07-00: January 2007, used for M2, M3 01-08-01: July 2007, used for M4 (SLC4) 01-08-03: October 2007, used for M5 ROD upgrades Input monitoring (tile_rod_input) Events monitoring (tile_rod_events) TTC syncrhonization, BCR and ECR handling RITMO Last TTC event counters High rate testing  TTC, Staging, Input FPGA firmware upgrades Plugin structure for OFC ROD firmware download through VME General upgrades DDC state exchange and meta-data in byte stream Raw data decoding online DVS digital front-end tests whole partition Parallel data acquisition per TTC partition Scripts for lab release upgrade VME crates rebooting

5. TDAQ status and plans for 2008, 17/12/2007Carlos Solans5 Milestone weeks performance M2, M3: ROD booting too slow OFC retrieved from file M4: ROD booting ~10 times faster Missing events in DSP detected (more TTC in than Data in) OFC plugin structure tried out Too many controller applications (3 per TTC partition: TTC, ROD, ROS) M5: ROD booting problems: failure in fast booting of Input FPGA Missing events detected when random CTP trigger Busy logic problem (CTP still sends triggers when RODs are busy) OFC plugin structure working One controller application per TTC partition

6. TDAQ status and plans for 2008, 17/12/2007Carlos Solans6 Plans for 2008 Investigation Missing events: M6 milestone Front-end digital DVS tests event corruption. ROD boot. Improvements DDC meta-data inclusion in byte-stream TileCal online release installation OFC plugin reading from COOL Maintenance Release upgrades: RCD/ROS drivers, TDAQ version DVS tests integrated with DVS GUI ROD hardware in USA15 Documentation Packages documentation Calibration data acquisition Training sessions to calibration data acquisition

7. TDAQ status and plans for 2008, 17/12/2007Carlos Solans7 Other tasks not in my plan Service job TileCal calibration integration shaft + laser Development ROD/DSP Histogramming with GNAM infrastructure OMB integration with TDAQ Stop less recovery implementation DSP and Read-Out Links description Investigation Configuration database values for Laser runs

8. Back-up

9. TDAQ status and plans for 2008, 17/12/2007Carlos Solans9 TTC partition data acquisition TileCal is sub-divided in four TTC partitions. Each TTC partition is execised in parallel for calibration data acquisition Data flow TTC (LTP, TTCvi, TTCex, TTCpr) sends trigger to front-end (FE), ROD and itself (TTCpr). ROD matches data with TTC event. ROS sends data to REB. LAE sends data to REB. REB stores to disk. FE ROD ROS REB LAE TTC