1. Summary of TPC/TRD/DCS/ECS/DAQ meeting on FERO configuration CERN,January 31 st 2006 Peter Chochula

2. Peter Chochula, January 31, 2006 Agenda of the meeting  Introduction (P.Ch.)  TRD overview (Kai)  DB tests (Sve)  TPC and TRD configuration records (Roland)  FED status (Benjamin)  Discussion – all

3. Peter Chochula, January 31, 2006  References: 11 th, 12 th and 13 th DCS Workshops ALICE offline calibration workshops FED API 2.0 TPC/TRD meeting during ALICE week in October 2005  Documents and transparencies are available on the DCS web For the summary of the workshop follow the “Detectors” link and choose either TPC or TRD

4. Peter Chochula, January 31, 2006  the data flow for different running modes

5. Peter Chochula, January 31, 2006 Obtaining the configuration data FERO Configuration Database Calibration Procedure (online systems) Analysis Procedure DCS Archive DAQ Data

6. Peter Chochula, January 31, 2006  detector calibration … is not a just one simple process, one detector can have several calibration modes … all online systems are involved  Data is sometimes coming from several sources … procedures are unknown The example of TPC follows

7. Peter Chochula, January 31, 2006 Pedestal taking 1.Once (or more per run) 2.HV: on or off (on only without beam) 3.FERO: Taking raw data without zero suppression 4.Trigger: random trigger 5.Gating pulser on 6.Calculation of averages 7.Generating of Altro code -> write into database 8.Push from Database to Fero (via DCS or DDL) Calibration procedures for TPC (1)

8. Peter Chochula, January 31, 2006 Calibration procedures for TPC (2) Calibration Pulser 1.Once (or more per run) 2.No Gating pulser 3.Trigger: Pulser 4.Take data for offline analysis

9. Peter Chochula, January 31, 2006 Calibration procedures for TPC (3) Laser Calibration 1.Normal operation mode 2.Trigger: laser or 3.Laser triggered external? 4.Two modes wanted: Exclusive laser run Once (or more per run) Laser embedded in normal run Continues 5.Take data for offline Analysis

10. Peter Chochula, January 31, 2006 Calibration procedures for TPC (4) Krypton calibration run 1.Before and after beam times (shutdown phases) 2.Special gas system operation (manual) 3.Random trigger 4.Gating triggered (closed ?) 5.HV reduced voltage settings

11. Peter Chochula, January 31, 2006  organization of configuration records

12. Peter Chochula, January 31, 2006  Configuration data will be stored in the DCS configuration database  The data will be accessed by FED servers and sent to the electronics  For some detectors the data can be loaded via DDL (DAQ) The configuration records will be provided to DAQ as files – in fact DAQ typically already maintains a local copy of the data  Configuration database structure follows the layout of each detector (no generic model)

13. Peter Chochula, January 31, 2006 FED Server FEE Client InterCom Layer Config. PVSS Cmd / ACK Channel Service Channel FED Client... FeeServer incl. CE FeeServer incl. CE FeeServer incl. CE Command Broadcast Cmd ACK Acknowledges Service Services... FeeCommunication chain DCS Archive Conditions Database Amanda

14. Peter Chochula, January 31, 2006  Present strategy is to store the configuration data in form of BLOBs and/or tables where appropriate Conversion to DAQ configuration files and/or local FED cache should be straightforward TPC Pedestals will be stored in files  If needed, the files should be stored in the conditions database  Data size (assuming 200kB/RCU): ~43 MB for TPC ~108 MB for TRD Next slides were presented by Jorge Mercado and Roland Bramm

15. Peter Chochula, January 31, 2006 TPC Structure (Roland)

16. Peter Chochula, January 31, 2006 TRD Structure (Roland) TRD

17. Peter Chochula, January 31, 2006 TRAP configuration overview add r13 c3 r13 shl 1 r11 r11 jmp cc_carry return1 mov bitnum work const dut = 3 reset dut write dut, NMOD, 0x1C expect dut, NMOD, 0x1C write NICLK, 1.ASM.TCS ASM_MIMD TCC CODEM 10 53249 511 127 24 10 53250 11 127 25 10 53251 11 127 26 10 57344 -1895563249 127 10 57345 -1895825408 127.DAT.C + SCSN Master TRAPs

18. Peter Chochula, January 31, 2006 www.ztt.fh-worms.de FED Server FEE Client InterCom Layer Config. DB PVSS Cmd / ACK Channel Service Channel FED Client... FeeServer incl. CE FeeServer incl. CE FeeServer incl. CE Command (Broadcast) Cmd ACK Acknowledges Service Services... Config. File Load configuration data for ICL from file OR database Command Coder Load FERO configuration from database (in developmente) Load configuration data for ICL from file OR database

19. Peter Chochula, January 31, 2006 Implementation status (roland)

20. Peter Chochula, January 31, 2006  DB Performance: It is difficult to estimate the time needed to configure the detectors due to unclear requirements Some numbers were presented at the DCS review and there were no objections  New request presented at the meeting assumes a speed-up by factor of ~10 An additional fronted data caching mechanism must be implemented if this request is justified

21. Peter Chochula, January 31, 2006 Test With Small BLOBs  Test records consists of 10 Blobs with size 10kB each  260 configuration records were retrieved per test  Allocation of BLOBs between configuration records altered From random To shared (certain BLOBs were re-used between configuration records) -> to test the ORACLE caching mechanism

22. Peter Chochula, January 31, 2006 BLOB Retrieval Tests

23. Peter Chochula, January 31, 2006 TPC and TRD can perform FERO reconfiguration during the run if needed.  It is not necessary to stop the run, because the data is loaded using the DCS board  DCS will be notified ( a SEU flag will be monitored). This information will be recorded to the DCS archive along with a timestamp of the event – precision depends on the SEU detection algorithm

24. Peter Chochula, January 31, 2006  dependencies on external data sources ( e.g. database of positions of super modules)

25. Peter Chochula, January 31, 2006  TRD requests a link to an external database of super module positions  This database contains static fronted configuration  DCS cannot link to any external sources  DCDB was proposed as a proper place for storing this information by DCS and LB. This is an important topic, but out of scope of the FERO meeting….

26. Peter Chochula, January 31, 2006  Monitored data and data to be sent to offline Rather unclear situation  What data will be monitored (some information is available)  What data is needed for offline processing (some information is available)  What will be the related datapoint names and DIM services (we do not know) Amanda needs this information

27. Peter Chochula, January 31, 2006 Monitored TPC FERO Parameters  4500*5 parameters  4500 statuses

28. Peter Chochula, January 31, 2006 Monitored TRD FERO Parameters/ Offline Conddb Source: TRD URD 1.MCM temperature 2.user ADC 3.pulsing pattern 4.pedestals 5.zero suppression thresholds 6.memory 7.user I/O 8.MCM status 9.exceptions Source: Offline (Dariusz Miskowiec)* 1.clock frequency 2.number of time bins 3.list of masked channels 4.list of active chambers 5.ADC thresholds 6.temperature * These parameters should be collected for each run and sent to offline Source: 11 th DCS Workshop (Q&A) 1.18*6*4 Voltages 2.Some temperatures (DCS board) 3.Eventually 65000 temperatures from MCM

29. Peter Chochula, January 31, 2006  There is a clear difference between the answers  TRD will update the documents  All detectors seem to have similar problems

30. Peter Chochula, January 31, 2006 Tests with the full chain should be launched in ~1 month time  Yet another workshop is organized in Bergen after the ALICE week  The discussed architecture will be re- used by other detectors There will be detector specific deviations from the scheme, mainly in the operational aspects (calibration modes)