*********************************************************************** * * * PART 3 PART 3 * * H1 LUMI LOGBOOK * * * * PREPARATION TO THE EP-DATA TAKING * * * * * * Use command: F ====== to find all messages, and then select * * those you are interested in * * * To print this part on the logbook put * in the next line: * PRINT 'F11LEV.H1.LUMI.LOGBOOK.JAN92.MAY92' DEST LI1 OVFL ONA NOHEAD * * * S.Levonian Opened: 2/01/92 at 10:00 * * Closed : 31/05/92 at 23:59 * * * *********************************************************************** 04.01.1992 ==================== H01USA === Fast REC ................ Now the Moscow line is working again (after breaking from 17.12.91). It's very nice to read about new possibillities, new hardware, speciall y about using RISC-board. But is it enough or not for reconstruction? I remember that in our ideology in common case we calculate out lumi as L = R*k/sigmaL, where R - rate of our HW trigger (~30kHz), k - correction coefficient, which we define from reconstructed events sigmaL - cross-section+geometrical aceptance. If we want to have k with the statistical error (sigma) ~ 1% we need firstly to process the following number of events: N = k*(1-k)*10**4 ==> N = 900 for k=0.9 or 1.5' N = 2500 for k=0.5 or 4' if the reconstruction rate=10 Hz. Then this coefficient is corrected continuosly using iteration procedure, but in the beginner we will have this delay. If (using RISC-board) we will have rate of reconstuction 100 Hz instead 10 Hz benefit will be sqrt(10). This estimation of delay before real measuaring of lumonosity was done without calibration (factor 2 or 3 ). So even using RISC-board we will have delay more then one minute for every restart of our subdetector. ==>... FAST RECONSTRUCTION program ?? 08.01.1992 ==================== H1KFOM === Additional MacVEE........ Yesterday, 07.01.92, Bill Haynes put to H1Lumi-subsystem the new (additional) MacVEE. From this day it is possible to use both MacII (H1Lumi and H1Lumi2) for monitoring of VME-boards. CAMAC is monitored only through H1Lumi2. All promissings of H1 community at Brasse's operation meeting at 11 Dec. 91 are done. 1 15.01.1992 ==================== F11LEV === About our photo-trigger.. In the November'91 run the total photoproduction trigger used was: T_lumi(ET*noPD*noVC) * T_H1(CALO*noIV) This gives total trigger rate containing both signal and background. Since the background is of the random coincidence nature, it can be estimated, provided the single rates in both branches are known: p(bgr) = p(T_lumi)*p(T_H1) where p(i) is a probability of the "event"-i to occur in the same bunch crossing. Let N1 and N2 are the total number of T_lumi and T_H1 triggers correspondingly detected during the time t (sec) within a single bunch. Then, taking into account that the total number of bunch crossings for this particular bunch is t*f (f=47.3kHz) one gets (in case of p(i)<< 1) p(T_lumi) = N1/(f*t) = r1/f, (r1=N1/t) p(T_H1) = N2/(f*t) = r2/f, (r2=N2/t) r(bgr) = N(bgr)/t = p(bgr)*t*f/t = r1*r2/f In case of n filled and colliding bunches the total background rate is: n n R(bgr) = Sum{r(bgr)(j)} = Sum{r1(j)*r2(j)}/f (1) j=1 j=1 Important remark: ---------------- As one can easily see, the last formula can only be simplified to the form we usually use it in case of "uniform" bunches, i.e. if all r1(j) and r2(j) are the same for all bunches j: R(bgr) = n*r1*r2/f = n*r1*n*r2/(n*f) = R1*R2/F, (2) where F = n*f (= 10.4 MHz for all bunches filled), R1=n*r1, R2=n*r2. The difference between (1) and (2) can easily reach a big value, if bunch intensity is far from uniform. A simple example. Let's consider 2-bunch situation with luminosity which differs in 4 times: r1(1)=2, r1(2)=8 -> R1 = 10 and r2(1)=20, r2(2)=80 -> R2 = 100 Then R(bgr) from (1) and (2) will give different results. Correct one (1): R(bgr) = (2*20+8*80)/f = 680/f Wrong result (2): R(bgr) = 10*100/2f = 500/f Thus, in this case an error when using (2) is 36%. In reality this will be even more comlicated, since bunch behaviour seems to be different in time and therefore r1(j), r2(j) in (1) will be also time dependent. Concequence: ------------ This means, that in order to calculate our background correctly, we must treat each bunch separately and therefore to have 220 counters not only for LUMI trigger branch (r1(j) in (1)), but also for H1 trigger element(s) used in photoproduction trigger (r2(j)). Who will do this? Preliminary discussion with E.Elsen showed that in principle this might be possible. I think, that in our group a natural responsible for the realisation of this kind of trigger is I(or E?) Sheviakov, who should as soon as possible contact relevant experts: Elsen, Krehbiel, Straumann. Trigger elements we forsee from H1 are: a) all 4 planes of BPC are fired b) energy deposited in PLUG > E_min (15-20GeV) (in or with a) c) no negative TOF d) may be also: positive TOF Therefore, subdetectors of our interest are: BPC,TOF,PLUG. 15.01.1992 ==================== F11LEV === Background to photoprod.. After careful analysis of last runs I found, that something is wrong with our trigger counters (LRTB bank). Simple formulas (1-2) from previous message do not work. They give approximately in 150 times higher rates for the photoproduction trigger than expected (even not accounting of small acceptance of Korbel's calorimeter compared to H1, which should give another factor 3-4 leading to the 500 times higher rates). This means, that single rates for LUMI and/or CALO branches are under- estimated (of coarse, not in 500 times but in 2-3 times in fact: r_signal = 2-3Hz - 0.5-1.5Hz, while expected rate is about 0.02Hz). Possible reasons which immediately come to the mind: a) dead time for some trigger elements b) incorrect time adjustment between LUMI and CALO trigger signals c) simply wrong content of LRTB bank d) non-random background (what kind of ???) What else? Please, think over! 1 16.01.1992 ==================== F11LEV === Background to photoprod.. Just not to forget (mainly for myself): a nonrandom background to the photoproduction is total hadroproduction on residual gas. Preliminary estimate for the final conditions was done in my LPI note 9-90. Here I repeat it also for November run situation. 0.9 R(bgr) sigma(bgr)*L(e_gas) sigma(gp;s=33)*A L(e_gas) r = ------ = ------------------- = --------------------------- (1) R(sig) sigma(gp) * L(ep) sigma(gp;s=s(ep))*L(ep) Using actual numbers for =8, sigma(gp;s=33)=0.114 mb, sigma(gp;s= s(ep)) = 0.15-0.20 mb, gas pressure = 3.4*10**(-12) bar one can get from (1): a) Final conditions: = 60000 GeV**2 L(ep) = 1.5*10**31 cm-2s-1 L(e_gas)= 0.344*10**28 cm-2s-1 per 1m r = 0.1%/m b) Nov-Dec'91: = 30000 GeV**2 L(ep) = 2*10**27 - 8*10**28 cm-2s-1 n(e) = 4*10**10 - 3.4*10**11 L(e_gas)= (0.17-1.46)*10**26 cm-2s-1 per 1m r < (0.9-4.0)%/m Note, that in case of November run we can estimate only an upper limit for r, since acceptance of Korbel's Calorimeter is definitely better for signal compared to background where all particles go preferentially backward in the lab. frame, while for the final H1 trigger this is not the case (BPC may be as good for background as for the signal). 27.01.1992 ==================== H01USA === Correction coefficient == Interaction algorithm for calculation of software correction of hardware luminosity scaler (for memory) Remember that because of slow changing effeciency of lumi HW trigger we must correct it measuring this efficiency by on-line program. Because of low rate of lumireadout (~10Hz) we need some minutes for get ting small statistic error (see my previous message). After this we can use the following interaction algorithm for calculation of correction coefficient. If K{n} - correction coeffient for event number "n", then for next event we have: K{n+1} = K{n}*n/(n+1) + X{n+1}/(n+1), where X{}=0 if event is rejected X{}=1 if event is accepted. For watching of correction coefficient changing we must fix the number of events (N) for requied statistical accuracy and use finaly the following formula: K{current} = K{previous}*(N-1)/N + X{current)/N, where f.ex. N=900 for K~=0.9 ( N=K*(1-K)/sigma**2 ). Better use the max value of N (when K=0.5) =2500.It garanties sigma < 1% for all range of K. For fast monitoring of big changing of K ( deltaK > 10% ) it is enough to use N=25 ( ==> time < 2.5 sec). 21.02.1992 ==================== H1KFOM === Project of LRTL-bank ===== It is proposed to create at our subsystem the new LRTL-bank. Format of LRTL-bank is B32. Length of this bank is near 1Kbytes. This bank is so-called "asynchronous". It means that it will be created outside of ReadOut chain (for example at the second FIC or at BG-area of the first(main) FIC). Time of creating of the next LRTL-bank is some time period which can be changed(for example 5 sec. or 10 sec. etc). This bank will be included into H1 CDAQ data flow with nearest H1-event It is possible to ask J.Olsson to move this bank at special data sto- rage. It is possible to ask P.Hill to use this bank for filling of LOOK-histos of vector-type or something else. 1 Data structure at this bank is the next: LRTL - name 0 0 XXXXXXXX - length (at longwords without header length)(233 at current release) NRow - 231 at current release Ncol - 1 at current release Rate(1) - rate of pure lumi trigger at bunch 1 (HW) ...... Rate(220) - rate of pure lumi trigger at bunch 220 (HW) Rate0 - integral rate of pur lumi trigger at all bunches (HW) a1 - current value of PureKoeffLumiTriggEff. int(real)*1000. a2 - current value of RoughKoeffLumiTriggEff. int(real)*1000. a3 - current value of PureXpd int(real)*1000. a4 - current value of PureYpd int(real)*1000. a5 - current value of RoughXpd int(real)*1000. a6 - current value of RoughYpd int(real)*1000. a7 - current value of PureApertureKoeff int(real)*1000. a8 - current value of KoeffUneffFADC int(real)*1000. a9 - current value of Revolution Counter a10 - current value of LumiLocalTimer Comments: 1) PureKoeffLumiTriggEff - this value is permanently monitored at the second FIC (10000 last events passed through reconstruction proce- dure); 2) RoughKoeffLumiTriggEff - this value is permanently monitored at the second FIC (100 last events); 3) PureXpd and PureYpd - current values of profiles at PD with good accuracy (last 2500 events); 4) RoughXpd and RoughYpd - current values of profiles at PD with bad accuracy (last 30 events); 5) PureApertureKoeff - current values of apperture correction due to not central position of beam profile at the face of PD (=1. yet) at future must be calculated and must be >1. 6) KoeffUneffFADC - unefficiency of FADCs (=1 yet). 7) Revolution counter - used only as timer which can be cleared at the start Run procedure; 8) LumiLocalTimer - used as timer which can be cleared only once per seance. Welcome to any critysism and additions. 22.02.1992 ==================== H1KMAL === HV-power supply ======= HV Power Supply for Detectors. The three LeCroy Moduls are used as power sourses for Lumi detectors. In daisy-chain the mainframes were joined in the next order: 1 - Module 4032 number 37084 - address 60, 2 - Module 4032A number 93434 - address 15, 3 - Module 4032A number 57561 - address 16. The mainframes with address 60 and 15 are used for ET - 49 channels, and mainframe 16 for PD (25 channels) and Veto - 2 channels. The HV system was swiched On 15 Junuary and after two or three small trubles is operating with a good stability. 25.02.1992 ==================== H1KFOM === Situation with LRTL-bank = Yesterday it was discussed some problems connected with LRTL-bank: 1) Paul Hill said that he has no experience to fill LOOK-objects of vector-type at his Histo-application on FIC-board at H1 CDAQ (only HHPACK(Erwin Deffur's SW product) are used for creating of different histos). And second remark - LRTL-bank must be not at every event and (as You know) Histo-application get for histogramming nor each event - it is possible to lost some important pieces of luminosity behaviour; 2) Another problem was connected with farm activity at H1 CDAQ - if the next event with LRTL-bank (may be one from 100 events) will be rejected with farm activity - our (may be important piece of infor- mation about luminocity behaiviour) LRTL-bank could be lost. But... after talking with Bill Haynes and Alan Campbell it is clear now that H1 CDAQ community look forward with prediction of this situation (not only for our subdetector) and proposed the next variant of creation and passing through H1 CDAQ of our LRTL-bank: a) our subsystem must create so-called KEEP-bank with LRTL-bank inside of this KEEP-bank. b) H1 CDAQ farm retrans- lates this type of banks into H1 CDAQ and forward to IBM cartridges at any case of decision of farm ... and all is OK with our LRTL- -bank. I think that with this type of retranslation of important pieces of information we must retranslate our LRPC and LPEC-banks with calibration coefficients. May be some analog of LRTC-bank must be retranslated through this chain of data passing. 1 3) Last problem - situation with LRTL-bank must be discussed with Jan Olsson. But nobody (good exeption - Egor) does not put any crytisizm on contents and structure of LRTL-bank. It is clear that at contents of LRTL-bank we must have some information about current value of luminosity. Usik promised to write the first (may be not very good) algorithm of calculation of current luminosity from all values which are disposed at LRTL-bank and from measured by anybody of bunch intensity. Asking to all members of our H1Lumi-community - think please about possible algorithm of current value of luminosity. Think and propose please. 01.03.1992 ==================== H1KMAL === Situation at HERA tunnel== Description of all works which were done at HERA-tunnel for RUN - preparation. Both main calorimeters have been checked. We had troubles with the electron detector - we were to do over again three times it: 1) First - it was the electric strike-through between two neighbour element PMs. 2) Second - it was the bad Resistance at anode of PM. 3) Third - there was the elecrtric strike of the Resistance at PM-divider. Every calorimeter was provided by the temperature switch with limit +85C (right LEMO conector on the backpanel of the electron detector and the black cabel on the photon detector). Besides that every detector has been supplied with the temperature senders (ET has even two senders) - S 201 PT, which have the resistance velues from 107,8 to 130,9 OM at the temperature region 20-80C with exit via the grey cable on Pd and two LEMO connectors on ET. Moreover the temperature senders were putted at the elec- tronic crates (inside the lead boxes), filter, vetocounter and the iron support of electron detector moving table- temperature of HERA tunnel. The picture of temperature measuring includes 8 positions: t P_elec. - temperature of photon detector electronic t E_elec. - temperatyre of electron detector electro- nic crate t P_det. - temperature inside of photon detector t E_det1. - temperature inside of electron detector t VETO - temperature of the water box of veto- counter t E_det2. - temperature inside of electron detector t Filter - temperature of SS casee for plates of filter t Tunnel - temperature of support of the electron moving table - tunnel temperature. The calorimeters were provided the additional ventilators and have been installed on moving platforms into HERA tunnel. The boxe with 4 light diodes was putted on the front plane of the each calorimeter. The every light diode has his own supply cable (with possibility to swich ON - OFF and to change the control signal amplitudes) - for that the conector on the side of front box is used. For first stage of HERA- operation it was decided to use the filter with the total lenght about 2 Xo: ---|---|---step 17 mm ____________________|___|______ | || | | Pb ||----------| |------------------|| || || |1- 7 mm Cu | || || || | | ||1 || 2|| 3|2- 3 mm Pb | D = 90 mm || || || | | || || || |3- 5.5 mm Pb |------------------|| || || | |---- 170 mm ------||----------| |__________________||__________| Kollimator and Filter. 02.03.1992 ==================== H1KFOM === Run 13450 ================ At Friday 28.02.1992 it was good posibility to test the new release of the H1LumiOnlineProgram together with H1CDAQ. This posibility was used. It was written Run 13450 with near 37000 events with MODE=1 and with new bank LRTL (with KEEP-folder). It is pity but this Run was written with option "temporary data" and was scratched at this day with new data from H1 Technical Run. But in principal this data are live at H1KMAL-directory on permanent cartridges (Evgenio agreed with my asking and move this data from two temporary cartridges F11JOL.H01.TESTDATA.G7369V00 and ...G7370V00 on his personal cartridges H1KMAL.LUMI91.CRT13450 (first 4999 events) and H1KMAL.LUMI91.CRT1.N50A (last 31985 events). 1 This data has the next H1Lumi-banks: LREC,LRPC - as Start-Run-Record, LREE,LRPE,LREF,LRPF,LRTE,TSTC,LRTN,LRTF,LRTL(at KEEP- -folders) and LRTB-bank as End-Run-Record. LRTL-bank was appeared at H1Lumievents only 65 times (once per 10 sec.) It means that this Run was written near 650 sec. Average Event Length was 1.444 Kbyte. Minimal - 0.531 Kbyte. Maximal- 2.559 Kbyte (event with LRTL-bank). Length of End-Run-Record was 26980 bytes as ordinary. Some news from data format: 1) it is changed the length of LRPC-bank (was 27 - now is 28) - due to appearence of WaterVeto Spectr.Channel Calibr.Coeff at p25 place; (at earlier releases this information was placed at p08-place); 2) it is appeared p25-cell at Photon Detector banks (LRPE,LRPF) - this is information from Water Veto Spectr.Channel; (at earlier releases this information was placed at p08-place); 3) it is appeared new (non-event,asynchronous) LRTL-bank with KEEP-folders for passing through H1CDAQ-farm. 4) at LREE and LRPE it is appeared new specific value (earlier we had only 20000 as overflow situation at cell). Now it is possible to find at contents of cell`s amplitude the new value 20001. This is the label of so-called "zero-pedestal situation". In principal we must have this label - especially this will be useful at high rates. But in principal it is possible to switch off this label. Proposal for thinking: may be channel with overflow information or with "zero-pedestal"-information we can name as 'dead'-channel for current event and it is possible to save this event? This is question for S.Levonian - is it needed and is it possible to do without large update of H1LumiRec? About contents of the Run13450`s events: This events have information about test pulses at each cell of PD,ET and Water Veto. In principal we must have at each event 49 values from ET and 25+1 from PD and WaterVeto. But there were some problems with efficiency of Trigger (Trigger was WaterVeto-only), nonefficiency of FADCs, specific of some channel`s preamplifiers etc. At Run Summary we can see that lengths of LRPE-bank during this Run were: 25(minimal) 27(maximal) 26(average); lengths of LREE-bank were: 1 (minimal) 50(maximal) 49(average). At best situation we must have: 26 26 26 for LRPE and 50 50 50 for LREE. It were simulated Pure Luminosity Trigger with very low thresholds on SumET SumPD for testing of creation and contents of the new LRTL-bank. At each from 220 bunches You can see rate near 400 Hz. It was made the change of e-mail with Jan Olsson with the next information: "..... READMAIL message stored : FRI, 28 FEB 92 12:10:08 MEZ Date: FRI, 28 FEB 92 11:54:57 MEZ From: Jan-Erik Olsson Subject: MAIL from F11JOL at DHHDESY3 To: Alexander Fomenko Stradsvuite! I observe a NEW BANK with name LRTL in the data stream this morning. What Format should it have ?? Paka, Jan Olsson ------------------------------------------------------------------------------- SENDMAIL message Date: FRI, 28 FEB 92 12:12:14 MEZ From: Alexander Fomenko Subject: MAIL from H1KFOM at DHHDESY3 To: Jan-Erik Olsson A.M. Fomenko, DESY -F22- Notkestrasse 85, D 2000 Hamburg 52 Tel. (040) 8998-2568 or -2074 (North Hall of HERA,CCR of H1) (permanent address: Lebedev Phys.Inst., Moscow, USSR) NODE: DHHDESY3 USERID: H1KFOM Dear Jan, At 10:55 I sent mail to You but with userid F11OLS about new bank LRTL. Now I repeate this mail to You with userid F11JOL. "... As I promised earlier I am duty to inform You about apperence of new bank at H1Lumi Data stream. Today it was first test of the new release of H1Lumi OnLine program with H1CDAQ and this new bank was appeared at H1CDAQ data flow. Its name is LRTL (luminosity bank). Its format is B32. Length of this bank is near 1 Kbyte. 1 Content of this bank is discussed now at our H1Lumi-community. But at current release it has 220 rates at Hz (multiplied on 1000.) of Pure Lumi-events at each bunces, integral rate from all bunches of Pure Lumi-events (at Hz multiplied on 1000.) and 10 different values which are used for calculation of current value of luminosity (Luminosity Trigger Efficiency Coefficient, Beam Position (for possible aperture correction) and some another values). In future we plan to place at this bank calculated value of luminosity (divided on 10**28 for example). This bank is non-event bank and is prepared at the non-readout FIC and connected to nearest event at H1Lumi data flow. This bank is included at so-called "KEEP"-bank from our branch (as proposed by Alan Campbell some days ago). It would be good if this bank it would be possible to move at non-event cartridges. First apperence of LRTL-bank at KEEP-environment was at Runs 13438, 13450,13451. Frieguency of apperence of this bank at H1Lumi data flow is option (at current release - one bank per 10 sec.). It is possible to send it more often or more rare. I am sorry for little delay with this information. I am ready to receive from You any comment on this topic...." Sorry for incorrect userid. Sincerely, Alexander Fomenko ....." 16.03.1992 ==================== H1KFOM === Run 15178 ================ At Monday 16.03.1992 it was good posibility to test the new release of the H1LumiOnlineProgram together with H1CDAQ. This posibility was used. Run 15178 was written on IBM-cartridges (temporary). It is possible move this Run on permanent cartridges during some hours. First part od this Run is written on F11JOL.H01.TESTDATA.G8483V00 the second - on F11JOL.H01.TESTDATA.G8484V00. At this Run there are new release of LRTN-bank (not full), LREC and LRPC banks at KEEP-folder and VETE-bank. It were written near 40000 events with test pulses. This data has the next H1Lumi-banks: LREC,LRPC - as Start-Run-Record and once at KEEP-folders, LREE,LRPE,LREF,LRPF,LRTE,TSTC,LRTN,LRTF,VETE,LRTL(at KEEP- -folders) and LRTB-bank as End-Run-Record. 23.03.1992 ==================== H1KFOM === Run 15445 ================ After almost 10 days of different problems with formats of our new banks which are resolved now I am glad to introduce to H1Lumi community first Run with as I hope right formats and contents. Run 15445 was written on 4 cartridges yesterday 22.03.1992. I moved this dat on my cartridges: H1KFOM.LUMI92.CAR15445 - 101810 events H1KFOM.LUMI92.CAA15445 - 102218 events H1KFOM.LUMI92.CAB15445 - 102125 events H1KFOM.LUMI92.CAC15445 - 76968 events. 383011 events at all cartridges. This Run have the next banks: LREC,LRPC - as Start Run Record and as non-event data LREE,LRPE,LREF,LRPF,LRTE,TSTC,LRTF,LRTN,VETE as event data LRTL - as non-event data LRTB - as End_Run_Record. LREC,LRPC and LRTL were written once per second at KEEP-environment. KEEP could have length 1 (LRTL-only), 2 (LREC and LRPC), 3 (LRTL,LREC and LRPC banks as non-event data). VETE-bank has format B32 and structure as was recomended S.Egli. It has 32 strings always (for current release) and 3 rows. First row - bunch-crossing number (if=0 - t0, if=-1 - t0-1, if = 1 t0+1 etc.). Contents of LREE,LRPE,LREF,LRPF are test pulses with low amplitude (85 counts at PD and 89 counts at ET). In principle it is possible get values of Trigger Sums at LRTN-bank. It were choosen the next coefficients for conversation FADC counts of Trigger Sums into GeV (0.0017 for PD,0.003 for ET and 0.0025 for ET+PD). (GeV on FADC count). At this Run it was switched off option "Zero Pedestal Finding" - so You can not see values 20001 at LREE and LRPE banks and 5001 at LRTN bank. Calibration coefficients for LREC and LRPC banks were got from second FIC where 800 simulated brems.events were the source of calibration procedure of Usik. Egor`s bunch counters (31x220) were not operated and LumiLocal Timer too - so at LRTL You can find zeros at 220-rates and non-changable value of H1Lumi Local Timer. But in principle it is possible to work with this data as good example of future data flow from H1Lumi. 1 24.03.1992 ==================== H1KFOM === Run 15487,15488 ========== It is possible to play with another data from H1Lumi-flow. Today it were written two Runs - 15487 with test pulses with large amplitude (200 at Egor counts on both detectors) and 15488 with simulated brems.events (800 x many times repeated). It is possible to find this Runs at my catalog: H1KFOM.LUMI92.CRT15487 H1KFOM.LUMI92.CRT15488 This data sets are kept on cartridges. Bank set at this Runs the same as at previous Run. 25.03.1992 ==================== H1KFOM === Test with H1 Central Trigg Yesterday H1Lumi-subdetector was tested with H1 Central Trigger and H1 Central DAQ simultaneously. Last this type test was at 4th March 1991. It was two part of testing: 1) Trigger Bits from H1LumiTrigger was transfered into H1 CTRIG and H1 CTRIG was the reason of L2Keep- and L3Keep-interrupts at our H1LumiOnLine-program. Test pulses were the reason of hits H1Lumi Trigger Bits and after tuning of our shift constant we looked at H1 OnLine Event Display screen very nice picture of our test pulses. All is OK with this part of test. 2) Testing of last release of H1LumiOnLine program with randomly appearing L2Keep-,L3Keep- and L3Reject- interrupts. After some hours of work it was found the optimal chain of processing of this interrupts. Last Run - 15529 - was started at 20:30 24.03.1992 and is continuied up to just moment (9:30 25.03.92). Little local success - but very important for nearest future. 26.03.1992 ==================== H1KFOM === Remote Run of H1Lumi ===== Due to help from Bill Haynes and Alan Campbell from yesterday it is possible to run H1LumiOnLineProgram from H1 CDAQ supervisor. 27.03.1992 ==================== H1KFOM === Runs 15500,15529,15617 === During three days it was carried out different tests of H1Lumi with H1 CTRIG and H1 CDAQ. Run 15500: First Run of H1Lumi together with H1CTRIG. Source of L2Keep - trigger bit from ET. Start Run 24.03.92 at 16:38:39. Stop Run 24.03.92 at 16:47:43. Number of Events - 25589. This Run was written on 2 cartridges: F11JOL.H01.TESTDATA.G9011V00 - first 16698 events, F11JOL.H01.TESTDATA.G9012V00 - last 8891 events, Contents of data - test pulses with low amplitude (near 70 Egor`s counts on both detectors). Without Run-Start-Record (attempt to write Run-Start-Record at previous Runs was unsuccessful - problem under studying). Bank set: H1Lumi: LREE,LRPE,LREF,LRPF,LRTE,LRTF,LRTN,VETE,TSTC. Trigger:TGPP,TBOB,TLV1,TMDM,TSTC. There are no banks: LRTL,LRTB,LRTC,LRPC. Run 15529: Run of H1Lumi together with H1CTRIG for time stability studying. Source of L2Keep - random from H1CTRIG (with random L3Keep,L3Reject). Start Run 24.03.92 at 20:23:05. Stop Run 25.03.92 at 09:37:48. Number of Events - near 1.5 million L2Keep together with L3Keep. This Run was written on 15 cartridges (as temporary data): F11JOL.H01.TESTDATA.G9014V00 - first 53808 events, .................................................. F11JOL.H01.TESTDATA.G9029V00 - last 97624 events, Contents of data - 800 brems.events many times repeated. Without Run-Start-Record (attempt to write Run-Start-Record at previous Runs was unsuccessful - problem under studying). There were near 71% of L3Keep and near 29% L3Reject. Bank set: H1Lumi: LREE,LRPE,LREF,LRPF,LRTE,LRTF,LRTN,VETE,TSTC,LRTC. Trigger:TGPP,TBOB,TLV1,TMDM,TSTC. No banks: LRTL,LRTB,LRPC. Run 15617: Run of H1Lumi together with H1CTRIG for time stability studying. New Release of H1LumiOnLineProgram (FER at L2Keep with waiting L3Keep or LrReject flags). Source of L2Keep - random from H1CTRIG (with random L3Keep,L3Reject). Start Run 25.03.92 at 19:30:13. Stop Run 26.03.92 at 08:06:29. 1 Number of Events - near 0.6 million L2Keep together with L3Keep. This Run was written on 7 cartridges (as temporary data): F11JOL.H01.TESTDATA.G9032V00 - first 7579 events, .................................................. F11JOL.H01.TESTDATA.G9038V00 - last 93732 events, Contents of data - 800 brems.events many times repeated. Without Run-Start-Record (attempt to write Run-Start-Record at previous Runs was unsuccessful - problem under studying). At this Run it was another L3Keep-frequency (near 27% L3Keep, 73% L3Reject). Bank set: H1Lumi: LREE,LRPE,LREF,LRPF,LRTE,LRTF,LRTN,VETE,TSTC. LREC,LRPC,LRTL - as non-event data at KEEP-folders. Trigger:TGPP,TBOB,TLV1,TMDM,TSTC. Run was aborted (not stopped as needed for writting of End-Run-Record) So - LRTB-bank is absent. Last two Runs - specially for testing of time stability of H1Lumi+ +H1CTRIG+H1CDAQ operation. 28.03.1992 ==================== H1KFOM === StartRun,StopRun,AbortRun= Today was tested the creating of RunStartRecord at Mode 0 during working together with H1CDAQ and H1CTRIG. Now this little problem is resolved. AbortRun and StopRun also were tuned at H1LumiOnLine. From this day there exists the release of H1LumiOnLine for working with H1CTRIG and H1CDAQ without problems at this areas. 29.03.1992 ==================== H1KFOM === Proposal ================= P R O J E C T O F M E M O R Y M A P P I N G F O R L U M I N O S I T Y M E A S U R E M E N T S (29.03.1992 - Fomenko A.M.) - after discussions with A.P.Usik from 26 and 27 March 1992 D0A5E0C0 - D0A5EB87 - Luminosity Measurements Areas $AC8 bytes = 2760 bytes = 76 + 2684 bytes ______________________________________________________________________ D0A5E0C0 - D0A5E10B - Area 1 (Total Luminosity Measurements Area) $4C bytes = 76 bytes = (4+8+7)*4 bytes ______________________________________________________________________ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ D0A5E0C0 - D0A5E0CF - Region 0 (Common Constants for Area 1) $10 bytes = 16 bytes = 4*4 bytes ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ D0A5E0C0 - - DT1=Time Period for getting of the new Current Total Lumi Value (cm-2sec-1), sec. - LONGINTEGER D0A5E0C4 - - WT= WhichTime for getting of the new Current Total Lumi Value 1 - Mac,2 -LumiLocalTimer,3-Revolu- tion Counterer - LONGINTEGER: D0A5E0C8 - - CL= Value of WhichTime Counter of the last getting of Total Current Luminosity value LONGINTEGER D0A5E0CC - - MT= Value of MacintoshTime Counter of the last getting of Current Total Luminosity value LONGINTEGER ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ D0A5E0D0 - D0A5E0EF - Region 1 (Total Luminosity Measure- ments First Region) Run, Running, Data Taking $20 bytes = 32 bytes = 8*4 bytes ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ D0A5E0D0 - - A1= Current Total Luminosity value di- vided on Norm.Coeff.(the next cell) at (cm-2sec-1 units) - REAL: D0A5E0D4 - - Norm.Coeff. for Total Current Lu- minosity Value (10**10 at the first release) REAL D0A5E0D8 - - B1= Current Run Integral Luminosity va- lue divided on Norm.Coeff.(the next cell) at (cm-2 units or ,may be,pb) REAL Zeroed at Start H1 Run Incremented on A1*DT1 each DT1 sec. D0A5E0DC - - Norm.Coeff. for Current Run Integral Luminosity value (10**10 for cm-2 units) - REAL 1 D0A5E0E0 - - C1= Current Running Integral Luminosity value divided on Norm.Coeff.(the next (the next cell) (cm-2 units or pb) cell) at (cm-2 units or pb) - REAL Zeroed at Start First H1 Run at Running (after Ramping) Incremented on B1 after end of H1 Run D0A5E0E4 - - Norm.Coeff. for Current Running In- tegral Luminosity value (10**10 for cm-2 units) - REAL D0A5E0E8 - - D1= Current Data Taking Integral Lumi- nosity value divided on Norm.Coeff. (the next cell) (cm-2 units or pb) REAL Zeroed at Start First H1 Run at Data Taking Incremented on C1 after end of Run- ning D0A5E0EC - - Norm.Coeff. for Current H1 Data Ta- king Integral Luminosity value (10**10 for cm-2 units) - REAL ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ D0A5E0F0 - - Region 2 (Total Luminosity Measure- ments Second Region) Time Period, Running, Data Taking $1C bytes = 28 bytes = 7*4 bytes ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ D0A5E0F0 - D0A5E10B - DT2=TimePeriod for counting B2 (next cell),sec.,LONGINTEGER D0A5E0F4 - - B2= Current TimePeriod Integral Lumi- sity value divided on Norm.Coeff. (the next cell) (cm-2 units or pb) REAL Zeroed at Start TimePeriod Incremented on A1*DT1 each DT1 sec. D0A5E0F8 - - Norm.Coeff. for Current Run Integ- ral Luminosity value (10**10 for cm-2 units) - REAL D0A5E0FC - - C2= Current Running Integral Luminosity value divided on Norm.Coeff. (the next cell) (cm-2 units or pb) REAL Zeroed at Start of Running (after Ramping) Incremented after end of TimePeriod on B2 (each DT2 sec.) D0A5E100 - - Norm.Coeff. for Current Running In- tegral Luminosity value (10**10 for cm-2 units) - REAL D0A5E104 - - D2= Current Data Taking Integral Lumino- sity value divided on Norm.Coeff. (the next cell) (cm-2 units or pb) REAL Zeroed at Start of H1 Data Taking Incremented C2 after end of Running D0A5E108 - - Norm.Coeff. for Current Data Taking Integral Luminosity value value (10**10 for cm-2 units) - REAL _______________________________________________________________________ D0A5E10C - D0A5EB77 - Area 2 (Bunches Luminosity Measure- ments Area) $A7C bytes = 2684 bytes = = (8 + 220*3 + 3)*4 bytes _______________________________________________________________________ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ D0A5E10C - D0A5E11B - Region 0 (Common Constants for Area2) $20 bytes = 32 bytes = 8*4 bytes ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ D0A5E10C - - DT3=Time Period for getting of the new Current Bunches Lumi Values (cm-2sec-1), sec. - LONGINTEGER D0A5E110 - - WT2=WhichTime for getting of the new Current Bunches Lumi Values; 1- Mac,2 -LumiLocalTimer,3-Revolu- tion Counter LONGINTEGER D0A5E114 - - CL2=Value of WhichTime Counter of the last getting of Bunches Current Luminosity values - LONGINTEGER D0A5E118 - - MT2=Value of MacintoshTime Counter of the last getting of Current Bunches Luminosity values - LONGINTEGER: D0A5E11C - - PB = First PilotBunch Number (0-219) LONGINTEGER D0A5E120 - - NPB= Number of PilotBunches (1-10) LONGINTEGER D0A5E124 - - PNB =First Non-PilotBunch Number(0-219) LONGINTEGER D0A5E128 - - NPNB=Number of Non-PilotBunches (1-210) LONGINTEGER 1 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ D0A5E12C - D0A5EB87 - Region 1 (Bunches Luminosity Measu- rements First Region) Run, Running; $A5C bytes = 2652 bytes = (220*3 + 3)*4 bytes ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ D0A5E12C - D0A5E49B - A3(220) = Current Bunches Luminosity va- lue divided on Norm.Coeff. (the next cell) (cm-2sec-1 units) - REAL: D0A5E49C - - Norm.Coeff. for Current Bunch.Lumi- nosity value (10**10 at the first release) -REAL: D0A5E4A0 - D0A5E80F - B3(220)= Current Run Bunches Luminosity values divided on Norm.Coeff. (the next cell) (cm-2 units or may be,pb) REAL Zeroed at Start H1 Run Incremented on A3(i)*DT3 each DT3 s. D0A5E810 - - Norm.Coeff. for Current Run Bunches Luminosity value (10**10 for cm-2 units) - REAL D0A5E814 - D0A5EB84 - C3(220)= Current Running Integral Bun- ches Luminosity value divided on Norm.Coeff.(the next cell) (cm-2 units or pb) REAL Zeroed at Start First H1 Run at Running (after Ramping) Incremented on B3(i) after end of H1 Run D0A5EB84 - - Norm.Coeff. for Current Running In- tegral Luminosity value (10**10 for cm-2 units) - REAL 30.03.1992 ==================== H1KFOM === New edition of proposal == P R O J E C T O F M E M O R Y M A P P I N G F O R L U M I N O S I T Y M O N I T O R I N G (30.03.1992 - Fomenko A.M.) second edition: - after putting of Usik's and Egor's remarks (30.03.1992) first edition: - after discussions with A.P.Usik from 26 and 27 March 1992 D0A5E0C0 - D0A5EF38 - Luminosity Measurements Areas $E78 bytes = 3704 bytes = 132+3572 bytes ______________________________________________________________________ D0A5E0C0 - D0A5E144 - Area 1 (Total Luminosity Measurements Area) $84 bytes = 132 bytes = (12+14+7)*4 bytes ______________________________________________________________________ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ D0A5E0C0 - D0A5E0F0 - Region 0 (Common Variables for Area 1) $30 bytes = 48 bytes = 12*4 bytes ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ D0A5E0C0 - - DT1=Time Period for getting of the new Current Total Lumi Value (cm-2sec-1), sec. - LONGINTEGER D0A5E0C4 - - WT= WhichTime for getting of the new Current Total Lumi Value 1 - MacTicks,2-LumiLocalTimer,3-Re- volution Counter - LONGINTEGER D0A5E0C8 - - CL= Value of WhichTime Counter of the last getting of Total Current Luminosity value LONGINTEGER D0A5E0CC - - MT= Value of MacintoshTime Counter of the last getting of Current Total Luminosity value, sec from 1.01.1904 LONGINTEGER D0A5E0D0 - D0A5E0E0 - Xold(4) - "old" values of two counters from Fast Card (1) - all bunch crossings (bits 32- -39) (2) - all bunch crossings (bits 00- -31) (3) - beam Xing during L1Atv (bits 32-39) (4) - beam Xing during L1Atv (bits 00-31) Filled at Start H1 Run and each DT1-period 1 D0A5E0E0 - D0A5E0F0 - Xnew(4) - "new" values of two counters from Fast Card (1) - all bunch crossings (bits 32- -39) (2) - all bunch crossings (bits 00- -31) (3) - beam Xing during L1Atv (bits 32-39) (4) - beam Xing during L1Atv (bits 00-31) Filled at each DT1 period and at H1 Run Stop ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ D0A5E0F0 - D0A5E128 - Region 1 (Total Luminosity Measure- ments First Region) Run, Running, Data Taking $38 bytes = 56 bytes = 14*4 bytes ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ D0A5E0F0 - - A1= Current Total Luminosity value di- vided on Norm.Coeff.(the next cell) at (cm-2sec-1 units) - REAL: D0A5E0F4 - - Norm.Coeff. for A1 (10**10 at the first release) REAL D0A5E0F8 - - B1= Current Run Integral Luminosity va- lue divided on Norm.Coeff.(the next cell) at (cm-2 units or ,may be,pb) REAL Zeroed at Start H1 Run Incremented on A1*DT1 each DT1 sec. and at EndOfRun A1*DT0, where DT0 - time period from last getting of A1 up to EndOfRun (less then DT1) D0A5E0FC - - Norm.Coeff. for B1 (10**10 for cm-2 units) - REAL D0A5E100 - - B11=Current Run Integral Luminosity va- lue in 'L1Atv'-periods (H1Live time) divided on Norm.Coeff.(the next cell) at (cm-2 units or ,may be,pb) REAL Zeroed at Start H1 Run Incremented on A1*DT1*K each DT1 sec and at EndOfRun A1*DT0*K, where DT0 - time period from last getting of A1 up to EndOfRun (less then DT1) K -ratio of two counts from FastCard D0A5E104 - - Norm.Coeff. for B11 (10**10 for cm-2 units) - REAL D0A5E108 - - C1= Current Running Integral Luminosity value divided on Norm.Coeff(the nextt cell) at (cm-2 units or pb) - REAL Zeroed at Start First H1 Run at Running (after Ramping) Incremented on B1 after end of H1 Run D0A5E10C - - Norm.Coeff. for Current Running In- tegral Luminosity value (10**12 for cm-2 units) - REAL D0A5E110 - - C11=Current Running Integral Luminosity value in 'L1Atv'-periods (H1Live time) divided on Norm.Coeff(the nextt cell) at (cm-2 units or pb) - REAL Zeroed at Start First H1 Run at Running (after Ramping) Incremented on B11 at end of H1 Run n D0A5E114 - - Norm.Coeff. for C11 (10**12 for cm-2 units) - REAL D0A5E118 - - D1= Current Data Taking Integral Lumi- nosity value divided on Norm.Coeff. (the next cell) (cm-2 units or pb) REAL Zeroed at Start First H1 Run at Data Taking Incremented on C1 after end of Run- ning D0A5E11C - - Norm.Coeff. D1 (10**14 for cm-2 units) - REAL D0A5E120 - - D11=Current Data Taking Integral Lumi- nosity value in 'L1Atv'-periods (H1Live time) divided on Norm.Coeff. (the next cell) (cm-2 units or pb) REAL Zeroed at Start First H1 Run at Data Taking Incremented on C11 at end of Running D0A5E124 - - Norm.Coeff. for D11 (10**14 for cm-2 units) - REAL 1 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ D0A5E128 - D0A5E144 - Region 2 (Total Luminosity Measure- ments Second Region) Time Period, Running, Data Taking $1C bytes = 28 bytes = 7*4 bytes ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ D0A5E128 - - DT2=TimePeriod for counting B2 (next cell),sec.,LONGINTEGER D0A5E12C - - B2= Current TimePeriod Integral Lumi- sity value divided on Norm.Coeff. (the next cell) (cm-2 units or pb) REAL Zeroed at Start TimePeriod Incremented on A1*DT1 each DT1 sec. D0A5E130 - - Norm.Coeff. for B2 (10**10 for cm-2 units) - REAL D0A5E134 - - C2= Current Running Integral Luminosity value divided on Norm.Coeff. (the next cell) (cm-2 units or pb) REAL Zeroed at Start of Running (after Ramping) Incremented after end of TimePeriod on B2 (each DT2 sec.) D0A5E138 - - Norm.Coeff. for C2 (10**12 for cm-2 units) - REAL: D0A5E13C - - D2= Current Data Taking Integral Lumino- sity value divided on Norm.Coeff. (the next cell) (cm-2 units or pb) REAL Zeroed at Start of H1 Data Taking Incremented C2 after end of Running D0A5E140 - - Norm.Coeff. for D2 value (10**14 for cm-2 units) - REAL _______________________________________________________________________ D0A5E144 - D0A5EF38 - Area 2 (Bunches Luminosity Measure- ments Area) $DF4 bytes = 3572 bytes = = (9+220*3+3+220+1)*4 bytes _______________________________________________________________________ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ D0A5E144 - D0A5E168 - Region 0 (Common Constants for Area2) $24 bytes = 36 bytes = 9*4 bytes ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ D0A5E144 - - DT3=Time Period for getting of the new Current Bunches Lumi Values (cm-2sec-1), sec. - LONGINTEGER D0A5E148 - - WT2=WhichTime for getting of the new Current Bunches Lumi Values; 1- Mac,2 -LumiLocalTimer,3-Revolu- tion Counter LONGINTEGER D0A5E14C - - DTA= Time Period for averaging of the Averaged Bunches Lumi Values (cm-2sec-1), sec. - LONGINTEGER b WhichTime is the same as at DT3. D0A5E150 - - CL2=Value of WhichTime Counter of the last getting of Bunches Current Luminosity values - LONGINTEGER D0A5E154 - - MT2=Value of MacintoshTime Counter of the last getting of Current Bunches Luminosity values - LONGINTEGER: D0A5E158 - - PB = First PilotBunch Number (0-219) LONGINTEGER D0A5E15C - - NPB= Number of PilotBunches (1-10) LONGINTEGER D0A5E160 - - PNB =First Non-PilotBunch Number(0-219) LONGINTEGER D0A5E164 - - NPNB=Number of Non-PilotBunches (1-210) LONGINTEGER ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ D0A5E168 - D0A5EBC4 - Region 1 (Bunches Luminosity Measu- rements First Region) Run, Running; $A5C bytes = 2652 bytes = (220*3 + 3)*4 bytes ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ D0A5E168 - D0A5E4D8 - A3(220) = Current Bunches Luminosity va- lue divided on Norm.Coeff. (the next cell) (cm-2sec-1 units) - REAL: D0A5E4D8 - - Norm.Coeff. for A3(i) (10**10 at the first release) -REAL: D0A5E4DC - D0A5E84C - B3(220)= Current Run Integral Bunches Lu minosity values divided on Norm. Coeff.(the next cell) (cm-2 units or may be,pb) REAL Zeroed at Start H1 Run Incremented on A3(i)*DT3 each DT3 s. 1 D0A5E84C - - Norm.Coeff. for B3(i) (10**10 for cm-2 units) - REAL D0A5E850 - D0A5EBC0 - C3(220)= Current Running Integral Bun- ches Luminosity value divided on Norm.Coeff.(the next cell) (cm-2 units or pb) REAL Zeroed at Start First H1 Run at Running (after Ramping) Incremented on B3(i) after end of H1 Run D0A5EBC0 - - Norm.Coeff. for C3(i) (10**10 for cm-2 units) - REAL ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ D0A5EBC4 - D0A5EF38 - Region 2 (Bunches Luminosity Measu- rements Second Region) $374 bytes = 884 bytes = (220 + 1)*4 bytes ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ D0A5EBC4 - D0A5EF34 - B4(220)= Averaged Bunches Luminosity values divided on Norm.Coeff. (the next cell) (cm-2sec-1 units) REAL Filled with A3(i) on first H1 Run at Running (after Ramping) Calculated on iteractive formula each DT3 period D0A5EF34 - - Norm.Coeff. for B4(i) (10**10 at first release) - REAL: 31.03.1992 ==================== H01USA === lumi formula ============= Calculation of luminosity in on-line (for A.Fomenko request) If we want to measure the luminosity of collision of Ne electr. bunches with Np proton bunches, we must take into account (and subtract) the contribution from collision of electron bunches with residial pipe gas. It is possible if Ne>Np, it means that we have so called "pilots" bunches, which don't collide with proton bunches. In addition we must know relative intensities of electron bunches(IEi). Then we can use the following formulas for calculation of luminosity event rates: Rlumi = Rall - Rpilots * (IEall/IEpilots) or Rlumi = Rcollide - Rpilots * (IEcollide/IEpilots), where Rall,Rpilots,Rcollide - sum rates for all, pilot or collided bunches correspondently; IEall,IEpilots,IEcollide - sum intensities (currents) for all, pilot or collided electron bunches ( IExx = Sum(IEi) ). i=xx We can calculate above mentioned rates Rxx = Sum(Ri) , i=xx where Ri - rate for bunch number i (extracted from Egors trigger module). It is more convinient to have scalers for Rxx, but we have it only for Rall ("blue" scaler), but cannot use directly, because we haven't one for pilot bunches (they are very pilot). For lumi events rate for every bunch we have: Rlumii = Ri - Rpilots *(IEi/IEpilots) After this we can at last calculate luminosity: LUMI = Keff*Rlumi/(SIG*Kgeom), where Keff - efficiency of Lumi Trigger (currently monitoring in on-line programm); SIG - Lumi trigger cross section (brems cross section with taking into account energy-geometrical acceptance of our subdetector) - provided by S.Levonian for different combinations of electron and proton beam energies. Kgeom - correction coefficient for SIG ( depends on beam position)- also provided by S.Levonian. For bunch luminosity we have correspondently: LUMIi = Keff*Rlumii/(SIG*Kgeom) . 1 04.04.1992 ==================== H1KFOM === No beam yet ============== Yesterday from 19:00 we was waiting for e-beam with 12 GeV at HERA e-ring (it was promised by F.Brasse yesterday evening). From 19:00 up to 11:30 today it was not any activity of e-beam at HERA (as was shown with our monitoring system). Today morning I looked our beam archive picture (only Veto-counter picture) - with threshold at Veto with 20 Egor's units - there were rates during all night near 0.7 - 0.8 Hz (cosmic background). Today morning (from words of our Run Coordinator K.Meier) it was pro- mised from machine people the injection of electrons but at 11:20 from phone talking - there are some problems with PETRA power supply - it must get some time. We are waiting for yet. It was no beam up to 16:30 04.04.1992 also. It was no beam up to 14:30 05.04.1992 also. 06.04.1992 ==================== H1KFOM === First e-beam at April92 == Today early morning it was the first e-beam at April 92. Beam was looked at our BeamHistory picture from 4:47 morning up to 10:13 (with 3 little pauses). Energy of e-beam was 12 GeV. After some short pause e-beam is injected again and now we are looking for the e-beam (13:20) also. Number of bunches - 1. 06.04.1992 ==================== H1KFOM === Video-card on H1Lumi2 ==== Today Erwin Deffur installed on H1Lumi2 MacII the special videocard for creating of video-signal at our H1Lumi2 MacII which can be retranslated to any black-white TV-screen which can be disposed anywhere at DESY. Special system of Video-signal retranslation is preparing now at H1CDAQ- and H1CTRIG- teams. In principle HERA machine people will look any of H1Lumi-pictures at own TV-screen at HERA Control Room (some kind of alternative to previous retranslation of our information through H1LAN). Information about common current of e-beam and bunch currents are prepared now and will be soon ready (we need this information for on-line luminosity calculation). H1CTRIG-team is preparing now special tools for delivering of this information through H1LAN to H1-subdetectors (for H1Lumi too). 07.04.1992 ==================== H1KMAL === ET - geometry ======= ... Taking into account Levonian"s remarks about difference of opinion about OLD and NEW geometry of ET- hodoscop, I have checked the detector position: Distance between e-beam pipe axis and ET-axis is about 160.5 mm. that corresponds to old position - 160 mm. e-beam ____________________________________ ------|------ | 42 | 43 | | | | 47 | 48 | / | \ |__________________________________! ________|_______** | | | | | | | | | | ** |__________________________________! \ | / |__________________________________| ------|------ | 0 | 1 | 2 | 3 | 4 | 5 | 6 ! |__________________________________| | 160.5 mm | -->|----------------------------|<-- The view down e-beam 08.04.1992 ==================== H1KFOM === Last HERA-news =========== The copy of the information from pinboard at H1 Control Room: " 8.04.92 08:30. HERA news: setting-up injection line stored beam later today " 08.04.1992 ==================== H1KFOM === Last HERA-news =========== The copy of the information from pinboard at H1 Control Room: " April 8 16.00 LINAC II problems Restart near 17.00" 09.04.1992 ==================== H1KFOM === Last HERA-news =========== The copy of the information from pinboard at H1 Control Room: " April 9 09.00 access to HERA until 12:00" 1 09.04.1992 ==================== H01USA === e-beamactivity&calibration It was some e-beam activity last shift: Time(8-9.04.92) rate,Hz (WC:HV=700/700V,thr=8/8 ) 19:22 - 21:32 80-100 21:50 - 23:00 50-80 23:36 - 23:49 50 24:00 - 00:05 40 00:11 - 00:19 30 1 bunch, Ne=1.0e+10 . Better to return to October values of HV and thresholds of WC for comparison. I hope that next shifts we'll start to calibrate all what we can. Let me remind that for quality calibration of subdetector channels we must have maximal energy range on Eet-Epd plot to decrease the calibration error of correspondence between electron and photon arms. If Emin - Emax - the energy range for electrons registrated by ET ( defined by geometrical acceptance of ET) and E0 - e-beam energy, than we must have for PD and ET thresholds (PD&ET&AVW trigger): ETthr =< Emin, PDthr =< E0-Emax. From Levonian's calculations we know for present ET geometry: E0=12.0 GeV -> Emin=2.2 GeV, Emax= 9.2 Gev E0=26.7 GeV -> Emin=5.0 GeV, Emax=21.0 Gev, that corresponds to the following thresholds: E0=12.0 GeV -> ETthr=2.2 GeV, PDthr= 2.8 Gev E0=26.7 GeV -> ETthr=5.0 GeV, PDthr= 5.7 Gev. So we must make some iteration joint thresholds/channels calibration or better use ET+PD trigger with high threshold: 10 and 24 GeV for 12 and 26.7 GeV e-beams correspondently. To provide homogenious distribution of event on ET/PD plot (instead of 1/E distribution) it is necessary to add some new rejectiont into calibration algorithm: two counters - Nless and Nmore for events with Eet > or < than (2*Emin+Emax)/3. If for next event Nmore > Nless, than we reject this event as calibration event. 09.04.1992 ==================== H1KFOM === e-beam at night 8-9.04.92 It was observed at H1Lumi Beam Archive picture that it was 2 periods of activity at e-beam of HERA last night: 1) from 20:24 08.04.1992 up to 01.11 09.04.1992 - near 3.5 hours; 2) from 03:22 09.04.1922 up to 06:13 09.04.1992 - near 3 hours. At both periods of activity it was looked only one (may be two) bunch with bunch number 154(155) at our units. Maximal frequency of counts of WaterVeto was achived at the second period of e-beam activity - near 200 Hz at 4:40 09.04.1992 (threshold at Water Veto was installed by Egor not SW manner and must be constant during of nearest period). Bunch statistics pictures: group 1: WV & anti(PD) & anti(ET) - peak at 154 with 588942 max group 2: anti(WV) & PD & anti(ET) - no any peaks with 27969 max near 27000 at all bunches group 3: WV) & PD & anti(ET) - peak at 154 with 61 max group 4: anti(WV) & anti(PD) & ET - peak at 154 with 57293 max near 20000 at all bunches group 5: WV & anti(PD) & ET - peak at 154 with 1975 max group 6: anti(WV) & PD & ET - peak at 154 with 14 max near 2-3 at all bunches group 7: WV & PD & ET - no any statistics(all zero) Thresholds which were installed yesterday by Sasha Usik were: PD - 40, ET - 10, WaterVeto - 8. 09.04.1992 ==================== H1KFOM === Last HERA-news =========== The copy of the information from pinboard at H1 Control Room: " April 9 12.00 Restart Injection " 09.04.1992 ==================== H01USA === line news ================ DELO LEVONIANA JIVET I POBEJDAET The new logbook is organized. It is so called The Line Logbook for information concerning Moscow-DESY computer line. Copy members lll (List Line Logbook) and ell (Edit Line Logbook) from my CLIST. More nice things: old fasion WS Apollo DN3500 was installed in our 125b room. Documentation for our future RISC WS was received (see lll). 1 10.04.1992 ==================== H1KFOM === First attempt of calibr. = It was very good 12 GeV e-beam all this day (and previous night). We had some local successes at different areas: first attempt of calibration, first observing of beam profile, first observing of Lumi-trigger efficiency coefficient behaivour, first real Energy plot (Ee/Epd), first seance of testing of S.Levonian H1Lumi Reconsruction Package with real events and new detectors. All this news I promise to write tomorrow. But: we have now 16 calibrated cells at PD and 11 cells at ET (very preliminary - for internal needs). 11.04.1992 ==================== H1KFOM === Last HERA-news =========== The copy of the information from pinboard at H1 Control Room: "Last update April 11, 13:00 setting-up injection wrong quadrupole not yet moved most likely no ramping this weekend" 11.04.1992 ==================== H1KFOM === More detail about 10.04.92 After Egor's night activity (from 09.04.92 to 10.04.92) the H1Lumi subsystem is working right on the first view. 1) For example - bunch statistics at 14:10 10.04.1992 were the next: group 1: WV & anti(PD) & anti(ET) - peak at 15 with 1879564 max group 2: anti(WV) & PD & anti(ET) - peak at 15 with 227434 max group 3: WV & PD & anti(ET) - peak at 15 with 729775 max group 4: anti(WV) & anti(PD) & ET - peak at 15 with 4177643 max group 5: WV & anti(PD) & ET - peak at 15 with 296693 max group 6: anti(WV) & PD & ET - peak at 15 with 67074 max group 7: WV & PD & ET - peak at 15 with 224540 max Thresholds which were installed yesterday by Egor were: PD - 15, ET - 15, WaterVeto - 6. 2) There was attempt to calibrate existing release of our detectors: with HV-values from files - "FileHVETdefault.22.01.92" and "FileHVPDdefault.03.02.92" with only changing HV on VETO-counters - both values are now 700 V (not 800 V as at the second file). Thresholds were the same as at previous puncte (15,15,8). It was switched off Veto-counter from calibration - it were calibrated only PD- and ET-cells. Trigger was chosen - Sum(ET) & Sum(PD). Algorithm for calibration - Usik's. The next option were installed: BeamEnergy = 12.0 GeV CutHigh = 15.0 GeV CutLow = 9.0 GeV DeltaET = 6.5 cm DelatPD = 4.0 cm ccw = 0.02 ETPDFix = 0 a) first attempt - from start values of coefficients as 1.0 for both detectors (this is relative values - for real MeV/FADCcount this values must be multiplied on own coeeficients - 3.89 for PD and 3.65 for ET). This attempt was unsuccesful - the values of coeffici- ents became negative at PD-cells. After looking on energy distribution with this start values of coeffi- cients - ET-energy was looked resonable - PD-energy had maximum at 30 GeV point - it was decided to decrease all start values of coeffi- cients at PD-cells from 1.0 to 0.333. b) the second attempt seems resonable and after some hours of permanent calibration at the both FICs we have now the preliminary set of calibration coefficients for our PD- and ET-cells: (16 PD-cells and 11 ET-cells had "good" values of calibrating weights - more then 10.0 relative units). In principle all cells had the values of this weight more then start value - 0.65 - at ET-cells minimal value - 1.1, at PD-cells - minimal value - 3.6. Number of events passed through calibration procedure - 16529 (near 35% from trigger decisions about candidate to Rough Lumi event. Full set of calibration coefficients is the next(with weight at low) PD - detector pd20=0.278 0.287 0.268 0.325 0.297 3.6 4.6 43.4 13.4 10.3 pd15=0.301 0.347 0.199 0.094 0.335 5.8 32.5 169.8 311.5 36.5 pd10=0.209 0.142 0.132 0.105 0.380 8.2 58.3 131.9 384.2 38.1 pd05=0.297 0.170 0.127 0.137 0.289 5.3 32.0 105.0 112.4 36.5 pd00=0.312 0.275 0.325 0.318 0.313 2.7 11.2 6.2 7.8 4.5 1 ET - detector et42=0.959 0.978 0.947 0.981 0.981 0.976 0.999 2.8 1.3 3.6 1.1 1.8 1.4 1.4 et35=1.053 0.938 0.999 0.960 1.035 0.980 0.978 2.4 4.7 3.4 3.2 1.8 2.0 1.3 et28=1.183 1.318 1.232 1.170 1.012 1.019 1.013 11.7 24.8 2.9 3.9 4.4 1.4 1.5 et21=1.349 0.381 0.499 2.131 1.277 0.987 0.991 1388.1 1821.2 1575.5 562.1 3.5 1.3 1.5 et14=0.831 0.856 0.888 1.006 1.007 1.002 0.912 28.5 26.1 28.2 14.6 12.9 1.7 6.2 et07=0.986 0.856 0.984 1.039 1.014 1.023 1.031 1.4 2.4 2.4 1.9 2.2 1.3 3.0 et00=0.964 0.959 0.977 0.971 0.990 0.956 0.974 1.2 2.0 1.4 1.1 2.6 2.4 1.5 During this very long calibration period (with good intensity - maximal rate of WaterVeto was near 3.5Khz and rate of trigger near 150-200 Hz) machine people made some manipulations with e-beam position on the face of our PD-detector. We looked the beam position at different areas of face of PD. This is the answer why so many cells were calibrated (preliminary). During calibration procedure we permanently could look the different energy distributions: Sum rec. energy, ET rec. energy, PD rec.energy Sum deposited energy, PD dep. energy and Et dep. energy. At the "end of beam" time this disributions were the next: Sum rec. energy: mean value - 11.80 GeV, dE = 1.10 GeV; low value - 9 GeV (SW made threshold) high value - near 16 Gev ET rec.energy: low value - 6 GeV (SW made one bin peak) high value - near 8 GeV PD rec.energy: low value - 3 GeV (SW made threshold) high value - near 9 GeV Sum dep.energy: mean value - 12.54 GeV, dE = 1.45 GeV low value - 8 GeV high value - near 18 Gev ET dep.energy: low value - 3 GeV high value - near 10 GeV PD dep.energy: low value - 3 GeV high value - near 13 GeV 3) Shortly about observing of beam-profile: during calibration it was possible to look the two-dimensional plot of X- and Y-coordinates of hitted photons fron bemstrahlung events on the face of PD-detector. Levonian was right some month ago - reconstruction of coordinates is not good - we clear look the cell boundaries (pieces of plot with pu- re statistics). In principle this two-dimensional plot shows the last 1000 coordinates. If we have 9Hz the rate of reconstruction - for near 2min we have full updated picture of beam-profile - 2 min. minimum delay of reaction of our picture on machine people manipulation. For fast monitoring of beam position we have two values which are updated after each new Lumi-event and averaged on the last 25 Lumi-events - near 3 sec. only delay after machine people manipulation. Yesterday we could look this very interesting pictures on our MacII. 4) Luminosity event trigger efficiency. Yesterday we could see first pictures of behaivour of this coeffici- ent with time and to look the absolute value - near 0.4. It must be studied and understood. I have the all values of different program counters - which were reasons of cutting of some Lumi-candidates. 5) First observation of energy plot ET/PD. Very bad picture - first opinion. SW made thresholds and bad resolution at this area of plot made this picture not undestandable - but in principle it seems reasonable. 6) First impressions about H1LumiReconstruction package. In principle all is OK. Something must be undestood (SW thresholds for example). Very interesting fact - at ET coordinate plot we looked that hitted only 4 nearest to beam-pipe rows. At 5,6,7 row there are almost no hits. The wide of Y-distribution is not the same as at 800 simulated events - at real events it is more then at simulated. And the last: It seems that calibration coefficients are depended from rates. If cell is at centrum of beam position at the face of our PD-detector - the coefficient became with time another value. But it is very preliminary. 1 12.04.1992 ==================== H1KFOM === Last Hera-news =========== The copy of the information from pinboard at H1 Control Room: "Last update April 12, 12:00 wrong quadrupole not yet moved First ramping tests this afternoon" 12.04.1992 ==================== H1KFOM === First rampings =========== Today from 16:45 up to 19:15 we looked for the first attempts of rampings at HERA e-ring. Start energy of e- was 12 Gev. After some manipulation of HERA-people the energy was 14 Gev, 17 Gev, 22 GeV and 25 GeV. During last step of ramping from 22 to 25 GeV we looked for very large rates on VetoVall global OR counters (maximum was 47 KHz - without any e-beam this rate is near 100 Hz - cosmic BG). Our Veto Counter had rate near 20-30 Hz and before moment when beam was lost the rate of Water veto counters was near 90 Hz. Ramping finished unsuccesfully - e-beam was lost. At the ET-coordinate plot we looked another picture as 10.04.92 - all raws were members of electron hits (not only 4 nearest to beam pipe). The rate of coincidence SumET & SumPD was low during all this period (at 20 times less then rate of WaterVeto). 13.04.1992 ==================== H1KFOM === Last HERA-news =========== The copy of the information from pinboard at H1 Control Room: "Last update April 13, 08:00 HERA has reached near 26 GeV (big losses) e-activity this morning possible access this afternoon" 13.04.1992 ==================== H1KFOM === High Rates on WaterVeto == From 13:17 this day up to 13:32 this day (almost 15 min.) machine people else one had attempt to make ramping and store 26GeV e- but without success - it were large losses again. At the our monitoring picture we looked very high rates on Veto Wall counters (near 100 kHz) and very high rate on our WaterVeto - almost 50 kHz (from 1 bunch ! not very high intensity at bunch - at 2 times less then yesterday from 22.00 - up to 23.00 when the first attempt to store 26. Gev e- was made - near 0.5 * 10**10 particles per this single bunch). 14.04.1992 ==================== H1KFOM === Last HERA-news =========== The copy of the information from pinboard at H1 Control Room: "Last update April 14, 09:00 This is a "stable" 26.5 GeV electron beam it will stay the full morning (PETRA is on gamma's)" 14.04.1992 ==================== H1KFOM === Night 13-14.04.92 ======== e-beam activity began near 02:48 and was continued up to 09:52. It was looked 8 attempts of ramping: 03:25, 03:58, 04:22, 04:38, 05:00 05:13, 06:33 and 08:58. Three from this rampings were with the very high frequencies on the VetoWall and WaterVeto: 3:58 - VetoWall up to 108kHz, WaterVeto up to 34 kHz (near 7min.) 4:22 - VetoWall up to 108kHz, WaterVeto up to 34 kHz (near 2min.) 5:13 - VetoWall up to 108kHz, WaterVeto up to 40 kHz (near 15 min.) Most succesful was 05:13 ramping with e-beam life time after end of ramping (which was near 15 min.) near 60 min. At this 60 min period we had very stable rate on our WaterVeto (near 70 Hz). Last ramping at 08:58 was at the period of update HERA news on H1 Control Room's pinboard. The promising of machine people "Full morning" was not made: beam was lost at 9:05. Last attempt of activity was at 9:23 (without ramping) and any acti- vity of e-beam was stopped from 9:52 up to now (11:00). 14.04.1992 ==================== H1KFOM === WV Noncorellated Activity During this day it was looked the activity of our WaterVeto which was noncorellated with VetoWall activity: a) at 11:30 it was looked peak of rate at WaterVeto from 2-3 Hz up to 70-80 Hz (on VetoWall - nothing); b) at 12:55 it was looked decrementing of rate on WaterVeto from 2-3 Hz up to 0.5-1Hz (ordinary cosmic BG) - on VetoWall - without any changing; c) at 13:17 it was looked peak of rate on WaterVeto from 0.5-1 Hz up to 70-80 Hz and during next 15 min the level of rate was near 2-3 Hz (VetoWall - nothing); 1 d) at 13:23 the level of WaterVeto rate was decremented again on cosmic background level (0.5 - 1 Hz) - VetoWall nothing; e) at 13:40 the level of WaterVeto rate was incremented on the level 2-3Hz (VetoWall - nothing). Run Coordinator asked - all is OK with Your WaterVeto? Not undestan- dable situation... Machine people promised no-activity at this time... 14.04.1992 ==================== H1KFOM === Last HERA-news =========== The copy of the information from pinboard at H1 Control Room: "Last update April 14, 13:00 stored beam at 26 GeV lost after very short time PETRA switched to proton operation no prospects for beam in HERA before near 18.00 " 15.04.1992 ==================== H1KFOM === Last HERA-news =========== The copy of the information from pinboard at H1 Control Room: "Last update April 15, 08:30 2 stored e-bunches at 26.5 GeV try to fill protons today...!? (not a very clear statement) " 15.04.1992 ==================== H1KFOM === Night 14-15.04.92 e-beam = HERA e-beam activity at last night (14-15.05) was began near 23:00 14.04.1992 and finished near 09:20 15.04.92. The first ramping was near 23:45. Beam was lost at 01:37. The second ramping was at 01.42. Beam was lost at 04:18. The third (and the last) ramping was 04:30 and this beam was stopped near 09:20. The last e-beam(after third ramping) was most succesful. It was sto- red two bunches (on the start of this period intensity per bunches was 12*10**10 at the first bunch and 10*10**10 at the second. Bunch numbers at Egor`s counters were: 180 and 183. This beam started with stable condition (after ramping) at 5:06 and was existed up to 09:20 (more then 4 hours). At this time it was possible to look the next rates on our monitoring counters: VetoWall - all this period near 90KHz. WaterVeto - 15 kHz at 5:20 and 5 kHz at 9:00. Sasha Usik was all this very interesting period at H1 Control Room and may be will write his impressions on this first very long and very intensive e-beam. 15.04.1992 ==================== H1KMAL ============= ================ It have been established from eye-witnesses (E.Gianfelice - a member of the nihgt shift) before the end of the beamrunning intensities were 3.6*10**10 at the first bunch and 2.5*10**10 at the second. It was about 9:10 - 9:15. 15.04.1992 ==================== H1KFOM === Run 17088 ================ It was written first Run with real events and new detectors. Its number is 17088. Start of Run -at 9:00 15.04.1992. Abort of Run (due to crash of FIC`s program) - at 9:13 15.04.1992. Number of events - 69689. Trigger - SumET&SumPD. Thresholds: SumPD - 199/15; SumET - 199/15; WaterVeto - 6. Mode 6 (without LREF and LRPF-banks). It is possible to find the next banks at data from this Run: LREE,LRPE,LRTE,TSTC,LRTN,LRTF,VETE as event`s banks; LREC,LRPC,LRTL - as non-event banks. LREC and LRPC must exist at Start Run Record. No end-run-record (LRTB) - due to crash of FIC's program. Data at LREC and LRPC from start-run-record are the same which was described at first caliubration attempt. But at another LREC and LRPC data must be changed due to permanent calibration. But... not right options of calibration were installed and this data are wrong. 15.04.1992 ==================== H1KFOM === Run 17088 on IBM-cartridge At 12:56 today Run17088 was dumped on cartridges: F11JOL.H01.TESTDATA.G0650V00 (first 43810 events) F11JOL.H01.TESTDATA.G0651V00 (last 25879 events). Average event length - 927 bytes. It was written near 65 Mbyte per this Run. 1 15.04.1992 ==================== H1KFOM === New bank LRTS at H1Lumi == SENDMAIL message Date: WED, 15 APR 92 17:03:45 MESZ From: Alexander Fomenko Subject: New bank at H1Lumi data stream To: Jan-Erik Olsson A.M. Fomenko, DESY -F22- Notkestrasse 85, D 2000 Hamburg 52 Tel. (040) 8998-2568 or -2074 (North Hall of HERA,CCR of H1) (permanent address: Lebedev Phys.Inst., Moscow, Russia) NODE: DHHDESY3 USERID: H1KFOM Zdravstvuite, Dear Jan, I inform You that at nearest Runs with H1Lumi data is is waited the appearence of new bank with name LRTS. Its format is B32. I know that default format is B32 and hope it will be no problem with this new bank. At nearest future it will be made the full discription of LRTS at "lbanks"-command area. Sincerely, Alexander Fomenko Contents of the LRTS-bank is the same as LRTB (only another format B32 not B16 as LRTB). This bank is non-event bank and must appear at H1Lumi data stream once per DT1 (see DPM mapping proposal). At nearest future it is planned to test this new bank with H1CDAQ. Old name not kept on simple reason - better exclude old bank and include new then change the old ("bad tone" as said S.Levonian). 15.04.1992 ==================== H1KFOM === Last HERA-news =========== The copy of the information from pinboard at H1 Control Room: "Last update April 15, 16:30 HERA setting up for protons * beam tonight very unlikely * certainly no more electrons before Easter " 16.04.1992 ==================== H1KFOM === Last HERA-news =========== The copy of the information from pinboard at H1 Control Room: "Last update April 16, 09:00 trying to set up PETRA for protons very small probability for any kind of particles in HERA(until Easter) machines stop at 21:00" 16.04.1992 ==================== H1KFOM === New High Voltage Set ===== Yesterday evening with Egor`s methodics of calibration with light pulses response it was installed new high voltage set on both detectors. This HV sets are kept at files (folder "SuperCard" H1Lumi2) "FileHVPDdefault.15.04.92.b" - for PD and WaterVeto "FileHVETdefault.15.04.92.c" - for ET. The next values of HV were installed: PD - detector pd20= 1825 V 2080 V 2015 V 2080 V 1870 V pd15= 2095 V 2050 V 1860 V 1760 V 1920 V pd10= 1850 V 1905 V 1890 V 1890 V 1735 V pd05= 2120 V 1880 V 1790 V 1615 V 1835 V pd00= 1900 V 1820 V 1875 V 1800 V 1970 V ET - detector et42= 1980 V 2100 V 1920 V 1855 V 2120 V 2110 V 1910 V et35= 1980 V 2250 V 2050 V 1950 V 2065 V 2030 V 1895 V et28= 2030 V 2200 V 2225 V 2055 V 1715 V 1815 V 1850 V et21= 2035 V 2000 V 1790 V 1985 V 2025 V 1965 V 1800 V et14= 1940 V 1960 V 1800 V 1835 V 1680 V 1650 V 1720 V et07= 2010 V 1790 V 1910 V 1790 V 1725 V 1680 V 1760 V et00= 2000 V 2050 V 1715 V 1835 V 1670 V 1760 V 1630 V WaterVeto 700 V on both PHEU. For ET it was 4 iteration procedure (0,a,b,c) for PD - 3 (0,a,b). All this procedure get near 3 hours of preliminary fine tuning. The difference at responses from light pulses on cells of both detectors is now not more then 10% (single exeption is e23 - near 40%) Something happened with channel e23 - the changing of HV on this chan- nel without adequate changing of response at e23. It is needed to understand - what is the reason of this behaivour. 16.04.1992 ==================== H1KFOM === Last HERA-news =========== The copy of the information from pinboard at H1 Control Room: "AOB. most likely no beam during the day Thuesday 21.04 (after Easter)" 1 17.04.1992 ==================== H1KFOM === Last HERA-news =========== The copy of the information from pinboard at H1 Control Room: "Last update April 16, 18:00 news from beam meeting: * some problems with ramping protons in PETRA * most likely no protons in HERA most of next week * the machine people are prepared to deliver stable 26 GeV electrons over nights next week (from near 23:00 up to near 07:00) This will be happen on rather short (1-2 h) notice ! " " A.O.B. The HERA injection interlock is operational. Use it when working with "sensitive" chambers. Don`t forget to release it after use." 21.04.1992 ==================== H1KFOM === Last HERA-news =========== The copy of the information from pinboard at H1 Control Room: "Thuesday 21 April 1992 18:00 - 18:15 Power Cut ! General Emergency System Test 23:00 Very Low Probability of e-beam" 22.04.1992 ==================== H1KFOM === New High Voltage Set ===== Yesterday evening with Egor`s methodics of calibration with light pulses response it was installed new high voltage set on both detectors. This HV sets are kept at files (folder "SuperCard" H1Lumi2) "FileHVPDdefault.21.04.92" - for PD and WaterVeto "FileHVETdefault.21.04.92" - for ET. The next values of HV was installed: PD - detector pd20= 1825 V 2080 V 2015 V 2080 V 1870 V pd15= 2095 V 2050 V 1860 V 1760 V 1920 V pd10= 1780 V* 1905 V 1890 V 1890 V 1650 V* pd05= 2120 V 1880 V 1790 V 1615 V 1835 V pd00= 1920 V* 1820 V 1890 V* 1800 V 1970 V ET - detector et42= 2015 V* 2100 V 1920 V 1855 V 2120 V 2110 V 1910 V et35= 2020 V* 2250 V 2050 V 1925 V* 2065 V 2030 V 1895 V et28= 2030 V 2200 V 2225 V 2055 V 1715 V 1815 V 1910 V* et21= 2050 V* 2000 V 1710 V* 1985 V 2025 V 1965 V 1800 V et14= 1940 V 1910 V* 1800 V 1835 V 1680 V 1650 V 1720 V et07= 2010 V 1790 V 1910 V 1790 V 1610 V* 1680 V 1760 V et00= 2000 V 2070 V* 1715 V 1825 V* 1670 V 1780 V* 1650 V* WaterVeto 700 V on both PHEU. Only for 4 cells HV was changed at PD and for 12 at ET (signed with *). Reason of this new changing - changing at H1LumiTrigger HW. It seems that Evgenio understood the problem with e23 (see ealier message on HV from 16.04.92). He probably will write about this late. 22.04.1992 ==================== H1KMAL === Trubles with e23 == ===== Yesterday during the total voltage switch off the resistance of all dividers at E-hodoscope was checked : e00-1.90 e01-1.93 e02-1.93 e03-1.89 e04-1.91 e05-1.91 e06-1.90 MoM e07-1.88 e08-1.90 e09-1.93 e10-1.91 e11-1.91 e12-1.91 e13-1.89 e14-1.91 e15-1.90 e16-???? e17-1.90 e18-1.90 e19-1.90 e20-1.92 e21-1.91 e22-1.94 e23-xxxx e24-1.91 e25-1.88 e26-1.91 e27-1.91 e28-1.92 e29-1.88 e30-1.93 e31-1.92 e32-1.88 e33-1.92 e34-1.89 e35-1.87 e37-1.87 e37-1.92 e38-1.90 e39-1.90 e40-1.92 e41-1.91 e42-1.94 e43-1.94 e44-1.90 e45-1.89 e46-1.93 e47-1.91 e48-1.91 And three spare channels, which were not connected: e50 - **** e51 - **** e52 - 1.95 (!!!) Remark: It seems that e52 is connected to e23- module. The change of HV on e52 shows that e23-response follows to this changes. This situations should be checked during the first possibility to come into tunnel. Note >> It was found during access that Cables e24 was damaged and substituted for e52, but record about that is absent. 22.04.1992 ==================== H1KFOM === New Run Coordinators ===== It is proclaimed on H1 Control Room pinboard that from April,21 (thue- sday) up to May,1 the next persons are Run Coordinators: Mike Forbush and David Newton. Last update of HERA-news was at 22, April, 9:00: It was repeated information from 17 April 1992: 1 "...... news from beam meeting: * some problems with ramping protons in PETRA * most likely no protons in HERA most of next week * the machine people are prepared to deliver stable 26 GeV electrons over nights next week (from near 23:00 up to near 07:00) This will be happen on rather short (1-2 h) notice ! " ....." 23.04.1992 ==================== H01USA === News from night shift ==== No any activity from HERA was observed. New DA "IntensitySc4" is installed on left MAC for monitoring of 4CAMAC scalers from VETO Wall. VME addresses of 4 scalers are defined in Super Card (card Init of Lumi menu ). 23.04.1992 ==================== H1KFOM === Last HERA-news =========== The copy of the information from pinboard at H1 Control Room: "Thuesday April, 23, 10:00 Attempt to inject protons into HERA" 24.04.1992 ==================== H1KFOM === First Runs with 5 Branches Today on request of Bill Haynes our H1Lumi-subsystem was tested at Mode 0 together with H1CDAQ and H1CTRIG with 4 and 5 another brunches of H1 CDAQ. Tests was began at 17:54 and finished at 18:44 24.04.1992. It was tested two OnLineProgram (for both FICs): H1LumiOnLineFIFOC - release of 23.04.1992, 15:34 - for FIC#1 H1LumiOnLineRecNew19 - release of 21.04.1992, 20:58 - for FIC#2 L2Keep-interrupts were activated from H1CTRIG due to Global OR of all trigger bits which are proposed for nearest work - our "etag"-bit was not active - our subsytem was a satellite (not active). Average rate of events (from cosmics - beams were absent) was near 10-20 Hz. It was written on temporary IBM-cartridges 5 Runs with H1Lumi data flow (only for testing of on-line program compatibility with another brunches). A little about this Runs: Run 17610. Central Trigger + Central Tracker + MWPC + Luminosity brunches. Start Run - 17:54:17. Abort Run - 18:20:13. near 26 min. of data taking. Mode at H1Lumi - 6. Number of events - 6582. Average length of events - 7.1 Kbytes. Minimal length of events - 6.6 Kbytes. Maximal length of events - 44.2 Kbytes. H1Lumi FIC#2 was operated and put into H1Lumi data flow 54 LREC&LRPC banks and 60 LRTL&LRTS-banks at KEEP-folders. It was fixed one error at our subsystem - no Front-End-Ready from L2Keep. After Egor`s clearing - Run was prolongated. Run 17612. CentralTrigger + CentralTracker + MWPC + Muons +Luminosity brunches. Start Run - 18:21:12. Abort Run - 18:21:40. near 28 sec. of data taking. Mode at H1Lumi - 6. Number of events - 163. Average length of events - 28.1 Kbytes. Minimal length of events - 28.1 Kbytes. Maximal length of events - 48.3 Kbytes. H1Lumi FIC#2 was not operated Run 17613. CentralTrigger + CentralTracker + MWPC + Muons +Luminosity brunches. Start Run - 18:21:46. Stop Run - 18:26:40. near 5 min. of data taking. Mode at H1Lumi - 6 at begin of Run and - 1 after first near 300 ev. Number of events - 1758. Average length of events - 25.7 Kbytes. Minimal length of events - 25.4 Kbytes. Maximal length of events - 48.3 Kbytes. H1Lumi FIC#2 was not operated Run 17614. CentralTrigger + CentralTracker + MWPC + Muons brunches. Start Run - 18:29:22. Stop Run - 18:29:27. near 5 sec. of data taking. Number of events - 30. Average length of events - 23.7 Kbytes. Minimal length of events - 1.8 Kbytes. Maximal length of events - 48.0 Kbytes. 1 Run 17615. CentralTrigger + CentralTracker + MWPC + Muons +Luminosity brunches. Start Run - 18:29:46. Stop Run - 18:29:50. near 4 sec. of data taking. Mode at H1Lumi - 1. Number of events - 20. Average length of events - 26.7 Kbytes. Minimal length of events - 25.4 Kbytes. Maximal length of events - 48.3 Kbytes. H1Lumi FIC#2 was not operated Run 17616. CentralTrigger + CentralTracker + MWPC + Muons +Luminosity brunches. Start Run - 18:30:04. Stop Run - 18:44:30. near 14 min. of data taking. Mode at H1Lumi - 1. Number of events - 5182. Average length of events - 24.5 Kbytes. Minimal length of events - 21.6 Kbytes. Maximal length of events - 48.4 Kbytes. H1Lumi FIC#2 was not operated Remarks from Bill: 1) long period of preparing of Start-RunRecord at H1Lumi; 2) StopRun-interruption is not operated (AbortRun - OK.) Almost 30 min of operation of H1Lumi-subsystem inside H1CDAQ together with 3 or 4 another brunches was fixed with little remarks and problems - no so large as waited. 27.04.1992 ==================== H1KFOM === Last HERA-news =========== The copy of the information from pinboard at H1 Control Room: "Present Situation (08:30 Monday 27.04.1992) work on the proton beam continues" 01.05.1992 ==================== H1KFOM === Night30.04-01.05.92p-beam Today it was posibility to look for our "BeamArchiv"-memory with attention and to try making of some conclusion from this looking: 1) At our last contents of archive memory there are full history of the next time period : from 18:20 30.04.1992 up to 10:35 01.05.1992 (almost 17 hours of beam history); 2) there is posibility to look for the behaivour of three rates of different H1-subdetectors during this period: a) rates of GlobalOR of H1VetoWall-subdetector; b) rates of WaterVeto of H1Lumi-subdetector; c) rates of PhotonDetector of H1Lumi-subdetector. 3) First conclusion from looking for of full history of high mentioned period - at p-ring of HERA there existed p-beam during 732 min. from 1020 min. of this time period (almost 3/4 of effective work); 4) The longest storing p-beam existed from 18:20 30.04.1992 up to 00:27 01.05.92 (a little more then 6 hours); 5) It was looked for near 55 injections of protons from PETRA into p-ring of HERA with different time period between its and with differents aims (start of p-beam storing or incrementing of intensity of existing p-beam). 6) In principle it is possible to divide all 17 hours period on 11 different time period - 9 succesful(1-9) and 2 unsuccesful(B1,B2): 1. 18:20 - 00:27 - 367min. with 5(+1) injections - successful; 2. 00:43 - 01:36 - 50min. with 9 injections - successful; B1. 01:38 - 01:53 - 6min. with 3 injections - unsuccesful; 3. 01:58 - 02:31 - 31min. with 6 injections - successful; 4. 02:46 - 03:42 - 56min. with 6(+1) injections - successful; 5. 03:49 - 04:02 - 13min. with 3 injections - successful; 6. 04:12 - 05:03 - 51min. with 5(+1) injections - successful; B2. 05:15 - 06:36 - 63min. with 10(+2) injections - unsuccesful; 7. 06:41 - 07:03 - 21min. with 1(+1) injections - succesful; 8. 07:41 - 09:41 - 120min. with 1 injection - succesful; 9. 10:12 - 10:35 - 23min. with 1 injection - succesful. 7) At B1 and B2 periods it were achived "record" rates of different detectors during injection time: GlobalOR of VetoWall - near 41kHz at 05:20 unsuccesful injection; - near 16kHz at 05:15 unsuccesful injection. WaterVeto of H1Lumi - near 300 Hz at 01:38 unsuccesful injection. PhotonDetector of H1Lumi - near 20 Hz at 01:38 unsucceful injection. Note: Ordinary rates (during injection - GlobalOr-300-700Hz, WaterVeto - near 10-20 Hz, PhotonDetector - single events) 1 8) Many times it was looked for the situation "beam lost" after next attempt of injection for incrementing of existed p-beam intensity (injections 0:23(period 1),03:42(period 4),05:03(period 6), 06:03 and 06:36(period B2),07:03(period 7). 9) It was looked for the disapperence of p-beam without incrementing of rates at all detectors (10:12 (period 9),04:02 (period 5),02:31 (period 3) etc. All this period (I am not shure) energy of p-beam was equal injection energy - 40 GeV and existed only single bunch (173 number at our subsystem at 19:20) - at night I do not know how much. All previous days machine people worked with single bunch and with 40GeV protons. 03.05.1992 ==================== H1KFOM === Last HERA-news =========== The copy of the information from pinboard at H1 Control Room: "Message from HERA CTRL Room 3 May 1992 9:30 Unlikely that there will be stable beam until Sunday 3rd On Sunday 3rd may be there will be 2 hours of stable beam after 14:00" "H1 Run Coordinators 1-14 May 1992: Gunter Eckerlin (DESY) Friedrich Niebergall (HAM2 II Inst. Fuer Exp. Phys. Univ. Hamburg)" 03.05.1992 ==================== H1KFOM === H1 Solenoid On =========== H1 Solenoid was ON today near 12:20. At this period there existed p-beam with 40 GeV. Very interesting picture was looked on the our DA for monitoring of rates of different subsystem of H1 VetoWall. On asking of Run Coordinator we put this picture into H1 LogBook (for history). It was started ramping of H1 Solenoid on 1/2 of current = 2750 A. This procedure must get near 30 min. During start of ramping we looked the picture (high mentioned). Now after 30 min. - p-beam exists - current is 0.07 ma. All is OK. Now (at 14:40) 40 GeV p-beam current is 30 mkA. P-beam is living. At HERA-TV-screen it is possible to look for message: "40 GeV p+ for H1/ZEUS". H1TOF-people got first Runs for beam-study. 05.05.1992 ==================== H1KFOM === Last HERA-news =========== The copy of the information from pinboard at H1 Control Room: "Message from HERA CTRL Room 5 May 1992 9:30 - injecting p into HERA soon - Chromaticity studies today - no ramping " At 15:55 at TV-screen from HERA CTRL room is appeared the message: " No protons up to 16:45" 05.05.1992 ==================== H1KMAL == How to get access at tunnel During the temporary stop of HERA-operation(4 hours, May 4) I have tryed to have access to our detectors at tunnel. It is sufficiently complecated operation. I will try to list of this procedure: 1) After that as HERA peoples declare about any future access at tunnel (as a rule it is 2-3 days before) at some definite time, it is necessary to ask H1RUN coordinator for this time to phone to HERA access response man (now it is Bialowons) and to explane all (reason, needed time, place - HERA Nord to the rihgt from IP, names of peoples). P.S. In the case of urgent works it is necessary to give your request to H1RUN coordinator in order to ask the HERA peoples about that. 2) If You got OK, You can go to entrance. Before entrance You should phone by white telephone and present itself. If there is agreement the transparent box for keys will be opened. 3) You must give keys one/person and close box. Wait then the rad buld up the door will go out and open the door. Remember!! NO ENTRANCE UNDER THE RAD LAMP !! If You touch door before the bulb swich off HERA will be stopped for a few hours. 4) Droping inside, close the door. 5) Before leaving of tunnel You should phone again by white phone nearly exit. If all is OK - there is permis- sion and lamp is swiched off, please, can open door. 6) Close the entrance door and ptone again. Only after that the pransparent box will be opened. Put keys at its places. Good luck and don"t troble HERA ! 1 14.05.1992 ==================== H1KFOM === Lumi Acceptance at On-Line New subroutine Tilt.f was inserted today into On-Line System for FIC#2 for calculation of the correction factor to the lumi acceptance due to the e-beam tilt at the H1 Interaction Point. It became possible due to today appearence of new LPI-report 01-92 S.V.Levonian "Data for the Online Luminosity Evaluation". This subroutine carried out interpolation (with FINT-subroutine from CERN KERNLIB - library) which based on 49 samples presented by S.Levonian at his report. On the first view (with the simple test) all is working. It is possible to switch off this correction (new option for H1 Lumi On-line system). 15.05.1992 ==================== F.Willeke = HERA-p Design Energy ===== This is the copy of information from pinboard HERANEWS: "..... F. Willeke May 15 1992 Tel 3187 ================================ HERA-P REACHED THE DESIGN ENERGY ================================ On Friday morning May 15 at 7:28h a proton beam of 85muA was accelerated up to 820GeV in HERA. The HERA proton ring thus reached its design energy. ....." 17.05.1992 ===================== H1KFOM === Experience of Coexistence = From 15 May 1992 H1Lumi subsystem was included into H1 CDAQ almost permanently. During last two days and nights it was written the set of Runs with our branch. Data which are written at LREE,LRPE,LRTE - banks are not useful for any using. This is random appearence of anything at random FADC-window (not right shifts for FADCs). This Runs are useful only as experience of coexistance of our H1Lumi branch with other H1 brunches at H1 CDAQ environment. This is the list of written Runs during last two days and nights with H1Lumi-branch: Run Evts. Br. Start of Run End of Run Mins. Which End 19168 9355 7 15.05.92 02:57 15.05.92 03:07 10min. Abort 19169 912 7 15.05.92 03:10 15.05.92 03:12 2min. Abort 19448 228 8 17.05.92 00:18 17.05.92 00:20 2min. Stop 19449 61 8 17.05.92 00:20 17.05.92 00:22 2min. Stop 19450 16 8 17.05.92 00:23 17.05.92 00:32 9min. Stop 19453 11 8 17.05.92 01:02 17.05.92 01:35 33min. Abort 19455 1 8 17.05.92 01:49 17.05.92 01:49 0min. Abort 19457 29 8 17.05.92 01:52 17.05.92 03:22 90min. Stop 19458 2162 8 17.05.92 03:25 17.05.92 03:28 3min. Abort 19462 1 8 17.05.92 03:32 17.05.92 03:32 0min. Abort 19466 1 8 17.05.92 03:37 17.05.92 03:37 0min. Abort 19469 4062 8 17.05.92 03:43 17.05.92 03:49 6min. Abort 19470 6688 8 17.05.92 05:16 17.05.92 05:26 10min. Abort 19477 2715 8 17.05.92 07:02 17.05.92 07:06 4min. Abort 19478 23 8 17.05.92 07:08 17.05.92 08:25 77min. Stop 19479 3 8 17.05.92 08:29 17.05.92 08:30 1min. Stop 19480 4701 8 17.05.92 08:35 17.05.92 09:00 25min. ? From Run Summary analysis it is possible to note: 1) Once (Run 19168) it was looked "BOS Structure Error" from our subsystem ( name LREE was retranslated to Bill`s memory with not right name -'00000000' replaced '4C524545') - it means that it is needed to think about more protective against this situation release of H1LumiOnLineFIFO-program for FIC#1; 2) Once (Run19470) it was looked ROERROR which was fixed with H1Lumi On-Line Program and Run19470 has one TSTC less from our subsystem - this is familiar situation and it is appeared may be due to bus-error on our may be overload VVME-bus; 3) All StopRuns had adequate responses from our subsystem - EndRunRe- cord with LRTS-bank. 19.05.1992 ===================== H1KFOM === e-beam 18-19 May 1992 ===== HERA e-beam was active from near 14:00 18.05.92 up to 05:34 19.05.92. Main part of this time period 12 GeV e-beam was existed and once (from 3:40 up to 05:34 - near 2 hours 26.7 GeV e-beam existed). All our team (I.Sheviakov, E.Malinovski. A.Usik and me) made during this time different needed works and something was made and understood 1) First of all I.Sheviakov together with H1 Central Trigger people carried out the timing of our trigger element "etag". Timing was tuned during Run19519 and 19520. 1 Now we have (as we think) final values of so-called Shift Constants for our ET- and PD-FADC for finding of FADC-window which "connected with t0 - time period. For H1LumiOnLine program this constants are: 192 - for ET FADCs and 138 - for PD FADCs. During Run19520 with trigger - OR of three trigger elements (one of its was "etag") it was possible to look for our "ET&PD"-events at H1CDAQ Event Display environment. Run 19520 was started at 16:42:10 and stopped at 17:03:24. It was written on permanent cartridge - HERA04.H1RAWD.C9200110 Energy of e-beam was 12.0 GeV. 2) It was written Run 19528 with data from only Luminosity branch. Start Run - 17:19. Stop Run - 17:55. Trigger - SumET & SumPD. Thresholds: SumET 199/21;SumPD 199/21 (but its were changed during Run - 17:26 - low thresholds were installed 5 on both Sums, 17:40 - low thresholds were installed 21 on both Sums. (first near 6000 events-we forgot to switch off multitrigger mode it is possible that at this events trigger was not ET&PD). Number of events - 51007. Energy of e-beam was 12.0 GeV. Rate of WaterVeto - 340-370 Hz Rate of Trigger - 30 -37 Hz (with "main thresholds" - 21). - 70 -90 Hz (with low threshoods - 5) Run was written on permanent cartridge HERA04.H1RAWD.C9200110. 3) On both detectors it was tuned and installed new values of HV. Main kriteria - right boundary of spectra and absence of overflow situation at FADC channels connected with cells. The HV sets are kept at the next files: FileHVETDefault.18.05.92 FileHVPDDefault.18.05.92 The next values of HV was installed: PD - detector pd20= 1825 V 2050 V 1950 V 2050 V 1870 V pd15= 2095 V 2050 V 1700 V 1700 V 1920 V pd10= 1780 V 1880 V 1760 V 1850 V 1700 V pd05= 2120 V 1840 V 1770 V 1615 V 1835 V pd00= 1950 V 1820 V 1890 V 1860 V 2020 V ET - detector et42= 2015 V 2150 V 1920 V 1860 V 2120 V 2110 V 1910 V et35= 2020 V 2250 V 2080 V 1960 V 2065 V 2030 V 1895 V et28= 1950 V 2150 V 2225 V 2055 V 1715 V 1815 V 1910 V et21= 2050 V 1790 V 1910 V 1900 V 2000 V 1980 V 1800 V et14= 1900 V 1910 V 1800 V 1880 V 1730 V 1720 V 1800 V et07= 2010 V 1850 V 1910 V 1850 V 1610 V 1770 V 1760 V et00= 2040 V 2070 V 1770 V 1840 V 1670 V 1780 V 1720 V WaterVeto 700 V on vetoing PHEU and 560 V on spectr.PHEU. 4) It was carried out the first attempt of calibration of our detectors on 12 GeV e-beam. Through calibration procedure it was passed near 20000 events during 3-4 hours. 18 cells at PD and 26 cells at ET had "good" weights - it means that it is possible to beleive to calibration coefficient values. Trigger was chosen - Sum(ET) & Sum(PD) & antiWaterVeto Algorithm for calibration - Usik's. The next option were installed: BeamEnergy = 12.0 GeV CutHigh = 16.0 GeV CutLow = 8.0 GeV DeltaET = 6.5 cm DelatPD = 4.0 cm ccw = 0.02 ETPDFix = 0 Start values of coefficients - 1.0 for ET, 0.3 for PD and WaterVeto. Full set of calibration coefficients is the next(with weight at low) PD - detector pd20=0.265 0.260 0.353 0.391 0.316 5.4 26.7 34.6 7.8 1.8 pd15=0.311 0.332 0.235 0.281 0.273 15.7 58.6 140.1 149.6 21.0 pd10=0.355 0.265 0.219 0.244 0.341 17.4 93.3 451.2 178.6 5.6 pd05=0.308 0.171 0.189 0.264 0.333 10.5 88.0 181.6 93.3 8.7 pd00=0.302 0.218 0.209 0.317 0.311 3.5 18.1 49.0 10.5 2.6 ET - detector et42=1.041 1.024 1.038 1.060 1.187 1.032 1.034 1.6 6.2 1.8 1.7 3.3 1.4 1.6 et35=1.001 0.794 0.823 1.385 1.033 1.316 1.228 6.4 19.6 19.8 17.0 31.3 22.6 7.7 et28=0.816 0.521 1.189 1.234 1.529 0.969 1.345 22.9 73.4 78.5 118.6 112.1 197.5 155.0 et21=1.222 0.937 1.315 0.909 0.767 0.912 1.350 487.9 717.7 1119.5 1166.5 1108.4 852.2 496.2 et14=0.966 0.965 1.234 1.276 1.211 0.858 0.776 11.7 15.4 12.9 23.4 13.7 20.0 16.8 et07=0.722 0.998 1.062 1.144 1.000 0.875 1.085 2.0 2.4 2.1 4.2 1.7 5.2 4.3 et00=0.972 0.986 0.993 0.988 0.924 0.909 0.984 1.3 1.3 2.1 1.7 3.8 2.5 1.7 1 Values must be multiplied on own coeeficients - 3.89 for PD and 3.65 for ET. Final histos of energy distribution are looked for reasonable: a) ETrec + PDrec - max bin statistic = 1394 - mean value 11.79 GeV - dE = 1.01 GeV - SW made low threshold at 9 GeV - maximal energy - near 16 GeV. b) ETdep + PDdep - max bin statistic = 1517 - mean value 11.08 GeV - dE = 1.01 GeV - minimal value - near 7.5 GeV - maximal value - near 15 GeV c) ETrec - max bin statistic = 1722 - SW made low threshold - 6 GeV (peak at one bin) - maximal value - near 11 GeV - peak region bin - near 8 GeV - "working" line between 6 and 8 GeV d) ETdep - max bin statistic = 1491 - minimal value - near 3 GeV - maximal value - near 11 GeV - peak region bin - near 8 GeV - "working" line between 3 and 8 GeV e) PDrec - max bin statistic = 3034 - SW made low threshold - 3 GeV - maximal value - near 7 GeV - peak region bin - near 3 GeV - "working" line between 3 and 7 GeV f) PDdep - max bin statistic = 2620 - minimal value - near 3 GeV(SW made low threshold) - maximal value - near 7 GeV - peak region bin - near 3 GeV - "working" line between 3 and 7 GeV 5) Calibration of detectors on 26.7 GeV e-beam was short (due to time limit-only 5531 events were passed through calibration procedure with trigger ET&PD&antiWaterVeto). There are only 6 cells at PD and 12 cells at ET with "good" weights. These are the values of coefficients with "good" weights: PD - detector pd15=????? 0.278 0.324 0.295 ????? 3.2 14.5 91.7 174.5 9.3 pd10=????? 0.265 0.255 0.274 ????? 7.4 28.1 51.8 35.4 1.5 ET - detector et28=????? 0.877 1.099 1.200 ????? 1.069 1.211 5.3 73.4 78.5 118.6 6.5 197.5 155.0 et21=1.297 1.019 1.459 1.042 0.815 0.981 1.361 752.4 790.8 496.3 482.6 251.1 175.3 80.0 Final histos of energy distribution are looked for reasonable: a) ETrec + PDrec - max bin statistic = 91 - mean value 26.78 GeV - dE = 1.32 GeV - minimal value - near 22.5 GeV - maximal energy - near 31 GeV. c) ETrec - max bin statistic = 55 - minimal value - near 10 GeV - maximal value - near 23 GeV - peak region bin - near 17 GeV - "working" line between 10 and 17 GeV e) PDrec - max bin statistic = 61 - minimal value - near 5 GeV - maximal value - near 14.5 GeV - peak region bin - near 10 GeV - "working" line between 10 GeV abds 14.5 GeV - little statistics at 25-32.5 Gev region. 6) The calibration of Water Veto was attempted due to fixing of ET and PD coefficients and switching on into trigger PD&ET. Start value of Water Veto Coeff. was 0.300. After 10 min. of calibration it became 0.309 with weigth 1.2. Due to time limit this attempt was interrupted. 7) EnergyPD-EnergyET plot for 26.7 GeV e- is looked also reasonable. Main statisics (near 80 %) are coupled at 26.7GeV+-3*1.3 region. The correlation exists - plot looked as wide line from 26.6 GeV at Eet axis up to 26.7 GeV on Epd axis. This "line" has main sta- tistics between Eet (15-23 GeV) and Epd (5-12 GeV). Statistics boundaries Eet(6-24.5 GeV) and Epd(3-17.5Gev). Little population of statistics exists under low line without creating of any forms - randomly distributed may be due to bad reconstruction of electron energy when electron hit is near ET boundaries. The second little population of statistics exists due to 25-32 Gev existance of Epd (higher then high line). 1 8) The coordinates plots (both ET and PD) are looked also reasonable. As it was looked for earlier - there are clear boundaries empty spaces on both plots. This pictures are very impressionable and intersting. We look for the predicted by S.Levonian at LPI Internal report 01-92 behaivour of ET coordinate plot when e-beam produces non-central hitted st PD photons. When photons hits into centrum of PD - the ET coordinate plot is simmetrical (as also was predicted at this report). 9) The coefficient of Luminosity Trigger Efficiency was changed due to different reason - HERA people manipulation and due to changing of Lumi-trigger. For ET&PD&antiWaterVeto trigger the values of this coefficient was near 0.8. For ET&PD - near 0.4 for fixed energy resolution (1.3 GeV). 10) LumiReconstruction program worked very good: all cuts - energy and claster worked. It was existed enough quantity of events passed the reconstruction succesfully - 16499 events from 19549 passed ET-reconstruction and 15372 from 19549 - PD reconst- ruction. 13188 events from 19549 had both reconstructions. 11) Attempt to write Run with 26.7GeV e-beam with Luminosity branch was at 5:00 (up to 0.5 hours before e-beam stop) - but H1CDAQ was busy with Mr.Schroder experiments with collimators. Common impression from past 16 hours of work is enough good. As me seems we made very difficult step forward - first calibration on 26.7 GeV e-beam. It was very waitable event for all our H1Lumi community. 21.05.1992 ===================== H1KFOM === Off-line Calibration ====== Today it was carried out the calibration of our detectors (ET,PD and WaterVeto) with HV-set which was installed before last (see previous message) changing. It was happened due to strange order of our work with e-beam. First of all we wrote Run 19528 (with old release of HV-set) and after that we carried out the tuning of HV. After last changing of HV-set we have not any Run with e-beam for today. But in principle this work is useful for first estimation of different parameters of H1Lumi-subdetector. All work with detector calibration was made with 5 step: 1) creating of raw-DST cartridge with events - candidates to events with SW-trigger SumET & SumPD & antiWaterVeto. This events are kept on cartridge H1KFOM.LUMI92.AWC19528 (number of events near 3200); Job is kept at H1KFOM.RAWDST(#WCRANTI). 2) first iteration of calibration ET- and PD-channels with this events (start values of CC are the same which were determined at on-line for 12 GeV (see previous message) but calibration coefficient for e22 was changed due to very different HV on this channel for on-line CC set - in two times less); Job is kept at H1KFOM.LUMI92H(#C210592). 3) second iteration of calibration ET- and PD-channels with this events (start values of CC are the result of the 1st iteration); Job is kept at H1KFOM.LUMI92H(#D210592). 4) calibration of WaterVeto-spectrometrical channel on all events of Run19528 with fixing of ET- and PD-coefficients; Job is kept at H1KFOM.LUMI92H(#E210592). 5) processing of all events from Run 19528 with all fixed calibration coefficients (near 42000 events). Job is kept at H1KFOM.LUMI92H(#F210592). Results are the next: 1) Energy distribution spectra (number of entries - 42000 events) a) ETrec + PDrec + WaterVetodep - peak with mean value 11.77 GeV and sigma=0.76 GeV (no any assymetry) max. bin statistics is near 3800 events - peak begins from 7.50 GeV with statistics near 100 events - peak finishes at 16 Gev with statistics near 50 events; - little population at low energy region (from 3 up to 7.5 GeV); it is looking as peak with mean value near 5.5 Gev and statistics at max. bin statistics of this region near 200 events b) ETrec + PDrec - peak with mean value 10.88 GeV and sigma=1.54 GeV max. bin statistics is near 2100 events - peak begins from 6.00 GeV with statistics near 100 events - peak finishes at 15 Gev with statistics near 50 events; - little population at low energy region (from 1 up to 6.0 GeV); it is looking as peak with mean value near 5.0 Gev and statistics at max. bin statistics of this region near 125 events c) ETrec - max bin statistics is at 7.42 Gev (near 2800 events) - spectrum begins from 1.18 GeV with statistics near 100 events - spectrum finishes at 11 Gev with statistics near 50 events; 1 d) PDrec - max bin statistics is at 3.12 Gev (near 2500 events) - spectrum begins from 0.5 GeV with statistics near 50 events - spectrum finishes at 9.0Gev with statistics near 50 events; - there is a liitle population (near 600 events with 0.0 GeV) may be due to some manipulation during Run with thresholds and Multitrigger mode). e) WaterVeto dep - max bin statistics is at 1.5 GeV (near 400 events) (there is population of statistics at region 0.0 - 0.5 GeV with maximum at first nearest to 0.0 bin - near 750 events) at 0.5 GeV region we can look clear decrementing of statistics up to 300 events per bin). - spectrum begins from 0.0 GeV with statistics near 750 events - spectrum finishes at 5.0Gev with statistics near 10 events; 2) Two-dimensional coordinate spectra: a) Xpd versus Ypd - Xpd mean value -1.05 cm; Sigma = 1.36 cm Ypd mean value 1.36 cm; Sigma = 1.17 cm It is clear that boundaries between cells exists as empty regions on two dimensional plot. b) Xet versus Yet - Yet mean value -0.012 cm; Sigma = 0.64 cm Large difference at calibration coefficient values of central layer of ET is the reason of changing of population statistics at regions which are corespondent to this cells. For example - very low statistics from e23 - large CC and small signal and small addition to analog trigger sums. It is possible to hope that with last HV-set this problem dissappered. Full set of calibration coefficients is the next(with weight at low) ( o n l y f o r R u n 1 9 5 2 8) All calibration coefficients are at MeV/FADCcount units PD - detector pd20=0.903 0.788 1.142 1.390 1.224 1.6 9.9 15.7 2.7 0.8 pd15=0.706 1.272 0.791 1.122 0.989 23.2 750.6 652.2 52.4 3.6 pd10=1.330 1.248 0.591 1.072 1.376 36.6 432.2 206.2 24.6 1.0 pd05=1.154 0.657 0.712 1.084 1.301 4.4 12.9 8.9 2.5 0.8 pd00=1.168 0.834 0.739 1.225 1.194 0.8 1.0 3.3 0.7 0.9 ET - detector et42=3.532 3.559 3.705 3.796 4.215 3.677 3.661 1.1 0.9 1.3 0.8 0.8 0.9 0.9 et35=4.115 2.062 2.852 3.467 4.300 4.519 4.285 2.7 2.8 2.7 2.7 1.5 1.1 1.0 et28=1.860 1.384 3.635 3.760 4.905 3.069 4.450 11.0 18.0 13.0 14.7 9.6 8.5 5.8 et21=4.598 1.445 4.764 2.129 2.446 3.311 4.453 1142.0 1617.3 458.4 709.7 450.8 121.7 55.0 et14=3.744 2.822 4.564 5.742 4.823 3.849 3.768 16.0 15.4 6.3 12.5 6.9 3.9 5.3 et07=3.280 3.406 3.662 3.814 3.441 3.139 3.261 1.2 1.3 1.3 1.1 1.1 0.9 3.2 et00=3.367 3.414 3.451 3.411 2.844 2.653 3.315 1.0 1.0 1.3 1.1 1.5 1.5 1.2 Water Veto: 4.732 MeV/FADCcount, weight = 1793.1 Really it is calibrated only 11 cells at PD and 14 cells at ET (this channels have weight more then 10.0). But this cells was hitted mainly at this Run and in principle it is possible to make some conclusion from presented results. It is needed to write Run with the last HV-set. 25.05.1992 ===================== H1KFOM === e-beam 24-25.05.92 ====== HERA e-beam activity (as was promissed) began at Sunday 24.05.92 at near 12:20 and is continueing up to now (06:23 25.05.92). Almost 20 hours of good posibility for calibration of our detectors was used on 100%. We have now calibration coefficients for our detectors which were calculated at on-line (we had else one change of HV-set today). We used Movable Platform of ET for calibration as more as possible of cells of ET. We wrote some Runs before last changing of HV-set (with HV of 19.05.92) - Runs 20333,20334 (for Egor`s needs with H1CTRIG). Run 20335 - trigger SumPD & SumET & anti(waterVeto) - thresholds: SumPD - 21, SumET - 21, WaterVeto - 2. - near 10000 events (first 1100 events - SumETonly trigger) Run 20337 - trigger SumPD & SumET - thresholds: SumPD - 21, SumET - 21, WaterVeto - 2. - near 50000 events 1 Run 20348 - (for Egor`s needs with H1CTRIG). - thresholds: SumPD - 21, SumET - 21, WaterVeto - 2. - near 50000 events After this it was made the changing HV-set and wrote next Runs: Run 20408 - trigger SumPD & SumET & anti(waterVeto) - thresholds: SumPD - 15, SumET - 31, WaterVeto - 2. - near 11000 events (first 5500 events - SumETonly trigger) Run 20409 - trigger SumPD & SumET - thresholds: SumPD - 15, SumET - 31, WaterVeto - 2. - near 29000 events Run 20409 - trigger SumPD & SumET - thresholds: SumPD - 15, SumET - 31, WaterVeto - 2. - near 17200 events Run 20411 - trigger SumPD & SumET (as etag-trigger bit) - thresholds: SumPD - 15, SumET - 31, WaterVeto - 2. - near 16680 events - this Run was written with 9 brunches of H1 After inserting into On-Line Program of the new calibration coeff. it was written two Runs with right LREC and LRPC-banks: Run 20416 - trigger SumPD & SumET & anti(waterVeto) - thresholds: SumPD - 15, SumET - 31, WaterVeto - 2. - 18437 events (first 5500 events - SumETonly trigger) Run 20417 - trigger SumPD & SumET (as etag-trigger bit) - thresholds: SumPD - 15, SumET - 31, WaterVeto - 2. - near 54900 events - this Run was written with 2 brunches of H1 (H1CTRIG + + Luminosity). It was obtained our own "record" resolution for system with three detectors: ET,PD and WaterVeto - at the spectrum Eetrec+Epdrec+Water Vetodep we looked mean value 26.78 GeV and Sigma = 0.82 GeV. The waited value if this resolution is 0.71 GeV for 26.7 GeV e-beam. 25.05.1992 ===================== H1KFOM === H1Lumi at H1CDAQ (e-beam) = After finishing of our almost 20 hours work with e-beam our branch "Luminosity" was included into H1CDAQ-H1CTRIG environment with Trigger Bit "ETag" as SumET & SumPD & anti(WaterVeto) - on request of Brasse. Luminosity branch succesfully worked at this environment from 07:11 up to 11:40 25.05.1992 (4.5 hours). At three Runs our Trigger Bit "ETag" was active (Run 20429,20430 and 20431) and in principle we have enough good collection of our pure luminosity events at this Runs (near 6000 + 22000 + 10000). Our Trigger Bit has special place at Trigger2 word - it is diposed at bit number 0 of this word. May be it is interesting to look another H1 subdetectors during appearence of our Trigger Bit (what they can see at this time - nothing or something?)? Run 20429 was written on 2 permanent cartridges (12468 events). Run 20430 was written on 6 permanent cartridges (43538 events). Run 20431 was written on 3 permanent cartridges (21535 events). Rate of our Trigger Bit was near 9-10 Hz. It was switched on else one trigger bit (TRIGG1 = 00000040,TRIGG2= 00000001). Both this trigger bits gave common rates (with OR) near 20 Hz. All 9 branches was included into H1CDAQ during this Runs. At 08:25 25.05.95 our Trigger Bit was made inactive and up to 11:40 out branch was as sattelite branch - wrote all what was at our detectors due to different external trigger. 27.05.1992 ===================== H1KFOM === Calibration Coefficient Set Full set of calibration coefficients is the next(with weight at low) ( f o r R u n 2 0 4 0 8 a n d l a t e ) All calibration coefficients are at MeV/FADCcount units PD - detector pd20=1.019 0.965 1.431 1.521 1.225 1.0 1.4 2.5 1.0 0.7 pd15=0.961 1.128 1.116 1.132 1.093 3.9 28.4 39.7 48.6 3.5 pd10=1.112 0.996 1.132 1.159 1.404 15.0 94.5 410.8 304.2 8.0 pd05=1.144 0.673 0.755 0.965 1.252 2.1 8.3 24.4 30.6 3.0 pd00=1.167 0.836 0.793 1.214 1.202 0.8 1.0 1.6 1.2 0.9 1 ET - detector et42=3.814 4.431 3.800 3.902 5.055 3.756 3.883 1.3 3.4 0.8 1.0 2.2 0.9 1.7 et35=3.588 4.292 3.796 2.989 3.143 3.135 3.391 160.7 104.7 91.9 148.1 93.7 125.5 107.0 et28=3.716 3.581 3.493 3.383 3.380 3.292 3.573 389.6 141.8 266.2 125.5 163.0 75.1 126.3 et21=2.964 3.540 3.336 3.661 3.369 3.270 3.354 2465.9 1820.2 1266.6 890.7 655.1 525.2 315.9 et14=3.362 3.216 3.843 3.588 4.179 3.307 2.909 49.0 35.1 27.9 16.5 10.3 4.7 2.5 et07=2.628 3.617 3.847 4.117 3.632 3.186 3.916 0.8 2.0 1.4 2.2 0.9 1.3 2.4 et00=3.537 3.584 3.613 3.599 3.329 3.292 3.581 0.8 1.1 1.0 1.3 2.2 1.1 1.2 Water Veto: 4.732 MeV/FADCcount, not calibrated (old) This set of calibration coefficients was obtained at On-Line calibra- tion procedure for "Photoproduction Brunch" of H1Lumi at 01:15 25.05.92 Start values of this coefficients was got from previous calibartion (see message from 19.05.1992). 29.05.1992 ===================== H1KFOM === Difference at CC sets ===== Due to attempts to make off-line calibration it was found that there is difference at calibration coefficients sets for different releases of H1LumiOnLineFIFO-program (which can run at the FIC#1). It is very imporatant for created with this program LREC and LRPC-banks at RunStartRecords. There are three releases of H1LumiOnlineFIFO-program for today: H1LumiOnLineFIFOA - for autonomous work at Mode 3 without H1CDAQ and without H1CDAQ - source of triggers - our H1Lumi Trigger. H1LumiOnLineFIFOB - for work at Mode 3 with H1CDAQ and without H1CTRIG - source of triggers - our H1Lumi Trigger. H1LumiOnLineFIFOC - for work at Mode 0 with H1CDAQ and with H1CTRIG - source of triggers - H1CTRIG (ETAG-trigger bit as one of possible sources). At last HERA e-beam run for H1 and ZEUS (24-25 May1992) we wrote a part of H1Lumi Runs with release H1LumiOnLineFIFOB (Runs 20408, 20409,20416) and with release H1LumiOnLineFIFOC (Runs 20411,20417, 20429,20430,20431). First evidence on this very important point was looked after first attempt to process Run20411 with calibration coefficients set which was used at On-Line (status of CC from 25.05.92 01:15). It was clear that we have sistematic shift into low energy at all energy distribution spectra. Note that OnLine calibration coefficient set was determined during work nonH1LumiOnLineFIFOC releases (H1LumiOnLineFIFOA or H1LumiOnLine- FIFOB). Yesterday it was carried out the off-line calibration of data which was produced with H1LumiOnLineFIFOC release (Run 20431 with "ETAG"- trigger bit as SumET & SumPD & anti(WaterVeto) trigger). It was processed only one cartridge with near 9000 events and the next results are preliminary. Situation with calibration coefficients sets is reflected at the next table: cell name CC Value at C release CC Value at A,Breleases Factor C/A (MeV/FADC count) (MeV/FADC count) E l e c t r o n T a g g e r e21 3.708 2.964 1.25 e22 4.088 3.540 1.15 e23 3.780 3.336 1.13 e24 4.119 3.661 1.13 e25 3.874 3.369 1.15 e26 3.843 3.270 1.18 e27 3.826 3.354 1.14 P h o t o n D e t e c t o r p12 1.256 1.132 1.11 p13 1.289 1.159 1.11 In principle it is possible to make conclusion that all CC at ET must be corrected on factor near 1.13 and all CC at PD must be corrected on factor near 1.11. But it of course depends from the situation - are the all CC at ET almost equal and CC at PD almost equal with each other at PD-cell community. WaterVeto CC must be calibrated on the Runs 20411,20417. The reason of this difference is obvious - difference at pipe-line deep with different source of trigger - local or central. For example for A,B-releases we have FADCs shift constants 102(ET) and 46(PD, WaterVeto) and for C-release - 192(ET) and 138(PD,WaterVeto) as was proclaimed at message 19.05.92 at LLO "e-beam 18-19 May 1992". Each count at shift constants is near 10 nsec. At C-release we have a little less integral value of FADC-counts as at A,B-releases. In principle it is possible to tune shift constants for more near values (factor closely to 1) but we never obtain =1 - it depends from 10 nsec digitization. 1 29.05.1992 ===================== H1KFOM === Off-line Calibration ====== Yesterday (as was proclaimed at previous message) it was carried out off-line calibration of our ET and PD detectors channels on the data which was taken with H1LumiOnLineFIFOC-release (part of Run 20431 with trigger SumPD & SumET & anti(WaterVeto)). After this new calibration coefficients was tested with data collected with the same On-line program release but with another trigger - SumET & SumPD (Run 20417). The job for calibration is kept at H1KFOM.LUMI92I (#A280192) - data set. The job for testing of new CC set is kept at H1KFOM.LUMI92I(#B280592) data set. Coefficient for Water Veto was not calibrated (was got from previous off-line calibration see message 21.05.1992 as 4.730 MeV/FADCcount). LOOK produced histos are kept at H1KFOM.HLOOKA.R20431 data set (for calibration step) and at H1KFOM.HLOOKB.R20417 data set (for test step). More interesting histos are inserted into H1Lumi-logbook which is kept at H1 Control Room (after page 52). Most intersting digits and details: Calibration step (trigger SumPD & SumET & anti(waterVeto) 1) at calibration step it was obtained on the energy distribution spectrum -"Eetrec + Epdrec" the mean value 26.77 CeV and Sigma = 0.88 GeV. 2) at calibration step it was obtained on PD and ET coordinate plots Xpd mean value 0.26 cm and Sigma = 1.32 cm Ypd mean value -0.20 cm and Sigma = 0.77 cm Yet mean value 0.10 cm and Sigma = 0.32 cm 3) Epdrec versus Eetrec plot seems as reasonable - very good population of statistics inside region 26.7GeV+-3Sigma. Epd region for this population is from 3.8 Gev up to 13 Gev, Eet - from 11.5 GeV up to 23.5 GeV. Main statistics inside regions for Epd between 4.7 and 10.2 GeV for Eet between 15.5 and 22.5 GeV. There exists very good correlation between this energies - almost all population of statistics is laied out on the "wide line" between 26.7 GeV points on both axis. Test step (trigger SumPD & SumET ) 1) at test step it was obtained on the energy distribution spectrum -"Eetrec + Epdrec + Ewvdep" the mean value 26.83 CeV and Sigma = 1.19 GeV 2) at test step it was obtained on PD and ET coordinate plots Xpd mean value 0.31 cm and Sigma = 1.53 cm Ypd mean value 0.01 cm and Sigma = 1.01 cm Yet mean value 0.12 cm and Sigma = 0.43 cm 3) Eph=Epdrec+Ewvdep versus Eetrec plot seems as reasonable - main population of statistics is inside region 26.7GeV+-3Sigma. Eph region for this population is from 3.0 Gev up to 16.5 Gev, Eet - from 9.0 GeV up to 25.5 GeV. Main statistics inside regions for Eph between 5.0 and 10.0 GeV for Eet between 16.0 and 24.0 GeV. There exists very good correlation between this energies - almost all population of statistics is laied out on the "wide line" between 26.7 GeV points on both axis. 29.05.1992 ===================== H1KFOM === Problems with On-line ===== Today was appeared unwaitable situation with coexistance of H1LumiOnLine-program with H1CDAQ and H1CTRIG - sometimes our subsystem had stopped H1 Run during timeout - "no L3Keep acknolege". Problems under studying. 29.05.1992 ===================== H1KFOM === HV set 24.05.1992 ========= We forgot to write the last HV set which was installed at 24.05.92 during last great HERA e-beam activity for H1 and ZEUS 24-25.05.92. The HV sets are kept at the next files: FileHVETDefault.24.05.92a FileHVPDDefault.24.05.92a The next values of HV was installed: PD - detector pd20= 1865 V 2050 V 1950 V 2050 V 1870 V pd15= 2080 V 2050 V 1670 V 1680 V 1900 V pd10= 1770 V 1840 V 1710 V 1810 V 1720 V pd05= 2120 V 1770 V 1710 V 1595 V 1835 V pd00= 1950 V 1820 V 1890 V 1860 V 2020 V ET - detector et42= 2015 V 2150 V 1920 V 1860 V 2120 V 2110 V 1910 V et35= 1960 V 2100 V 1950 V 2020 V 2015 V 2035 V 1965 V et28= 1890 V 1940 V 2215 V 2085 V 1835 V 1795 V 1970 V et21= 2100 V 1810 V 2010 V 1900 V 1960 V 1995 V 1860 V et14= 1890 V 1900 V 1870 V 1910 V 1770 V 1670 V 1720 V et07= 1930 V 1840 V 1910 V 1890 V 1610 V 1725 V 1760 V et00= 2040 V 2070 V 1770 V 1840 V 1670 V 1780 V 1720 V WaterVeto 700 V on vetoing PHEU and 560 V on spectr. 1 29.05.1992 ===================== H1KFOM === PD cells Strange Behaivour First observation of spontanious incrementing of SumPD trigger bit rate was looked for at 19.05.1992. This incrementing of rate was not correlated with any visible monitoring scalers and counters - it was not any incrementing od rate on GlobalOr of H1VetoWall or rate of Cherenkov Water Veto of H1Lumi etc. It was not any injection of p-beam at this time - only preparing for injection may be. This incrementing was not very large - from 0 up to 1-10 Hz. At 23.05.92 firstly it was observed the "reason" of this incrementing. When we looked for the picture of raw event with trigger SumPD only we saw very intersting picture - during of the next "activity" of this trigger bit on the p08 it was clear observed very good pulse with good form and large amplitude - on the histos we could see peak at region near 3500 of FADC counts. At neighbour cells we look for nothing - only pedestals. It means that the nature of this pulse is not shower nature - may be some electrical reason - noise or something else. The changing of HV at p08 had adequate changing of amplitude of this strange pulse with not undestandable nature. But this strange behaivour of p08 was not reflected on its good work during HERA e-run 24-25 May 1992. All was OK with energy response of this cell and with coordinate distribution. After e-Run (remember that we changed HV-set during this Run) the situation was changed. Strange pulse at p08 disappeared forever (at last some days we don't look for it) but it were apperead two the same pulses (may be the same nature at p15 and p20). Today it was written Run20960 with all brunches and with almost full trigger bits set. ETAG trigger bit was switched on too. On this trigger was connected the trigger bit "SumPD" The rate of this trigger bit was near 0.06 Hz during first 10 min of this Run. In principle it would be possible to see above mentioned pulses (p15 and p20) at this Run. But this pulses "live" only single p15 or p20. I never looked for both pulses. 29.05.1992 ===================== H01USA === H1Lumi_May#fic2 ========== Sasha, Your request was done. Address for bunch intensity values was changed for fic2 (to 0XB012B300). But there are another addresses from fic1: 0XB002B2D8 - numbers of bunces 0XB002A888 - Photon beam profile 0XB002A9E4 - reset profile flag. They were changed to fic2 too. This DA now is called "H1Lumi_May#fic2" and is installed on right Mac. 29.05.1992 ===================== H01USA === remarks about beam position We must change the title of DA "Beam position" because it provides false impression that we do monitoring of electron beam position in IP. Of coarse it is not so. We are monitoring only the center of hits distribution on the face PD detector not more, which depends as from beam position as from average angle of electron beam in IP. We can not separate them. May be the "Photon beam position" is better? The same situation with "beam profile" - the sigma's of hits distribu- tion on PD reflects angle distribution of electrons in IP, not electron beam profile.