C 2/06/93 411031634 MEMBER NAME EDITFILE (RUN94.S) M *********************************************************************** * * * PART 10 PART 10 * * H1 LUMI LOGBOOK * * * * e+p DATA TAKING JULY-OCTOBER 1994 * * * * * * Enter command LLC under NEWLIB in order to add new information * * Press PF3 button when finish your editting to save the file. * * If you don't yet have LLC command defined, copy it from the * * 'F11LEV.CLIST(LLC)' into your clist member 'userid.CLIST(LLC)' * * * * Use command: F ===== to find all messages, and then select * * those you are interested in * * * * The following commands allow to inspect earlier logbook parts: * * * * LL1 ........ list Part 1 of the Lumi Logbook: Jun'91 - Aug'91 * * LL2 ........ list Part 2 of the Lumi Logbook: Aug'91 - Dec'91 * * LL3 ........ list Part 3 of the Lumi Logbook: Jan'92 - May'92 * * LL4 ........ list Part 4 of the Lumi Logbook: Jun'92 - Aug'92 * * LL5 ........ list Part 5 of the Lumi Logbook: Aug'92 - Nov'92 * * LL6 ........ list Part 6 of the Lumi Logbook: Nov'92 - Jun'93 * * LL7 ........ list Part 7 of the Lumi Logbook: Jun'93 - Nov'93 * * LL8 ........ list Part 8 of the Lumi Logbook: Nov'93 - May'94 * * LL9 ........ list Part 9 of the Lumi Logbook: May'94 - Jul'94 * * * * S.Levonian Opened: 27/07/94 at 16:00 * * Closed: 03/11/94 at 16:30 * * * *********************************************************************** 27.07.1994 ==================== F11LEV === New Chapter of the logbook We (Nelly, Fomenko and me) decided to split last logbook chapter in two separate parts. Splitting is made before first e+p collision run. You can inspect earlier parts by the commands LL1-LL9, where LL9 = LIST 'F11LEV.H1.LUMI.LOGBOOK.PART09' 27.07.1994 ==================== H1KFOM === e+ Injection Attempts Today after 15:00 it were began attempts to inject positrons into HERA e-ring with stable p-beam existing at HERA p-beam.Up to now-18:15 no any progress at injection. We looked for at H1VetoWall rates and H1Lumi VC-rates behaivours with time that really injection attempts took place (jumps at H1VetoWall rates and appearence of VC bunch rates at first 3 bunches on very short time). As seems positrons immediately after injection are lost. At 18:15 it was achieved some progress at e+injection. It was fixed Ie+total near 52 mkA at 3 bunches. Rates at our system are fixed at another bunches as bunch currents value exist (as seems signal of first bunch is shifted). 28/7/94 ======================= H1KSOL === Lumi RUN# 503 Start lumi run503 date: 28/7/94 Collision time: 3:58:44 - 4:55:48 Currents (mkA): Ie= 3000.00, Ip= 36900.00 Peak luminosity: 138.794 mb-1 s-1 Peak spec.lumi : 258.08551 mb-1 s-1 mA-2 Number of collided b.: 36 Number of e+filled b.: 42 Number of p-filled b.: 170 Number of e+pilot b.: 6 Number of p-pilot b.: 134 HERA total lumi: 722.911091 mkb-1 H1 Run total lumi: 622.204 mkb-1 H1 data taken lumi: 368.0458 mkb-1 H1 Runs: 82960 - -1 HERA - physics: 394.807695 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: -1 - -1 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 0.94% RCF Run gated: 0.94% Relative ET trigg accept.: 0.2869 PS.h01lns: L4 histos for this run# are OK, at least qualitatively. PS.h01lns: L5 histos for this run# are OK, at least qualitatively. 28.07.1994 ==================== H1KFOM === H1Lumi Dedicated Runs Today during Lumi RUN# 504(A) it were recorded 2 H1Lumi Dedicated Runs: 1) 82980 - near 250K events with s86,s92-s95 H1Lumi Monitrigs only; H1RAWD.C9401991-1993(82978 and 82979 were prescale gap tuning Runs) from 09:39:55 up to 10:18:02 28.07.94 2) 82994 - near 40K events with s91 and s93 H1Lumi Monirigs only with Mode 1 and with Movable Platform ET at parking position (for Cherenkov Gas Counter Prototype investigation H1RAWD.C9401993 (82988 - 82993 were prescale gap tuning Runs) from 10:43:06 up to 10:51:57 28.07.94 (agreement with HERA crew on absence of Luminosity measurements at this period due to ET at parking positions). 28.07.1994 ==================== F11LEV === Lumi cross check ........ Two messages here: 1) A brief comment to Brinkmann's scan. If we expect, that e-beam deflection influences ET acceptance significantly, one can easily check this using PD rates only instead of ET*PD ones. Just to plot the same figure as B-n and see whether the width will be different from what B obtained. 2) A preliminary cross check of online LUMI was made using data, prepared by Nelly. The result is somewhat unexpected: two samples were used: VC-events (S93) and PD_low events(S91) and they gave different luminosity estimate after all known to me corrections (trigger eff, prescaling, background, double gammas). Only data from G+M runs were used. Gamma spectra used showed a global shift > 0, in spite of LUMIMON events were re-reconstructed with latest calibration from DB. and shift was found to be different for VC and PD samples. Run period Online lumi VC-method PD-method 79913-82005 298 nb-1 326 nb-1 345 nb-1 E-shift 2.4+-0.6% 1.3+-0.5% Note, the values are still preliminary, but what is interesting: a visible difference between VC and PD methods (5-6%). Any ideas? Remember, ZEUS uses analog of PD method, not VC. And in 1993 we used VC to cross check online lumi (that time there was no good PD monitoring trigger) In any case, it seems our 1994 online estimate is too low. How much? More analysis is needed. Ideas, suggestions are welcome. 28/7/94 ======================= h1kric === Lumi RUN# 503(A) Start lumi run503(A) date: 28/7/94 Collision time: 7:04:27 - 13:26:58 Currents (mkA): Ie= 12762.00, Ip= 35701.00 Peak luminosity: 0 mb-1 s-1 Peak spec.lumi : 0 mb-1 s-1 mA-2 Number of collided b.: 0 Number of e-filled b.: 0 Number of p-filled b.: 170 Number of e-pilot b.: 0 Number of p-pilot b.: 170 HERA total lumi: 7265.7864 mkb-1 H1 Run total lumi: 5863.489551 mkb-1 H1 data taken lumi: 4404.272916 mkb-1 H1 Runs: 82969 - 83016 HERA - physics: -0.000236 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 83016 - 83016 Tot curr/rate factor: 0.3% C/R F H1Run gated: 0.34% Rand.C.F: 1% RCF Run gated: 1.03% Relative ET trigg accept.: 0.2932 28.07.1994 ===== dice2 ======== H1KFOM === Relation Coeff.Set R82980 Today it was made Relation Coefficient defining for H1Lumi Dedicated Run data sample. After selection it were produced the next numbers of events: 30859 events with ET&PD&nVC trigger 45094 events with ET&PD&VC trigger 19966 events with S92-trigger. It were got 30859 ET&PD&nVC from these Runs and it were used for calibration 20736 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 1.102 1.114 1.069 1.156 1.172 1.303 1.118 1.027 1.203 1.046 2.181 0.830 0.991 1.104 0.983 0.941 0.949 0.941 1.003 0.448 1.056 1.026 1.002 0.991 0.973 1.017 0.976 0.929 1.002 1.060 1.004 0.905 0.975 0.998 0.994 0.938 0.867 1.096 0.969 0.970 0.000 0.000 1.026 1.048 0.857 0.855 0.931 1.048 0.000 ==> Relation Coeff.Set for PD 2.141 0.933 1.015 1.534 0.000 0.976 1.016 1.048 1.056 0.973 1.001 1.050 1.032 1.043 1.057 1.020 1.023 1.021 1.019 0.982 1.600 1.039 1.105 1.050 0.000 ==> Sig. at Relation Coeff.Set for ET 0.000 0.001 0.000 0.001 0.000 0.000 0.000 0.000 0.002 0.005 0.002 0.001 0.001 0.000 0.003 0.007 0.004 0.008 0.004 0.003 0.009 0.011 0.008 0.008 0.006 0.004 0.008 0.012 0.002 0.008 0.005 0.007 0.002 0.001 0.001 0.007 0.000 0.001 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 ==> Sig. at Relation Coeff.Set for PD 0.000 0.002 0.002 0.002 0.000 0.006 0.004 0.012 0.008 0.004 0.007 0.009 0.011 0.011 0.011 0.004 0.005 0.004 0.015 0.006 0.000 0.010 0.010 0.003 0.000 ==> Ent. at Relation Coeff.Set for ET 4 17 5 6 51 36 6 12 38 30 38 6 6 5 1709 1270 971 551 317 53 52 10107 14107 7867 3554 1451 533 142 3849 3952 1577 377 144 44 17 23 7 16 4 1 0 0 1 5 2 4 3 1 0 ==> Ent. at Relation Coeff.Set for PD 7 13 17 16 0 108 1689 5236 2446 92 1523 9736 17136 8683 713 274 1969 3319 1156 57 11 14 20 7 0 As You can see all is OK with sigma values for all hot channels Relation Coeff. histos. We never looked for these values for Monitrigs. Runs 82978- 82980 (ET&PD&nVC-sample - near 31K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.48 0.98 27.50 0.94 27.49 0.95 Runs 82978- 82980 (ET&PD&VC-sample - near 45K events) all events xetcut Step Mean Sigma Mean Sigma 3 28.20 1.61 28.18 1.54 CCvcs was changed significantly as seems (from ET&PD&VC-sample digits into more low value). It means that VCs response at this period had more large amplitude then at ep Runs. It were used as start values of CC for Photoproduction branch ones which were produced after 3rd step of calibration with 4B sample of (Runs81700-81933) and CCvcs as 3.476. (from H1KFOM's 19.07.94 message at LLC). 28.07.1994 ===== dice2 ======== H1KFOM === PDREC-spectrum for R82980 Today it were produced 100th ntuple for S92=1 events from earlier mentioned H1Lumi Dedicated Run with events from Runs 82978-82980: H1KFOM.ZLOOKQ4.R82978 (17966 entries) FAST12 3010200E 00000 DASD At interactive LOOK-session it was produced 70th histo for this data set and written into the next LOOK-binary data set: H1KFOM.BLOOKQ2.R82978 16430 entries into 70hFAST04 3010200E 00000 DASD First attempt to fit 70th histo at BLOOKQ2-data set put positive sign of Global Energy Shift at Photon Arm (+3.9%) and enough good resolution digits (13%). It were prepared 100th tuples with ET&PD&nVC and ET&PD&VC-events for procedure of defining Global Energy Shifts and CCvcs: H1KFOM.ZLOOKQ2.R82978 30736 entries FAST13 3010200E 00000 DASD H1KFOM.ZLOOKQ3.R82978 44081 entries FAST01 3010200E 00000 DASD 28.07.1994 ==================== H1KFOM === Global Shifts,CCvcs R82980 It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 0.961 for PD Channels (exept VCs), 1.044 for ET channels. Correction factor for CCvcs is 0.734 So CCvcs = 3.476*0.734=2.551Mev FADCcount. These digits are valid for H1Lumi events from Run 82978 up to 82980 Runs 82978- 82980(ET&PD&nVC-sample - near 31K events) xetcut&vcdepcut Step Mean Sigma 0 27.53 0.95 Runs 82978- 82980 (ET&PD&VC-sample - near 45K events) xetcut Step Mean Sigma 0 27.52 1.28 29.07.1994 ==================== H1KFOM === Dedicated Run samples For calibration and another needs it were selected next data sets from high mentioned three H1RAWD-data sets with H1Lumi Dedicated Runs A B C D E F 47.6 H1KFOM.ETPDNVC.R82978.C00 33725 30859 30747 ET&PD&nVC=1 71.3 H1KFOM.ETPDVC.R82978.C00 50448 45094 43973 ET&PD&VC=1 30.1 H1KFOM.S92.R82978.C00 21348 19652 17804 s92 only 67.9 H1KFOM.S86.R82978.C00 48173 43414 42048 s86 only 195.0 H1KFOM.S91.R82978.C00 (*) 49.0 H1KFOM.S91.R82978.C01 (*)173625 118784 59223 s91 only 115.8 H1KFOM.S93.R82978.C00 (*) 82445 44039 6205 s93 only (*) these subsamples includes data with ET at parking position (only s91 and S93 were triggers for this situation. A - data set size (Mbytes) B - data set name C - number of events (selected from 3 H1RAWD.C9401991-C9401993. D - number of events for Runs 82978-82980 (H1 Lumi Dedicated Runs) E - number of entries into 100th ntuple F - data sample trigger High mentioned datasets include events from H1 Runs 82969-82996. It were produced 100th ntuples for each from high mentioned samples(D) with using of Relation Constants, CCvcs and Global Energy Shifts which were defined for H1Lumi Dedicated Run 82980. 100th ntuples are kept at the next data LOOK-binary data sets: H1KFOM.YLOOKQ2.R82978 ETPDnVC FAST09 3010200E 00000 DASD H1KFOM.YLOOKQ3.R82978 ETPDVC FAST02 3010200E 00000 DASD H1KFOM.YLOOKQ4.R82978 S92 FAST08 3010200E 00000 DASD H1KFOM.YLOOKQ5.R82978 S86 FAST18 3010200E 00000 DASD H1KFOM.YLOOKQ6.R82978 S91 FAST04 3010200E 00000 DASD H1KFOM.YLOOKQ7.R82978 S93 FAST01 3010200E 00000 DASD Some facts from view on these data: a) at samples S91 and S92 there are evidence on old problem with p11 (one-element p11-clusters) - 1.1% for s91 and near 3% for S92; b) very different from ordinary ETrec vs PDrec plots: a)there are the same resolution for all PDrec - at e-p Lumi Runs it were fixed that resolution is better for high PDrec; b) no population at low ETrec and high PDrec); c) more or less uniform distribution of statistics along 'beam energy' line - we never saw this at e-p Runs; c) it was made attempt to measure acceptance (visible cross-section) for ET&PD events at s91-sample with using PDrec subsample from PD_Low events (PD.eq.1) and PDrec subsample with ET.eq.1. Threshold value for PD-trigger was estimated as 3.75 GeV. Visible cross-section for PD with this threshold (with accounting of sharpness) was estimated as 89.53 mb. Ratio of entries into PDrec(PD) abd PDrec(ET) is 22173/59125 - so result is unwaitable - Sigma visible is near 33.57 mb (?). It is very preliminary due to Vova is not shure that 89.53 mb is estimated right with his methodic d) good sample for investigation Xet,Yet plot for positrons at HERA e-ring during this time period (very low population at more positive Xet). e) it is possible to check Thresholds values for PD,PD2(eff.) etc. (preliminary PDthr=3.75 GeV, PD2=11.25 GeV); f) very interesting distribution - Xet vs ETrec - for eTAG sample. (more clear presence at plot of offmomentum positrons). g) etc. 29.07.1994 ==================== H01LNS === a Point of View on Lumi == 1.) Instead of Introduction: I should just remind, mostly in an order of Time, of different kinds of LUMI Warnings(!) written recently to LLO: - Many comments on cases of "Wrong Lumi" in Lumi-Summaries, - A number of A.F.'s messages on cases of "Lumi-Spikes", - A few messages on cases of "Different Lumi Crashes", - My own "Draft Warning message" based on L4 observations, - A number of my own "PS L4/L5 Warnings" for the Last(!) RUNs, - A.De Roeck's H1news message on the subject of Lumi "panic", - A.De Roeck's "Check event rates/lumi unit for 93 and 94!!!!" - A.Fomenko's LLO message on the subject of "Lumi Crisis", - A number of "Negative reactions" to some of the above warnings, - A few messages in LLO on the problem of H1-ZEUS Lumi-Difference, - A kind of discussion on the "Brinkman's report on H1/ZEUS", - Some kind of meeting of H1-LPI- and ZEUS- "Lumi people". A Summary at this point: Too many "Signs for the Wrong Lumies". 2.) Instead of Extensive Report, just to gain the Time: I would like to make some kind of "Lumi Forecast", in an order of importance(!): - I believe that the issued set of Lumi measurements includes a good number of wrong values, as underestimated, and overestimated, some kind of "ACCIDENTAL-LARGE-LUMI-ERRORS" by factor of ~2-3 & more. Going to the integrated Lumi These Errors make Lumi wrong by ~10-20%, sometimes "under", but sometimes "over"(!) I am sorry to be so crazy. - Best of all, Existance of such Errors might be checked by comparing H1/ZEUS speccially for the suspected Runs, not for integrated values, and, a careful analysis of our Lumi-Log can be useful in these cases. In a case, I would be right, It seems not difficult to fish-out the wrong measurements (I have done it) and then to mark them "not-Good". - I believe also that, Systematically(!), the "TRUE Lumi-values" must be HIGHER than the issued values, because, I think, the constant MC "True-Lumi-Efficiency" is lower by ~ 5 - 15 %, than the used one. - I think softer(!) that the discussion on the "Brinkman's report on H1/ZEUS", being interesting as itself(!), is mooving us to the questions of minor importance for the problem of Lumi Values. A Summary at this point: Some "Large Lumi Errors" to be checked for. PS: Now I am not trying to proove the points of the above Forecasts, I am trying to lay down my Point of View on the Problem of Lumi. I hope soon to report my Figures for "suspected" Large Lumi Errors. L.Shtarkov, Moscow, Pitomnik. 29.07.1994 ===== #FIC1,2 ====== H1KFOM === H1LumiOnLineReleases === PD-arm Rate Method Attempt H1LumiOnLineFIC1-release which was proclaimed at 27.07.94 my message as seems is not succesful. So we shall live with old one (01.07.94) and problem with miniheaders at LRPE and VETE banks is not resolved now FIC#1 was booted with old release at Lumi RUN #503 period (night). Today due to U.Straumann's request it was prepared release of H1LumiOnLineFIC2 program with attempt to fit Usik's application on measurement of Luminosity with PD-trigger element rate (for HERA . people mainly): It were made only 2 changings: 1) it was added some new array into Local DPM of FIC#2 for supporting of Pilot PD rate measurements for Usik's used 10 variables; 2) it was made update of TenBunchNew.f subroutine for the same fit. Release was booted into FIC#2 near 16:35 today and was tested with test pulses and by hand involved non-zero values connected with beam currents and Usik's calculations. Due to Usik is using direct addresse for getting ET*PD total rate counter from Egor's TTL scaler (...C4-addresse) for fitting to PD- -method it will be needed to reconnect some connectors at Egor's Scalers-module. Today we made this manipulation (ET*PD counts were connected with ...C8-addresse, PD-counts - with C4-addresse). Before testing with real beams it will be needed to put new Visible Cross-section to Usik's application and switch-off acceptance correction involving into Lumi calculation (it is better to not use ACCC at all then to use non-right (calculated for ET*PD)). Vova preliminary estimated Visible Cross Section for PD-rate method (on last Dedicated Run data) and proclaimed this value as 88.1 mb. Really we are not ready to use this method as base method for H1Lumi Calculation but due to request of HERA-people we are making this attempt. As U.Straumann said HERA-people need both methods Lumi estimations digits at their screen. So, Usik - due to he made nothing for data presentation of any alternative method of Lumi Calculation - as seems will be got from his Kream's vacation for making of things which were promised to be made many monthes ago. Let's see what will happen at this case. Now all is came back to old communications. Release will be tested during nearest Lumi RUNs. Now old release is operated at FIC#2. Be careful - at period of high mentioned tests the 221stword at LRTL bank will show PD-total rate (not ET*PD) --> SHOWLUMI ----> OffLine correction may be are not ready for this changing (may be some Egor's tools too - I do not know). But this variant of fitting as seems is simpliest decision at today crisis situation with H1Lumi measurements. Date and time of release creation - 29.07.94 16:35. 30.07.1994 ==================== H1KFOM === HERA p-beam activity Tonight p-beam was injected into HERA p-ring at 23:30. It was fixed Ip total more then 40 mA. At 02:30 p-beam was lost. Today morning enough quickly it was injected and ramped up to 820 GeV enough powerful p-beam and now (near 11:00) as seems it is possible to wait e+injection into HERA e-ring: #D=1994-07-30-11:06:26#K=HEMAGEN #T=2#V= 1.19699826E1 #U=[GeV/c]#E= #D=1994-07-30-11:06:26#K=HPMAGEN #T=2#V= 8.19919813E2 #U=[GeV/c]#E= #D=1994-07-30-11:06:26#K=HESUCURR#T=2#V= 0 #U=[mA] #E= #D=1994-07-30-11:06:26#K=HPSUCURR#T=2#V= 3.78800000E1 #U=[mA] #E= #D=1994-07-30-11:06:26#K=HPSULIFE#T=2#V= 9.99900000E1 #U=[h] #E= #D=1994-07-30-11:06:26#K=HERATXT2#T=3#V= MACHINE STUDIES #U=#E= Really at 11:30 it was started e+injection into HERA e-ring: #D=1994-07-30-11:31:33#K=HEMAGEN #T=2#V= 1.19699826E1 #U=[GeV/c]#E= #D=1994-07-30-11:31:33#K=HESUCURR#T=2#V= 2.59999999E-1 #U=[mA] #E= #D=1994-07-30-11:31:33#K=HESULIFE#T=2#V= 9.99900000E1 #U=[h] #E= 30.07.1994 ==================== H1KFOM === PhArmRateMethod OnLineTest Today during Lumi RUN# 504 it was tested yesterday mentioned release of H1LumiOnLineFIC2 program which can fit the Usik's application for Photon Arm Rate method Luminosity measurement. Test got 17 min of Lumi RUN# 504 (from 13:45 up to 14:02). The next results of this test are proclaimed: a) at 13:48 after switching PD-total rate on Egor's TTL counter with addresse ..C4: Current Lumi value had jumped on 1.66*10**30 cm-2s-1 (due to another total rate accounting at Usik's application); b) after booting of new release (righ accounting of pilots for PD) - --> 1.44*10**30 cm-2s-1 c) after putting 88.1 mb as Visible Cross Section and switching off ACCC accounting at Usik's application ---> 5.48*10**29 cm-2s-1. as seems - too low value. ZEUS Lumi was at this period 6.51-6.53*10**29 cm-2s-1. d) it was found that the same Current Luminosity values were calculated for both method (ET*PD(FIC#2) and PD(Usik's applica- tion) if Sigma visible for Photon Arm method was installed on 75.5 mb (?). e) note - HV at VCv was installed on 920 V (at last Dedicated Run it was installed on 1020 V). 30.07.1994 ==================== H1KFOM === PhArmRateMethod OnLineTest Today during Lumi RUN# 504 it was tested yesterday mentioned release of H1LumiOnLineFIC2 program which can fit the Usik's application for Photon Arm Rate method Luminosity measurement. At this 2nd test we changed HV at VCV on value 1020V which was used at last Dedicated Run (for which Vova defined Visible Cross Section as 88.1 mb for Photon Arm method (with PD-trigger element rates). Test got 10 min of Lumi RUN# 504 (from 14:26 up to 14:36). At 14:36 most of HERA e+beam was lost. The next results of this test are proclaimed: a) after putting 88.1 mb as Visible Cross Section and switching off ACCC accounting at Usik's application ---> 4.08*10**29 cm-2s-1. as seems - the same with ET*PD method (!!!!). ZEUS Lumi was at this period 5.80-5.85*10**29 cm-2s-1. First conclusion: both methods put the same Luminosity values (but ZEUS Lumi was at this period more then at H1). It means that H1Lumi not responsible for low Lumi values at H1 IP - as seems HERA crew can make something for incrementing Lumi at H1 IP. Note: today during first 40 min of Lumi RUN #504 ZEUS Lumi values were always less then H1 Lumi valus on 7-8% (as we could see due too so-called non-standard 'Beam Profile' postion - it was at value near -0.2 cm (standard is near -1.5 cm). At 13:42 HERA crew made tuning of ZEUS 'Beam position' and H1 Lumi became less then ZEUS. ASCII file from ZEUS team for Lumi RUN# 504 is very desirable. 30/7/94 ====================== F. Rouse === Lumi RUN# 504 Start lumi run504 date: 30/7/94 Collision time: 12:48:55 - 14:53:31 Currents (mkA): Ie= 15235.00, Ip= 37700.00 Peak luminosity: 736.539 mb-1 s-1 Peak spec.lumi : 335.426698 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 3449.337742 mkb-1 H1 Run total lumi: 2299.618 mkb-1 <-- must be corrected (2699) H1 data taken lumi: 68.6832 mkb-1 H1 Runs: 83145 - 83149 HERA - physics: 2599.835177 mkb-1 H1Run - physics: 1971.184595 mkb-1 <-- must be corrected (2371) H1data - physics: 40.719637 mkb-1 H1 Runs: 83146 - 83149 Tot curr/rate factor: 0.12% C/R F H1Run gated: 0.12% Rand.C.F: 0.87% RCF Run gated: 0.88% Relative ET trigg accept.: 0.3320 P.S. at 13:20 it was fixed jump at H1Lumi Run Gated and H1 Lumi data taken on value near 0.4 nb-1 (during some manipulation at H1CDAQ) Dead time after 13:20 was always 99% - H1 Shift Crew cannot strugle this problem. P.S. HVvcv before 14:22 was 920V after 14:22 was installed on 1020V. PS.h01lns: L4 histos for this run# are ~OK, too low stat., strange Eet PS.h01lns: L5 histos for this run# are not yet ready ... 30.07.1994 ==================== H1KFOM === Dedicated Run S93 100thntp It were recalculated 100th ntuple for PDmin and ETmin =0.5 (at all previous ntuples this values were 3.0 GeV) for S93-sample only with using of Relation Constants, CCvcs and Global Energy Shifts which were defined for H1Lumi Dedicated Run 82980. 100th ntuple is kept at the next data LOOK-binary data sets: H1KFOM.YLOOKQ7A.R82978 FAST04 3010200E 00000 DASD P.S. It is pity but fact is fact - new value of SigmaVisible which was calculated with recalculated 100th ntuple for s93 -events for new LREC thresholds (0.5 GeV) put new value of PD-threshold - near 4.2 GeV and new value of SigmaVisible (82.1 mb). It means that ET&PD method and PhotonArm method put different Luminosity values (ET&PD method is underestimated Current Luminosity value on 8-10% - preliminary). Today was really dramatical day. 30/7/94 ======================= === Lumi RUN# 505 Start lumi run505 date: 30/7/94 Collision time: 22:14:50 - 22:41:41 Currents (mkA): Ie= 0.00, Ip= 1.00 Peak luminosity: 0.952 mb-1 s-1 Peak spec.lumi : 0.24799 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 2.20069 mkb-1 H1 Run total lumi: 2.063572 mkb-1 H1 data taken lumi: 1.079113 mkb-1 H1 Runs: 83158 - 83159 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 83159 - 83159 Tot curr/rate factor: 0.61% C/R F H1Run gated: 0.22% Rand.C.F: Not calc.% RCF Run gated: Not calc.% Relative ET trigg accept.: Not calc. 31/7/94 ======================= J.Moeck === Lumi RUN# 506 Start lumi run506 date: 30/7/94 Collision time: 22:44:39 - 3:07:26 Currents (mkA): Ie= 19820.00, Ip= 36500.00 Peak luminosity: 1017.187 mb-1 s-1 Peak spec.lumi : 308.16826 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 5538.408949 mkb-1 H1 Run total lumi: 4859.7634 mkb-1 H1 data taken lumi: 1731.0636 mkb-1 H1 Runs: 83159 - 83170 HERA - physics: 3580.659886 mkb-1 H1Run - physics: 2945.714137 mkb-1 H1data - physics: 767.49048 mkb-1 H1 Runs: 83160 - 83170 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 2.27% RCF Run gated: 2.31% Relative ET trigg accept.: 0.3093 P.S. LRTL- and LUMM-banks were not written into H1DataFlow after 23:50 (during Run 83161 were fixed last LRTL-banks with SHOWLUMI). All Intergrated Values for H1DataBase must be recalculated with LRTN-bank using).Data from part of Run83161 up to Run 83170 were written without LRTL and LUMM banks. Alarm on absence of LRTL-bank at H1DataFlow became very important This is second case at H1DataTaking with LRTL-absence at H1Data- Flow. PS.h01lns: L4 histos for this run# are ~OK, too low stat., strange Eet PS.h01lns: L5 histos for this run# are ~OK, too low stat., strange Eet PS.h01lns: Warning for Eet: N for ch's ~ 10-12 as if highly decreased PS.h01lns: Warning for Etag: The "left peak" as if disappeered ... 31.07.1994 ================= V.Andreev === CrossSection for positrons Today the value of Cross Section for the ET*PD coincidence method for the positrons was recalculated. Because the pisitron's beam optics is the same as for the electrons except of course the oppposite sign (this information was recieved from Bialowons W.), the cross section is also the same Sigma = 32.204 mb. The cross sections for the different X-cut at the ET-detector are shown in the table. Acceptance is valid for the next energy range of scattered electrons 4.0 GeV <= E_e <= 24.0 GeV ----------------------------------------------------------------------- XCUT[cm] = 7.70 7.60 7.00 6.60 6.00 5.50 ACCEPTANCE= 0.37696 0.36835 0.33717 0.31497 0.28438 0.25974 SIGMA[mb] = 32.2036 31.4680 28.8043 26.9078 24.2945 22.1895 ----------------------------------------------------------------------- 01.08.1994 ==================== H01LNS === LRTL and L4/L5 s/w ===== 31.07.1994 was not the first time for a talk about RRTL/L4 alarm. I feel myself a little responsible for L4-controls, that is why, in LLO 14.06.1994 I proposed some update of L4 including the Lumi-banks, etc. Before such updating, the L4/L5 controls of Lumi can not be effective. Unfortunately, Nobody at all have responded to these proposals, and as for me, I have not got a Real Access for Updating of L4/L5 software. Presently, I would like just to read in LLO of any plans for this item.1NEWS == I think, the recent H1news on L4/L5 (Prosi; Beyer; Egli; Beyer) were not responded, as they should be. It was, too, not accessible for me. L.Shtarkov, Moscow, Pitomnik. 1/8/94 ===================== droutskoi === Lumi RUN# 507 Start lumi run507 date: 31/7/94 Collision time: 22:45:35 - 2:09:14 Currents (mkA): Ie= 23177.00, Ip= 37301.00 Peak luminosity: 1360.486 mb-1 s-1 Peak spec.lumi : 305.519026 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 12358.922552 mkb-1 H1 Run total lumi: 10702.3564 mkb-1 H1 data taken lumi: 5637.8148 mkb-1 H1 Runs: 83227 - 83249 HERA - physics: 11480.14319 mkb-1 H1Run - physics: 9918.6534 mkb-1 H1data - physics: 4946.7309 mkb-1 H1 Runs: 83230 - 83249 Tot curr/rate factor: 3.11% C/R F H1Run gated: 2.59% Rand.C.F: 2.77% RCF Run gated: 2.62% Relative ET trigg accept.: 0.3216 PS: LRTL and LUMM banks were not tranfered to the CDAQ, PS.h01lns: L4 histos are ~OK, But ET35; PD25 are too high. PS.h01lns: L5 histos are ~OK. PS.h01lns: Warning: ET+PD+VC Mean is > 27.0 GeV, that is unusial. 01.08.1994 ===================== H1KSOL === PD Lumi ..... During Lumi Run#509 online Lumi measurement was done by PD only since beginning of Lumi Run till 22.20 (H1 Run 83298 inclusive). Comments and conclusions later on. 2/8/94 ======================= koehler === Lumi RUN# 509 PS.lns.03.07.94: #508 ? Start lumi run509 date: 1/8/94 Collision time: 19:36:38 - 1:12:11 Currents (mkA): Ie= 14611.00, Ip= 44100.00 Peak luminosity: 671.123 mb-1 s-1 Peak spec.lumi : 343.438256 mb-1 s-1 mA-2 Number of collided b.: 152 Number of e-filled b.: 167 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 18 HERA total lumi: 10349.851657 mkb-1 H1 Run total lumi: 9328.3982 mkb-1 H1 data taken lumi: 8679.3878 mkb-1 H1 Runs: 83294 - 83303 HERA - physics: 8451.567221 mkb-1 H1Run - physics: 7715.208874 mkb-1 H1data - physics: 7083.201191 mkb-1 H1 Runs: 83295 - 83303 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 0.77% RCF Run gated: 0.69% Relative ET trigg accept.: 0.3210 PS.lns: L4 histos are ~OK, But only PD25 is too high. PS.lns: L5 histos are ~OK. PS.lns: Warning: ET+PD+VC Mean is > 27.0 GeV, that is unusial. 02.08.1994 ==================== F11LEV === few remarks ........... 1) Lumi cross check off-line, made 28/07. Some people suspected, that the difference in VC and PD_low samples could be explained by some changes in the trigger threshold made in July. It is not true, since for the offline cross check, only events with E(gamma)>16 GeV were used (far above any threshold effects) 2) On the online PD-method. Never made such a basic changes in the system before leaving! I am not sure, that all minuses we got by these "test" (? or new running mode?) can be compensated by questionnable "plus" of more correct online Lumi. a) obvious things: how we are going to control dynamically a possible changes of trigger threshold and gain factors? b) i suspect, that in all cases where PD method was used (by replacing ET*PD rates by PD) the lumi in database are wrong, because they are calculated from rates in LRTL of course assuming they are ET*PD rates (corresponding cross section used is ~ 32mb) P.S. If, as pointed by Yura, only a total ET*PD rate was replaced by PD rate, then the database values are not affected, because I am using not a total rate, but a Sum{R(i)} over all filled bunches. 3) As far as overall lumi system reliability is concerned, I basically agree with Shtarkov, and can only refer to my own message in LLO from June, 11. 4) MC for ET-acceptance. Recently, few events happend for which H1LUMI MC was used: - Andreev estimated visible cross section for ET*PD method for e+p - Yura & Brinkmann made measurements scanning e+/p beams in H1 IP - H1 people wanted to know again the dependence of ET-acceptance on the beam tilt. My comments. a) In principle, there is no difference whatsoever between e- and e+ modes in H1LUMI, except possible influence of H1 mag.field. Therefore a question I asked before is still valid: is the sign of H1 field changed compared to e-p mode, or not? On the other hand, as it follows from few messages by Fomenko, there was a visible difference observed in ET spectra between e+p and e-p cases. If this is not H1 mag.field effect - it means there is something which is not taken into account correctly in H1LUMI MC (exact fields/positions of quadrupoles? wake fields?) or just beam conditions (tilt,offset) has changed. b) It was demonstrated many times during years, that ET-acceptance depends on both a) e-beam tilt in IP and b) e-beam offset in IP. Both effects can be simulated in H1LUMI. However, only one can be experimentally measured by PD beam profile (tilt: 1cm=0.1mrad) At least we cannot distinguish from the position of gamma spot at PD between tilt and offset. Usually, offset is small compared to beam spot shift due to the tilt (1-2mm or less). However an effect on the ET-acceptance can be large. So, if we do not have an independent method of estimating the offset in H1 IP, the only thing we can do (what I did in 1993) is to tune both tilt and offset such, that ET-acceptance as measured from the data is described by MC. c) Yura has mentioned in mail to me, that a gradual drift of the gamma spot at PD is explained by magnets warming up and then going back to the normal temperature over the whole ep-cycle. Is it true? If yes, why ZEUS does not observe similar effect? And most important: those changes in magnets cause change in the beam tilt only, or also an offest in IP? 03.08.1994 ==================== H1KSOL === Beam drift.... The drift is conserned (as I understood) mainly to the shift of orbit in IP (XOFF value in MC),but of course the drift of tilt is not excluded (but I have to clarify that with Brinkmann). And if shift is 1-2mm inside the ring (and there are indirect indications to that) we will underestimate Lumi by relatively large value,specially at the beginning of the LUMI Run when tilt equal 0 or has a positive value. The results of Monte Carlo one can see by executing 'H1KSOL.MCETAC.mac ro' and issuing command 'f 1-4' in LOOK sesion. PS: shift = offset 03.08.1994 ==================== H1KSOL === PD Lumi....... Since H1 Run #83402 PD method for online Lumi was switched on. So word#221 (etpd rate is actually pd rate). Some online observations for PD compare ETPD : 1.At the beginnig of the Lumi Run (Monday evening) Lumi (PD) was about 6-7% higher then Lumi(ETPD). After half an hour the difference gets smaller namely about 3% and stayed on this level till end of Lumi Run. The behavior of X-PD was the following: it starts from 0 and then during about 30 min went to -5mm smoothly and then fixed on this level till end of Lumi Run. 2.Today measurements showed difference between PD and ETPD of order 2-3%. X-PD was rather uniform and near zero. 3/8/94 ======================= koehler === Lumi RUN# 510 Start lumi run510 date: 2/8/94 Collision time: 22:38:38 - 9:51:27 Currents (mkA): Ie= 24567.00, Ip= 40400.00 Peak luminosity: 1714.103 mb-1 s-1 Peak spec.lumi : 332.958955 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 36276.664958 mkb-1 H1 Run total lumi: 34908.412091 mkb-1 H1 data taken lumi: 29566.709562 mkb-1 H1 Runs: 83379 - 83397 HERA - physics: 35319.423084 mkb-1 H1Run - physics: 33244.876883 mkb-1 H1data - physics: 27952.731494 mkb-1 H1 Runs: 83381 - 83397 Tot curr/rate factor: 0.4% C/R F H1Run gated: 0.4% Rand.C.F: 1.5% RCF Run gated: 1.49% Relative ET trigg accept.: 0.3104 PS.lns: L4 histos are ~OK, But only PD25 is too high. PS.lns: L5 histos are ~OK. PS.lns: Warning: ET+PD+VC Mean is > 28.0 GeV(!), that is unusial. PS.lns: This LRun#=509 and the previous LRun#=509, Why? 3/8/94 ======================= koehler === Lumi RUN# 511 Start lumi run511 date: 3/8/94 Collision time: 10:02:21 - 12:34:16 Currents (mkA): Ie= 7154.00, Ip= 38701.00 Peak luminosity: 477.428 mb-1 s-1 Peak spec.lumi : 323.130568 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 4017.086695 mkb-1 H1 Run total lumi: 3337.06 mkb-1 H1 data taken lumi: 2459.0504 mkb-1 H1 Runs: 83401 - 83406 HERA - physics: 3961.131919 mkb-1 H1Run - physics: 3322.598213 mkb-1 H1data - physics: 2453.168042 mkb-1 H1 Runs: 83401 - 83406 Tot curr/rate factor: 0.04% C/R F H1Run gated: 0.05% Rand.C.F: 0.4% RCF Run gated: 0.4% Relative ET trigg accept.: 0.3178 PS.lns: L4 histos are ~OK, But only PD25 is too high. PS.lns: Warning: ET+PD+VC_Mean > 28.0(!) GeV, that is unusial. 4/8/94 ====================== === Lumi RUN# 512 Start lumi run512 date: 3/8/94 Collision time: 16:01:21 - 0:48:16 Currents (mkA): Ie= 22178.00, Ip= 37400.00 Peak luminosity: 1337.635 mb-1 s-1 Peak spec.lumi : 321.530257 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 165 Number of p-filled b.: 170 Number of e-pilot b.: 12 Number of p-pilot b.: 17 HERA total lumi: 26220.721863 mkb-1 H1 Run total lumi: 21351.9193 mkb-1 H1 data taken lumi: 17380.0619 mkb-1 H1 Runs: 83429 - 83460 HERA - physics: 23889.629997 mkb-1 H1Run - physics: 18944.246996 mkb-1 H1data - physics: 15040.19302 mkb-1 H1 Runs: 83431 - 83460 Tot curr/rate factor: 0.03% C/R F H1Run gated: 0.03% Rand.C.F: 1.29% RCF Run gated: 1.31% Relative ET trigg accept.: 0.3086 PS.lns: L4 histos are OK, High PD25 became usial. PS.lns: L5 histos are OK. PS.lns: Warning: ET+PD+VC_Mean came back to < 28.0(!) GeV. 4/8/94 ====================== koehler === Lumi RUN# 513 Start lumi run513 date: 4/8/94 Collision time: 6:19:56 - 13:52:03 Currents (mkA): Ie= 22849.00, Ip= 35900.00 Peak luminosity: 2110.284 mb-1 s-1 Peak spec.lumi : 500.559674 mb-1 s-1 mA-2 Number of collided b.: 152 Number of e-filled b.: 167 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 18 HERA total lumi: 38468.765484 mkb-1 H1 Run total lumi: 33662.021522 mkb-1 H1 data taken lumi: 30090.726567 mkb-1 H1 Runs: 83482 - 83520 HERA - physics: 36727.456566 mkb-1 H1Run - physics: 32412.204272 mkb-1 H1data - physics: 28883.495431 mkb-1 H1 Runs: 83484 - 83520 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 1.36% RCF Run gated: 1.32% Relative ET trigg accept.: 0.3318 PS.lns: L4 histos are OK, High PD25 became usial. PS.lns: L5 histos are OK. PS.lns: Warning: ET+PD+VC_rec_Mean again > 28.0 GeV. 05.08.1994 ===== dice2 ======== H1KFOM === Selected H1Lumi Monitrig.. Today it were selected calibration data samples from the next data sets which were produced with standard job prepared by S.Levonyan at dice1-environment: HERA03.H01.LUMIMON.C9400048 L09600 78048081 00002 ACS-E-C ...... HERA03.H01.LUMIMON.C9400056 K32870 78048081 00001 ACS-E-C It were selected events with (s92=1 only),with ET&PD&VC=1 and with ET&PD&nVC from these data sets (as ordinary) from 599100 events: 1) S92=1 only 16653 events ( 26.2 MBytes) 2) ET&PD&VC 65746 events (108.0 MBytes) 3) ET&PD&nVC 28827 events ( 47.9 MBytes) Created data sets were saved at DESY IBM storage at the next data sets H1KFOM.ETPDNVC.M4856.C00 K23840 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M4856.C00 K23937 78048081 00001 ACS-E-C H1KFOM.S92.M4856.C00 K23969 78048081 00001 ACS-E-C These data include events from Lumi RUNs# 503(A)-513 (H1 Runs 83004- 83499). P.S. after selection ET&PD&nVC-events from only Good and Medium Runs it was kept for calibration only 11340 events and it was used for calibration only 7877 events (attempt of first step). It were events from Lumi RUNs# 504-513, H1Runs 83146-83499). As seems there are not enough data for first calibration with H1Lumi Monitrig events (first calibration with e+p data). Let's wait (a little I hope). 6/8/94 ===================== droutskoi === Lumi RUN# 514 Start lumi run514 date: 6/8/94 Collision time: 1:28:22 - 10:30:26 Currents (mkA): Ie= 24780.00, Ip= 28700.00 Peak luminosity: 1034.496 mb-1 s-1 Peak spec.lumi : 332.719138 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 21445626.544562 mkb-1 <---- NAN in HERA produced H1 Run total lumi: 15761.1305 mkb-1 H1 data taken lumi: 10838.0183 mkb-1 H1 Runs: 83757 - 83801 HERA - physics: 21444452.026599 mkb-1 <----- NAN in HERA produced H1Run - physics: 14514.24466 mkb-1 H1data - physics: 9708.007515 mkb-1 H1 Runs: 83762 - 83801 Tot curr/rate factor: 0.13% C/R F H1Run gated: 0.14% Rand.C.F: 1.47% RCF Run gated: 1.47% Relative ET trigg accept.: 0.3053 PS: Hera Total Lumi: 19000 mkb-1 - estimation from History plot Hera Physics : 18580 mkb-1 - from Lumi and time for tuning.(YS) PS.lns: L4 histos are OK, High PD25 became usial. PS.lns: L5 histos are OK. PS.lns: Warning: ET+PD+VC_rec_Mean again > 28.0 GeV. 6/8/94 ======================= === Lumi RUN# 515 Start lumi run515 date: 6/8/94 Collision time: 18:28:23 - 19:48:41 Currents (mkA): Ie= 24413.00, Ip= 32400.00 Peak luminosity: 1219.083 mb-1 s-1 Peak spec.lumi : 316.860071 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 3812.484887 mkb-1 H1 Run total lumi: 3587.427916 mkb-1 H1 data taken lumi: 3364.681072 mkb-1 H1 Runs: 83811 - 83818 HERA - physics: 1769.030242 mkb-1 H1Run - physics: 1269.347476 mkb-1 H1data - physics: 1093.41384 mkb-1 H1 Runs: 83814 - 83818 Tot curr/rate factor: 0.22% C/R F H1Run gated: 0.21% Rand.C.F: 2.78% RCF Run gated: 2.84% Relative ET trigg accept.: 0.3289 PS.lns: L4 histos are OK, High PD25 became usial. PS.lns: L5 histos are OK. 7/8/94 ======================= koehler === Lumi RUN# 516 Start lumi run516 date: 6/8/94 Collision time: 21:25:07 - 5:45:50 Currents (mkA): Ie= 24152.00, Ip= 32200.00 Peak luminosity: 967.722 mb-1 s-1 Peak spec.lumi : 242.204009 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 21047.613759 mkb-1 H1 Run total lumi: 19683.5901 mkb-1 H1 data taken lumi: 18053.0044 mkb-1 H1 Runs: 83826 - 83844 HERA - physics: 20743.725347 mkb-1 H1Run - physics: 14212.472617 mkb-1 H1data - physics: 12831.104727 mkb-1 H1 Runs: 83828 - 83844 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 1.7% RCF Run gated: 1.7% Relative ET trigg accept.: 0.3061 PS.lns: L4 histos are OK, High PD25 became usial. PS.lns: L5 histos are OK. 7/8/94 ======================= koehler === Lumi RUN# 517 Start lumi run517 date: 7/8/94 Collision time: 7:57:50 - 9:11:09 Currents (mkA): Ie= 26537.00, Ip= 30800.00 Peak luminosity: 733.418 mb-1 s-1 Peak spec.lumi : 196.06301 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 3259.444039 mkb-1 H1 Run total lumi: 3228.3744 mkb-1 H1 data taken lumi: 3168.405 mkb-1 H1 Runs: 83844 - 83846 HERA - physics: 513.262118 mkb-1 H1Run - physics: 317.483812 mkb-1 H1data - physics: 284.054783 mkb-1 H1 Runs: 83845 - 83846 Tot curr/rate factor: 0.79% C/R F H1Run gated: 0.8% Rand.C.F: 3.89% RCF Run gated: 3.9% Relative ET trigg accept.: 0.3392 PS.lns: L4, L5 histos are OK. 8/8/94 ======================= meyer === Lumi RUN# 518 Start lumi run518 date: 8/8/94 Collision time: 6:19:42 - 8:40:18 Currents (mkA): Ie= 27964.00, Ip= 30700.00 Peak luminosity: 1840.012 mb-1 s-1 Peak spec.lumi : 458.436408 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 8984.317064 mkb-1 H1 Run total lumi: 7775.2401 mkb-1 H1 data taken lumi: 7201.0869 mkb-1 H1 Runs: 83935 - 83945 HERA - physics: 4570.291999 mkb-1 H1Run - physics: 3155.13598 mkb-1 H1data - physics: 2651.955012 mkb-1 H1 Runs: 83936 - 83945 Tot curr/rate factor: 1.92% C/R F H1Run gated: 2.11% Rand.C.F: 3.51% RCF Run gated: 3.67% Relative ET trigg accept.: 0.3424 PS.lns: L4, L5 histos are OK. 8/8/94 ======================= buesser === Lumi RUN# 519 Start lumi run519 date: 8/8/94 Collision time: 11:22:13 - 20:49:57 Currents (mkA): Ie= 26800.00, Ip= 30000.00 Peak luminosity: 1661.917 mb-1 s-1 Peak spec.lumi : 417.340589 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 21488602.081648 mkb-1 <--NAN in HERA produced H1 Run total lumi: 23815.2104 mkb-1 H1 data taken lumi: 19073.9896 mkb-1 H1 Runs: 83957 - 83992 HERA - physics: 21485496.192159 mkb-1 <---NAN in HERA produced H1Run - physics: 20523.54236 mkb-1 H1data - physics: 16187.007696 mkb-1 H1 Runs: 83963 - 83992 Tot curr/rate factor: 0.41% C/R F H1Run gated: 0.42% Rand.C.F: 1.97% RCF Run gated: 1.94% Relative ET trigg accept.: 0.3259 PS.lns: GKS in LOOK is not working ! PS.lns: L4, L5 histos are OK. PS. HERA total Lumi: 28927.08 mkb-1 HERA - physics : 25821 mkb-1 (YS) 8/8/94 ======================= i04rie === Lumi RUN# 520 Start lumi run520 date: 8/8/94 Collision time: 22:18:03 - 22:22:38 Currents (mkA): Ie= 24419.00, Ip= 0.00 Peak luminosity: 0 mb-1 s-1 Peak spec.lumi : 0 mb-1 s-1 mA-2 Number of collided b.: 0 Number of e-filled b.: 168 Number of p-filled b.: 0 Number of e-pilot b.: 168 Number of p-pilot b.: 0 HERA total lumi: 0 mkb-1 H1 Run total lumi: 0 mkb-1 H1 data taken lumi: 0 mkb-1 H1 Runs: -1 - -1 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: -1 - -1 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: Not calc.% RCF Run gated: Not calc.% Relative ET trigg accept.: Not calc. 09.08.1994 ==================== H1KFOM === Lumi=2.7**10**30 cm-2s-1 Today during Lumi RUN# 521 it was fixed new record Current Luminosity value as 2.7*10**30 cm-2s-1. This event happened near 04:20 09.08.94. ET&PD total trigger rate was near 105kHz. =-1.0cm =0.0cm. 09.08.1994 ==================== H1KFOM === New Brinkmann's Scan? Today early morning (from 06:01:31 up to 06:44:31) it were fixed on 71st vector of SHOWLUMI (Current Luminosity value behaivour with time) 5 jumps (as seems artificial) which are very similar to Brinkmann's scan exercises at July 94: 1) from 06:01:31 during 2 min. Lumi=1.98*10**30cm-2s-1 --> 1.6 --> 1.98 2) from 06:13:31 during 2 min. Lumi=1.84*10**30cm-2s-1 --> 1.52--> 1.98 3) from 06:23:31 during 2 min. Lumi=1.89*10**30cm-2s-1 --> 1.48--> 1.90 4) from 06:32:31 during 2 min. Lumi=1.84*10**30cm-2s-1 --> 1.44--> 1.84 5) from 06:44:31 during 2 min. Lumi=1.76*10**30cm-2s-1 --> 1.24--> 1.84 Only during first 'jump' it was fixed changing at -value from -1.0 cm to 0.0cm and durimg 2-5th 'jumps' no any evidence on - changing. Is it possible to know which nature of high mentioned jumps at Current Luminosity values? May be it is really new Brinkmann's scan? 09.08.1994 ==================== H1KFOM === Else One Brinkmann's Scan Today from 13:08:33 up to 13:31:33 it was made else one new Brinkmann 's Scan (as it was possible to look for at SHOWLUMI 71th vector). It was made during current Lumi RUN# 521. H1 Current Luminosity value had the next values at this period: 0.87*10**30 cm-2s-1 --> 0.05 --> 0.70 --> 0.00 --> 0.87 --> 0.55 --> --> 0.87 --> 0.55 --> 0.45 --> 0.87*10**30cm-2s-1 09.08.1994 ===== dice2 ======== H1KFOM === Selected H1Lumi Monitrig.. Today it were selected calibration data samples from the next data sets which were produced with standard job prepared by S.Levonyan at dice1-environment: HERA03.H01.LUMIMON.C9400057 K24269 78048081 00001 ACS-E-C ...... HERA03.H01.LUMIMON.C9400062 K26896 78048081 00001 ACS-E-C It were selected events with (s92=1 only),with ET&PD&VC=1 and with ET&PD&nVC from these data sets (as ordinary) and combined with events which were selected at 05.08.94 (48-56 LUMIMONs): 1) S92=1 only 29979 events ( 47.3 MBytes) 2) ET&PD&VC 106271 events (176.2 MBytes) 3) ET&PD&nVC 49342 events ( 82.0 MBytes) Created data sets were saved at DESY IBM storage at the next data sets H1KFOM.ETPDNVC.M4862.C00 K19738 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M4862.C00 K40603 78048081 00001 ACS-E-C H1KFOM.S92.M4862.C00 K21075 78048081 00001 ACS-E-C These data include events from Lumi RUNs# 503(A)-521 (H1 Runs 83004- 84028). 9/8/94 ======================= h1kleb === Lumi RUN# 521 Start lumi run521 date: 9/8/94 Collision time: 3:55:37 - 16:46:15 Currents (mkA): Ie= 26348.00, Ip= 44500.00 Peak luminosity: 2066.168 mb-1 s-1 Peak spec.lumi : 342.778781 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 59246.830281 mkb-1 H1 Run total lumi: 56676.458313 mkb-1 H1 data taken lumi: 41178.526931 mkb-1 H1 Runs: 84014 - 84039 HERA - physics: 57623.985513 mkb-1 H1Run - physics: 54478.825013 mkb-1 H1data - physics: 39013.204331 mkb-1 H1 Runs: -1 - 84039 Tot curr/rate factor: 0.54% C/R F H1Run gated: 0.52% Rand.C.F: 1.32% RCF Run gated: 1.31% Relative ET trigg accept.: 0.3311 PS.lns: L4, L5 histos are OK for RR==84023;84038(!) 10/8/94 ======================= i04rie === Lumi RUN# 522 Start lumi run522 date: 9/8/94 Collision time: 18:07:50 - 5:56:16 Currents (mkA): Ie= 31219.00, Ip= 41100.00 Peak luminosity: 1863.246 mb-1 s-1 Peak spec.lumi : 316.578791 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 34188.859369 mkb-1 H1 Run total lumi: 31469.2311 mkb-1 H1 data taken lumi: 24287.5975 mkb-1 H1 Runs: 84044 - 84091 HERA - physics: 29866.872814 mkb-1 H1Run - physics: 26934.158094 mkb-1 H1data - physics: 19987.711453 mkb-1 H1 Runs: 84045 - 84091 Tot curr/rate factor: 1.65% C/R F H1Run gated: 1.69% Rand.C.F: 2.99% RCF Run gated: 3.06% Relative ET trigg accept.: 0.3287 PS.lns: L4, __ histos are OK for RR==84069;84089(h1ep) 10.08.1994 ==================== H1KFOM === New Scan Exercises Tonight from 00:52 up to 01:49 during Lumi RUN# 522 it were fixed at 71 and 73th vectors of SHOWLUMI-facility some manipulation of HERA people with beam position(and with beam tilt) at H1 Interaction Point (as it was proclaimed at H1RUN pinboard - provocated by Brinkmann and Soloviev): 1) 00:52 during 4 min: Lumi=0.56*10**30cm-2s-1 --> 0.34 --> 0.58 =-0.4cm -->+0.7cm-->+1.0cm =-2.0cm without changing 2) 01:09 during 16 min: Lumi=0.56*10**30cm-2s-1 --> 0.04 --> 0.40 --> --> 0.46 --> 0.28 --> 0.32 --> 0.50 =+1.0cm -->-2.0cm-->-2.4cm =-1.8cm without changing 3) 01:26 during 23 min: Lumi=0.50*10**30cm-2s-1 --> 0.01 --> 0.50 --> --> 0.48 --> 0.44 --> 0.50 =-2.4cm -->+0.6cm-->+1.2cm-->+0.4cm =-1.8cm -->-1.0cm 10.08.1994 ==================== F11LEV === Useful value when scanning Last time several scans were made by Brinkmann and Yura Soloviev, to understand ET acceptance behaviour as a function of beam conditions. It seems, that the following quantity is very useful to control during such scans: R(ET*PD) ---------- as a function of time R(PD) Present claim is, that PD-acceptance is practically independent on beam conditions (offset) while ET-acceptance is strongly varying. Thus, a proposed ratio should reflect this directly. 10.08.1994 ===== dice2 ======== H1KFOM === Problems with PD-rates Today Vova Andreev sent mail to me with evidence that during Lumi RUN# 509 (H1Runs83294-83298) he looked for different PD-total rates at 221st word od LRTL-bank and 226th word of LUMM-bank. At high mentioned H1 Runs Y.Soloviev investigated Lumi measurements at OnLine with PD-method and switched on PD-total rate counter on C4-TTL scaler (and at 221st word of LRTL it must be fixed PD-total rate - not ET&PD total rate as at ordinary Runs). I tested else one contents of LRTL- and LUMM banks at these H1 Runs and found that really this fact is true. As example: 1) t0 - start of H1 Run 83294: Ie+= 10 mA, Ip=43.76 mA PD Total Rate (TTL scaler, 221st word of LRTL) = 105 kHz PD Total Rate (Sum of 220 PD bunch trigger rates) = 120 kHz Lumi = 0.8*10**30 cm-2s-1 2) t70- some intermediate point (near 70 min from t0): Ie+= 8.3mA, Ip=43.7 mA PD Total Rate (TTL scaler, 221st word of LRTL) = 70 kHz PD Total Rate (Sum of 220 PD bunch trigger rates) = 82 kHz Lumi = 0.7*10**30 cm-2s-1 3) t160-end of H1Run 83298 (near 160 min after t0): Ie+= 6.4mA, Ip=43.6 mA PD Total Rate (TTL scaler, 221st word of LRTL) = 50 kHz PD Total Rate (Sum of 220 PD bunch trigger rates) = 58 kHz Lumi = 0.5*10**30 cm-2s-1 Vectors with PD-total rates behaivours with time are kept at the LOOK-binary data sets at DESY IBM: H1KFOM.LOOK.R83294 (30000th vector) FAST05 3010200E 00000 DASD H1KFOM.LOOKA.R83294 (3000th vector) FAST02 3010200E 00000 DASD As seems this difference (near 10 percents) is not understandable. And it is not understandable which from this two digits is right. Only Egor can put some clearity on this question (as seems). 10.08.1994 ==================== F11LEV === Lumi cross check ........ In one of the previous messages (28/07) it was stated, that: "Gamma spectra used showed a global shift > 0, in spite of LUMIMON events were re-reconstructed with latest calibration from DB. and shift was found to be different for VC and PD samples. Run period Online lumi VC-method PD-method 79913-82005 298 nb-1 326 nb-1 345 nb-1 E-shift 2.4+-0.6% 1.3+-0.5%" This is understood, as not fully correct calibration of VC. In average, CC(veto) in database is ~10% higher than it should be. After taking this into account, it was found no energy shift in E-gamma spectra for both s91 and s93 samples (and also subsample of events with E(veto)<0.3 GeV is OK). However, there is still ~8% difference in "offline" luminosity estimated from s91 and s93. The difference between online and offline becomes smaller: Run period Online lumi VC-method PD-method 79913-82005 298 nb-1 300 nb-1 325 nb-1 E-shift 0.2+-0.6% -0.4+-0.5% P.S. (S.L., 11/08) This is an example how important to cross check each other in our lumi business. Even trivial bugs are always possible, if no cross check is made. Trying to understand, why the difference between "offline" lumi values from 28/7 and 10/8 is so large (326,345 vs 300,325) it was found (thanks to Nelly) that the treatment of E-shift values at 28/07 was wrong. In order to get luminosity from the total number of VC or PD events, one has to divide it by the cross section sigma B-H for E_gamma>E_min (E_min=16 GeV was used in this case): NEV (E>16GeV) L = ---------------- sigma(E>16GeV) And in this moment one has to take into account a possible E-scale shift correctly (E_true=E_hist/E_shift). I did it wrongly and calculated sigma B-H for E>16*E_shift instead of E>16/E_shift. If one corrects for this trivial bug, then the results from 28/7 and 10/8 become consistent: Analysis date Online lumi VC-method PD-method 28/07 298 nb-1 299 nb-1 330 nb-1 10/08 298 nb-1 300 nb-1 325 nb-1 Sorry for misleading due to this bug. (S.L.) P.P.S. Note, that main question - why VC- and PD_low samples gave so much different results - still remains unclear. It is more or less evident, however, that PD-data are correct and VC is wrong (8-10% less). This conclusion comes from our present iunderstanding of online ET*PD method after several scans made by Brinkmann. (S.L.) 10.08.1994 ===== dice2 ======== H1KFOM === R(ET*PD)/R(PD) for scan 100003rd vector was built with proposed by S.Levonyan ratio behaivour with time for first two scans (09.08.94 - from 06:01 and from 13:08). Vector is kept at the next LOOK binary data set: H1KFOM.LOOK.R84022 FAST08 3010200E 00000 DASD T0 at this vector is start of Run 84022. Scan exercises are fixed near t0+12 and near t0+430 min. Really it is seen 'jumps' into low values during scan.. 11.08.1994 ==================== F11LEV === Lumi cross check ........ After some thoughts and consultation with Igor Sheviakov, the only (preliminary) conclusion/explanation of the difference between VC- and PD-samples "offline lumi" is the timing of VC trigger. 1) According to Igor, in a few (may be up to 10) % of all cases VC-trigger bit can stay for more than one bunch crossing and thus appear in the next (wrong) BC. 2) This would mean, that in S91 sample (triggered by PD_low) there should be few (up to 10) % of events which have VC-bit = 1 wrongly, because in fact it should be in previous BC. 3) This in turn means, that VC efficiency defined from PD-sample is overestimated by those few %: eff(VC) = N(s91;VC=1)/N(s91) where in the nominator there are few % of extra events with VC=1. 4) Thus, true number of VC events from S93 sample is underestimated: N(VC_true)=N(s93)/eff(VC), and this leads to smaller value of the "offline" LUMI estimated from S93 (VC)-sample Conclusions. o If all this is true (or close to the reality), then only PD-triggered sample must be used for a single-gamma rate method of lumi definition. o Also, VC-bit efficiency cannot be correctly obtained without this timing problem consideration. o VC-triggered sample is still a good source of unbiased events for various acceptance/efficiency determination for ET and PD. o Finally, as far as I remember, in 1993, the VC-timing was better, so for 1993 the use of VC-sample was OK (and also that time we had no alternatives) And thus, a correct "offline" integrated luminosity is 328+-5 nb-1 where an error given includes only E-scale precision. And we can also conclude that our 1994 online LUMI in e-p mode was low by ~9%: (328-298)/328 = 9.1% , or to arrive to correct lumi we have to multiply our online value by ~1.1 (10%): 328/298 = 1.10 11/8/94 ======================= i01fwb === Lumi RUN# 523 Start lumi run523 date: 11/8/94 Collision time: 2:16:01 - 2:44:50 Currents (mkA): Ie= 32475.00, Ip= 54500.00 Peak luminosity: 0 mb-1 s-1 Peak spec.lumi : 0 mb-1 s-1 mA-2 Number of collided b.: 0 Number of e-filled b.: 0 Number of p-filled b.: 0 Number of e-pilot b.: 0 Number of p-pilot b.: 0 HERA total lumi: 1678.536 mkb-1 H1 Run total lumi: 1607.745615 mkb-1 H1 data taken lumi: 1577.210849 mkb-1 H1 Runs: 84193 - 84193 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 84193 - 84193 Tot curr/rate factor: 7.39% C/R F H1Run gated: 7.68% Rand.C.F: 8.01% RCF Run gated: 6.18% Relative ET trigg accept.: Not calc. 11.08.1994 ==================== F11LEV === re:Problems with PD-rates In the same spirit as VC-timing problem, one can look on the discrepancy of the order of 10% between total PD-rate and summed PD-rate over all bunches, reported yesterday by Andreev and Fomenko. Namely, if for this run (or always?) some small (10%) fraction of PD-triggers can stay for longer than one BC (overlap to the next BC) then those events may give 2 entries to the bunch rates, but only one entry to the total rate. And thus, total rate should always be by few % less than the summed bunch rate. The question to Igor: could it happen, or not? I.e. how the hardware (bunch rate scalers) are built: could a signal from one photon in princilpe give triggers for more than one BC? 11.08.94 ====================== H1KSOL === ET acceptance..... Here are the results of measurements made by Brinkmann on Monday on 8.08.94 at about 13.00: P.S. As seems - on Tuesday 09.08.94 near 13:00(see earlier) (a.f.) Tilt's value was -0.15 mrad diring whole measurements. XOFF value is refered to one been measured by dump magnet. XOFF(mm) L_sp(H1) R(%) -0.86 4.25 e29 3.5 +0.13 3.4 e29 20 -1.36 4.4 e29 0 -1.86 4.3 e29 2.3 All points were also checked from the ET*PD/PD rates ratio got from Fomenko's LOOK file,and it turned out that actual value of ET acceptance change at point +0.13 is 12% but not 20%. One can find the results in LOOK session by executing 'H1KSOL.MCETAC.MACRO' and issuing command 'fig2' which shows the MC data and measurement's data. One can see that MC data and measurements are in agreement if one assumes that XOFF mesurements by dump magnets has offset 1.5-1.8mm to '-' region,that could be because according to Brinlmann the uncertanty of the measurements is +-1mm(sigma) and the real reference orbit does not coincide with MC due to the fact that accuracy of magnet elements installation is of order 0.1-0.3 mm (Brinkmann). Concerning the rumors that a lot of scans were made during recent time I can only refer to Brinkmann statement made on the HERA meeting at 2.08.94 that he dont intend to make more scan measurements because this item is clear for him and hence is closed(ausgeschlossen 11.08.94 ====================== H1KSOL === To Lumi cross check.... "3) This in turn means, that VC efficiency defined from PD-sample is overestimated by those few %: eff(VC) = N(s91;VC=1)/N(s91) where in the nominator there are few % of extra events with VC=1" N(s91) = N(s91;VC=1)+N(s91;VC=0),and N(s91;VC=0) is much smaller ca. 10-15%, than N(s91;VC=1).So where are those few %?. P.S. (by S.L.): N(s91;VC=1) contains some (up to 10)% fraction of events, in which VC should be =0, but because of the timing problem they "migrated" to the same BC as s91 (PD_low) triggers. So these are "false" VC=1 events. Thus a number of "true" VC=1 events should be by (up to 10%) less. 12/8/94 ==================== Lebedev A === Lumi RUN# 524 Start lumi run524 date: 11/8/94 Collision time: 23:55:23 - 6:26:33 Currents (mkA): Ie= 29367.00, Ip= 52301.00 Peak luminosity: 3516.497 mb-1 s-1 Peak spec.lumi : 424.136646 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 49809.7803 mkb-1 H1 Run total lumi: 81493.4639 mkb-1 <---jump in Lumi by 39.8nb-1 H1 data taken lumi: 40110.8372 mkb-1 <---jump in Lumi by 11 nb-1 H1 Runs: 84251 - 84289 HERA - physics: 48977.523535 mkb-1 H1Run - physics: 34929.7746 mkb-1 H1data - physics: 24577.0011 mkb-1 H1 Runs: 84254 - 84289 Tot curr/rate factor: 0.6% C/R F H1Run gated: 0.62% Rand.C.F: 2.15% RCF Run gated: 2.02% Relative ET trigg accept.: 0.3555 PS(lns): L4, L5 histos are OK. PS(lns): a Good(?) Warning: Lumi_ET+PD+VC_sigma is ~1.5 times better! 12.08.94 ====================== H1KSOL === Jumps in Lumi....... During ep Run#525 two jumps in h1gated and h1datataken lumi were observed at 9.05 : H1gated by 0.8nb-1,h1datataken by 1.4nb-1, at the same time in HERA produced value was drop by 0.1nb-1. At that time was smooth H1 data taking,no correlations with any actions. The only one correlation - at 9.05 H1Lumi2MAC hanged up and was reboted by me 10 min later. 12.08.1994 ===== dice2 ======== H1KFOM === Set of Vectors for # 522 100003rd vector was built with proposed by S.Levonyan ratio behaivour with time for last 'scan' (10.08.94 - from 00:52) during Lumi RUN# 522. Vector is kept at the next LOOK binary data set: H1KFOM.LOOK.R84046 FAST14 3010200E 00000 DASD T0 at this vector is start of Run 84046. 'Scan' exercises are fixed near t0+360 min. Really it is seen 'jumps' into low values during 'scan'. There are a lot of useful vectors with H1Lumi Trigger bits and Trigger elements Rates behaivour during more then 10 hours at Lumi RUN#522: (20000-VC,30000-PD,40000-ET,50000-PD1(PD-Low),60000-PD2,70000-ET&PD, 80000-ET&PD&nVC,90000-PD&nVC,100000-eTAG). It is seen that RateVC was changed from 1.0MHz-->130kHz RatePD was changed from 225kHz--> 26kHz RateET was changed from 150kHz--> 20kHz RatePD1 was changed from 320kHz--> 45kHz RatePD2 was changed from 90kHz--> 14kHz RateET&PD was changed from 90kHz--> 14kHz Rate(eTAG) was changed from 50kHz--> 9kHz Some usefull vectors produced from LRTL-bank contents are kept at the next data set: H1KFOM.LOOKA.R84046 FAST05 3010200E 00000 DASD 803,805th - behaivours of and (rough) with time especially it is interesting around t0+340 - t0+400 min 903 - Current Luminosity value behaivour with time 3000 - Total ET&PD Rate (TTL-counter) behaivour with time - there are no siginificant difference between vector 70000 from previous data set - so the same counts at TTL and at HistoMemory; 1501,4501 - vectors with Ie total and Ip total behaivours with time. 12.08.1994 ===== dice2 ======== H1KFOM === Selected H1Lumi Monitrig.. Today it were selected calibration data samples from the next data sets which were produced with standard job prepared by S.Levonyan at dice1-environment: HERA03.H01.LUMIMON.C9400063 K44202 78048081 00001 ACS-E-C ...... HERA03.H01.LUMIMON.C9400065 K21698 78048081 00001 ACS-E-C It were selected events with (s92=1 only),with ET&PD&VC=1 and with ET&PD&nVC from these data sets (as ordinary) and combined with events which were selected at 09.08.94 (48-62 LUMIMONs): 1) S92=1 only 37782 events ( 59.6 MBytes) 2) ET&PD&VC 126438 events (209.6 MBytes) 3) ET&PD&nVC 60399 events (100.3 MBytes) Created data sets were saved at DESY IBM storage at the next data sets H1KFOM.ETPDNVC.M4865.C00 K19738 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M4865.C00 K40603 78048081 00001 ACS-E-C H1KFOM.S92.M4865.C00 K19213 78048081 00001 ACS-E-C These data include events from Lumi RUNs# 503(A)-524 (H1 Runs 83004- 84287). 12/8/94 ======================= i01fwb === Lumi RUN# 525 Start lumi run525 date: 12/8/94 Collision time: 7:48:30 - 16:09:43 Currents (mkA): Ie= 29100.00, Ip= 48500.00 Peak luminosity: 2540.101 mb-1 s-1 Peak spec.lumi : 356.073068 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 42749.270146 mkb-1 H1 Run total lumi: 34516.1775 mkb-1 H1 data taken lumi: 26505.8973 mkb-1 H1 Runs: 84291 - 84309 HERA - physics: 39508.081158 mkb-1 H1Run - physics: 29931.0889 mkb-1 H1data - physics: 22165.399 mkb-1 H1 Runs: 84293 - 84309 Tot curr/rate factor: 1.12% C/R F H1Run gated: 1.17% Rand.C.F: 1.76% RCF Run gated: 1.84% Relative ET trigg accept.: 0.3275 PS(lns): L4, L5 histos are OK. PS(lns): Lumi_ET+PD+VC_sigma is back, ~ 1.3 GeV, as usially. PS(lns): Have been noticed: Etag is "better" = "Background" much lower. PS(lns): Have been noticed: Edep-Etrig for ET is ~ 1.5GeV inst.of.~ 0. 13/8/94 ======================= Valkar === Lumi RUN# 526 Start lumi run526 date: 13/8/94 Collision time: 1:00:40 - 2:11:56 Currents (mkA): Ie= 27400.00, Ip= 50100.00 Peak luminosity: 3375.169 mb-1 s-1 Peak spec.lumi : 465.454459 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 11934.5885 mkb-1 H1 Run total lumi: 62661.971967 mkb-1 <----jump 52nb-1 H1 data taken lumi: 59061.76654 mkb-1 <-----jump 52nb-1 H1 Runs: 84335 - 84338 HERA - physics: 11732.050749 mkb-1 H1Run - physics: 2957.001796 mkb-1 H1data - physics: 1191.323557 mkb-1 H1 Runs: 84337 - 84338 Tot curr/rate factor: 1.71% C/R F H1Run gated: 1.51% Rand.C.F: 3.67% RCF Run gated: 3.36% Relative ET trigg accept.: 0.3714 13/8/94 ======================= h1kleb === Lumi RUN# 527 Start lumi run527 date: 13/8/94 Collision time: 10:59:41 - 11:48:29 Currents (mkA): Ie= 26510.00, Ip= 49301.00 Peak luminosity: 3302.108 mb-1 s-1 Peak spec.lumi : 506.946568 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 6853.477393 mkb-1 H1 Run total lumi: 6129.3681 mkb-1 H1 data taken lumi: 5109.3112 mkb-1 H1 Runs: 84366 - 84368 HERA - physics: 3802.283486 mkb-1 H1Run - physics: 1637.359393 mkb-1 H1data - physics: 843.179111 mkb-1 H1 Runs: 84367 - 84368 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 3.38% RCF Run gated: 3.56% Relative ET trigg accept.: 0.3618 13/8/94 ======================= i01fwb === Lumi RUN# 528 Start lumi run528 date: 13/8/94 Collision time: 13:22:38 - 21:40:03 Currents (mkA): Ie= 25902.00, Ip= 49200.00 Peak luminosity: 2941.744 mb-1 s-1 Peak spec.lumi : 454.895266 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 52006.246966 mkb-1 H1 Run total lumi: 45138.673278 mkb-1 H1 data taken lumi: 37631.244752 mkb-1 H1 Runs: 84372 - 84390 HERA - physics: 47604.332292 mkb-1 H1Run - physics: 42520.094178 mkb-1 H1data - physics: 35364.459252 mkb-1 H1 Runs: -1 - 84390 Tot curr/rate factor: 1.28% C/R F H1Run gated: 1.21% Rand.C.F: 1.29% RCF Run gated: 1.2% Relative ET trigg accept.: 0.3562 PS(lns): L4, L5 histos are OK. PS(lns): Lumi_ET+PD+VC_sigma is back, ~ 1.3 GeV, as usially. PS(lns): Have been noticed: Etag is "better" = "Background" much lower. PS(lns): Have been noticed: Edep-Etrig for ET is ~ 1.5GeV inst.of.~ 0. 14/8/94 ======================= i01fwb === Lumi RUN# 529 Start lumi run529 date: 13/8/94 Collision time: 22:45:40 - 1:03:00 Currents (mkA): Ie= 28349.00, Ip= 47800.00 Peak luminosity: 1209.277 mb-1 s-1 Peak spec.lumi : 209.793244 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 13311.593846 mkb-1 H1 Run total lumi: 8759.7213 mkb-1 H1 data taken lumi: 6890.5806 mkb-1 H1 Runs: 84393 - 84400 HERA - physics: 9720.593319 mkb-1 H1Run - physics: 5353.597124 mkb-1 H1data - physics: 3691.071885 mkb-1 H1 Runs: 84397 - 84400 Tot curr/rate factor: 0.57% C/R F H1Run gated: 0.52% Rand.C.F: 2.18% RCF Run gated: 2.17% Relative ET trigg accept.: 0.3477 14/8/94 ======================= i04rie === Lumi RUN# 530 Start lumi run530 date: 14/8/94 Collision time: 2:35:47 - 3:51:36 Currents (mkA): Ie= 28282.00, Ip= 42000.00 Peak luminosity: 2050.391 mb-1 s-1 Peak spec.lumi : 347.499514 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 8164.511505 mkb-1 H1 Run total lumi: 8048.5089 mkb-1 H1 data taken lumi: 6856.2451 mkb-1 H1 Runs: 84403 - 84406 HERA - physics: 5325.99168 mkb-1 H1Run - physics: 3900.913231 mkb-1 H1data - physics: 2825.558939 mkb-1 H1 Runs: 84404 - 84406 Tot curr/rate factor: 1.46% C/R F H1Run gated: 1.47% Rand.C.F: 2.72% RCF Run gated: 2.72% Relative ET trigg accept.: 0.3581 PS(lns): L4, L5 histos are OK. 14/8/94 ======================= i04rie === Lumi RUN# 531 Start lumi run531 date: 14/8/94 Collision time: 5:01:14 - 5:05:42 Currents (mkA): Ie= 28233.00, Ip= 41400.00 Peak luminosity: 0 mb-1 s-1 Peak spec.lumi : 0 mb-1 s-1 mA-2 Number of collided b.: 0 Number of e-filled b.: 0 Number of p-filled b.: 170 Number of e-pilot b.: 0 Number of p-pilot b.: 170 HERA total lumi: 21.949618 mkb-1 H1 Run total lumi: 21.949618 mkb-1 H1 data taken lumi: 21.515374 mkb-1 H1 Runs: 84406 - 84406 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 84406 - 84406 Tot curr/rate factor: 4.58% C/R F H1Run gated: 4.58% Rand.C.F: 10.01% RCF Run gated: 10.01% Relative ET trigg accept.: Not calc. 14.08.1994 ==================== H1KSOL === H1TCL data....... H1TCL carts C9400046-57 were processed and LOOK files are under name 'H1KSOL.RLOOK.CARTXX' where XX = 46-57. Job output files are on dice2 in dir /home/soloviev/lumi/lumi94 with name tcl0XX.out. 14/8/94 ======================= h1kleb === Lumi RUN# 532 Start lumi run532 date: 14/8/94 Collision time: 16:46:06 - 18:56:58 Currents (mkA): Ie= 29700.00, Ip= 45500.00 Peak luminosity: 2894.864 mb-1 s-1 Peak spec.lumi : 419.295328 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 18558.5436 mkb-1 H1 Run total lumi: 13427.5554 mkb-1 H1 data taken lumi: 9597.3993 mkb-1 H1 Runs: 84434 - 84448 HERA - physics: 15853.875277 mkb-1 H1Run - physics: 10172.8051 mkb-1 H1data - physics: 6436.6276 mkb-1 H1 Runs: -1 - 84448 Tot curr/rate factor: 1.64% C/R F H1Run gated: 1.82% Rand.C.F: 3% RCF Run gated: 3.3% Relative ET trigg accept.: 0.3443 PS(lns): L4, L5 histos are OK. 15.08.1994 ===== dice2 ======== H1KFOM === Lumi=3.6*10**30 cm-2s-1... As it was seen earlier from H1Lumi Run Summary during Lumi RUN# 524 it was fixed new record value of Current Luminosity. Today it was possible to check contents of LRTL- and LUMM-banks from this Lumi RUN (H1Runs 84251 etc.). It were produced 2 LOOK binary data sets with vectors which keep behaivour of different useful variables with time (for more then 460 min with t0=22:31:47 11.08.94): H1KFOM.LOOKA.R84251 FAST19 3010200E 00000 DASD From vector 903 it is possible to see that at 00:09 12.08.94 it was fixed Current Luminosity value near 3.6*10**30 cm-2s-1. Time slice of different parameters at 00:09 12.08.94: Ie+total = 29 mA Ee= 27.520 GeV Ip total = 51.8 mA Ep=819.920 GeV = -0.75cm VC total rate =2200 kHz = +0.4 cm PD total rate = 480 kHz ET total rate = 230 kHz PD1total rate = 630 kHz PD2 otal rate = 160 kHz ET&PD total rate = 155 kHz ET&PD&nVC total rate= 20 kHz PD&nVC total rate = 60 kHz eTAG total rate = 49 kHz It is possible to see all high mentioned H1Lumi Trigger elements and bits rates from 20000,30000,40000,....,100000th vectors at time slice 97 min at the next LOOK-binary data set: H1KFOM.LOOK.R84251 FAST12 3010200E 00000 DASD OnLine Calibration Coefficients were changed with next manner (at start of Lumi RUN): e21=-2%; e22=+10%; e23=+9%; e24=-5%; e25=-5%; e26=-5%; e27=-20%. p10=-7%; p11=-31%; p12=-14%; p13=-17%; p14=-4%. 15.08.1994 ===== dice2 ======== H1KFOM === New Length of LUMIMON Today it was found that 67th LUMIMON-data set have length not 100 Mb but 200Mbyte. HERA03.H01.LUMIMON.C9400067 200055240 Aug 15 11:15 16/8/94 ======================= h1kleb === Lumi RUN# 533 Start lumi run533 date: 15/8/94 Collision time: 19:48:25 - 7:05:44 Currents (mkA): Ie= 19638.00, Ip= 54000.00 Peak luminosity: 2699.058 mb-1 s-1 Peak spec.lumi : 496.437005 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 60670.396199 mkb-1 H1 Run total lumi: 55881.6864 mkb-1 H1 data taken lumi: 50386.75 mkb-1 H1 Runs: 84573 - 84590 HERA - physics: 57033.33445 mkb-1 H1Run - physics: 50037.095 mkb-1 H1data - physics: 44609.1952 mkb-1 H1 Runs: -1 - 84590 Tot curr/rate factor: 0.83% C/R F H1Run gated: 0.84% Rand.C.F: 0.89% RCF Run gated: 0.89% Relative ET trigg accept.: 0.3371 PS(lns): L4, L5 histos are OK. 16/8/94 ===================== riepenha === Lumi RUN# 534 Start lumi run534 date: 16/8/94 Collision time: 8:28:21 - 9:54:26 Currents (mkA): Ie= 21124.00, Ip= 50400.00 Peak luminosity: 1644.563 mb-1 s-1 Peak spec.lumi : 297.573364 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 7242.9991 mkb-1 H1 Run total lumi: 5791.0402 mkb-1 H1 data taken lumi: 5169.0593 mkb-1 H1 Runs: 84593 - 84598 HERA - physics: 5898.880275 mkb-1 H1Run - physics: 3883.099846 mkb-1 H1data - physics: 3295.061136 mkb-1 H1 Runs: 84594 - 84598 Tot curr/rate factor: 1.33% C/R F H1Run gated: 1.44% Rand.C.F: 1.49% RCF Run gated: 1.52% Relative ET trigg accept.: 0.3399 PS(lns): L4, L5 histos are OK. 16/8/94 ======================= h01pie === Lumi RUN# 535 Start lumi run535 date: 16/8/94 Collision time: 15:30:39 - 20:08:23 Currents (mkA): Ie= 30212.00, Ip= 52600.00 Peak luminosity: 4319.576 mb-1 s-1 Peak spec.lumi : 520.319257 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 50858.431602 mkb-1 H1 Run total lumi: 48129.7395 mkb-1 H1 data taken lumi: 35976.8209 mkb-1 H1 Runs: 84616 - 84630 HERA - physics: 46574.790695 mkb-1 H1Run - physics: 39110.404004 mkb-1 H1data - physics: 30235.710549 mkb-1 H1 Runs: 84620 - 84630 Tot curr/rate factor: 1.42% C/R F H1Run gated: 1.42% Rand.C.F: 2.31% RCF Run gated: 2.29% Relative ET trigg accept.: 0.3533 PS(lns): L4, L5 histos are OK. 17.08.1994 ===== dice2 ======== H1KFOM === Selected H1Lumi Monitrig.. Today it were selected calibration data samples from the next data sets which were produced with standard job prepared by S.Levonyan at dice1-environment: HERA03.H01.LUMIMON.C9400066 K20082 78048081 00001 ACS-E-C ...... HERA03.H01.LUMIMON.C9400068 K21957 78048081 00001 ACS-E-C It were selected events with (s92=1 only),with ET&PD&VC=1 and with ET&PD&nVC from these data sets (as ordinary) and combined with events which were selected at 12.08.94 (48-68 LUMIMONs): 1) S92=1 only 48598 events ( 76.7 MBytes) 2) ET&PD&VC 155600 events (257.5 MBytes) 3) ET&PD&nVC 75203 events (124.9 MBytes) Created data sets were saved at DESY IBM storage at the next data sets H1KFOM.ETPDNVC.M4868.C00 K30155 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M4868.C00 K30174 78048081 00001 ACS-E-C H1KFOM.S92.M4868.C00 K30239 78048081 00001 ACS-E-C These data include events from Lumi RUNs# 503(A)-533 (H1 Runs 83004- 84585). P.S. first calibration attempt shows that at Lumi RUN#521 (H1Run84025) it was fixed again jump at CCp11 so first subsamples for e+p calibration will include events from H1Runs 83004 up to 84024 (for G and M H1Runs there are 25510 ET&PD&nVC at this first subsample). 17.08.1994 ===== dice2 ======== H1KFOM === Lumi=4.3*10**30cm-2s-1. It was produced LOOK-binary file with set of vectors for first 30 min. of Lumi RUN# 535 at which new record Luminosity was achieved. Data set name is: H1KFOM.LOOKA.R84616 FAST02 3010200E 00000 DASD t0 at all vectors is 15:32:28 16.08.94. During almost 20 first min. of high mentioned Lumi RUN Current Luminosity value was fixed near 4.3-4.2*10**30 cm-2s-1 (vector 903). At start of Lumi RUN# 535 it was fixed ET&PD total near 194 kHz(vector 3000). = -1.6 cm --> -1.4 cm (802nd, 803rd vectors) = +0.6 cm --> +0.4 cm (804th, 805th vectors) Ie+ total = 30.1 mA --> 27.8 mA (1501st vector) Ip total = 51.82 mA --> 51.78 mA (4501st vector) It was produced LOOK-binary data set with LUMM-bank parameters: H1KFOM.LOOK.R84616 FAST03 3010200E 00000 DASD The next Rates were fixed at H1Lumi Trigger Elements and Bits at first 30 min. of Lumi RUN# 535 (vectors 20000,30000,...,100000): RateVC = 2450-->2000 kHz RatePD = 520--> 410 kHz RateET = 300--> 225 kHz RatePD1= 740--> 570 kHz RatePD2= 196--> 150 kHz RateET&PD = 196--> 157 kHz RateET&PD&nVC = 22--> 20 kHz RatePD&nVC = 63--> 57 kHz Rate(eTAG) = 73--> 52 kHz The next Calibration Coefficients changings during first 30 min. of this Lumi RUN were fixed (vectors 6026,6011-6015,5022-5028); CCvc = -6%; CCp10 = -3%, CCp11 = -19%, CCp12 =-7%, CCp13 =+5%, CCp14 = 0% CCe21 = -2%, CCe22 = -6%, CCe23 =+4%, CCe24 =-3%, CCe25 =-7%, CCe26 = -4%, CCe27 = -2%. 17.08.1994 ==================== H1KSOL === TCL cart............... I removed RLOOK.CARTxx files from my directory,because one can find them in H01GOG directory. 18.08.1994 === H1KAND == Integrated Luminosity from LUMM bank ===== The first attempt to estimate the integrated luminosity by the photon arm method was made. The PD1, PD and PD2 trigger rates from LUMM bank were used for this purpose. And values of the energy thresholds for these triggers were estimated by using S93 sample (from LUMIMON cartridge ) and suitable callibration coefficients. 1) Integrated luminosity for the positron beam: H1 runs 82961-84025 (only G and M runs were used). LRTL-bank LUMM-bank ET*PD ET*PD PD1 PD PD2 153 nb-1 154 nb-1 188 nb-1 176 nb-1 153 nb-1 "ov. corr." - - ? 153 nb-1 ? As we understand now there is additional source to the trigger rate from the "overlapping trigger" (see S.L. 11.08.94 ). During 83295-83298 H1 runs (~ 4 nb-1) the online luminosity was measured by photon arm method with PD trigger and for these runs the "overlapping correction" to the integrated luminosity is ~ 13 %. And it is almost obviosly (?!) that this correction to the PD2 trigger must be small. Conclusion: the ET*PD, PD and PD2 method are given the agreement results for the positron opperation. 2) Come back to the electron beam . The same procedure was made for the H1 runs 79913-82005 with electron beam (G and M runs were considered) and it were obtained the next values for the integrated luminosity: LRTL-bank LUMM-bank ET*PD ET*PD PD1 PD PD2 294 nb-1 294 nb-1 377 nb-1 352 nb-1 325 nb-1 "ov. corr." - - 328 nb-1 ? ? As one remember that value of the PD1 threshold was ~ 4 GeV (almost during all considered runs) and it is equal ~ the value PD threshold for the positron opperation. Then the "overlapping correction" for the PD1 trigger ~ 13 %. As the result we have the agreement integrated luminosity estimations by PD1 and PD2 triggers but ET*PD method is underestimated ~ 11 % (325/294=1.11) for the electron beam opperation. Conclusion: o the photon arm method cannot be used for the online luminosity measurement at this moment, o for the offline luminosity calculation it is necessary to take into account the "overlapping correction" (how to do this now more correct?) 19.08.1994 ===== dice2 ======== H1KFOM === Relation Coeff.Set 5A Today it was made Relation Coefficient defining for data sample 5A - data from H1Runs 83004-84024 (first data with e+p collisions from Lumi RUN# 503(A) up to Lumi RUN# 521 - before large jump at CCp11 value at H1 Run 84025). "Jump_p11"-value is -50% into low direction (RC jump was fixed on 100% into high direction - from value near 1. into 2.0 region). a) it were excluded data from P-marked H1 Runs (see H1EP) and non- -marked with any P or M or G letters. After all high mentioned 'cleaning' of 5A-data samples it were collected: 25510 events with ET&PD&nVC trigger 51594 events with ET&PD&VC trigger 17428 events with S92-trigger (PD&nVC-events). It were got 25510 ET&PD&nVC from these Runs and it were used for calibration 17177 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 1.100 1.125 1.006 1.160 1.139 1.406 1.098 0.915 1.047 0.969 1.552 0.821 1.011 1.030 1.045 0.945 0.952 0.920 1.029 0.626 0.983 1.032 1.018 1.005 1.009 1.032 1.005 1.040 1.053 1.011 0.964 0.939 0.973 1.055 1.098 0.906 0.897 1.110 1.026 0.989 0.932 0.000 0.866 1.075 0.835 0.848 0.926 1.048 0.000 ==> Relation Coeff.Set for PD 2.153 0.980 1.100 1.546 0.961 1.006 0.966 1.041 0.997 0.968 0.948 1.034 1.008 1.022 1.005 1.022 0.982 1.005 0.991 0.955 1.686 0.986 1.066 0.997 0.919 ==> Sig. at Relation Coeff.Set for ET 0.001 0.042 0.012 0.022 0.012 0.042 0.018 0.022 0.027 0.028 0.031 0.012 0.013 0.024 0.017 0.051 0.034 0.012 0.020 0.031 0.025 0.014 0.019 0.020 0.022 0.029 0.034 0.022 0.015 0.027 0.028 0.028 0.021 0.029 0.052 0.004 0.031 0.023 0.024 0.018 0.003 0.000 0.000 0.004 0.001 0.005 0.005 0.000 0.000 ==> Sig. at Relation Coeff.Set for PD 0.004 0.024 0.016 0.003 0.001 0.019 0.024 0.023 0.013 0.013 0.024 0.028 0.017 0.036 0.017 0.035 0.030 0.029 0.038 0.018 0.034 0.021 0.027 0.024 0.001 ==> Ent. at Relation Coeff.Set for ET 6 16 4 7 24 26 6 13 47 59 60 31 26 16 635 708 739 606 592 248 187 5413 8848 6821 4618 3010 1796 641 2052 1928 1265 646 349 173 96 11 7 7 5 5 2 0 1 5 3 2 2 2 0 ==> Ent. at Relation Coeff.Set for PD 17 10 14 16 2 209 1318 2289 728 44 2047 9596 12936 5687 625 641 3656 4806 2047 163 29 36 55 24 3 As You can see all sigma values for 'hot' H1Lumi cahnnels RC histos have more or less reasonable values (may be p13,e25,e15,e16 are more then ordinary). Runs 83004- 84024 (ET&PD&nVC-sample - near 25.5K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.46 0.97 27.48 0.94 27.53 0.92 Runs 83004- 84024 (ET&PD&VC-sample - near 51.5K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.01 1.26 27.02 1.21 Sigma values (especially for ET&PD&nVC events) are more on near 10% (this fact was seen at OnLine histos too). Incident is Incident. Something happened. It were used as start values of CC for Photoproduction branch ones which were produced after 3rd step of calibration with 4B sample of (Runs81701-81977) and CCvcs as 2.551. (from H1KFOM's 28.07.94 message at LLC). 19.08.1994 ===== dice2 ======== H1KFOM === PDREC-spectra for 5A Today it were produced 100th ntuple for S92=1 events from earlier mentioned 5A sample with events from Runs 83004-84024: H1KFOM.YLOOKQ4.R83004 (14101 entries) FAST08 3010200E 00000 DASD At interactive LOOK-session it was produced 70th histo for this data set and written into the next LOOK-binary data set: H1KFOM.BLOOKQ2.R83004 12383 entries in 70h FAST13 3010200E 00000 DASD First attempt to fit 70th histo at BLOOKQ2-data set put positive sign of Global Energy Shift at Photon Arm (+0.4%) and enough good resolution digits (14%). It were prepared 100th tuples with ET&PD&nVC and ET&PD&VC-events for procedure of defining Global Energy Shifts and CCvcs: H1KFOM.YLOOKQ2.R83004 25367 entries FAST04 3010200E 00000 DASD H1KFOM.YLOOKQ3.R83004 49406 entries FAST13 3010200E 00000 DASD 19.08.1994 ==================== H1KFOM === Global Shifts,CCvcs 5A It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 1.0 for PD Channels (exept VCs), 1.0 for ET channels. Correction factor for CCvcs is 1.25. So CCvcs = 2.551*1.2500=3.189Mev FADCcount. These digits are valid for H1Lumi events from Run 83004 up to 84024 Runs 83004- 84024(ET&PD&nVC-sample - near 25K events) xetcut&vcdepcut Step Mean Sigma 0 27.53 0.92 Runs 83004- 84024 (ET&PD&VC-sample - near 51.5K events) xetcut Step Mean Sigma 0 27.52 1.25 19.08.1994 ==================== H1KFOM === New RC Sets in H1DataBase As final action of all today calibration steps it was made update of LFRC and LESC banks at H1DataBase with S.Levonyan's tool. All Relation Coefficients values, CCvcs and Global Energy Shift constants were got from the next messages at LLO: 19.08.1994 ----- dice2 -------- H1KFOM --- Relation Coeff.Set 5A 19.08.1994 -------------------- H1KFOM --- Global Shifts,CCvcs 5A Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LFRC (_501) 33 e-p data 408191139 83004 0 77 940819 H1KFOM Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LESC (_582) 42 e-p data 408191139 83004 0 3 940819 H1KFOM 19/8/94 ======================= janoth === Lumi RUN# 536 Start lumi run536 date: 18/8/94 Collision time: 23:13:57 - 2:04:04 Currents (mkA): Ie= 29200.00, Ip= 49200.00 Peak luminosity: 2598.435 mb-1 s-1 Peak spec.lumi : 496.047083 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 19384.086341 mkb-1 H1 Run total lumi: 18314.268688 mkb-1 H1 data taken lumi: 15231.714243 mkb-1 H1 Runs: 84818 - 84827 HERA - physics: 15908.123404 mkb-1 H1Run - physics: 14275.888932 mkb-1 H1data - physics: 11276.290952 mkb-1 H1 Runs: 84819 - 84827 Tot curr/rate factor: 0.92% C/R F H1Run gated: 0.94% Rand.C.F: 1.65% RCF Run gated: 1.67% Relative ET trigg accept.: 0.3419 PS(lns): L4, L5 histos are OK. 20.08.1994 ==================== H1KSOL === LRTL bank missing........ This morning I found that LRTL LREC LRPC banks were not created in Lumi branch during ep Run #537.Shift crew can not note it because data logging was on Storage TEK. During e+injection there was a warning "BOS structure (LRTL)" at 5.47,and due to that I suspect that there were no LRTL bank since beginning of Lumi - H1Run 84891 till 84926.After rebooting FIC1 all OK - since H1Run 84927. And there was NAN in HERA produced again. 20.08.1994 ==================== H1KSOL === NAN in HERA produced..... At 11.18 NAN in HERA prod. appeared - in B0A5E12C. It was not succesful Run start due to the "Timeout STC Central,Forward, and mu DC". This situation repeated several (3-4) times with the same messages on supervisor and NAN in HERA prod.(after every NAN I corrected it but got again after not succesfull Run start). On the other hand farm does not work at all,and there were problems with Storage TEK logging. After every unsuccesfull H1run start we get NAN in HERA produced. 20/8/94 ======================= === Lumi RUN# 537 Start lumi run537 date: 20/8/94 Collision time: 6:07:39 - 16:53:43 Currents (mkA): Ie= 29767.00, Ip= 49900.00 Peak luminosity: 3457.529 mb-1 s-1 Peak spec.lumi : 465.872796 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 57478.522654 mkb-1 H1 Run total lumi: 36230.4141 mkb-1 H1 data taken lumi: 25078.1166 mkb-1 H1 Runs: 84890 - 84974 HERA - physics: 54655.52927 mkb-1 H1Run - physics: 32626.776035 mkb-1 H1data - physics: 21737.605179 mkb-1 H1 Runs: 84891 - 84974 Tot curr/rate factor: 1.32% C/R F H1Run gated: 1.34% Rand.C.F: 1.28% RCF Run gated: 1.44% Relative ET trigg accept.: 0.3337 PS(lns): L4, L5 histo-files are absent at all ... 21/8/94 ======================= erdmann === Lumi RUN# 538 Start lumi run538 date: 20/8/94 Collision time: 18:50:29 - 3:07:38 Currents (mkA): Ie= 28376.00, Ip= 44500.00 Peak luminosity: 1688.37 mb-1 s-1 Peak spec.lumi : 373.20795 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 2142302852.62953 mkb-1<--- NAN H1 Run total lumi: 33842.7992 mkb-1 H1 data taken lumi: 32126.0699 mkb-1 H1 Runs: 84979 - 84992 HERA - physics: 2142291271.663998 mkb-1<--- NAN H1Run - physics: 21973.344733 mkb-1 H1data - physics: 20449.903524 mkb-1 H1 Runs: 84986 - 84992 Tot curr/rate factor: 0.66% C/R F H1Run gated: 0.66% Rand.C.F: 1.27% RCF Run gated: 1.27% Relative ET trigg accept.: 0.3399 HERA total lumi: 37815.0111 mkb-1 HERA - physics : 26234.051 mkb-1 PS(lns): L4, L5 histos are ~OK. Some histo-files are absent. 21/8/94 ======================= schacht === Lumi RUN# 539 Start lumi run539 date: 21/8/94 Collision time: 5:48:44 - 8:12:40 Currents (mkA): Ie= 28287.00, Ip= 33100.00 Peak luminosity: 1520.009 mb-1 s-1 Peak spec.lumi : 340.544164 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 10221.22227 mkb-1 H1 Run total lumi: 9128.230433 mkb-1 H1 data taken lumi: 7912.602759 mkb-1 H1 Runs: 84996 - 85003 HERA - physics: 7820.732969 mkb-1 H1Run - physics: 6619.264822 mkb-1 H1data - physics: 5470.048453 mkb-1 H1 Runs: 84997 - 85003 Tot curr/rate factor: 1.34% C/R F H1Run gated: 1.37% Rand.C.F: 2.13% RCF Run gated: 2.14% Relative ET trigg accept.: 0.3497 PS(lns): L4, L5 histos are ~OK. Some histo-files are absent. 22/8/94 ======================= === Lumi RUN# 541 Start lumi run541 date: 21/8/94 Collision time: 17:58:48 - 7:17:17 Currents (mkA): Ie= 29867.00, Ip= 50500.00 Peak luminosity: 2828.744 mb-1 s-1 Peak spec.lumi : 429.292574 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 65067.0438 mkb-1 H1 Run total lumi: 56885.761481 mkb-1 H1 data taken lumi: 49495.422943 mkb-1 H1 Runs: 85030 - 85056 HERA - physics: 54445.613195 mkb-1 H1Run - physics: 45647.157367 mkb-1 H1data - physics: 38490.096963 mkb-1 H1 Runs: 85031 - 85056 Tot curr/rate factor: 0.95% C/R F H1Run gated: 1% Rand.C.F: 1.36% RCF Run gated: 1.41% Relative ET trigg accept.: 0.3450 Lumi Run# 540 was empty.(Yu.S) PS(lns): L4 histos are OK. Warning: Some histo-files are absent. PS(lns): SOS_Warning: Not sure in OK: L4 WITH BREAKES, L5 NOT WORKING. 22.08.1994 ==================== H01GOG === upgrade of LRATES routine According to the request of S.Levonian a routine LRATES (from CMZ file F11LEV.H1LOOLS) has been upgraded to include: 1) Basic trigger rates from LUMM bank 2) Creation of text file in a format required by ZEUS (see mail from L.Suszycki to Yu.Soloviev and A.Fomenko) The text of new LRATES can be found in H01GOG.NELRUN94.S(#LUMTCL) An example of text output file: H01GOG.ZEUSOUT.EP522 LOOK macro file H01GOG.LUMI.MACRO contains commands creating few additional figures from LUMM rates (fig. 30-35) I would like to ask Sergey to check this job and, in case of no problems, to release it officially. 22/8/94 ======================= === Lumi RUN# 542 Start lumi run542 date: 22/8/94 Collision time: 11:39:32 - 14:33:38 Currents (mkA): Ie= 21500.00, Ip= 36200.00 Peak luminosity: 1497.863 mb-1 s-1 Peak spec.lumi : 366.461857 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 8829.4644 mkb-1 H1 Run total lumi: 7425.0469 mkb-1 H1 data taken lumi: 5789.9976 mkb-1 H1 Runs: 85073 - 85088 HERA - physics: 8283.583579 mkb-1 H1Run - physics: 6536.5723 mkb-1 H1data - physics: 4972.8495 mkb-1 H1 Runs: -1 - 85088 Tot curr/rate factor: 1.5% C/R F H1Run gated: 1.59% Rand.C.F: 1.28% RCF Run gated: 1.3% Relative ET trigg accept.: 0.3257 PS(lns): L4 R85074 histos ~ OK. Warning: Some histo-files are absent. PS(lns): SOS_Warning: Not sure in OK: L4 WITH BREAKES, L5 NOT WORKING. 22.08.1994 ==================== H1KSOL === LRTL bank missing........ Suspicions (see mess. 20.08) about LTRL bank missing were confirmed. Since H1 Run 84891 till 84926 there were no LRTL and LUMM banks in H1 Data Flow.Other banks are there. P.S. (S.L.) Lumi information in the database and H1EP file is restored from LRTN banks of RAW data. 22.08.1994 ==================== H1KSOL === TCL LOOK files........... One can find TCL RLOOK files for cart.53,58,59,60 in H1KSOL directory. 22.08.1994 ==================== F11LEV === upgrade of LRATES routine I tested new version of LRATES from Nelly (see message of H01GOG early today). It is basically OK, except few cosmetic things. In addition, some more important corrections were made, explained below. 1) During tests, it was found an old and forgotten (at least by me) "feature" of LRTL rates: they are wrong for the first measurement in the run. It can be seen from text file H01GOG.ZEUSLUMI.EP522. In principle it must be easy to cure online. Until this is done by Fomenko, I added in LRATES to skip (ignore) those LRTL banks, with negative rates. 2) As was pointed by Soloviev, it now often happens that H1 runs are written during injection. Then the bunch structure may change. The same may happen if part of the beam is suddenly lost during data taking. So I corrected this part of the code (not related to last modifications by Nelly) to update bunch structure each time rather than once per H1 run, as it was before. Questions which appeared during these tests: - Presently LRTL is NOT created if e-beam current = 0 (to reduce amount of useless lumi data). However, LUMM bank IS created. Why? It seems more logical to create them always together, under the same conditions. If I(e)=0, LUMM rates are not very interesting anyway. - In new LRATES version, a creation of text file for ZEUS is optional (if IDB flag = 1 is set in main program). Question (to ZEUS?): how often do they need this information? Should we send these files them only by request, or by default (too boring: each day to send a mail of 5-6 thousand lines long). This has to be clarified (by Nelly as a contact person for this activity?) - On the plot of total trigger rates (fig. 10 in RLOOK files, or fig.74 in SHOWLUMI) it is seen a funny regular structure. It was present also in old files (e.g. from 1993, or beginning 1994), but not so well pronounced as now. In order to see it clearly one has to zoom these figures. Does anybody knows an explanation for that? Status of LRATES now. --------------------- 1) An official version is kept on IBM file F11LEV.H1TOOLS.CMZ in /LUMI/LRATES directory and compiled to F11LEV.H1TOOLS.LOAD library 2) A sample job is in F11LEV.RUN94.S(#LUMTCL). It is identical to those from H01GOG.NELRUN94.S Note, that IDB = 0/1 will switch off/on a creation of "ZEUSOUT" file (see a line before CALL LRATES) 3) This job is always creating files with a standard names: userid.RLOOK.EP000 - a LOOK history file userid.ZEUSOUT.EP000 - a text file for ZEUS After job is finished, one has to rename the files according to actual ep run #. This is just a recommendation. If there are ideas for more convenient procedure/convention of naming these files - they are welcome. Note, that in present scheme, a file with a name ZEUSOUT.EP000 must NOT exist before the job is submitted, because it is opened as a NEW by FPACK statement at the bottom of the job. So it must be either renamed, or deleted before submit a job. 4) A corresponding LOOK macro in H01GOG.LUMI.MACRO is ok, so I copied it also to F11LEV.LUMI.MACRO Figures 30-35 are very important and interesting. If one ignores occasional large spikes (another task for Fomenko - to cure them online!) they show a time evolution of different rate ratios, like R(PD)/R(ET*PD), R(VC)/R(PD) etc. Please, those, who want to use the job - copy it from ('*' next line): get 'F11LEV.RUN94.S(#LUMTCL)' Also for future: before you submit #LUMTCL for new H1TCL cartridge - verify, that it is not yet done by others. So far it was done by one of the F11LEV, H01GOG, H1KSOL. So check their catalogs (e.g. lc F11LEV.RLOOK) It was agreed, that by default it must be done by Nelly. In case she is not able to do it by any reason - then either Yura, or me should do it. 22/8/94 ======================= janoth === Lumi RUN# 543 Start lumi run543 date: 22/8/94 Collision time: 20:19:48 - 21:54:12 Currents (mkA): Ie= 30223.00, Ip= 44501.00 Peak luminosity: 0 mb-1 s-1 Peak spec.lumi : 0 mb-1 s-1 mA-2 Number of collided b.: 0 Number of e-filled b.: 0 Number of p-filled b.: 170 Number of e-pilot b.: 0 Number of p-pilot b.: 170 HERA total lumi: 11043.2383 mkb-1 H1 Run total lumi: 11043.1482 mkb-1 H1 data taken lumi: 10918.6192 mkb-1 H1 Runs: 85095 - 85096 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 85096 - 85096 Tot curr/rate factor: 1.71% C/R F H1Run gated: 1.71% Rand.C.F: 2.31% RCF Run gated: 2.31% Relative ET trigg accept.: 0.3336 22/8/94 ======================= janoth === Lumi RUN# 544 Start lumi run544 date: 22/8/94 Collision time: 23:03:19 - 23:17:55 Currents (mkA): Ie= 14013.00, Ip= 41400.00 Peak luminosity: 0 mb-1 s-1 Peak spec.lumi : 0 mb-1 s-1 mA-2 Number of collided b.: 0 Number of e-filled b.: 0 Number of p-filled b.: 170 Number of e-pilot b.: 0 Number of p-pilot b.: 170 HERA total lumi: 4.030517 mkb-1 H1 Run total lumi: 20.7978 mkb-1 H1 data taken lumi: 16.8547 mkb-1 H1 Runs: 85099 - 85100 HERA - physics: 0 mkb-1 H1Run - physics: -0.000025 mkb-1 H1data - physics: 0.000039 mkb-1 H1 Runs: 85099 - 85100 Tot curr/rate factor: Not calc.% C/R F H1Run gated: 0.14% Rand.C.F: 0.64% RCF Run gated: 2.25% Relative ET trigg accept.: Not calc. 23/8/94 ======================= popov === Lumi RUN# 545 Start lumi run545 date: 23/8/94 Collision time: 1:24:14 - 7:27:53 Currents (mkA): Ie= 29708.00, Ip= 40600.00 Peak luminosity: 1718.856 mb-1 s-1 Peak spec.lumi : 375.715592 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 28687.139139 mkb-1 H1 Run total lumi: 27834.4299 mkb-1 H1 data taken lumi: 25262.2147 mkb-1 H1 Runs: 85101 - 85113 HERA - physics: 22285.085963 mkb-1 H1Run - physics: 20844.672294 mkb-1 H1data - physics: 18408.463227 mkb-1 H1 Runs: 85103 - 85113 Tot curr/rate factor: 1.41% C/R F H1Run gated: 1.41% Rand.C.F: 1.97% RCF Run gated: 1.99% Relative ET trigg accept.: 0.3383 PS(lns): L4, L5 histos ~ OK. Warning: Some histo-files are YET absent. PS(lns): Warning(?): Shape E_rec for PD is changing (from Run # to Run) from the "monotonicly decreasing" to the "peaked and then decreasing". 23.08.1994 ==================== H1KBEL === Positron annigilation There is some possibility to use our Photon Detector for registra- tion the process of annigilation positrons from HERA beam on the atoms of residual gas. In the final state of this process in the most cases will appear two annigilation photons. They will go at small angles to the direction of positron beam, and should be re- gistered by our Photon Detector. In this cases the energy, absorbed in the PD, will be equal the energy of positrons in the HERA beam. If it is possible to obtain the spectrum of photons in PD for events from pilot bunches only, then at the high energy end of the usual brensstrahlung spectrum will be small peak from these events. The relation of numbers annigilation events to the brems- strahlung events should be of the order 10**-3. The ratio of corres- ponding cross sections you can find in W.Heitler "The Quattum The- ory of Radiation". If this process will be registered, it can be used for indepen- dent calibration of the Photon Detector. 24/8/94 ======================= janoth === Lumi RUN# 546 Start lumi run546 date: 24/8/94 Collision time: 0:51:12 - 7:55:31 Currents (mkA): Ie= 28365.00, Ip= 44100.00 Peak luminosity: 2731.811 mb-1 s-1 Peak spec.lumi : 458.602549 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 41024.591348 mkb-1 H1 Run total lumi: 38976.6416 mkb-1 H1 data taken lumi: 30495.6069 mkb-1 H1 Runs: 85155 - 85175 HERA - physics: 37708.783902 mkb-1 H1Run - physics: 35030.629673 mkb-1 H1data - physics: 26683.591767 mkb-1 H1 Runs: 85157 - 85175 Tot curr/rate factor: 2.17% C/R F H1Run gated: 2.18% Rand.C.F: 1.61% RCF Run gated: 1.61% Relative ET trigg accept.: 0.3422 PS(lns): L4 OK; L5 files not yet ready, ended at run 85113. H1ep not. 24.08.1994 ===== dice2 ======== H1KFOM === More detail about p11-jump It was made LOOK-binary data set with behaivours with time of calibra- tion coefficients for Luminosity subbranch (only for 'hot' channel - e21-e27,p10-p14 and vcs). Vectors 10022-10028,20011-20015 and 20026 are keeping high mentioned behaivours (X-axis variable is event number at ET&PD&nVC-sample from Run 84025 up to 84585). There are 29220 events at this sample. This LOOK-binary data set is kept at DESY IBM: H1KFOM.LOOKB.R84025 FAST13 3010200E 00000 DASD Vector 20012 shows behaivour of CCp11. You can see that during Run 84025 CCp11 was changed on value near 50% from some start value into low direction (it means that p11-response at this time was incremented on factor 2 at Luminosity subbranch). It was happened near 1520th event (it means that near 08:42 09.08.94) - note that 5/6 of events from the same H1Run 84025 (near 1520 events) were collected with some 'normal' CCp11 value and after 1520 event it was fixed jump. During almost 15000 events new value of CCp11 was confirmed with permanent online calibration procedure and only 12.08.94 at 10:40 (during H1Run 84296) CCp11 came back to old 'normal' value. Note that both mentioned H1 Runs are inside ordinary Lumi RUNs (not boundaries between neighbour Lumi RUN. Lumi RUN# 521 includes H1Runs from 84014 up to 84039, from 03:55:37 up to 16:46:15) and Lumi RUN# 525 includes H1 Runs 84291-84309 which were recorded from 07:48:30 up to 16:09:43. So - no any influence of new e+filling or something connected with new filling. I am not shure that 15K ET&PD&nVC which were collected during last part of Lumi RUN# 521, during Lumi RUNs 522-524 and first part of Lumi RUN# 525 will be enough for calibration of this 5B-sample as it must be exluded some part of events from non G and M H1 Runs (as or- dinary). Sample 6A will start from H1 Run 84297 etc. Now new LUMIMON-data sets are ready (69-72) and it will be possible to select new data and check on possible 'non-standard' behaivour of p11 at latest events. 24.08.1994 ==================== F11LEV === structure on the R_total As it was written 2 days ago: " On the plot of total trigger rates (fig. 10 in RLOOK files, or fig.74 in SHOWLUMI) it is seen a funny regular structure. It was present also in old files (e.g. from 1993, or beginning 1994), but not so well pronounced as now. In order to see it clearly one has to zoom these figures. Does anybody knows an explanation for that?" After some more detailed investigations in became clear that: 1) This always was the case 2) It is more pronounced in total rates; in summed over all bunches rates it is less visible (smeared) 3) An effect is exactly 1% and happens in a constant time intervals = 10 measurements = 100 sec. 4) An effect is the following: each 10-th measurement the value of R_total is on 1% larger than it should be, and each next measurement is on 1% less than it should be To remind: R_total = [N(t1)-N(t0)]/(t1-t0) where N(t) is content of the Egors counters in the moment t, and t1-t0=10sec. This observation can be explained if something like following happens online: each 10-th measurement R_total = [N(t0+10.1)-N(t0)]/10. and then the next one: R_total = [N(t0+20.)-N(t0+10.1)]/10. 24.08.1994 ==================== F11LEV === LUMI task list .......... To remind most urgent task waiting in a queue, and people expected to work on them: 1) Many small bugs/problems in online software, like spikes due to counters overflow, negative rates in the first LRTL, wrong # of rows in BOS banks subheader, NAN appearing elsewhere, etc. 2) Alarm on the absence of LRTL/LUMM banks 3) Optimisation of signals/trigger from gas C-counter 4) Timing/thresholds for VC trigger 5) Estimate of the work for new ET at 3 possible positions, to incorporate them to the system 6) Stability control for the trigger sums (to use PD-method online) 7) Improvements in L4/L5 monitor plots + automatic control creating alarms in abnormal situations 8) Improvements in online LUMI data presentation for H1, HERA, ZEUS 9) Permanent offline control on the system using monitor events 10) Offline cross check of the integrated luminosity for physics Fomenko - 1,5,9 Sheviakov - 2,3,4,5,6 Soloviev - 6,9 Shtarkov - 7 Usik - 8 Gogitidze - 9,10 Of course, there is a lot of other work which is being done and not mentioned here (like calibration e.g.) I also have two organizational proposals: 1) V.Andreev as a responsible person for all offline work related to new e-taggers (MC simulation, data analysis, calibration, physics with them etc.) 2) W.Krasny as a possible new coordinator for the LUMI group in H1 in case I could not continue. He has got a permanent position in Paris - so he is available (if he will not leave H1) Also he has a large experience and knowledge with all QED type of processes, familiar with luminosity problems, and is a good coor- dinator. 24/8/94 ======================= v.popov === Lumi RUN# 547 Start lumi run547 date: 24/8/94 Collision time: 11:34:59 - 13:31:43 Currents (mkA): Ie= 25278.00, Ip= 38300.00 Peak luminosity: 2052.382 mb-1 s-1 Peak spec.lumi : 410.477221 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 172 Number of e-pilot b.: 15 Number of p-pilot b.: 19 HERA total lumi: 10944.145502 mkb-1 H1 Run total lumi: 10005.0145 mkb-1 H1 data taken lumi: 7602.9493 mkb-1 H1 Runs: 85189 - 85197 HERA - physics: 9543.325874 mkb-1 H1Run - physics: 7287.614639 mkb-1 H1data - physics: 5912.237105 mkb-1 H1 Runs: 85191 - 85197 Tot curr/rate factor: 2% C/R F H1Run gated: 2% Rand.C.F: 1.74% RCF Run gated: 1.75% Relative ET trigg accept.: 0.3494 PS(lns): L4 histos OK. Warning: Many histo-files are YET absent. PS(lns): L5 files not yet ready, ended at run 85167. H1ep OK. 25/8/94 ======================= Lacour === Lumi RUN# 548 Start lumi run548 date: 25/8/94 Collision time: 0:08:36 - 2:24:36 Currents (mkA): Ie= 28451.00, Ip= 48901.00 Peak luminosity: 3485.103 mb-1 s-1 Peak spec.lumi : 488.172224 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 18529.968468 mkb-1 H1 Run total lumi: 17023.7675 mkb-1 H1 data taken lumi: 13558.1182 mkb-1 H1 Runs: 85260 - 85271 HERA - physics: 16740.800143 mkb-1 H1Run - physics: 14321.102581 mkb-1 H1data - physics: 10986.977844 mkb-1 H1 Runs: 85262 - 85271 Tot curr/rate factor: 1.17% C/R F H1Run gated: 1.14% Rand.C.F: 1.73% RCF Run gated: 1.72% Relative ET trigg accept.: 0.3482 PS(lns): L4 histos OK. Warning: Many histo-files are YET absent. PS(lns): L5 files not yet ready, ended at run 85167. H1ep absent. 25/8/94 ======================= Lacour === Lumi RUN# 549 Start lumi run549 date: 25/8/94 Collision time: 4:23:02 - 8:04:51 Currents (mkA): Ie= 25595.00, Ip= 45800.00 Peak luminosity: 1474.757 mb-1 s-1 Peak spec.lumi : 286.990289 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 14746.558133 mkb-1 H1 Run total lumi: 13917.128475 mkb-1 H1 data taken lumi: 11286.929473 mkb-1 H1 Runs: 85273 - 85287 HERA - physics: 11493.94505 mkb-1 H1Run - physics: 10682.597594 mkb-1 H1data - physics: 8123.31335 mkb-1 H1 Runs: 85274 - 85287 Tot curr/rate factor: 2.32% C/R F H1Run gated: 2.32% Rand.C.F: 1.65% RCF Run gated: 1.65% Relative ET trigg accept.: 0.3278 PS(lns): L4 histos OK. Warning: Many histo-files are YET absent. PS(lns): L5 files not yet ready, ended at run 85167. H1ep absent. 25.08.1994 ==================== F11LEV === to: Positron annihilation I tried to see the e+e- -> gamma+gamma peak proposed by A.S.Belousov for PD-calibration, in our data, but so far did not succeeded. I selected events from LUMIMON files processed by Nelly (LOOK files H01GOG.MLOOK.xxx) by the following conditions: a) e-pilot bunches and b) PD_high bit = 1 and c) ET bit = 0 and then I compared e-p and e+p samples. Conclusions: 1) There were very few events found satisfying conditions a*b*c (in e-p data for runs 81355 to 81976 ~ 500 events, in e+p data for runs 84028 to 85055 ~ 300 events) 2) There is no significant difference in E(PD) for e-p and e+p data; both show a broad distribution with "peak" at 21-22 GeV and sigma= 4 GeV. This is consistent with high energy end of the bremstrahlung spectrum, biased by the requirement to see nothing in E-tagger. 3) E(VC) spectra for these samples are also very similar 4) Thus, if there are such events, their rate is very small, and a special trigger with smaller prescaling is required to see them. A small rate may also be explained by the fact, that at least part of the rest gas is highly ionized, and amount of electrons is much smaller, than A.S.Belousov has expected. This assumption can be checked with machine experts. 25.08.1994 ===== dice2 ======== H1KFOM === Selected H1Lumi Monitrig.. Today it were selected calibration data samples from the next data sets which were produced with standard job prepared by S.Levonyan at dice1-environment: HERA03.H01.LUMIMON.C9400069 K14557 78048081 00001 ACS-E-C ...... HERA03.H01.LUMIMON.C9400072 K23373 78048081 00001 ACS-E-C It were selected events with (s92=1 only),with ET&PD&VC=1 and with ET&PD&nVC from these data sets (as ordinary) from 519138 events: 1) S92=1 only 21596 events ( 34.8 MBytes) 2) ET&PD&VC 57005 events ( 96.0 MBytes) 3) ET&PD&nVC 30271 events ( 51.1 MBytes) Created data sets were saved at DESY IBM storage at the next data sets H1KFOM.ETPDNVC.M6972.C00 K38361 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M6972.C00 K38738 78048081 00001 ACS-E-C H1KFOM.S92.M6972.C00 K38829 78048081 00001 ACS-E-C These data include events from Lumi RUNs# 533-546 (H1 Runs 84585- 85166). First view on CCp11 behaivour with time at ETPDnVC sample shows that there is no any evidence on 'non-standard' response of p11 at these H1 Runs. It were fixed short-time jumps into high direction at start of each Lumi Run (as ordinary) - from 20 up to 30%. So it is possible to suppose that all these data will be included into 6A-sample of events for calibration (from H1 Run 84297 up to latest H1 Runs - 85166 for today). 27/8/94 ======================= Lacour === Lumi RUN# 550 Start lumi run550 date: 27/8/94 Collision time: 13:44:28 - 21:51:07 Currents (mkA): Ie= 30735.00, Ip= 32900.00 Peak luminosity: 2561.296 mb-1 s-1 Peak spec.lumi : 515.782614 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 35533.014523 mkb-1 H1 Run total lumi: 27805.819008 mkb-1 H1 data taken lumi: 20505.788265 mkb-1 H1 Runs: 85476 - 85522 HERA - physics: 33834.65539 mkb-1 H1Run - physics: 25802.941346 mkb-1 H1data - physics: 19114.746888 mkb-1 H1 Runs: 85483 - 85522 Tot curr/rate factor: 1.04% C/R F H1Run gated: 1.07% Rand.C.F: 1.32% RCF Run gated: 1.24% Relative ET trigg accept.: 0.3453 PS(lns): L4 & L5 histos OK. Warning: Some histo-files are YET absent. 28/8/94 ======================= Vazdik === Lumi RUN# 551 Start lumi run551 date: 28/8/94 Collision time: 0:58:43 - 4:15:55 Currents (mkA): Ie= 28551.00, Ip= 31200.00 Peak luminosity: 1608.15 mb-1 s-1 Peak spec.lumi : 380.671818 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 14567.940942 mkb-1 H1 Run total lumi: 13943.282284 mkb-1 H1 data taken lumi: 11896.926555 mkb-1 H1 Runs: 85526 - 85534 HERA - physics: 11222.181429 mkb-1 H1Run - physics: 10374.017632 mkb-1 H1data - physics: 9109.40758 mkb-1 H1 Runs: 85528 - 85534 Tot curr/rate factor: 1.23% C/R F H1Run gated: 1.24% Rand.C.F: 2.36% RCF Run gated: 2.34% Relative ET trigg accept.: 0.3464 PS(lns): L4 & L5 histos OK. Some histo-files are YET absent. 28/8/94 ======================= List === Lumi RUN# 552 Start lumi run552 date: 28/8/94 Collision time: 12:39:58 - 21:08:48 Currents (mkA): Ie= 26532.00, Ip= 44800.00 Peak luminosity: 3027.214 mb-1 s-1 Peak spec.lumi : 504.850188 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 46474.672258 mkb-1 H1 Run total lumi: 37476.714978 mkb-1 H1 data taken lumi: 32434.327865 mkb-1 H1 Runs: 85610 - 85652 HERA - physics: 44635.992005 mkb-1 H1Run - physics: 35595.294949 mkb-1 H1data - physics: 30918.428653 mkb-1 H1 Runs: 85615 - 85652 Tot curr/rate factor: 0.93% C/R F H1Run gated: 0.95% Rand.C.F: 1.11% RCF Run gated: 1.02% Relative ET trigg accept.: 0.3503 PS(lns): L4 & L5 histos OK. 29/8/94 ======================= Lacour === Lumi RUN# 553 Start lumi run553 date: 29/8/94 Collision time: 3:00:16 - 12:37:36 Currents (mkA): Ie= 24886.00, Ip= 43300.00 Peak luminosity: 1544.461 mb-1 s-1 Peak spec.lumi : 274.961608 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 33834.443561 mkb-1 H1 Run total lumi: 32113.4508 mkb-1 H1 data taken lumi: 29529.1277 mkb-1 H1 Runs: 85655 - 85671 HERA - physics: 33375.499751 mkb-1 H1Run - physics: 30005.561229 mkb-1 H1data - physics: 27577.118038 mkb-1 H1 Runs: 85657 - 85671 Tot curr/rate factor: 1.15% C/R F H1Run gated: 1.16% Rand.C.F: 1.09% RCF Run gated: 1.08% Relative ET trigg accept.: 0.3394 PS(lns): L4 histos OK. L5 files not yet ready. 30/8/94 ======================= List === Lumi RUN# 554 Start lumi run554 date: 29/8/94 Collision time: 22:27:43 - 6:18:11 Currents (mkA): Ie= 27198.00, Ip= 45400.00 Peak luminosity: 2845.315 mb-1 s-1 Peak spec.lumi : 441.044874 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 47057.262101 mkb-1 H1 Run total lumi: 36380.8186 mkb-1 H1 data taken lumi: 31108.1122 mkb-1 H1 Runs: 85697 - 85741 HERA - physics: 45307.39221 mkb-1 H1Run - physics: 34148.588778 mkb-1 H1data - physics: 28945.362245 mkb-1 H1 Runs: 85698 - 85741 Tot curr/rate factor: 1.09% C/R F H1Run gated: 1.11% Rand.C.F: 1.14% RCF Run gated: 1.19% Relative ET trigg accept.: 0.3394 PS(lns): for R85700 L4 histos absent; L5 OK. PS(lns): for R85741 L4 histos OK; L5 absent. 30.08.1994 ===== dice2 ======== H1KFOM === Relation Coeff.Set 5B Today it was made attempt to produce Rel. Coeff. Set for 5B data sample (from H1 Run 84026 up to H1 Run 84295). It were selected 14166 ET&PD&nVC events from this H1 Run range from data set: H1KFOM.ETPDNVC.M4868.C00 K30155 78048081 00001 ACS-E-C All sample include data from 62 H1 Runs. 10 H1 Runs are not M- or G- labeled at H1EP (84039,84044,84081,84082,84191,84251,84265,84270,84291 and 84292). After excluding of ET&PD&nVC-events from these 10 H1 Runs there are 12153 ET&PD&nVC events for calibration making (and only 6999 events were used for calibration after all cuts at the first step). There are 33 events with ovfl at p11, 9 ovfl at p16, 7 ovfl at p05 and 1 ovfl at e21,e22,e24,e25,p10,p12,p13. Max sigmas at Relation Coefficient Histos (e26-0.157,p11-0.149,e25- 0.064 and p13-0.042) were fixed after first step of calibration on 5B-sample events. After 2nd step of calibration Max Sigmas at Relaton Coefficients Histos were fixed as next values: (e26-0.158,e25-0.060,p11-0.023 and p13-0.046). 7227 ET&PD&nVC events were used for calibration after all cuts. After all high mentioned 'cleaning' of 5B-data samples it were collected: 12153 events with ET&PD&nVC trigger 22511 events with ET&PD&VC trigger 8820 events with S92-trigger (PD&nVC-events). It were got 12153 ET&PD&nVC from these Runs and it were used for calibration 7227 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 1.095 1.133 0.987 1.122 1.041 1.456 1.170 0.862 1.018 0.895 1.162 0.847 0.984 0.911 1.080 0.923 0.894 0.926 0.959 0.793 0.940 1.009 1.013 0.992 0.991 1.005 1.025 0.960 1.116 1.033 1.016 0.896 1.011 1.059 1.068 0.913 0.830 1.085 1.024 0.918 0.000 0.000 0.000 1.074 0.980 0.851 0.960 0.000 0.000 ==> Relation Coeff.Set for PD 2.116 1.004 1.120 1.542 0.960 1.049 1.032 1.028 1.044 0.975 0.986 1.034 1.018 1.026 1.053 1.017 1.011 1.007 1.024 0.964 1.711 0.935 1.067 1.004 0.905 ==> Sig. at Relation Coeff.Set for ET 0.000 0.033 0.000 0.012 0.017 0.017 0.029 0.006 0.010 0.003 0.024 0.005 0.008 0.012 0.014 0.021 0.016 0.013 0.017 0.006 0.007 0.027 0.027 0.015 0.019 0.060 0.159 0.016 0.006 0.019 0.023 0.010 0.005 0.014 0.026 0.004 0.002 0.020 0.004 0.000 0.000 0.000 0.000 0.002 0.000 0.001 0.000 0.000 0.000 ==> Sig. at Relation Coeff.Set for PD 0.014 0.013 0.005 0.007 0.000 0.014 0.019 0.029 0.016 0.002 0.017 0.022 0.016 0.046 0.025 0.014 0.023 0.022 0.020 0.006 0.002 0.005 0.012 0.024 0.000 ==> Ent. at Relation Coeff.Set for ET 1 8 1 11 8 16 5 9 23 38 33 28 21 15 216 163 211 288 294 263 130 1932 3142 2585 2096 1630 1122 430 868 945 672 358 309 118 71 7 2 3 3 1 0 0 0 3 2 2 2 0 0 ==> Ent. at Relation Coeff.Set for PD 27 21 14 2 1 474 1651 1191 184 5 1893 5473 4451 957 55 452 1877 1430 336 17 13 8 7 3 1 As You can see all sigma values for 'hot' H1Lumi cahnnels RC histos have more or less reasonable values (may be p13,e25,e26) are more then ordinary). Runs 84026- 84295 (ET&PD&nVC-sample - near 12.0K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.46 0.97 27.48 0.96 27.53 0.95 Runs 84026- 84295 (ET&PD&VC-sample - near 22.5K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.18 1.23 27.23 1.18 As start values of Calibration Coefficients for Photoproduction Branch were got ones after 3rd step of calibration with ET&PD&nVC events from 5A-sample (H1 Runs 83004-84024 - near 25.5 K events). CCvcs value was got from last VCs calibration at 5A-sample of ETPDVC- events (the same H1 Runs range - see message from 19.08.94 at LL10). 30.08.1994 ===== dice2 ======== H1KFOM === PDREC-spectra for 5B Today it were produced 100th ntuple for S92=1 events from earlier mentioned 5B sample with events from Runs 84026-84295: H1KFOM.YLOOKQ4.R84026 ( 6643 entries) FAST13 3010200E 00000 DASD At interactive LOOK-session it was produced 70th histo for this data set and written into the next LOOK-binary data set: H1KFOM.BLOOKQ2.R84026 5203 entries in 70h FAST17 3010200E 00000 DASD First attempt to fit 70th histo at BLOOKQ2-data set put positive sign of Global Energy Shift at Photon Arm (+2.3%) and enough good resolution digits (12%)- but poor statistic (1048 entries,24-35 GeV region). It were prepared 100th tuples with ET&PD&nVC and ET&PD&VC-events for procedure of defining Global Energy Shifts and CCvcs: H1KFOM.YLOOKQ2.R84026 12032 entries FAST04 3010200E 00000 DASD H1KFOM.YLOOKQ3.R84026 21343 entries FAST18 3010200E 00000 DASD 30.08.1994 ==================== H1KFOM === Global Shifts,CCvcs 5B It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 0.976 for PD Channels (exept VCs), 1.027 for ET channels. Correction factor for CCvcs is 1.06. So CCvcs = 3.189*1.06 =3.380Mev FADCcount. These digits are valid for H1Lumi events from Run 84026 up to 84295 Runs 84026- 84295 (ET&PD&nVC-sample - near 12.0K events) xetcut&vcdepcut Step Mean Sigma 0 27.52 0.96 Runs 84026- 84295 (ET&PD&VC-sample - near 22.5K events) xetcut Step Mean Sigma 0 27.52 1.21 P.S. As seems it is reasonable to put high mentioned Relation Coeff. VCs and Global Energy Shifts into H1DataBase after 6A sample calibration (due to latest data must differ from 5B sample due to early mentioned CCp11 jump). 30.08.1994 ===== dice2 ======== H1KFOM === Selected H1Lumi Monitrig.. Today it were selected calibration data samples from the next data sets which were produced with standard job prepared by S.Levonyan at dice1-environment: HERA03.H01.LUMIMON.C9400073 K19048 78048081 00001 ACS-E-C ...... HERA03.H01.LUMIMON.C9400075 K21396 78048081 00001 ACS-E-C It were selected events with (s92=1 only),with ET&PD&VC=1 and with ET&PD&nVC from these data sets (as ordinary) and combined with events which were selected at 25.08.94 (69-72 LUMIMONs): 1) S92=1 only 35433 events ( 56.7 MBytes) 2) ET&PD&VC 94412 events (157.9 MBytes) 3) ET&PD&nVC 49859 events ( 83.7 MBytes) Created data sets were saved at DESY IBM storage at the next data sets H1KFOM.ETPDNVC.M6975.C00 K19145 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M6975.C00 K41985 78048081 00001 ACS-E-C H1KFOM.S92.M6975.C00 K42181 78048081 00001 ACS-E-C These data include events from Lumi RUNs# 533 - 554 (H1 Runs 84585- 85697). 30.08.1994 ===== dice2 ======== H1KFOM === e19-Response Decrementing. Today during first attempt to check on data sample 6A (H1Runs 84297- -85697) it was found that all is OK with p11-response at this data sample - so it is possible to hope on large statistics at this data sample and possible good calibration. But firstly it was noted that e19-Response (as seems) became too low. First evidence on decremention of e19-response was fixed at 5B-data sample (when CCe19 became near 7 MeV/FADCcount). During first step of calibration with 6A-data sample it was fixed the next degradation steps - CCe19 became more then 9 MeV/FADC count. Even CCe21 is near 6.9 MeV/FADCcount. These are final values of CC for all H1Lumi sp. channel (exept VCs) after first step of calibration with 6A sample (all H1 Runs without selection of Good and Medium Runs). Near 35.5K events were used for calibration: ==> ET Calibr.Coefficients Final Status 4.028 4.268 4.012 3.413 3.924 3.718 3.815 4.092 3.711 3.768 2.008 4.956 3.822 3.363 5.520 2.614 4.459 4.940 4.554 9.673 4.380 6.876 4.761 5.278 4.576 4.233 4.737 4.250 4.233 4.486 4.430 3.965 4.441 4.782 2.915 4.221 4.584 3.501 3.469 4.375 4.004 3.983 4.046 3.991 4.280 1.957 3.712 4.133 4.018 ==> PD & VC Calibr.Coefficients Final Status 2.153 1.541 1.461 2.329 2.538 1.236 2.284 2.683 2.202 1.590 2.228 4.605 2.909 2.912 2.089 2.005 1.854 2.610 2.829 2.496 1.625 1.518 2.162 3.209 2.549 3.380 ==> ET Channels Final Weights 0.660 1.081 0.661 1.231 0.849 1.057 0.847 0.700 2.932 6.506 7.660 4.774 5.809 3.033 6.759 20.473 33.199 48.709 45.481 27.605 25.627 3518.339 4353.684 3058.716 2099.819 1503.775 974.825 355.179 30.001 27.987 15.585 11.720 7.440 3.733 1.758 0.881 0.704 0.706 0.671 0.671 0.661 0.912 0.660 0.716 0.686 0.663 0.659 0.653 0.650 ==> PD & VC Channels Final Weights 0.843 0.833 0.841 0.681 0.650 11.211 39.940 33.642 7.555 0.686 787.449 3436.839 2572.903 310.521 6.851 65.092 384.489 261.956 47.425 1.705 1.236 2.878 3.086 0.935 0.651 CCp11 became more on factor 2 and is more or less stable during all presented piece of 6A sample. Relation Coefficient for e19 almost was not changed - so this problem is common for both subbranches (photomultiplier, divider or crystal transparancy). 30.08.1994 ==================== H1KSOL === New Trig.Sum Coeff........ Coefficients for Trig.Summs were changed today according to info from Monit.Trig. It was : PD - 0.00337 ET - 0.00437 SETPD - 0.00389 It is now (will be seen at next Lumi Run # 555): PD - 0.00396 ET - 0.00583 SETPD - 0.00598 31.08.1994 ==================== H1KSOL === New Trig.Sum Coeff........ Since H1 Run# 85952 coeff. for Trig.Summs were set to: PD - 0.00421 ET - 0.00662 SETPD - 0.00598 (have been not changed) 31/8/94 ======================= zacek === Lumi RUN# 555 Start lumi run555 date: 31/8/94 Collision time: 3:21:33 - 14:04:49 Currents (mkA): Ie= 22680.00, Ip= 32801.00 Peak luminosity: 1390.523 mb-1 s-1 Peak spec.lumi : 355.87586 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 32043.224506 mkb-1 H1 Run total lumi: 29706.7384 mkb-1 H1 data taken lumi: 27711.2722 mkb-1 H1 Runs: 85938 - 85961 HERA - physics: 31613.439263 mkb-1 H1Run - physics: 29118.2452 mkb-1 H1data - physics: 27146.3314 mkb-1 H1 Runs: 85940 - 85961 Tot curr/rate factor: 1.06% C/R F H1Run gated: 1.05% Rand.C.F: 0.87% RCF Run gated: 0.89% Relative ET trigg accept.: 0.3326 PS(lns): L4 & L5 histos OK (R85944). 31.08.1994 ==================== H1KSOL === e19 Rel.Coeff.behaviour... Here is the history of e19 Relation Coeff. behavior: Run range e19 Rel.Coeff 80601 - 81700 0.466 81701 - 81977 0.419 82980 - 82981 0.448 83004 - 84024 0.626 84026 - 84295 0.793 So the reason seems to be not related with PM or crystall. 1/9/94 ===================== fretwurst === Lumi RUN# 557 Start lumi run557 date: 31/8/94 Collision time: 22:37:18 - 9:43:21 Currents (mkA): Ie= 26628.00, Ip= 35300.00 Peak luminosity: 922.901 mb-1 s-1 Peak spec.lumi : 193.093984 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 41678.080002 mkb-1 H1 Run total lumi: 36260.0883 mkb-1 H1 data taken lumi: 32836.6613 mkb-1 H1 Runs: 85979 - 85997 HERA - physics: 40768.561456 mkb-1 H1Run - physics: 35230.729725 mkb-1 H1data - physics: 31836.342634 mkb-1 H1 Runs: 85980 - 85997 Tot curr/rate factor: 0.87% C/R F H1Run gated: 0.86% Rand.C.F: 1.06% RCF Run gated: 1.04% Relative ET trigg accept.: 0.3298 PS : Lumi Run# 556 was empty.(Yu.S) PS(lns): for R85987 (the largest Lumi): L4 histos absent; L5 OK. 1/9/94 ======================= Flamm === Lumi RUN# 558 Start lumi run558 date: 1/9/94 Collision time: 21:15:11 - 21:26:44 Currents (mkA): Ie= 25882.00, Ip= 38000.00 Peak luminosity: 0 mb-1 s-1 Peak spec.lumi : 0 mb-1 s-1 mA-2 Number of collided b.: 0 Number of e-filled b.: 0 Number of p-filled b.: 170 Number of e-pilot b.: 0 Number of p-pilot b.: 170 HERA total lumi: 4.6985 mkb-1 H1 Run total lumi: 4.698534 mkb-1 H1 data taken lumi: 4.608983 mkb-1 H1 Runs: 86044 - 86044 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 86044 - 86044 Tot curr/rate factor: 74.43% C/R F H1Run gated: 74.43% Rand.C.F: Not calc.% RCF Run gated: Not calc.% Relative ET trigg accept.: Not calc. 2/9/94 ======================= Raupach === Lumi RUN# 559 Start lumi run559 date: 2/9/94 Collision time: 5:02:26 - 5:16:03 Currents (mkA): Ie= 28799.00, Ip= 35900.00 Peak luminosity: 0 mb-1 s-1 Peak spec.lumi : 0 mb-1 s-1 mA-2 Number of collided b.: 0 Number of e-filled b.: 0 Number of p-filled b.: 170 Number of e-pilot b.: 0 Number of p-pilot b.: 170 HERA total lumi: 7.549612 mkb-1 H1 Run total lumi: 6.478252 mkb-1 H1 data taken lumi: 6.434092 mkb-1 H1 Runs: 86048 - 86049 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 86049 - 86049 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 2.51% RCF Run gated: 1.47% Relative ET trigg accept.: Not calc. 2/9/94 ======================= Raupach === Lumi RUN# 560 Start lumi run560 date: 2/9/94 Collision time: 6:14:34 - 13:58:50 Currents (mkA): Ie= 27487.00, Ip= 35900.00 Peak luminosity: 2172.839 mb-1 s-1 Peak spec.lumi : 456.710207 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 33590.994665 mkb-1 H1 Run total lumi: 30795.1864 mkb-1 H1 data taken lumi: 27547.9582 mkb-1 H1 Runs: 86055 - 86083 HERA - physics: 32138.673269 mkb-1 H1Run - physics: 29025.772014 mkb-1 H1data - physics: 25811.557313 mkb-1 H1 Runs: 86061 - 86083 Tot curr/rate factor: 1.64% C/R F H1Run gated: 1.65% Rand.C.F: 1.01% RCF Run gated: 1.01% Relative ET trigg accept.: 0.3353 PS(lns): for R86065 (high statistics) L4 histos absent; L5 OK. 2/9/94 ====================== Theissen === Lumi RUN# 561 Start lumi run561 date: 2/9/94 Collision time: 16:05:10 - 17:13:02 Currents (mkA): Ie= 25324.00, Ip= 34201.00 Peak luminosity: 0.111 mb-1 s-1 Peak spec.lumi : 0.028043 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 1934.594959 mkb-1 H1 Run total lumi: 1880.6272 mkb-1 H1 data taken lumi: 1795.7958 mkb-1 H1 Runs: 86094 - 86096 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 86096 - 86096 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 38.51% RCF Run gated: 38.97% Relative ET trigg accept.: Not calc. 2/9/94 ====================== Theissen === Lumi RUN# 562 Start lumi run562 date: 2/9/94 Collision time: 17:20:41 - 22:50:16 Currents (mkA): Ie= 21145.00, Ip= 34000.00 Peak luminosity: 1172.554 mb-1 s-1 Peak spec.lumi : 301.536441 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 22031.606507 mkb-1 H1 Run total lumi: 21190.9494 mkb-1 H1 data taken lumi: 16552.7822 mkb-1 H1 Runs: 86096 - 86110 HERA - physics: 20014.887518 mkb-1 H1Run - physics: 14781.4028 mkb-1 H1data - physics: 12154.179 mkb-1 H1 Runs: 86101 - 86110 Tot curr/rate factor: 4.36% C/R F H1Run gated: 4.37% Rand.C.F: 4.74% RCF Run gated: 4.82% Relative ET trigg accept.: 0.3313 PS(lns): for R86104 (the largest Lumi): L4 & L5 are OK. PS(YuS): Int.Lumi values were not reset after Lumi Run#561,because it was the same e+ fill. 3/9/94 ====================== Theissen === Lumi RUN# 563 Start lumi run563 date: 3/9/94 Collision time: 10:20:37 - 10:37:55 Currents (mkA): Ie= 27980.00, Ip= 33701.00 Peak luminosity: 0 mb-1 s-1 Peak spec.lumi : 0 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 7.053515 mkb-1 H1 Run total lumi: 7.053544 mkb-1 H1 data taken lumi: 6.183176 mkb-1 H1 Runs: 86112 - 86112 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 86112 - 86112 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: Not calc.% RCF Run gated: Not calc.% Relative ET trigg accept.: Not calc. 03.09.1994 ==================== H1KSOL === "Small accidents.......... During start of Lumi Run# 561 there was a slow dump of H1 solenoid due to malfunctioning of steering computer in criogenic plant in HERA. We had again large rates on Lumi detectors. The same occured during Lumi Run#564 at about 13.30 on 03.09. After these two accidents responce of VETO chanells reduced by about factor 1.5. One could see the decreasing of Veto responce both in online monitoring and in L4 histos. 04.09.1994 ==================== F11LEV === NAN at online lumi........ This night again a NAN appeared in the integrated HERA lumi. It was correlated with Farm crash. But what was a real reason is unknown. The shift crew also noticed, that the integrated run lumi in the run summary was too small in this run when it happened (Run 86154). At the same time, run lumi on the supervisor screen was OK. So online people once again are asked: a) to correct NAN for this ep-run and b) to investigate the problem deeper. Could it be, that also integrated H1 lumi was reset to 0 in the middle of the run? By the way, I saw this situation earlier (recognized by large discre- pancies in H1EP list and LH1R bank in DB). When I printed LRTL content for such runs, it turned out, that in the middle of the runs, integ- rated lumi in LRTL was for some reason reset to 0. 3/9/94 ======================= Raupach === Lumi RUN# 564 Start lumi run564 date: 3/9/94 Collision time: 11:18:17 - 20:32:54 Currents (mkA): Ie= 24800.00, Ip= 33700.00 Peak luminosity: 1.793 mb-1 s-1 Peak spec.lumi : 0.403443 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 33596.93987 mkb-1 H1 Run total lumi: 31642.122 mkb-1 H1 data taken lumi: 24061.9469 mkb-1 H1 Runs: 86112 - 86136 HERA - physics: 33596.443678 mkb-1 H1Run - physics: 29085.793849 mkb-1 H1data - physics: 23926.951454 mkb-1 H1 Runs: 86120 - 86136 Tot curr/rate factor: 2.2% C/R F H1Run gated: 2.22% Rand.C.F: 1.46% RCF Run gated: 1.48% Relative ET trigg accept.: 0.3436 PS(lns): for R86133 (higher statistics) L4 histos absent; L5 OK. 4/9/94 ======================= Fedotov === Lumi RUN# 565 Start lumi run565 date: 3/9/94 Collision time: 22:18:31 - 9:08:24 Currents (mkA): Ie= 26336.00, Ip= 32900.00 Peak luminosity: 1719.757 mb-1 s-1 Peak spec.lumi : 376.071436 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 40895.4 mkb-1 <---- corrected value (NAN) H1 Run total lumi: 36775.934376 mkb-1 H1 data taken lumi: 30280.069493 mkb-1 H1 Runs: 86137 - 86161 HERA - physics: 40604.5481 mkb-1 <---- corrected H1Run - physics: 36477.779683 mkb-1 H1data - physics: 29995.064664 mkb-1 H1 Runs: 86138 - 86161 Tot curr/rate factor: 2.31% C/R F H1Run gated: 2.35% Rand.C.F: 0.93% RCF Run gated: 0.92% Relative ET trigg accept.: 0.3230 PS(lns): for R86151 (higher statistics) L4 histos OK; L5 absent. 5/9/94 ======================= === Lumi RUN# 566 Start lumi run566 date: 4/9/94 Collision time: 18:35:47 - 6:57:32 Currents (mkA): Ie= 25953.00, Ip= 38400.00 Peak luminosity: 2007.981 mb-1 s-1 Peak spec.lumi : 401.186909 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 2140464767.320428 mkb-1 <-- NAN value H1 Run total lumi: 48101.74354 mkb-1 H1 data taken lumi: 41162.994491 mkb-1 H1 Runs: 86205 - 86238 HERA - physics: 2140464542.889933 mkb-1 <-- NAN value H1Run - physics: 47267.90434 mkb-1 H1data - physics: 40413.69748 mkb-1 H1 Runs: 86207 - 86238 Tot curr/rate factor: 0.46% C/R F H1Run gated: 0.49% Rand.C.F: 0.78% RCF Run gated: 0.79% Relative ET trigg accept.: 0.3384 PS(lns): for R86211 (statistics 40K) L4 histos OK; L5 absent. PS(YuS): Hera total = 52744.323 mkb-1 Hera physics = 52519.893 mkb-1 5/9/94 =======================theissen === Lumi RUN# 567 Start lumi run567 date: 5/9/94 Collision time: 8:26:03 - 8:41:43 Currents (mkA): Ie= 25006.00, Ip= 37800.00 Peak luminosity: 0 mb-1 s-1 Peak spec.lumi : 0 mb-1 s-1 mA-2 Number of collided b.: 0 Number of e-filled b.: 0 Number of p-filled b.: 170 Number of e-pilot b.: 0 Number of p-pilot b.: 170 HERA total lumi: 486.351 mkb-1 H1 Run total lumi: 372.749823 mkb-1 H1 data taken lumi: 345.275735 mkb-1 H1 Runs: 86238 - 86239 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 86239 - 86239 Tot curr/rate factor: 1.65% C/R F H1Run gated: 1.46% Rand.C.F: 2% RCF Run gated: 1.96% Relative ET trigg accept.: Not calc. 5/9/94 =======================theissen === Lumi RUN# 568 Start lumi run568 date: 5/9/94 Collision time: 9:57:26 - 10:02:20 Currents (mkA): Ie= 26400.00, Ip= 37700.00 Peak luminosity: 0 mb-1 s-1 Peak spec.lumi : 0 mb-1 s-1 mA-2 Number of collided b.: 0 Number of e-filled b.: 0 Number of p-filled b.: 170 Number of e-pilot b.: 0 Number of p-pilot b.: 170 HERA total lumi: 0.6805 mkb-1 H1 Run total lumi: 0.4282 mkb-1 H1 data taken lumi: 0.4259 mkb-1 H1 Runs: 86253 - 86256 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 86256 - 86256 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: Not calc.% RCF Run gated: Not calc.% Relative ET trigg accept.: Not calc. 05.09.1994 ===== dice2 ======== H1KFOM === Relation Coeff.Set 6A Today it was made attempt to produce Rel. Coeff. Set for 6A data sample (from H1 Run 84297 up to H1 Run 85697). It were selected 53825 ET&PD&nVC events from this H1 Run range from data sets (only G- and M- labeled H1 Runs at H1EP): H1KFOM.ETPDNVC.M4868.C00 K30155 78048081 00001 ACS-E-C H1KFOM.ETPDNVC.M6975.C00 K19145 78048081 00001 ACS-E-C After all high mentioned 'cleaning' of 6A-data samples it were collected: 53825 events with ET&PD&nVC trigger 103028 events with ET&PD&VC trigger 38546 events with S92-trigger (PD&nVC-events). It were got 53825 ET&PD&nVC from these Runs and it were used for calibration 31099 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 1.054 1.206 0.731 1.169 0.931 1.355 1.150 0.778 1.016 0.975 1.097 1.037 1.010 0.973 1.000 0.964 1.017 0.960 1.020 0.933 0.962 1.023 1.012 0.993 0.992 1.031 0.986 1.001 1.124 1.044 1.031 1.001 1.002 1.027 1.029 1.033 0.876 1.156 1.033 0.926 0.931 1.076 0.860 1.086 0.964 0.853 0.964 1.048 0.000 ==> Relation Coeff.Set for PD 2.007 0.962 1.110 1.489 0.956 1.048 1.007 1.014 1.010 0.986 0.963 1.027 1.009 1.018 1.026 0.993 0.978 0.992 0.979 1.011 1.570 0.906 1.009 1.015 0.000 ==> Sig. at Relation Coeff.Set for ET 0.019 0.052 0.098 0.017 0.033 0.033 0.017 0.043 0.021 0.019 0.032 0.020 0.026 0.013 0.046 0.057 0.021 0.022 0.013 0.022 0.027 0.014 0.018 0.014 0.014 0.026 0.018 0.014 0.028 0.021 0.039 0.017 0.016 0.016 0.027 0.080 0.013 0.069 0.036 0.002 0.000 0.002 0.001 0.013 0.002 0.003 0.003 0.000 0.000 ==> Sig. at Relation Coeff.Set for PD 0.024 0.011 0.022 0.025 0.000 0.021 0.020 0.025 0.021 0.003 0.017 0.017 0.016 0.037 0.022 0.013 0.020 0.021 0.021 0.016 0.023 0.015 0.021 0.020 0.000 ==> Ent. at Relation Coeff.Set for ET 8 49 14 38 41 55 16 33 135 200 180 211 144 87 633 722 1047 1113 1289 1533 699 8306 13173 10599 8628 7077 5221 2197 3945 4056 2941 1856 1073 510 276 27 12 15 8 8 3 4 6 14 5 5 4 1 0 ==> Ent. at Relation Coeff.Set for PD 31 10 14 12 1 1057 2801 1821 235 7 10264 24643 17350 3222 149 3881 12408 7697 1414 67 48 37 39 8 0 As You can see all sigma values for 'hot' H1Lumi cahnnels RC histos have more or less reasonable values (may be p13,e14,e15 are more then ordinary). Runs 84297- 85697 (ET&PD&nVC-sample - near 54.0K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.44 0.99 27.41 0.96 27.50 0.95 Runs 84297- 85697 (ET&PD&VC-sample - near 103.0K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.22 1.29 27.25 1.26 As start values of Calibration Coefficients for Photoproduction Branch were got ones after 3rd step of calibration with ET&PD&nVC events from 5B-sample (H1 Runs 84026-84295 - near 12.0 K events). CCvcs value was got from last VCs calibration at 5B-sample of ETPDVC- events (the same H1 Runs range - see message from 30.08.94 at LL10). 05.09.1994 ===== dice2 ======== H1KFOM === PDREC-spectra for 6A Today it were produced 100th ntuple for S92=1 events from earlier mentioned 6A sample with events from Runs 84297-85697: H1KFOM.YLOOKQ4.R84297 (31604 entries) FAST07 3010200E 00000 DASD At interactive LOOK-session it was produced 70th histo for this data set and written into the next LOOK-binary data set: H1KFOM.BLOOKQ2.R84297 24948 entries in 70h FAST01 3010200E 00000 DASD First attempt to fit 70th histo at BLOOKQ2-data set put negative sign of Global Energy Shift at Photon Arm (-1.1%) and enough good resolution digits (17%) for energy regions 14-,16-,18-,20-35 GeV. It were prepared 100th tuples with ET&PD&nVC and ET&PD&VC-events for procedure of defining Global Energy Shifts and CCvcs: H1KFOM.YLOOKQ2.R84297 53490 entries FAST12 3010200E 00000 DASD H1KFOM.YLOOKQ3.R84297 94508 entries FAST17 3010200E 00000 DASD 05.09.1994 ==================== H1KFOM === Global Shifts,CCvcs 6A It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 1.011 for PD Channels (exept VCs), 0.9928 for ET channels. Correction factor for CCvcs is 1.12. So CCvcs = 3.380*1.12 =3.786Mev FADCcount. These digits are valid for H1Lumi events from Run 84297 up to 85697 Runs 84297- 85697 (ET&PD&nVC-sample - near 54.0K events) xetcut&vcdepcut Step Mean Sigma 0 27.52 0.95 Runs 84297- 85697 (ET&PD&VC-sample - near 103.0K events) xetcut Step Mean Sigma 0 27.52 1.30 05.09.1994 ==================== H1KFOM === New RC Sets in H1DataBase As final action of all 30.08.94 and today calibration steps it was made update of LFRC and LESC banks at H1DataBase with S.Levonyan's tool. All Relation Coefficients values, CCvcs and Global Energy Shift constants were got from the next messages at LLO: 30.08.1994 ----- dice2 -------- H1KFOM --- Relation Coeff.Set 5B 30.08.1994 -------------------- H1KFOM --- Global Shifts,CCvcs 5B 05.09.1994 ----- dice2 -------- H1KFOM --- Relation Coeff.Set 6A 05.09.1994 -------------------- H1KFOM --- Global Shifts,CCvcs 6A Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LFRC (_501) 34 e-p data 409051146 84026 84296 77 940905 H1KFOM 35 e-p data 409051148 84297 0 77 940905 H1KFOM Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LESC (_582) 43 e-p data 409051146 84026 84296 3 940905 H1KFOM 44 e-p data 409051148 84297 0 3 940905 H1KFOM 05.09.1994 ===== dice2 ======== H1KFOM === Selected H1Lumi Monitrig.. Today it were selected calibration data samples from the next data sets which were produced with standard job prepared by S.Levonyan at dice1-environment: HERA03.H01.LUMIMON.C9400076 K35033 78048081 00001 ACS-E-C ...... HERA03.H01.LUMIMON.C9400080 K43225 78048081 00001 ACS-E-C It were selected events with (s92=1 only),with ET&PD&VC=1 and with ET&PD&nVC from these data sets (as ordinary) from 656750 events: 1) S92=1 only 25725 events ( 40.8 MBytes) 2) ET&PD&VC 66207 events (109.8 MBytes) 3) ET&PD&nVC 37281 events ( 62.0 MBytes) Created data sets were saved at DESY IBM storage at the next data sets H1KFOM.ETPDNVC.M7680.C00 K35559 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M7680.C00 K21985 78048081 00001 ACS-E-C H1KFOM.S92.M7680.C00 K41440 78048081 00001 ACS-E-C These data include events from Lumi RUNs# 546-566 (H1 Runs 85697- 86219). First view on CC behaivours with time (see vectors 10022-10028,20011- -20015 at LOOK binary data set: H1KFOM.LOOKB.R85697 FAST13 3010200E 00000 DASD) presents first conclusion - this new sample of calibration data must be divided on 2 subsamples - 6B and 7A. New CCp11 jump was fixed into low direction (incrementing of p11 response) between H1 Runs 86161 and 86205 (33520th event at sample).7A-sample will be incremented with new latest events and 6B-sample is ready for calibration (H1 Runs 85697 - 86161 - near 33.5K without G- and M- labeled H1 Runs selection) 5/9/94 ======================= Fedotov === Lumi RUN# 569 Start lumi run569 date: 5/9/94 Collision time: 10:53:36 - 22:04:50 Currents (mkA): Ie= 23355.00, Ip= 37500.00 Peak luminosity: 1632.671 mb-1 s-1 Peak spec.lumi : 363.726873 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 36050.479851 mkb-1 H1 Run total lumi: 33549.8491 mkb-1 H1 data taken lumi: 28532.4676 mkb-1 H1 Runs: 86258 - 86278 HERA - physics: 34254.303692 mkb-1 H1Run - physics: 31429.403499 mkb-1 H1data - physics: 26504.99308 mkb-1 H1 Runs: 86259 - 86278 Tot curr/rate factor: 0.89% C/R F H1Run gated: 0.93% Rand.C.F: 0.79% RCF Run gated: 0.8% Relative ET trigg accept.: 0.3333 PS(lns): for R86273 (~78 Kevents) L4 histos OK; L5 absent. 6/9/94 ======================= nguyen === Lumi RUN# 570 Start lumi run570 date: 6/9/94 Collision time: 3:32:44 - 15:29:04 Currents (mkA): Ie= 25249.00, Ip= 41801.00 Peak luminosity: 2308.019 mb-1 s-1 Peak spec.lumi : 419.123306 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 52562.525502 mkb-1 H1 Run total lumi: 49781.9345 mkb-1 H1 data taken lumi: 42595.7478 mkb-1 H1 Runs: 86285 - 86302 HERA - physics: 51573.709312 mkb-1 H1Run - physics: 48403.735376 mkb-1 H1data - physics: 41251.831968 mkb-1 H1 Runs: 86286 - 86302 Tot curr/rate factor: 0.76% C/R F H1Run gated: 0.79% Rand.C.F: 0.73% RCF Run gated: 0.72% Relative ET trigg accept.: 0.3392 PS(lns): for R86291 (~74 Kevents) L4 histos OK; L5 absent. 6/9/94 ====================== theissen === Lumi RUN# 571 Start lumi run571 date: 6/9/94 Collision time: 17:49:04 - 20:03:44 Currents (mkA): Ie= 27287.00, Ip= 41000.00 Peak luminosity: 1914.822 mb-1 s-1 Peak spec.lumi : 349.624999 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 174 Number of p-filled b.: 170 Number of e-pilot b.: 21 Number of p-pilot b.: 17 HERA total lumi: 10356.1996 mkb-1 H1 Run total lumi: 8406.6712 mkb-1 H1 data taken lumi: 6655.3998 mkb-1 H1 Runs: 86327 - 86340 HERA - physics: 9222.878023 mkb-1 H1Run - physics: 6943.380443 mkb-1 H1data - physics: 5315.923529 mkb-1 H1 Runs: 86329 - 86340 Tot curr/rate factor: 0.98% C/R F H1Run gated: 1.13% Rand.C.F: 1.92% RCF Run gated: 2.07% Relative ET trigg accept.: 0.3473 PS(lns): for R86332 (~ 9 Kevents) L4 histos OK; L5 absent. 7/9/94 ======================= Fedotov === Lumi RUN# 572 Start lumi run572 date: 6/9/94 Collision time: 20:51:55 - 7:12:18 Currents (mkA): Ie= 26109.00, Ip= 40500.00 Peak luminosity: 1617.453 mb-1 s-1 Peak spec.lumi : 294.510797 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 39077.093036 mkb-1 H1 Run total lumi: 37432.5329 mkb-1 H1 data taken lumi: 34656.4623 mkb-1 H1 Runs: 86341 - 86354 HERA - physics: 37759.458276 mkb-1 H1Run - physics: 35516.510011 mkb-1 H1data - physics: 32813.686481 mkb-1 H1 Runs: 86343 - 86354 Tot curr/rate factor: 0.64% C/R F H1Run gated: 0.65% Rand.C.F: 0.9% RCF Run gated: 0.9% Relative ET trigg accept.: 0.3290 PS(lns): for R86344 (~39 Kevents) L4 absent; L5 absent. PS(lns): for R86345 (~32 Kevents) L4 histos OK; L5 absent. PS(SL): Online reconstruction was not running full day, because of the problem found in LAr module. Until it fixed, there will be of course no L5 histograms. 07.09.1994 ===== dice2 ======== H1KFOM === Relation Coeff.Set 6B Today it was made attempt to produce Rel. Coeff. Set for 6B data sample (from H1 Run 85697 up to H1 Run 86161). It were selected 30750 ET&PD&nVC events from this H1 Run range from data set (only G- and M- labeled H1 Runs at H1EP): H1KFOM.ETPDNVC.M7680.C00 K35559 78048081 00001 ACS-E-C After all high mentioned 'cleaning' of 6B-data samples it were collected: 30750 events with ET&PD&nVC trigger 52549 events with ET&PD&VC trigger 21435 events with S92-trigger (PD&nVC-events). It were got 30750 ET&PD&nVC from these Runs and it were used for calibration 16490 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 1.025 1.297 0.586 1.133 0.880 1.318 1.093 0.701 0.961 0.967 1.009 1.008 1.019 0.937 0.868 0.971 0.953 0.938 0.968 0.871 0.892 1.026 1.008 0.981 0.982 1.012 0.977 0.984 1.078 1.015 1.048 0.889 1.060 0.945 0.973 1.102 0.832 1.185 0.992 0.873 0.930 0.000 0.860 1.088 0.938 0.846 0.000 0.000 0.000 ==> Relation Coeff.Set for PD 1.952 1.018 1.118 1.443 0.000 1.012 1.010 0.987 0.999 0.982 0.984 1.045 1.026 1.052 1.033 1.045 0.996 0.995 0.992 1.007 1.557 0.928 1.020 1.055 0.000 ==> Sig. at Relation Coeff.Set for ET 0.003 0.041 0.019 0.015 0.009 0.013 0.017 0.014 0.022 0.016 0.009 0.020 0.029 0.011 0.020 0.012 0.009 0.021 0.011 0.009 0.014 0.014 0.014 0.013 0.012 0.025 0.018 0.012 0.007 0.024 0.012 0.025 0.006 0.006 0.004 0.001 0.050 0.001 0.046 0.000 0.000 0.000 0.000 0.004 0.010 0.032 0.000 0.000 0.000 ==> Sig. at Relation Coeff.Set for PD 0.015 0.011 0.028 0.008 0.000 0.013 0.019 0.019 0.012 0.006 0.018 0.018 0.016 0.036 0.007 0.019 0.023 0.026 0.116 0.040 0.009 0.026 0.010 0.023 0.000 ==> Ent. at Relation Coeff.Set for ET 4 19 8 17 14 24 8 11 50 76 87 100 75 48 173 279 350 435 438 577 297 4230 6897 5577 4398 3745 3122 1413 1875 1888 1777 912 815 359 258 11 2 5 2 2 2 0 2 6 5 4 0 0 0 ==> Ent. at Relation Coeff.Set for PD 21 10 15 10 0 398 1797 1454 246 11 5543 13109 8813 1579 77 As You can see all sigma values for 'hot' H1Lumi cahnnels RC histos have more or less reasonable values (may be p18 is more then ordinary). Runs 85697- 86161 (ET&PD&nVC-sample - near 30.8K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.46 0.96 27.48 0.94 27.51 0.92 Runs 85697- 86161 (ET&PD&VC-sample - near 53.0K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.21 1.30 27.23 1.29 As start values of Calibration Coefficients for Photoproduction Branch were got ones after 3rd step of calibration with ET&PD&nVC events from 6A-sample (H1 Runs 84297-85697 - near 50.0 K events). CCvcs value was got from last VCs calibration at 6A-sample of ETPDVC- events (the same H1 Runs range - see message from 05.09.94 at LL10). 07.09.1994 ===== dice2 ======== H1KFOM === PDREC-spectra for 6B Today it were produced 100th ntuple for S92=1 events from earlier mentioned 6B sample with events from Runs 85697-86161: H1KFOM.YLOOKQ4.R85697 (17916 entries) FAST14 3010200E 00000 DASD At interactive LOOK-session it was produced 70th histo for this data set and written into the next LOOK-binary data set: H1KFOM.BLOOKQ2.R85697 13529 entries in 70h FAST07 3010200E 00000 DASD First attempt to fit 70th histo at BLOOKQ2-data set put negative sign of Global Energy Shift at Photon Arm (-0.7%) and enough good resolution digits (17%) for energy regions 14-,16-,18-,20-35 GeV. It were prepared 100th tuples with ET&PD&nVC and ET&PD&VC-events for procedure of defining Global Energy Shifts and CCvcs: H1KFOM.YLOOKQ2.R85697 30543 entries FAST16 3010200E 00000 DASD H1KFOM.YLOOKQ3.R85697 48508 entries FAST07 3010200E 00000 DASD 07.09.1994 ==================== H1KFOM === Global Shifts,CCvcs 6B It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 1.007 for PD Channels (exept VCs), 0.9955 for ET channels. Correction factor for CCvcs is 1.164. So CCvcs = 3.786*1.164 =4.407Mev FADCcount. These digits are valid for H1Lumi events from Run 85697 up to 86161 Runs 85697- 86161 (ET&PD&nVC-sample - near 30.5K events) xetcut&vcdepcut Step Mean Sigma 0 27.52 0.94 Runs 85697- 86161 (ET&PD&VC-sample - near 52.5K events) xetcut Step Mean Sigma 0 27.53 1.34 P.S. Due to mentioned by Yu.Soloviev accidents with H1 Main Solenoid during #561 and #564th Lumi RUNs - may be it is reasonable to divide 6B-sample on less pieces (only for VC-calibration). Run 86104 - first jump and Run 86124 - second jump at CCvcs at online calibration. As seems CCvcs slowly goes to "old" value after jumps. P.S.1 - first view on subsamples shows that up to Run 86104 correction coefficient for CCvcs is 1.035(27.52 /1.22 GeV) after Run 86104 - correction coefficient for CCvcs is near 1.33 (27.52/1.29 GeV). 8/9/94 ====================== theissen === Lumi RUN# 573 Start lumi run573 date: 8/9/94 Collision time: 0:59:01 - 6:40:32 Currents (mkA): Ie= 27575.00, Ip= 40400.00 Peak luminosity: 2165.521 mb-1 s-1 Peak spec.lumi : 380.542057 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 22769.542182 mkb-1 H1 Run total lumi: 20628.0828 mkb-1 H1 data taken lumi: 18223.7618 mkb-1 H1 Runs: 86597 - 86613 HERA - physics: 22341.20701 mkb-1 H1Run - physics: 19843.121228 mkb-1 H1data - physics: 17478.499741 mkb-1 H1 Runs: 86598 - 86613 Tot curr/rate factor: 0.43% C/R F H1Run gated: 0.45% Rand.C.F: 1.06% RCF Run gated: 1.02% Relative ET trigg accept.: 0.4649 PS(lns): for R86606 (~52 Kevents) L4 histos OK; L5 absent. 08.09.1994 ==================== H1KFOM === CCvcs for 6B-subsamples CCvcs for H1Runs 85697-86103 is 3.786*1.035=3.919 MeV/FADCcount Runs 85697- 86103 (ET&PD&VC-sample - near 25.0K events) xetcut Step Mean Sigma 0 27.52 1.22 CCvcs for H1Runs 86103-86161 is 3.786*1.330=5.035 MeV/FADCcount Runs 86104- 86161 (ET&PD&VC-sample - near 11.5K events) xetcut Step Mean Sigma 0 27.52 1.29 <-- this value of sigma it is possible to explain with CCvcs changing to 'old' value during some days after accidents. 08.09.1994 ===== dice2 ======== H1KFOM === Selected H1Lumi Monitrig.. Today it were selected calibration data samples from the next data sets which were produced with standard job prepared by S.Levonyan at dice1-environment: HERA03.H01.LUMIMON.C9400081 K29638 78048081 00001 ACS-E-C ...... HERA03.H01.LUMIMON.C9400083 K18057 78048081 00001 ACS-E-C It were selected events with (s92=1 only),with ET&PD&VC=1 and with ET&PD&nVC from these data sets (as ordinary) from 387486 events: 1) S92=1 only 18202 events ( 29.0 MBytes) 2) ET&PD&VC 47049 events ( 78.1 MBytes) 3) ET&PD&nVC 28640 events ( 47.6 MBytes) Created data sets were saved at DESY IBM storage at the next data sets H1KFOM.ETPDNVC.M8183.C00 K25330 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M8183.C00 K25713 78048081 00001 ACS-E-C H1KFOM.S92.M8183.C00 K38157 78048081 00001 ACS-E-C These data include events from Lumi RUNs# 566-573 (H1 Runs 86219- 86607). First view on CC behaivours with time (see vectors 10022-10028,20011- -20015 at LOOK binary data set: H1KFOM.LOOKB.R86205 FAST07 3010200E 00000 DASD) presents first conclusion - this new sample of calibration data (7A) - from H1 Run 86205 up to 86607 can be used for calibration without any dividing on subsamples (there are no any jumps at CCp11 and CCvcs). 8/9/94 ======================= Raupach === Lumi RUN# 574 Start lumi run574 date: 8/9/94 Collision time: 8:01:55 - 17:49:44 Currents (mkA): Ie= 30185.00, Ip= 40200.00 Peak luminosity: 2328.913 mb-1 s-1 Peak spec.lumi : 379.549364 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 48255.197703 mkb-1 H1 Run total lumi: 43312.8334 mkb-1 H1 data taken lumi: 35348.4089 mkb-1 H1 Runs: 86615 - 86652 HERA - physics: 46584.090169 mkb-1 H1Run - physics: 40485.790237 mkb-1 H1data - physics: 32817.609619 mkb-1 H1 Runs: 86623 - 86652 Tot curr/rate factor: 0.63% C/R F H1Run gated: 0.63% Rand.C.F: 1.19% RCF Run gated: 1.21% Relative ET trigg accept.: 0.4758 PS(lns): for R86624 (~46 Kevents) L4 histos OK; L5 absent. 8/9/94 ======================= Raupach === Lumi RUN# 575 Start lumi run575 date: 8/9/94 Collision time: 21:17:23 - 21:52:14 Currents (mkA): Ie= 29000.00, Ip= 38700.00 Peak luminosity: 0.025 mb-1 s-1 Peak spec.lumi : 0.006784 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 1752.228436 mkb-1 H1 Run total lumi: 1752.216768 mkb-1 H1 data taken lumi: 1390.148975 mkb-1 H1 Runs: -1 - 86671 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 86671 - 86671 Tot curr/rate factor: 2.02% C/R F H1Run gated: 2.02% Rand.C.F: 3.1% RCF Run gated: 3.1% Relative ET trigg accept.: 0.4797 9/9/94 ======================= Nguyen === Lumi RUN# 576 Start lumi run576 date: 8/9/94 Collision time: 22:02:04 - 2:47:37 Currents (mkA): Ie= 26281.00, Ip= 28201.00 Peak luminosity: 961.497 mb-1 s-1 Peak spec.lumi : 304.93047 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 12510.88404 mkb-1 H1 Run total lumi: 12020.5667 mkb-1 H1 data taken lumi: 11180.9415 mkb-1 H1 Runs: 86672 - 86680 HERA - physics: 10672.23854 mkb-1 H1Run - physics: 10247.263224 mkb-1 H1data - physics: 9428.514343 mkb-1 H1 Runs: 86673 - 86680 Tot curr/rate factor: 0.59% C/R F H1Run gated: 0.6% Rand.C.F: 1.12% RCF Run gated: 1.12% Relative ET trigg accept.: 0.4255 PS(lns): WARNING: H1epRuns: 86674 - 86677 RUN# 576 : 86674=15k-;86675=20k-;86676=44k- Nevertheless for 86674;75;76 L4 and L5 histos are absent. Why,Dont know PS(lns): WARNING: Bellow seen "the spring" of "Rel.accept.": ~0.34 to ~0.46 = ~*1.36(!!!) 6/9/94 Lumi RUN# 570 Relative ET trigg accept.: 0.3392 6/9/94 Lumi RUN# 571 Relative ET trigg accept.: 0.3473 7/9/94 Lumi RUN# 572 Relative ET trigg accept.: 0.3290 8/9/94 Lumi RUN# 573 Relative ET trigg accept.: 0.4649 8/9/94 Lumi RUN# 574 Relative ET trigg accept.: 0.4758 8/9/94 Lumi RUN# 575 Relative ET trigg accept.: 0.4797 9/9/94 Lumi RUN# 576 Relative ET trigg accept.: 0.4255 09.09.1994 ===== dice2 ======== H1KFOM === Relation Coeff.Set 7A Today it was made attempt to produce Rel. Coeff. Set for 7A data sample (from H1 Run 86205 up to H1 Run 86607). It were selected 31221 ET&PD&nVC events from this H1 Run range from data set (only G- and M- labeled H1 Runs at H1EP): H1KFOM.ETPDNVC.M7680.C00 K35559 78048081 00001 ACS-E-C H1KFOM.ETPDNVC.M8183.C00 K25330 78048081 00001 ACS-E-C After all high mentioned 'cleaning' of 7A-data samples it were collected: 31221 events with ET&PD&nVC trigger 51520 events with ET&PD&VC trigger 19712 events with S92-trigger (PD&nVC-events). It were got 31221 ET&PD&nVC from these Runs and it were used for calibration 15417 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 1.022 1.344 0.559 1.100 0.857 1.299 1.066 0.659 0.971 0.920 0.927 0.963 0.900 0.909 0.918 0.910 0.860 0.865 0.886 0.851 0.856 1.011 0.987 0.983 0.959 0.991 0.944 0.952 1.093 1.022 1.042 0.927 1.031 0.971 0.988 1.106 0.783 1.182 1.012 0.871 0.000 1.080 0.861 1.084 0.925 0.814 0.000 0.000 0.000 ==> Relation Coeff.Set for PD 1.919 0.997 1.161 1.453 0.000 1.037 1.049 1.034 1.047 0.978 0.998 1.059 1.040 1.049 1.031 1.062 1.060 1.031 1.098 1.047 1.532 0.909 1.077 1.020 0.000 ==> Sig. at Relation Coeff.Set for ET 0.001 0.008 0.001 0.006 0.003 0.003 0.002 0.011 0.003 0.006 0.007 0.006 0.013 0.002 0.005 0.007 0.011 0.006 0.010 0.013 0.009 0.013 0.014 0.012 0.013 0.019 0.017 0.011 0.004 0.013 0.007 0.014 0.005 0.004 0.003 0.001 0.005 0.013 0.004 0.001 0.000 0.000 0.000 0.000 0.002 0.019 0.000 0.000 0.000 ==> Sig. at Relation Coeff.Set for PD 0.010 0.002 0.002 0.000 0.000 0.009 0.015 0.014 0.022 0.002 0.023 0.018 0.015 0.023 0.005 0.015 0.021 0.022 0.047 0.008 0.002 0.011 0.013 0.004 0.000 ==> Ent. at Relation Coeff.Set for ET 2 10 6 17 22 16 4 8 42 63 59 79 46 30 188 241 320 338 376 519 229 4022 6483 5210 4329 3645 2811 1197 1709 1919 1590 1105 899 413 257 11 2 5 6 3 0 1 3 5 3 2 0 0 0 ==> Ent. at Relation Coeff.Set for PD As You can see all sigma values for 'hot' H1Lumi cahnnels RC histos have more or less reasonable values (may be p18 is more then ordinary). Runs 86205- 86607 (ET&PD&nVC-sample - near 31.2K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.39 1.01 27.44 0.99 27.41 0.99 Runs 86205- 86607 (ET&PD&VC-sample - near 51.5K events) all events xetcut Step Mean Sigma Mean Sigma 3 ??.?? ?.?? 27.70 1.36 As start values of Calibration Coefficients for Photoproduction Branch were got ones after 3rd step of calibration with ET&PD&nVC events from 6B-sample (H1 Runs 85697-86191 - near 30.5 K events). CCvcs value was got from last VCs calibration at 6B-sample of ETPDVC- events (H1Runs 86104-86161 - see message from 08.09.94 at LL10). (CCvcs start = 5.075 MeV/FADCcount). As seems start value was got on near 7% more then needed (really due to 'drift' of CCvcs to 'old'(before accident) value CCvcs became less then 5.075). I was surprized with bad resolution digits (Sigmas) at ET&PD&nVC sample. As seems this effect of Yura Soloviev mentioned accidents with H1 main Solenoid and (may be) at OnLine histos at this period resolution digits were 'bad' too? 09.09.1994 ===== dice2 ======== H1KFOM === PDREC-spectra for 7A Today it were produced 100th ntuple for S92=1 events from earlier mentioned 7A sample with events from Runs 86205-86607: H1KFOM.YLOOKQ4.R86205 (16944 entries) FAST01 3010200E 00000 DASD At interactive LOOK-session it was produced 70th histo for this data set and written into the next LOOK-binary data set: H1KFOM.BLOOKQ2.R86205 11599 entries in 70h FAST04 3010200E 00000 DASD First attempt to fit 70th histo at BLOOKQ2-data set put positive sign of Global Energy Shift at Photon Arm (+1.0%) and enough good resolution digits (17%) only for energy region 22-35 GeV.All another energy regions had bad fit results (as seems bad fit result at all). It were prepared 100th tuples with ET&PD&nVC and ET&PD&VC-events for procedure of defining Global Energy Shifts and CCvcs: H1KFOM.YLOOKQ2.R86205 30995 entries FAST13 3010200E 00000 DASD H1KFOM.YLOOKQ3.R86205 48237 entries FAST14 3010200E 00000 DASD 09.09.1994 ==================== H1KFOM === Global Shifts,CCvcs 7A It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 0.990 for PD Channels (exept VCs), 1.0157 for ET channels. Correction factor for CCvcs is 1.070. So CCvcs = 5.075*1.070 =5.430Mev FADCcount. These digits are valid for H1Lumi events from Run 86205 up to 86607 Runs 86205- 86607 (ET&PD&nVC-sample - near 31.2K events) xetcut&vcdepcut Step Mean Sigma 0 27.51 1.00 Runs 86205- 86607 (ET&PD&VC-sample - near 51.5K events) xetcut Step Mean Sigma 0 27.51 1.31 9/9/94 ======================== F11LEV === Lumi RUN# 577 Start lumi run577 date: 9/9/94 Collision time: 10:14:40 - 21:23:34 Currents (mkA): Ie= 24164.00, Ip= 31201.00 Peak luminosity: 889.474 mb-1 s-1 Peak spec.lumi : 391.212753 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 37367.783265 mkb-1 H1 Run total lumi: 36774.449 mkb-1 H1 data taken lumi: 33923.2403 mkb-1 H1 Runs: 86702 - 86715 HERA - physics: 37310.73031 mkb-1 H1Run - physics: 36747.2898 mkb-1 H1data - physics: 33898.7106 mkb-1 H1 Runs: 86707 - 86715 Tot curr/rate factor: 1.36% C/R F H1Run gated: 1.35% Rand.C.F: 0.7% RCF Run gated: 0.7% Relative ET trigg accept.: 0.5142 PS(lns): for R86709 (~15 Kevents) L4 histos OK; L5 absent. PS(lns): WARNING: The so called "Rel.accept." increased even more, see up & #576.STRANGE. Small warning: Ratio (VC/VCtrig) decreased from ~10^1.5 to ~10^1. 10/9/94 ======================= Semenov === Lumi RUN# 578 Start lumi run578 date: 10/9/94 Collision time: 0:37:06 - 10:36:10 Currents (mkA): Ie= 22119.00, Ip= 30500.00 Peak luminosity: 1329.348 mb-1 s-1 Peak spec.lumi : 379.491688 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 28885.068808 mkb-1 H1 Run total lumi: 27593.4468 mkb-1 H1 data taken lumi: 24812.9424 mkb-1 H1 Runs: 86720 - 86741 HERA - physics: 27649.423143 mkb-1 H1Run - physics: 25883.79361 mkb-1 H1data - physics: 23197.608292 mkb-1 H1 Runs: 86722 - 86741 Tot curr/rate factor: 0.92% C/R F H1Run gated: 0.94% Rand.C.F: 0.83% RCF Run gated: 0.84% Relative ET trigg accept.: 0.4976 PS(lns): for R86723 (~25 Kevents) L4 histos and L5 absent. PS(lns): for R86725 (~55 Kevents) L4 histos OK; L5 absent. Small warning: Ratio (VC/VCtrig) came back to ~10^2. 10.09.1994 ==================== H1KSOL === LRTL missing.... During Start of Lumi Run 579 - H1 Runs 86754-86756 - there was no LRTL banks in data flow. After rebooting of FIC1 by shift crew (according to manual) - OK since Run 86757. P.S. (S.L.) Lumi information in the database for these runs is recovered from the raw data (LRTN banks) 10.09.1994 ==================== F11LEV === LUMI banks errors ........ To remind you (mainly Fomenko and myself): there is a special routine running at L5, which checks all bank formats and contents. Today two new cases of wrong data from LUMI system have been reported to me: LRTS bank and LRTN bank. Together with already known problems, we have 3 banks with permanent errors in the structure and one with the occasional error (?) in the content: LRPE - wrong # of rows in subheader VETE - wrong # of rows in subheader LRTS - #col and #rows are exchanged in subheader LRTN - occasionaly, content of col.12 (trigger energy sum ET+PD) appears greater than the limit given in DDL (5001) e.g. in the run 86758 there were 3 cases: 6321,5603,6094 (reminder: these are energies in units 10 MeV) It was supposed, that it never can be larger than ~4400. Special cases 5000 and 5001 were reserved for the overflow and zero pedestal situations. 10/9/94 ==================== Botterweck === Lumi RUN# 579 Start lumi run579 date: 10/9/94 Collision time: 14:45:52 - 22:57:08 Currents (mkA): Ie= 23700.00, Ip= 35100.00 Peak luminosity: 2013.759 mb-1 s-1 Peak spec.lumi : 459.498904 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 36754.593336 mkb-1 + 3062.0 mkb-1 (see P.S.) H1 Run total lumi: 34413.41081 mkb-1 H1 data taken lumi: 31355.652248 mkb-1 H1 Runs: 86753 - 86776 HERA - physics: 35565.125256 mkb-1 + 3062.0 mkb-1 (see P.S.) H1Run - physics: 32670.159578 mkb-1 H1data - physics: 29639.11619 mkb-1 H1 Runs: 86754 - 86776 Tot curr/rate factor: 1.07% C/R F H1Run gated: 1.09% Rand.C.F: 0.81% RCF Run gated: 0.82% Relative ET trigg accept.: 0.4977 PS(lns): for R86758 (~64 Kevents): L4 histos OK; L5 absent. P.S. (S.L.) There was no lumi measurement during one hour in the middle of the run. The reason - crashed Central Trigger. Missing HERA produced/delivered luminosity was estimated from SHOWLUMI picture with the precision ~2% (3.06 nb-1) 11/9/94 ======================= Fedotov === Lumi RUN# 580 Start lumi run580 date: 11/9/94 Collision time: 6:36:06 - 18:06:05 Currents (mkA): Ie= 28404.00, Ip= 33601.00 Peak luminosity: 2151.257 mb-1 s-1 Peak spec.lumi : 430.3806 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 53960.538577 mkb-1 H1 Run total lumi: 52320.681476 mkb-1 H1 data taken lumi: 48338.670474 mkb-1 H1 Runs: 86790 - 86807 HERA - physics: 52529.878021 mkb-1 H1Run - physics: 49581.709345 mkb-1 H1data - physics: 45774.180071 mkb-1 H1 Runs: 86793 - 86807 Tot curr/rate factor: 0.87% C/R F H1Run gated: 0.87% Rand.C.F: 0.93% RCF Run gated: 0.92% Relative ET trigg accept.: 0.4897 PS(lns): for R86798 (~90 Kevents): L4 histos OK; L5 absent. 11/9/94 ======================= h1klap === Lumi RUN# 581 Start lumi run581 date: 11/9/94 Collision time: 21:06:41 - 23:31:53 Currents (mkA): Ie= 27141.00, Ip= 33100.00 Peak luminosity: 701.728 mb-1 s-1 Peak spec.lumi : 153.565904 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 8345.875121 mkb-1 H1 Run total lumi: 7486.84143 mkb-1 H1 data taken lumi: 6765.036988 mkb-1 H1 Runs: 86815 - 86821 HERA - physics: 7308.647935 mkb-1 H1Run - physics: 6392.417239 mkb-1 H1data - physics: 5879.544256 mkb-1 H1 Runs: 86816 - 86821 Tot curr/rate factor: 2.22% C/R F H1Run gated: 2.13% Rand.C.F: 23.07% RCF Run gated: 19.97% Relative ET trigg accept.: 0.4778 PS(lns): for R86816 both L4, and L5 histos are absent, Why? PS(lns): for R86821 both L4, and L5 histos are absent, Why? PS(S.L.) L4 are missing in case of Run was aborted instead of Stopped L5 are missing because online rec. is behind the data taking Comment : At the beginning of the Lumi Run HERA lost the steering of e+ beam (as got clear later) and photon beam was completely out of PD geom. acc. Only 1.5 hour later HERA succeed to steer e+ beam. Since 21.10 till 22.40 there was no Lumi in H1 IP. During that period we get again crazy rates on our detectors: about 1 MHz - VETO, 800 KHz - PD and so on. VETO responce went down again by factor 2.(YuS) 12.09.1994 ==================== H1KFOM === LUMIMON Data Set Absence Today it was found that one of LUMIMON-data sets HERA03.H01.LUMIMON.C9400084 is absent at IBM cartridges. Next data sets-C are presented at HERA03-catalog: HERA03.H01.LUMIMON.C9400085 K23400 78048081 00001 ACS-E-C HERA03.H01.LUMIMON.C9400086 K31812 78048081 00001 ACS-E-C HERA03.H01.LUMIMON.C9400087 K29884 78048081 00001 ACS-E-C P.S. (S.L.) The file is now on IBM. The reason was: problem with ultranet connection from dice to IBM at the time when this file was completed by data logging job. 12.09.1994 ===== dice2 ======== H1KFOM === Selected H1Lumi Monitrig.. Today it were selected calibration data samples from the next data sets which were produced with standard job prepared by S.Levonyan at dice1-environment: HERA03.H01.LUMIMON.C9400084 K44066 78048081 00001 ACS-E-C ...... HERA03.H01.LUMIMON.C9400087 K29884 78048081 00001 ACS-E-C It were selected events with (s92=1 only),with ET&PD&VC=1 and with ET&PD&nVC from these data sets (as ordinary) from 516901 events: 1) S92=1 only 23728 events ( 37.7 MBytes) 2) ET&PD&VC 60577 events (100.5 MBytes) 3) ET&PD&nVC 36393 events ( 60.5 MBytes) Created data sets were saved at DESY IBM storage at the next data sets H1KFOM.ETPDNVC.M8487.C00 K21684 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M8487.C00 K21689 78048081 00001 ACS-E-C H1KFOM.S92.M8487.C00 K21853 78048081 00001 ACS-E-C These data include events from Lumi RUNs# 573-580 (H1 Runs 86607- 86799). 12/9/94 ======================= charles === Lumi RUN# 582 Start lumi run582 date: 12/9/94 Collision time: 9:20:28 - 11:20:03 Currents (mkA): Ie= 28908.00, Ip= 40800.00 Peak luminosity: 2563.845 mb-1 s-1 Peak spec.lumi : 428.295292 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 13176.822652 mkb-1 H1 Run total lumi: 11105.596943 mkb-1 H1 data taken lumi: 8455.197287 mkb-1 H1 Runs: 86839 - 86849 HERA - physics: 11902.339326 mkb-1 H1Run - physics: 9650.461979 mkb-1 H1data - physics: 7199.740106 mkb-1 H1 Runs: 86840 - 86849 Tot curr/rate factor: 1.3% C/R F H1Run gated: 1.42% Rand.C.F: 1.47% RCF Run gated: 1.44% Relative ET trigg accept.: 0.5238 PS(LNS): for R86848 (~31 Kevents): L4 histos OK; L5 absent. 13.09.1994 ===== dice2 ======== H1KFOM === Relation Coeff.Set 7B(??) Today it was made attempt to produce Rel. Coeff. Set for 7B data sample (from H1 Run 86607 up to H1 Run 86799). It were selected 35315 ET&PD&nVC events from this H1 Run range from data set (only G- and M- labeled H1 Runs at H1EP): H1KFOM.ETPDNVC.M8487.C00 K21684 78048081 00001 ACS-E-C After all high mentioned 'cleaning' of 7B-data samples it were collected: 35315 events with ET&PD&nVC trigger 58709 events with ET&PD&VC trigger 23110 events with S92-trigger (PD&nVC-events). It were got 35315 ET&PD&nVC from these Runs and it were used for calibration 16665 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 1.023 1.368 0.563 1.050 0.859 1.269 1.085 0.597 0.925 0.943 1.013 0.980 0.871 0.948 0.959 1.007 0.972 0.979 0.964 0.912 0.857 1.020 1.000 1.002 0.998 1.028 0.981 0.990 1.154 1.010 1.086 0.939 0.959 0.942 0.996 1.109 0.774 1.159 0.998 0.849 0.936 1.080 0.861 1.062 0.000 0.828 0.961 1.047 0.000 ==> Relation Coeff.Set for PD 1.903 0.968 1.130 1.450 0.947 1.043 1.006 1.002 1.066 0.993 0.968 1.036 1.018 1.019 1.080 1.051 1.006 1.041 0.932 1.056 1.520 1.003 1.149 1.030 0.925 ==> Sig. at Relation Coeff.Set for ET 0.000 0.018 0.002 0.008 0.007 0.006 0.022 0.030 0.007 0.011 0.019 0.021 0.017 0.008 0.022 0.013 0.016 0.004 0.026 0.006 0.009 0.016 0.015 0.018 0.012 0.017 0.018 0.011 0.005 0.013 0.008 0.005 0.012 0.011 0.006 0.000 0.008 0.008 0.003 0.006 0.000 0.001 0.000 0.000 0.000 0.000 0.000 0.000 0.000 ==> Sig. at Relation Coeff.Set for PD 0.003 0.009 0.008 0.003 0.002 0.006 0.018 0.020 0.017 0.005 0.015 0.016 0.016 0.042 0.014 0.022 0.021 0.029 0.019 0.033 0.009 0.021 0.026 0.011 0.000 ==> Ent. at Relation Coeff.Set for ET 6 26 6 11 13 12 7 9 43 72 37 62 46 29 183 323 337 415 358 469 199 4475 6968 5644 4723 3819 2975 1333 2087 1997 1898 1017 684 422 288 13 3 4 8 4 1 3 1 2 0 1 1 1 0 ==> Ent. at Relation Coeff.Set for PD 16 10 11 7 2 388 1875 1790 385 17 5885 13597 9090 1700 71 2602 5790 2634 288 10 34 32 17 4 1 As You can see all sigma values for 'hot' H1Lumi cahnnels RC histos have more or less reasonable values (may be p13 is more then ordinary). Runs 86607- 86799 (ET&PD&nVC-sample - near 35.1K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.42 1.06 27.45 1.03 27.43 1.01 Runs 86607- 86799 (ET&PD&VC-sample - near 58.7K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.84 1.57 27.90 1.52 As start values of Calibration Coefficients for Photoproduction Branch were got ones after 3rd step of calibration with ET&PD&nVC events from 7A-sample (H1 Runs 86205-86607 - near 31.2 K events). CCvcs value was got from last VCs calibration at 7A-sample of ETPDVC- events (H1Runs 86205-86607 - see message from 10.09.94 at LL10). (CCvcs start = 5.430 MeV/FADCcount). There are 'bad' resolution digits again at 7B-sample of events. As seems this effect seen due to accidents with overloading of VC at begin of Septemeber. Can anybody proclaim at LLO which Sigmas are seen at OnLine ETrec+PDrec histos for ET&PD&nVC sample? the same 'bad'? Attempt to make fit of PhotonArm Energy spectrum is almost unsucces- ful (with more or less good statistics). May be something happened not only with VC Photomultiplier but with some from PD-cells photo- multipliers due to PD&nVC spectrum is bad? 13.09.1994 ===== dice2 ======== H1KFOM === PDREC-spectra for 7B(???) Today it were produced 100th ntuple for S92=1 events from earlier mentioned 7B sample with events from Runs 86607-86799: H1KFOM.YLOOKQ4.R86607 (19248 entries) FAST12 3010200E 00000 DASD At interactive LOOK-session it was produced 70th histo for this data set and written into the next LOOK-binary data set: H1KFOM.BLOOKQ2.R86607 12921 entries in 70h FAST16 3010200E 00000 DASD First attempt to fit 70th histo at BLOOKQ2-data set put positive sign of Global Energy Shift at Photon Arm (+0.2%) and enough good resolution digits (17%) only for energy region 24-35 GeV.All another energy regions had bad fit results (as seems bad fit result again). It were prepared 100th tuples with ET&PD&nVC and ET&PD&VC-events for procedure of defining Global Energy Shifts and CCvcs: H1KFOM.YLOOKQ2.R86607 35083 entries FAST16 3010200E 00000 DASD H1KFOM.YLOOKQ3.R86607 54688 entries FAST14 3010200E 00000 DASD 13.09.1994 ==================== H1KFOM === Global Shifts,CCvcs 7B(??) It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 1.000 for PD Channels (exept VCs), 1.0095 for ET channels. Correction factor for CCvcs is 0.825. So CCvcs = 5.430*0.825 =4.480Mev FADCcount. These digits are valid for H1Lumi events from Run 86607 up to 86799 Runs 86607- 86799 (ET&PD&nVC-sample - near 35.3K events) xetcut&vcdepcut Step Mean Sigma 0 27.52 1.03 Runs 86607- 86799 (ET&PD&VC-sample - near 58.7K events) xetcut Step Mean Sigma 0 27.51 1.36 13/9/94 ======================= h1kshe === Lumi RUN# 583 Start lumi run583 date: 13/9/94 Collision time: 5:54:33 - 14:27:00 Currents (mkA): Ie= 28478.00, Ip= 46201.00 Peak luminosity: 2481.062 mb-1 s-1 Peak spec.lumi : 396.368518 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 52276.3793 mkb-1 H1 Run total lumi: 50458.8076 mkb-1 H1 data taken lumi: 44620.4536 mkb-1 H1 Runs: 86922 - 86935 HERA - physics: 46080.001485 mkb-1 H1Run - physics: 43645.732142 mkb-1 H1data - physics: 37925.120734 mkb-1 H1 Runs: 86924 - 86935 Tot curr/rate factor: 1.4% C/R F H1Run gated: 1.41% Rand.C.F: 0.83% RCF Run gated: 0.83% Relative ET trigg accept.: 0.5134 PS(LNS): for R86926 (~23 Kevents): L4 histos OK; L5 absent. 13.09.1994 ==================== H1KFOM === New RC Sets in H1DataBase As final action of all 07-13.09.94 calibration steps it was made update of LFRC and LESC banks at H1DataBase with S.Levonyan's tool. All Relation Coefficients values, CCvcs and Global Energy Shift constants were got from the next messages at LLO: 07.09.1994 ----- dice2 -------- H1KFOM --- Relation Coeff.Set 6B 07.09.1994 -------------------- H1KFOM --- Global Shifts,CCvcs 6B 08.09.1994 -------------------- H1KFOM --- CCvcs for 6B-subsamples 09.09.1994 ----- dice2 -------- H1KFOM --- Relation Coeff.Set 7A 09.09.1994 -------------------- H1KFOM --- Global Shifts,CCvcs 7A 13.09.1994 ----- dice2 -------- H1KFOM --- Relation Coeff.Set 7B(??) 13.09.1994 ----- dice2 -------- H1KFOM --- PDREC-spectra for 7B(???) 13.09.1994 -------------------- H1KFOM --- Global Shifts,CCvcs 7B(??) Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LFRC (_501) 36 e-p data 409131418 85697 86103 77 940913 H1KFOM 37* e-p data 409131421 86104 86204 77 940913 H1KFOM 38 e-p data 409131424 86205 86606 77 940913 H1KFOM 39 e-p data 409131427 86607 0 77 940913 H1KFOM Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LESC (_582) 45 e-p data 409131418 85697 86103 3 940913 H1KFOM 45 e-p data 409131421 86104 86204 3 940913 H1KFOM 46 e-p data 409131424 86205 86606 3 940913 H1KFOM 47 e-p data 409131427 86607 0 3 940913 H1KFOM P.S. As seems something is wrong (or non-standard) due to appearence 37* (so called delta bank) and twice numered 45th LESC-bank. P.S. (S.L.) See my mails to you for the explanation of these two facts and act accordingly. Do it carefully! In case of questions better ask immediately: H1 database is very "delicate" thing. 13.09.1994 ==================== F11LEV === LMONI94 files ............ Thanks to the heroic effort of Nelly Gogitidze and Sasha Fomenko, most of our lumi monitoring events from the first part of the e-p data 1994 were not lost, but carefully selected (before automatic LUMIMON selection was available). These events were finally compressed to 13 IBM cartridges: F11LEV.LMONI94.A00-A12 and can be used for the analysis. The files contain in total 1.582.433 events from the H1 run range 76846-79840 (~ 1/2 of one run 76856 is missing). They correspond to the following luminosity (online estimate): RQ Total lumi [nb-1] H1 gated [nb-1] G 201.046616 140.007736 M 56.3381195 40.3113708 P 22.1691742 15.4924974 ? 0.427378118 0.407615066 -------------------------------------------- SUM 279.980713 196.219208 -------------------------------------------- First and most important use: offline correction to the lumi value for this period, using sub-samples s91 (PD_low) and s93 (VC). 14/9/94 ======================= semenov === Lumi RUN# 584 Start lumi run584 date: 13/9/94 Collision time: 17:06:41 - 3:40:48 Currents (mkA): Ie= 27000.00, Ip= 43800.00 Peak luminosity: 2066.043 mb-1 s-1 Peak spec.lumi : 337.905926 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 46457.83656 mkb-1 H1 Run total lumi: 44278.779 mkb-1 H1 data taken lumi: 38416.4118 mkb-1 H1 Runs: 86944 - 86963 HERA - physics: 45388.590934 mkb-1 H1Run - physics: 42772.839136 mkb-1 H1data - physics: 36973.269499 mkb-1 H1 Runs: 86946 - 86963 Tot curr/rate factor: 1.31% C/R F H1Run gated: 1.31% Rand.C.F: 0.7% RCF Run gated: 0.7% Relative ET trigg accept.: 0.5252 PS(LNS): for R86952 (~57 Kevents): L4 histos OK; L5 absent. Small Warning: Picture of VC/VCtriggered changed, VCtrig went to right. 14/9/94 ======================= semenov === Lumi RUN# 585 Start lumi run585 date: 14/9/94 Collision time: 5:44:49 - 9:28:09 Currents (mkA): Ie= 27348.00, Ip= 40001.00 Peak luminosity: 1867.644 mb-1 s-1 Peak spec.lumi : 341.733067 mb-1 s-1 mA-2 Number of collided b.: 154 Number of e-filled b.: 170 Number of p-filled b.: 170 Number of e-pilot b.: 16 Number of p-pilot b.: 16 HERA total lumi: 19693.1693 mkb-1 H1 Run total lumi: 18274.0636 mkb-1 H1 data taken lumi: 15587.2679 mkb-1 H1 Runs: 86963 - 86975 HERA - physics: 16723.400694 mkb-1 H1Run - physics: 15034.283395 mkb-1 H1data - physics: 12413.889285 mkb-1 H1 Runs: 86964 - 86975 Tot curr/rate factor: 2.86% C/R F H1Run gated: 2.93% Rand.C.F: 1.33% RCF Run gated: 1.34% Relative ET trigg accept.: 0.5460 PS(LNS): for R86967 (~12 Kevents): L4 histos OK; L5 absent. Small Warning: Picture of VC/VCtriggered changed, the same as prev.run. 15.09.1994 ==================== H01GOG === LMONI94 data reprocessing As a first step for the offline lumi estimate procedure for the runs 76846-79840 (25/05 - 22/06), all s91 and s93 events from the files F11LEV.LMONI94.A00-A12, announced in LLO 13.09.94 by F11LEV, were selected and reprocessed by LREC with latest CC from database. Output LOOK files H01GOG.NLOOK.LMONI94.xxxxxx, created by the job H01GOG.NELRUN94.S(#LMONI3) will be used to obtain final result, similar to how it was done in July-August for the second part of e-p data. 15.09.1994 ==================== H01GOG === LUMIMON data processing Here comes a summary table for e+p LUMIMON files, processed so far. Three latest existing LUMIMON files (88,89,90) are being processed now. For monitrigs from e-p files see my early messages in LL9. Sorry for some delay: graphics from Moscow is sometimes difficult. ---------------------------------------------------------------------- File H1 runs Events Actual triggers (xx) s86 s91 s92 s93 s94 s95 ---------------------------------------------------------------------- 38 82343-82979 47952 7410 9253 5631 12286 5467 6459 39-51 82979-83014 no G+M data; some test and special dedicated runs ---------------------------------------------------------------------- 52 83014-83244 66878 22684 9159 830 18235 964 1745 53 83244-83386 65969 7729 3745 1751 4474 2121 3860 54 83386-83397 65921 5740 3802 2002 5292 2286 4195 55 83397-83449 65752 6038 4274 2394 6466 2694 4988 56 83449-83499 65395 7185 3609 2078 4467 2503 4336 57 83499-83771 65881 7437 4064 2470 6048 2718 4965 58 83771-83828 66627 15156 4757 2233 7588 2392 4598 59 83828-83844 65608 11435 4401 2648 6737 2898 4909 60 83844-83977 65886 13601 4307 2344 4818 2854 4846 61 83977-84023 65752 5880 3482 2170 4776 2500 4348 62 84023-84028 65200 3171 4033 2716 6011 2869 5119 63 84028-84044 65217 8284 4522 3212 6296 3460 5827 64 84044-84075 65184 8432 3024 2481 3932 2642 3993 65 84075-84287 66694 6346 3195 2413 3774 2284 3703 66 84287-84306 65767 9652 3204 2553 3918 2428 3935 > 67 84297-84398 130942 13499 7235 6037 8707 5987 8830 68 84398-84585 154084 15969 18918 4005 35727 3863 6497 69 84585-84793 131360 11477 7969 5339 9257 5342 8870 70 84793-85010 131644 17426 11284 5182 10109 5199 8701 > 71 84891-85056 124856 9898 8201 6083 11341 6137 10364 72 85056-85166 131278 16085 7822 5909 10581 5932 7992 73 85166-85286 131840 12275 5755 4406 7877 4399 7254 74 85286-85642 131771 13066 8300 6432 11206 6476 9748 75 85642-85697 130499 12294 7244 5482 10840 5497 9199 76 85697-85946 130686 9790 6974 5174 10353 5216 8785 77 85946-86065 129899 13534 8292 6308 12519 6358 10530 78 86065-86112 132193 9933 6482 4910 9399 4766 8107 79 86112-86146 132193 9933 6482 4910 9399 4766 8107 80 86146-86219 129320 10037 6779 6507 10093 7066 10333 81 86219-86277 129121 10539 5995 6261 11156 7086 10923 82 86277-86332 128987 10092 6187 6414 11417 7254 11324 83 86332-86607 129378 15210 5175 5500 9178 6157 9321 84 86607-86671 129695 11887 4881 4914 8401 5523 8485 85 86671-86714 129397 14772 6194 5972 11527 6710 10373 86 86714-86759 128945 13374 6228 6117 10795 6922 10558 87 86759-86799 128864 10875 6316 6081 10952 6961 10879 ---------------------------------------------------------------------- Corresponding n-tuples NT(1) have been created and stored in LOOK files: H01GOG.MLOOK.C94000xx First simple observations: -------------------------- 1) Two files labelled by > (67 and 71) contain runs coming in a wrong order. After check in H1RUN pinboard this was associated with the cases, when data were recorded to the Storage TeK. Therefore they appear in the SGI logging after some later runs. 2) Warning! The shape of the energy spectra at ET for eTAG monitor sample (s86) is significantly varying in time. According to S.Levonian, this was not the case in 1992 and 1993. 3) The peak in x_PD distribution at -2cm due to the famous (noisy?) channel PD(11) is ABSENT in the run ranges: [84028 - 84306] and [86219 - 86799] 15/9/94 ======================= charles === Lumi RUN# 586 Start lumi run586 date: 14/9/94 Collision time: 19:04:48 - 6:06:06 Currents (mkA): Ie= 26832.00, Ip= 51400.00 Peak luminosity: 3059.096 mb-1 s-1 Peak spec.lumi : 422.393353 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 67402.107791 mkb-1 H1 Run total lumi: 60893.5984 mkb-1 H1 data taken lumi: 52879.4879 mkb-1 H1 Runs: 87031 - 87060 HERA - physics: 66339.973233 mkb-1 H1Run - physics: 59434.40431 mkb-1 H1data - physics: 51551.440289 mkb-1 H1 Runs: 87032 - 87060 Tot curr/rate factor: 1.29% C/R F H1Run gated: 1.33% Rand.C.F: 0.65% RCF Run gated: 0.62% Relative ET trigg accept.: 0.4732 PS(LNS): for R87049 (~19 Kevents): L4 histos OK; L5 OK, too. Small Warning: Picture of VC/VCtriggered changed, the same as prev.run. 15.09.1994 ==================== F11LEV === VC-trigger bit status..... After more detailed investigation, a suspition, described in my message from 11.08.94 has been confirmed: present VC-bit once being set stays typically more than one BC, sometimes up to 11 (!) This was not the case in 1993 (checked with the real data). Igor gave a detailed explanation why it happened. He also changed the VC-bit 2 days ago after preliminary agreement with me. I asked him, and repeat my request agan, to write in LLO when exactly the change was made, and what does this change mean. This may explain a "warning" from L.N.S.: we expect new VC to be "less efficient" at low energies due to higher threshold, but more stable agains noise and junk, and have better "timing" (not extend for so many consequtive bunches) P.S. As seems distinct description of VC-status changing is needed for calibration data sample choice. For me it is needed to know from which Run (or from which time) this changing was made. Is this changing valid for both subbranches ("Lumi","Photopr")? nVC at s92 is changing too? etc.(a.f.) 15.09.1994 ===== dice2 ======== H1KFOM === Selected H1Lumi Monitrig.. Today it were selected calibration data samples from the next data sets which were produced with standard job prepared by S.Levonyan at dice1-environment: HERA03.H01.LUMIMON.C9400088 K33134 78048081 00001 ACS-E-C ...... HERA03.H01.LUMIMON.C9400090 K41809 78048081 00001 ACS-E-C It were selected events with (s92=1 only),with ET&PD&VC=1 and with ET&PD&nVC from these data sets (as ordinary) from 386613 events: 1) S92=1 only 19361 events ( 30.8 MBytes) 2) ET&PD&VC 44117 events ( 73.3 MBytes) 3) ET&PD&nVC 31007 events ( 51.6 MBytes) Created data sets were saved at DESY IBM storage at the next data sets H1KFOM.ETPDNVC.M8890.C00 K30673 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M8890.C00 K30847 78048081 00001 ACS-E-C H1KFOM.S92.M8890.C00 K34003 78048081 00001 ACS-E-C These data include events from Lumi RUNs# 580-586 (H1 Runs 86799- 87054). 15.09.1994 ==================== H1Kshe === VC-trigger bit status..... After detailed comparison of the online histos there were not found any big disadvantageous for using VCv1(see LUTR descr.) trigg.bit instead of VC. But so called overlaping effect for neihgbour BC must disappear due to different H/W logic for VCv1 The only small disadvantage is that the threshold for VCv1 will be on 40% more with respect to VC. Reboot of the trigger LUT was made between lumi Runs 583 and 584, so since h1run # 86944 ------------------- we have statistic for new trigg set. For Photopr. branch the bits exchenge was made everywhere, but for lumi in the calib- ration trigger only. Question: What about VC-trigger bit status for 2nd calibration trigger at Lumi-subbranch (ET&PD&VC)? Was it changed too on VCv1? (a.f.) 15/9/94 ======================= semenov === Lumi RUN# 587 Start lumi run587 date: 15/9/94 Collision time: 12:06:11 - 17:05:40 Currents (mkA): Ie= 32029.00, Ip= 46600.00 Peak luminosity: 2242.08 mb-1 s-1 Peak spec.lumi : 288.373571 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 32598.509659 mkb-1 H1 Run total lumi: 27386.6933 mkb-1 H1 data taken lumi: 17963.5821 mkb-1 H1 Runs: 87091 - 87102 HERA - physics: 31533.986584 mkb-1 H1Run - physics: 25373.687821 mkb-1 H1data - physics: 16498.261956 mkb-1 H1 Runs: 87092 - 87102 Tot curr/rate factor: 1.06% C/R F H1Run gated: 1.08% Rand.C.F: 1.35% RCF Run gated: 1.37% Relative ET trigg accept.: 0.4928 PS(LNS): for R87094 (~69 Kevents): L4 histos OK; L5 absent. Small Warning: Picture of VC/VCtriggered changed, probably for ever. 16.09.1994 ==================== F11LEV === VC-trigger bit status..... I have checked offline a present situation with VC trigger bit using lumi monitoring events from the last available file LUMIMON.C9400090 (H1 runs >= 86955). Our expectations were confirmed: 1) effective VC threshold increased on ~30% and "plateau" of the efficiency curve went down from ~0.87 to ~0.80. Since there should be NO influence from the threshold to the asymptotic value of the plateau, this means, that indeed, ca. 7-8% of VC-efficiency were "false", i.e. VC efficiency before this change was overestimated for high E(gamma) 2) "timing" becomes much better (practically perfect) - the effect described 11.08 and 15.09 disappeared, so VC-bit efficiency now can be safely determined from e.g. s91 (PD_low) sample. Last remaining question, raised by Fomenko: is there a significant (or any) influence on the calibration procedure, using ET*PD*!VC trigger? 16.09.1994 ===== dice2 ======== H1KFOM === Relation Coeff.Set 7C(??) Today it was made attempt to produce Rel. Coeff. Set for 7C data sample (from H1 Run 86799 up to H1 Run 87054). It were selected 27444 ET&PD&nVC events from this H1 Run range from data set (only G- and M- labeled H1 Runs at H1EP): H1KFOM.ETPDNVC.M8890.C00 K21684 78048081 00001 ACS-E-C After all high mentioned 'cleaning' of 7C-data samples it were collected: 27444 events with ET&PD&nVC trigger 38671 events with ET&PD&VC trigger 17129 events with S92-trigger (PD&nVC-events). It were got 27444 ET&PD&nVC from these Runs and it were used for calibration 11883 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 1.019 1.277 0.560 1.084 0.865 1.313 1.071 0.556 0.895 0.968 1.058 1.037 0.955 0.964 0.996 0.934 1.001 0.987 0.942 0.936 0.930 1.029 1.008 1.002 1.002 1.025 0.970 0.958 1.059 1.048 1.068 0.925 1.011 0.941 1.102 1.053 0.772 1.165 1.010 0.867 0.000 0.000 0.000 1.030 0.875 0.864 0.959 1.048 0.000 ==> Relation Coeff.Set for PD 1.879 0.954 1.103 1.451 0.946 1.096 0.994 1.018 1.014 1.001 0.961 1.036 1.022 1.038 1.059 1.022 1.040 1.034 0.822 1.022 1.506 0.969 1.153 1.010 0.925 ==> Sig. at Relation Coeff.Set for ET 0.000 0.025 0.001 0.017 0.005 0.007 0.009 0.010 0.009 0.009 0.010 0.007 0.017 0.012 0.019 0.015 0.014 0.012 0.019 0.012 0.018 0.014 0.014 0.017 0.010 0.025 0.019 0.011 0.009 0.019 0.012 0.013 0.024 0.007 0.008 0.028 0.009 0.035 0.018 0.006 0.000 0.000 0.000 0.077 0.030 0.020 0.000 0.000 0.000 ==> Sig. at Relation Coeff.Set for PD 0.004 0.026 0.024 0.009 0.000 0.021 0.010 0.024 0.013 0.007 0.015 0.015 0.014 0.038 0.025 0.023 0.021 0.020 0.027 0.008 0.014 0.022 0.023 0.018 0.000 ==> Ent. at Relation Coeff.Set for ET 1 16 3 18 11 9 3 6 39 54 72 68 32 32 152 221 256 286 277 400 182 3172 4941 3863 3147 2705 2260 979 1296 1701 1311 742 670 375 308 17 3 4 4 2 0 0 0 4 2 3 1 2 0 ==> Ent. at Relation Coeff.Set for PD 23 10 15 10 1 590 2508 2337 431 17 4091 9707 6722 1259 57 1074 2582 938 95 5 10 9 10 4 2 As You can see all sigma values for 'hot' H1Lumi cahnnels RC histos have more or less reasonable values (may be p13 is more then ordinary). Runs 86799- 87054 (ET&PD&nVC-sample - near 27.4K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.45 1.11 27.46 1.06 27.48 1.03 Runs 86799- 87054 (ET&PD&VC-sample - near 38.7K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.16 1.38 27.23 1.34 As start values of Calibration Coefficients for Photoproduction Branch were got ones after 3rd step of calibration with ET&PD&nVC events from 7B-sample (H1 Runs 86607-86799 - near 35.1 K events). CCvcs value was got from last VCs calibration at 7B-sample of ETPDVC- events (H1Runs 86607-86799 - see message from 13.09.94 at LL10). (CCvcs start = 4.480 MeV/FADCcount). There are 'bad' resolution digits again at 7C-sample of events. Attempt to make fit of PhotonArm Energy spectrum is almost unsucces- ful (with more or less good statistics) again. 16.09.1994 ===== dice2 ======== H1KFOM === PDREC-spectra for 7C(???) Today it were produced 100th ntuple for S92=1 events from earlier mentioned 7C sample with events from Runs 86799-87054: H1KFOM.YLOOKQ4.R86799 (17129 entries) FAST13 3010200E 00000 DASD At interactive LOOK-session it was produced 70th histo for this data set and written into the next LOOK-binary data set: H1KFOM.BLOOKQ2.R86799 9055 entries in 70h FAST04 3010200E 00000 DASD First attempt to fit 70th histo at BLOOKQ2-data set put negative sign of Global Energy Shift at Photon Arm (+1.6%) and enough good resolution digits (15%) only for energy region 22-35 GeV.All another energy regions had bad fit results (as seems bad fit result again). It were prepared 100th tuples with ET&PD&nVC and ET&PD&VC-events for procedure of defining Global Energy Shifts and CCvcs: H1KFOM.YLOOKQ2.R86799 27196 entries FAST04 3010200E 00000 DASD H1KFOM.YLOOKQ3.R86799 35843 entries FAST08 3010200E 00000 DASD 16.09.1994 ==================== H1KFOM === Global Shifts,CCvcs 7C(??) It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 1.016 for PD Channels (exept VCs), 0.9908 for ET channels. Correction factor for CCvcs is 1.1358 So CCvcs = 4.480*1.1358=5.088Mev FADCcount. These digits are valid for H1Lumi events from Run 86799 up to 87054 Runs 86799- 87054 (ET&PD&nVC-sample - near 27.4K events) xetcut&vcdepcut Step Mean Sigma 0 27.51 1.04 Runs 86799- 87054 (ET&PD&VC-sample - near 38.7K events) xetcut Step Mean Sigma 0 27.52 1.40 Remark: This is 3rd calibration (with events from 7A,7B and 7C samples) which is very preliminary due to bad fit results and 'bad' resolution digits (near 1.00 GeV and more). Possible reasons could be Y.Soloviev's mentioned accidents (and possible changing of vetoing at nVC-trigger element) or significant changing of into region near -2.0cm and less (as seems with this for more significant part photons the PD does not register full shower (due to PD is disposed at shadow of collimator for more significant part of photons). Really can be less then -2.00 due to specific of iteractive -calculation - so for this (enough large) shift from PDcenter it is possible that is calculated not right. As seems important part of calibration procedure (fit of Photon Arm spectra for events without VC-response) is at crisis status now. 17/9/94 ======================= charles === Lumi RUN# 588 Start lumi run588 date: 16/9/94 Collision time: 14:01:44 - 1:55:40 Currents (mkA): Ie= 27260.00, Ip= 43800.00 Peak luminosity: 2297.609 mb-1 s-1 Peak spec.lumi : 367.329395 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 67837.334845 mkb-1 H1 Run total lumi: 60740.9849 mkb-1 H1 data taken lumi: 50699.1917 mkb-1 H1 Runs: 87167 - 87195 HERA - physics: 66080.560971 mkb-1 H1Run - physics: 58561.73079 mkb-1 H1data - physics: 48609.392144 mkb-1 H1 Runs: 87169 - 87195 Tot curr/rate factor: 0.83% C/R F H1Run gated: 0.87% Rand.C.F: 0.74% RCF Run gated: 0.75% Relative ET trigg accept.: 0.4770 PS(LNS): for R87175 (~28 Kevents): L4 absent; L5 absent. PS(LNS): for R87181 (~42 Kevents): L4 histos OK; L5 absent. 17/9/94 ======================= charles === Lumi RUN# 589 Start lumi run589 date: 17/9/94 Collision time: 3:25:27 - 16:20:13 Currents (mkA): Ie= 26369.00, Ip= 39601.00 Peak luminosity: 1291.85 mb-1 s-1 Peak spec.lumi : 233.8375 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 48224.922492 mkb-1 H1 Run total lumi: 46049.8105 mkb-1 H1 data taken lumi: 37235.1267 mkb-1 H1 Runs: 87199 - 87220 HERA - physics: 47785.496342 mkb-1 H1Run - physics: 45419.766114 mkb-1 H1data - physics: 36716.293533 mkb-1 H1 Runs: 87201 - 87220 Tot curr/rate factor: 1.27% C/R F H1Run gated: 1.3% Rand.C.F: 0.57% RCF Run gated: 0.56% Relative ET trigg accept.: 0.4649 PS(LNS): for R87204 (~36 Kevents): L4 histos OK; L5 absent. 18/9/94 ======================= charles === Lumi RUN# 590 Start lumi run590 date: 17/9/94 Collision time: 21:27:18 - 10:16:32 Currents (mkA): Ie= 29020.00, Ip= 49800.00 Peak luminosity: 3402.588 mb-1 s-1 Peak spec.lumi : 439.547135 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 82230.542488 mkb-1 H1 Run total lumi: 79345.780818 mkb-1 H1 data taken lumi: 68392.482774 mkb-1 H1 Runs: 87222 - 87241 HERA - physics: 81177.727662 mkb-1 H1Run - physics: 77693.577618 mkb-1 H1data - physics: 66834.223974 mkb-1 H1 Runs: 87223 - 87241 Tot curr/rate factor: 0.86% C/R F H1Run gated: 0.86% Rand.C.F: 0.81% RCF Run gated: 0.8% Relative ET trigg accept.: 0.4784 PS(LNS): for R87226 (~82 Kevents): L4 histos OK; L5 absent. 18/9/94 ======================= Carsten === Lumi RUN# 591 Start lumi run591 date: 18/9/94 Collision time: 12:00:43 - 20:14:17 Currents (mkA): Ie= 27860.00, Ip= 48900.00 Peak luminosity: 2472.71 mb-1 s-1 Peak spec.lumi : 346.832249 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 46392.907875 mkb-1 H1 Run total lumi: 45124.5775 mkb-1 H1 data taken lumi: 37126.6372 mkb-1 H1 Runs: 87244 - 87261 HERA - physics: 43945.431675 mkb-1 H1Run - physics: 42194.373361 mkb-1 H1data - physics: 34289.428265 mkb-1 H1 Runs: 87245 - 87261 Tot curr/rate factor: 0.56% C/R F H1Run gated: 0.56% Rand.C.F: 0.91% RCF Run gated: 0.91% Relative ET trigg accept.: 0.4887 PS(LNS): for R87249 (~82 Kevents): L4 histos OK; L5 absent. 19/9/94 ======================= Charles === Lumi RUN# 592 Start lumi run592 date: 19/9/94 Collision time: 0:29:10 - 3:06:57 Currents (mkA): Ie= 26400.00, Ip= 47100.00 Peak luminosity: 2112.051 mb-1 s-1 Peak spec.lumi : 346.035977 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 15838.005986 mkb-1 H1 Run total lumi: 15540.3854 mkb-1 H1 data taken lumi: 13645.506 mkb-1 H1 Runs: 87268 - 87274 HERA - physics: 12471.287275 mkb-1 H1Run - physics: 10138.479275 mkb-1 H1data - physics: 9003.643482 mkb-1 H1 Runs: 87271 - 87274 Tot curr/rate factor: 1.62% C/R F H1Run gated: 1.62% Rand.C.F: 1.15% RCF Run gated: 1.15% Relative ET trigg accept.: 0.4377 PS(LNS): for R87271 (~10 Kevents): L4 histos OK; L5 absent. 19.09.1994 ==================== H01GOG === LUMIMON data processing Here is a continuation of summary table for e+p LUMIMON files, processed so far. Three latest existing LUMIMON files (92,93,94) are being processed now. ---------------------------------------------------------------------- File H1 runs Events Actual triggers (xx) s86 s91 s92 s93 s94 s95 ---------------------------------------------------------------------- 88 86799-86928 129490 13025 7420 5801 10926 6490 9769 89 86928-86955 128458 8385 6312 6973 10511 8072 10828 90 86955-87054 128665 11638 5235 6990 8000 7637 8601 91 87054-87178 129115 10025 5060 6598 7596 7467 8425 ---------------------------------------------------------------------- Pay attention, that from file 90 on, fig.41 in a standard set of figures produced by H01GOG.LUMMON.MACRO was changed. It now compares ET energy spectra for s86-events in all bunches and e-pilot bunches. This was considered to be more important, to control and understand variation of this shape with time (see my previos message in LLO). Old figure 41 was anyway not very informative. As an example, compare fig. 41 from LUMIMON 58 and 59. In the first case, the shapes for colliding and pilot bunches are very different, while in the second case - similar. (Note: in order to make the comparison easier, a histogram for pilot bunches is filled with weight 11.0, which is around the average ratio of Ie_total/Ie_pilot). 19.09.1994 ===== dice2 ======== H1KFOM === Selected H1Lumi Monitrig.. Today it were selected calibration data samples from the next data sets which were produced with standard job prepared by S.Levonyan at dice1-environment: HERA03.H01.LUMIMON.C9400091 K26480 78048081 00001 ACS-E-C ...... HERA03.H01.LUMIMON.C9400094 K37414 78048081 00001 ACS-E-C It were selected events with (s92=1 only),with ET&PD&VC=1 and with ET&PD&nVC from these data sets (as ordinary) from 512994 events: 1) S92=1 only 31099 events ( 49.6 MBytes) 2) ET&PD&VC 58047 events ( 84.9 MBytes) 3) ET&PD&nVC 51123 events ( 96.3 MBytes) Created data sets were saved at DESY IBM storage at the next data sets H1KFOM.ETPDNVC.M9194.C00 K36212 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M9194.C00 K36353 78048081 00001 ACS-E-C H1KFOM.S92.M9194.C00 K36435 78048081 00001 ACS-E-C These data include events from Lumi RUNs# 586-591 (H1 Runs 87054- 87249). P.S. First evidence of VC-bit setting influence on something at H1Lumi calibration procedure - relative numbers of ET&PD&nVC and ET&PD&VC - events had changed - and it is good as seems. ET&PD&nVC - sample is more important data sample. 19.09.1994 ===== dice2 ======== H1KFOM === Relation Coeff.Set 7D(??) Today it was made attempt to produce Rel. Coeff. Set for 7D data sample (from H1 Run 87054 up to H1 Run 87249). It were selected 43224 ET&PD&nVC events from this H1 Run range from data set (only G- and M- labeled H1 Runs at H1EP): H1KFOM.ETPDNVC.M9194.C00 K36212 78048081 00001 ACS-E-C After all high mentioned 'cleaning' of 7D-data samples it were collected: 43224 events with ET&PD&nVC trigger 48534 events with ET&PD&VC trigger 31099 events with S92-trigger (PD&nVC-events). It were got 43224 ET&PD&nVC from these Runs and it were used for calibration 15460 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 1.017 1.297 0.540 1.072 0.821 1.282 0.985 0.539 0.867 1.000 1.043 0.985 0.938 0.947 1.034 0.917 0.977 0.991 0.994 0.946 0.912 1.029 1.013 1.011 0.998 1.020 0.971 0.960 0.966 0.997 1.019 0.917 1.029 0.943 1.114 1.048 0.773 1.235 0.967 0.852 0.928 1.086 0.942 0.930 0.900 0.888 0.950 0.000 0.000 ==> Relation Coeff.Set for PD 1.867 0.923 1.076 1.476 0.000 0.985 1.022 1.005 1.007 0.987 0.950 1.037 1.023 1.022 1.078 1.094 0.995 0.985 0.947 0.955 1.469 0.978 1.162 1.017 0.924 ==> Sig. at Relation Coeff.Set for ET 0.000 0.015 0.006 0.007 0.006 0.005 0.009 0.004 0.003 0.007 0.006 0.006 0.008 0.004 0.017 0.012 0.006 0.005 0.008 0.006 0.011 0.014 0.016 0.017 0.013 0.020 0.015 0.009 0.008 0.007 0.011 0.010 0.005 0.006 0.007 0.001 0.000 0.023 0.009 0.022 0.003 0.000 0.000 0.000 0.000 0.001 0.000 0.000 0.000 ==> Sig. at Relation Coeff.Set for PD 0.004 0.002 0.005 0.003 0.000 0.007 0.010 0.015 0.010 0.007 0.027 0.019 0.015 0.026 0.007 0.018 0.020 0.025 0.016 0.014 0.003 0.002 0.005 0.006 0.000 ==> Ent. at Relation Coeff.Set for ET 7 26 5 10 18 31 10 9 49 75 57 76 48 37 392 181 306 331 317 541 219 4007 6258 5065 4253 3616 2932 1319 1228 2059 1612 947 1086 615 472 16 4 8 7 2 2 1 1 5 1 6 1 0 0 ==> Ent. at Relation Coeff.Set for PD 18 11 10 16 0 442 3150 3437 630 38 4314 12170 9685 2082 109 1242 2900 1184 162 11 13 14 16 2 3 As You can see all sigma values for 'hot' H1Lumi cahnnels RC histos have more or less reasonable values. Runs 87054- 87249 (ET&PD&nVC-sample - near 43.2K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.41 1.09 27.45 1.06 27.51 1.06 Runs 87054- 87249 (ET&PD&VC-sample - near 48.5K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.62 1.43 27.67 1.39 As start values of Calibration Coefficients for Photoproduction Branch were got ones after 3rd step of calibration with ET&PD&nVC events from 7C-sample (H1 Runs 86799-87054 - near 27.4 K events). CCvcs value was got from last VCs calibration at 7C-sample of ETPDVC- events (H1Runs 86799-87054 - see message from 16.09.94 at LL10). (CCvcs start = 5.088 MeV/FADCcount). There are 'bad' resolution digits again at 7D-sample of events. Attempt to make fit of PhotonArm Energy spectrum is almost unsucces- ful (with more or less good statistics) again. 19.09.1994 ===== dice2 ======== H1KFOM === PDREC-spectra for 7D(???) Today it were produced 100th ntuple for S92=1 events from earlier mentioned 7D sample with events from Runs 87054-87249: H1KFOM.YLOOKQ4.R87054 (21850 entries) FAST13 3010200E 00000 DASD At interactive LOOK-session it was produced 70th histo for this data set and written into the next LOOK-binary data set: H1KFOM.BLOOKQ2.R87054 11526 entries in 70h FAST12 3010200E 00000 DASD First attempt to fit 70th histo at BLOOKQ2-data set put negative sign of Global Energy Shift at Photon Arm (-1.6%) and enough good resolution digits (17%) only for energy region 22-35 GeV.All another energy regions had bad fit results (as seems bad fit result again). It were prepared 100th tuples with ET&PD&nVC and ET&PD&VC-events for procedure of defining Global Energy Shifts and CCvcs: H1KFOM.YLOOKQ2.R87054 42757 entries FAST17 3010200E 00000 DASD H1KFOM.YLOOKQ3.R87054 44772 entries FAST16 3010200E 00000 DASD 19.09.1994 ==================== H1KFOM === Global Shifts,CCvcs 7D(??) It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 1.016 for PD Channels (exept VCs), 0.9879 for ET channels. Correction factor for CCvcs is 0.9600.So CCvcs = 5.088*0.9600=4.884Mev FADCcount. These digits are valid for H1Lumi events from Run 87054 up to 87249 Runs 87054- 87249 (ET&PD&nVC-sample - near 43.2K events) xetcut&vcdepcut Step Mean Sigma 0 27.51 1.05 Runs 87054- 87249 (ET&PD&VC-sample - near 48.5K events) xetcut Step Mean Sigma 0 27.52 1.37 P.S. As You can see 7D-calibration data samples were collected after Egor's changing VC-bit setting and there are no significant (may be any) influences on calibration results. So - no any remark to VC-trigger bit setting - all is OK from calibration procedure side. 19/9/94 ======================= Gruber === Lumi RUN# 593 Start lumi run593 date: 19/9/94 Collision time: 7:43:44 - 14:25:29 Currents (mkA): Ie= 28216.00, Ip= 45600.00 Peak luminosity: 3000.107 mb-1 s-1 Peak spec.lumi : 457.094246 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 48777.0053 mkb-1 H1 Run total lumi: 46246.5278 mkb-1 H1 data taken lumi: 39165.6757 mkb-1 H1 Runs: 87285 - 87302 HERA - physics: 45779.424384 mkb-1 H1Run - physics: 42771.38448 mkb-1 H1data - physics: 35716.001501 mkb-1 H1 Runs: 87286 - 87302 Tot curr/rate factor: 0.94% C/R F H1Run gated: 0.95% Rand.C.F: 1.03% RCF Run gated: 1.03% Relative ET trigg accept.: 0.4850 PS(LNS): for R87291 (~10 Kevents): L4 histos OK; L5 absent. 20/9/94 ======================= gruber === Lumi RUN# 594 Start lumi run594 date: 19/9/94 Collision time: 18:45:18 - 3:03:28 Currents (mkA): Ie= 26808.00, Ip= 44700.00 Peak luminosity: 2086.162 mb-1 s-1 Peak spec.lumi : 337.981323 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 40873.969816 mkb-1 H1 Run total lumi: 39448.1955 mkb-1 H1 data taken lumi: 34453.1969 mkb-1 H1 Runs: 87314 - 87324 HERA - physics: 39547.53512 mkb-1 H1Run - physics: 37682.1771 mkb-1 H1data - physics: 32771.0886 mkb-1 H1 Runs: 87317 - 87324 Tot curr/rate factor: 1.45% C/R F H1Run gated: 1.44% Rand.C.F: 1.01% RCF Run gated: 1.01% Relative ET trigg accept.: 0.5006 PS(LNS): for R87319 (~59 Kevents): L4 absent; L5 absent. PS(LNS): for R87322 (~59 Kevents): L4 histos OK; L5 absent. PS(LNS): Little Warning: Edep-Etrig for PD -> the 2-nd reak at ~+1. 20.09.1994 ==================== H1KFOM === New RC Sets in H1DataBase As final action of all 16-19.09.94 calibration steps it was made update of LFRC and LESC banks at H1DataBase with S.Levonyan's tool. All Relation Coefficients values, CCvcs and Global Energy Shift constants were got from the next messages at LLO: 16.09.1994 ----- dice2 -------- H1KFOM --- Relation Coeff.Set 7C(??) 16.09.1994 -------------------- H1KFOM --- Global Shifts,CCvcs 7C(??) 19.09.1994 ----- dice2 -------- H1KFOM --- Relation Coeff.Set 7D(??) 19.09.1994 -------------------- H1KFOM --- Global Shifts,CCvcs 7D(??) Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LFRC (_501) 40 e-p data 409200830 86799 87053 77 940920 H1KFOM 41 e-p data 409200918 87054 0 77 940920 H1KFOM Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LESC (_582) 48 e-p data 409200830 86799 87053 3 940920 H1KFOM 49 e-p data 409200918 87054 0 3 940920 H1KFOM P.S. after succesful updating of LFRC and LESC banks (40th and 48th versions) H1DataBase was disabled on some time for service and last versions (41st and 49th)were written after today H1DataBase service). 20/9/94 ======================= gruber === Lumi RUN# 595 Start lumi run595 date: 20/9/94 Collision time: 6:25:03 - 9:48:48 Currents (mkA): Ie= 28467.00, Ip= 41500.00 Peak luminosity: 2017.245 mb-1 s-1 Peak spec.lumi : 331.178282 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 17728.339396 mkb-1 H1 Run total lumi: 17218.5043 mkb-1 H1 data taken lumi: 14973.0411 mkb-1 H1 Runs: 87326 - 87330 HERA - physics: 15549.461166 mkb-1 H1Run - physics: 15169.076975 mkb-1 H1data - physics: 13011.399624 mkb-1 H1 Runs: 87327 - 87330 Tot curr/rate factor: 1.48% C/R F H1Run gated: 1.48% Rand.C.F: 1.32% RCF Run gated: 1.31% Relative ET trigg accept.: 0.5233 PS(LNS): for R87329 (~48 Kevents): L4 histos OK; L5 absent. 20.09.1994 ==================== F11LEV === Temporary problem with DB. It was found, that since yesterday noon lumi banks LH1R and LH1T are not written to the database. After investigations, it became clear, that the IBM disk where DB is sitting is full and no longer accepts new information. The problem was cured two hours ago, and now missing lumi (and other) banks are being written to the database. 20.09.1994 ==================== F11LEV === DQ meeting report ........ Today, on a weekly DQ meeting I reported the following LUMI status: 1) NAN problem fixing by I.Sheviakov in the online s/w. It is clear (for him) that this is LUMI s/w bug, which is now cured in a way, that whenever NAN appears in the cell, containing HERA produced lumi, it is replaced by the previous correct value. Igor also is monitoring such cases. They are still happening and then corrected by this procedure. 2) New status of VC trigger bit. Several plots were shown, comparing VC-behaviour in 1993, beginning of 1994 and now, after raising the threshold. Some values, obtained from H01GOG.MLOOK files analysis: ------------------------------------------------------------------ H1 runs VC threshold in E(VC) asymptotic VC-efficiency (at eff.=0.5 level) (in E_gamma=10-28GeV interval) ------------------------------------------------------------------ 81353-81977 0.4 GeV 0.865 +- 0.007 86955-87298 0.7 GeV 0.807 +- 0.005 ------------------------------------------------------------------ Conclusion: VC(1993) - basically OK, VC(1994 - before 14-Sep.) - wrong behaviour, overestimated eff. VC(1994 - now) - correct behaviour and lower efficiency 3) New situation with etag background behaviour. After recent report from Nelly (see LLO, 15.09) I checked s86 sub-samples from files H01GOG.MLOOK and can confirm her statements. Indeed (plots were shown): a) a shape of the energy spectrum at ET for s86 events is different compared to 92 and 93 data (where they were similar) b) there is a difference between all: 92+93, e-p(94) and e+p(94) shapes. c) now, for e+p data, the shape is varying in time d) in most cases the shape for the colliding and pilot bunches are very similar, but sometimes (e.g. runs 83771-83828) - very different. Conclusion: this has a definite impact for the physics analysis of etag-94 data! A statistical subtraction of the remaining background in 94 will be more complicated than before, when an average spectrum over the whole period was used. Now we have to monitor this constantly and subtract on the run-by-run basis (or subdivide 94 data on several periods with similar bgr. shapes) 20/9/94 ======================= gruber === Lumi RUN# 596 Start lumi run596 date: 20/9/94 Collision time: 19:59:39 - 20:03:13 Currents (mkA): Ie= 28445.00, Ip= 48900.00 Peak luminosity: 0 mb-1 s-1 Peak spec.lumi : 0 mb-1 s-1 mA-2 Number of collided b.: 0 Number of e-filled b.: 0 Number of p-filled b.: 170 Number of e-pilot b.: 0 Number of p-pilot b.: 170 HERA total lumi: 10.07371 mkb-1 H1 Run total lumi: 109.414367 mkb-1 H1 data taken lumi: 49.509382 mkb-1 H1 Runs: 87402 - 87402 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 87402 - 87402 Tot curr/rate factor: 13.03% C/R F H1Run gated: 13.03% Rand.C.F: 3.24% RCF Run gated: 3.24% Relative ET trigg accept.: Not calc. 20/9/94 ======================= gruber === Lumi RUN# 597 Start lumi run597 date: 20/9/94 Collision time: 21:09:13 - 21:15:21 Currents (mkA): Ie= 28512.00, Ip= 48901.00 Peak luminosity: 0 mb-1 s-1 Peak spec.lumi : 0 mb-1 s-1 mA-2 Number of collided b.: 0 Number of e-filled b.: 0 Number of p-filled b.: 170 Number of e-pilot b.: 0 Number of p-pilot b.: 170 HERA total lumi: 2.3037 mkb-1 H1 Run total lumi: 2.303729 mkb-1 H1 data taken lumi: 2.259007 mkb-1 H1 Runs: 87403 - 87403 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 87403 - 87403 Tot curr/rate factor: 1.68% C/R F H1Run gated: 1.68% Rand.C.F: 0.61% RCF Run gated: 0.61% Relative ET trigg accept.: Not calc. 21/9/94 ======================= gruber === Lumi RUN# 598 Start lumi run598 date: 20/9/94 Collision time: 22:33:03 - 9:20:12 Currents (mkA): Ie= 27799.00, Ip= 48800.00 Peak luminosity: 2840.381 mb-1 s-1 Peak spec.lumi : 398.272151 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 68530.728762 mkb-1 H1 Run total lumi: 64764.789 mkb-1 H1 data taken lumi: 55818.8928 mkb-1 H1 Runs: 87406 - 87436 HERA - physics: 66922.867272 mkb-1 H1Run - physics: 62723.40616 mkb-1 H1data - physics: 53946.864188 mkb-1 H1 Runs: 87407 - 87436 Tot curr/rate factor: 0.36% C/R F H1Run gated: 0.37% Rand.C.F: 0.89% RCF Run gated: 0.9% Relative ET trigg accept.: 0.4856 PS(LNS): for R87411 (~69 Kevents): L4 histos OK; L5 OK, too. 22.09.1994 ==================== H01GOG === LUMIMON data processing Here is a continuation of summary table for e+p LUMIMON files, processed so far. The latest existing LUMIMON file (98) is being processed now. ---------------------------------------------------------------------- File H1 runs Events Actual triggers (xx) s86 s91 s92 s93 s94 s95 ---------------------------------------------------------------------- 92 87178-87208 128124 7997 5961 7693 8655 8784 9796 93 87208-87232 128104 9013 5092 7367 6383 8451 8304 94 87232-87249 127651 8887 6261 8966 7950 10452 10202 95 87249-87298 128384 11279 5566 7814 7335 9015 9083 96 87298-87329 127921 11179 5886 7855 7812 9653 9776 97 87329-87423 128437 11741 4918 5899 7212 7303 8337 ---------------------------------------------------------------------- Two observations: ================= 1) A peak in x_PD distribution at -2cm (PD-11) has appeared again starting from run 87315 (LUMIMON-96). Amount of such events is however relatively small: ~ 1% for E_gamma > 3GeV. 2) Triggered by the remark of A.Fomenko about possible influence of the changed VC-trigger on the calibration results, I have compared the energy resolutions from lumi events in the last 18 LUMIMON files: 80-97. Figure 36 was used, which shows total reconstructed energy for ET*PD*nVC events. The result shown below, indeed indicates, that the resolution gets worse. But what is the real reason? I don't know. VC Files H1 runs sigma resol.=sigma/E_tot old 80-84 86146-86671 27.44 1.027 3.74 % old 85-89 86671-86955 27.34 1.086 3.97 % new 90-97 86955-87423 27.57 1.121 4.07 % From the average values it looks like the resolution is changed gradually, but in fact within each of these pieces it stays more or less on the same level. 21/9/94 ======================= === Lumi RUN# 599 Start lumi run599 date: 21/9/94 Collision time: 11:08:44 - 21:33:49 Currents (mkA): Ie= 29300.00, Ip= 47100.00 Peak luminosity: 2225.434 mb-1 s-1 Peak spec.lumi : 356.93963 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 47759.65575 mkb-1 H1 Run total lumi: 43322.6243 mkb-1 H1 data taken lumi: 37073.6456 mkb-1 H1 Runs: 87446 - 87484 HERA - physics: 45932.65568 mkb-1 H1Run - physics: 41034.606612 mkb-1 H1data - physics: 35320.683584 mkb-1 H1 Runs: 87448 - 87484 Tot curr/rate factor: 0.71% C/R F H1Run gated: 0.71% Rand.C.F: 1% RCF Run gated: 1% Relative ET trigg accept.: 0.4837 PS(LNS): for R87449 (~26 Kevents): L4 absent; L5 absent. PS(LNS): for R87457 (~30 Kevents): L4 histos OK; L5 absent. PS(LNS): I suspect, 87448-87484 is wrong, RUN# is shorter.(?) 22.09.1994 ===== dice2 ======== H1KFOM === Selected H1Lumi Monitrig.. Today it were selected calibration data samples from the next data sets which were produced with standard job prepared by S.Levonyan at dice1-environment: HERA03.H01.LUMIMON.C9400095 K20694 78048081 00001 ACS-E-C ...... HERA03.H01.LUMIMON.C9400098 K35985 78048081 00001 ACS-E-C It were selected events with (s92=1 only),with ET&PD&VC=1 and with ET&PD&nVC from these data sets (as ordinary) from 512970 events: 1) S92=1 only 29035 events ( 46.3 MBytes) 2) ET&PD&VC 56802 events ( 94.3 MBytes) 3) ET&PD&nVC 49416 events ( 82.1 MBytes) Created data sets were saved at DESY IBM storage at the next data sets H1KFOM.ETPDNVC.M9598.C00 K23887 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M9598.C00 K24116 78048081 00001 ACS-E-C H1KFOM.S92.M9598.C00 K24131 78048081 00001 ACS-E-C These data include events from Lumi RUNs# 591-600 (H1 Runs 87249- 87509). 22.09.1994 ===== dice2 ======== H1KFOM === New CCp11 "jumps"......... It was found that CCp11 at OnLine calibration procedure 'jumped' into high value side on factor 2 (20.09.94, near 19:00, during start Lumi RUN# 594) and came back during H1 Run 87458 (21.09.94, between 14:38 and 15:34, during Lumi RUN# 599). During this period it were collected near 26K ET&PD&nVC events and (as seems) it will be possible to make calibration with new 8A-data sample (H1Runs 87314-87457). Data from H1 Runs 87249 up to 87313 will be added to 7D-samples and it will be made recalibration of 7D-sample with data from H1 Runs 87054-87313. Data after H1 Run 87458 will be start data subsamples for new 8B-calibration samples. High mentioned CCp11 'jumps' it is possible to see at vector 20012 which is kept at LOOK-binary data set: H1KFOM.LOOKB.R87249 FAST12 3010200E 00000 DASD Incrementing of CCp11 is fixed near 17500th event at ET&PD&nVC sample events from data set: H1KFOM.ETPDNVC.M9598.C00 K23887 78048081 00001 ACS-E-C and decrementing of CCp11 (coming back to old value) - near 43500th event at sample. 22/9/94 ======================= === Lumi RUN# 600 (jubilee) Start lumi run600 date: 22/9/94 Collision time: 5:16:23 - 16:16:18 Currents (mkA): Ie= 25670.00, Ip= 45200.00 Peak luminosity: 2003.659 mb-1 s-1 Peak spec.lumi : 347.276561 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 54304.862237 mkb-1 H1 Run total lumi: 48471.6212 mkb-1 H1 data taken lumi: 41344.7019 mkb-1 H1 Runs: 87509 - 87556 HERA - physics: 53741.216174 mkb-1 H1Run - physics: 48075.3369 mkb-1 H1data - physics: 40951.4138 mkb-1 H1 Runs: 87510 - 87556 Tot curr/rate factor: 0.89% C/R F H1Run gated: 0.92% Rand.C.F: 0.56% RCF Run gated: 0.56% Relative ET trigg accept.: 0.4502 PS(LNS): for R87521 (~73 Kevents): L4 histos OK; L5 absent. 23/9/94 ======================= zuber === Lumi RUN# 601 Start lumi run601 date: 23/9/94 Collision time: 2:18:03 - 2:19:14 Currents (mkA): Ie= 27647.00, Ip= 46100.00 Peak luminosity: 0 mb-1 s-1 Peak spec.lumi : 0 mb-1 s-1 mA-2 Number of collided b.: 0 Number of e-filled b.: 0 Number of p-filled b.: 170 Number of e-pilot b.: 0 Number of p-pilot b.: 170 HERA total lumi: 12.110113 mkb-1 H1 Run total lumi: 12.110113 mkb-1 H1 data taken lumi: 11.726887 mkb-1 H1 Runs: 87577 - 87577 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 87577 - 87577 Tot curr/rate factor: 0.61% C/R F H1Run gated: 0.61% Rand.C.F: 6.16% RCF Run gated: 6.16% Relative ET trigg accept.: Not calc. 23.09.1994 ==================== H1KFOM === Huge Rates at H1Lumi Again Tonight at periods 04:03-04:18 (near 15 min) and 05:13-05:23 (near 10 min)during Dump Condition of H1 Main Solenoid and during Its Ramping Up it were fixed again huge rates at H1Lumi Detectors (at first period ET&PD rate achieved up to 1 - 1.1 MHz - at second - near 0.9-1.0 MHz. It is 3rd accident at current month (first 2 were fixed at 02.09.94 and 03.09.94 - and (as seems) after this resolution of H1Lumi Detectors became bad(1.05 - 1.06 GeV with the 'best' cuts at ETrec+PDrec spectrum for ET&PD&nVC sample of events). H1 RUN news presented information that something not good with Movable Platform for PD and it is needed 'no beam' time period for e understanding what happened. 23.09.1994 ===== dice2 ======== H1KFOM === Relation Coeff.Set 7D(new) Today it was made attempt to recalculate Rel.Coeff.Set for 7Dextended data sample (from H1 Run 87054 up to Run 87313).It were selected 60105 ET&PD&nVC events from this H1 Run range from data sets(only G- and M- labeled H1 Runs at H1EP): H1KFOM.ETPDNVC.M9194.C00 K36212 78048081 00001 ACS-E-C H1KFOM.ETPDNVC.M9598.C00 K23887 78048081 00001 ACS-E-C After all high mentioned 'cleaning' of 7Dextended-data samples it were collected: 60105 events with ET&PD&nVC trigger 67264 events with ET&PD&VC trigger 36478 events with S92-trigger (PD&nVC-events). It were got 60105 ET&PD&nVC from these Runs and it were used for calibration 21891 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 1.030 1.316 0.538 1.086 0.822 1.238 0.972 0.543 0.884 1.014 1.065 0.961 0.974 0.952 1.243 0.916 0.972 0.996 1.001 0.962 0.916 1.020 1.009 1.014 1.002 1.019 0.979 0.967 0.952 1.020 1.013 0.916 1.084 0.953 1.109 1.055 0.784 1.241 0.982 0.845 0.967 1.085 0.942 0.930 0.903 0.894 0.952 1.048 0.000 ==> Relation Coeff.Set for PD 1.857 0.915 1.098 1.493 0.000 0.978 1.021 1.008 0.995 0.987 0.950 1.031 1.018 1.020 1.073 1.084 1.014 0.982 0.951 0.969 1.447 0.942 1.149 1.013 0.924 ==> Sig. at Relation Coeff.Set for ET 0.002 0.014 0.008 0.006 0.005 0.005 0.008 0.004 0.006 0.007 0.005 0.005 0.010 0.004 0.013 0.011 0.004 0.005 0.010 0.005 0.012 0.014 0.015 0.017 0.012 0.019 0.018 0.011 0.007 0.007 0.014 0.010 0.004 0.006 0.007 0.002 0.008 0.019 0.009 0.015 0.008 0.001 0.000 0.000 0.001 0.014 0.002 0.000 0.000 ==> Sig. at Relation Coeff.Set for PD 0.004 0.002 0.006 0.004 0.000 0.006 0.011 0.014 0.010 0.006 0.022 0.017 0.016 0.027 0.008 0.016 0.019 0.024 0.015 0.013 0.003 0.004 0.005 0.004 0.000 ==> Ent. at Relation Coeff.Set for ET 8 36 6 12 25 33 11 10 60 85 69 92 63 42 1262 265 392 453 439 735 287 5709 8955 7288 5998 5100 4111 1808 1693 2976 2230 1354 1677 910 648 27 9 14 11 4 3 3 2 7 4 8 2 2 0 ==> Ent. at Relation Coeff.Set for PD 33 18 14 28 0 626 4262 4590 833 51 6193 17217 13650 2931 138 1937 4811 2042 263 13 19 19 23 4 4 As You can see all sigma values for 'hot' H1Lumi cahnnels RC histos have more or less reasonable values. Runs 87054- 87313 (ET&PD&nVC-sample - near 60.1K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.45 1.10 27.45 1.07 27.48 1.06 Runs 87054- 87313 (ET&PD&VC-sample - near 67.2K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.49 1.41 27.56 1.38 As start values of Calibration Coefficients for Photoproduction Branch were got ones after 3rd step of calibration with ET&PD&nVC events from 7D-sample (H1 Runs 87054-87249 - near 43.2 K events). CCvcs value was got from last VCs calibration at 7D-sample of ETPDVC- events (H1Runs 87054-87249 - see message from 19.09.94 at LL10). (CCvcs start = 4.884 MeV/FADCcount). There are 'bad' resolution digits again at 7Dext.-sample of events. Attempt to make fit of PhotonArm Energy spectrum is almost unsucces- ful (with more or less good statistics) again. 23.09.1994 ===== dice2 ======== H1KFOM === PDREC-spectra for 7D(new) Today it were produced 100th ntuple for S92=1 events from earlier mentioned 7Dextended sample with events from Runs 87054-87313: H1KFOM.YLOOKQ4.R87054.NEW(30240 entries) FAST09 3010200E 00000 DASD At interactive LOOK-session it was produced 70th histo for this data set and written into the next LOOK-binary data set: H1KFOM.BLOOKQ3.R87054 16074 entries in 70h FAST12 3010200E 00000 DASD First attempt to fit 70th histo at BLOOKQ2-data set put negative sign of Global Energy Shift at Photon Arm (-1.8%) and enough good resolution digits (17%)only for energy regions 22,24-35 GeV.All another energy regions had bad fit results (as seems bad fit result again). It were prepared 100th tuples with ET&PD&nVC and ET&PD&VC-events for procedure of defining Global Energy Shifts and CCvcs: H1KFOM.YLOOKQ2.R87054.NEW 59456 entries FAST04 3010200E 00000 DASD H1KFOM.YLOOKQ3.R87054.NEW 61987 entries FAST08 3010200E 00000 DASD 23.09.1994 ==================== H1KFOM === Global Shifts,CCvcs 7D(new It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 1.018 for PD Channels (exept VCs), 0.986 for ET channels. Correction factor for CCvcs is 1.008. So CCvcs = 4.884*1.008 =4.923Mev FADCcount. These digits are valid for H1Lumi events from Run 87054 up to 87313 Runs 87054- 87313 (ET&PD&nVC-sample - near 60.1K events) xetcut&vcdepcut Step Mean Sigma 0 27.52 1.05 Runs 87054- 87313 (ET&PD&VC-sample - near 67.2K events) xetcut Step Mean Sigma 0 27.52 1.38 P.S. CCe19 at Photoproduction Branch became near 10.0 MeV/FADCcount This is firstly at all 3 year period - one of channel have very low response (factor 2-3 in compare with another channels). For any case - this is the final values of CC at Photoproduction branch after 3rd step of calibration with 7Dextended data sample (H1 Runs 87054-87313): ==> ET Calibr.Coefficients Final Status e01= 4.122 4.187 4.077 3.234 3.924 3.117 e06=3.453 4.358 3.333 3.881 1.842 4.775 3.736 3.520 7.013 2.495 4.255 4.687 4.166 10.049 4.083 e21= 6.901 4.788 5.523 4.614 4.150 4.764 e27=4.135 3.799 5.012 4.606 3.639 5.021 4.433 3.167 4.392 4.643 3.565 3.660 4.370 4.261 4.018 e42= 4.054 3.964 4.335 1.966 3.722 4.141 e49=4.018 ==> PD & VC Calibr.Coefficients Final Status p01= 2.069 1.485 1.505 2.368 p04=2.538 1.237 2.544 2.882 2.169 1.606 2.317 2.229 2.969 2.933 2.199 2.378 2.053 2.706 2.890 2.361 p20= 1.340 1.542 2.362 3.172 p24=2.549 vcs= 4.923 23.09.1994 ==================== H1KFOM === New RC Sets in H1DataBase As final action of all 23.09.94 calibration steps it was made update of LFRC and LESC banks at H1DataBase with S.Levonyan's tool. All Relation Coefficients values, CCvcs and Global Energy Shift constants were got from the next messages at LLO: 23.09.1994 ----- dice2 -------- H1KFOM --- Relation Coeff.Set 7D(new) 23.09.1994 -------------------- H1KFOM --- Global Shifts,CCvcs 7D(new Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LFRC (_501) 42 e-p data 409231319 87054 0 77 940923 H1KFOM Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LESC (_582) 50 e-p data 409231319 87054 0 3 940923 H1KFOM 23/9/94 ======================= === Lumi RUN# 602 Start lumi run602 date: 23/9/94 Collision time: 5:08:55 - 14:48:50 Currents (mkA): Ie= 21481.00, Ip= 45900.00 Peak luminosity: 1833.721 mb-1 s-1 Peak spec.lumi : 345.686304 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 39924.93507 mkb-1 H1 Run total lumi: 37114.3649 mkb-1 H1 data taken lumi: 29174.7642 mkb-1 H1 Runs: 87579 - 87610 HERA - physics: 39906.484728 mkb-1 H1Run - physics: 36681.856532 mkb-1 H1data - physics: 28769.82854 mkb-1 H1 Runs: 87580 - 87610 Tot curr/rate factor: 1.72% C/R F H1Run gated: 1.72% Rand.C.F: 1% RCF Run gated: 1.01% Relative ET trigg accept.: 0.4969 PS(LNS): for R87608 (~77 Kevents): L4 histos OK; L5 absent. 23/9/94 ======================= robmann === Lumi RUN# 603 Start lumi run603 date: 23/9/94 Collision time: 19:40:16 - 21:04:57 Currents (mkA): Ie= 29431.00, Ip= 39600.00 Peak luminosity: 1669.126 mb-1 s-1 Peak spec.lumi : 319.049751 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 5569.346143 mkb-1 H1 Run total lumi: 3962.0803 mkb-1 H1 data taken lumi: 3352.3852 mkb-1 H1 Runs: 87633 - 87647 HERA - physics: 4698.772712 mkb-1 H1Run - physics: 3550.650377 mkb-1 H1data - physics: 3188.647457 mkb-1 H1 Runs: 87642 - 87647 Tot curr/rate factor: 2.77% C/R F H1Run gated: 2.56% Rand.C.F: 2.09% RCF Run gated: 1.94% Relative ET trigg accept.: 0.4979 PS(LNS): WARNING: for R87644 (~28 Kevents): L4 histos are present, but not OK: pictures for ET are not standard, disturbed; L5 absent. 24/9/94 ======================= Gruber === Lumi RUN# 604 Start lumi run604 date: 24/9/94 Collision time: 20:13:31 - 20:29:17 Currents (mkA): Ie= 28239.00, Ip= 33200.00 Peak luminosity: 0 mb-1 s-1 Peak spec.lumi : 0 mb-1 s-1 mA-2 Number of collided b.: 0 Number of e-filled b.: 0 Number of p-filled b.: 0 Number of e-pilot b.: 0 Number of p-pilot b.: 0 HERA total lumi: 15.4766 mkb-1 H1 Run total lumi: 15.476622 mkb-1 H1 data taken lumi: 15.077093 mkb-1 H1 Runs: 87687 - 87687 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 87687 - 87687 Tot curr/rate factor: 8.25% C/R F H1Run gated: 8.25% Rand.C.F: 21.1% RCF Run gated: 21.1% Relative ET trigg accept.: Not calc. 25/9/94 ======================= Gruber === Lumi RUN# 605 Start lumi run605 date: 25/9/94 Collision time: 0:37:31 - 11:02:54 Currents (mkA): Ie= 30466.00, Ip= 45500.00 Peak luminosity: 2701.44 mb-1 s-1 Peak spec.lumi : 407.160272 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 76394.936579 mkb-1 H1 Run total lumi: 68324.502176 mkb-1 H1 data taken lumi: 58861.966425 mkb-1 H1 Runs: 87695 - 87721 HERA - physics: 65032.631558 mkb-1 H1Run - physics: 57385.367799 mkb-1 H1data - physics: 48796.154235 mkb-1 H1 Runs: 87699 - 87721 Tot curr/rate factor: 1.56% C/R F H1Run gated: 1.57% Rand.C.F: 0.71% RCF Run gated: 0.69% Relative ET trigg accept.: 0.4874 PS(LNS): for R87713 (~82 Kevents): L4 histos OK; L5 absent. 25/9/94 ======================= === Lumi RUN# 606 Start lumi run606 date: 25/9/94 Collision time: 12:20:28 - 21:01:38 Currents (mkA): Ie= 28984.00, Ip= 43900.00 Peak luminosity: 2411.312 mb-1 s-1 Peak spec.lumi : 384.86242 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 46688.353682 mkb-1 H1 Run total lumi: 44142.3064 mkb-1 H1 data taken lumi: 38731.9701 mkb-1 H1 Runs: 87727 - 87742 HERA - physics: 43861.302186 mkb-1 H1Run - physics: 41094.515444 mkb-1 H1data - physics: 36461.574117 mkb-1 H1 Runs: 87731 - 87742 Tot curr/rate factor: 2.16% C/R F H1Run gated: 2.11% Rand.C.F: 0.87% RCF Run gated: 0.86% Relative ET trigg accept.: 0.5127 PS(LNS): for R87735 (~83 Kevents): L4 histos OK; L5 absent. *H1epRuns: 87763 - 87790? RUN# 607 >> 87765=84k 26.09.1994 ===== dice2 ======== H1KFOM === Selected H1Lumi Monitrig.. Today it were selected calibration data samples from the next data sets which were produced with standard job prepared by S.Levonyan at dice1-environment: HERA03.H01.LUMIMON.C9400099 K25394 78048081 00001 ACS-E-C ...... HERA03.H01.LUMIMON.C9400102 K26492 78048081 00001 ACS-E-C It were selected events with (s92=1 only),with ET&PD&VC=1 and with ET&PD&nVC from these data sets (as ordinary) from 512810 events: 1) S92=1 only 27784 events ( 44.4 MBytes) 2) ET&PD&VC 59487 events ( 98.7 MBytes) 3) ET&PD&nVC 49028 events ( 81.4 MBytes) Created data sets were saved at DESY IBM storage at the next data sets H1KFOM.ETPDNVC.M99102.C00 K20004 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M99102.C00 K20294 78048081 00001 ACS-E-C H1KFOM.S92.M99102.C00 K39770 78048081 00001 ACS-E-C These data include events from Lumi RUNs# 600-607 (H1 Runs 87509- 87774). 26.09.1994 ===== dice2 ======== H1KFOM === Relation Coeff.Set 8A Today it was made attempt to produce Rel.Coeff.Set for 8A (low p11) data sample (from H1 Run 87314 up to Run 87457).It were selected 24760 ET&PD&nVC events from this H1 Run range from data set (only G- and M- labeled H1 Runs at H1EP): H1KFOM.ETPDNVC.M9598.C00 K23887 78048081 00001 ACS-E-C After all high mentioned 'cleaning' of 8A(low p11)-data samples it were collected: 24760 events with ET&PD&nVC trigger 29351 events with ET&PD&VC trigger 13997 events with S92-trigger (PD&nVC-events). It were got 24760 ET&PD&nVC from these Runs and it were used for calibration 9275 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 1.035 1.315 0.524 1.091 0.823 1.235 0.970 0.537 0.903 1.067 1.105 0.965 1.013 0.995 1.233 0.974 1.020 1.035 0.996 0.992 0.916 1.012 1.016 1.021 1.003 1.037 0.983 0.991 1.088 0.975 0.923 0.977 1.084 1.007 1.116 1.056 0.000 0.000 0.976 0.836 0.974 1.084 0.000 0.929 0.904 0.924 0.948 1.047 0.000 ==> Relation Coeff.Set for PD 1.852 0.909 1.101 1.500 0.000 1.027 1.020 1.027 1.004 0.988 0.969 1.024 0.999 1.010 1.031 1.002 0.989 0.955 0.972 0.967 1.473 0.947 1.178 0.000 0.000 ==> Sig. at Relation Coeff.Set for ET 0.000 0.004 0.000 0.000 0.003 0.006 0.000 0.000 0.004 0.015 0.006 0.010 0.009 0.012 0.034 0.016 0.018 0.028 0.023 0.017 0.023 0.015 0.017 0.014 0.015 0.017 0.019 0.018 0.016 0.008 0.013 0.005 0.013 0.008 0.008 0.001 0.000 0.000 0.009 0.000 0.003 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 ==> Sig. at Relation Coeff.Set for PD 0.003 0.011 0.005 0.001 0.000 0.018 0.009 0.021 0.008 0.003 0.016 0.040 0.021 0.032 0.006 0.011 0.015 0.017 0.011 0.007 0.010 0.005 0.047 0.000 0.000 ==> Ent. at Relation Coeff.Set for ET 1 4 4 3 6 6 4 2 12 27 19 17 16 16 494 143 191 214 165 270 85 2394 3813 3132 2643 2210 1750 806 927 967 683 727 725 416 304 10 0 0 4 1 4 1 0 1 1 1 1 1 0 ==> Ent. at Relation Coeff.Set for PD 14 8 6 6 0 259 1591 1880 296 14 2604 7290 5858 1194 51 684 2010 851 119 10 13 4 3 0 0 As You can see all sigma values for 'hot' H1Lumi cahnnels RC histos have more or less reasonable values. Runs 87314-87457 (ET&PD&nVC-sample - near 24.8K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.39 1.12 27.42 1.09 27.44 1.05 Runs 87314- 87457 (ET&PD&VC-sample - near 29.4K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.89 1.50 27.89 1.47 As start values of Calibration Coefficients for Photoproduction Branch were got ones after 3rd step of calibration with ET&PD&nVC events from 7Dext.-sample (H1 Runs 87054-87313 - near 60.1 K events). CCvcs value was got from last VCs calibration at 7Dext-sample of ETPDVC events (H1Runs 87054-87313 - see message from 23.09.94 at LL10). (CCvcs start = 4.923 MeV/FADCcount). There are same 'bad' resolution digits again at 8A-sample of events. Attempt to make fit of PhotonArm Energy spectrum was successful (with more or less good statistics). 26.09.1994 ===== dice2 ======== H1KFOM === PDREC-spectra for 8A Today it were produced 100th ntuple for S92=1 events from earlier mentioned 8A-sample with events from Runs 87314-87457: H1KFOM.YLOOKQ4.R87314 (12118 entries) FAST09 3010200E 00000 DASD At interactive LOOK-session it was produced 70th histo for this data set and written into the next LOOK-binary data set: H1KFOM.BLOOKQ3.R87314 6737 entries in 70h FAST12 3010200E 00000 DASD First attempt to fit 70th histo at BLOOKQ2-data set put negative sign of Global Energy Shift at Photon Arm (-2.0%) and enough good resolution digits (16%)only for (10-20)-35GeV regions. It were prepared 100th tuples with ET&PD&nVC and ET&PD&VC-events for procedure of defining Global Energy Shifts and CCvcs: H1KFOM.YLOOKQ2.R87314 24760 entries FAST04 3010200E 00000 DASD H1KFOM.YLOOKQ3.R87314 29351 entries FAST08 3010200E 00000 DASD 26.09.1994 ==================== H1KFOM === Global Shifts,CCvcs 8A It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 1.020 for PD Channels (exept VCs), 0.9878 for ET channels. Correction factor for CCvcs is 0.868. So CCvcs = 4.923*0.868 =4.273Mev FADCcount. These digits are valid for H1Lumi events from Run 87314 up to 87457 Runs 87314- 87457 (ET&PD&nVC-sample - near 24.8K events) xetcut&vcdepcut Step Mean Sigma 0 27.52 1.05 Runs 87314- 87457 (ET&PD&VC-sample - near 29.4K events) xetcut Step Mean Sigma 0 27.52 1.39 P.S. CCp11 at Photoproduction Branch became near 4.3 MeV/FADCcount (almost factor 2 decremention of p11-response). CCe19 was incremented again (on 4%). CCvcs(averaging) was decremented on 13% (!). For any case - this is the final values of CC at Photoproduction branch after 3rd step of calibration with 8A-data sample (H1 Runs 87314-87457): ==> ET Calibr.Coefficients Final Status e01= 4.119 4.188 4.077 3.249 3.923 3.118 3.454 4.367 3.348 4.185 1.914 4.880 3.850 3.694 6.722 2.644 4.472 5.057 4.224 10.461 4.051 e21= 6.910 4.879 5.608 4.637 4.187 4.787 4.213 4.438 4.865 4.157 3.961 5.077 4.719 3.224 4.390 4.643 3.564 3.661 4.402 4.262 4.018 e42= 4.054 3.961 4.336 1.976 3.722 4.138 4.018 ==> PD & VC Calibr.Coefficients Final Status p01= 2.069 1.454 1.500 2.368 2.538 1.298 2.529 2.941 2.149 1.607 2.306 4.280 2.940 2.879 2.099 2.163 1.994 2.650 3.030 2.393 p20= 1.362 1.548 2.358 3.172 2.549 vcs= 4.273 26/9/94 ======================= Rybicki === Lumi RUN# 607 Start lumi run607 date: 26/9/94 Collision time: 1:14:50 - 12:47:35 Currents (mkA): Ie= 29657.00, Ip= 37701.00 Peak luminosity: 2493.605 mb-1 s-1 Peak spec.lumi : 426.180771 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 61198.256257 mkb-1 H1 Run total lumi: 57836.7441 mkb-1 H1 data taken lumi: 53151.109 mkb-1 H1 Runs: 87761 - 87792 HERA - physics: 59046.373761 mkb-1 H1Run - physics: 55577.503554 mkb-1 H1data - physics: 50933.026495 mkb-1 H1 Runs: 87763 - 87792 Tot curr/rate factor: 1.34% C/R F H1Run gated: 1.35% Rand.C.F: 0.75% RCF Run gated: 0.74% Relative ET trigg accept.: 0.4906 PS(LNS): for R87765 (~84 Kevents): L4 histos OK; L5 absent. PS(LNS): Warning(?): E mean for LUMI is 27.7, unusially large. 26.09.1994 ===== dice2 ======== H1KFOM === New CCp11 "jumps"......... Today it was produced LOOK-binary data set with vectors which keep behaivours with time of Calibration Coefficients at Luminosity sub- branch for 'hot' channels: 10022-10028 for central layer at ET (e21- e27) and 20011-20015 - for central layer at PD. These vectors were built for ET&PD&nVC data sample from H1 Run 87459 up to 87774 (54681 events). It was made for defining of new data samples (8B, etc.). This data set is kept at DESY IBM with the next name: H1KFOM.LOOKB.R87459 FAST04 3010200E 00000 DASD From looking for vector 20012 it is clear that last data sets (today collected) is full with new 'jumps' at CCp11 values. As example all last data set it is possible to divide on 9(!) subsets with criteria more or less CCp11 'stability' or 'non-stability': 1) 0- 7000 events - subsample 7Dextended type; 2) 7000- 9000 events - 'jump' at CCp11 on 45% into high region and coming back to (1)-values; there is no any plato values - permanently changing; 3) 9000-13000 events - subsample 7Dextended type; 4) 13000-18000 events - 'jump' at CCp11 on 55% into high region with little plato value; 5) 18000-22000 events - No calibration at Lumi Subbranch at all (unsuccesful Lumi RUN# 601 and problems with PD Movable Platform at start of Lumi RUN# 602; 6) 22000-22500 events - 'jump' at CCp11 on 5% into high region during short attempt of Luminosity subbranch calibration; 7) 22500-23500 events - No calibration at Lumi Subbranch at all (problems with PD Movable Platform at start of Lumi RUN# 602 (as seems)); 8) 23500-27500 events - 'jump' at CCp11 on 20% into high region - subsample 8A type; 9) 27500-54681 events - 'jump' at CCp11 on 15% into low region - subsample 'intermediate' between 7Dext and 8A. Good base for new samples of calibration data. It will be very difficult to make calibration for first half of early mentioned data samples (Lumi RUNs#600-602). Last part of data samples can be good calibrated (Lumi RUN# 603 etc.). 26.09.1994 ==================== H1KFOM === New RC Sets in H1DataBase As final action of all 26.09.94 calibration steps it was made update of LFRC and LESC banks at H1DataBase with S.Levonyan's tool. All Relation Coefficients values, CCvcs and Global Energy Shift constants were got from the next messages at LLO: 26.09.1994 ----- dice2 -------- H1KFOM --- Relation Coeff.Set 8A 26.09.1994 -------------------- H1KFOM --- Global Shifts,CCvcs 8A Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LFRC (_501) 43 e-p data 409261602 87314 0 77 940926 H1KFOM Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LESC (_582) 51 e-p data 409261602 87314 0 3 940926 H1KFOM 26.09.1994 ==================== F11LEV === Proposal for new e-taggers An information on the official Proposal for the new electron taggers can be obtained from the PostScript file at DESY IBM: F11LEV.NEWET.TEXT.PS The same text is now given to Sabine Platz as H1 note (H1-09/94-383) and should be announced soon. Further prospects depend on the decision of DESY directorate and PRC, to be held in October at DESY. According to the preliminary information and few common discussions, ZEUS also expressed an interest to similar project. Most difficult part is a modification of the beampipe sections. 27/9/94 ======================= === Lumi RUN# 608 Start lumi run608 date: 26/9/94 Collision time: 16:11:30 - 0:20:16 Currents (mkA): Ie= 28863.00, Ip= 36800.00 Peak luminosity: 1787.027 mb-1 s-1 Peak spec.lumi : 333.060602 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 33088.621003 mkb-1 H1 Run total lumi: 30561.4631 mkb-1 H1 data taken lumi: 25141.7097 mkb-1 H1 Runs: 87803 - 87837 HERA - physics: 31840.134077 mkb-1 H1Run - physics: 29601.035455 mkb-1 H1data - physics: 24294.924286 mkb-1 H1 Runs: 87820 - 87837 Tot curr/rate factor: 3.42% C/R F H1Run gated: 3.41% Rand.C.F: 1.32% RCF Run gated: 1.28% Relative ET trigg accept.: 0.5067 PS(LNS): for R87830 (~49 Kevents): L4 histos OK; L5 absent. 27/9/94 ======================= h01usa === Lumi RUN# 609 Start lumi run609 date: 27/9/94 Collision time: 1:26:39 - 6:06:36 Currents (mkA): Ie= 29301.00, Ip= 34400.00 Peak luminosity: 1645.948 mb-1 s-1 Peak spec.lumi : 309.810402 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 20231.308621 mkb-1 H1 Run total lumi: 19392.6981 mkb-1 H1 data taken lumi: 16120.9929 mkb-1 H1 Runs: 87838 - 87847 HERA - physics: 19347.229378 mkb-1 H1Run - physics: 18035.943111 mkb-1 H1data - physics: 14833.962917 mkb-1 H1 Runs: 87839 - 87847 Tot curr/rate factor: 2.17% C/R F H1Run gated: 2.2% Rand.C.F: 1.24% RCF Run gated: 1.24% Relative ET trigg accept.: 0.5158 PS(LNS): for R87842 (~51 Kevents): L4 histos OK; L5 absent. PS(LNS): Warning: E_Etag: a "shoulder at >20Gev" appiered. 27/9/94 ===================== K.Rybicki === Lumi RUN# 610 Start lumi run610 date: 27/9/94 Collision time: 16:55:19 - 21:15:30 Currents (mkA): Ie= 28053.00, Ip= 36400.00 Peak luminosity: 1275.04 mb-1 s-1 Peak spec.lumi : 290.034742 mb-1 s-1 mA-2 Number of collided b.: 150 Number of e-filled b.: 165 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 20 HERA total lumi: 17648.40731 mkb-1 H1 Run total lumi: 15699.1294 mkb-1 H1 data taken lumi: 12968.4044 mkb-1 H1 Runs: 87904 - 87938 HERA - physics: 14087.944386 mkb-1 H1Run - physics: 11559.79752 mkb-1 H1data - physics: 9214.985123 mkb-1 H1 Runs: 87915 - 87938 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 1.45% RCF Run gated: 1.41% Relative ET trigg accept.: 0.4879 PS(LNS): for R87923 (~26 Kevents): L4 histos OK; L5 absent. PS(LNS): Warning: E_Etag: a "shoulder at >20Gev" appiered. 28.09.1994 ===== dice2 ======== H1KFOM === 8B,8C,8D,8E Calibr.Samples Today it was made attempt to define calibration data samples with 26.09.94 mentioned criteria of CCp11 jumps at last data samples (99102) H1KFOM.ETPDNVC.M99102.C00 K20004 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M99102.C00 K20294 78048081 00001 ACS-E-C H1KFOM.S92.M99102.C00 K39770 78048081 00001 ACS-E-C As You can see first 3 calibration data samples have very poor statistics of ET&PD&nVC events (9146,3872 and 3866) and (as seems) it will be impossible to make 'standard' H1Lumi Calibration ofthis data (45.3+11.2+30.9=87.4nb-1). Relation Coefficients, Global Energy Shifts and CCvcs which were defined for 8A-calibration data sample will work for this data. May be it will be possible to make 'tuning' of Global Shifts and CCvcs for low mentioned 8B,8C and 8D calibration data sampls with using of Relation Coefficients Sets of 8A data samples. Calibration data samples 8E will be extended with latest data and 'standard' calibration procedure for 8E will be made later. This is short characteristics of 8B,8C,8D and 8E calibration data samples with explaining of reasons to skip on another data sample: 8B - H1 Runs 87459 - 87526-(exept 87521 which labeled as Good Run but (Lumi RUNs#599-600) excluded due to CCp11 jumps up and down collected from: during this Run); 21/09/94 15:35:18 - exept 87526 which labeled as Good Run but up to excluded due to CCp11 jump into high value 22/09/94 12:21:28 during this Run); - 1 Non G- and M- Runs: 87509 Int.Lumi=45.3nb-1 - near 9146 ET&PD&nVC events(after cleaning) -------- - near 45.3 nb-1 of H1 Gated Lumi at this H1 Runs Range (15.5 nb-1 at 87521,87526) - go to 8C due to CCp11 "+"jump at Run 87526 (22/09/94 between 10:59 and 12:21) 8C - H1 Runs 87533 - 87556 (Rest of Lumi RUN#600) - 0 Non G- and M- Runs: - collected from: - near 3872 ET&PD&nVC events 22/09/94 12:30:04 - near 11.2 nb-1 of H1 Gated Lumi at this up to H1 Runs Range 22/09/94 16:12:01 - go to 8D due to CCp11 "+"jump at start of Lumi RUN# 602 (after unsuccesful Lumi RUN# Int.Lumi=11.2nb-1 601, problems with PD Movable Platforms -------- and may be H1 Main Solenoid Ramping Up at midnight between 22-23/09/94) (23/09/94 near 05:34) 8D - H1 Runs 87582 - 87687 (Lumi RUNs#602-604) - 11 Non G- and M- Runs: 87582-87584,87633- collected from: 87640,87646-87687 23/09/94 05:34:18 - near 3866 ET&PD&nVC events(after cleaning) up to - near 38.9 nb-1 of H1 Gated Lumi at this 24/09/94 21:31:06 H1 Runs Range (8.0 nb-1 at non M- and G-) - go to 8E due to CCp11 "-"jump at start of Int.Lumi=30.9nb-1 Lumi RUN# 605 (from H1 Run 87695) -------- (25/09/94 near 00:28) 8E - H1 Runs 87695 - 87774 ...(will be extended) (Lumi RUNs#605-607..)- 9 Non G- and M- Runs: 87695-87696,87701- collected from: 87703,87727-87731, 25/09/94 00:28:23 87761 up to - with possible extension with latest data 26/09/94 05:45:17 - near 25675 ET&PD&nVC events(after cleaning - near 123.9 nb-1 of H1 Gated Lumi at this Int.Lumi=115.2 nb-1 H1 Runs Range (8.7 nb-1 at non M- and G-) ---------- 28.09.1994 ===== dice2 ======== H1KFOM === Tuning of CC for 8B-sample Today it was made first attempt to tune Global Energy Shifts and CCvcs for 8B-sample with using of Relation Coefficients which were produced for 8A-sample. As seems this attempt is unsuccesful. Main reason of unsuccesful attempt was 'bad' Photon Arm Energy Spectrum Fit - 2 attempts of fit with all events (3897 entries at 70th histo -BLOOKQ2.R87459) and with events without Run 87521 and 87526 (2482 entries at 70th histo - BLOOKQ3.R87459) put bad resolution digits (32-35%) and unreasonable values of Global Photon Energy Spectrum Shifts (from -6.5 up -7.5%) Diagnose 'unreasonable' appeared due to very bad Sigma values which were obtained at ETrec+PDrec energy spectra after involving this large Global Shift (1.07-->1.15 for ET&PD&nVC and 1.32-->1.38 for ET&PD&VC events). If we shall use the same Global Shifts and CCvcs as for 8A-samples: mean=27.55 Sigma = 1.07 for ET&PD&nVC events (with best cuts) and mean=27.36 Sigma = 1.32 for ET&PD&VC events (with best cuts). May be best way to try 'standard' Calibration procedure for 8B? 28/9/94 ================ J. Spiekermann === Lumi RUN# 611 Start lumi run611 date: 28/9/94 Collision time: 14:18:31 - 23:46:54 Currents (mkA): Ie= 31833.00, Ip= 37000.00 Peak luminosity: 1746.955 mb-1 s-1 Peak spec.lumi : 313.478355 mb-1 s-1 mA-2 Number of collided b.: 152 Number of e-filled b.: 167 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 18 HERA total lumi: 40277.989702 mkb-1 H1 Run total lumi: 35911.1112 mkb-1 H1 data taken lumi: 26855.5005 mkb-1 H1 Runs: 87986 - 88007 HERA - physics: 38045.001193 mkb-1 H1Run - physics: 32603.768266 mkb-1 H1data - physics: 24898.236616 mkb-1 H1 Runs: 87992 - 88007 Tot curr/rate factor: 3.39% C/R F H1Run gated: 3.4% Rand.C.F: 1.29% RCF Run gated: 1.29% Relative ET trigg accept.: 0.4781 PS(LNS): for R88004 (~55 Kevents): L4 histos OK; L5 absent. PS(LNS): Warning: E_Etag: a "shoulder at >20Gev" is yet existing. 29/9/94 ================== A.Buniatian === Lumi RUN# 612 Start lumi run612 date: 29/9/94 Collision time: 2:15:44 - 8:22:28 Currents (mkA): Ie= 24300.00, Ip= 31700.00 Peak luminosity: 1386.885 mb-1 s-1 Peak spec.lumi : 354.820471 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 22306.182742 mkb-1 H1 Run total lumi: 21842.4671 mkb-1 H1 data taken lumi: 19448.1779 mkb-1 H1 Runs: 88014 - 88023 HERA - physics: 20880.007694 mkb-1 H1Run - physics: 19762.410028 mkb-1 H1data - physics: 17405.317214 mkb-1 H1 Runs: 88015 - 88023 Tot curr/rate factor: 1.74% C/R F H1Run gated: 1.75% Rand.C.F: 0.82% RCF Run gated: 0.81% Relative ET trigg accept.: 0.5082 PS(LNS): for R88020 (~57 Kevents): L4 histos OK; L5 absent. PS(LNS): Warning: E_Etag: a "shoulder at >20Gev" is yet existing. 29.09.1994 ===== dice2 ======== H1KFOM === 8A Rel.Coeff. for 8B,8C,8D Today it were produced 100th ntuples for 8B,8C and 8D calibration samples with using of Relation Coefficients which were defined for 8A - data samples and with using CCvcs=4.273 MeV/FADCcount (see LL10 messages from 26.09.94). 100th ntuples are kept at next data sets at DESY IBM: 8B sample: i ---------- H1KFOM.YLOOKQ2.R87459 14438 entries FAST01 3010200E 00000 DASD H1KFOM.YLOOKQ3.R87459 16254 entries FAST08 3010200E 00000 DASD H1KFOM.YLOOKQ4.R87459 8623 entries FAST09 3010200E 00000 DASD 8C sample: --------- H1KFOM.YLOOKQ2.R87533 3872 entries FAST04 3010200E 00000 DASD H1KFOM.YLOOKQ3.R87533 4429 entries FAST08 3010200E 00000 DASD H1KFOM.YLOOKQ4.R87533 1772 entries FAST02 3010200E 00000 DASD 8D sample: --------- H1KFOM.YLOOKQ2.R87582 3835 entries FAST01 3010200E 00000 DASD H1KFOM.YLOOKQ3.R87582 4090 entries FAST08 3010200E 00000 DASD H1KFOM.YLOOKQ4.R87582 2179 entries FAST16 3010200E 00000 DASD Next Mean and Sigma values are seen at ETrec+PDrec energy spectra if Global Energy Shifts defined for 8A-samples are used (0.9878 for ET and 1.020 for PD): 8B sample: i ---------- Runs 87459- 87526 (ET&PD&nVC-sample - near 14.4K events) xetcut&vcdepcut Step Mean Sigma 0 27.55 1.07 Runs 87459- 87526 (ET&PD&VC-sample - near 16.3K events) xetcut Step Mean Sigma 0 27.26 1.32 Unsuccesfull PDfit with both LOOK-binary data sets(BLOOKQ2,BLOOKQ3) There are 3897 entries at 70th histo at BLOOKQ2.R87459 and 2482 entries at BLOOKQ3.R87459 data sets. 8C sample: --------- Runs 87533 - 87556 (ET&PD&nVC-sample - near 3.9K events) xetcut&vcdepcut Step Mean Sigma 0 27.54 0.97 Runs 87533- 87556 (ET&PD&VC-sample - near 4.4K events) xetcut Step Mean Sigma 0 27.48 1.23 PDfit with reasonable digits (resolution near 17%, shift near-2%) at 22-35 GeV region. There are 967 entries at 70th histo of BLOOKQ2.R87533 data set. 8D sample: --------- Runs 82582 - 87687 (ET&PD&nVC-sample - near 3.9K events) xetcut&vcdepcut Step Mean Sigma 0 27.59 1.09 Runs 87582- 87687 (ET&PD&VC-sample - near 4.1K events) xetcut Step Mean Sigma 0 27.39 1.23 Unsuccesful PDfit (all resolution digits are 35 %).1044 entries at 70th histo of data set BLOOKQ2.R87582. 29.09.1994 ==================== H1KFOM === LRTL Data at H1Status Today I was surprized when I found at old file HERA03.H1STATUS.MEX new contents. Some time ago only H1 Shift Crew lines were updated more or less regularly. Now there are a lot of useful information about current H1 Status - Run Number, Runs Status, Event size, XIMASK and another H1CDAQ status words, H1CentralTrigger Status words and Trigger Phase status, Information about H1 Magnet Status, Current value of H1 Dead Time and prepared at H1Lumi 3 words from LRTL-bank: 232 CTLV I 0 +INF ! Current Total Luminosity Value ! (averaged over the last 10 sec., in ! units of 10**25 cm-2s-1) 233 RUNLUMI I 0 +INF ! Total Integrated Luminosity from the ! beginning of the run ! (in units 10**25 cm-2 = 0.01 mb-1) 234 RH1LUMI I 0 +INF ! H1 Integrated Luminosity from the ! beginning of the run (during H1active) ! (in units 10**25 cm-2 = 0.01 mb-1) #D=1994-09-29-14:18:06#K=BEGIN #T=1#V= 780844686 #U=#E= #D=1994-09-29-14:18:06#K= Run Nr#T=1#V= 88069 #U=#E= #D=1994-09-29-14:18:06#K= Status#T=3#V= RUNNING #U=#E= #D=1994-09-29-14:18:06#K= Start#T=3#V= 14:17:46 #U=#E= #D=1994-09-29-14:18:06#K=Event Nr#T=1#V= 10 #U=#E= #D=1994-09-29-14:18:06#K=Evt Size#T=2#V= 0.18516E+02 #U=[KB]#E= #D=1994-09-29-14:18:06#K=Log Rate#T=2#V= 0.00000E+00 #U=[Hz]#E= #D=1994-09-29-14:18:06#K= XIMASK#T=1#V= 4094 #U=#E= #D=1994-09-29-14:18:06#K= FEBMASK#T=1#V= 443 #U=#E= #D=1994-09-29-14:18:06#K= SYSMODE#T=1#V= 53249 #U=#E= #D=1994-09-29-14:18:06#K= DAQMODE#T=1#V= -2146434811 #U=#E= #D=1994-09-29-14:18:06#K=DeadTime#T=2#V= 0.10000E+03 #U=[%]#E= #D=1994-09-29-14:18:06#K=I_Compen#T=1#V= 863 #U=[A]#E= #D=1994-09-29-14:18:06#K= I_Solen#T=1#V= 5486 #U=[A]#E= #D=1994-09-29-14:18:06#K=I_Toroid#T=1#V= 65387 #U=[A]#E= #D=1994-09-29-14:18:06#K=Tr Phase#T=3#V= PHASE 0 #U=#E= #D=1994-09-29-14:18:06#K=Tr word1#T=1#V= 10223936 #U=#E= #D=1994-09-29-14:18:06#K=SubTrig0#T=1#V= -513 #U=#E= #D=1994-09-29-14:18:06#K=SubTrig1#T=1#V= -105547 #U=#E= #D=1994-09-29-14:18:06#K=SubTrig2#T=1#V= -1 #U=#E= #D=1994-09-29-14:18:06#K=SubTrig3#T=1#V= -1308622849 #U=#E= #D=1994-09-29-14:18:06#K=H1 CDAQ1#T=3#V= W.Hildesheim #U=#E= #D=1994-09-29-14:18:06#K=H1 CDAQ2#T=3#V= A.Buniatian #U=#E= #D=1994-09-29-14:18:06#K=H1 CDAQ3#T=3#V= J.Haack #U=#E= #D=1994-09-29-14:18:06#K=H1 CDAQ4#T=3#V= G.Pope #U=#E= #D=1994-09-29-14:18:06#K=Data Log#T=3#V= SGI #U=#E= #D=1994-09-29-14:18:06#K=CurrLumi#T=2#V= 0.00000E+00 #U=[mb**(-1)]#E= #D=1994-09-29-14:18:06#K=Int ungL#T=2#V= 0.00000E+00 #U=[mb**(-1)]#E= #D=1994-09-29-14:18:06#K=Int gatL#T=2#V= 0.00000E+00 #U=[mb**(-1)]#E= #D=1994-09-29-14:18:06#K=READY #T=4#V= =1994-09-29-14:18:06 #U=#E= Units at CurrLumi line it is needed to understand as mb**(-1)sec(-1). 30/9/94 ================ J. Spiekermann === Lumi RUN# 613 Start lumi run613 date: 29/9/94 Collision time: 19:13:53 - 1:57:57 Currents (mkA): Ie= 28816.00, Ip= 44200.00 Peak luminosity: 2426.473 mb-1 s-1 Peak spec.lumi : 363.249192 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 42609.4658 mkb-1 H1 Run total lumi: 37311.7667 mkb-1 H1 data taken lumi: 29009.4663 mkb-1 H1 Runs: 88080 - 88098 HERA - physics: 40636.829042 mkb-1 H1Run - physics: 35784.5934 mkb-1 H1data - physics: 27636.158 mkb-1 H1 Runs: 88082 - 88098 Tot curr/rate factor: 0.21% C/R F H1Run gated: 0.29% Rand.C.F: 1.16% RCF Run gated: 1.11% Relative ET trigg accept.: 0.4878 *H1epRuns: 88082 - 88098? RUN# 613 >> 88090=54k- 88096=26k PS(LNS): for R88090 (~54 Kevents): L4 histos absent, strange. PS(LNS): for R88096 (~26 Kevents): L4 histos OK; L5 absent. PS(LNS): Warning: E_Etag: a "shoulder at >20Gev" has dissiapiered. 30.09.1994 ==================== H01GOG === LUMIMON data processing Here is a continuation of a summary table for e+p LUMIMON files, processed so far. ---------------------------------------------------------------------- File H1 runs Events Actual triggers (xx) s86 s91 s92 s93 s94 s95 ---------------------------------------------------------------------- 98 87423-87509 128228 13368 5409 7018 7434 8426 8915 99 87509-87579 127731 10310 6609 8499 9422 10146 10972 100 87579-87712 128724 13978 3719 5439 4448 6449 6256 101 87712-87733 128167 7277 6366 7069 10849 8989 10857 102 87733-87774 128188 9947 5510 6470 8556 8253 9476 103 87774-87830 127983 9674 5871 7144 8861 9071 9955 104 87830-88004 129655 13852 4298 5238 7420 6420 7266 105 88004-88092 130190 12877 5417 6630 8470 8152 9092 ---------------------------------------------------------------------- As it was mentioned in the previous message from 22.09 a peak at x_PD=-2cm (PD-11 channel) appeared again. (According to several messages of Sasha Fomenko in LLO, this channel is known also like giving the problems in the calibration procedure). Therefore, I have used last files 96-104 to obtain some statistical information about possible influence of this defect on various LUMI triggers. It is briefly summarized below. 1) Amount of such "false PD-11 events" among all events with E_gamma > 3 GeV is (now) small - only 1.3% 2) Reconstructed energy for these events is clustered around E_gamma = 9+-2GeV 3) The contamination of such events into various LUMI subtriggers is negligible: s86(eTAG) = 0.2% s91(PD_low) = 0.6% s92(L_cal) = 0.8% s93(VC) = 0.02% s94(ET*PD*nVC) = 0.06% s95(ET*PD*VC) = 0.03% Thus for our online lumi trigger (ET*PD) the contribution from these events is also negligible (<0.04%) By the way, what is now a real definition for s92(L_cal) trigger? 30/9/94 ================ J. Spiekermann === Lumi RUN# 614 Start lumi run614 date: 30/9/94 Collision time: 3:21:18 - 9:58:38 Currents (mkA): Ie= 29170.00, Ip= 43401.00 Peak luminosity: 2372.101 mb-1 s-1 Peak spec.lumi : 365.192227 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 37699.812429 mkb-1 H1 Run total lumi: 33611.9605 mkb-1 H1 data taken lumi: 30135.5802 mkb-1 H1 Runs: 88100 - 88115 HERA - physics: 34510.566361 mkb-1 H1Run - physics: 28377.86562 mkb-1 H1data - physics: 25105.219984 mkb-1 H1 Runs: 88101 - 88115 Tot curr/rate factor: 1.27% C/R F H1Run gated: 1.33% Rand.C.F: 1.08% RCF Run gated: 1.1% Relative ET trigg accept.: 0.5074 30/9/94 ==================== K.Rybicki === Lumi RUN# 615 Start lumi run615 date: 30/9/94 Collision time: 11:24:50 - 12:42:41 Currents (mkA): Ie= 12629.00, Ip= 41800.00 Peak luminosity: 864.665 mb-1 s-1 Peak spec.lumi : 323.685394 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 3969.527808 mkb-1 H1 Run total lumi: 1972.848784 mkb-1 H1 data taken lumi: 1256.427953 mkb-1 H1 Runs: 88130 - 88135 HERA - physics: 1747.512327 mkb-1 H1Run - physics: 1195.859884 mkb-1 H1data - physics: 744.758653 mkb-1 H1 Runs: 88133 - 88135 Tot curr/rate factor: 0.69% C/R F H1Run gated: 0.81% Rand.C.F: 0.48% RCF Run gated: 0.48% Relative ET trigg accept.: 0.4713 30/9/94 ==================== K.Rybicki === Lumi RUN# 616 Start lumi run616 date: 30/9/94 Collision time: 17:39:27 - 17:45:44 Currents (mkA): Ie= 19144.00, Ip= 44500.00 Peak luminosity: 0 mb-1 s-1 Peak spec.lumi : 0 mb-1 s-1 mA-2 Number of collided b.: 0 Number of e-filled b.: 0 Number of p-filled b.: 170 Number of e-pilot b.: 0 Number of p-pilot b.: 170 HERA total lumi: 0.6872 mkb-1 H1 Run total lumi: 0.616373 mkb-1 H1 data taken lumi: 0.607494 mkb-1 H1 Runs: 88156 - 88157 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 88157 - 88157 Tot curr/rate factor: 0.03% C/R F H1Run gated: 0.03% Rand.C.F: Not calc.% RCF Run gated: Not calc.% Relative ET trigg accept.: Not calc. 1/10/94 ===================== A.Usik === Lumi RUN# 618 Start lumi run618 date: 30/9/94 Collision time: 18:30:03 - 2:01:12 Currents (mkA): Ie= 31050.00, Ip= 44500.00 Peak luminosity: 2710.457 mb-1 s-1 Peak spec.lumi : 376.393445 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 57515.047521 mkb-1 H1 Run total lumi: 46229.805236 mkb-1 H1 data taken lumi: 31917.941894 mkb-1 H1 Runs: 88160 - 88205 HERA - physics: 56394.868297 mkb-1 H1Run - physics: 44536.928083 mkb-1 H1data - physics: 30586.036696 mkb-1 H1 Runs: 88161 - 88205 Tot curr/rate factor: 1.28% C/R F H1Run gated: 1.24% Rand.C.F: 1.15% RCF Run gated: 1.11% Relative ET trigg accept.: 0.5087 1/10/94 ===================== A.Usik === Lumi RUN# 619 Start lumi run619 date: 1/10/94 Collision time: 3:15:14 - 8:39:47 Currents (mkA): Ie= 30429.00, Ip= 43500.00 Peak luminosity: 2466.455 mb-1 s-1 Peak spec.lumi : 356.236285 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 36021.922768 mkb-1 H1 Run total lumi: 35500.6846 mkb-1 H1 data taken lumi: 29800.9199 mkb-1 H1 Runs: 88208 - 88214 HERA - physics: 34721.916593 mkb-1 H1Run - physics: 32339.784615 mkb-1 H1data - physics: 26778.367839 mkb-1 H1 Runs: 88210 - 88214 Tot curr/rate factor: 0.91% C/R F H1Run gated: 0.9% Rand.C.F: 1.25% RCF Run gated: 1.25% Relative ET trigg accept.: 0.5037 1/10/94 =================== K.Rybicki === Lumi RUN# 620 Start lumi run620 date: 1/10/94 Collision time: 17:29:15 - 17:39:51 Currents (mkA): Ie= 33226.00, Ip= 46000.00 Peak luminosity: 0 mb-1 s-1 Peak spec.lumi : 0 mb-1 s-1 mA-2 Number of collided b.: 0 Number of e-filled b.: 0 Number of p-filled b.: 170 Number of e-pilot b.: 0 Number of p-pilot b.: 170 HERA total lumi: 1109.297561 mkb-1 H1 Run total lumi: 1109.297026 mkb-1 H1 data taken lumi: 1090.140064 mkb-1 H1 Runs: 88224 - 88224 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 88224 - 88224 Tot curr/rate factor: 4.8% C/R F H1Run gated: 4.8% Rand.C.F: 2.98% RCF Run gated: 2.98% Relative ET trigg accept.: Not calc. 1/10/94 =================== K.Rybicki === Lumi RUN# 621 Start lumi run621 date: 1/10/94 Collision time: 20:52:40 - 22:23:27 Currents (mkA): Ie= 31086.00, Ip= 45600.00 Peak luminosity: 3174.028 mb-1 s-1 Peak spec.lumi : 449.694076 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 15341.214118 mkb-1 H1 Run total lumi: 15032.8432 mkb-1 H1 data taken lumi: 12747.2169 mkb-1 H1 Runs: 88230 - 88233 HERA - physics: 11693.90737 mkb-1 H1Run - physics: 7826.988655 mkb-1 H1data - physics: 6807.062849 mkb-1 H1 Runs: 88231 - 88233 Tot curr/rate factor: 1.79% C/R F H1Run gated: 1.8% Rand.C.F: 1.7% RCF Run gated: 1.7% Relative ET trigg accept.: 0.4387 2/10/94 ================== A.Buniatian === Lumi RUN# 622 Start lumi run622 date: 2/10/94 Collision time: 4:40:58 - 8:00:09 Currents (mkA): Ie= 28711.00, Ip= 50400.00 Peak luminosity: 3633.823 mb-1 s-1 Peak spec.lumi : 482.719552 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 34308.285424 mkb-1 H1 Run total lumi: 33253.4875 mkb-1 H1 data taken lumi: 24139.9245 mkb-1 H1 Runs: 88249 - 88259 HERA - physics: 31004.241881 mkb-1 H1Run - physics: 29537.17338 mkb-1 H1data - physics: 20718.220518 mkb-1 H1 Runs: 88250 - 88259 Tot curr/rate factor: 2.77% C/R F H1Run gated: 2.78% Rand.C.F: 1.17% RCF Run gated: 1.17% Relative ET trigg accept.: 0.4924 PS(LNS): for R88251 (~23 Kevents): L4 histos OK; L5 OK, too. PS(LNS): for R88258 (~52 Kevents): L4 histos OK; L5 just a few events! PS(LNS): for R88258 SOS-WARNING: L4 histos OK but L5 just a few events! 03.10.1994 ==================== F11LEV === LUMI system configuration. This is an important question, addressed to the attention of the relevant experts. Please consider it seriousely and prepare your arguments before our next group meeting (after arrival of bosses). Recently, I had an informal discussion with several ZEUS people related to their LUMI system. We talked about: 1) New e-taggers (projects & prospects) 2) Background at the present e-tagger 3) Configuration and performance of the gamma-arm. Here I want to comment only the last point. As may be some of you know, after very first ep-run at HERA ZEUS removed their Veto counter from the gamma-arm completely. This was done because of the negative experience with the original (similar to our present) configuration. They also moved their sinchrotron absorber close to the gamma-detector, such, that this is now in fact a first layer in their samling sandwich calorimeter. As a result, they are very happy with the present situation. They claim, they are sure that now PD has a linear response down to 1 GeV. This also improves a resolution of those 90% of gammas, which convert in 3X0 filter. Therefore, I propose to the experts to consider a similar change in our system. Below I summarize my own arguments pro and contra such a modification. 1) First, to be honest, one has to remind, that our VC is probably better, compared to their old (gas counter). Nevertheless. 2) The only important function, presently left for our VC is a triggering and selection of clean, non-showering photons for the purpose of KRS calibration. Other task, being important in 93 (offline lumi cross check and e-tagger acceptance verification) is now better done by the new PD_low trigger. Note, that the original proposal - to use ET*PD*!VC trigger for the online lumi measurements - was NEVER realized, since from the very beginning it became clear, that we cannot reliably calculate the overall acceptance for such a trigger (which in addition is proportional to the HV on veto, not only ~ to the luminosity) 3) Problems, arising from VC: a) non-linearity of the overall E_gamma (depends how much was deposited in a water) b) difficulties with the VC-calibration (only in average it is OK, the resolution for showring gammas is probably worse than it would be if we follow ZEUS scheme: no VC+absorber close to PD) c) instabilities and other bad influence on the gamma-arm trigger, since VC-responce is included in gamma-arm trigger elements d) the same bad influence in all cases of accidentally high rates seen by VC 4) Positive information delivered by VC: a) better resolution for ~10% of all photons with E_veto<0.2GeV b) some rate information permanently available from the photon arm, even during injection and ramping. c) triggering on very low energy photons with reasonable efficiency (~80% for E_gamma>2GeV and ~50% at E_gamma=1GeV). This kind of trigger we cannot expect from the KRS calorimeter (corresponding threshold of the present PD_low is 4-5GeV) 5) We have to weight "+" against "-" in order to take a right decision Where the energy scale linearity is important? First of all, if we anywhen want to achieve a precision of lumi measurement better than 3% (ZEUS aims even for 1% in 1995) Where it is important to trigger on low (~1-3GeV) photons? Mainly, for the new e-taggers, where the acceptance would be exactly in that region. Then we would need a) to determine e-tag acceptances from the data (as we do now), using lumi events. This however can be done even from the random triggers; one needs to be able to RECONSTRUCT low energy photons (down to 1GeV), rather than to trigger on them. And the reliable reconstruction is only possible, if E-scale is correct in this region as well; b) to veto these low energy photons for new eTAG trigger elements in order to reduce background rate from ep-bremsstrahlung c) to select lumi events for new taggers calibration (if no other possibilities for their calibration will be found) Question to Igor: what could be a lowest possible threshold for 5*5 channel KRS detector in absolute GeV scale, before it starts to pick up too much noise? 03.10.1994 ===== dice2 ======== H1KFOM === Selected H1Lumi Monitrig.. Today it were selected calibration data samples from the next data sets which were produced with standard job prepared by S.Levonyan at dice1-environment: HERA03.H01.LUMIMON.C9400103 K42323 78048081 00001 ACS-E-C ...... HERA03.H01.LUMIMON.C9400107 K10662 78048081 00001 ACS-E-C It were selected events with (s92=1 only),with ET&PD&VC=1 and with ET&PD&nVC from these data sets (as ordinary): 1) S92=1 only 31282 events ( 50.4 MBytes) 2) ET&PD&VC 60315 events (100.2 MBytes) 3) ET&PD&nVC 49907 events ( 83.0 MBytes) Created data sets were saved at DESY IBM storage at the next data sets H1KFOM.ETPDNVC.M103107.C00 K35976 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M103107.C00 K44038 78048081 00001 ACS-E-C H1KFOM.S92.M103107.C00 K35985 78048081 00001 ACS-E-C These data include events from Lumi RUNs# 607-621 (H1 Runs 87774- 88232). 03.10.1994 ===== dice2 ======== H1KFOM === Relation Coeff.Set 8E Today it was made attempt to produce Rel.Coeff.Set for 8E (low p11) data sample (from H1 Run 87695 up to Run 88022).It were selected 56014 ET&PD&nVC events from this H1 Run range from data sets (only G- and M- labeled H1 Runs at H1EP): H1KFOM.ETPDNVC.M99102.C00 K20004 78048081 00001 ACS-E-C H1KFOM.ETPDNVC.M103107.C00 K35976 78048081 00001 ACS-E-C After all high mentioned 'cleaning' of 8E(low p11)-data samples it were collected: 56014 events with ET&PD&nVC trigger 69329 events with ET&PD&VC trigger 27603 events with S92-trigger (PD&nVC-events). It were got 56014 ET&PD&nVC from these Runs and it were used for calibration 21400 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 1.033 1.281 0.516 1.029 0.809 1.181 0.948 0.530 0.888 1.020 0.968 0.997 0.949 1.056 1.327 0.902 0.980 0.926 0.926 0.909 0.948 0.999 1.001 0.989 0.985 1.010 0.952 0.948 1.098 1.018 0.994 0.990 0.944 1.041 1.041 1.039 0.784 1.272 1.013 0.860 0.982 1.083 0.941 0.930 0.898 0.913 0.938 1.048 0.000 ==> Relation Coeff.Set for PD 1.842 0.932 1.041 1.507 0.944 0.991 1.077 1.032 1.055 1.014 0.990 1.041 1.019 1.018 0.999 1.079 1.067 1.023 1.029 0.962 1.458 0.913 1.146 1.013 0.923 ==> Sig. at Relation Coeff.Set for ET 0.001 0.009 0.003 0.007 0.004 0.009 0.004 0.013 0.002 0.011 0.012 0.008 0.007 0.010 0.004 0.005 0.012 0.009 0.006 0.006 0.013 0.014 0.015 0.014 0.012 0.018 0.019 0.011 0.005 0.011 0.008 0.007 0.015 0.009 0.009 0.031 0.009 0.033 0.005 0.027 0.003 0.002 0.000 0.000 0.000 0.005 0.000 0.000 0.000 ==> Sig. at Relation Coeff.Set for PD 0.004 0.001 0.004 0.004 0.000 0.021 0.015 0.014 0.016 0.001 0.014 0.022 0.015 0.013 0.012 0.013 0.020 0.017 0.025 0.005 0.008 0.008 0.006 0.004 0.000 ==> Ent. at Relation Coeff.Set for ET 5 34 5 14 19 25 11 7 49 104 90 117 82 54 1510 264 402 346 379 626 265 5686 8893 6969 5814 4958 3983 1816 2493 2757 2156 1768 1262 1058 566 29 10 13 6 3 5 3 2 3 1 6 2 2 0 ==> Ent. at Relation Coeff.Set for PD 41 17 19 7 1 713 3714 3075 576 22 7127 17182 12248 2594 99 2568 6380 2616 387 24 24 16 21 7 3 As You can see all sigma values for 'hot' H1Lumi cahnnels RC histos have more or less reasonable values. Runs 87695-88022 (ET&PD&nVC-sample - near 56.0K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.38 1.05 27.37 1.02 27.42 1.00 Runs 87695- 88022 (ET&PD&VC-sample - near 69.3K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.18 1.30 27.17 1.28 As start values of Calibration Coefficients for Photoproduction Branch were got ones after 3rd step of calibration with ET&PD&nVC events from 8A-sample (H1 Runs 87314-87457 - near 24.7 K events). CCvcs value was got from last VCs calibration at 8A-sample of ETPDVC events (H1Runs 87314-87457 - see message from 26.09.94 at LL10). (CCvcs start = 4.273 MeV/FADCcount). There are a little better resolution digits at 8E-sample of events. Attempt to make fit of PhotonArm Energy spectrum was successful (with more or less good statistics). 03.10.1994 ===== dice2 ======== H1KFOM === PDREC-spectra for 8E Today it were produced 100th ntuple for S92=1 events from earlier mentioned 8E-sample with events from Runs 87695-88022: H1KFOM.YLOOKQ4.R87695 (27603 entries) FAST09 3010200E 00000 DASD At interactive LOOK-session it was produced 70th histo for this data set and written into the next LOOK-binary data set: H1KFOM.BLOOKQ2.R87695 15711 entries in 70h FAST12 3010200E 00000 DASD First attempt to fit 70th histo at BLOOKQ2-data set put negative sign of Global Energy Shift at Photon Arm (-1.0%) and enough good resolution digits (18-19%)only for (10-20)-35GeV regions. It were prepared 100th tuples with ET&PD&nVC and ET&PD&VC-events for procedure of defining Global Energy Shifts and CCvcs: H1KFOM.YLOOKQ2.R87695 55484 entries FAST04 3010200E 00000 DASD H1KFOM.YLOOKQ3.R87695 63701 entries FAST08 3010200E 00000 DASD 03.10.1994 ==================== H1KFOM === Global Shifts,CCvcs 8E It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 1.010 for PD Channels (exept VCs), 0.9985 for ET channels. Correction factor for CCvcs is 1.100. So CCvcs = 4.273*1.100 =4.700Mev FADCcount. These digits are valid for H1Lumi events from Run 87695 up to 88022 Runs 87695- 88022 (ET&PD&nVC-sample - near 56.0K events) xetcut&vcdepcut Step Mean Sigma 0 27.51 1.00 Runs 87695- 88022 (ET&PD&VC-sample - near 69.3K events) xetcut Step Mean Sigma 0 27.52 1.31 P.S. CCe19 was deceremented (a little) and became again less then 10. CCvcs(averaging) was incremented on 10% (!). For any case - this is the final values of CC at Photoproduction branch after 3rd step of calibration with 8E-data sample (H1 Runs 87695-88022): ==> ET Calibr.Coefficients Final Status e00= 4.125 4.233 4.108 3.156 3.921 3.037 3.408 4.377 3.339 4.044 1.691 5.190 3.697 3.881 7.152 2.501 4.236 4.486 4.001 9.778 4.265 6.846 4.743 5.473 4.595 4.120 4.683 4.109 4.555 5.085 4.546 4.041 4.475 4.862 3.061 4.457 4.632 3.611 3.727 4.404 4.289 4.021 e42= 4.054 3.970 4.339 1.981 3.722 4.141 4.018 ==> PD & VC Calibr.Coefficients Final Status p00= 2.060 1.445 1.351 2.361 2.538 1.256 2.715 2.968 2.250 1.613 2.314 3.979 2.997 3.000 2.084 2.371 2.131 2.842 3.083 2.435 p20= 1.354 1.481 2.300 3.169 2.549 vcs= 4.700 During start of Lumi RUN#613 CCp11 was decremented again (on 32%) and from H1Run 88079 it is needed to collect new (9A) data sample for calibration. 3/10/94 ================= W.Hildesheim === Lumi RUN# 623 Start lumi run623 date: 3/10/94 Collision time: 6:15:37 - 16:46:22 Currents (mkA): Ie= 32600.00, Ip= 49000.00 Peak luminosity: 3158.346 mb-1 s-1 Peak spec.lumi : 407.023702 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 63423.758079 mkb-1 H1 Run total lumi: 50814.9387 mkb-1 H1 data taken lumi: 40463.46 mkb-1 H1 Runs: 88298 - 88348 HERA - physics: 58774.559891 mkb-1 H1Run - physics: 46626.503541 mkb-1 H1data - physics: 40187.598568 mkb-1 H1 Runs: 88310 - 88348 Tot curr/rate factor: 1.19% C/R F H1Run gated: 1.18% Rand.C.F: 1.07% RCF Run gated: 1.1% Relative ET trigg accept.: 0.4903 PS(LNS): for R88315 (~76 Kevents): L4 histos OK; L5 OK, too. 4/10/94 ====================== G. Lobo === Lumi RUN# 624 Start lumi run624 date: 4/10/94 Collision time: 5:26:53 - 7:11:06 Currents (mkA): Ie= 27300.00, Ip= 41200.00 Peak luminosity: 2601.933 mb-1 s-1 Peak spec.lumi : 437.277616 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 14764.271402 mkb-1 H1 Run total lumi: 13012.221957 mkb-1 H1 data taken lumi: 11580.490801 mkb-1 H1 Runs: 88356 - 88366 HERA - physics: 13884.606361 mkb-1 H1Run - physics: 11574.508266 mkb-1 H1data - physics: 10257.061915 mkb-1 H1 Runs: 88358 - 88366 Tot curr/rate factor: 9.47% C/R F H1Run gated: 9.98% Rand.C.F: 1.54% RCF Run gated: 1.5% Relative ET trigg accept.: 0.4991 PS(LNS): for R88365 (~33 Kevents): L4 histos ~OK, see; L5 absent. PS(LNS): WARNING: E_Etag: a BIG BUMP appiered at low E, ~30% in it. 5/10/94 ================== a.v.semenov === Lumi RUN# 625 Start lumi run625 date: 4/10/94 Collision time: 19:45:22 - 6:13:34 Currents (mkA): Ie= 29100.00, Ip= 49400.00 Peak luminosity: 3182.353 mb-1 s-1 Peak spec.lumi : 438.884585 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 64475.566511 mkb-1 H1 Run total lumi: 51213.623602 mkb-1 H1 data taken lumi: 34925.546545 mkb-1 H1 Runs: 88434 - 88474 HERA - physics: 62547.354975 mkb-1 H1Run - physics: 48900.740705 mkb-1 H1data - physics: 32931.133415 mkb-1 H1 Runs: 88436 - 88474 Tot curr/rate factor: 0.45% C/R F H1Run gated: 0.52% Rand.C.F: 2.16% RCF Run gated: 2.52% Relative ET trigg accept.: 0.4891 PS(LNS): for R88471 (~59 Kevents): L4 histos OK; L5 OK, too. PS(LNS): E_Etag: a BIG BUMP at low E (see #624) has disappiered. 05.10.1994 ===== dice2 ======== H1KFOM === New CCp11 "jumps"......... Today it was produced LOOK-binary data set with vectors which keep behaivours with time of Calibration Coefficients at Luminosity sub- branch for 'hot' channels: 10022-10028 for central layer at ET (e21- e27) and 20011-20015 - for central layer at PD. These vectors were built for ET&PD&nVC data sample from H1 Run 88079 up to 88473 (37396 events). It was made for defining of new data samples (9A, etc.). This data set is kept at DESY IBM with the next name: H1KFOM.LOOKB.R88079 FAST04 3010200E 00000 DASD From looking for vector 20012 it is clear that early mentioned data sample (from Lumi RUN# 613 up to Lumi RUN# 625) is divided on 4 sub- samples due to 'jumps' at CCp11-behaivor with time at Luminosity subbranch: 1) 0-17600 events - subsample 9A with more or less stable CCp11 2) 17600-20700 events - data collected during second part of Lumi RUN# 621 and all Lumi RUN# 622 (from H1 Run 88232 up to H1 Run 88258 - from 01/10/94 21:35 up to 02/10/94 07:57). This data subsample was collected with CCp11 on 47% more then at 9A- subsample; 3) 20700-29700 events - subsample 9A- type (CCp11 had back 'jump' on -47% (to 'old' value)) - Lumi RUN# 623; 4) 29700-37396 events - 'jump' at CCp11 on 57% into high region with stable plato value during Lumi RUNs # 624,625 Good base for new sample of calibration data(9B 05.10.1994 ===== dice2 ======== H1KFOM === G-Runs Absence at LUMIMON Today I found (ocasionally) that some H1 Good Runs have not Lumi Monitrig events (I am not sure that absence of all Lumi Monitrig is fixed - only ET&PD&nVC-events are absent for some from H1 Good Runs). As example: There are no ET&PD&nVC events for almost 50% of Lumi RUN# 613th and near 1/7 of Lumi RUN# 614th (%-tage from time interval). H1Runs 88084-88089 (from 29/09/94 20:04 up to 29/09/94 21:03) and H1Runs 88092-88096 (from 29/09/94 22:50:36 up to 30/09/94 01:09) have not any ET&PD&nVC events (3 hours 08 min and 26 sec). H1Run 88111 have not any ET&PD&nVC events too (from 30/09/94 07:29:18 up to 30/09/94 08:27:10) - 57 min.52 sec. During high mentioned Good H1 Runs it were collected 19.2 nb-1. I am not sure that this event is single at H1 Data Taking'94 (before today I never checked this situation specially). May be this is problem connected with LUMIMON-data set creation only? May be H1RAWD- data sets have this type of events? Who knows anything about? P.S. I checked contents of HERA04.H1RAWD.C9403998 data set with presence of ET&PD&nVC events and found nothing - from 9042 events of H1 Run 88111 it was not found nothing with ET&PD&nVC trigger. So - the reason of absence of ET&PD&nVC events is not at LUMIMON-data set making.... May be bad timing was reason of ET&PD&nVC-events or something else? May be some 'play' with H1Lumi subtriggers (may somebody swithched off s92 and s94)? Or somebody played with H1Lumi trigger element setting? P.S.1 I checked Subtrigger setting at high mentioned H1 Runs - no any difference at Trigger Setting for H1 Runs 88082 (which includes ET&PD&nVC events) and high mentioned H1 Runs. May be Prescale Factors were installed for H1Lumi Monitrig on high value? 05.10.1994 ==================== H01GOG === LUMIMON data processing Here is a continuation of a summary table for e+p LUMIMON files, processed so far. ---------------------------------------------------------------------- File H1 runs Events Actual triggers (xx) s86 s91 s92 s93 s94 s95 ---------------------------------------------------------------------- 106 88092-88203 133298 13992 4382 5923 6379 6706 7258 107 88203-88232 129901 11334 4547 6287 6334 7376 7566 108 88232-88320 129855 11285 3802 4795 6004 5648 6527 109 88320-88473 128773 10219 5470 6517 8723 8063 9301 ---------------------------------------------------------------------- It is easy to check from LUMIMON files 105 and 106 all doubtful run periods mentioned by Sasha Fomenko in his previous message. It was done by a slightly modified H01GOG.LUMMON.MACRO, (adding the selection of these runs) as it is shown in a fragment of this macro below: * *---- trigger statistics --------------------------------------------- * do '/rr=((run>88083 & run<88090) | (run>88091 & run<88097)|run==88111)' MESS ' fig2: trigger statistics' do 'hs(10,0,60,0,30)=nt(1)(ee)@(s86 & rr)' do 'hs(11,0,80,0,40)=nt(1)(ep)@(s91 & rr)' do 'hs(12,0,120,10,40)=nt(1)(ee+ep)@(s92 & rr)' do 'hs(13,0,100,-5,15)=nt(1)(ev)@(s93 & rr)' do 'hs(14,0,120,10,40)=nt(1)(ee+ep)@(s94 & rr)' do 'hs(15,0,120,10,40)=nt(1)(ee+ep)@(s95 & rr)' fig2 = as f 10-15 logy 2 4 histos 10 6 The result shows, that ALL standard LUMI triggers are present in those runs. In particular the following statistics was obtained: H1 runs s92 s94 s95 events prescale events prescale events prescale 88084-88089,88092 407 280001 457 100001 477 400001 88092-88096,88111 1195 90001 1344 30001 1433 100001 From the standard LUMIMON summary table, which is regularly presented in LLO, there was so far no evidence seen on any specific problem with LUMI trigger statistics; just normally expected fluctuations. Perhaps, we have to compare the selection criteria used in our jobs? P.S. I used for selection standard TEL1-bank contents. ET&PD&nVC events absence means that there are no combinations ET=1 PD=1 VC=0 at high mentioned Good H1 Runs. I changed nothing at selection procedure and it means that something is non-standard at early mentioned H1 Runs (may be timing at H1LumiTrigger was shifted, may be some problems at H1Central Trigger). As seems at Your mentioned macro it is possible to add some lines and to be sure that s94=1 and ET&PD&nVC .ne. 1 I will be very surprized if it is not so. (a.f.) P.S. I checked the situation in LUMIMON file 105 for the runs 88084-88089. It is perfectly OK: in 100% of the cases (427 evts) the decision of CTL (s94) agrees with the content of TEL1 bank (ET=1&PD=1&VC=0). It is also true for other subtriggers. Fomenko, can you show me your selection code? How do you unpack TEL1? May be something has changed NOT in your code, but in tools (H1UTIL) you might be using? (S.Lev.) P.S. As seems the reason of 'absence' of ET&PD&nVC events at early mentioned H1 Runs is at selection program which was used by me at dice2-environment (particularly at TEL1-bank decoding). (a.f.) 05.10.1994 ==================== H01LNS === prescalers R88000-88475 == Some recent data on the prescalers, taken from MDB (!), by N_of_RUN, can be seen by starring: LIST 'H01LNS.PRESC.R88000.R88475' Unfortunately (will be improoved): 1. ALL the NRUNs are included to the Table, irrelevant of "LUMI"/NOT, 2. Two columnes for Lumi-value, naturally, sometimes empty, 3. LUMI_RUN # is == 999 in all this table, 4. The word "new" should be ignored. PS: this LLO was written soon after A.Fomenko's, then it dissapiered. PPS: This is well known effect: that time, A.Fomenko added more information to his message, and thus erased this one. Please, communicate with each other to not interfere destructi- vely when updating LLO. (S.Lev.) 06.10.1994 ===== dice2 ======== H1KFOM === Relation Coeff.Set 9A Today it was made attempt to produce Rel.Coeff.Set for 9A (high p11) data sample (from H1 Run 88079 up to Run 88347).It were selected 24365 ET&PD&nVC events from this H1 Run range from data sets (only G- and M- labeled H1 Runs at H1EP and skip data from H1Runs 88232-88258): H1KFOM.ETPDNVC.M103107.C00 K35976 78048081 00001 ACS-E-C H1KFOM.ETPDNVC.M108109.C00 K22266 78048081 00001 ACS-E-C After all high mentioned 'cleaning' of 9A(high p11)data samples it were collected: 24365 events with ET&PD&nVC trigger 29687 events with ET&PD&VC trigger 17745 events with S92-trigger (PD&nVC-events). It were got 24365 ET&PD&nVC from these Runs and it were used for calibration 8666 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 1.030 1.268 0.512 1.022 0.797 1.177 0.944 0.509 0.889 0.971 0.946 1.013 0.932 1.008 1.358 0.809 0.872 0.855 0.884 0.909 0.846 1.002 1.000 1.001 0.993 1.008 0.941 0.933 1.125 1.062 1.018 0.911 0.974 1.005 1.066 0.994 0.760 1.305 1.005 0.000 0.980 0.000 0.940 0.000 0.892 0.000 0.000 0.000 0.000 ==> Relation Coeff.Set for PD 1.848 0.938 1.016 1.489 0.000 1.039 1.051 1.063 1.051 1.026 1.013 1.055 1.017 1.019 1.076 1.024 1.002 1.022 1.036 0.968 1.445 0.948 1.132 1.011 0.000 ==> Sig. at Relation Coeff.Set for ET 0.000 0.002 0.001 0.001 0.002 0.001 0.001 0.002 0.003 0.004 0.004 0.005 0.001 0.005 0.006 0.011 0.012 0.005 0.008 0.008 0.008 0.014 0.014 0.016 0.011 0.022 0.022 0.011 0.005 0.005 0.004 0.004 0.003 0.009 0.005 0.000 0.003 0.001 0.002 0.000 0.000 0.000 0.000 0.000 0.004 0.000 0.000 0.000 0.000 ==> Sig. at Relation Coeff.Set for PD 0.006 0.003 0.003 0.006 0.000 0.009 0.011 0.012 0.009 0.001 0.013 0.016 0.016 0.013 0.006 0.013 0.019 0.017 0.017 0.001 0.001 0.005 0.002 0.000 0.000 ==> Ent. at Relation Coeff.Set for ET 2 11 4 3 11 7 3 3 17 29 32 36 17 21 725 91 128 147 112 262 84 2288 3583 2875 2327 1995 1678 759 1035 1264 899 618 580 443 283 8 3 7 5 0 1 0 1 0 2 0 0 0 0 ==> Ent. at Relation Coeff.Set for PD 11 8 9 7 0 309 1497 1548 268 13 2750 6897 5102 1144 56 747 1922 877 157 9 7 10 9 1 0 As You can see all sigma values for 'hot' H1Lumi cahnnels RC histos have more or less reasonable values. Runs 88079-88347 (ET&PD&nVC-sample - near 24.4K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.32 1.05 27.37 1.02 27.41 1.03 Runs 88079- 88347 (ET&PD&VC-sample - near 29.7K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.34 1.35 27.29 1.31 As start values of Calibration Coefficients for Photoproduction Branch were got ones after 3rd step of calibration with ET&PD&nVC events from 8E-sample (H1 Runs 87695-88022 - near 56.0 K events). CCvcs value was got from last VCs calibration at 8E-sample of ETPDVC events (H1Runs 87695-88022 - see message from 03.10.94 at LL10). (CCvcs start = 4.700 MeV/FADCcount). Attempt to make fit of PhotonArm Energy spectrum was unsuccessful (with not very good statistics). 06.10.1994 ===== dice2 ======== H1KFOM === PDREC-spectra for 9A Today it were produced 100th ntuple for S92=1 events from earlier mentioned 9A-sample with events from Runs 88079-88347: H1KFOM.YLOOKQ4.R88079 (14767 entries) FAST09 3010200E 00000 DASD At interactive LOOK-session it was produced 70th histo for this data set and written into the next LOOK-binary data set: H1KFOM.BLOOKQ2.R88079 8122 entries in 70h FAST12 3010200E 00000 DASD First attempt to fit 70th histo at BLOOKQ2-data set put negative sign of Global Energy Shift at Photon Arm (-5.5%) and enough bad resolution digits (28-32%) for (10-20)-35GeV regions. It were prepared 100th tuples with ET&PD&nVC and ET&PD&VC-events for procedure of defining Global Energy Shifts and CCvcs: H1KFOM.YLOOKQ2.R88079 24114 entries FAST04 3010200E 00000 DASD H1KFOM.YLOOKQ3.R88079 27312 entries FAST08 3010200E 00000 DASD 06.10.1994 ==================== H1KFOM === Global Shifts,CCvcs 9A It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 1.055 for PD Channels (exept VCs), 0.9600 for ET channels. Correction factor for CCvcs is 1.110. So CCvcs = 4.700*1.110 =5.217Mev FADCcount. These digits are valid for H1Lumi events from Run 88079 up to 88347 Runs 88079- 88347 (ET&PD&nVC-sample - near 24.4K events) xetcut&vcdepcut Step Mean Sigma 0 27.52 1.05 Runs 88079- 88347 (ET&PD&VC-sample - near 29.7K events) xetcut Step Mean Sigma 0 27.52 1.37 P.S. CCp11 was deceremented significantly (factor 1.7). CCvcs(averaging) was incremented on 11% again(!). For any case - this is the final values of CC at Photoproduction branch after 3rd step of calibration with 9A-data sample (H1 Runs 88079-88347): ==> ET Calibr.Coefficients Final Status e00= 4.125 4.235 4.111 3.158 3.901 3.031 3.375 4.378 3.369 3.860 1.661 5.255 3.651 3.755 7.392 2.185 3.853 4.255 3.759 9.828 3.850 6.962 4.771 5.495 4.650 4.169 4.615 4.005 4.722 5.360 4.672 3.794 4.739 4.680 3.185 4.478 4.632 3.617 3.719 4.404 4.292 4.021 e42= 4.054 3.970 4.339 1.981 3.722 4.141 4.018 ==> PD & VC Calibr.Coefficients Final Status p00= 2.067 1.448 1.338 2.361 2.538 1.318 2.723 3.047 2.285 1.631 2.474 2.373 3.098 3.053 2.268 2.284 2.080 2.860 3.253 2.443 p20= 1.357 1.587 2.307 3.169 2.549 vcs= 5.217 During start of Lumi RUN#624 CCp11 was incremented again (on 57%) and from H1Run 88357 it is needed to collect new (9B) data sample for calibration. 6/10/94 ====================== === Lumi RUN# 626 Start lumi run626 date: 6/10/94 Collision time: 20:43:42 - 21:47:08 Currents (mkA): Ie= 28000.00, Ip= 46700.00 Peak luminosity: 2928.625 mb-1 s-1 Peak spec.lumi : 444.106869 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 9712.496298 mkb-1 H1 Run total lumi: 9250.0958 mkb-1 H1 data taken lumi: 8520.1805 mkb-1 H1 Runs: 88666 - 88671 HERA - physics: 8353.771003 mkb-1 H1Run - physics: 7518.252748 mkb-1 H1data - physics: 6831.489681 mkb-1 H1 Runs: 88668 - 88671 Tot curr/rate factor: 0.44% C/R F H1Run gated: 0.45% Rand.C.F: 1.97% RCF Run gated: 1.96% Relative ET trigg accept.: 0.4251 PS(LNS): for R88669 (~21 Kev,Phase2): L4 histos ~OK, see; L5 ~OK, too. PS(LNS): WARNING: E_Etag: a SHOULDER-BUMP appiered at ~ 22-25 GeV. PS(LNS): WARNING: "Rel.... accept." started down a little ~0.5->~0.4. 07.10.1994 ===== dice2 ======== H1KFOM === Selection Upgrade... After involving more detail decoding of TEL1-bank contents the next result was obtained: 'New' TEL1-Decoding 'Old' TEL1-Decoding H1 Runs ET&PD&nVC events ET&PD&nVC events 88079 157 157 88080 4 4 88081 86 86 88082 78 78 88083 227 216 <--- 88084 329 0 <--- 88086 56 0 <--- 88089 240 0 <--- 88090 857 2 <--- 88092 185 0 <--- 88093 197 0 <--- 88094 303 0 <--- 88095 20 0 <--- 88096 857 0 <--- 88098 658 658 88100 382 382 88101 233 233 88102 15 15 88103 712 712 88104 194 194 88105 15 15 88110 827 52 <--- 88111 467 0 <--- 88112 145 0 <--- 88114 28 0 <--- 88115 378 0 <--- 88125 1 1 88132 3 3 88134 5 5 As seems at early mentioned H1Runs (88084-88096,88111) and at parts of H1 Runs 88110,88083 it was used non-standard quantity of time slices at TEL1-bank (ordinary from -5 - at these H1 Runs - another). As seems at most cases 'old' and 'new' TEL1-decoding put the same results of selection. P.S. To make things clear: in all jobs, prosessing LUMIMON files by H01GOG and F11LEV, the unpacking of TEL1 bank was done in a most general way, according to the official description of this bank in DDL. It was never assumed, that zero time slice must be at some fixed position in the bank. (S.Lev) 08.10.1994 ==================== H01LNS === General comments on PD === Some General comments on the LUMI PD -arm configuration. (Mainly, for the possible Meeting of the DESY LPI Group, particul., in connection with S.Levonian's LLO 03.10.94) 1. Some time ago, I had come to conclussion that our PD-config should have had "not a good Linearity" upon the Energies of photons. - I have not found any info on Linearity in LUMI LLO and preprints, I have had talks to A.M.F., P.S.B, A.S.B. of LPI -none of this info. (May be, something from Protvino LPI calibrations was not reported) - I have not found any info on Linearity in Reports from GAMS, and in a few Surveys on the Cherenkov Total Absorption Spectrometers. - So, I had belived that "Non-Linearity in LUMI-PD-arm" can be real. - By that time I had had some confirmations from my computer jobs. 2. Nevertheless I had taken a little speculative thesis, rather excuse: - A possible PD-arm Non-Linearity should not play any significant role for the LUMI-value measurements - the main function of LUMI Setup. - This thesis had been confirmed at some discussions with P.S.Baranov. - The other physical applications of PD-arm Energies were not touched. - So, I had paused my computer exercices on the Topic of Linearity. - But, bellow I returned to this problem because of S.Levonian's LLO. 3. Shortly speaking, My GENERAL point of view is as following: 1) A Cherenkov Total Absorption Spectrometer as itself is E-linear, 2) Adding of any "passive" absorber (before it) makes it NON-LINEAR (The "passive" means no Energy measurements in the absorber), 3) This is a fundumental specific disadvantage of Cherenkov T.A.S., comparing to any Scintilator T.A.S. (*** My own statement ***) 4) But: Energy measurement in absorber can make "our Config" LINEAR. 4. Some Other impacts of the "passive" absorber (special problems): 1) It spoiles the upper end of the bremsstrahlung spectrum, 2) It makes worse the overall Energy Resolution, The following are some important Detales: 3) Non-linearity is connected to the Energies before the absorber, 4) The effects of absorber depend mostly on it's thickness in X0, 5) Effect of absorber-detector distance is not important, at all, for the detector of a large apperture, comparing to "the beam". 5. Some General Conclussions: 1) The most important H1/ZEUS difference is difference of Cherenkov and Scintillating detectors, it is neither the presence of VC, nor the short distance between absorber and detector of ZEUS. 2) Remooving of VC, and closing detector to absorber are of no use, 3) Any improoving of VC will not improove the above defectes. 6. Some Speculative Proposals: 1) Because Remooving of the rather thick absorber is not possible, the only way to improove the config is making an Active Absorber that has to work at the background of high synchrotron radiation, 2) In this way, much better would be make some "Hodoscopic Absorber" to realize some independant and better measurements of tracks (It is my old proposal and something like this is done at ZEUS), 3) For realization of such an Active Hodoscopic Absorber, something from the H1 detectors should be used, probably, Spacal variantes. 4) But may be possible to make use of Cherenkov modules of ~ 2X0, this way does not contradict to the above general statements. These proposals are speculative, because in any way of realization the Active Absorber has to measure energies at the extreemly high flux of synchrotron radiation, and I don't think that this problem can be solved at LPI. But may be somebody would propose a solution? 7. Some closing comments: Comparing to S.Levonian's LLO 03.10.94, I reported here my point of view only at the selected topics - the LUMI PD-arm Linearity, the possible remooving of VC, and the relevant PD-arm configuration. I am not sure I am right in General 3.3 disadvantage of Cherenkov's. I believe that the "problem of calibration" has yet to be discussed. As for the Proposals, unfortunately, I don't believe in any success. PS: Sorry for such a big piece (== 1 page) of nothing numerical in LLO. Lollii Shtarkov, Moscow, LPI, Pitomnik, 08.10.1994. 7/10/94 ==================== G.D.Patel === Lumi RUN# 627 Start lumi run627 date: 7/10/94 Collision time: 7:12:13 - 16:19:30 Currents (mkA): Ie= 29907.00, Ip= 44700.00 Peak luminosity: 3146.644 mb-1 s-1 Peak spec.lumi : 456.098423 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 63506.45423 mkb-1 H1 Run total lumi: 55438.8025 mkb-1 H1 data taken lumi: 46223.7396 mkb-1 H1 Runs: 88689 - 88708 HERA - physics: 61679.060265 mkb-1 H1Run - physics: 51769.250786 mkb-1 H1data - physics: 42701.017722 mkb-1 H1 Runs: 88691 - 88708 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 1.18% RCF Run gated: 1.2% Relative ET trigg accept.: 0.4807 8/10/94 ==================== Shekelyan === Lumi RUN# 628 Start lumi run628 date: 7/10/94 Collision time: 19:19:05 - 4:45:58 Currents (mkA): Ie= 28809.00, Ip= 43100.00 Peak luminosity: 50.752 mb-1 s-1 Peak spec.lumi : 7.621029 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 50708.767237 mkb-1 H1 Run total lumi: 41059.2097 mkb-1 H1 data taken lumi: 36224.0483 mkb-1 H1 Runs: 88719 - 88747 HERA - physics: 50695.132957 mkb-1 H1Run - physics: 40338.126798 mkb-1 H1data - physics: 35568.882039 mkb-1 H1 Runs: 88720 - 88747 Tot curr/rate factor: 1.19% C/R F H1Run gated: 1.2% Rand.C.F: 0.77% RCF Run gated: 0.73% Relative ET trigg accept.: 0.4962 8/10/94 ==================== G.D.Patel === Lumi RUN# 629 Start lumi run629 date: 8/10/94 Collision time: 12:26:07 - 20:18:38 Currents (mkA): Ie= 30900.00, Ip= 48700.00 Peak luminosity: 3445.87 mb-1 s-1 Peak spec.lumi : 461.479783 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 61763.3785 mkb-1 H1 Run total lumi: 57331.1655 mkb-1 H1 data taken lumi: 50817.3391 mkb-1 H1 Runs: 88785 - 88806 HERA - physics: 59775.699034 mkb-1 H1Run - physics: 54499.925057 mkb-1 H1data - physics: 48049.644826 mkb-1 H1 Runs: 88786 - 88806 Tot curr/rate factor: 0.81% C/R F H1Run gated: 0.82% Rand.C.F: 0.9% RCF Run gated: 0.91% Relative ET trigg accept.: 0.4820 9/10/94 ==================== a.semenov === Lumi RUN# 630 Start lumi run630 date: 8/10/94 Collision time: 21:48:31 - 5:11:34 Currents (mkA): Ie= 26663.00, Ip= 45800.00 Peak luminosity: 2442.546 mb-1 s-1 Peak spec.lumi : 395.622561 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 40750.62254 mkb-1 HERA total lumi: 40750.62254 mkb-1 H1 Run total lumi: 39130.0072 mkb-1 H1 data taken lumi: 36623.2519 mkb-1 H1 Runs: 88807 - 88816 HERA - physics: 38382.02594 mkb-1 HERA - physics: 38382.02594 mkb-1 H1Run - physics: 34531.1834 mkb-1 H1data - physics: 30148.872 mkb-1 H1 Runs: 88809 - 88816 Tot curr/rate factor: 1.04% C/R F H1Run gated: 1.06% Rand.C.F: 0.76% RCF Run gated: 0.76% Relative ET trigg accept.: 0.4877 10/10/94 ====================== Royon === Lumi RUN# 631 Start lumi run631 date: 9/10/94 Collision time: 13:45:05 - 1:50:07 Currents (mkA): Ie= 28664.00, Ip= 52100.00 Peak luminosity: 3259.102 mb-1 s-1 Peak spec.lumi : 432.163523 mb-1 s-1 mA-2 Number of collided b.: 154 Number of e-filled b.: 173 Number of p-filled b.: 170 Number of e-pilot b.: 19 Number of p-pilot b.: 16 HERA total lumi: 85671.756326 mkb-1 H1 Run total lumi: 81910.2 mkb-1 H1 data taken lumi: 74776.944 mkb-1 H1 Runs: 88836 - 88864 HERA - physics: 83431.043163 mkb-1 H1Run - physics: 78508.665217 mkb-1 H1data - physics: 71496.266522 mkb-1 H1 Runs: 88837 - 88864 Tot curr/rate factor: 1.35% C/R F H1Run gated: 1.37% Rand.C.F: 0.81% RCF Run gated: 0.82% Relative ET trigg accept.: 0.4900 10.10.1994 ==================== H1KFOM === Corrupted LUMIMON-data set Today I found that data set HERA03.H01.LUMIMON.C9400110 is corrupted as seems. After succesful stagin into dice2-environment: :::::::::::::: LUMIMON110.2 :::::::::::::: Oct 10 07:04:57 tpread[22843]: selected tape server is ibm. Oct 10 07:05:02 tpread[22843]: job submission successful Oct 10 07:10:11 tpread[22843]: transfer starts Oct 10 07:12:44 tpr: 176604120 bytes transferred Oct 10 07:12:44 tpr: transfertime was 126.000000 sec, transferrate was 1.402 MB/s Oct 10 07:12:23 tpread[22843]: command successful (only length of this data set was non-standard (ordinary 200 Mbyte)). all attempts to make some reading from this data set were finished with the next messages: :::::::::::::: S92Selection_109_114.o74515 :::::::::::::: inwrite: off end of record apparent state: unit 6 named last format: (Unexpected end-of-file on input ",a,") lately writing (null) formatted internal IO *** Execution Terminated (110) *** Option for skipping of corrupted events was installed at FPACK-options but could not help at this situation: OPEN BOSINPUT UNIT=1 SHIFT & FILE="[h1stage.h1]HERA03.H01.LUMIMON.C9400109, & [h1stage.h1]HERA03.H01.LUMIMON.C9400110, & [h1stage.h1]HERA03.H01.LUMIMON.C9400111, & [h1stage.h1]HERA03.H01.LUMIMON.C9400112, & [h1stage.h1]HERA03.H01.LUMIMON.C9400113, & [h1stage.h1]HERA03.H01.LUMIMON.C9400114" read SKIPCOREV All jobs never achieved to the next data set (111). I sent mail to Ralf Gerhards with asking to help at this situation. 10.10.1994 ==================== F11LEV === LUMIMON 110 .............. The fact, that the file HERA03.H01.LUMIMON.C9400110 is corrupted, was found also by Nelly Gogitidze last Friday, when trying to process it by her standard LMONI2 job. The file is readable till H1 run 88704 inclusively (~80% of the data). Last runs 88705-88728 are not access- ible (permanent I/O error). Since Ralf is in vacations for two weeks, and Uwe will come from his holidays only today, and Zbyshek Szkutnik left H1 at all, it was not possible to recover this file earlier. Those who want to read through LUMIMON # 110 before the problem is fixed, can use the following selection, skipping corrupted records (file example is taken from the previous Fomenko's message): OPEN BOSINPUT UNIT=1 SHIFT & FILE="[h1stage.h1]HERA03.H01.LUMIMON.C9400109, & [h1stage.h1]HERA03.H01.LUMIMON.C9400110, & [h1stage.h1]HERA03.H01.LUMIMON.C9400111, & [h1stage.h1]HERA03.H01.LUMIMON.C9400112, & [h1stage.h1]HERA03.H01.LUMIMON.C9400113, & [h1stage.h1]HERA03.H01.LUMIMON.C9400114" read SKIPCOREV SELECT BOSINPUT NUMRA = :88704 88729: P.S. (23:00) LUMIMON.C9400110 is recreated on IBM and can be read without problems till the end. 10/10/94 ==================== a.semenov === Lumi RUN# 632 Start lumi run632 date: 10/10/94 Collision time: 4:56:13 - 12:32:11 Currents (mkA): Ie= 23566.00, Ip= 49901.00 Peak luminosity: 1838.09 mb-1 s-1 Peak spec.lumi : 129.442 mb-1 s-1 mA-2 Number of collided b.: 165 Number of e-filled b.: 196 Number of p-filled b.: 170 Number of e-pilot b.: 31 Number of p-pilot b.: 5 HERA total lumi: 40811.641869 mkb-1 H1 Run total lumi: 38339.695372 mkb-1 H1 data taken lumi: 34619.178396 mkb-1 H1 Runs: 88872 - 88885 HERA - physics: 40007.794869 mkb-1 H1Run - physics: 37212.211072 mkb-1 H1data - physics: 33712.008596 mkb-1 H1 Runs: 88874 - 88885 Tot curr/rate factor: 1.18% C/R F H1Run gated: 1.21% Rand.C.F: 0.73% RCF Run gated: 0.73% Relative ET trigg accept.: 0.5005 11.10.1994 ==================== H1KFOM === New RC Sets in H1DataBase As final action of all 03-06.10.94 calibration steps it was made update of LFRC and LESC banks at H1DataBase with S.Levonyan's tool. All Relation Coefficients values, CCvcs and Global Energy Shift constants were got from the next messages at LLO: 03.10.1994 ----- dice2 -------- H1KFOM --- Relation Coeff.Set 8E 03.10.1994 -------------------- H1KFOM --- Global Shifts,CCvcs 8E 06.10.1994 ----- dice2 -------- H1KFOM --- Relation Coeff.Set 9A 06.10.1994 -------------------- H1KFOM --- Global Shifts,CCvcs 9A Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LFRC (_501) 44 e-p data 410110701 87695 88078 77 941011 H1KFOM 45 e-p data 410110710 88079 0 77 941011 H1KFOM Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LESC (_582) 52 e-p data 410110701 87695 88078 3 941011 H1KFOM 53 e-p data 410110710 88079 0 3 941011 H1KFOM 11.10.1994 ===== dice2 ======== H1KFOM === Selected H1Lumi Monitrig.. Today it were selected calibration data samples from the next data sets which were produced with standard job prepared by S.Levonyan at dice1-environment: HERA03.H01.LUMIMON.C9400109 K10373 78048081 00001 ACS-E-C ...... HERA03.H01.LUMIMON.C9400114 K10447 78048081 00001 ACS-E-C It were selected events with (s92=1 only),with ET&PD&VC=1 and with ET&PD&nVC from these data sets (as ordinary): 1) S92=1 only 41190 events ( 65.8 MBytes) 2) ET&PD&VC 95110 events (157.8 MBytes) 3) ET&PD&nVC 73876 events (122.8 MBytes) Created data sets were saved at DESY IBM storage at the next data sets H1KFOM.ETPDNVC.M109114.C00 K44113 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M109114.C00 K45248 78048081 00001 ACS-E-C H1KFOM.S92.M109114.C00 K10538 78048081 00001 ACS-E-C These data include events from Lumi RUNs# 623-632 (H1 Runs 88320- 88877). P.S. Selection was made with 'new' TEL1-bank decoding and after recalculation of 110th LUMIMON data set. 11.10.1994 ===== dice2 ======== H1KFOM === New CCp11 "jumps"......... Today it was produced LOOK-binary data set with vectors which keep behaivours with time of Calibration Coefficients at Luminosity sub- branch for 'hot' channels: 10022-10028 for central layer at ET (e21- e27) and 20011-20015 - for central layer at PD. These vectors were built for ET&PD&nVC data sample from H1 Run 88320 up to 88877 (73876 events). It was made for defining of new data samples (9B, etc.). This data set is kept at DESY IBM with the next name: H1KFOM.LOOKB.R88320 FAST04 3010200E 00000 DASD From looking for vector 20012 it is clear that early mentioned data sample (from Lumi RUN# 623 up to Lumi RUN# 632) is divided on 3 sub- samples due to 'jumps' at CCp11-behaivour with time at Luminosity subbranch: 1) 0- 3658 events - end of 9A-subsample (see 05.10.94 message) 2) 3659-13000 events - 'jump' at CCp11 on 100% into high region with stable plato during Lumi RUNs # 624,625 There is 'jump' period from 3659 up to 4300 event at sample. During this period CCp11 was changed permanently into more high value region There is more or less stable CCp11 period between 4300 and 13000 events (9B-subsample). As seems this quantity of events is not enough for calibration. 3) 13000-73876 events - 'jump' at CCp11 on 10-12% into more high region and stable plato during very long period (from Lumi RUN#626 up to Lumi RUN# 632) - 9C-sub- sample - from H1 Run 88558 up to 88877. 11/10/94 ==================== a.semenov === Lumi RUN# 633 Start lumi run633 date: 10/10/94 Collision time: 21:21:41 - 10:07:44 Currents (mkA): Ie= 29292.00, Ip= 51800.00 Peak luminosity: 3986.449 mb-1 s-1 Peak spec.lumi : 488.179811 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 93670.18663 mkb-1 H1 Run total lumi: 90335.6963 mkb-1 H1 data taken lumi: 80938.9086 mkb-1 H1 Runs: 88910 - 88931 HERA - physics: 93471.04689 mkb-1 H1Run - physics: 89540.358805 mkb-1 H1data - physics: 80192.769463 mkb-1 H1 Runs: 88910 - 88931 Tot curr/rate factor: 0.87% C/R F H1Run gated: 0.87% Rand.C.F: 0.73% RCF Run gated: 0.72% Relative ET trigg accept.: 0.5043 11/10/94 ====================== Ch.C. === Lumi RUN# 634 Start lumi run634 date: 11/10/94 Collision time: 12:30:01 - 14:05:37 Currents (mkA): Ie= 26322.00, Ip= 49600.00 Peak luminosity: 2408.593 mb-1 s-1 Peak spec.lumi : 354.860353 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 12382.1416 mkb-1 H1 Run total lumi: 11909.589 mkb-1 H1 data taken lumi: 11214.66 mkb-1 H1 Runs: 88954 - 88959 HERA - physics: 9831.462614 mkb-1 H1Run - physics: 9171.068759 mkb-1 H1data - physics: 8703.129882 mkb-1 H1 Runs: 88957 - 88959 Tot curr/rate factor: 2.6% C/R F H1Run gated: 2.56% Rand.C.F: 1.29% RCF Run gated: 1.29% Relative ET trigg accept.: 0.4752 12/10/94 ================= Malinovsky-p === Lumi RUN# 635 Start lumi run635 date: 11/10/94 Collision time: 20:53:34 - 5:46:26 Currents (mkA): Ie= 29850.00, Ip= 47700.00 Peak luminosity: 2918.273 mb-1 s-1 Peak spec.lumi : 392.818184 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 70753.828572 mkb-1 H1 Run total lumi: 69053.9362 mkb-1 H1 data taken lumi: 62239.5171 mkb-1 H1 Runs: 88988 - 89001 HERA - physics: 68812.651568 mkb-1 H1Run - physics: 65897.0576 mkb-1 H1data - physics: 59121.6684 mkb-1 H1 Runs: 88989 - 89001 Tot curr/rate factor: 0.99% C/R F H1Run gated: 1% Rand.C.F: 0.84% RCF Run gated: 0.83% Relative ET trigg accept.: 0.4887 PS(LNS): for R88992 (~72 Kevents): L4 histos OK; L5 OK, too. 12.10.1994 ==================== H01GOG === LUMIMON data processing Here is a continuation of a summary table for e+p LUMIMON files, processed so far. ---------------------------------------------------------------------- File H1 runs Events Actual triggers (xx) s86 s91 s92 s93 s94 s95 ---------------------------------------------------------------------- 110 88473-88728 129220 10149 5585 6027 10448 7324 9599 111 88728-88794 128330 8690 6307 6789 11764 8794 11159 112 88794-88812 128012 7272 6596 7302 11629 9598 11744 113 88812-88843 128402 9486 5009 6022 7894 7686 8797 114 88843-88877 127858 6216 6528 7733 10477 10053 11307 115 88877-88917 128222 8464 5634 6737 8873 8818 10050 116 88917-88929 128340 6019 5353 6361 8436 8383 9500 117 88929-88992 128483 9063 5068 6217 7766 8088 8983 ---------------------------------------------------------------------- From the comlete statistics available up to now, one can see a clear degradation in the resolution of our KRS detectors (for clean ep -> epgamma events with E(veto)<0.2GeV): H1 run period Resolution (sigma(E)/E) e-p data-94 (76846 -> 82322) 3.0% --> 4.0% e+p data-94 (83146 -> 88929) 3.3% --> 4.0% 12.10.1994 ============ F11LEV, H01GOG === Offline Lumi-94 value Using all processed LUMIMON events from the files up to C9400114 inclusively (sample s91 = PD_low) we calculated offline values for 1994 e-p and e+p luminosities. A short summary is given in the table below. ---------------------------------------------------------------------- H1 run period E_gamma shift Online Lumi Offline Lumi Correction ---------------------------------------------------------------------- 76846-77991 +0.8 % 68.4 nb-1 68.9 nb-1 +0.7 % 76996-79840 +0.7 % 111.4 nb-1 119.1 nb-1 +6.9 % 79913-81023 +2.1 % 158.2 nb-1 174.5 nb-1 +10.0 % 81024-82005 +1.0 % 139.6 nb-1 155.7 nb-1 +11.5 % ---------------------------------------------------------------------- 477.6 nb-1 518.2 nb-1 +8.5 % ---------------------------------------------------------------------- 83146-84045 +2.7 % 173.4 nb-1 164.0 nb-1 -5.4 % 84046-86096 +2.3 % 544.8 nb-1 479.0 nb-1 -12.1 % 86097-86944 +2.3 % 431.8 nb-1 411.0 nb-1 -4.8 % 86945-87577 0.0 % 519.2 nb-1 473.0 nb-1 -8.9 % 87678-88215 -1.3 % 366.9 nb-1 337.0 nb-1 -8.1 % 88216-88864 -1.5 % 347.9 nb-1 307.0 nb-1 -11.7 % ---------------------------------------------------------------------- 2384. nb-1 2171. nb-1 -8.9 % ---------------------------------------------------------------------- Few remarks: 1) All events were re-reconstructed by LREC module with the latest CC from the database, which were prepared by A.Fomenko BEFORE 10-Oct-94. 2) Still remaining energy shift was determined for each sub-sample by a standard technique of fitting E-gamma distributions. All fits in the range from (10-12) to 32 GeV gave reasonably good results. Typical error on the E-shift values, given in the table, are 0.3-0.5% 3) To get an estimate for pure ep-bremsstrahlung, the events from the e-pilot bunches were subtracted after reweighting to the e-current ratio I_e(total)/I_e(pilot). In general, this also improves a bit E-fit quality. 4) Only G+M H1 runs were used. Prescale factors for s91 subtrigger were extracted from the database during standard #LMONI processing 5) Typical error in the so defined off-line luminosity is ~1.5-2% per subsample (shared roughly 50% by 50% between statistical error and the precision of the E-scale after final calibration+E_shift correction) Conclusion: There were observed significant errors in the online lumi values for both e-p and e+p data. Time behaviour of the correction factor (from the last column) is different for those two cases: it was slowly and steadily changing in the e-p running (pointing to the possible changes in optics in H1 IP), and more stable for the e+p data (pointing just to the wrong overall normalization used online?) The result should be for the time being considered as a preliminary, and everybody is invited to discuss the situation. If however no major problem in this analysis will be discovered, then we are back to the well known situation of the ~10% difference with ZEUS Lumi value. This by the way could still be (at least partially) a REAL difference, rather than an error in one of the measurements (H1 or ZEUS). A better stability in the specific luminosity and beam position at PD in ZEUS IP compared to H1 IP, observed in many occasions in 1994, may point to this possibility. 12/10/94 ===================== J.Ebert === Lumi RUN# 636 Start lumi run636 date: 12/10/94 Collision time: 13:57:55 - 14:59:04 Currents (mkA): Ie= 25764.00, Ip= 44500.00 Peak luminosity: 2533.321 mb-1 s-1 Peak spec.lumi : 431.232603 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 9236.898236 mkb-1 H1 Run total lumi: 9037.395097 mkb-1 H1 data taken lumi: 8376.570178 mkb-1 H1 Runs: 89020 - 89023 HERA - physics: 6735.986815 mkb-1 H1Run - physics: 5350.541767 mkb-1 H1data - physics: 4756.234387 mkb-1 H1 Runs: 89022 - 89023 Tot curr/rate factor: 1.65% C/R F H1Run gated: 1.65% Rand.C.F: 1.2% RCF Run gated: 1.2% Relative ET trigg accept.: 0.4972 13.10.1994 ===== dice2 ======== H1KFOM === Relation Coeff.Set 9C Today it was made attempt to produce Rel.Coeff.Set for 9C (low p11) data sample (from H1 Run 88558 up to Run 88877).It were selected 59661 ET&PD&nVC events from this H1 Run range from data sets (only G- and M- labeled H1 Runs at H1EP): H1KFOM.ETPDNVC.M109114.C00 K44113 78048081 00001 ACS-E-C After all high mentioned 'cleaning' of 9C(low p11)data samples it were collected: 59661 events with ET&PD&nVC trigger 76737 events with ET&PD&VC trigger 32786 events with S92-trigger (PD&nVC-events). It were got 59661 ET&PD&nVC from these Runs and it were used for calibration 20383 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 1.030 1.267 0.509 1.010 0.789 1.175 0.932 0.487 0.909 1.092 1.128 1.103 0.996 0.972 1.155 1.022 1.062 1.065 1.032 0.987 1.035 1.031 1.035 1.026 1.024 1.052 1.011 0.995 1.086 0.953 1.026 1.001 1.025 0.966 1.033 1.012 0.734 1.238 0.962 0.863 0.981 0.000 0.942 0.927 0.876 0.894 0.924 0.000 0.000 ==> Relation Coeff.Set for PD 1.851 0.964 1.042 1.533 0.937 0.988 0.999 0.987 1.034 1.032 0.941 1.007 0.997 0.975 0.991 0.982 0.955 0.956 0.959 0.980 1.420 0.956 1.126 1.001 0.921 ==> Sig. at Relation Coeff.Set for ET 0.001 0.012 0.009 0.019 0.011 0.007 0.004 0.008 0.016 0.012 0.026 0.018 0.025 0.033 0.056 0.034 0.018 0.022 0.020 0.026 0.019 0.015 0.015 0.016 0.014 0.019 0.028 0.010 0.036 0.021 0.020 0.020 0.015 0.018 0.015 0.002 0.000 0.025 0.014 0.000 0.001 0.000 0.000 0.006 0.004 0.001 0.000 0.000 0.000 ==> Sig. at Relation Coeff.Set for PD 0.008 0.015 0.022 0.006 0.000 0.015 0.011 0.030 0.015 0.005 0.016 0.019 0.016 0.019 0.018 0.014 0.017 0.019 0.018 0.006 0.011 0.021 0.016 0.005 0.000 ==> Ent. at Relation Coeff.Set for ET 3 21 7 16 13 17 14 8 46 93 88 111 62 58 1235 348 366 381 307 550 243 5409 8369 6619 5383 4574 3879 1878 2461 2140 2379 1813 1633 1113 797 19 1 6 4 3 4 0 5 2 2 3 1 0 0 ==> Ent. at Relation Coeff.Set for PD 59 16 20 20 1 899 4666 4026 620 25 6311 16324 12182 2242 65 1643 4284 1709 259 14 20 22 22 8 2 As You can see all sigma values for 'hot' H1Lumi cahnnels RC histos have more or less reasonable values. Runs 88558-88877 (ET&PD&nVC-sample - near 60.0K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.50 1.06 27.50 1.03 27.49 0.99 Runs 88558- 88877 (ET&PD&VC-sample - near 77.0K events) all events xetcut Step Mean Sigma Mean Sigma 3 28.05 1.48 28.16 1.44 As start values of Calibration Coefficients for Photoproduction Branch were got ones after 3rd step of calibration with ET&PD&nVC events from 9A-sample (H1 Runs 88079-88347 - near 24.0 K events). CCvcs value was got from last VCs calibration at 9A-sample of ETPDVC events (H1Runs 88079-88347 - see message from 06.10.94 at LL10). (CCvcs start = 5.217 MeV/FADCcount). Attempt to make fit of PhotonArm Energy spectrum was more or less succesful (with enough good statistics). 13.10.1994 ===== dice2 ======== H1KFOM === PDREC-spectra for 9C Today it were produced 100th ntuple for S92=1 events from earlier mentioned 9C-sample with events from Runs 88558-88877: H1KFOM.YLOOKQ4.R88558 (27884 entries) FAST09 3010200E 00000 DASD At interactive LOOK-session it was produced 70th histo for this data set and written into the next LOOK-binary data set: H1KFOM.BLOOKQ2.R88558 15337 entries in 70h FAST12 3010200E 00000 DASD First attempt to fit 70th histo at BLOOKQ2-data set put negative sign of Global Energy Shift at Photon Arm (-6.4%) and enough good resolution digits (19%) for (14-20)-35GeV regions. It were prepared 100th tuples with ET&PD&nVC and ET&PD&VC-events for procedure of defining Global Energy Shifts and CCvcs: H1KFOM.YLOOKQ2.R88558 58905 entries FAST04 3010200E 00000 DASD H1KFOM.YLOOKQ3.R88558 69018 entries FAST08 3010200E 00000 DASD 13.10.1994 ==================== H1KFOM === Global Shifts,CCvcs 9C It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 1.064 for PD Channels (exept VCs), 0.9549 for ET channels. Correction factor for CCvcs is 0.873. So CCvcs = 5.217*0.873 =4.554Mev FADCcount. These digits are valid for H1Lumi events from Run 88558 up to 88877 Runs 88558- 88877 (ET&PD&nVC-sample - near 60.0K events) xetcut&vcdepcut Step Mean Sigma 0 27.52 1.03 Runs 88558- 88877 (ET&PD&VC-sample - near 76.7K events) xetcut Step Mean Sigma 0 27.52 1.33 P.S. CCp11 was incremented significantly (factor more then 2). CCe19 became again more then 10. CCvcs(averaging) was decremented on 12.5% (vice versa with previous 2 calibration - 8E and 9A). For any case - this is the final values of CC at Photoproduction branch after 3rd step of calibration with 9C-data sample (H1 Runs 88558-88877): ==> ET Calibr.Coefficients Final Status e00= 4.139 4.362 4.124 3.271 3.909 3.067 3.430 4.397 3.633 4.600 2.029 5.807 4.061 3.844 6.655 2.445 4.629 5.440 4.484 10.648 4.807 6.990 4.995 5.812 4.734 4.393 4.917 4.326 4.749 4.817 4.778 4.097 5.064 4.662 3.277 4.494 4.638 3.633 3.747 4.408 4.307 4.021 e42= 4.066 3.970 4.342 1.981 3.719 4.141 4.018 ==> PD & VC Calibr.Coefficients Final Status p00= 2.073 1.476 1.330 2.367 2.538 1.233 2.562 2.895 2.169 1.632 2.227 4.886 2.986 2.900 2.021 2.134 1.969 2.632 2.941 2.439 p20= 1.336 1.567 2.226 3.168 2.549 vcs= 4.554 13.10.1994 ==================== H1KFOM === New RC Sets in H1DataBase As final action of all 13.10.94 calibration steps it was made update of LFRC and LESC banks at H1DataBase with S.Levonyan's tool. All Relation Coefficients values, CCvcs and Global Energy Shift constants were got from the next messages at LLO: 13.10.1994 ----- dice2 -------- H1KFOM --- Relation Coeff.Set 9C 13.10.1994 -------------------- H1KFOM --- Global Shifts,CCvcs 9C Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LFRC (_501) 46 e-p data 410130914 88356 0 77 941013 H1KFOM Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LESC (_582) 54 e-p data 410130914 88356 0 3 941013 H1KFOM P.S. It was decided to add 9B-sample to 9C-sample for 1st Run references. 13.10.1994 ===== dice2 ======== H1KFOM === Selected H1Lumi Monitrig.. Today it were selected calibration data samples from the next data sets which were produced with standard job prepared by S.Levonyan at dice1-environment: HERA03.H01.LUMIMON.C9400115 L11847 78048081 00006 ACS-E-C ...... HERA03.H01.LUMIMON.C9400118 K36142 78048081 00001 ACS-E-C It were selected events with (s92=1 only),with ET&PD&VC=1 and with ET&PD&nVC from these data sets (as ordinary): 1) S92=1 only 26807 events ( 42.9 MBytes) 2) ET&PD&VC 60317 events (100.1 MBytes) 3) ET&PD&nVC 49528 events ( 82.3 MBytes) Created data sets were saved at DESY IBM storage at the next data sets H1KFOM.ETPDNVC.M115118.C00 K44113 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M115118.C00 K45248 78048081 00001 ACS-E-C H1KFOM.S92.M115118.C00 K10538 78048081 00001 ACS-E-C These data include events from Lumi RUNs# 632-637 (H1 Runs 88877- 89075). 13/10/94 ====================== Reimer === Lumi RUN# 637 Start lumi run637 date: 13/10/94 Collision time: 2:30:14 - 12:56:53 Currents (mkA): Ie= 31100.00, Ip= 38500.00 Peak luminosity: 2928.702 mb-1 s-1 Peak spec.lumi : 463.090215 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 66292.338745 mkb-1 H1 Run total lumi: 64219.93 mkb-1 H1 data taken lumi: 58959.3068 mkb-1 H1 Runs: 89072 - 89090 HERA - physics: 64706.43677 mkb-1 H1Run - physics: 61702.6782 mkb-1 H1data - physics: 56493.7901 mkb-1 H1 Runs: 89073 - 89090 Tot curr/rate factor: 3.3% C/R F H1Run gated: 3.31% Rand.C.F: 0.92% RCF Run gated: 0.92% Relative ET trigg accept.: 0.4988 PS(LNS): for R89082 (~87 Kevents): L4 histos OK; L5 OK, too. PS(LNS): A little warning: PD (Edet-Etrig) a little changed: a few runs ago the second "peak" appiered at positive values. 13/10/94 ====================== J.Ebert === Lumi RUN# 638 Start lumi run638 date: 13/10/94 Collision time: 19:25:57 - 20:19:36 Currents (mkA): Ie= 25425.00, Ip= 47200.00 Peak luminosity: 2770.651 mb-1 s-1 Peak spec.lumi : 435.000181 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 7300.023659 mkb-1 H1 Run total lumi: 6613.1436 mkb-1 H1 data taken lumi: 6062.2386 mkb-1 H1 Runs: 89127 - 89133 HERA - physics: 5895.857132 mkb-1 H1Run - physics: 4466.005658 mkb-1 H1data - physics: 3956.618232 mkb-1 H1 Runs: 89128 - 89133 Tot curr/rate factor: 1.95% C/R F H1Run gated: 1.98% Rand.C.F: 1.08% RCF Run gated: 1.09% Relative ET trigg accept.: 0.4895 14/10/94 ====================== J.Ebert === Lumi RUN# 639 Start lumi run639 date: 13/10/94 Collision time: 22:22:17 - 9:41:19 Currents (mkA): Ie= 26552.00, Ip= 47100.00 Peak luminosity: 2732.42 mb-1 s-1 Peak spec.lumi : 416.129959 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 65948.027434 mkb-1 H1 Run total lumi: 63095.5343 mkb-1 H1 data taken lumi: 57767.6634 mkb-1 H1 Runs: 89133 - 89156 HERA - physics: 64147.372953 mkb-1 H1Run - physics: 60784.8909 mkb-1 H1data - physics: 55522.108 mkb-1 H1 Runs: 89133 - 89156 Tot curr/rate factor: 1.21% C/R F H1Run gated: 1.21% Rand.C.F: 0.64% RCF Run gated: 0.64% Relative ET trigg accept.: 0.5066 14/10/94 =================== Malinovski === Lumi RUN# 640 Start lumi run640 date: 14/10/94 Collision time: 12:17:50 - 19:00:07 Currents (mkA): Ie= 27275.00, Ip= 43200.00 Peak luminosity: 1861.763 mb-1 s-1 Peak spec.lumi : 315.321904 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 33025.709473 mkb-1 H1 Run total lumi: 30717.828 mkb-1 H1 data taken lumi: 27611.0829 mkb-1 H1 Runs: 89185 - 89200 HERA - physics: 30440.825568 mkb-1 H1Run - physics: 27871.593622 mkb-1 H1data - physics: 24797.524369 mkb-1 H1 Runs: 89187 - 89200 Tot curr/rate factor: 1.08% C/R F H1Run gated: 1.11% Rand.C.F: 0.78% RCF Run gated: 0.79% Relative ET trigg accept.: 0.4919 14.10.1994 ==================== F11LEV === Nelly's talk on LUMI-94 For those who are interested. A postscript file (18 pages) with the content of the talk given by Nelly Gogitidze on the H1 plenary meeting 13-Oct-94 is available on dice2: ~nellyg/oct94.nelly.talk.ps You can look in it by e.g. ghostview. It would be also useful to include it in WWW under our LPI server. It contains an interesting information, which also can be used in future. P.S. Before send a coplete file (> 5Mb) to the plotter think twice! It will block the plotter for 2 hours (because of the p. 8,13,14) This is one of the reasons, why the file is announced at dice2: everybody can look in it without hardcopy. 15/10/94 ==================== squinabol === Lumi RUN# 641 Start lumi run641 date: 15/10/94 Collision time: 1:39:33 - 2:17:53 Currents (mkA): Ie= 29787.00, Ip= 42001.00 Peak luminosity: 3265.159 mb-1 s-1 Peak spec.lumi : 481.303415 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 4107.9198 mkb-1 H1 Run total lumi: 3112.412 mkb-1 H1 data taken lumi: 2565.4437 mkb-1 H1 Runs: 89206 - 89213 HERA - physics: 3156.911292 mkb-1 H1Run - physics: 1968.06699 mkb-1 H1data - physics: 1480.728331 mkb-1 H1 Runs: 89207 - 89213 Tot curr/rate factor: 4.49% C/R F H1Run gated: 4.5% Rand.C.F: 1.79% RCF Run gated: 1.77% Relative ET trigg accept.: 0.4775 15/10/94 ==================== squinabol === Lumi RUN# 642 Start lumi run642 date: 15/10/94 Collision time: 3:18:15 - 4:14:47 Currents (mkA): Ie= 26516.00, Ip= 42000.00 Peak luminosity: 2555.577 mb-1 s-1 Peak spec.lumi : 439.348069 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 6657.9347 mkb-1 H1 Run total lumi: 7551.5716 mkb-1 H1 data taken lumi: 6978.5297 mkb-1 H1 Runs: 89217 - 89223 HERA - physics: 4380.143107 mkb-1 H1Run - physics: 3676.306738 mkb-1 H1data - physics: 3166.624985 mkb-1 H1 Runs: 89219 - 89223 Tot curr/rate factor: 1.9% C/R F H1Run gated: 1.92% Rand.C.F: 1.38% RCF Run gated: 1.38% Relative ET trigg accept.: 0.5063 15/10/94 ==================== squinabol === Lumi RUN# 643 Start lumi run643 date: 15/10/94 Collision time: 6:05:47 - 12:53:21 Currents (mkA): Ie= 27800.00, Ip= 41300.00 Peak luminosity: 2542.965 mb-1 s-1 Peak spec.lumi : 407.596661 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 38937.198778 mkb-1 H1 Run total lumi: 35578.162265 mkb-1 H1 data taken lumi: 31004.314424 mkb-1 H1 Runs: 89228 - 89245 HERA - physics: 38886.164798 mkb-1 H1Run - physics: 35476.256738 mkb-1 H1data - physics: 30907.756044 mkb-1 H1 Runs: 89228 - 89245 Tot curr/rate factor: 1.12% C/R F H1Run gated: 1.15% Rand.C.F: 0.82% RCF Run gated: 0.82% Relative ET trigg accept.: 0.5291 PS(LNS): for R89232 (~51 Kevents): L4 histos OK; L5 OK, too. PS(LNS): A little warning: PD (Edet-Etrig) a little changed: "the positive (the second) peak" transformed into "a shoulder". 16/10/94 =================== Malinovski === Lumi RUN# 644 Start lumi run644 date: 15/10/94 Collision time: 20:08:10 - 7:07:26 Currents (mkA): Ie= 30299.00, Ip= 49700.00 Peak luminosity: 3164.711 mb-1 s-1 Peak spec.lumi : 388.543465 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 80011.486981 mkb-1 H1 Run total lumi: 75469.2869 mkb-1 H1 data taken lumi: 69615.9584 mkb-1 H1 Runs: 89252 - 89266 HERA - physics: 78657.589102 mkb-1 H1Run - physics: 73482.418747 mkb-1 H1data - physics: 67693.840813 mkb-1 H1 Runs: 89253 - 89266 Tot curr/rate factor: 0.89% C/R F H1Run gated: 0.9% Rand.C.F: 0.87% RCF Run gated: 0.87% Relative ET trigg accept.: 0.5079 PS(LNS): for R89259 (~99 Kevents): L4 histos OK; L5 OK, too. PS(LNS): A little warning: PD (Edet-Etrig) a little changed: "the positive (the second) peak" transformed to "a well-seen shoulder". 16/10/94 ==================== Squinabol === Lumi RUN# 645 Start lumi run645 date: 16/10/94 Collision time: 8:15:24 - 18:47:35 Currents (mkA): Ie= 30618.00, Ip= 48400.00 Peak luminosity: 2897.392 mb-1 s-1 Peak spec.lumi : 364.441326 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 59593.34709 mkb-1 H1 Run total lumi: 55673.5256 mkb-1 H1 data taken lumi: 49953.6253 mkb-1 H1 Runs: 89266 - 89285 HERA - physics: 57437.928227 mkb-1 H1Run - physics: 52977.093969 mkb-1 H1data - physics: 47314.072653 mkb-1 H1 Runs: 89267 - 89285 Tot curr/rate factor: 1.43% C/R F H1Run gated: 1.43% Rand.C.F: 0.78% RCF Run gated: 0.77% Relative ET trigg accept.: 0.5345 PS(LNS): for R89278 (~70 Kevents): L4 histos OK; L5 OK, too. PS(LNS): A little warning: PD (Edet-Etrig) a little changed: "a well-seen shoulder" (see up) has disappiered; ET/channel changed. 17.10.1994 ===== dice2 ======== H1KFOM === Selected H1Lumi Monitrig.. Today it were selected calibration data samples from the next data sets which were produced with standard job prepared by S.Levonyan at dice1-environment: HERA03.H01.LUMIMON.C9400119 K41302 78048081 00001 ACS-E-C ...... HERA03.H01.LUMIMON.C9400123 K35173 78048081 00001 ACS-E-C It were selected events with (s92=1 only),with ET&PD&VC=1 and with ET&PD&nVC from these data sets (as ordinary): 1) S92=1 only 33701 events ( 54.0 MBytes) 2) ET&PD&VC 75709 events (125.8 MBytes) 3) ET&PD&nVC 62075 events (103.2 MBytes) Created data sets were saved at DESY IBM storage at the next data sets H1KFOM.ETPDNVC.M119123.C00 K24107 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M119123.C00 K24236 78048081 00001 ACS-E-C H1KFOM.S92.M119123.C00 K24427 78048081 00001 ACS-E-C These data include events from Lumi RUNs# 637-644 (H1 Runs 89075- 89264). 17.10.1994 ==================== H01GOG === H1TCL data processing..... In agreement with Yura, after his return to Moscow I continue now the H1TCL files processing by LRATES tool on IBM. Here below a list of last output LOOK history files is given: H1KSOL.RLOOK.CART58-CART77 H01GOG.RLOOK.CART78-CART91 17.10.1994 ==================== H01GOG === LUMIMON data processing Here is a continuation of a summary table for e+p LUMIMON files, processed so far. ---------------------------------------------------------------------- File H1 runs Events Actual triggers (xx) s86 s91 s92 s93 s94 s95 ---------------------------------------------------------------------- 118 88992-89075 128365 10375 5894 6946 9643 9040 10426 119 89075-89089 128116 7601 6301 6895 10893 9015 11081 120 89089-89146 128651 7890 5094 5994 8796 7737 8963 121 89146-89221 128081 8948 5809 6959 9651 9139 10122 122 89221-89256 128215 10453 4838 6022 7413 7686 8401 123 89256-89264 128017 6907 5746 7070 8676 9378 10094 ---------------------------------------------------------------------- No new observations. All figures look reasonable and standard. Peak at PD-11 still there. Resolution in fig.36, sigma(E)/E = ~4% 18/10/94 ===================== M.Seidel === Lumi RUN# 646 Start lumi run646 date: 18/10/94 Collision time: 3:33:53 - 18:35:08 Currents (mkA): Ie= 32505.00, Ip= 52300.00 Peak luminosity: 3547.451 mb-1 s-1 Peak spec.lumi : 405.305224 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 104420.019014 mkb-1 H1 Run total lumi: 86374.8254 mkb-1 H1 data taken lumi: 69925.9142 mkb-1 H1 Runs: 89412 - 89478 HERA - physics: 102564.618251 mkb-1 H1Run - physics: 83479.1848 mkb-1 H1data - physics: 67092.5711 mkb-1 H1 Runs: 89413 - 89478 Tot curr/rate factor: 0.51% C/R F H1Run gated: 0.54% Rand.C.F: 0.85% RCF Run gated: 0.84% Relative ET trigg accept.: 0.5102 19/10/94 ====================== S.Riess === Lumi RUN# 647 Start lumi run647 date: 18/10/94 Collision time: 20:28:55 - 6:05:06 Currents (mkA): Ie= 30930.00, Ip= 49601.00 Peak luminosity: 2921.205 mb-1 s-1 Peak spec.lumi : 370.124731 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 59431.895564 mkb-1 H1 Run total lumi: 52508.2922 mkb-1 H1 data taken lumi: 47069.5876 mkb-1 H1 Runs: 89490 - 89518 HERA - physics: 56204.121883 mkb-1 H1Run - physics: 48101.938225 mkb-1 H1data - physics: 42783.242167 mkb-1 H1 Runs: 89491 - 89518 Tot curr/rate factor: 0.36% C/R F H1Run gated: 0.39% Rand.C.F: 1.08% RCF Run gated: 1.09% Relative ET trigg accept.: 0.5067 PS(LNS): for R89496 (~53 Kevents): L4 histos OK; L5 OK, too. PS(LNS): A little warning: E_Etag: a shoulder 21-25 GeV appiered. 20.10.1994 ==================== F11LEV === Minutes of the LPI meeting Place: DESY Time: 19/17/94 19-21 pm. Participants: Baranov, Belousov, Eliseev, Gogitidze, Gorbov, Levonian, Lebedev, Malinovski, Rusakov, Sheviakov, Usik, Vazdik, Smirnov (part of time) Topics: 1) Status of the new e-tagger project 2) Work during the winter shutdown 94/95 3) Preliminary schedule for the 95-visits (proposal) 1) History: o First proposal on the H1 long term upgrade meeting at DESY, Dec'93 (S.Lev.) o First rough simulation of the acceptances, Dc'93-Mar'94 (S.Lev.) o Detailed MC studies including H1LUMI program upgrade, Jun-Aug'94 (V.And.) o Discussions with ZEUS: May'94 (S.Lev.), Aug'94(S.L.,V.A.,R.Felst) o Technical Proposal + H1 note, Sept'94 (S.L, V.A. + Eichler,Egli) o PRC meeting, closed session, 17-Oct-94, DESY. Outcome: a) go ahead with the design work for the beampipe modifications (target date: April'95) b) final decision - after price estimate when the design is finished. Possible scenario for 1995: a simple (temporary?) solution: new small ET at z=-44m with very small acceptance (~20% of the z=-38m in our proposal), but - which is much simpler (minor modifications in the tunnel), and - which could be ready by summer'95 This is a proposal from ZEUS (Uwe Schneekloth). And this is the only chance to have at least something available already next year. This solution does not satisfy our major physics motivation (HQ triggering), but we also can profit from this, by measuring a real rates and background conditions for small y values (large E_e), which is very difficult to predict otherwise. Also a real data can be used to develop a calibration procedure and to set up a best trigger threshold for physics events. Concequences: a) a simple small detector should be ready for the installation by May'95. A necessary infrastructure in the tunnel (cabels, support etc.) - even earlier (till the end of the shutdown) b) online (trigger, DAQ) and offline (MC, rec, calibr) should be ready as well Contact/responsible persons, nominated officially by H1 and ZEUS collaborations: ZEUS: Uwe Schneekloth H1: G.Winter, V.Andreev General: R.Felst P.S. Very fresh information (1 hour ago)! A basic design for the 44m is done(!) It is possible to be prepared during this shutdown and thus the detector can be installed before the data taking starts (March-April). The design (top view) looks as follows (precise values are being checked by R.Felst presently): -------------------------------------------------- e-beam axis beam pipe +-----------------+ | place for ET-1 | -------------------+ +----------------------- z=-44m 2) Work during winter shutdown 94/95. This was summarized in the talk of N.Gogitidze at the Collaboration meeting and is available on dice2 (last page of the talk). Just few comments to that. a) This (1994) year, thanks to the great effort of A.Fomenko, the situation with the calibration procedure improved significantly, compared to 1993. However, this was done, in my personal view, at the expence of the quality of the online DAQ s/w, which was not sufficiently supported/improved/debugged! This MUST be avoided in future. Taking into account, that a major modifications in this part is necessary to speed up a LUMI branch (new hardware -> new multiprocessor scheme -> new s/w), this implies, that A.Fomenko should concentrate exclusively on the online s/w at least until the system will work reliably and all known (for a long time!) bugs will be fixed. In parallel to that, the offline calibration procedure should be simplified in terms of reducing the amount of manual operations which is presently involved in this work. This task I would consider as one of the important remaining tools to be prepared most likely by myself. b) Another remark concerns a general system design and the situation with the long term investigations of its behaviour. Again, in my view, there was absolutely insufficient activity in this area. There was no clear long term program to study various basic problems like: - an optimization of the system architecture - understanding of all details of the VC behaviour - possible influence of the synchrotron radiation on various components of the system etc. This is very strange remembering how many well qualified experts in corresponding areas we have in our group. 3) Proposal for the visits to DESY in 1995. This was first given in my mail to A.S.Belousov in Sept-94 with the basic argumentations, and was then distributed (by A.S.?) between part of the group: P.Baranov, S.Rusakov, A.Lebedev, E.Malinovski and L.Shtarkov. I see no reasons why others should not be informed as well. I want also to mention, that I gave my proposal and my motivaton to Feltesse and Straumann. The proposals concerns exclusively the people involved in the LUMI business, which is still our main resposibility in the collaboration The rest of the group is not discussed, there and I cannot judge on the requirements. MINIMAL scheme for the work (!) at DESY (x - full month, o - 1/2 month) ----------------------+---------------------------------------+------ Name / Month-95 | J F M A M J J A S O N D | Sum ----------------------+---------------------------------------+------ Andreev .......... | x x x x x x | 6 Fomenko .......... | x x x x x x x x | 8 Gogitidze ........ | x x x x x | 5 Levonian ........ | | Malinovski ....... | x o x o | 3 Sheviakov ........ | x x x x x x x x x x x x | 12 Soloviev ......... | x x x x x x x x | 8 Usik ............. | x x x x x | 5 Shtarkov ......... | x x x | 3 ----------------------+---------------------------------------+------ Sum: | | 50 ----------------------+---------------------------------------+------ Remarks: 1) These 50 men-months have to be compared to the time distribution in 1994: -LUMI/eTAG tasks (V.A, A.F, N.G, E.M, I.Sh, L.S, Yu.S, A.U) ...... 38 mm -Spacal, FPS (H1 members) (P.S, S.K) ...................................... 16 mm -Other H1 members from LPI (A.L, S.R, Ya.V) ................................ 16 mm -Spacal construction (non H1 members) (A.E,L.G,S.K,V.M,V.K,A.Ch,A.Sh,V.M,K.Kh,M.B) .... 50.5 mm ---------------------------------------------------------- Sum 120.5 mm ---------------------------------------------------------- (Information from H.Kleinebenne, Sept-94) 2) This time is necessary only for the work which is already now under the responsibility of corresponding persons. It may be changed in case this responsibility will include an additional work, or opposite, will be reduced. 3) Main tasks for the discussed people are listed below: V.A. - new tagger: MC, SIM/REC implementation, real data analysis LUMM data analysis with the aim to develop real online algorithm for the lumi estimate from the single gamma-rate. A.F. - LUMI DAQ s/w !!! Improvement of the overall reliability of the system (s/w part) I.Sh. - Trigger, electronics; h/w system upgrade, including new taggers in the system Yu.S. - Detectors, some offline lumi tools, general system support (can act as an online system manager, on my view) A.U. - Lumi information distribution (improvements & upgrade) N.G. - Lumi monitoring, calibration -> offline L corrections L.S. - Data quality check at L4/L5, including automatization of this procedure (!) E.M. - Infrastructure for the new taggers, first small additional detector for the position 44m 4) A (very high) potential of A.Usik is used insufficiently (my personal opinion). He can contribute to various aspects much more. 5) For all: there is a large room for the initiative. Any task is available for everybody. However, it will not work unless the is a clear responsible person, known to the collaboration, and who indeed FEELS the responsibility and provides a definite final RESULT, not just trying and playing around infinitely long. There was a question rised by A.Lebedev: which part (if any) of the discussed work can be done at Moscow either using local computing facilities (SGI), or working remotely at DESY over the computer link? Yes, part of the work (not urgent MC simulations, some limited data analysis, some physics analysis, most of the theoretical physics) can be done this way. And partially it is being done already now. For example, the correction for the online Lumi-94 would not be possible to make in time for the collaboration meeting, without hard work done by Nelly Gogitidze in August-September from Moscow. Also for example, 6 months of V.Andreev at DESY does not mean that another 6 months he will relax. No, he must and I hope will work from Moscow in order to prepare most efficiently his time at DESY. Finally, now A.Fomenko is doing the calibration from Moscow and thus helps a lot for the offline data analysis. So these were "good" examples. However, there are other examples, very well known to everybody in the group, showing, that often a time at DESY is spent without any profit for our work and for the collabo- ration. In such cases, the time should be taken from inefficient persons in favor of others. 21/10/94 ====================== J.MEYER === Lumi RUN# 648 Start lumi run648 date: 20/10/94 Collision time: 21:52:07 - 2:12:14 Currents (mkA): Ie= 29000.00, Ip= 36100.00 Peak luminosity: 2359.6 mb-1 s-1 Peak spec.lumi : 442.013458 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 19262.650314 mkb-1 H1 Run total lumi: 18355.9019 mkb-1 H1 data taken lumi: 16565.1525 mkb-1 H1 Runs: 89698 - 89712 HERA - physics: 18027.72979 mkb-1 H1Run - physics: 16673.835324 mkb-1 H1data - physics: 14931.966275 mkb-1 H1 Runs: 89700 - 89712 Tot curr/rate factor: 0.08% C/R F H1Run gated: 0.08% Rand.C.F: 1.3% RCF Run gated: 1.3% Relative ET trigg accept.: 0.4639 PS(LNS): for R89707 (~52 Kevents): L4 histos ~ OK; L5 ~ OK, too. PS(LNS): Warning, going to SOS: all L4 and L5 ET-spectra display high background at the energies 2-4 Gev higher than usial. For E_Etag it is a broud enchacement at 20 - 24 GeV, about twice higher than usial. B.t.way, Rel.ET accept. is ~10-15% lower than the values of last time. 21.10.1994 ===== dice2 ======== H1KFOM === Relation Coeff.Set 10A Today it was made attempt to produce Rel.Coeff.Set for 10A (low p11) data sample (from H1 Run 88877 up to Run 89264).It were selected 108598 ET&PD&nVC events from this H1 Run range from data sets (only G- and M- labeled H1 Runs at H1EP): H1KFOM.ETPDNVC.M115118.C00 K44113 78048081 00001 ACS-E-C H1KFOM.ETPDNVC.M119123.C00 K24107 78048081 00001 ACS-E-C After all high mentioned 'cleaning' of 10A(low p11)data samples it were collected: 108598 events with ET&PD&nVC trigger 132056 events with ET&PD&VC trigger 58680 events with S92-trigger (PD&nVC-events). It were got 108598 ET&PD&nVC from these Runs and it were used for calibration 39743 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 0.944 1.223 0.697 0.943 0.820 0.991 0.852 0.791 0.968 0.989 0.862 1.088 0.959 0.961 1.202 0.902 0.891 1.008 0.937 1.267 0.916 1.028 1.018 1.005 1.009 1.013 0.968 0.981 0.990 1.058 1.010 0.925 1.045 0.998 0.944 1.015 0.809 1.125 0.923 0.989 0.983 0.915 0.936 0.912 0.931 0.670 0.873 0.946 0.000 ==> Relation Coeff.Set for PD 1.533 0.938 1.006 1.437 1.198 0.945 1.033 1.059 1.034 0.973 0.986 1.053 1.020 1.013 1.057 1.080 1.024 0.990 1.010 1.070 1.171 0.989 1.054 1.162 1.018 ==> Sig. at Relation Coeff.Set for ET 0.000 0.163 0.223 0.101 0.030 0.152 0.078 0.271 0.055 0.057 0.240 0.046 0.073 0.063 0.068 0.161 0.070 0.055 0.108 0.440 0.084 0.043 0.022 0.022 0.024 0.033 0.040 0.025 0.009 0.040 0.027 0.032 0.037 0.013 0.085 0.007 0.160 0.189 0.063 0.000 0.003 0.000 0.003 0.009 0.085 0.249 0.040 0.000 0.000 ==> Sig. at Relation Coeff.Set for PD 0.379 0.035 0.118 0.139 0.221 0.078 0.097 0.072 0.035 0.068 0.066 0.063 0.032 0.034 0.031 0.068 0.036 0.067 0.111 0.104 0.335 0.033 0.031 0.264 0.197 ==> Ent. at Relation Coeff.Set for ET 2 34 14 32 31 33 11 13 112 181 165 200 134 79 2308 522 635 843 638 1237 415 10432 16109 13007 10739 8982 7601 3634 3915 6144 4632 3259 3443 2401 1453 30 4 11 16 2 10 1 3 3 2 4 3 1 0 ==> Ent. at Relation Coeff.Set for PD 83 31 46 52 3 1181 7025 8040 1477 77 11246 30846 24799 5232 200 3300 8889 3570 493 29 37 33 37 20 4 As You can see all sigma values for 'hot' H1Lumi cahnnels RC histos have more values then ordinary and it is possible to explain with large statistics at this data sample. e19 has very large sigma value (0.440) Runs 88877-89264 (ET&PD&nVC-sample - near 109.0K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.43 1.06 27.45 1.05 27.50 1.03 Runs 88877-89264 (ET&PD&VC-sample - near 132.0K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.53 1.35 27.55 1.32 As start values of Calibration Coefficients for Photoproduction Branch were got ones after 3rd step of calibration with ET&PD&nVC events from 9C-sample (H1 Runs 88558-88877 - near 60.0 K events). CCvcs value was got from last VCs calibration at 9C-sample of ETPDVC events (H1Runs 88558-88877 - see message from 13.10.94 at LL10). (CCvcs start = 4.554 MeV/FADCcount). Attempt to make fit of PhotonArm Energy spectrum was not enough succesful (with enough good statistics). 21.10.1994 ===== dice2 ======== H1KFOM === PDREC-spectra for 10A Today it were produced 100th ntuple for S92=1 events from earlier mentioned 10A-sample with events from Runs 88877-89264: H1KFOM.YLOOKQ4.R88877 (50455 entries) FAST09 3010200E 00000 DASD At interactive LOOK-session it was produced 70th histo for this data set and written into the next LOOK-binary data set: H1KFOM.BLOOKQ2.R88877 28190 entries in 70h FAST12 3010200E 00000 DASD First attempt to fit 70th histo at BLOOKQ2-data set put negative sign of Global Energy Shift at Photon Arm (-4.2%) and not very good resolution digits (23-25%) for (14-20)-35GeV regions. It were prepared 100th tuples with ET&PD&nVC and ET&PD&VC-events for procedure of defining Global Energy Shifts and CCvcs: H1KFOM.YLOOKQ2.R88877 107394 entries FAST04 3010200E 00000 DASD H1KFOM.YLOOKQ3.R88877 120078 entries FAST08 3010200E 00000 DASD 21.10.1994 ==================== H1KFOM === Global Shifts,CCvcs 10A It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 1.042 for PD Channels (exept VCs), 0.9708 for ET channels. Correction factor for CCvcs is 1.020. So CCvcs = 4.554*1.020 =4.645Mev FADCcount. These digits are valid for H1Lumi events from Run 88877 up to 89264 Runs 88877- 89264 (ET&PD&nVC-sample - near 108.0K events) xetcut&vcdepcut Step Mean Sigma 0 27.52 1.04 Runs 88877- 89264 (ET&PD&VC-sample - near 132.0K events) xetcut Step Mean Sigma 0 27.52 1.33 P.S. CCp11 was the same almost as at 9C-samples. CCe19 was the same almost as at 9C-samples. CCvcs(averaging) was incremented only on 2%. For any case - this is the final values of CC at Photoproduction branch after 3rd step of calibration with 10A-data sample (H1 Runs 88877-89264): ==> ET Calibr.Coefficients Final Status e00= 4.136 4.516 4.196 3.397 3.972 2.995 3.364 4.412 4.028 4.374 1.946 5.686 4.346 3.991 6.597 2.404 4.325 5.375 4.425 10.530 4.590 7.305 4.931 5.746 4.858 4.315 4.972 4.331 4.339 5.272 4.783 3.991 5.330 4.897 3.142 4.481 4.650 3.508 3.718 4.411 4.323 4.021 e42= 4.094 3.973 4.341 1.984 3.719 4.144 4.018 ==> PD & VC Calibr.Coefficients Final Status p00= 2.084 1.472 1.409 2.376 2.576 1.231 2.586 2.956 2.142 1.645 2.289 4.955 3.020 2.970 2.100 2.232 2.010 2.654 2.900 2.442 p20= 1.334 1.598 2.092 3.089 2.549 vcs= 4.645 21.10.1994 ==================== H1Kshe === Beam scan. Last e,p beams scan data: H1 Run # 89733, has started at 10.56 Time Xe Ye Xp Yp 11:02 -0.5mm 0.0 -0.5mm 0.0 11:07 -1.0mm 0.0 -1.0mm 0.0 --The next data corresponds to definitly stable beam positions.-- 11:22 -0.25mm 0.0 0.0 0.0 11:25 -0.5mm 0.0 0.0 0.0 11:30 -0.5mm -0.5mm 0.0 0.0 11:34 -0.75mm -0.5mm 0.0 0.0 11:37 -0.75mm -1.0mm 0.0 0.0 ------Finally up to the end of 89733 run ------------ 11:59 -1.0mm -0.5mm Luminos.tuning The next h1run # 89734 has been started with new e+beam position (Xe=-1.00,Ye=-0.5) and specific lum. = 3.4E29 sm-2 ma-2. 21.10.1994 ==================== H1KFOM === New RC Sets in H1DataBase As final action of all 21.10.94 calibration steps it was made update of LFRC and LESC banks at H1DataBase with S.Levonyan's tool. All Relation Coefficients values, CCvcs and Global Energy Shift constants were got from the next messages at LLO: 21.10.1994 ----- dice2 -------- H1KFOM --- Relation Coeff.Set 10A 21.10.1994 -------------------- H1KFOM --- Global Shifts,CCvcs 10A Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LFRC (_501) 47 e-p data 410211258 88877 0 77 941021 H1KFOM Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LESC (_582) 55 e-p data 410211258 88877 0 3 941021 H1KFOM 21/10/94 ====================== J.MEYER === Lumi RUN# 649 Start lumi run649 date: 21/10/94 Collision time: 3:10:31 - 12:17:49 Currents (mkA): Ie= 24719.00, Ip= 35900.00 Peak luminosity: 1990.35 mb-1 s-1 Peak spec.lumi : 427.22705 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 37979.398205 mkb-1 H1 Run total lumi: 36621.9346 mkb-1 H1 data taken lumi: 33154.6808 mkb-1 H1 Runs: 89714 - 89735 HERA - physics: 36664.645417 mkb-1 H1Run - physics: 35023.583652 mkb-1 H1data - physics: 31597.299516 mkb-1 H1 Runs: 89715 - 89735 Tot curr/rate factor: 0.06% C/R F H1Run gated: 0.07% Rand.C.F: 0.97% RCF Run gated: 0.97% Relative ET trigg accept.: 0.4510 P.S. During Runs 89733,89734 beam scan was made (see today I Shev. message). PS(LNS): for R89718 (~41 Kevents): L4 histos ~ OK ? ; L5 ~ OK ? , too. PS(LNS): WARNING, ABOUT SOS ! E_Etag became much worse, then prev.run: Background at 20 - 24 GeV "has overgrown the main peak" ~ *2 times. Again, Rel.ET accept. is ~10-15% lower than the values of "last time". 21.10.1994 ==================== F11LEV === No SOS in etag events..... Shtarkov wrote: PS(LNS): Warning, going to SOS: all L4 and L5 ET-spectra... PS(LNS): WARNING, ABOUT SOS ! E_Etag became much worse, then prev.run: Background at 20 - 24 GeV "has overgrown the main peak" ~ *2 times." Explanation: ------------ Since H1 run 89469 (18-Oct) till next Monday, when a shifted IP data taking will start, a new subtrigger is added: s90 = eTAG && ToF_IA with the purpose to get high acceptance for the total cross section measurement (including high efficiency to the elastic channel). Since most of the elastic events are essentially empty in the main H1 detector (except hits in ToF and small energy in the backward tail catcher), we decided to pass these events through L4 and L5 without any cuts, up to DST level. Only there in the offline analysis one has to develop an appropriate selection criteria to reject the background, keeping reasonably high acceptance for the signal. Of course, this trigger (s90) also accepts a lot of background (e-gas, random coincidences etc.) As a concequence, this trigger now contributes a higher level of background, compared to the standars eTAG setting (s80,s83,...) where a sharp cuts were applied already at L4. This explains an observation of worse E-etag distribution in L4/L5 histograms. This is known and was expected when we proposed to add subtrigger s90 for the last week of the normal (nominal IP positition) data taking. I should perhaps give this information earlier, to avoid unnecessary warnings. Anyway, it is good, that this was recognized independently. PS(LNS): It makes neccessary to update the L4 Reference histos. PPS(SL): Has not too much sence, because an exercise will finish tomorrow, 23-Oct. PS(LNS): 24 Oct. the E_ET & E_Etag are about the same "backgrounded". PPS(SL): This collisions (652) have started still at Oct,23. Therefore. See also PPS for the Lumi RUN# 652. 22/10/94 ====================== Zarbock === Lumi RUN# 650 Start lumi run650 date: 22/10/94 Collision time: 9:57:14 - 10:11:40 Currents (mkA): Ie= 32847.00, Ip= 33700.00 Peak luminosity: 0 mb-1 s-1 Peak spec.lumi : 0 mb-1 s-1 mA-2 Number of collided b.: 0 Number of e-filled b.: 0 Number of p-filled b.: 0 Number of e-pilot b.: 0 Number of p-pilot b.: 0 HERA total lumi: 8.836783 mkb-1 H1 Run total lumi: 8.836831 mkb-1 H1 data taken lumi: 8.726235 mkb-1 H1 Runs: 89792 - 89792 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 89792 - 89792 Tot curr/rate factor: -2.07% C/R F H1Run gated: -2.07% Rand.C.F: Not calc.% RCF Run gated: Not calc.% Relative ET trigg accept.: Not calc. 22/10/94 ====================== Schleif === Lumi RUN# 651 Start lumi run651 date: 22/10/94 Collision time: 19:04:32 - 23:27:07 Currents (mkA): Ie= 28781.00, Ip= 24700.00 Peak luminosity: 889.679 mb-1 s-1 Peak spec.lumi : 384.623931 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 12605.8099 mkb-1 H1 Run total lumi: 12089.9222 mkb-1 H1 data taken lumi: 11326.8761 mkb-1 H1 Runs: 89821 - 89834 HERA - physics: 12328.920054 mkb-1 H1Run - physics: 11388.5563 mkb-1 H1data - physics: 10632.7674 mkb-1 H1 Runs: 89823 - 89834 Tot curr/rate factor: 0.25% C/R F H1Run gated: 0.25% Rand.C.F: 0.68% RCF Run gated: 0.68% Relative ET trigg accept.: 0.4236 PS(LNS): for R89867, Nev~24k, L4 and L5 are ~ OK, however, the ET-spectra are "backgrounded", as it had started at the previous runs. Btw, Erec-Edep is ~2 Gev for ET. 24/10/94 ============== Zarbock/Schleif === Lumi RUN# 652 Start lumi run652 date: 23/10/94 Collision time: 20:21:58 - 4:23:37 Currents (mkA): Ie= 26817.00, Ip= 28300.00 Peak luminosity: 1758.212 mb-1 s-1 Peak spec.lumi : 435.739733 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 33400.474285 mkb-1 H1 Run total lumi: 30224.193 mkb-1 H1 data taken lumi: 27189.6968 mkb-1 H1 Runs: 89862 - 89886 HERA - physics: 32721.288094 mkb-1 H1Run - physics: 29254.9568 mkb-1 H1data - physics: 26311.8807 mkb-1 H1 Runs: 89863 - 89886 Tot curr/rate factor: 0.42% C/R F H1Run gated: 0.43% Rand.C.F: 0.92% RCF Run gated: 0.93% Relative ET trigg accept.: 0.4333 PS(LNS): for R89824, Nev~53k, L4 and L5 are ~ OK, however, the ET-spectra are "backgrounded", as it had started at the previous runs. (Btw, Erec-Edep is ~2 Gev for ET). A little Warning: there is none for R89868-R89886 at H1EP; Why ? PPS (S.L.) 1) Runs 89868-89886 ARE in H1EP. 2) HERA has started an exercise with shifted z-vertex collisions. First attempt was unsuccessful: beam was lost They will try again. However, it is difficult to predict what will happen during this last week of data taking. So many distributions may look non-standard. If, e.g. collisions with shifted vertex will be achieved, then practically all triggers except BSET (low Q^2 DIS) will be disabled (some monitoring triggers will stay of course, but etag physics triggers not). 24/10/94 ====================== Schleif === Lumi RUN# 653 Start lumi run653 date: 24/10/94 Collision time: 6:04:52 - 7:53:42 Currents (mkA): Ie= 28022.00, Ip= 27800.00 Peak luminosity: 522.009 mb-1 s-1 Peak spec.lumi : 366.801135 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 4654.686788 mkb-1 H1 Run total lumi: 3426.680581 mkb-1 H1 data taken lumi: 2178.60574 mkb-1 H1 Runs: 89895 - 89912 HERA - physics: 2041.051339 mkb-1 H1Run - physics: 797.011381 mkb-1 H1data - physics: 295.36344 mkb-1 H1 Runs: 89896 - 89912 Tot curr/rate factor: 0.58% C/R F H1Run gated: 0.49% Rand.C.F: 1.28% RCF Run gated: 1.57% Relative ET trigg accept.: 0.4712 PS(LNS): None of info at L4 / L5, even there is something at H1ep. 24.10.1994 ===== dice2 ======== H1KFOM === Selected H1Lumi Monitrig.. Today it were selected calibration data samples from the next data sets which were produced with standard job prepared by S.Levonyan at dice1-environment: HERA03.H01.LUMIMON.C9400124 K42914 78048081 00001 ACS-E-C ...... HERA03.H01.LUMIMON.C9400129 K23438 78048081 00001 ACS-E-C It were selected events with (s92=1 only),with ET&PD&VC=1 and with ET&PD&nVC from these data sets (as ordinary): 1) S92=1 only 32045 events ( 50.8 MBytes) 2) ET&PD&VC 70605 events (117.4 MBytes) 3) ET&PD&nVC 54219 events ( 90.1 MBytes) Created data sets were saved at DESY IBM storage at the next data sets H1KFOM.ETPDNVC.M124129.C00 K20120 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M124129.C00 K20648 78048081 00001 ACS-E-C H1KFOM.S92.M124129.C00 K13208 78048081 00001 ACS-E-C These data include events from Lumi RUNs# 644-652 (H1 Runs 89264- 89877). 24/10/94 ====================== Smirnov === Lumi RUN# 654 Start lumi run654 date: 24/10/94 Collision time: 12:24:29 - 20:11:46 Currents (mkA): Ie= 28401.00, Ip= 41100.00 Peak luminosity: 2020.205 mb-1 s-1 Peak spec.lumi : 377.355125 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 165 Number of p-filled b.: 170 Number of e-pilot b.: 12 Number of p-pilot b.: 17 HERA total lumi: 34012.432276 mkb-1 H1 Run total lumi: 29705.103456 mkb-1 H1 data taken lumi: 27998.910962 mkb-1 H1 Runs: 89927 - 89949 HERA - physics: 32302.812211 mkb-1 H1Run - physics: 28238.114631 mkb-1 H1data - physics: 26586.014421 mkb-1 H1 Runs: 89930 - 89949 Tot curr/rate factor: 0.26% C/R F H1Run gated: 0.27% Rand.C.F: 0.83% RCF Run gated: 0.77% Relative ET trigg accept.: 0.4883 PS(LNS): for R89944, Nev~33k, L4 and L5 are ~ OK, only if remembering the S.L.'s remarks at LLO and at DQ last Meeting. 24/10/94 =================== Niedzballa === Lumi RUN# 655 Start lumi run655 date: 24/10/94 Collision time: 21:31:03 - 21:36:53 Currents (mkA): Ie= 31414.00, Ip= 38900.00 Peak luminosity: 0 mb-1 s-1 Peak spec.lumi : 0 mb-1 s-1 mA-2 Number of collided b.: 0 Number of e-filled b.: 0 Number of p-filled b.: 170 Number of e-pilot b.: 0 Number of p-pilot b.: 170 HERA total lumi: 0.054178 mkb-1 H1 Run total lumi: 0.054178 mkb-1 H1 data taken lumi: 0.053855 mkb-1 H1 Runs: 89957 - 89957 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 89957 - 89957 Tot curr/rate factor: 0% C/R F H1Run gated: 0% Rand.C.F: 31.24% RCF Run gated: 31.24% Relative ET trigg accept.: Not calc. PS(LNS): None of info ... 25/10/94 ==================== Buniatian === Lumi RUN# 656 Start lumi run656 date: 25/10/94 Collision time: 0:24:06 - 0:48:46 Currents (mkA): Ie= 30197.00, Ip= 38700.00 Peak luminosity: 0 mb-1 s-1 Peak spec.lumi : 0 mb-1 s-1 mA-2 Number of collided b.: 0 Number of e-filled b.: 0 Number of p-filled b.: 170 Number of e-pilot b.: 0 Number of p-pilot b.: 170 HERA total lumi: 481.6847 mkb-1 H1 Run total lumi: 481.684164 mkb-1 H1 data taken lumi: 392.866604 mkb-1 H1 Runs: 89957 - 89957 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 89957 - 89957 Tot curr/rate factor: 2.55% C/R F H1Run gated: 2.55% Rand.C.F: 4.74% RCF Run gated: 4.74% Relative ET trigg accept.: 0.4645 PS(LNS): None of info ... 25/10/94 ==================== Buniatian === Lumi RUN# 657 Start lumi run657 date: 25/10/94 Collision time: 4:32:48 - 6:38:04 Currents (mkA): Ie= 27725.00, Ip= 35500.00 Peak luminosity: 1657.242 mb-1 s-1 Peak spec.lumi : 320.64063 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 9413.248067 mkb-1 H1 Run total lumi: 9201.5627 mkb-1 H1 data taken lumi: 8358.9257 mkb-1 H1 Runs: 89968 - 89973 HERA - physics: 7371.031609 mkb-1 H1Run - physics: 6970.912206 mkb-1 H1data - physics: 6307.042106 mkb-1 H1 Runs: 89969 - 89973 Tot curr/rate factor: 0.27% C/R F H1Run gated: 0.27% Rand.C.F: 1.46% RCF Run gated: 1.46% Relative ET trigg accept.: 0.4662 PS(LNS): Too little of info ... 25/10/94 ============ Buniatian/Schleif === Lumi RUN# 658 Start lumi run658 date: 25/10/94 Collision time: 7:50:50 - 9:37:42 Currents (mkA): Ie= 27400.00, Ip= 32500.00 Peak luminosity: 1060.684 mb-1 s-1 Peak spec.lumi : 234.695393 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 5594.6773 mkb-1 H1 Run total lumi: 5254.807102 mkb-1 H1 data taken lumi: 4823.586059 mkb-1 H1 Runs: 89974 - 89982 HERA - physics: 4482.647924 mkb-1 H1Run - physics: 4069.839179 mkb-1 H1data - physics: 3660.924441 mkb-1 H1 Runs: 89975 - 89982 Tot curr/rate factor: 0.68% C/R F H1Run gated: 0.7% Rand.C.F: 1.45% RCF Run gated: 1.45% Relative ET trigg accept.: 0.4894 PS(LNS): Too little of info ... 26/10/94 ============== Schlief/Smirnov === Lumi RUN# 659 Start lumi run659 date: 25/10/94 Collision time: 15:41:06 - 1:23:28 Currents (mkA): Ie= 24200.00, Ip= 46600.00 Peak luminosity: 1335.156 mb-1 s-1 Peak spec.lumi : 322.881186 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 30947.823454 mkb-1 H1 Run total lumi: 29306.4787 mkb-1 H1 data taken lumi: 27881.2606 mkb-1 H1 Runs: 90004 - 90017 HERA - physics: 29582.469155 mkb-1 H1Run - physics: 27752.89979 mkb-1 H1data - physics: 26357.273849 mkb-1 H1 Runs: 90006 - 90017 Tot curr/rate factor: 0.38% C/R F H1Run gated: 0.39% Rand.C.F: 0.54% RCF Run gated: 0.55% Relative ET trigg accept.: 0.4972 PS(LNS): for R90003, Nev~93k: L4 absent, L5 are OK., PS(LNS): for R90012, Nev~56k: L4 absent, L5 are OK., 26/10/94 ================== Niedzballa === Lumi RUN# 660 Start lumi run660 date: 26/10/94 Collision time: 3:41:37 - 4:49:55 Currents (mkA): Ie= 29681.00, Ip= 43001.00 Peak luminosity: 1587.492 mb-1 s-1 Peak spec.lumi : 236.082688 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 5344.14894 mkb-1 H1 Run total lumi: 4922.2148 mkb-1 H1 data taken lumi: 4548.4315 mkb-1 H1 Runs: 90023 - 90027 HERA - physics: 4591.246142 mkb-1 H1Run - physics: 3912.438641 mkb-1 H1data - physics: 3583.12382 mkb-1 H1 Runs: 90024 - 90027 Tot curr/rate factor: 0.81% C/R F H1Run gated: 0.81% Rand.C.F: 1.79% RCF Run gated: 1.8% Relative ET trigg accept.: 0.4976 PS(LNS): None of L4/L5 info ... 27.10.1994 ===== dice2 ======== H1KFOM === Relation Coeff.Set 10B Today it was made attempt to produce Rel.Coeff.Set for 10B (low p11) data sample (from H1 Run 89264 up to Run 89877).It were selected 52813 ET&PD&nVC events from this H1 Run range from data set (only G- and M- labeled H1 Runs at H1EP): H1KFOM.ETPDNVC.M124129.C00 K20120 78048081 00001 ACS-E-C After all high mentioned 'cleaning' of 10B(low p11)data samples it were collected: 52813 events with ET&PD&nVC trigger 68809 events with ET&PD&VC trigger 31003 events with S92-trigger (PD&nVC-events). It were got 52813 ET&PD&nVC from these Runs and it were used for calibration 21331 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 0.937 1.039 0.880 0.917 0.786 0.923 0.781 0.969 0.916 0.875 0.864 1.122 0.889 0.975 1.278 0.878 1.009 0.905 0.925 1.037 0.867 1.025 1.019 1.011 1.004 1.028 0.977 0.990 0.983 1.106 0.931 0.994 0.965 1.021 0.938 1.025 0.999 0.859 0.889 0.954 0.967 0.916 0.934 0.882 0.986 0.453 0.874 0.947 0.000 ==> Relation Coeff.Set for PD 1.303 0.992 1.071 1.341 1.329 1.062 1.041 1.016 1.041 0.947 0.967 1.039 1.022 1.014 1.004 1.133 0.985 0.974 1.000 1.137 0.916 1.032 1.055 1.387 1.313 ==> Sig. at Relation Coeff.Set for ET 0.003 0.009 0.023 0.030 0.016 0.020 0.017 0.012 0.014 0.028 0.063 0.022 0.022 0.014 0.041 0.048 0.079 0.016 0.045 0.096 0.054 0.016 0.017 0.016 0.015 0.027 0.026 0.017 0.032 0.022 0.010 0.016 0.014 0.021 0.048 0.002 0.038 0.035 0.017 0.039 0.004 0.003 0.000 0.005 0.002 0.001 0.000 0.000 0.000 ==> Sig. at Relation Coeff.Set for PD 0.064 0.018 0.009 0.030 0.000 0.017 0.019 0.027 0.013 0.009 0.027 0.028 0.021 0.050 0.033 0.030 0.018 0.025 0.040 0.035 0.076 0.022 0.022 0.048 0.000 ==> Ent. at Relation Coeff.Set for ET 3 22 5 7 16 16 7 13 50 66 64 105 53 39 1315 369 332 329 348 610 199 5655 8758 7201 5710 4939 3924 1733 2044 3499 2397 2186 1698 1353 664 25 4 7 7 3 5 2 1 4 3 3 1 1 0 ==> Ent. at Relation Coeff.Set for PD 34 16 27 24 1 900 5101 4427 712 35 6200 17203 12986 2326 87 1645 4350 1691 232 13 14 22 25 8 1 As You can see all sigma values for 'hot' H1Lumi cahnnels RC histos have more ore less reasonable values. Runs 89264-89877 (ET&PD&nVC-sample - near 53.0K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.42 1.04 27.46 1.01 27.46 1.01 Runs 89264-89877 (ET&PD&VC-sample - near 69.0K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.83 1.48 27.74 1.45 As start values of Calibration Coefficients for Photoproduction Branch were got ones after 3rd step of calibration with ET&PD&nVC events from 9C-sample (H1 Runs 88877-89264 - near 109.0 K events). CCvcs value was got from last VCs calibration at 10A-sample of ETPDVC events (H1Runs 88877-89264 - see message from 21.10.94 at LL10). (CCvcs start = 4.645 MeV/FADCcount). Attempt to make fit of PhotonArm Energy spectrum was not enough succesful (with enough good statistics). 27.10.1994 ===== dice2 ======== H1KFOM === PDREC-spectra for 10B Today it were produced 100th ntuple for S92=1 events from earlier mentioned 10B-sample with events from Runs 88877-89264: H1KFOM.YLOOKQ4.R89264 (25823 entries) FAST09 3010200E 00000 DASD At interactive LOOK-session it was produced 70th histo for this data set and written into the next LOOK-binary data set: H1KFOM.BLOOKQ2.R89264 15006 entries in 70h FAST12 3010200E 00000 DASD First attempt to fit 70th histo at BLOOKQ2-data set put negative sign of Global Energy Shift at Photon Arm (-3.5%) and a little better then at 10A sample resolution digits (21-23%) for (12-20)-35GeV regions. It were prepared 100th tuples with ET&PD&nVC and ET&PD&VC-events for procedure of defining Global Energy Shifts and CCvcs: H1KFOM.YLOOKQ2.R89264 52257 entries FAST04 3010200E 00000 DASD H1KFOM.YLOOKQ3.R89264 63094 entries FAST08 3010200E 00000 DASD 27.10.1994 ==================== H1KFOM === Global Shifts,CCvcs 10B It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 1.035 for PD Channels (exept VCs), 0.9760 for ET channels. Correction factor for CCvcs is 0.897. So CCvcs = 4.645*0.897 =4.167Mev FADCcount. These digits are valid for H1Lumi events from Run 89264 up to 89877 Runs 89264- 89877 (ET&PD&nVC-sample - near 53.0K events) xetcut&vcdepcut Step Mean Sigma 0 27.52 1.01 Runs 89264- 89877 (ET&PD&VC-sample - near 69.0K events) xetcut Step Mean Sigma 0 27.51 1.36 P.S. CCp11 was the same almost as at 9C-samples. CCe19 was the same almost as at 9C-samples. CCvcs(averaging) was decremented on 10%. For any case - this is the final values of CC at Photoproduction branch after 3rd step of calibration with 10B-data sample (H1 Runs 89246-89877): ==> ET Calibr.Coefficients Final Status e00= 4.139 4.598 4.199 3.408 4.051 2.995 3.329 4.413 3.935 4.008 2.101 6.027 4.083 3.973 6.604 2.538 4.363 4.876 4.438 10.334 4.623 7.463 5.028 5.667 4.931 4.252 4.848 4.274 4.219 5.549 4.498 4.300 5.033 5.019 3.032 4.513 4.656 3.435 3.727 4.451 4.344 4.021 e42= 4.094 3.875 4.318 1.952 3.719 4.147 4.018 ==> PD & VC Calibr.Coefficients Final Status p00= 2.093 1.495 1.429 2.385 2.576 1.297 2.643 2.933 2.154 1.654 2.228 4.972 3.164 3.126 2.029 2.331 2.027 2.621 2.973 2.469 p20= 1.284 1.628 2.143 3.089 2.549 vcs= 4.167 27.10.1994 ==================== H1KFOM === New RC Sets in H1DataBase As final action of all 27.10.94 calibration steps it was made update of LFRC and LESC banks at H1DataBase with S.Levonyan's tool. All Relation Coefficients values, CCvcs and Global Energy Shift constants were got from the next messages at LLO: 27.10.1994 ----- dice2 -------- H1KFOM --- Relation Coeff.Set 10B 27.10.1994 -------------------- H1KFOM --- Global Shifts,CCvcs 10B Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LFRC (_501) 48 e-p data 410270731 89264 0 77 941027 H1KFOM Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LESC (_582) 56 e-p data 410270731 89264 0 3 941027 H1KFOM 27/10/94 ====================== Smirnov === Lumi RUN# 661 Start lumi run661 date: 27/10/94 Collision time: 2:58:03 - 7:54:07 Currents (mkA): Ie= 28540.00, Ip= 50400.00 Peak luminosity: 3628.405 mb-1 s-1 Peak spec.lumi : 496.353074 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 28936.263366 mkb-1 H1 Run total lumi: 27063.4744 mkb-1 H1 data taken lumi: 24103.7088 mkb-1 H1 Runs: 90100 - 90111 HERA - physics: 27184.948254 mkb-1 H1Run - physics: 24877.332953 mkb-1 H1data - physics: 22081.812481 mkb-1 H1 Runs: 90101 - 90111 Tot curr/rate factor: 0.14% C/R F H1Run gated: 0.15% Rand.C.F: 1.05% RCF Run gated: 1.06% Relative ET trigg accept.: 0.4570 PS(LNS): for R90101, Nev~50k: L4 and L5 are ~ OK; E_Etag became much better, peaking at ~ 18 GeV; A Little Warning: Edep-Etrig(PD) -> again the 2-nd reak at ~+1. 27/10/94 ====================== Wagener === Lumi RUN# 662 Start lumi run662 date: 27/10/94 Collision time: 17:42:09 - 22:15:25 Currents (mkA): Ie= 27512.00, Ip= 42700.00 Peak luminosity: 3103.848 mb-1 s-1 Peak spec.lumi : 501.752988 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 36681.539127 mkb-1 H1 Run total lumi: 35298.455 mkb-1 H1 data taken lumi: 31159.3857 mkb-1 H1 Runs: 90151 - 90164 HERA - physics: 34765.708814 mkb-1 H1Run - physics: 33312.77623 mkb-1 H1data - physics: 29261.669231 mkb-1 H1 Runs: 90152 - 90164 Tot curr/rate factor: 0.41% C/R F H1Run gated: 0.42% Rand.C.F: 1.16% RCF Run gated: 1.16% Relative ET trigg accept.: 0.4676 PS (S.L.) During this lumi run there was a famous "Brinkmann's" scan performed once again. First if was done in ZEUS IP without changes at H1, and then (at ~20:30 till ~21:30, H1 run 90160) at H1 IP without changes in ZEUS. That time we asked to make a "wider" scan (at least ~2 sigmas in x- and y- planes). SHOWLUMI picture showed 4 big dips in the trigger rate and luminosity, ~ in 7 times from max to min values. This corresponds to a full scan in 2 planes. More detailed study of various rates will be possible after the corresponding H1TCL file will be completed and created by the logging job. PS(LNS): for R90152: L4 and L5 are OK.; E_Etag peak is at ~ 18 GeV; h1ep: 90152 | 67.6K |15623.8 | (*M) | phase 2, all in readout ps(au) h1scan was started at 20:58 (x-scan) and 21:25 (y-scan), then ZEUS was scanned. At the end of the last e-beam was lost. dx,mm Lsp*E-29 dy,mm Lsp*E-29 -0.103 4.70 -0.000 4.78 -0.202 4.34 -0.0196 4.48 -0.301 3.75 -0.0400 3.80 -0.385 3.06 -0.0499 4.45 <== ?? -0.503 2.28 -0.0595 3.05 -0.600 1.63 -0.0797 2.20 -0.703 1.07 -0.1002 1.41 -0.759 0.69 -0.1199 0.85 0.101 4.32 0.0203 4.68 0.199 3.66 0.0409 4.22 0.305 2.93 0.0601 3.53 0.403 2.25 0.0802 2.76 0.499 1.69 0.1003 1.93 0.598 1.18 0.1207 1.22 0.704 0.76 0.1405 0.82 0.009 4.72 Axes - HERA coordinates. Correction to this values should be done in accordance of DESY HERA TN 94-03 28/10/94 ====================== Wagener === Lumi RUN# 663 Start lumi run663 date: 27/10/94 Collision time: 23:42:14 - 10:32:50 Currents (mkA): Ie= 25593.00, Ip= 41500.00 Peak luminosity: 2503.026 mb-1 s-1 Peak spec.lumi : 450.465587 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 54585.239119 mkb-1 H1 Run total lumi: 49553.7822 mkb-1 H1 data taken lumi: 40847.2658 mkb-1 H1 Runs: 90169 - 90217 HERA - physics: 53057.69772 mkb-1 H1Run - physics: 47661.007109 mkb-1 H1data - physics: 39034.104761 mkb-1 H1 Runs: 90170 - 90217 Tot curr/rate factor: 0.27% C/R F H1Run gated: 0.29% Rand.C.F: 0.8% RCF Run gated: 0.81% Relative ET trigg accept.: 0.4913 PS(LNS): R90175 | 39.8K | 4561.6 | (*G) | phase 3 => L4/L5 are absent PS(LNS): R90202 | 34.9K | 2390.8 | (*G) | phase 4 => L4 OK, L5 absent PS(LNS): A little warning: L4 ET=f(#) has a little changed. 29/10/94 ====================== Smirnov === Lumi RUN# 664 Start lumi run664 date: 28/10/94 Collision time: 15:39:10 - 3:49:46 Currents (mkA): Ie= 29525.00, Ip= 39600.00 Peak luminosity: 3076.685 mb-1 s-1 Peak spec.lumi : 506.982141 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 67175.837579 mkb-1 H1 Run total lumi: 60881.0558 mkb-1 H1 data taken lumi: 49993.6127 mkb-1 H1 Runs: 90231 - 90260 HERA - physics: 65277.142542 mkb-1 H1Run - physics: 60599.0326 mkb-1 H1data - physics: 49733.7323 mkb-1 H1 Runs: 90232 - 90260 Tot curr/rate factor: 0.37% C/R F H1Run gated: 0.37% Rand.C.F: 1.04% RCF Run gated: 1.01% Relative ET trigg accept.: 0.4915 PS(LNS): for R90250, Nev~66k: L4 are OK, L5 are OK; PS(LNS):h1ep: 90250 | 66.8K | 5352.8 | (*G) | phase 4 29/10/94 ============== Wagener/Schleif === Lumi RUN# 665 Start lumi run665 date: 29/10/94 Collision time: 5:28:30 - 15:52:19 Currents (mkA): Ie= 24116.00, Ip= 36600.00 Peak luminosity: 1697.404 mb-1 s-1 Peak spec.lumi : 368.49875 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 39390.590617 mkb-1 H1 Run total lumi: 36705.202571 mkb-1 H1 data taken lumi: 31140.204875 mkb-1 H1 Runs: 90262 - 90295 HERA - physics: 37748.43146 mkb-1 H1Run - physics: 34793.100599 mkb-1 H1data - physics: 29267.870602 mkb-1 H1 Runs: 90263 - 90295 Tot curr/rate factor: 0.31% C/R F H1Run gated: 0.33% Rand.C.F: 0.75% RCF Run gated: 0.76% Relative ET trigg accept.: 0.4946 PS(LNS): for R90273, Nev~88k: L4 are absent, L5 are ~ OK; PS(LNS):h1ep: 90273 | 88.4K | 6679.7 | (*G) | phase 4 29.10.1994 ==================== H01GOG === LUMIMON data processing Here is a continuation of a summary table for e+p LUMIMON files, processed so far. ---------------------------------------------------------------------- File H1 runs Events Actual triggers (xx) s86 s91 s92 s93 s94 s95 ---------------------------------------------------------------------- 124 89264-89414 128150 9651 5322 6767 7945 8901 9259 125 89414-89456 128264 8307 4498 5577 6563 7182 7919 126 89456-89515 128569 11252 4207 5172 6253 6672 7391 127 89515-89721 129172 12521 3974 4426 6728 5281 6690 128 89721-89830 129338 10880 4508 4556 8650 5111 7290 129 89830-89877 129673 8319 4050 4024 8267 4360 6610 130 89877-90008 129261 18311 4083 4857 6691 5194 6586 131 90008-90013 130078 4739 783 1070 1047 1170 1384 132 90013-90162 129692 13518 3004 3768 4457 4108 5082 133 90162-90236 129126 10458 4178 4667 6919 5628 7245 134 90236-90263 128904 11112 4244 4829 6898 5972 7380 135 90263-90305 129150 12343 4236 4659 7216 5700 7319 ---------------------------------------------------------------------- 29/10/94 ====================== Smirnov === Lumi RUN# 666 Start lumi run666 date: 29/10/94 Collision time: 20:44:59 - 21:33:28 Currents (mkA): Ie= 27960.00, Ip= 38801.00 Peak luminosity: 2217.671 mb-1 s-1 Peak spec.lumi : 431.147337 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 4573.192449 mkb-1 H1 Run total lumi: 4447.0997 mkb-1 H1 data taken lumi: 4091.9421 mkb-1 H1 Runs: 90300 - 90301 HERA - physics: 3603.583772 mkb-1 H1Run - physics: 3042.448054 mkb-1 H1data - physics: 2725.288072 mkb-1 H1 Runs: 90301 - 90301 Tot curr/rate factor: 0.19% C/R F H1Run gated: 0.2% Rand.C.F: 1.75% RCF Run gated: 1.75% Relative ET trigg accept.: 0.4818 PS(LNS): Too low statistics. 30/10/94 ===================== Starosta === Lumi RUN# 667 Start lumi run667 date: 29/10/94 Collision time: 23:20:57 - 10:04:17 Currents (mkA): Ie= 26448.00, Ip= 38700.00 Peak luminosity: 1840.176 mb-1 s-1 Peak spec.lumi : 342.515022 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 46849.336702 mkb-1 H1 Run total lumi: 43945.4496 mkb-1 H1 data taken lumi: 37819.0093 mkb-1 H1 Runs: 90302 - 90325 HERA - physics: 45153.594208 mkb-1 H1Run - physics: 41872.736583 mkb-1 H1data - physics: 35787.418763 mkb-1 H1 Runs: 90303 - 90325 Tot curr/rate factor: 0.18% C/R F H1Run gated: 0.19% Rand.C.F: 0.95% RCF Run gated: 0.96% Relative ET trigg accept.: 0.4855 PS(LNS): for R90305, Nev~52k: L4 are absent, L5 are ~ OK; PS(LNS): h1ep:90305 | 52.2K | 6752.0 | (*G) | phase 3 30.10.1994 ==================== F11LEV === To Beam separation scan... Recently (see message from 27-Oct, PS by S.L. and A.U.) another attempt was made to measure specific luminosity by the beam separation scan method of Brinkmann. I assumed, that the position shift are correct (no further corrections to dx and dy are necessary). Only then the results of the scan can be compared to the online lumi measurements. In order to interpret the result of this measurement correctly, one needs to know, which beam was kept in a transverse plane without changes, and which (p or e+) was moved against another one. This information could be derived from LUMM rates,which are usually automatically available after H1TCL files processing. Unfortunately, the relevant file (99) was corrupted by the logging job and will need some time to be recreated. Before this is done I assume, that e+ was kept and p-beam was moved in x and y planes (as it is suggested by rough observation of SHOWLUMI figures). Then no ET-acceptance corrections are necessary and the gaussian fit of the data written by A.Usik (with one typing error? -- see mess. 27-Oct) gives: sigma_x* = 0.267 mm 6.5*10^25 cm-2s-1mA-2 sigma_y* = 0.0491 mm ==> L_sp = --------------------- = 4.96*10^29 sigma_x* * sigma_y* This has to be compared with the online measurement of L_sp(online) = (4.81+-0.03) * 10^29 I.e. (3.1+-0.6)% difference. Note, that offline correction is not yet done to this online Lumi. PS (S.L., 31-Oct) After the analysis of LUMM rates from raw data tapes I defined an effective beam sizes in H1 IP again: sigma_x*[mm] sigma_y*[mm] from L_sp 0.268 +- 0.001 0.0489 +- 0.0002 from ET*PD rates 0.266 +- 0.002 0.0491 +- 0.0004 from PD rates 0.266 +- 0.001 0.0491 +- 0.0002 PPS (S.L.) After conversation with R.Brinkmann, it became clear that: 1) p-beam was kept and e+ beam was moved in x-y plane 2) Raw dx, dy values given by Usik indeed need (5-10%) corrections (as A.U. wrote in his message) 3) R.Brinkmann's evaluation of the scan data had shown that the effective beam sizes at H1 IP was significantly (~10%) larger than in ZEUS IP, and therefore L_sp was lower. The reason was found to be a large crossing angle between e+ and p beams during last 5-6 days due to the wrong p-orbit (perhaps after beam steerings made for our Fwd.Muon system). When this was identified and corrected, L_sp at H1 and ZEUS IP became practically equal. 4) ZEUS online lumi measurements during this last scan was in very good agreement with machine expectations from the beam sizes at their IP. 31/10/94 ===================== Starosta === Lumi RUN# 668 Start lumi run668 date: 30/10/94 Collision time: 21:00:42 - 0:38:46 Currents (mkA): Ie= 29400.00, Ip= 47700.00 Peak luminosity: 3331.685 mb-1 s-1 Peak spec.lumi : 462.336547 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 32992.1909 mkb-1 H1 Run total lumi: 17859.8856 mkb-1 H1 data taken lumi: 14957.8707 mkb-1 H1 Runs: 90342 - 90360 HERA - physics: 30560.119293 mkb-1 H1Run - physics: 15394.036677 mkb-1 H1data - physics: 12605.124236 mkb-1 H1 Runs: 90345 - 90360 Tot curr/rate factor: 0.1% C/R F H1Run gated: 0.14% Rand.C.F: 1.33% RCF Run gated: 1.46% Relative ET trigg accept.: 0.4718 PS(LNS): Too low statistics at L4/L5. 31/10/94 ======================= Martin === Lumi RUN# 669 Start lumi run669 date: 31/10/94 Collision time: 2:00:10 - 13:19:17 Currents (mkA): Ie= 23964.00, Ip= 47300.00 Peak luminosity: 2570.092 mb-1 s-1 Peak spec.lumi : 431.421828 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 60179.907805 mkb-1 H1 Run total lumi: 55051.319315 mkb-1 H1 data taken lumi: 46113.119164 mkb-1 H1 Runs: 90361 - 90392 HERA - physics: 58326.12419 mkb-1 H1Run - physics: 53286.779015 mkb-1 H1data - physics: 44371.092364 mkb-1 H1 Runs: 90363 - 90392 Tot curr/rate factor: 0.18% C/R F H1Run gated: 0.19% Rand.C.F: 0.71% RCF Run gated: 0.71% Relative ET trigg accept.: 0.5007 31/10/94 ======================= H.Jung === Lumi RUN# 670 Start lumi run670 date: 31/10/94 Collision time: 17:48:01 - 17:49:29 Currents (mkA): Ie= 28402.00, Ip= 44400.00 Peak luminosity: 451.358 mb-1 s-1 Peak spec.lumi : 0 mb-1 s-1 mA-2 Number of collided b.: 0 Number of e-filled b.: 0 Number of p-filled b.: 170 Number of e-pilot b.: 0 Number of p-pilot b.: 170 HERA total lumi: 13.557896 mkb-1 H1 Run total lumi: 13.557896 mkb-1 H1 data taken lumi: 13.482034 mkb-1 H1 Runs: 90404 - 90404 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 90404 - 90404 Tot curr/rate factor: -0.05% C/R F H1Run gated: -0.05% Rand.C.F: 5.25% RCF Run gated: 5.25% Relative ET trigg accept.: Not calc. 31.10.1994 ===================== F11LEV === New e-tagger at 44m ...... The drawings are ready for the modified beam pipe at ~44m to install new small electron tagger there. It is sketched below. The copy of the drawing I will give to E.Malinovsky. ------------------------------------------------------------------- ..................................................e-beam -->....... ^ : : r = 26 mm R = 41 mm __________:_________________ : /: :\ ______V__________/ : : \__________________ : : :<-------- 559 mm -------->: 1/11/94 ======================== H.Jung === Lumi RUN# 671 Start lumi run671 date: 31/10/94 Collision time: 19:03:11 - 5:46:44 Currents (mkA): Ie= 28323.00, Ip= 44200.00 Peak luminosity: 1979.031 mb-1 s-1 Peak spec.lumi : 313.539464 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 17 HERA total lumi: 45965.306617 mkb-1 H1 Run total lumi: 43604.2208 mkb-1 H1 data taken lumi: 34688.5212 mkb-1 H1 Runs: 90404 - 90420 HERA - physics: 43106.131713 mkb-1 H1Run - physics: 40320.1262 mkb-1 H1data - physics: 31563.0045 mkb-1 H1 Runs: 90406 - 90419 Tot curr/rate factor: 0.48% C/R F H1Run gated: 0.49% Rand.C.F: 1.03% RCF Run gated: 1.04% Relative ET trigg accept.: 0.4775 PS(LNS): for R90408, Nev~57k: L4 are OK, L5 are OK; PS(LNS):h1ep: 90408 | 57.2K | 8521.7 | (*G) | phase 2 01.11.1994 ===================== F11LEV === End of LUMI-1994 ! ....... Today at ~6 a.m. the luminosity run of 1994 was successfully finished. HERA has delivered to H1 almost 6 pb-1 of (e- + e+)p data (as measured online). A final statistics will come later today, after all last runs appear in the database. 01.11.1994 ===================== H01GOG === Final LUMI-1994 statistics A final luminosity values and related statistics are summarized below: L (HERA-tot.): 5.916 pb-1 L (HERA-phys): 5.510 pb-1 L (H1-runs ): 4.825 pb-1 L (H1-gated): 4.042 nb-1 L (H1-phys.): 3.917 pb-1 = 0.493 (e-p) + 3.359 (e+p,IP=0.0cm) + 0.065 (E+p,IP=+65cm) An average offline corrections to the online Lumi measurements are (preliminary): (+8.4+-1.6)% for e-p and (-8.0+-1.4)% for e+p data. ------------ ----------- The correction was obtained analysing s91 monitoring events from all G+M runs in 1994. The errors quoted above include: - statistical errors (from # of s91 events with E_gamma>12GeV) - energy scale + resolution of gamma arm after final calibration - precision of the geometrical acceptance of PD (~0.7%) - e-gas background subtraction error (~1%) - double photons in the same bunch for "PD-only" method More detailed tables (as invented by S.Levonian): _______________________________________________________________ | | | | | ep-collisions 94: (22/05-17/07) | | --------------------------------- | | | | HERA ep-collisions: 116 (375-502) | | Permanent H1-runs: 1141 (76345 - 82005) | | : 1115 sec | | | | L (HERA-tot.): 938.21 nb-1 matrix [%] | | L (HERA-phys): 846.21 nb-1 90 | | L (H1-runs ): 714.23 nb-1 76 84 | | L (H1-gated): 532.03 nb-1 57 63 74 | | L (H1-phys.): 492.51 nb-1 52 58 69 93 | | | | G : 420.05 nb-1 | | M : 72.45 nb-1 | | P : 39.13 nb-1 | | ? : 0.41 nb-1 (not classified in H1EP) | | | | Peak lumi: 2.4 * 10**30 cm-2s-1 (05/07) | | | | Currents: = 28.55 mA (I_max = 47.0 mA) | | = 10.49 mA (I_max = 29.4 mA) | | | | Bunches: 153*153 + 15(e) + 17(p) | |_____________________________________________________________| _______________________________________________________________ | | | | | e+p-collisions 94: (28/07-01/11) | | --------------------------------- | | | | HERA ep-collisions: 169 (503-671) | | Permanent H1-runs: 1816 (82961 - 90419) | | : 1620 sec | | | | L (HERA-tot.): 4977.43 nb-1 matrix [%] | | L (HERA-phys): 4664.58 nb-1 94 | | L (H1-runs ): 4111.74 nb-1 82 88 | | L (H1-gated): 3509.62 nb-1 70 75 85 | | L (H1-phys.): 3424.00 nb-1 68 73 83 98 | | | | G : 2873.43 nb-1 | | M : 550.57 nb-1 | | P : 85.43 nb-1 | | ? : 0.19 nb-1 (not classified in H1EP) | | | | Peak lumi: 4.3 * 10**30 cm-2s-1 (16/08) | | | | Currents: = 41.02 mA (I_max = 53.8 mA) | | = 17.00 mA (I_max = 30.9 mA) | | | | Bunches: 153*153 + 15(e) + 17(p) | |_____________________________________________________________| _______________________________________________________________ | | | | | shifted IP e+p-collisions 94: (24/10-26/10) | | -------------------------------------------- | | | | HERA ep-collisions: 7 (654-660) | | Permanent H1-runs: 40 (89929 - 90026) | | : 1721 sec | | | | L (HERA-tot.): 85.79 nb-1 matrix [%] | | L (HERA-phys): 78.33 nb-1 91 | | L (H1-runs ): 71.67 nb-1 84 91 | | L (H1-gated): 67.38 nb-1 79 86 94 | | L (H1-phys.): 64.98 nb-1 76 83 91 96 | | | | G : 59.76 nb-1 | | M : 5.22 nb-1 | | P : 2.40 nb-1 | | ? : 0.00 nb-1 (not classified in H1EP) | | | | Peak lumi: 2.1 * 10**30 cm-2s-1 (24/10) | | | | Currents: = 41.17 mA (I_max = 46.2 mA) | | = 16.78 mA (I_max = 28.9 mA) | | | | Bunches: 153*153 + 15(e) + 17(p) | |_____________________________________________________________| Remarks: 1) All values represent online measurements corrected only for counting errors, but not for the: o satellite bunches effect o absolute normalization o detailed detector status (HV, LAr noise, ...) 2) Max H1run lumi = 17.899712 nb-1 in run 89256 Definitions: L (HERA-tot.): Total HERA lumi produced at final beam energies L (HERA-phys): HERA lumi delivered for physics (during LUMI runs) L (H1-runs ) : HERA lumi during H1 runs (H1 run gated luminosity) L (H1-gated) : H1 data taken luminosity (dead time corrected) L (H1-phys.) : H1 gated lumi, useful for physics analysis (G+M) 01.11.1994 ==================== H01LNS === Proposal for LLO LRS ===== A single proposal for the Shutdown: To make more informational The Lumi-Run-Summary at the LPI LLO. Motivation in a form of Critics: 1. The Lumi-Run-Summary (LRS) has not been changed for a long time; 2. The main LRS defect - the Contents is connected mostly to ON-line; 3. OFF-line is seen randomly, as some PS's, or as some Replacements; 4. Sometimes, at H1 there is a number of contradictory Lumi sources; 5. Often in the past, there were contradictions of LRS and Displays; 6. For ON-line itself, the tradittional values are not well named; 7. The new ON-line values (by I.P.Sh.) are named as a puzzle; 8. There is no splitting of the "LUMI#-Run" into "Standard" N-Runs; 9. The format of LRS is waisting of space, not suitable for "find". Motivation in a form of Targets: 1. The LRS of LPI should become more informational and more suitable; 2. It should get such a high status as the other H1 (Run) Summaries; 3. It should become "a Reference" to solve the Lumi contradictions. Some ways to improove the LRS: 1. Adding of OFF-line information - the corrections,final values,etc; 2. As a final target, OFF-line updating should be done automaticly; 3. Comparing and unificating of all H1(!) sources of the Lumi values; 4. Improoving (and referency!) of the used names for all the values; 5. Adding of information on the single Runs in the frame of Lumi#Run; 6. Adding of information that is summing up the values (in every LRS) 7. Trying to improove the format, esp, for using of "find" command; 8. Trying to unify the formats of a regular LRS and a super-summary; 9. I think that such an upgraded LRS should become a separated file. Having written this list, I saw, that it is hardly to be realized in the main - the OFF-line updating. Then I read S.L.'s LLO above. Sorry, Lollii N. Shtarkov, Moscow, Pitomnik, 01.11.1994 01.11.1994 ===================== F11LEV === LUMI run summaries ....... There was recently some progress made, getting online Lumi information publically available and automatically updated. This was done in the framework of H1 Unix tools by A.Usik. See DQ minutes of J.Olsson. Try for more details LUMIINFO command on dice2 and then several further options described in it. Proposals for the improvement of this new tool should be directed to the author (A.Usik) 01.11.1994 ==================== H01GOG === LUMIMON data processing Two last (but one) LUMIMON files: ---------------------------------------------------------------------- File H1 runs Events Actual triggers (xx) s86 s91 s92 s93 s94 s95 ---------------------------------------------------------------------- 136 90305-90359 128878 11467 4567 5034 7772 6140 7932 137 90359-90408 129111 12387 3742 4484 5663 5362 6480 ---------------------------------------------------------------------- Few still missing H1 e+p runs (90409-90419) will come later when the last LUMIMON file will be completed.