DAQ status for cosmic-ray test

1. DAQ status for cosmic-ray test Hideyuki Sakamoto 19th Sep 2007

2. Status on daq by DATE • Tests was almost finished. • Initializing AFE • Readout VLSB of original firmware • Same result as EXCEL • Remaining tasks • Test readout of VLSB with new firmware • Test trigger logic • Schedule • Install package tested at IC during CM19. • Starting remaining test after arrival of cassette/AFEIIt. 02Nov07? VLPC readout: expect to ship at the end of Oct. So, anticipate 02Nov07 as reasonable milestone for arrival in R12. Minutes of last meeting

3. Comments on QA • Now, we are considering Sr90 as source. • Co57 (gamma-ray) is difficult to determine hit fiber, while beta-ray allow us to take coincidence with 9 fibers. • First result shows that • Hot spot was actually observed, but smaller light yield was observed on V view compared by MC. ( see next slide) • Need to understand this behavior. • I will check by cosmic-ray data that this channel is alive. • If James is ready, it’s very helpful to take another Sr90 data with different location of Sr, (e.g. center of Station) • Will be reported soon! • First QA for 5 stations is needed to finish before assembly. • We have 1 month… Too small statistics to check if dead or alive

4. MC (Sr90) Data1 X view PE MeV W view V view Data2 10pe Data1 = Events for max. light yield @V#90&W#157&&X#72 Data2 = Data1 && 5 pe for all views peak around 5 p.e. looks like signal.. PE Check 10 p.e line in MC • Make PE distr. and comparing. Analyze by another Sr90 run. 10pe

5. (Backup)Short manual for DATE user

6. Startup No need to setup dateNetwork… dateNetwork –s –a”heppc55” Valid only for 1 PC DAQ?? • Run setup.sh script • source $DATE_ROOT/setup.sh • Start dim/dns • source /opt/dim/setup.sh • /opt/dim/linux/dns & • Start daemons • dateSiteDaemons start • Start info browser • infoBrowser • Start editor for MySQL • editDb • Run DAQ Control HI script • $DATE_ROOT/runControl/DAQControl.sh

7. Restart • Kill DAQCONTROL • Click “close HI” from menu button, or • type kill -9 <process id named runControl HI>. • Kill other processes • $DATE_ROOT/runControl/stop_daqDomains.sh • Note that user interfaces as DAQCONTROL, editDb, infoBrowser are not killed by this script. • Start DAQCONTROL • $DATE_ROOT/runControl/DAQControl.sh

8. How to refresh infoBrowser To remove previous message (used usually) • Click “clean view” button on inforBrowser To remove continuous long message (used for debug) • Delete fifo $DATE_SITE/logFiles/infoLoggerReader@$hostname.fifo • rm /opt/date_site/logFiles/infoLoggerReader@heppc55.fifo • Restart daemons • dateSiteDaemons restart

9. How to implement readout program • Define structure for equipment parameter • To access parameters defined in MySQL • argument for all of 5 functions • Implement 5 functions • ArmXXX • DisArmXX • AsynchReadoutXXX • EventArrivedXXX • EventReadoutXXX • Add the above 5 functions in DATE • Add EQUIPMENTDESCR (XXX) macro in the structure equipmentDescrType at the end of readout code. • After compiled, make copy or link in the $DATE_SITE/$hostname directory • Make directory $DATE_SITE/$hogtname in advance

10. Procedure to setup equipment on DATE This is the next step after preparing readout code. Parameters to be defined/set in MySQL • EQUIP_TYPES • EQUIP_PARAMS_XXX Setup by script For defining parameters $DATE_ROOT/readList/equip_table_maker.tcl ( no available @ ver.6.09) Setup by hand • See following page To register equipment in DATE editDb ($DATE_ROOT/editDb/edit.sh)

11. EQUIP_TYPES table Define that EventArrivedXXX will produce trigger or not Need for specifing equipment as read out equipments The order calling AimXXX function Define that ReadoutEventXXX will produce data or not Name of readout function located in $DATE_SITE/$hostname directory

12. Equipment_PARAM_XXX table Parameters • For DATE • LDC, EQUIPMENT_NAME, ACTIVE • For User • Connected to the argument in readout functions e.g. ArmVLSB (char *partype) Example for AFEIIt & VLSB DATE USER

13. Setup by script (equip_table_maker.tcl) Tool to make EQUIP_PARAM_XXX table and add an equipment in EQUIP_TYPES • Click New button in Equipment tab • Select equipment you defined • Click create button • Input values • Click Add button

14. Setup equipment by hand user hostname database name • At first, connect to DATE_CONFIG table mysql -u daq -p -h heppc55 DATE_CONFIG Just type –p to prevent typing password directly • Create table of EQUIP_PARAM_XXX e.g. XXX=VLSB • create table EQUIP_PARAM_VLSB ( LDC char(32), EQUIPMENT_NAME char(32), ACTIVE tinyint(1), BaseAddress1 char(32), BaseAddress2 char(32) ); • (to delete table) drop table EQUIP_PARAM_VLSB; • Add our equipment field in EQUIP_TYPES e.g. AFEIIt equipment • insert into EQUIP_TYPES values('AFEIIt',80,1,0,80,'readout'); • (to delete field) delete from EQUIP_TYPES where NAME='AFEIIt'; use DATE_CONFIG; show EQUIP_TYPES; select * from EQUIP_TYPES;

15. Registration equipment in DATE (editDb) Tool to register equipments using EQUIP_PARAM_XXX ( not made newly in MySQL ) • Click New button in Equipment tab • Select equipment you defined • Click create button • Input values • Click Add button 1 3 4 2 5

16. DAQCONTROL 1 4 5 2 3 Both unchecked LDC ON GDC OFF • lock • define configuration • define run parameters (see next page) • star process (calling ArmXXX functions) • start run Appear after step 2

17. Setup run parameters 4 1 2 #/events 1 select LDC 2 change parameters. • #/events • File name • # = run number 3 click Apply tagged values 4 click OK • Or click Save for next time File name 3

18. Change time out limit for long AFE initialization About 2 minutes is needed to initialize one AFEIIt board… $DATE_ROOT/runControl/RunParameters.config (21st line) #phaseTimeoutLimit "Max. time for SOR/EOR phases" 30 range 0 60 300 Max. time for SOR/EOF phases Default 60 sec => 300 sec

19. Event header (17 words) Equipment A header (7 words) Equipment A Data (X words) Equipment B header (7 words) Equipment B Data (X words) Other equipments Data format (for case of 1 LDC) Example of PHYSCIS event • Defined in $DATE_ROOT/commonDefs/event.h • A run includes several type of events, identified by “eventType” . • SOR/EOR • Every run has these type of events at the beginning/ending of run. • There is no data here • PHYSICS_EVENT • There is data from each equipments • (CALIBRAION_EVENT) • Tagged at calibration run • Data stored at each ReadEventXXX function are recorded sequentially in the PHYSICS_EVENT block • Headers • Event header • Contains 17 words • Follows blocks of equipment @PHYSICS event • Equipment header • Contains 7 words • Follows equipment block

20. Event header (17 words) format

21. Equipment header (7 words) format

22. Equipments (GENDATA) 2 AFEIIts & 1 VLSB (includes 2 boards) Events recorded SOR PHYSICS EOR (not seen here) Size of Equipments AFE = 23 words = 92(0x5c) bytes 7(Header) + 8 (temp) + 8 (heater power) VLSB = 1167 words = 4668 (0x123c) bytes 7(Header) + 1160 (145 x 4 links x 2 boards) Size of PHYSICS event 1230 words = 4920 (0x1338) bytes = 17(Header) + 23 x 2(2 AFE) + 1167(1 VLSB w/ 2boards) Real data sample SOR event Header SOR event Header PHYSICS event Header LHB Header LHB data RHB Header RHB data VLSB header VLSB data