*********************************************************************** * * * PART 1 PART 1 * * H1 LUMI LOGBOOK * * * * HERA e-run June/July 1991 * * * * This logbook is intended for a daily run summaries from H1 LUMI * * subdetector and can be used as a communication panel between on- * * and off-line sides. After the run is finished all collected in- * * formation will serve as a useful experience for the future work. * * * * Use command: F ====== to find all messages, and then select * * those you are interested in * * * * S.Levonian Openned: 21/06/91 at 23:45 * * Closed : 15/08/91 at 10:00 * * * *********************************************************************** 25.06.1991 ==================== H1KFOM === Input mapping ........... Layout of detectors if one sees along e-beam: Alternarive Photon Detector: Alternative Electron Tagger: _______________ __________________ | p2 | p3 | |______e0________| | | | |______e1________| |______|______| |______e2________| | p0 | p1 | |______e3________| | | | |______e4________| |______|______| |______e5________| |______e6________| Water counter (spectrometer channel) is connected to p8. Water counter (veto channel) is connected to p9. Veto counter of Electron Tagger arm is connected to e7. 28.06.1991 ==================== F11LEV === Offline requests ........ Dear onliners! Just not to forget in a hurry about some specific requests from the physics (or offline) side. Besides the list of main tasks for the current test run, like: - detector monitiring/calibration (ET+PD) - Veto calibration: a) A = f(E_gamma) for different HV b) eff(%)=f(E_gamma) -"- (?) - trigger efficiency - online s/w testing/debugging etc. i would like to ask you to consider a possibility for the following. 1) Doing an e-beam monitoring (e.g. e-current determination which is proportional to the lumi trigger rate/pressure) don't forget to measure e-beam tilt (!) e.g. on the basis of on-line histograms from PD, and try to study its stability (short time and long time behavior). This could be one of the important practical results for further calculations of our acceptances, efficiencies etc. 2) To trigger 2 event classes (perhaps trivial): a) lumi events (standard lumi trigger) b) photoproduction candidates on residual gas: only e-, no gamma 3) If possible (somewhere at the end of the e-run) make few dedicated runs with "photoproduction" trigger including the condition - e-hit point outside of the 2-3 central layers (events with max. amplitude in periphery of the ET) 4) For each of the "high Q**2 photo events" (3) it would be desirable to know a total h/w trigger rate both for lumi and all photo cand. 5) Now, or after end of the run we have to clearify what was an actual thickness and material of the e- and photon exit windows, and what was an absolute position of our counters (accuracy level 0.1 cm ?) 01.07.1991 ==================== H01USA === Daily information ....... Still there is no e-beam (from Friday,28 June). The rest time we learned previous message. 1 01.07.1991 ==================== F11LEV === LUMI reconstruction ..... If so much nothing to do, please, think about the following: 1) Do we need offline reconstruction for present setup? 2) If yes, who could provide necessary input, e.g. intrinsic resolution 3) How to transfer PD profile histograms to offline, etc. I propose to meet 3 July (after Operational meeting head by Eisele) at DESY side to discuss these and others questions and continue may be in North Hall... 02.07.1991 ==================== H01USA === Night information ...... SOME BEAM RATE WAS OBSERVED FROM 15:00 01.07.91 TO 3:00 02.07.91. During this time the the adjusment of HW trigger for LUMI events was continued. Now we have first release without veto counter in Electron Arm. I think that more usefull and more convinient if You'll visit NH. 02.07.1991 ==================== H1KFOM === Banks for Calibr.Coeff... It is possible to attempt the using of Start-Run-Record for retran- slating into IBM3090 storage some useful information. I propose to fill this record with new BOS-banks which must content informa- tion about Calibration Coefficients of both PD and ET detectors. It will be first attempt to use this record and I only am starting for modification of On-Line Program for this. Calibration Coefficients will be numbered from 0 to 24 for Photon Detector (note, that we use only p0-p3 - for alternative PD and p8 for Water Veto) and from 0 to 48 for ET (e0-e6 only at using). It is proposed that the names of this new banks may be LREC (for ET) and LRPC (for PD). Format will be "I" (as TSTC bank). The length of each bank will be some constant (without nimbering). Each Coefficient at this bank will be integer*4 which was made from real*4 with multiplication to 10000 and getting of integer component of this result. This coefficients will be at MeV/ADC counts unit. From today (very preliminary) night mesurements the set of calibration coefficients are the next: p0 = 2.167 MeV/count e0 = 6.052 MeV/count p1 = 0.864 MeV/count e1 = 1.646 MeV/count p2 = 2.735 MeV/count e2 = 3.523 MeV/count p3 = 1.486 MeV/count e3 = 3.227 MeV/count e4 = 1.110 MeV/count (?) p8(Water Veto) = 2.649 MeV/count e5 = 4.347 MeV/count e6 = 3.468 MeV/count (??) As example You can see this values (at future BOS-banks) as p0 = 21670 p1 = 8640 etc. 02.07.1991 ==================== H1KFOM === Retranslating of Proposal S.V.Rusakov asked me to retranslate to all people involved into our activity around Elecrtron Run the proposal - to meet at 9.00 at 4 July 1991 and discuss any problem (not long time). The meeting point is at 121 room of 1B (LPI office). This meeting will be connec- ted with phone speaking with Moskow. 02.07.1991 ==================== F11LEV === Correct previous message. Previous information became obsolete before being created... Final proposal: 1) To meet tomorrow after Operational meeting which will start at 11:00 in sem.5 2) Continue eventually discussion in North Hall after lanch 3) In addition, S.V.R. proposed to meet EACH thursday in 121 office after/during Moscow call (9:30-10:30) 03.07.1991 ==================== H1KFOM === Contact with J.Olsson ... Today evening it was tested first release of On-Line Program for H1 LUMI DAQ with Start-Run_Record. There are some problem with it but first Start-Run-Record was written into IBM3090 cartridge. After 10 minutes it was phone call from Jan Olsson about our new banks LREC and LRPC. He said that this banks not described anywhere at H1. I said that this is our new banks with format "I" and I hope that Dr. S.Levonian issued (may be) needed notes about its contents, format etc. J.Olsson said that format "B32" is equal to "I" (difference only at byte disposition at VAX etc.). May be at Your official note You will write about its format as "B32"? 1 04.07.1991 ==================== H1KFOM === First test run with SRR . Tonight it was written the first(MORE OR LESS SUCCESFUL) test run with Start-Run-Record (Run 5015, near 46 events, at 2:00:42). Data was gotten from test pulses (ACCELERATOR IS NOT OPERATED STILL). Contents of data and Start-Run-Record is not interesting. Format only is interesting for testing and teaching. The name of cartridge is G9037V00. If it is not difficult to You try please to decode contents of LREC and LRPC banks. I have problem with XIDAQ-package (after first 40-1000 events XIDAQ do not give me the next buffer ("try again"). I am trying very long time but only "try again" as answer from XIDAQ. I hope that tomorrow Bill will help me to do the next step. 04.07.1991 ==================== F11LEV === Strange calibration ..... Dear onliners, please, don't confuse me with wrong cartridge numbers. I need only correct RUN number in order to find your events (the rest is provided by J.Olsson's tool)... Now useful information. 1) For A.Usik (and Yu.Soloviev): I have LOOK pictures for present PD (lateral shower shape, sharing function for 2x2 modules set). You can get a copy in my office. 2) For A.Fomenko: calibration banks LREC, LRPC look strange (see listing below). Besides wrong subhearer order (1 <--> 49, 1 <--> 25) which you know perhaps, content itself seems to be wrong (esp. 7 first words in LREC and 4 first + 9-th in LRPC look like hollerith text). Please check them. *************** RUN = 5015 ****************** BOS--FSEQR- START OF FSEQR ------------------------- OOOOO OOOO OOO OOO O O O O O O O O O O O O O O O O O O O OOOO OOOOO OOOO OOOOO O OO O O O O O O O O O O O O O O O O O O O OOO O O Version 0.61/00 operating ... LREC 1 --------------- M/NPRNT---- NAMED BANK LREC 0 WITH 51 DATA WORDS AT INDEX 416 (INDEX TO NEXT BANK = 0) 1- 10 49 1 2147483647 2147483647 2147483647 2147483647 2147483647 2147483647 2147483647 43799 11- 20 29199 43799 29199 43799 29199 43799 29199 43799 29199 43799 21- 30 29199 43799 29199 43799 29199 43799 29199 43799 29199 43799 31- 40 29199 43799 29199 43799 29199 43799 29199 43799 29199 43799 41- 50 29199 43799 29199 43799 29199 43799 29199 43799 29199 43799 LRPC 1 --------------- M/NPRNT---- NAMED BANK LRPC 0 WITH 27 DATA WORDS AT INDEX 471 (INDEX TO NEXT BANK = 0) 1- 10 25 1 2147483647 2147483647 2147483647 2147483647 31119 46679 31119 46679 11- 20 2147483647 46679 31119 46679 31119 46679 31119 46679 31119 46679 21- 27 31119 46679 31119 46679 31119 46679 31119 BOS--FSEQR- EOF on input unit BOS--FSEQR- RUN-NR...EVTS RUN-NR...EVTS 4998 165 4999 48 5000 120 5001 1 5004 26 5005 31 5006 154 5007 18 5008 616 5009 832 5010 1 5012 3 5013 118 5014 316 5015 47 5016 1308 BOS--FSEQR- STOP OF FSEQR +++++++++++++++++++++++++ 1 Job statistic: -------------- Total number of records (events) processed: 3804 Total CPU time used: 24.52 seconds Average CPU time per record: 0.01 seconds ===> RUN 5015 47 RECORDS HAVE BEEN PROCESSED ===> LUMI STATISTICS: LRTE LREE LRPE LREF LRPF # of banks: 46 46 46 46 46 max # of entries: 4 37 14 37 14 min # of entries: 4 19 8 19 8 average length: 4.0 27.7 10.3 27.7 10.3 04.07.1991 ==================== H1KFOM === LREC & LRPC banks & runs. Today evening it was found little bugs at On-Line Program for H1 LUMI DAQ. After this it was produced some quantity of Runs: 5092 - 5097 with Test Pulses (without e-beam). It was corrected LREC and LRPC banks with (1<-->49 and 1<-->25). About contents of this banks at previous 46-events Run I asked do not mention. At new Runs all is OK with contents. It is not fixed the bug with rare message from Data Validity Program about bad BOS-format (it is not undestantable situation still). Most long Run was Run 5094 (25493 events). All Runs are with Start-Run-Record. 05.07.1991 ==================== F11LEV === Online bank formats ..... 1) To onliner's attention: Small LPI Internal Report is now under preparation containing some data and description of reconstruction procedure for Alternate PD. It is expected to be released tonight or tomorrow. 2) I read full cartridge with 17 runs. Some of them contain LUMI data. Interested people can look into summary below. -------------- RUN = 5070 ------------------ -------------- RUN = 5074 ------------------ -------------- RUN = 5075 ------------------ -------------- RUN = 5077 ------------------ -------------- RUN = 5079 ------------------ -------------- RUN = 5081 ------------------ -------------- RUN = 5085 ------------------ -------------- RUN = 5087 ------------------ -------------- RUN = 5091 ------------------ -------------- RUN = 5092 ------------------ LREC 0 = 1 49 0 1 5 6 100 100 1640154082 1640621632 1 300000 20482048 385 499 298137 4 0 388 0 299700 0 298444 298406 298410 0 0 0 298161 12345 0 0 0 0 0 0 0 9056 0 0 5733 303 0 0 0 0 0 0 0 0 0 LRPC 0 = 1 25 0 1 5 6 100 100 1640154082 1640621632 1 300000 20482048 385 499 298137 4 0 388 0 299700 0 298444 298406 298410 0 0 -------------- RUN = 5093 ------------------ LREC 0 = 1 49 0 1 5 6 100 100 1640154082 1640621632 1 300000 20482048 385 499 298102 4 0 388 0 299700 0 298444 298406 298410 0 0 0 298161 12345 0 0 0 0 0 0 0 12068 0 0 7741 303 0 0 0 0 0 0 0 0 0 LRPC 0 = 1 25 0 1 5 6 100 100 1640154082 1640621632 1 300000 20482048 385 499 298102 4 0 388 0 299700 0 298444 298406 298410 0 0 1 -------------- RUN = 5094 ------------------ LREC 0 = 1 49 0 1 5 6 100 100 1640154082 1640621632 1 300000 20482048 385 499 298102 4 0 388 0 299700 0 298444 298406 298410 0 0 0 298161 12345 0 0 0 0 0 0 0 35375 0 0 23279 303 0 0 0 0 0 0 0 0 0 LRPC 0 = 1 25 0 1 5 6 100 100 1640154082 1640621632 1 300000 20482048 385 499 298102 4 0 388 0 299700 0 298444 298406 298410 0 0 -------------- RUN = 5095 ------------------ LREC 0 = 1 49 0 1 5 6 100 100 1640154082 1640621632 1 300000 20482048 385 499 298102 4 0 388 0 299700 0 298444 298406 298410 0 0 0 298161 12345 0 0 0 0 0 0 0 111854 0 0 74265 303 0 0 0 0 0 0 0 0 0 LRPC 0 = 1 25 0 1 5 6 100 100 1640154082 1640621632 1 300000 20482048 385 499 298102 4 0 388 0 299700 0 298444 298406 298410 0 0 -------------- RUN = 5096 ------------------ LREC 0 = 1 49 0 1 5 6 100 100 1640154082 1640621632 1 300000 20482048 385 499 298102 4 0 388 0 299700 0 298444 298406 298410 0 0 0 298161 12345 0 0 0 0 0 0 0 124196 0 0 82493 303 0 0 0 0 0 0 0 0 0 LRPC 0 = 1 25 0 1 5 6 100 100 1640154082 1640621632 1 300000 20482048 385 499 298102 4 0 388 0 299700 0 298444 298406 298410 0 0 -------------- RUN = 5097 ------------------ LREC 0 = 1 49 0 1 5 6 100 100 1640154082 1640621632 1 300000 20482048 385 499 298102 4 0 388 0 299700 0 298444 298406 298410 0 0 0 298161 12345 0 0 0 0 0 0 0 132479 0 0 88015 303 0 0 0 0 0 0 0 0 0 LRPC 0 = 1 25 0 1 5 6 100 100 1640154082 1640621632 1 300000 20482048 385 499 298102 4 0 388 0 299700 0 298444 298406 298410 0 0 -------------- RUN = 5098 ------------------ -------------- RUN = 5100 ------------------ -------------- RUN = 5102 ------------------ 1 ===> 56229 RECORDS HAVE BEEN PROCESSED ===> LUMI statistics: LRTE LREE LRPE LREF LRPF # of banks: 51605 51605 51605 51605 51605 max # of entries: 4 49 21 49 21 min # of entries: 4 12 0 12 0 average length: 4.0 35.7 14.7 35.7 14.7 07.07.1991 ==================== H1KFOM === 10 hours of e-beam ...... Today morning we appeared at Nord Halle and observed at our beam moni- toring pictures that from yesterday morning had began some activity of accelerator. It was registered very stable E-beam from 22:20 06.07. 91 up to 8:20 07.07.91 (near 10 hours of stable beam). But... our (Usik,Soloviev,Sheviakov and Fomenko) attempts to enter into Nord Halle near 20:00-21:00 06.07.1991 were unsuccesful. It was damaged the remote control system of the door opening in Nord Halle. Asking of Sheviakov to Main Gate of DESY to do anything was registered yesterday between 20:00 and 21:00 by some people at Main Gate. This morning all was OK with this remote system and we appeared at Nord Halle but... good posibility to work (that is pity) was lost. 08.07.1991 ==================== H1KFOM === 1 hour of e-beam ........ It were two little activities of accelerator tonight. First activity was from 01:59 at 08.07.91 up to 2:40 08.07.91. The second activity - from 03:16 up to 4:24. At this time we attempted to find optimal high voltage at some channel (p2,p3,e2,e4,e5). It was changed the value of HV at e5 from 750V to 720 V. It was studied the behaviour of trigger counts with different values of thresholds for SumET and SumPD (for PD -199/60, 199/40, 199/34, 199/39, 199/46, 199/51, 199/61; for ET - 199/23, 199/29, 199/34, 199/26). The trigger counts were very low (near 0.5 Hz). It was very difficult to obtain any signifi- cant results. At the second activity of E-beam it was obtain near 5000 events for on-line analisis. We are ready to write information into IBM-cartridge but there are difficulties with calibration with low trigger counts. At the bunch statistics we see only single active bunch - with number 3 (at our local counts). Tigger was got as SumET & SumPD with thresholds at each sums. 08.07.1991 ==================== H1KFOM === 25 min. e-beam .......... It was observed third activity of E-beam from 05:05 up to 05:29 08.07. 91. Thresholds were taken as 199/40 for PD and 199/23 for ET. Trigger SumET & SumPD. Counts: 1-2 Hz Trigger and 25-11 kHz SumPD(+Water Veto) It was changed high voltage at e3 (650 V ---> 630 V). It was obtained information from Accelerator Control Room: Energy of e-beam is 26.5 GeV and bunch current 8*10**9 particles. It was attempted to calibrate our detectors with start values of all calibratiom coefficients with 1.0. Unsuccesfully - only 1 event from 165 reconstructed was entried into calibration procedure. 122 events were cut because XR(2) and YR(2) were out of range. It signes that start values of calibration coefficients are very far from true. Bunch statistics were observed at 13,17,18,...26 bunches. Bunch 17 was most significant. Counts of monitoring counters: near 8 mln. of SumPD counts (with thresholds 199/40) and 2871 event as trigger events. It was observed the next counts with different low thresholds of SumPD: 61 - 100 Hz, 44 - 15 kHz, 40 - 25 kHz. The number of triggered events were equal at each case: near 1-2 Hz. It was found the optimal procedure for moving of platform without crashing of FIC's program - try to start moving and to stop moving not simultaneously. It is proposed to write raw information into IBM-cartridge at the next activity of e-beam (without on-line calibration). 08.07.1991 ==================== H1KFOM === First Raw Data .......... Run 5190 was began at 07:12 and finished at 07:19 08.07.91. It consist of 310 events with trigger SumET & SumPD with thresholds 199/51 FOR Sum PD and 199/23 for SumET. Calibration was not carried out - don't belive to LREC and LRPC banks. 08.07.1991 ==================== F11LEV === Garbage collection? ..... I've looked into run 5190 which I.Sheviakov characterized as a garbage. Not really so. Please, read summary below and provide FULL CORRECT mapping. P.S. As usual, I produced a number of LOOK figures, which seems to be of no interest (because nobody ever wanted to look on them). 1 Summary of run 5190 ------------------- 1) LUMI statistics: LRTE LREE LRPE LREF LRPF # of banks: 310 310 310 310 310 max # of entries: 4 45 18 45 18 min # of entries: 4 24 4 24 4 average length: 4.0 34.4 11.1 34.4 11.1 2) Total # of overflowed cannels = 7 (content >= 20000) 3) Summed amplitude (ET+PD) shows 2 "peaks": one - below 600 and another - between 5000 and 13000 in units of LREE/LRPE. If this really corresponds to 26 GeV electrons, then overall cal.constant = 2.5 MeV/unit which is reasonable, however "width" ot this distribution is then about 10 GeV (sigma=4.7 GeV) - very poor... 4) From fig.10,11 one can see that pedestal threshold is below 200 both for ET and PD (note, that accuracy was limited by bin size = 200 for these figures, I will provede more accurate distribution for pedestals)... 09.07.1991 ==================== F11LEV === LUMI data ............... Data taking summary during the night shift 8/9 July 91. Beam conditions: e- energy = 26.6 GeV, Intensity = 2.1*10**10/bunch Run 5201 about 20500 events. (Normal LUMI trigger) Trigger: thresholds 199/69 (PD), 199/39 (ET) Sum_ET & Sum_PD; no E_veto in data Run 5203 with 6330 events. (Idea: stand alone offline PD calibration) Trigger: thresholds 199/169 (PD), 199/7 (ET) Sum_PD Actual mapping. --------------- Detector Channel Content ET 0...6 e_0...e_6 45 Sum_PD don't use 46 Sum_ET don't use 47 Sum_(ET+PD) don't use PD 0...3 p_0...p_3 4...7 KRS_0...KRS_3 8 Water Counter Spectrometrical channel 9 Water Counter Veto channel 12 Electron Veto Counter Inquire tel.no at HERA machine: 2750 10.07.1991 ==================== H01USA === Last news ............... Last night and today after first attempts to launch system at once the long period of tuning and debugging was started. HV for ET arm was tuned. Extra HV was in ET1 channel. Responces and statistics in the layers of ET was investigated with different vertical position of ET. It was done with period 22 mm (width of layer). There are some problems. It was decided to do it with period 5 mm for two layers. Trigger thresholds was tuning. Criteria for minimal possible threshold - appearence of structured bunch statistics instead of homogenious distribution. 10.07.1991 ==================== H1KFOM === Last news from NH ....... E-beam became very often guest at our life. Today the beam with good intensity was started near 16:30. During long time we observed very interesting pictures at bunch statistics: we looked 1 bunch (120 very often), 2 bunches (120,121), 28 bunches (93 - 120), 58 bunches (61 - 90 and 93 - 120), 107 bunches (7-12,17-93, 97-120) and once 111 bunches (previous and 3-6). From 19:06 up to 23:44 it was tuned the photon arm of our detector: we understood why at Run 5203 S.Levonian looked non monochromatic energy at the sum of PD-cells energy. E-beam was interrupted very often (from 19:30 up to 20:45, from 21:36 up to 22:06, from 22:09 up to 22:30, from 22:50 up to 23:09, from 23:10 up to 23:41). From 23:41 E-Beam is very stable with good intensity and at single (120) bunch. Up to this time (11.07.91 02:46) it was not interrupted. Very good work. After finishing of the production of the Run 5248 and 5249 it was tested the new release of the On-Line Program (we produced the short Run 5250 with near 600 events with the same trigger and threshold con- ditions as at Run 5249 - from 01:03:27 up to 01:06:38 at 11.07.1991). From 01:06:38 up to 02:51:00 Egor got the system for tuning of H1 Lumi Trigger System. 1 11.07.1991 ==================== H1KSOL === RUNS 5248,5249 .......... Energy of beam = 26.6 GeV, 9*10**10 particles in one bunch. 11.07.1991 ==================== H1KFOM === Runs 5248,5249 .......... As was agreed with S.Levonian it was produced two Runs: Run 5248: -------- Trigger SumPD only with the next thresholds (at special Egor's counts): High - 199, Low - 15. Number of events - 21429. Start of Run - 10.07.91 at 23:57:59. End of Run - 11.07.91 at 00:15:40. Before this Run it was tuned High Voltages at PD and Water Veto. The values of HV are the next: p0 = 800 V; p1 = 700 V; p2 = 780 V; p3 = 700 V; Water Veto (p8) = 570 V Events were produced from single (120) bunch. Run 5249: --------- Trigger SumPD only with the next thresholds (at special Egor's counts): High - 199, Low - 119. Number of events - 13725. Start of Run - 11.07.91 at 00:24:47. End of Run - 11.07.91 at 01:00:12. High Voltages were as at the previous Run. Events were produced from single (120) bunch. 11.07.1991 ==================== H1KFOM === Data set name ........... Today morning Bill moved our data from fast disc to cartridge. The name of data set is F11JOL.H01.TESTDATX.G0004V00. 11.07.1991 ==================== H01USA === First calibration ....... First test of calibration algorithm on the HERA beam was done. The results are in agreement with previous data got for different ET position. For S.Levonian- try to use the following coefficients for last run: PD0 - 0.53,PD1 - 0.59, PD2 - 0.61, PD3 - 0.28? ET0 - 1.05?, ET1 - 6.1, ET2 - 1.3,ET3 - 1.2, ET4 - 1.12?, ET5 - 1.08?, ET6 - 1.14?, Water(ch.8 of PD) - 0.62. ? means small statistic ==> don't belive. 11.07.1991 ==================== H1KFOM === Corrections to C.C. ..... It is important that for values of Calibration Coefficients at Mev/ ADCcounts You must to multiply above mentioned values with 3.65 for cells of ET-arm and with 3.89 for cells of PD-arm (p8 too as Water Veto). 12.07.1991 ==================== H1KFOM === No e-beam this night .... It was no e-beam this night. It was prepared the new release of the On-Line Program for H1 LUMI with recording at each event of current position of ET Movable Platform. This information is written at 4-word of LRTE-bank (at SW-flag place as position of Movable Platform at mm with multiply on 100. For example 34500 is position 345.00 mm. We hope to produce Run with scanning of Movable Platform ET along Y-axis with 5.5 mm step from 362.0 mm to 464.76 mm (last possible point). This infor- mation will be useful for calibration of ET. 12.07.1991 ==================== F11LEV === Data for PD calibration.. First guess shows that for off-line calibration of Alt. PD I need at least 4 times more events (70-80 000) at the conditions of the run 5248. However, if it is possible, trigger cuts should be more "sharp" (sofar they seem to be very soft, I mean, if one requires "energy" window 199/30, PD spectrum shows behavior similar to (150-200)/(5-40)) 13.07.1991 ==================== H1KFOM === E-beam tonight .......... It was happened many events this night. First what we made - satisfying of Levonian's request. It was produced Run 5314 with good statistics (almost 70000 events) with trigger and thresholds equal as at Run 5248. 1 Second step - we wrote two Runs (for comparison) 5318 and 5319 (on proposition of Egor) at equal intensity of accelerator (almost). First Run - 5318 with trigger SumPD & anti Water Veto with minimal thresholds (199/22) for PD and thresholds 2 for both Water Vetos. The second Run - 5319 with trigger equal as 5314 (but with another intensity of beam). This step was made for study of influence of anti water veto at trigger on sumP spectrum. Third step - scanning of position ET along Y-axis. At each point it was made three values of thresholds for ET+PD. During making of the third step we looked the spectra of individual ET-cell response and found the difference of response at equal condition. We carried out the allignement of the all cell response with changing High Voltage. Fourth step - we produced Run 5326 with trigger SumP & SumE & ET+PD WITH NEW HIGH VOLTAGE MAPPING. THE NEXT RUN 5327 WAS PRODUCED WITH AS- king of Bill Haynes for debugging of optical ring. But it consits of the same events as at previous (only first 1000-2000 events are wrong - we forgot to change so called shifts 91/43 at Show Event Card) Run 5314: -------- Trigger SumPD only with the thresholds (at special Egor's counts): High - 199, Low - 19. Counts 310/400 (Trigger/SumPD). Number of events - 68623. Start of Run - 13.07.91 at 01:20. End of Run - 13.07.91 at 02:17. Single bunch - 90. Run 5318: --------- Trigger SumPD & anti Water Veto. Thresholds 199/22 (PD), 2 - for both Water Vetos. Counts 300/4000 (Trigger/SumPD). Anti Water Veto = Anti (Veto1 or Veto2). Number of events - 10693. Start of Run - 13.07.91 at 05:36. End of Run - 13.07.91 at 05:44. Run 5319: --------- Trigger SumPD only. Thresholds 199/22 (PD). Counts 2000/3500 Hz (Trigger/SumPD). Number of events - 10083. Start of Run - 13.07.91 at 05:49. End of Run - 13.07.91 at 05:57. Run 5322: --------- Trigger SumPD & SumET & ET+PD Thresholds 199/24(PD), 198/10(ET), 198/24 or 198/63 or 198/81 (ET+PD) Counts 220/2500 or 80/600 or 220/2500 Hz (Trigger/SumPD). ET-detector was moved and stopped at the following Y-positions: 362,373,384,395,406,417,428,439.450 and 461 mm. At each point it was changed (three time) the value of minimal thres- hold for (ET+PD) (see earlier). Number of events - near 60000. Start of Run - 13.07.91 at 06:20. End of Run - 13.07.91 at 07:10. After this point we alligned the responses of e0-e5 through High Vol- tage changing. The last values are: e0 - 670V, e1 - 620V, e2 - 670V, e3 - 610V, e4 - 620V, e5 - 590V, e6 - 660V. After this point it was changed the contents of L1Keep-counter at TSTC-bank. It was the quantity of events with SumPD withing threshold interval. Now it is the count of WaterVeto hits (without any depen- dence from any thresholds). This counter will be useful during investigation of dependence of calibration coefficionts from counting rates. Run 5326: --------- Trigger SumPD & SumET & ET+PD. Thresholds 199/26 (PD), 198/10 (ET), 198/6 (ET+PD) Counts 30/500 (Trigger/WatereVeto) Number of events - 37033. Start of Run - 13.07.91 at 09:51. End of Run - 13.07.91 at 10:21. 1 Run 5328: --------- Trigger SumPD & SumET & ET+PD. Thresholds 199/26 (PD), 198/10 (ET), 198/6 (ET+PD) Counts 30/500 Hz (Trigger/SumPD). Number of events - 20584. Start of Run - 13.07.91 at 10:25. End of Run - 13.07.91 at 11:00. At this Run Some quantity of events (at begin of Run are wrong due to mistake with putting of needed option (so called Shift FADC at Show Event Card - must be 91/43 but were 81/33). As seems we understood that all is OK in principle with our detectors. We found so-called bremsstrahlung spectra of photon and spectra of tagged electrons at histos of sum PD and sum ET. All from us aggreed that absolutely needed to study the behaviour of calibration coefficient with changing of counting rates (beam inten- sity). Egor changed counter L1Keep as monitor of beam intensity. 15.07.1991 ==================== H1KFOM === Runs 5351,5352 .......... It were produced two Runs during Sunday shift: Run 5351: --------- Trigger SumPD & SumET & anti Water Veto. Anti Water Veto = Anti (Veto1 or Veto2). Thresholds 199/25 (PD), 199/10, 2 - for both Water Vetos. Counts 10/10000 (Trigger/WaterVeto - as beam indicator) HV - as at Runs 5326 and 5328. Detectors positions - 428 mm (ET) - the middle of e3-layer at beam plane; 380 mm (PD) - new position of PD. First Run with this position. Number of events - 16915. Start of Run - 14.07.91 at 14:37. End of Run - 14.07.91 at 14:59. Run 5352: --------- Trigger SumPD & SumET & anti Water Veto. Anti Water Veto = Anti (Veto1 or Veto2). Thresholds 199/25 (PD), 199/10, 2 - for both Water Vetos. Counts 3-15/800-900 Hz (Trigger/WaterVeto - as beam indicator) HV - as at Runs 5326,5328,5351 Detectors positions - 428 mm (ET) - the middle of e3-layer at beam plane; 380 mm (PD). Number of events - 44495. Start of Run - 14.07.91 at 15:03. End of Run - 14.07.91 at 17:02. Counts at the end of Run ( 1-8/640 Hz). Beam intensity was decreased slowly during Run. It is possible to look the changing of beam inten- sity through L1Keep-member of TSTC-bank and revolution counter of this bank. Revolution counter has 10MHz/220 frequency (constantly). L1Keep counter is proportional to beam intensity. This two Runs was written with hope to fix real bremstrahlung events. At on-line histos we saw good sumET and sum PD spectra (as seems for us). It were made very not distinct and preliminary estimations of calibration coefficients: for ET-cells all coefficients are near 5 MeV/ADC count; for PD-cells all coefficients are around 2 MeV/ADC count. Soloviev's algorithm of calibration was moved from IBM3090 to MacII and FIC8230. At LSC-FORTRAN-version it gave very good result of defining of calibration coefficients on the 800 LUMI-events from data set simulated by Levonian. All attempts to use this algorithm for real events (from 23:34 14.07 up to 3:00 15.07) were unsuccesful. Main reasons were at little mistakes at moving program from LSC-FORT- RAN to RTF-FORTRAN (mainly made by Fomenko). But we hope that the victory waits for Yura at nearest future. Good wishes to Yura at his Birth Day. Happy Birth Day to You. 15.07.1991 ==================== H01USA === C.C. .................... This night test of calibration algorithm on the HERA beam was done for new version of calibration trigger. For current version of HV there are following calibration coefficients (Because of beam dump the data are only for one position of ET ==> 3 callibrated channels): PD0 - 0.43,PD1 - 0.456, PD2 - 0.52, PD3 - 0.99 ET0 - 1.69?, ET1 - 1.51, ET2 - 1.08,ET3 - 1.174 ET4 - 1.57?,ET5-1.05?, ET6 - 1.05?, Water(ch.8 of PD) - 0.671. ? means small statistic ==> don't belive. 1 16.07.1991 ==================== H1KFOM === About future long Run ... I carried out the negoutiations with DC team member (onliner Steve) about principle posibility to get the H1 CDAQ for 10 hours for data taking with H1 LUMI branch only. Steve said that it is possible but we must put message about this for 4-5 hours before this future Run. We must do the next steps before long Run: - to carry out the calibration and be shure that it is right; - to align the responces of ET-cells and PD-cells through High Voltage changing; - to carry out the calibration with new values of High Voltage; - to do needed tuning of trigger analog sums(SumPD,SumET and SumPD+ET) through shielding of different attenuators with orientation on value of calibration coefficients; - to do some changing at On-Line Program for posibility of work with different triggers at one Run (may be it will be needed to use LRTE-bank members as labels of triggers - for example "1" at first member - "Bremstrahlung Trigger", "2" - "Photoproduction trigger"). Egor said that it is possible (in principle) to do the trigger for photoproduction as was proposed by Levonian&Andreev (maximal hit at not central layer). 17.07.1991 ==================== H01USA === Social request .......... Remind You that now after calibration we must do some simple measure- ments before writing "runs with the big physics". First of all we need to investigate "envirement" in which we work: - the energy spectra in electron arm: -- total - all what is absorbed in ET from all bunches; Trigger: SumET with minimal thresholds (f.e. 3); -- in filling bunch - from bunch statistic to find filling bunch and to add software trigger on coincidence with this bunch for Brems- histos; - the energy spectra in photon arm: -- total - all what is absorbed in PD from all bunches; Trigger: SumPD with minimal thresholds (f.e. 3); -- in filling bunch - from bunch statistic to find filling bunch and to add software trigger on coincidence with this bunch for Brems- histos; - the bremsstrachlung spectra for different triggers: -- ET&PD&(filling Bunch) with minimal and standart thresolds; -- ET&PD&AntiWater . -- ET&PD&AntiWater&(SW cut for sum energy +/- 2-3 sigma; - to calibrate thresholds levels in GEV. - coordinate distributions of hits on the detector faces; for the last - to turn ET. Poka 17.07.1991 ==================== H1KFOM === Run 5375 ................ This night it was appeared very waiting event - calibration of detectors. We all agreed that calibration coefficients are right. Its values: p0 = 0.883, p1 = 0.919, p2 = 0.939, p3 = 0.899; e0 = 0.979, e1 = 0.937, e2 = 1.100, e3 = 1.030, e4 = 0.986, e5 = 1.040, e6 = 1.00. Remember that for MeV/ADC counts You must multiply all PD coeff. on 3.89 and all ET-coefficients on 3.65. It was installed the new set of high voltages: p0 - 700 V; p1 - 650 V; p2 - 720 V; p3 - 730 V; e0 - 670 V; e1 - 620 V; e2 - 650 V; e3 - 640 V; e4 - 640; e5 - 600 e7 - 660 V. Run 5375: --------- Trigger SumPD & SumET & anti Water Veto. Anti Water Veto = Anti (Veto1 or Veto2). Thresholds 199/24 (PD), 199/11, 3 - for both Water Vetos. Counts ? / ? (Trigger/WaterVeto - as beam indicator) HV - new. Detectors positions - 428 mm (ET) - the middle of e3-layer at beam plane; 380 mm (PD). Number of events - 4159. Start of Run - 17.07.91 at 05:43. End of Run - 17.07.91 at 06:00. 1 17.07.1991 ==================== F11LEV === Last efforts ............ Hello everybody. As you know a few days only left to the end of this e-run. Let's make final efforts to get as much useful information as possible. Before trying to summarize my requests to online side for the future long term analysis (up to September Collaboration), I would like to say few words about present status at the offline side... 1. Based on the experience of the analysis of 14 runs (330.000 events) taken from 4/7 to 15/7 I can say, that during this period many things have been improved and generally system is ready for getting and processing reasonably good data. a) Off-line software is able to read, understand and analyse online files. The following modules/jobs exist, are tested and used: -- extracting of lumi data from online IBM cartridges and creation of datasets on disk or cartriges for further analysis All these files have the following naming convention: F11LEV.LUMI91.CRTxxxxx for files kept on cartridges F11LEV.LUMI91.RUNxxxxx for files kept on fast disks where xxxxx stands for run number, e.g. F11LEV.LUMI91.RUN05314 Command lc F11LEV.LUMI91 gives you an overview over all existing files with LUMI data at DESY IBM. -- Simple but sufficient reconstruction exist both for PD and ET alternate configuration. Partially it is installed already on the online computer, but can be used there completely, since it is really fast and trivial. -- An analysis job can process raw lumi data and produce a lot of uselul LOOK figures including: - beam parameters (bunch picture, intensity, ...) - amplitudes before and after calibration for any detector combination - reconstructed quantities (coordinates, energy) - different kind of correlation plots, etc. These LOOK figures can be aftewards displayed, analysed and plotted interactively. Several LOOK macro files exist allowing automatically to get a standard sets of figures for each run in a very simple and user friendly way. Of course, this job will be further developping according to our rising knowledge about detector and requirements for more sofisticated analysis... -- Besides, some additional small jobs have been prepared - to check calibration quality for gamma arm (PD & VC) - to retrieve and fit detector resolution, etc. b) I have produced many pictures which need to be summarized, but no time for consequtive analysis, this will be done later. Only those results, which influence on our data taking strategy are being analysed immediately together with the online experts. 2. I still have some extra requests for online community. Please, consider the possibilities for the following: A.Fomenko --------- - still wrong content of calibration banks in SRR, please fix! - include reconstruction piece for ET (I could bring code today) - if possible remove F-banks from the event in order to have more events on disk/cart available. Now an average event size is 0.8 kb so we are limited by 250.000 events/run = 200 Mb = 1 cartridge. Without FADC banks we could have 2 times more (0.5 mln per run). This is important at least for one run which I need (see item 3. below). I(or E?).Sheviakov ------------------ - some times ago we again discussed the possibility to fill 220 separate counters for different bunches. Is it possible already now to transfer this information to offline (like L1keep counter in TSTC bank, but 220 ones)? As a temporary solution, Fomenko could create a special BOS bank for that. 1 Yu.Soloviev ----------- - please get your calibration procedure running offline with modern s/w environment (F-pack I/O etc.). You can simply provide the calibration code as a separate module, which I could call inside my analysis job. Let's meet and discuss this. A.Usik ------ - the same request as for Yura. 3. Now come to the main point. Which kind of the data we need and could get before the end of this run? We already discussed this once. Based on the existing data I would propose three main data classes: ------------------------------------------------------------------- 1) High statistics run (300-500 thousands of events) in one go whith the trigger: PD only, thresholds: 199/(1-3) at the stable e-beam of high (!!!) energy (26 GeV, not 5 or 12 !) 2) Pure lumi events. Trigger ET & PD & aVC (& ET+PD if possible) 3) Photoproduction candidates. Trigger ET & no(PD,VC). ------------------------------------------------------------------- For 2nd and 3rd data to record as much events as possible, but in ALTERNATE ORDER, say several runs with 20.000 events per run, (or 15-20 min/run depending on the trigger rate): lumi run --> photo run --> lumi --> photo etc. This will ensure almost identical run conditions for 2 and 3 event classes and protect us against accidental beam switching off... All three sets of events must be taken at the same HV for all channels. All other exp. conditions which are depending on us also should be as identical as possible (detector positions for inst.). Of course, if somthing wrong will happen you should react properly, but please, DON'T TOUCH A WORKING SYSTEM without urgent necessity! Since aim of events from 2nd and 3rd classes is evident, I will explain what I expect from the first high statistics run. This is very similar to the 5314 run, which was so far most useful for me (does not mean, that most useful for everything). It showed that we indeed could see pure bremsstrahlung spectrum on PD (+VC), but low energy part (below 5-6 GeV) was absent because of too high lower threshold for PD trigger. Also calibration and HV were not perfect at all at this run. I expect to study with new run the possibilities of LUMI gamma arm: a) lowest possible energy of gammas to be detected and reconstruc- ted (important for rad.corr. physics) b) study/check energy resolution of PD in wide E range c) study spectrometrical responce of VC (compare with MC), this information we never will get with event classes 2 or 3 d) make independent check of calibration quality for PD e) study HERA beam parameters (note, that so far we still do not have enough off-line data to analyse not only our detectors but also HERA beam, which by the way is our main task within collaboration!) namely: - full bunch picture, including those bunches you usually call garbage, - time behavior of intensity inside individual bunches (pro- vided 220 separate counters will be available from Egor), - energy spectrum for different bunches (this is available anyway, only allow these small nice bunches to reach me, don't throw them away with your bloody high threshold!) Why so huge statistics? ----------------------- Again, from the run 5314 (as well as from theory of bremsstrahlung) is clear, that in order to cover whole energy interval and at the same time to have at least 5% stat. accuracy at the high-end we need approx. 500.000 events which means 500000/20 = 25000 sec = 7 hour of data taking if Fomenko is not able to speed up procedure, say to the 50 Hz (can the removing of FADC banks help?) Please, take it seriously. Such a run could give many other useful information, which can be used for preparation to the next test run in October'91. 1 To summarize: ------------- 1) Long run at high energy (and hopefully stable) HERA beam with a widely opened mouth in a gamma arm, without any suppression of smaller bunches (I can make all selections offline) and at highest possible data transferring rate to the CDAQ. Such a run (4-7 hours of work) must be agreed upon in advance not only with H1 subdetectors paticipating in present tests, but also with machine people, at least to get reliable predictions for the next few hours... 2) Lumi and photo events taken in identical conditions by short runs in alternate order, with 10-20 thousands events/run, depending on the actual trigger rate. For these event classes statistics is restricted only by the available time left to the end of the HERA run. 18.07.1991 ==================== H1KFOM === Runs 5410 - 5413 ........ Tonight we were happy due to very stable and long time living e-beam. As it was requested by Levonian and was discussed and agreed with all our on-line community members we had produced some quantity of Runs during this night. First mile-stone was installed with Runs 5410,5411. It was appeared first message at H1 Run Logbook about "Photoproduction (standalone) trigger" for Luminosity branch of the H1 detector. Calibration coefficients are recommended by Sasha Usik to use the same as at Run 5375 but he now observes wonderful bremsstrahlung peak at the current (5413) Run and proposes tomorrow to do "on-line" calibration at "off-line"-environment to compare its with yesterday set of calibration coefficients. We now observe fantastically beautiful bremsstrahlung spectra at the on-line SumPD+WaterVeto histo and hope that You will extract calibra- tion coefficients for PD with fitting with theoretical curve(Run 5413) At the on-line histo "SumP+SumE+EWaterVeto" at Run 5413 it was observed that with yesterday calibration coefficients we have peak at 26.37 GeV even at the poor statistics. It means that Sasha made very good tool for calibration coeffisients on-line finding. We now (else one) are shure that these coeffisients are right. It was observed very nice histo for SumET-energy: just the same as was got yesterday before "pure" "Bremstrahlung Trigger" - the same energy cuts: at 5GeV and 15-16GeV. The statistics at this energy region consists of more then 50% of full statistics. It means that registrated photons with this trigger are the photons from the "pure" bremstrahlung of beam elecrons on residual gas in supposed interaction point. As You remember this trigger was born today at negoutiations of Levonian with On-Line community for registration of all possible photons at PD-arm of H1 LUMI detector. In principle we can produce Run with "ET-arm spectra Trigger". From preliminary observations at On-Line environment of SumET-spectra with above mentioned Trigger when we observed big contribution into energy spectra so-called "off-momentum" electrons the "pure" brems. spectra with "PD-arm spectra" Trigger was unexpectable souvenire. At "Photoproduction (standalone) Trigger" data taking we observed very interesting picture with bunch statistics - we had events from all bunches almost (we suppose that may be this is "off-momentum electrons" background). This type pictures we observed earlier at low thresholds at SumPD or SumET. It were observed 4 bunches at this serie of Runs: 9/11/13/15 OR 8/10/12/14 (for different triggers ---> it depends). At 4:00 18:07.91 it was little interruption of e-beam activity (this manipulation was planned and we knew about this from phone talking with Central Control Room of HERA) but we do not interrupt the current data taking at Run 5413. You can see very interesting picture at behavior of Your beam-intensity pictures. This interruption was after 157819 event. After this we had near 10 minutes pause and it was began new injection of beam but at another bunches (172/174). At 4:22 we had counts 2500/3200 Hz. From phone talking with accelerator peoples we know that energy of beam was 26.66 GeV. Starting beam current (near 0:00 18.07.91) was 2.3 mA. At 2:09 18.07.91 this current was decreased to 0.7 mA. At 4:36 it were added else two bunches (150 and 154). Beam Intensity was changed without jumping. 1 Run 5410: -------- Trigger: "Photoproduction (standalone) Trigger" SumET & antiSumPD & antiWaterVeto & antiCentralLayerET Thresholds: 199/11 (ET), 199/23 (PD), 8 and 8 (WaterVeto), 7 (Central LayerET). Counts - 500/15000 Hz (Trigger/WaterVeto). Position of ET-Movable Platform - 428.0 mm (the center of ET3 layer as we supposed from previous experience). High Voltage - the same as at last (5375) run. We did not touch. Number of events - 11185. Start of Run - 18.07.91 at 00:28. End of Run - 18.07.91 at 00:38. Run 5411: -------- Trigger: "Photoproduction (standalone) Trigger" SumET & antiSumPD & antiWaterVeto & antiCentralLayerET Thresholds: 199/11 (ET), 199/23 (PD), 8 and 8 (WaterVeto), 7 (Central LayerET) - the same as at previous Run. Counts - ?/? Hz (Trigger/WaterVeto) it were not fixed. Position of ET-Movable Platform - 424.0 mm (the center of ET3 layer as we looked from Levonian's Y-ET histo at Run 5375). High Voltage - the same as at last (5375,5410) run. We did not touch. Number of events - 21294. Start of Run - 18.07.91 at 00:43. End of Run - 18.07.91 at 01:00. Run 5412: -------- Trigger: "Bremsstrahlung Trigger". SumPD & SumET & antiWaterVeto Thresholds: 199/23 (PD), 199/11 (ET), 8 and 8 (WaterVeto) Counts - 15-20/9500-10000 Hz (Trigger/WaterVeto). Position of ET-Movable Platform - 424.0 mm (the center of ET3 layer as we looked from Levonian's Y-ET histo at Run 5375). High Voltage - the same as at last (5375,5410,5411) Runs. Number of events - 12809. Start of Run - 18.07.91 at 01:10. End of Run - 18.07.91 at 01:27. Run 5413: -------- Trigger: "PD-arm Spectra Trigger". WaterVeto only Thresholds: 8 and 8 (WaterVeto) Counts - 3500/5000 Hz (Trigger/WaterVeto). Position of ET-Movable Platform - 424.0 mm (the center of ET3 layer as we looked from Levonian's Y-ET histo at Run 5375). High Voltage - the same as at last (5375,5410,5411,5412) Runs. It were changed the so-called "FADC windows-delays" from 93/41 to 83/31 (trigger influence). Number of events - 355334. Start of Run - 18.07.91 at 01:44. End of Run - 18.07.91 at 07:07. At this Run it was 10 min. interruption of beam intensity after 157819 events and new injection of e-beam was made without any pause of Run. The bunch numbers were changed from 8/11/13/15 to 170/174 and after some time two bunches were added (150/154). I am sorry for my unactivity with three requests of Levonian: 1) I know about bad contents of LREC and LRPC banks but we always forgot about needed manipulation before the next start run. I must do more simple environment for start of the next run. It will be made later on. 2) I am ready to include into the On-Line Program for H1 LUMI subde- tector the new code for reconstruction of ET-incoming point etc. but we forgot about this posibility yesterday evening when Sergey visited the Nord Halle. 3) Mode 6 of data taking of LUMI-data was tested with H1 CDAQ. On the first view without any problem but our on-line community was afraid to use this mode at very long Run (for short Run it was not very needed). This mode must be tested at any short Run and after this must be tested at Off-line environment and after this can be put the "green street" for this mode of data taking for us. We shall try to write any Run tomorrow with this mode (not long) and ask You to test this data with attention. In principle we wrote some data (test light pulses) at Run 5405, Run 5406 at this mode but data are not similar to anything at previous Runs. 1 18.07.1991 =========== H01USA & H1KFOM === First "Physics" at HERA.. After this night (when the first sun shine had appeared) we realized that it was a great night. Quality of recorded events which we observed at On-Line allowes to do the conclusion that the first run with "Photoproduction (standalone) Trigger" was succesful (we are shure in our data). So it was FIRST PHYSICAL RUN on HERA-beam. Bill marked our recording at H1 Run Logbook with the same words. 18.07.1991 ==================== F11LEV === Latest data analysis .... I've copied all data taken last night to my files partially on disks and partially on cartridges. Main message: all that was done according to my reccomendations gave an excellent result, while any deviations from them made me extra difficulties. 1) I managed to keep on fast disks only 61.000 events from the run 5413 ("full bremsstrahlung trigger"), since they still contain redundant information (FADC banks). Full run will occupy 2 cartridges, but sofar only 190.000 events have been copied to cartridge before all H1 time was used up. Thus I save all together 251.000 events from this run and next job to copy the rest is waiting somewhere 10-12 in a queue; perhaps it will start only tomorrow. 2) A barrel beer from those who did not believe in low energy part of bremsstrahlung: on 15% of statistics I got a brilliant energy dis- tribution which coincides with the theory starting at least from 1 GeV or even bit less! I believe, that this run will give a lot of useful information which I am going to analyse for a long time. 3) I did not look into other data so far, because I want to redesign before my analysis program to make it more transparent for other eventual users, and also to include calibration modules from Usik and Soloviev. Another reason: H1 community already used up daily kontingent on DESY IBM - as you could know, this week is devoted to the tuning and debugging of H1REC program, which will be released next week for 2-3 months of mass production and physics study, so this job has highest priority within collaboration... 4) Calibration seems to be ok, but not fully perfect: results could be improved by off-line calibration. Let's meet again in NH tonight to agree on further program... 19.07.1991 ==================== F11LEV === Length of the runs ...... Only two brief remarks today. 1) Of course, we are still very far from physics, so don't be too happy with so called "photoproduction trigger". This is in fact 99% of background + 1% of scattered e- from real photoproduction. We have to do much to understand what kind of electrons hit ET, and what at all is going on in our electron arm. 2) Based on the experience of the run 5413 I would like to ask you to produce from now on only runs shorter than 100.000 events, because I have problems with n-tuple size at the analysis stage. From the other side, 10.000 events per run seem to be lower limit taking into account statistical considerations. 19.07.1991 ==================== H01USA === Remarks on photo trigger. If we'll compare two triggers: - antiSumPD&antiPDveto&SumET&antiCentralLayerET (so called standalone photoproduction trigger) - SumET&antiCentralLayerET we could estimate the background contribution in first one from elect- rons scattered at curved part of electron trajectory before and past straight one near the IP. The photons from these electrons don't hit PD ====>so it looks for us as photoproduction events. From on-line histos for modified second trigger ( SumETonly) it seems that this events are the main part of statistics (very poor statistic in PD histos). 19.07.1991 ==================== F11LEV === Noch zwei remarks ....... 1) Usik, please don't occupy first column in the logbook, since it is already used for line control during printing! I 've got tired to correct text after you... 2) Unfortunatelly you missed the development of my idea concerning stand alone photo-trigger during last year. Final numbers are quite pessimistic (you can find them in my reports at different photopr. meetings: HERA WS, H1). Namely, even at ideal e-beam and other machine conditions, background to photoproduction from ep->epgamma events is huge. When using |Y_cut| = 1.1 cm (one central layer) the contamination to signal is 1000-1500%. In order to get background at the level of 50% or less |Y_cut|=4cm is necessary. Nevertheless, this should not prevent us from getting even such a dirty data with "photopr. trigger". 1 19.07.1991 ==================== H1KFOM === 120 Hz LogRate possible.. Today Bill promised that we can write our events to IBM with rate near 120 Hz (he made some improvements at his programm - blocking of short events before sending to IBM etc.). It seems that we can take data (for very fast Triggers) at 6 times faster. As You remember before this day we had 20 Hz as maximum lograte. 20.07.1991 ==================== H1KFOM === Runs 5496 - 5504 ........ The promise of accelerator people about 30 GeV concerned only the first stage of this seance of E-beam ( at 21.00 19.07.1991 the energy of E-beam was returned to 26.6). But we looked at our SumEnerg spectra this energy before 21:00. It was the attempt to calibrate the thresholds of different Trigger's conditions (SumET, SumPD, SumPD+SumET). Very preliminary calibration of thresholds was done.For example 1 count at SumET equals to 260MeV. Before middle of night Sasha Usik carried out the calibration without moving of ET-table. Trigger for calibration was SumPD & SumET & antiWaterVeto with thresholds 198/24(PD), 198/10(ET) and 8 8 for Water Veto counters. The next values of Calibration Coefficients were produced: p0 = 0.64 (was 0.88 at previous calibration 17.07.91) p1 = 0.89 (was 0.92 at previous calibration 17.07.91) p2 = 0.88 (was 0.94 at previous calibration 17.07.91) p3 = 0.98 (was 0.90 at previous calibration 17.07.91) e1 = 0.87 (was 0.94 at previous calibration 17.07.91) e2 = 0.94 (was 1.10 at previous calibration 17.07.91) e3 = 1.09 (was 1.03 at previous calibration 17.07.91) The rest of coefficients was not calibrated and not changed. After middle of night we started the executing of our Run-program: 0) Mode 1 "Photoproduction (standalone) Trigger" (as at Run 5410) with low statistics - near 10 000 events; 1) Mode 1 "Photoproduction (standalone) Trigger without anti- CentralLayerET" with low statistics - near 10 000 events; 2) Mode 6 "Photoproduction (standalone) Trigger without anti- CentralLayerET" with low statistics - near 10 000 events; 3) Mode 1 "Photoproduction (standalone) Trigger" (as at Run 5410) with threshold for ET near 10 GeV (near 39 Egor's counts preli- minary) with low statistics - near 10 000 events; 4) Mode 1 "Photoproduction (standalone) Trigger" (as at Run 5410) with threshold for ET near 15 GeV (near 57 Egor's counts preli- minary) with low statistics - near 10 000 events; 5) Mode 1 "ET-arm spectra" - trigger SumET only with low threshold with low statistics - near 10 000 events; 6) Mode 1 "ET-arm spectra" - trigger SumET & anti-CentralLayerET with the same threshold with low statistics - near 10 000 events; 7) Mode 1 "Bremsstrahlung Trigger" - SumPD & SumET & antiWaterVeto with good statistics - near 100 000 events; Levonian asked to include SumPD+SumET as fourth part of trigger but we don't undestand how this part is working (sorry). 8) Mode 1 "SumPD & antiWaterVeto" ( as at Run 5318) with 4-5 Gev low threshold at SumPD with good statistics - near 100 000 ev; 9) Mode 6 "PD-arm Spectra" ( as at Run 5413) with good statistics - near 100 000 events; The (3) & (4) points of our Run Plan were not done because threshold calibration is not right now (very preliminary). The (6) point of our Run Plan was skipped due to stopping of E-Beam at 01:23.After re-switching on (at 02:35) we decided to make "long" Runs. The (6) point was realized as Run 5504 after finishing of "long" prog ram. The (3) & (4) were not made, and as we hope then Run 5496 includes this condition and it is possible to select this trigger at off-line. Run 5496: -------- Trigger: "Photoproduction (standalone) Trigger" SumET & antiSumPD & antiWaterVeto & antiCentralLayerET Thresholds: 199/10 (ET), 199/24 (PD), 8 and 8 (WaterVeto), 7 (Central LayerET). Counts - 115/4300 Hz (Trigger/WaterVeto). Position of ET-Movable Platform - 424.0 mm (the center of ET3 layer as we looked from Levonian's Y-ET histo at Run 5375). High Voltage - the same as at previous Runs. We did not touch. 1 Number of events - 31734. Start of Run - 20.07.91 at 00:03. End of Run - 20.07.91 at 00:12. LogRate - near 60 Hz. It was three bunches (170,171,172). Run 5497: -------- Trigger: "Photoproduction (standalone) Trigger without antiCentrLayerE SumET & antiSumPD & antiWaterVeto Thresholds: 199/10 (ET), 199/24 (PD), 8 and 8 (WaterVeto) Counts - 700/3000 Hz (Trigger/WaterVeto). Position of ET-Movable Platform - 424.0 mm (the center of ET3 layer as we looked from Levonian's Y-ET histo at Run 5375). High Voltage - the same as at previous Runs. We did not touch. Number of events - 87847. Start of Run - 20.07.91 at 00:28. End of Run - 20.07.91 at 00:39. LogRate - near 110 Hz. It was three bunches (170,171,172). Run 5498: -------- Single changing from previous Run - Mode 6 of Bank Set (without so-called F-banks). Especially for testing. Trigger: "Photoproduction (standalone) Trigger without antiCentrLayerE SumET & antiSumPD & antiWaterVeto Thresholds: 199/10 (ET), 199/24 (PD), 8 and 8 (WaterVeto) Counts - 700/3000 Hz (Trigger/WaterVeto). Position of ET-Movable Platform - 424.0 mm (the center of ET3 layer as we looked from Levonian's Y-ET histo at Run 5375). High Voltage - the same as at previous Runs. We did not touch. Number of events - 16514. Start of Run - 20.07.91 at 00:42. End of Run - 20.07.91 at 00:44. LogRate - near 110 Hz. It was three bunches (170,171,172). Run 5499: -------- Single changing from previous Run - Mode 1 of Bank Set (with so-called F-banks). After this all Runs will be at Mode 1. Trigger: "ET-arm spectra" Thresholds: 199/9 (ET) Counts - 700/2300 Hz (Trigger/WaterVeto). Position of ET-Movable Platform - 424.0 mm (the center of ET3 layer as we looked from Levonian's Y-ET histo at Run 5375). High Voltage - the same as at previous Runs. We did not touch. Number of events - 15610. Start of Run - 20.07.91 at 01:15. End of Run - 20.07.91 at 01:18. LogRate - near 98 Hz. It was three bunches (170,171,172). Run 5500: -------- Trigger: "Bremsstrahlung Trigger" ==> SumPD & SumET & antiWaterVeto Thresholds: 199/24 (PD), 199/10 (ET), 6 8 (WaterVeto). Counts - 20-35/12300 Hz (Trigger/WaterVeto). Position of ET-Movable Platform - 424.0 mm (the center of ET3 layer as we looked from Levonian's Y-ET histo at Run 5375). High Voltage - the same as at previous Runs. We did not touch. Number of events - 101225. Start of Run - 20.07.91 at 02:50. End of Run - 20.07.91 at 04:56. LogRate - as trigger count. It was four bunches (168,170,172,174). Run 5501: -------- Trigger: "PD-arm spectra" ==> SumPD & AntiWaterVeto (as at Run 5318). Thresholds: 199/24 (PD), 6 8 (WaterVeto). Counts - 60/5000 Hz (Trigger/WaterVeto). Position of ET-Movable Platform - 424.0 mm (the center of ET3 layer as we looked from Levonian's Y-ET histo at Run 5375). High Voltage - the same as at previous Runs. We did not touch. Number of events - 90377. Start of Run - 20.07.91 at 05:21. End of Run - 20.07.91 at 06:09. LogRate - as trigger count (37 Hz at begin of Run at 25 at the end) It was four "real" bunches (168,170,172,174) and "false" (163,165,167, 169). Thresholds for SumPD as minimal as possible. After decreasing lower then 24 it was began big quantity of "empty"-triggers. 1 Run 5502 (with Egor's proposition) - without previous Run Plan -------- Trigger: "PD-arm spectra" ==> SumPD only (as at Run 5319). Thresholds: 199/24 (PD). Counts - 750/4500 Hz (Trigger/WaterVeto). Position of ET-Movable Platform - 424.0 mm (the center of ET3 layer as we looked from Levonian's Y-ET histo at Run 5375). High Voltage - the same as at previous Runs. We did not touch. Number of events - 16636. Start of Run - 20.07.91 at 06:13. End of Run - 20.07.91 at 06:16. LogRate - near 116 Hz. Thresholds for SumPD as minimal as possible. After decreasing lower then 24 it was began big quantity of "empty"-triggers. Run 5503: -------- This Run was taken with MODE 6 of bank set (without so-called F-banks) Trigger: "PD-arm Spectra Trigger". WaterVeto only Thresholds: 8 and 8 (WaterVeto) Counts - 1500/2500 Hz (Trigger/WaterVeto). Position of ET-Movable Platform - 424.0 mm (the center of ET3 layer as we looked from Levonian's Y-ET histo at Run 5375). High Voltage - the same as at previous Runs. It were changed the so-called "FADC windows-delays" from 93/41 to 83/31 (trigger influence). Number of events - 108427. Start of Run - 20.07.91 at 06:23. End of Run - 20.07.91 at 06:39. Run 5504: (pair to Run 5499) -------- This Run was taken with MODE 1 of bank set. Trigger: "ET-arm Spectra Trigger". SumET & antiCentralLayerET Thresholds: 199/9 (ET) and 7 (CentralLayerET). Counts - 130/2300 Hz (Trigger/WaterVeto). Position of ET-Movable Platform - 424.0 mm (the center of ET3 layer as we looked from Levonian's Y-ET histo at Run 5375). High Voltage - the same as at previous Runs. Number of events - 17325. Start of Run - 20.07.91 at 06:47. End of Run - 20.07.91 at 06:52. We need the new Run Plan at nearest shifts. Welcome any ideas. 20.07.1991 ==================== F11LEV === Latest data analysis .... Ok boys, you are producing data faster then I am able to analyse them carefully. So I stop processing until further improvements of analysis chain. Taking into account, that H1 community waits for the next LOOK release, I estimate restarting time for LUMI data analysis at the end of the next week. This should include off-line recalibration using all available algorithms. Therefore, A.Usik and Yu.Soloviev are again asked to provide their code in any reasonable form. Today I've looked into runs 5501,5503. I was mainly interesting in non- interacting bremsstrahlung photons (trigger: PD & aVC -> run 5501). This was new kind of data (run 5318 only gave me an idea for this, but small statistics and bad calibration exclude this run from the further analysis). Indeed, as I expected energy resolution became better (this is clearly seen at the high energy part of bremsstrahlung spectrum). Just to remind you: in this run only PD enery resolution should come into game, while in run 5413 also (filter & Veto) system contributed. As far as low energy part is concerned, it looks a bit strange for me, perhaps Igor should look on this figure to explain trigger behavior: spectrum rapidly goes down below 10-11 GeV, but still shows quite some entries around zero (say, E<2 GeV). Also 11 GeV threshold is too high. Calibration seems to be in ordnung, but such a big deviation from the previous one (at the level of 20%) worries me. What our calibration experts think about it? I checked mode 6 on 8.000 events from run 5498 and 80.000 events from run 5503. Everything is ok. Therefore - continue in mode 6 ! 1 Concerning further data taking I would say the following: --------------------------------------------------------- 1) in principle I am satisfied with the data wich are already there, it should be enough at least for the preparation to the next run 2) however, if 30 GeV beam will come at the end of the run, then get data in the following priority (50.000 events per run): - luminosity trigger (ET & PD & aVC ... & (ET+PD) if possible) - pure photons (like 5501: aVC & PD, but lower threshold: 4-5 GeV rather than 10-11 as was tonight - if there is any possibility) - pure electrons (ET only in a trigger) - the rest is up to you 3) if only 26.6 GeV electrons will be inside the ring, then everything is up to you 4) from now on please, write data only in mode 6 (no FADC banks!) if this does not contradict to your interests (but only strong reasons for writting redundant information!) Run statistics: 40-50.000 events/run in mode 6, or 20-25.000 - " - in mode 1 I will also produce a set of figures for our colleagues in Moscow, just to show that system is reasonably well working due to heroic efforts of online group. To A.Fomenko and I (or E?) Sheviakov ------------------------------------ The program for the October run will be worked out on the basis of July data. But one thing is clear already now: you have to concentrate on realization of multi-trigger mode (not all these software tricks with alternate order, but realy the possibility to accumulate both triggers simultaneously). Also 220 separate counters for different bunches at the h/w level are expected. So, don't relax too long in Moscow and come back as soon as possible! Thanks indeed for your extrimely productive and useful work during this run and for the nice cooperation. See you soon BEFORE next run. Have a quiet trip and no problem with Soviet custom department. Best regards to our colleagues in Troitsk. 22.07.1991 ==================== H01USA === Run 5515 ................ Run 5515: -------- This Run was recorded with MODE 6 of bank set. Trigger: "PD&ET". Thresholds: 120 (10 GeV) and 10 (5 GeV) correspondingly. Counts - 10/300 Hz (Trigger/WaterVeto). Position of ET-Movable Platform - 424.0 mm High Voltage - new (see message later). Number of events - 25700. Start of Run - 22.07.91 at 05-13. End of Run - 22.07.91 at 06:09. 22.07.1991 ==================== F11LEV === End of the e-run? ....... Is it an official End of the HERA e- run? Why no messages about this? If yes, then can we enter the tunnel and have a look on LUMI counters before HERA p-run? It would be important to - change radiation dosimeters and estimate an average rad. level during July e- run - measure carefully what was an actual ET x-position with respect to the Interaction Point - to understand what additional dead material was in front of ET - measure actual x,z-positions for Veto counter and Photon Detector, and relative positions of lead collimator and Photon Detector - what happens with filter and Veto counter in gamma-arm. I need perhaps one full day to prepare new LOOK release, and than I will really be prevented from starting of systematic data analysis by missing of your calibration codes. 23.07.1991 ==================== H1KSOL === End of the e-run!!! ..... YES,YES,E-RUN WAS ENDED AT 6 O'CLOCK OF JULI 22. The dosimeters were removed and given for control. There are no obvious changes in filter and Veto-counter, except of the fact that water in expanding vessel was evaporated. So we should add water inside of it. E-Veto was moved in a new position, namely in center of ET. Unfortunately people from e-ring didn't keep their promise and closed access to the tunnel today at 14.00. Now we have to wait the next access to finish the preparation in tunnel. 1 24.07.1991 ==================== H01USA === Missed message .......... Saturday 20.07.91 after injection (near 12.00-13.00) we observed some shifts in our reconstructed beam energy (~24 GeV instead of 26.6 GeV). After calibration we got increased values of calibration coefficients ( ~10 %) in PD3 and ET3 channels (where the main part of energy is absorbed). During the following work the calibration coefficients were permanent (with accuracy some percents). We interpreted it as some radiation damage of our detectors and worked more carefully - observing (on beam intensity monitor) the beam dump we moved our detectors down at parking position and moved up when the beam intensity became stable. At all we observed that last time HERA worked in more intensive mode: - the time of injection (when the beam intensity on our beam intensity monitor increases up to maximal value) changed from some minutes to more than half hour; - the maximal intensity increased by an order on value ( record - 45000 Hz on counter2 (Suturday morning)); - nominal mode with 3 or 4 bunches instead of 1 at the begin of run. At the end of injection we observed smooth decreasing and than increa- sing of beam intensity (downfall) during some minutes. We interpreted it as acceleration period. These days we tryed to catch somebody from HERA to improve our understanding but... Durind energy calibration of discriminator's thresholds we observed some dispersion in the region of cutting on the correspondent histos. We explained it by nonaligned responces of different channels before analoge summation. The responces alignment was done by changing of HV. After this calibration coefficients of channels are equal with the accuracy some percents. New energy calibration of discriminators's thresholds was done. As before it we have shift (95) in PD arm. After this more pure brems trigger with energy cutting in PD and ET arms was done (run 5515). For calibration of WS channel (Water counter Spectrometric channel) we need exclude the events without energy loss in water counter below some threshold. It's pity but at least last days the correspondent descriminator didn't work ( no changing of WS histos up to 198). So we can do it precisely in offline, but with the accurasy 5-7 % it was done in on-line and HV on WS was also alligned with this accuracy. 26.07.1991 ==================== F11LEV === Data for offline analysis Offline news. ------------- 1) An analysis package LUMI91 is now under preparation. It will allow to process real lumi data taken in July run and those expected in October'91. The following features are (or will be) supported: - off-line calibration by all available algorithms (Usik, Sol.) - general analysis using corrected calibration coefficients - utility programs for a) extracting lumi data from online cartridges on IBM b) simple reconstruction for Alternate LUMI configuration c) calculation of bremsstrahlung spectra for different beam energies and detector resolutions d) calculation of cross sections for ep-->epgamma and photopr. in different energy intervals First part of analysis package (offline calibration) is ready and can be used by everybody, having at least some idea what we are at all doing at DESY and also minimal experience with DESY IBM. Note, that in order to use this efficiently (as well as all other H1 software) you need to know something about LOOK. LUMI91 package is organized in form of so called CMZ file (you can look on this as on interactive PATCHY system). But typically you will need only a small member with a job to be submitted. Copy an example job (put a * in the 1st column of the next line) get 'F11LEV.LUMI.S(#LUCAL)' (don't forget to change F11LEV on your userid in the input data) 2) Below find a list of data available for the offline analysis. They are kept either on disk or on the cartridges. For some long runs a subset of data are on the disk, while full run is kept on the cartridge. In order to check present status of these files (some of them can migrate if there were no reference to them for a quite some time) use the following command: lc F11LEV.LUMI91 1 LIST OF LUMI RUNS FOR OFF-LINE ANALYSIS ********************************************************************* *) RUN EVENTS TRIGGER DESCRIPTION DATE ********************************************************************* 5015 47 (online formats test) 4/07/91 -------------------------------------------------------------------- 5190 310 ET & PD 8/07/91 -------------------------------------------------------------------- 5201 20161 ET & PD 9/07/91 5203 6339 ET & PD(high) -------------------------------------------------------------------- 5248 21429 Bremsstrahlung_1 11/07/91 5249 13725 Bremsstrahlung_2 -------------------------------------------------------------------- 5314 68623 Bremsstrahlung_1 13/07/91 5318 9505 Pure photons 5319 8228 Bremsstranlung_1 5322 60680 Luminosity_2 5326 37033 Luminosity_2 -------------------------------------------------------------------- 5328 20584 Luminosity_2 14/07/91 -------------------------------------------------------------------- 5351 16916 Luminosity_1 15/07/91 5352 41980 Luminosity_1 -------------------------------------------------------------------- 5375 4160 Luminosity_1 17/07/91 -------------------------------------------------------------------- 5410 11176 ** Photoproduction "high Q2" 19/07/91 5411 21295 Photoproduction "high Q2" 5412 12808 Luminosity_1 5413 355334 Bremsstrahlung_0 -------------------------------------------------------------------- 5496 31734 Photoproduction "high Q2" 20/07/91 5497 87847 Photo candidates 5498 7613 Photo candidates (mode 6) 5499 15610 Electrons_0 5500 101225 Luminosity_1 5501 90377 Pure photons 5502 16636 Bremsstrahlung_1 5503 108427 Bremsstrahlung_0 5504 17325 Electrons_1 -------------------------------------------------------------------- 5515 25700 ET & PD 22/07/91 ********************************************************************* *) Luminosity_0 = ET & PD & aVC & (ET+PD) Luminosity_1 = ET & PD & aVC Luminosity_2 = ET & PD & (ET+PD) Photoproduction candidates = ET & aPD & aVC Photoproduction "high Q2" = ET & aPD & aVC & aET_central_layer Bremsstrahlung_0 = VC --> any activity in gamma arm Bremsstrahlung_1 = PD Bremsstrahlung_2 = PD(high) --> high energy spectrum part Pure photons = PD & aVC --> non-interacted photons Electrons_0 = ET --> any activity in e-arm Electrons_1 = ET & aET_Central_layer **) Different y-position of ET (shifted on 4 mm) Files kept on cartridges Files resided on fast disks ------------------------ --------------------------- F11LEV.LUMI91.CRT05201 F11LEV.LUMI91.RUN05328 F11LEV.LUMI91.CRT05203 F11LEV.LUMI91.RUN05375 F11LEV.LUMI91.CRT05248 F11LEV.LUMI91.RUN05410 F11LEV.LUMI91.CRT05314 F11LEV.LUMI91.RUN05411 F11LEV.LUMI91.CRT05318 F11LEV.LUMI91.RUN05412 F11LEV.LUMI91.CRT05319 F11LEV.LUMI91.RUN05413 F11LEV.LUMI91.CRT05322 F11LEV.LUMI91.RUN05496 F11LEV.LUMI91.CRT05326 F11LEV.LUMI91.RUN05498 F11LEV.LUMI91.CRT05351 F11LEV.LUMI91.RUN05499 F11LEV.LUMI91.CRT05352 F11LEV.LUMI91.RUN05501 F11LEV.LUMI91.CRT05413 F11LEV.LUMI91.RUN05502 F11LEV.LUMI91.CRT05497 F11LEV.LUMI91.RUN05503 F11LEV.LUMI91.CRT05500 F11LEV.LUMI91.RUN05504 F11LEV.LUMI91.CRT05501 F11LEV.LUMI91.RUN05515 1 26.07.1991 ==================== F11LEV === Our data go to CERN ! ... To the attension of LPI group. ------------------------------ Professor Wiik goes to CERN where he will report on the results of the July HERA e- run. He asked me (via R.Felst) to provide several rather impressive figures from our recent data. Finally the followind results will be presented at CERN (with mentioning that they are obtained by LPI group from H1) - time dependence of beam intensity in 2 runs - beam profile at the PD calorimeter (XY-plot and both projections) - calibrated energy distibutions at ET, PD and total energy for the luminosity trigger (ET & PD & aVC) - comparison of the total energy distribution in gamma-arm from the run 5413 with Bethe-Heitler spectrum. 26.07.1991 ==================== F11LEV === Offline calibration ..... Below first results from off-line calibration are presented. They show that both procedures still produce unstable results. Bad data, or not clever enough algorithms? May be tuning can help? Experts are invited to the open discussion. +--------------------------------------------------+ | | | H 1 L U M I d a t a a n a l y s i s | | | | RUN = 5412 | | | | HERA e- run July-1991 | +--------------------------------------------------+ 3 iteration. 12807 events have been processed Counter CS (MeV/ADC) CU (MeV/ADC) ------- ------------ ------------ 0 5.129 3.655 1 4.282 4.965 2 4.346 4.552 3 4.462 4.841 4 2.596 1.932 5 6.535 3.752 6 3.501 3.650 ------- ------------ ------------ 0 2.504 1.357 1 3.132 3.228 2 2.855 3.100 3 3.140 3.133 4 4.650 3.650 ------- ------------ ------------ Method E0(GeV) Sigma(GeV) Resol(%) ------ ------- ---------- -------- S 26.679 1.129 4.231 U 26.866 1.010 3.760 +--------------------------------------------------+ | | | H 1 L U M I d a t a a n a l y s i s | | | | RUN = 5500 | | | | HERA e- run July-1991 | +--------------------------------------------------+ 3 iteration. 60000 events have been processed Counter CS (MeV/ADC) CU (MeV/ADC) ------- ------------ ------------ 0 2.061 3.626 1 2.678 4.020 2 2.360 3.613 3 3.275 4.506 4 4.044 1.861 5 1.415 3.717 6 0.000 3.650 ------- ------------ ------------ 0 2.646 1.540 1 4.052 3.575 2 3.805 3.521 3 4.194 3.636 4 4.068 3.654 ------- ------------ ------------ Method E0(GeV) Sigma(GeV) Resol(%) ------ ------- ---------- -------- S 26.993 1.139 4.221 U 26.887 1.008 3.749 1 +--------------------------------------------------+ | | | H 1 L U M I d a t a a n a l y s i s | | | | RUN = 5515 | | | | HERA e- run July-1991 | +--------------------------------------------------+ ** LINEXT ** Hist Time(msec) A0/E0 AMIN/EMIN AMAX/EMAX 0.00 20000.00 0.00 50.00 1 iteration. 25676 events have been processed Cell CS_1(MeV) CS_2(MeV) S_stat CC_U(MeV) SW_stat CSW_stat ---- --------- --------- ------ --------- ------- -------- 1 8.364 8.384 59.3 3.589 6.2 0.2 2 7.629 7.634 181.5 8.139 432.2 346.8 3 6.673 6.678 649.3 7.044 2678.1 2476.1 4 4.667 4.662 1292.9 4.365 3987.3 3929.4 5 0.503 0.514 360.6 1.318 100.3 68.0 6 4.668 4.656 63.0 3.605 14.0 1.8 7 6.760 6.694 36.0 3.633 2.9 0.1 8 2.706 2.701 698.2 2.617 617.0 448.9 9 0.486 0.477 863.9 1.028 198.9 72.1 10 2.946 2.937 519.0 2.672 370.4 242.6 11 0.994 0.977 1026.4 1.063 296.1 137.3 12 8.385 8.418 986.4 7.510 6545.5 6540.1 ITR,DEL = 56 0.999 SSUM = 25676. USUM = 25341. ** LINEXT ** Hist Time(msec) A0/E0 AMIN/EMIN AMAX/EMAX 100 12.92 6342.93 5534.93 7150.93 300 12.91 24.33 20.09 28.56 2 iteration. 25676 events have been processed Cell CS_1(MeV) CS_2(MeV) S_stat CC_U(MeV) SW_stat CSW_stat ---- --------- --------- ------ --------- ------- -------- 1 5.819 5.785 58.4 3.599 4.2 0.1 2 5.571 5.512 184.4 9.726 472.2 391.8 3 5.204 5.154 674.1 7.381 2178.0 2012.8 4 4.584 4.537 1242.7 5.956 4491.9 4449.9 5 4.436 4.437 242.3 1.513 49.2 36.1 6 2.203 2.110 47.1 3.747 7.9 1.6 7 5.609 5.420 31.1 3.633 1.6 0.0 8 3.590 3.596 666.1 2.777 337.8 196.9 9 3.422 3.391 772.2 1.040 63.2 3.7 10 4.423 4.435 483.3 3.002 230.7 121.4 11 3.032 3.017 937.6 1.108 101.6 9.5 12 4.647 4.786 982.1 7.206 3520.9 3514.5 ITR,DEL = 100 0.998 SSUM = 20285. USUM = 17131. ** LINEXT ** Hist Time(msec) A0/E0 AMIN/EMIN AMAX/EMAX 0.00 20000.00 0.00 50.00 3 iteration. 25676 events have been processed Counter CS (MeV/ADC) CU (MeV/ADC) ------- ------------ ------------ 0 5.802 3.599 1 5.541 9.726 2 5.179 7.381 3 4.560 5.956 4 4.437 1.513 5 2.157 3.747 6 5.515 3.633 ------- ------------ ------------ 0 3.593 2.777 1 3.407 1.040 2 4.429 3.002 3 3.024 1.108 4 4.716 7.206 ------- ------------ ------------ Method E0(GeV) Sigma(GeV) Resol(%) ------ ------- ---------- -------- S 26.511 1.396 5.267 U 27.298 1.844 6.754 1 26.07.1991 ==================== H01USA === Runs from H1 logbook .... This list of runs is extracted from H1 loggbook. There is some discre- pancy with previous one. Date - date, when run was really recorded; EVENTS - number of logged events from the viewpoint of H1DAQ. LIST OF LUMI RUNS OF SUMMER 91 e-RUN ###################################################################### | | *)|Da| Time | | |TRIGGER |te|-----------| | |_________|XX| | | **) RUN | EVENTS |P|E|P|W|C|07|Start|Stop | Remarks | |D|T|E|C|E|91| | | #######|########|#|#|#|#|#|##|#####|#####|############################ 5015 | 000047 | | | | | |04| | | ONLINE FORMATS TEST -------|--------|-|-|-|-|-|--|-----|-----|-------------------------- 5190 | 310 |&|&| | | | |07:12|07:19| -------|--------|-|-|-|-|-|--|-----|-----|-------------------------- 5201 | 20161 |&|&|&| | |09|22:42|23:10|Th:69,39,..; 5203 | 6339 |&|&| | | | |02:17|02:59|Th:169,7; -------|--------|-|-|-|-|-|--|-----|-----|-------------------------- 5248 | 21429 |&| | | | | |23:57|00:15|Th:15; C1/2=2000/5000 Hz 5249 | 13725 |&| | | | | |00:25|01:00|Th:119;C1/2=10/10 Hz;C2=PD 5250 | 600 | | | | | | |01:03!01:07|Test of new on-line release -------|--------|-|-|-|-|-|--|-----|-----|-------------------------- 5314 | 68623 |&| | | | |13|01:20|02:18|Th:19;C1/2=300/350 Hz 5318 | 9505 |&| | |a| | |05:36|05:44|Th:22,2;C1/2=300/4000 Hz 5319 | 8228 |&| | | | | |05:49|05:57|Th:22; C1/2=2200/3500 Hz 5322 | 60680 |&|&|&| | | |06:15|07:10|Th: 5326 | 37033 |&|&|&| | | |09:51|10:21|Th:26,10,6;C1/2=30/500 Hz 5328 | 20584 |&|&|&| | | |10:25|10:46|debugging of XIDAQ opt link | | | | | | | | | |Th:26,10,6;C1/2=30/500 Hz -------|--------|-|-|-|-|-|--|-----|-----|--------------------------- 5351 | 16916 |&|&| |a| |14|14:37|14:59|Th:25,10,2;C1/2=10/1000 Hz 5352 | 44495 |&|&| |a| | |15:03|17:02|Th:25,10,2;C1/2=5/500 Hz -------|--------|-|-|-|-|-|--|-----|-----|--------------------------- 5375 | 4160 |&|&| |a| |17|05:43|06:00|Th:24,11,(3,3);C1/2= | | | | | | | | | |New HV 5405 | 9498 | | | | | | |20:00|20:07|Test of mode 6(test pulses) 5406 | 9498 | | | | | | |20:11|20:15|------"------- with 30 buff. -------|--------|-|-|-|-|-|--|-----|-----|--------------------------- 5410 | 11185 |a|&| |a|a|18|00:28|00:38|Th:23,11,(8,8),7;500/1500 Hz | | | | | | | | | |hET=428 mm 5411 | 21296 |a|&| |a|a| |00:43|01:00|Th:23,11,(8,8),7;500/1500 Hz | | | | | | | | | |hET=424 mm 5412 | 12809 |&|&| |a| | |01:10|01:27|Th:23,11,(8,8);17/10000 Hz 5413 | 355334 | | | |&| | |01:44|07:07|Th:(8,8) C1/2=3500/5000 Hz -------|--------|-|-|-|-|-|--|-----|-----|-------------------------- 5496 | 31734 |a|&| |a|a|20|00:03|00:12|Th:24,10,(8,8),7;Q2" 5497 | 87847 |a|&| |a| | |00:25|00:39|Th:24,10.(8,8); 5498 | 16514 |a|&| |a| | |00:42|00:44| ------"------- (MODE 6) 5499 | 15610 | |&| | | | |01:15|01:18|Th:9; C1/2=580/2000 Hz 5500 | 101225 |&|&| |a| | |02:50|04:56|Th:24,10,(6,8); 5501 | 90377 |&| | |a| | |05:21|06:09|Th:24,(6,8); 5502 | 16636 |&| | | | | |06:13|06:16|Th:24; C1/2=700/4500 Hz 5503 | 108427 | | | |a| | |06:23|06:39|Th:(8,8); C1/2=700/4500 Hz 5504 | 17325 | |&| | |a| |06:47|06:52|Th:9,7; C1/2=130/2300 Hz -------|--------|-|-|-|-|-|--|-----|-----|-------------------------- 5515 | 25700 |&|&| | | |22|05:13|06:09|Th:120(10GeV),10(5GeV) | | | | | | | | | |10/300 Hz,new HV(aligned r.) ###################################################################### *) ET - Electron Tagger PD - Photon Detector EP - ET + PD WC - Water Counter = (WV or WS), V,S - veto and spectrometeric channels of WC CE - Central Layer of ET **) Th - threshold (non calibrated, arbitrary value) C1/2 -rates on counter1 (trigger)/counter2 (beam intensity =WC) 29.07.1991 ==================== H1KSOL === Substance in photon arm . Today I consulted with mr.Trines from proton vacuum group about additional substance in acceptance of PD-arm. I mean mainly the vacuum shieber (shutter) wich should separate e-ring from p-ring. Mr.Trines said very definitely that this shieber was closed (!!!) during last e-run. It means that we had additional material in acceptance of photon arm. This shieber is placed at distance 27.4 m from IP in proton vacuum pipe (drowing is in the folder "histos and graphics for e-run"). Construction of it is complicated enough, it is not homogenious, but we cam assume that it is stainless steel with thickness about 20 mm (>1X0). 1 30.07.1991 ==================== F11LEV === Calibration package ..... Description for the offline calibration package LUCAL is available in list 'F11LEV.LUMI.S(++CAL)' It includes also the results for all runs taken with triggers lumi_1 or lumi_2 (with or without aVC). LOOK figures which cannot be stored in a computer readable form are attached to the master copy in our office (1c-121). The best run from this point of view is those taken 17/07 just after the first successful online calibration: RUN = 5375 It gave for both methods (S- and U-) total energy resolution of 3.6% and average difference between two algorithms less than 5%. Energy distributions at the electron and photon arms for this run are in excellent agreement with MC predictions. Now I switch to the main analysis package LUANL. However, calibration experts should try to tune parameters for their algorithms further... Good luck with LUCAL ! 31.07.1991 ==================== H1KSOL === Dosimeters .............. I got the results of doses in dosimeters from D-group.They are the following: ET - Dosimeter # 1 (was placed inside electronic box) - 93 cGy -------- # 2 (----- on the AET near e-plane) - 1700 cGy -------- # 3 ( - on the lead shealding in front of AET ) - 1800 cGy PD - Dosimeter # 4 (was plased incide electronic box) - 280 cGy - - # 5 ( --- on APD near e-plane) - 90 cGy --- # 6 ( --- on the lead shealding near e-plane ) - 60 cGy 02.08.1991 ==================== F11LEV === Preparation to Oct. run . We should already start to think about the next test run in October. Note, that it hopefully will be in ep-colliding mode, which means that we will observe superposition of ep events with the bremsstrahlung on residual gas. During October run it would be very important - to improve online calibration procedure, - to check multi-trigger mode (lumi and photo simultaneousely), - to have 220 h/w counters, for each bunch separately, - to finalize all online LUMI banks including trigger information, - to have permanent connection with the HERA machine control room, - to get luminosity value online (in cm-2sec-1 units already), - to estimate and subtract background from the res.gas to lumi, - to provide beam profile at PD for the machine people, etc, etc, etc. You see: a lot of work, especially for A.Fomenko and I.Sheviakov. One thing is quite clear now. +---------------------------------------------------+ | We have to turn ET around z-axis on 90 degrees | | and fix it as close to the beam line as possible. | +---------------------------------------------------+ What we will gain by this? 1) Acceptance of ET will be increased compared to July run (Emax would be 21 GeV instead of 16 at E0=26.6 GeV), which should improve calibration procedure (according to Usik's explanation of why it is so poor now: the wider E-acceptance the better). 2) Reconstruction of x-coordinate is much more important than y, since in y direction beam anyway is localized around y=0. Again, this will allow not only correct on the energy leakage over the side boundaries, but also improve calibration conditi- ons: in this case ALL ET modules can be reasonably well calibra- ted since in x direction energy should be enough for all of them. 3) Wave length shifters will be then on the top and the bottom of ET which means in much better background conditions than now (main background is located around median plane of accelerator and rapidly falls down with vertical displacement). According to Rusakov's remark this background can produce Cherenkov light in the shifters and thus distort ET response. 4) We can remove ET veto counter, since anyway it was not useful. What would be the price for that? 1) Forget about photoproduction (but trigger formally can be tested if necessary e.g. for the combined mode). 2) No other control on the vertical position of ET exept platform counter (before, we could check with the ET response). Evidently, advantages are more serious than disadvantages. Therefore, let's try to do this. 1 Other news. ----------- Interested people can look into LUMI Calibration data kept in the room 121 where two new pictures have been added: 1. Comparison of U- and S- C.C. for all runs and all channels. 2. The same for E0, resolution and global difference between S and U LUMI91 Analysis Package (LUANL) is ready. Results obtained have been presented yesterday on the H1 group meeting. Copies of all shown tran- sparancies are also available in 1c-121. There are already a few potential users (e.g. Witek Krasny) who are interested to analyse LUMI data independently of us. Presently I am preparing a short description (User Guide). The "official" release will be done over the weekend. Again, those who want to be at least minimally prepared to the real data analysis should use a chance to become familiar with the LOOK system and use LUMI91 package as a small model for future analysis. 06.08.1991 ==================== H01USA === Event rate to IBM ....... Today Bill demonstrated new rate of event logon to IBM (after corres- pondent changings on IBM side (before it was done for DAQ side (see remarks 19.07.91))). Now we have: event size, kByte Rate, Hz 1 350 0.5 450 11.08.1991 ==================== F11LEV === Analysis package ........ Description for the off-line analysis package LUANL is available in list 'F11LEV.LUMI.S(++ANL)' It includes also the results of few runs taken with different triggers LOOK figures which cannot be stored in a computer readable form are attached to the master copy in our office (1b-121). Much more figures are available in my office (1c-349) by special request. An extensive analysis over all existing data has shown the following: 1) LUMINOSITY measurements with this configuration is possible with rather high accuracy level, however 2) TRIGGERS based on the any single arm information accept too much background. Efficiency of different trigger elements sometimes seem to be far from 100%, e.g. aPD, aVC (needs further investigations!). All data taken with trigger ET arm only show a presence of high energy threshold at the level of 19-20 GeV for ET-trigger! Why? This is not the case for PD arm. 3) PEDESTALS are one of the unsolved problems for our subdetector. Online people MUST provide more reliable data with this respect, therefore more detailed study of pedestal behavior is needed. July data can be used for this study since almost all runs contain full FADC information. This information is easily accessable within LUANL pack- age (see example in LUANL description) 4) OVERALL results are now almost completely understood: - number of "double" events (random coincidences) are in agreement within factor 2-3 with calculations based on the total trigger rate - bremsstrahlung spectrum after accounting of VC-trigger efficiency and detector resolution shows excellent agreement with theoretical (Bethe-Heitler) predictions - energy correlation plots (most informative ones by the way) look also quite reasonable. 5) IN FUTURE -it would be desirable to have in e-arm something similar to VC counter in gamma-arm: i.e. a simple counter which could be able to estimate total loading rate at ET (not a highest priority however) -much more important is to have a RELIABLE trigger info both online and offline: presently it sometimes is not clear what trigger conditions were actually used for a particular run. -in July we missed OR trigger data (ET OR PD,VC) which will be very important to get in October for different cross checks. -pedestals study must be done before October, including as much details as possible. Note, that in October much higher loading rates are expected at both our detectors! 1 15.08.1991 ==================== F11LEV === July logbook is closed .. This last message closes our July logbook. We are now already in a state of preparation to the October run, hence all working information will be important during future run. This information is better to keep in a new logbook (or new chapter of LUMI logbook). Therefore: all interested people are asked to create the following CLIST commands (you can copy them from the LLJ and LLO members of my library F11LEV.CLIST into your library USERID.CLIST) LLJ = list 'F11LEV.LUMI.J91.LOGBOOK'- to inspect old July logbook LLO = ((edit)) 'F11LEV.PUB.LUMI.LOGBOOK'- to update new October logbook Note, that LLO is simply alias of the former LLOG command. I renamed it because of a clash with already existing H1 LLOG command. The meaning of new abbreviations is evident: LLJ means Lumi Logbook for July run LLO means Lumi Logbook for October run