C 2/06/93 408091440 MEMBER NAME EDITFILE (CLIST) M *********************************************************************** * * * PART 9 PART 9 * * H1 LUMI LOGBOOK * * * * ep DATA TAKING MAY-JULY 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 * * * * S.Levonian Opened: 21/05/94 at 21:00 * * Closed: 27/07/94 at 16:00 * * * *********************************************************************** 21.05.1994 ==================== F11LEV === New Chapter of the logbook This message opens a new part of the LUMI Logbook. You can inspect earlier parts by the commands LL1-LL8, where LL8 = LIST 'F11LEV.H1.LUMI.LOGBOOK.PART08' 21.05.1994 ==================== F11LEV === Where is lumi information? Last year we had a standard format for run summaries, see example below It was critisized (occupies too much space and makes a search of the important messages difficult). However, it was important, and proven to be very useful. At some moment it was decided (or proposed) to split this information in a different file. But not to drop it! So, my question is: where one can find now the following data: ??? Start lumi run 160 date: 1/7/93 Collision time: 0:51:27 - 4:04:28 Currents (mkA): Ie= 7762.00, Ip= 3300.00 Peak luminosity: 207.55752 mb-1 s-1 Peak spec.lumi : 274.372054 mb-1 s-1 mA-2 Number of collided bunches: 30 Pilot bunch: 17 HERA total lumi: 1607.997814 mkb-1 H1 Run total lumi: 1258.106305 mkb-1 H1 data taken lumi: 812.1153 mkb-1 H1 Runs: 51389 - 51420 HERA - physics: 759.135061 mkb-1 H1Run - physics: 477.585051 mkb-1 H1data - physics: 209.832626 mkb-1 H1 Runs: 51394 - 51420 21.05.1994 ==================== F11LEV === New lumi bank in DB....... On the experience of the last year data analysis it was decided to create another bank with more detailed lumi history: now our measurements for each 10 sec will be stored in the DB in a compressed format: TABLE LH1T B32 ! Lumi table for H1 ep-runs ! (typically, one row per 10 sec.) ! ATTributes: ! ----------- !COL ATT-name FMT Min Max ! Comments ! 1 RTIME I 0 +INF ! total time from run start (msec) 2 ATIME I 0 +INF ! active time from run start (msec) 3 ILUMI I 0 +INF ! H1 gated lumi since run start (mb^-1) 4 POLAR I 0 1000 ! current polarization value (0.1%) 5 SCW1 I -INF +INF ! slow control word 1 from HEAR 6 SCW2 I -INF +INF ! slow control word 2 from HEAR END TABLE A tool creating this bank is ready and will be installed in SGI logging job as soon as data logging experts are around. An old bank LH1R still will be created as before. Note, that unlike last year, an integrated lumi for the database will ALWAYS be RECALCULATED using rates ifrom LRTL and currents from TCUR. Only if TCUR is not available, a LUMI from LRTL will be used directly. This is done to avoid errors due to the possible problems with current transmission from CTRIG to the online LUMI branch. P.S. LH1T bank is officially described in H1BANKS cmz file. Also the descriptions of other banks have been added or modified to reflect the present status of the system. Bank formats can be inquired by the command 'LHB name' at IBM, where 'name' is bank name. A complete list of all LUMI banks is given below. Please inform me if anything there is still missing or obsolete. LUMI system BOS bank list (status 21-May-1994) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ type name format MC/data DB content ---------------------------------------------------------------------- TABLE LESC D + ! Lumi detector's Energy SCale TABLE LETR M D ! Lumi_Electron_Tagger_Reconstruction TABLE LFRC D + ! Lumi_FADC_Relation_Coefficients TABLE LH1R I D + ! Lumi information for the run TABLE LH1T I D + ! Lumi information (1 row per 10 sec) TABLE LPDR M D ! Lumi_Photon_Detector_Reconstruction TABLE LREC I D + ! Lumi_Response_ET_CC_old TABLE LREE B16 M D ! Lumi_Response_ET_Event (digi bank) TABLE LREF B16 D ! Lumi_Response_ET_Fadc TABLE LREP B16 D ! Lumi_Response_ET_CC_perm TABLE LRET B16 M ! Lumi_Response_ET_Track (hit bank) TABLE LRPC I D + ! Lumi_Response_PD_CC_old TABLE LRPE B16 M D ! Lumi_Response_PD_Event (digi bank) TABLE LRPF B16 D ! Lumi_Response_PD_Fadc TABLE LRPP B16 D ! Lumi_Response_PD_CC_perm TABLE LRPT B16 M ! Lumi_Response_PD_Track (hit bank) TABLE LRTE B16 M ! Lumi_Response_Trigger_Event data TABLE LRTF B16 D ! Lumi_Response_Trigger_sums_FADCs TABLE LRTL B32 D ! Lumi_Response_Trigger_Luminosity TABLE LRTN B32 D ! Lumi_Response_Trigger_moNitoring TABLE LRTS B32 D ! Lumi_Response_Trigger_Statistics TABLE LRVT B16 M ! Lumi_Response_VC_Track (hit bank) TABLE LRXY M D ! Lumi_Reconstruction_XY_coordinates TABLE LS M ! Starting particle tracks for LUMI TABLE LUMM B32 D ! LUmi_Measurements by various Methods BANK LUTR B32 D + ! LUmi_TRigger setting ---------------------------------------------------------------------- 21.05.1994 ==================== F11LEV === SHOWLUMI ................. LOOK command SHOWLUMI to display luminosity history for the last few hours will from now on refer to the H1LUMI file resided on dice2. After discussion with experts it was decided NOT to transfer this file on IBM. As a consequence, those users wanted to access this information from IBM (or any machine other than dice2) have to have a special NETRC file, containing userid and password for dice2. On DESY IBM this file must have a name: userid.PER.NETRC (PER needed to protect this information) and a 3-line content: machine dice2 login ...... <--- replace dots by your userid on dice2 password ......... <--- replace dots by your password on dice2 If you run LOOK or H1ED locally on dice2, SHOWLUMI does not require any special files and acts exactly as before on IBM. 21.05.1994 ==================== F11LEV === Short and long term tasks It is useful once again to summarize most important tasks related to luminosity measurements and photoproduction tagging. Please see where you can and wish to contribute to the success of H1 LUMI group. 0) Improve stability and reliability of the online system. This I mainly mention, because of the too many complaints appeared last time in H1RUN reports: system crashes, CDAQ error mesasages, HV trips, etc. 1) Calibration procedure. We have in the moment very many steps, banks and data files to arrive finally to the precise absolute calibration of ET, PD and VC Not all of them are stable enough. In general too large efforts are needed each time to obtain correct CC. Therefore: procedure must be simplified as much as possible, and ideally fully automatized. 2) Data quality checks. Our system produces a lot of valuable data. The quality of those data directly influence almost ALL physics results in H1! Therefore, very serious attention must be paid to monitor and control the data quality regularly. Here also several automatic tools (in addition to the existing at L4/L5) are possible and needed. In more details the data are: o trigger efficiency, thresholds and timing o detector responce (noise, amplitude shapes, overflows) o background conditions and rates at ET, PD, VC o energy and coordinate spectra (related to calibration quality) o behaviour of physics triggers using eTAG element (see H1TRIG list) 3) Understand and implement different lumi estimates o basic ET*PD metod o cross check with ET*PD with limited ET acceptance (x_ET cuts) o gamma-arm estimates using various trigger rates o photon energy flow method For this all lumi monitoring events must me selected and analysed during the data taking (VC, ET*PD*!VC, ET*PD*VC, PD_low, ...) and not several months later. 4) A large study program on the extention of the tagging acceptance. o analyse response of our gas Cherenkov counter (reinstall it at first possibility as close to the e-beam axis as possible!) o calculate acceptance of the ET at possible positions between -90 and -175m downstream in the tunnel, and estimate rates of gamma-p signal and bremstrahlung background 21.05.1994 ==================== H01LNS === PDFIT BLOOKQ2.R73891 etc.. A.F. has updated BLOOKQ1 -> BLOOKQ2 for six (eGas) runs: R73981; R74115; R74116; R74117; R74397; R74403. The updated spectra BLOOKQ2 were PDFITted as (eGas) (!). The results were selected with (Probability > 1%) . Star(*) the next line for Fit results: LIST 'H01LNS.JPDFIT.R73981.R74403.BQ2' Pay attention to the (hidden) rightmost parts of the fit-results-lines. 22.05.1994 ==================== H1KFOM === Third Luminosity'94(374th) Tonight HERA p-beam injection started near 02:00 and was finished at 03:00 with Ip near 23.7 mA. Nothing from Ip current was lost during ramping. Number of bunches 170 with bunch structure: (10+1)*6 + (0+11) + (10+1)*6 + (0+5) + (10+1)*5. HERA e-beam injection started tonight at 04:25 and was finished at 05:00 with Ie near 15 mA. After succesful ramping and Luminosity tuning it was fixed maximal value of Luminosity at H1 IP as value near 8.8*10**29 cm-2s-1 with Specific Lumi near 5.0*10**29 cm-2s-1mA-2 at 05:20. It was started 3rd at this year Luminosity at H1 IP. Lumi Run was finished near 08:50 this morning. Standard actions for automatic filling of RunSummary was not made yet by H1 Lumi Shift Crew - only Movable platforms were put into Parking Positions and it were reseted Integrated Lumi Values (without fixing at RunSummaries). Yura before NH leaving after night shift made current picture keeping (at 08:06). At this time it were fixed the next Integral Lumi values: HERA Produced - 6.160 nb-1 H1 Run Gated - 5.132 nb-1 H1 Data Taken - 3.696 nb-1 Final HERA produced Luminosity Integral value was seen as value near 7.0 nb-1. No any information about H1RunGated anf H1DataTaken values. The next ep-collisions (4th) was fixed firstly at RunSummary - and I hope that soon at H1Lumi Logbook it must appear first standard record about ep-collisions (as S.Levonyan mentioned at one of his last messages at LLC). 22.05.1994 ==================== H1KFOM === Lumi Run #375 & H1LumiRun. I hope that this is the last non-standard report about ep-collisions. After e-beam dump near 09:00 the same p-beam was kept with Ip=23.1mA At 09:30 it was started new e-filling and at 10:05 Ie was collected as value near 20 mA. But this beam was lost. At 10:35 the next e-injection was started and was finished near 11:00 with value near 15 mA. After ramping and tuning of Luminosity the 4th Lumi Run was started near 11:12. Peak Luminosity value was fixed as value near 7.0*10**29 cm-2s-1 and Specific Lumi as 4.00*10**29 cm-2 s-1mA-2. It was started 375th ep-collisions at HERA history. Number of e-bunches -165. Bunch Structure is the next: (9+2)*13 + (3+2) + (9+2)*5 + (0+6) + (3+7) We have 150 collided bunches, 15 e-pilot bunches and 20 p-pilot bunches This Lumi Run (as it was decided earlier) was got for collimator studies - Luminosity Run was not proclaimed at HERA TV-screen. We asked to get 20 min of good ep-Run with enough high Luminosity for getting data for H1LumiCalibration with this new beam conditions. H1ShiftCrew after talking with HERA-people put to us this posibility. It was started H1 Run 76345 at 11:17 (Lumi=7.0*10**29) and was finished at 11:43. The set of subtriggers is the same as at all previous calibration Runs (s86 as PD1, s93 and s94).Thresholds the same as yesterday (PD=0.75, PD1=0.50, ET=5.5 etc.). HVvc the same as at yesterday Calibration Run. It were collected 146K events. During this Run Integrated Lumi was collected as 0.8 nb-1. 22.05.1994 ==================== H1KFOM === SHOWLUMI test at IBM...... I prepared H1KFOM.PER.NETRC-file as S.Levonyan recommended and go to LOOK-environment. After SHOWLUMI-command I got the next message: can't get addr for dice2 and *** after. After return - LUMIH1: Cannot access H1LUMI file P.S. (by S.Levonian) Something must be wrong with your NETRC file content, or maybe with your setting on dice2. I would then recommend to ask expert (Zbishek Szkutnik). When I try SHOWLUMI from LOOK at IBM, I get the following two messages (in a fortran window): "Connected to FPSERVER on dice2" "Connected to private server after 2 trials" So the connection is successful, however, no picture appears on the screen. The reason is - no LUMI data in the H1LUMI file on dice2. The reason for that is unclear for me and will be checked with logging job expert. 22.05.1994 ==================== H1KFOM === H1Lumi Trigger Setting.... Today at 14:20 we installed H1Lumi trigger elements as it was proposed at S.Levonian's mail (at Photoproduction branch) due to start of Prescale Gaps tuning for H1 Trigger Set'94: /* ------ TG o -------- Lumi/eTag -- TE 112-119 ---*/ #DEF Lum_int = o t0 Internal lumi bit (may vary) #DEF PD_low = o t1 Photon Detector low threshold #DEF Lcal = o t2 LUMI calibration trigger #DEF ElDet = o t3 #DEF PhotDet = o t4 #DEF WatVet = o t5 #DEF eTAG = o t6 #DEF NC = o t7 E(neutron calorimeter)>threshold Lum_int was installed on PD2 (before this it was PD1) PD_low PD1 (before this it was PD2) Lcal ET&PD&nVC (before this it was ET+PD) ElDet ET (not changed) PhotDet PD (not changed) WatVet VC (not chnaged) eTAG ET&nPD&nVC (before this it was PD1 at R76345) NC NC (not changed) At H1 Central Trigger the next subtriggers were found: s86 - eTAG s89 - eTAG&NC (made at H1 Central Trigger Logic from eTAG and NC) s91 - PD_low s92 - Lcal s93 - WatVet s94 - ET&PD&nVC (made at H1 Central Trigger Logic from ET,PD,VC) s95 - ET&PD&VC (made at H1 Central Trigger Logic from ET,PD,VC) 22.05.1994 ==================== H1KFOM === Lumi RUN# 375 ............ Start lumi run375 date: 22/5/94 Collision time: 11:08:29 - 16:09:43 Currents (mkA): Ie= 14200.00, Ip= 23300.00 Peak luminosity: 484.042 mb-1 s-1 Peak spec.lumi : 451.623136 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: 8095.502325 mkb-1 H1 Run total lumi: 6395.657375 mkb-1 H1 data taken lumi: 4749.25521 mkb-1 H1 Runs: 76342 - 76375 HERA - physics: 3019.821157 mkb-1 H1Run - physics: 1950.976072 mkb-1 H1data - physics: 699.959411 mkb-1 H1 Runs: 76349 - 76375 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.: 0.3309 P.S. after end of Lumi Run #375 ep-collisions were prolongated up to 16:56 (ZEUS request). Our Movable Platforms were moved into parking positions at 16:10. On the requst of H1 Shift crew Movable Platforms were moved into working positions again from 16:45 for some measurements. At 16:56 e-beam was dumped in with Ip=22.4mA it is preparing new e-filling. At 17:30 p-beam was lost during e-beam injection. 22.05.1994 ===== dice2 ======== H1KFOM === Relation Coefficients Set It was produced Relation Coefficients Set with ET&PD&nVC-events from data sample Run76345 (47569 events): ==> Relation Coeff.Set for ET 0.000 0.000 1.093 1.111 1.138 1.119 1.116 0.000 1.188 1.234 1.761 1.097 1.021 1.276 0.957 1.249 1.136 0.953 1.081 0.876 0.977 1.023 1.018 1.004 1.005 1.037 1.029 1.025 1.064 0.956 1.071 1.026 0.996 1.042 1.048 1.230 1.176 1.001 0.964 0.988 0.943 0.906 1.105 1.094 1.069 1.143 1.053 1.122 0.000 ==> Relation Coeff.Set for PD 1.134 1.244 1.356 1.034 0.000 1.116 0.983 0.978 1.003 0.975 0.962 1.034 1.002 0.999 1.001 1.024 0.902 1.007 0.977 0.983 0.960 0.956 0.979 0.915 0.934 ==> Sig. at Relation Coeff.Set for ET 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.010 0.000 0.011 0.010 0.006 0.008 0.005 0.006 0.004 0.010 0.008 0.007 0.010 0.006 0.006 0.008 0.003 0.005 0.012 0.003 0.004 0.007 0.006 0.000 0.005 0.004 0.006 0.006 0.001 0.001 0.000 0.002 0.004 0.017 0.005 0.001 0.000 ==> Sig. at Relation Coeff.Set for PD 0.000 0.005 0.019 0.001 0.000 0.007 0.012 0.003 0.005 0.005 0.003 0.011 0.011 0.009 0.015 0.006 0.017 0.010 0.008 0.004 0.003 0.005 0.014 0.009 0.000 ==> Ent. at Relation Coeff.Set for ET 0 0 1 3 7 9 2 0 3 3 5 3 5 6 740 2231 780 291 463 281 109 5583 9065 8453 7313 6238 5245 2388 1829 950 1075 1150 1238 1230 1021 13 19 52 95 84 34 30 1 4 10 44 19 2 0 ==> Ent. at Relation Coeff.Set for PD 8 15 38 30 0 63 723 2244 1726 274 497 6085 18259 15761 3157 166 2668 9085 8946 1311 26 19 103 58 1 These are the results of high mentioned test from ETrec+PDrec histo LOOK peak finder: Run 76345 all events xetcut vcdepcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma Mean Sigma 3 27.29 0.88 27.28 0.83 27.31 0.87 27.28 0.82 These digits it is possible to see from histos which are producing from 100th ntuple which is kept at the next LOOK binary data set: H1KFOM.TLOOK3.R76345 FAST04 3010200E 00000 DASD Start values were got as 22.02.94 results of calibration and CCvcs=3.1 It was made 3 steps of calibration. Ee =27.5151 GeV used for calibra- tion. 23.05.1994 ==================== H01USA === Lumi RUN# 376 ............ Start lumi run376 date: 23/5/94 Collision time: 5:10:57 - 5:53:21 Currents (mkA): Ie= 9401.00, Ip= 18200.00 Peak luminosity: 1.399 mb-1 s-1 Peak spec.lumi : 1399000 mb-1 s-1 mA-2 Number of collided b.: 0 Number of e-filled b.: 74 Number of p-filled b.: 0 Number of e-pilot b.: 74 Number of p-pilot b.: 0 HERA total lumi: 488.832878 mkb-1 H1 Run total lumi: 379.874981 mkb-1 H1 data taken lumi: 2.651294 mkb-1 H1 Runs: 76420 - 76427 HERA - physics: 0.563593 mkb-1 H1Run - physics: 0.563692 mkb-1 H1data - physics: 0.000808 mkb-1 H1 Runs: 76427 - 76427 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 2.34% RCF Run gated: 2.32% Relative ET trigg accept.: 0.3707 P.S. as it was looked for from OnLine pictures: Peak luminosity: near 300 mb-1 s-1 Peak spec.lumi : near 400 mb-1 s-1 mA-2 Information about number of e/p bunches is wrong due to non-standard shift action. 23.05.1994 ===== FIC#1 ======== H1KFOM === H1LumiOnLine release .... Problem of "RunStartRecord" with Luminosity branch today returned again near 11:25. Luminosity branch was Off from H1CDAQ. E.Elsen said that yesterday he received mail from Bill with possible explanation of this situation (TimeOut at H1CDAQ too small for waiting for RunStart records from all branches - TimeOut at H1CDAQ is not fixed value - it depends from branch structure and due to this fact 10th and 11th branch excluding from H1CDAQ helps at this situation). As temporary decision we decided to send RunStart record from Luminosity branch as soon as possible (immediately after recognition of RunStartPrepare phase at H1CDAQ - without waiting for RunStartPrepare Interrupt from H1CTRIG). At 12:36 new release of H1LumiOnLineFIC1 was ready and after Run 76480 Luminosity branch was On again into H1CDAQ. After 6 succesful Runs it was fixed similar situation again but with another time slice (Luminosity branch got response from H1CDAQ with "RunStartRecord not required" after Call MEBRecReady ( it means that really timeout problem exists at H1CDAQ). The next start Run was without problems and up to now (13:55) Luminosity branch is ON at H1CDAQ. Date and time of new release creation: 23.05.94, 12:23. 23.05.1994 ===== dice2 ======== H1KFOM === Relation Coefficients Set I mistaked during yesterday test of new Relation Coefficients set. I repeated the test procedure and made the same name LOOK-file. These are the results of high mentioned test from ETrec+PDrec histo LOOK peak finder: Run 76345 all events xetcut vcdepcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma Mean Sigma 3 27.46 0.86 27.49 0.82 27.48 0.85 27.56 0.81 These digits it is possible to see from histos which are producing from 100th ntuple which is kept at the next LOOK binary data set: H1KFOM.TLOOK3.R76345 FAST04 3010200E 00000 DASD 23.05.1994 ==================== H1KSOL === Lumi RUN# 377 ............ Start lumi run377 date: 23/5/94 Collision time: 10:39:08 - 16:09:42 Currents (mkA): Ie= 12741.00, Ip= 19501.00 Peak luminosity: 518.039 mb-1 s-1 Peak spec.lumi : 413.905705 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: 6411.544236 mkb-1 H1 Run total lumi: 2556.638419 mkb-1 H1 data taken lumi: 1559.328114 mkb-1 H1 Runs: 76466 - 76496 HERA - physics: 5660.672556 mkb-1 H1Run - physics: 1062.45889 mkb-1 H1data - physics: 607.711995 mkb-1 H1 Runs: 76482 - 76496 Tot curr/rate factor: 0.84% C/R F H1Run gated: 0.77% Rand.C.F: 0.73% RCF Run gated: 0.68% Relative ET trigg accept.: 0.3229 23.05.1994 ===== dice2 ======== H1KFOM === VCs calibration and ntuple It was firstly calibrated VCs after 17.05.94 replace of PHEU and divider at VCs. After 3 steps of VC-calibration it was produced value of CCvcs=4.322 Mev/FADCcount. These are the results of tests from ETrec+PDrec histo LOOK peak finder: Runs 76345 (near 30K events) all events xetcut Step Mean Sigma Mean Sigma 1-3 27.18 1.22 27.19 1.18 I propose to account this result as preliminary and hope that after making of PDrec-spectra fits and after tunning of CCvcs with shifted PD-spectra it will be possible to produce final value of CCvcs. It was made 100th ntuple with early mentioned Relation Coefficients Set and with CCvcs=4.322. This ntuple is kept at the next LOOK-binary data set: H1KFOM.ALOOKQ.R76345 FAST03 3010200E 00000 DASD From contents of this 100th ntuple it were produced 'standard' set of PDrec spectra for different H1Lumi trigger conditions (50-53,60-63, 70-73 and 80-83) which are kept at the next LOOK-binary data set: H1KFOM.BLOOKQ.R76345 FAST01 3010200E 00000 DASD Asking to L.N.Shtarkov to make PhotonArm Energy Spectra fits with his tool (only must be accounted ep-option). It were estimated effective thresholds values for different PD-trigger elements: PD1 - near 4.0 GeV (with 0.5 GeV value at Egor's card) PD - near 5.5 GeV (with 0.75 GeV value at Egor's card) PD2 - near 12.0 GeV (with 3.0 GeV value at Egor's card) ET&PD - near 7.0 GeV and as seems it is evidence that all is OK with PD-threshold setting. 23.05.1994 ==================== H01LNS === PDFIT BLOOKQ.R76345 ...... A.F. has prepared the PD spectra for a new (ep)(!) run R76345. They were fitted as (ep), and selected with (Probability > 1 %). Star (*) the next line to see the Fit Results For (ep): LIST 'H01LNS.JPDFIT.BLOOKQ.R76345.EP' For (eGas) were saved for any occasion, seem to be not useful: LIST 'H01LNS.JPDFIT.BLOOKQ.R76345.EG' 23.05.1994 ==================== H1KFOM === H1Lumi's Subtriggers ..... Today E.Elsen had finished Prescale Gaps tuning for H1Lumi's sub- triggers. As example - status of H1Lumi's trigger rates at ordinary Run 76554 (at 18:24 after 4 min of Run operation). M-monitoring Prescale Gap Rate Counts since P-physical Run Start M 86 eTAG 65536 0.29 Hz 33 P 89 eTAG&n cntr 20 0.58 Hz 53 M 91 PD low 50000 1.15 Hz 115 M 92 L Cal 3000 1.15 Hz 102 M 93 WatVet 500000 0.29 Hz 19 M 94 ElDet&PhotDet&!WatVet 8000 0.29 Hz 38 P 95 ElDet&PhotDet&WatVet 100000 0.29 Hz 16 23.05.1994 ==================== F11LEV === SHOWLUMI works ........... After small corrections in the SGI logging job, H1LUMI file exists now on dice2 (/h1/log/HERA05.H1LUMI) and contains correct information. Command SHOWLUMI therefore displays LUMI data, as in 1993. 23.05.1994 ==================== F11LEV === LH1T banks in DB ......... A new bank LH1T (see message from 21/05) from now on is permanently created and stored in DB for all H1 runs with non-zero integrated luminosity. By the way in LRTL bank an integrated lumi is stored in units of 10**25 which so far was ok, but may be a problem already during this year. With such units, a max. integrated lumi per H1 run cannot exceed 2**31*10**25 cm-2 = 2.147*10**34=21.47 nb-1. With the expected Lumi = few*10**30, it means max H1 run duration = 3 hours, and at design lumi even less (0.5-1 hour). After that Integrated lumi in LRTL becomes wrong, due to overflow. Therefore, we perhaps have to change everywhere the units for integrated lumi to 10**27. This has to be agreed upon before done, because in many places of H1 s/w LRTL is used, and thus all these places must be modified simultaneously. 23.05.1994 ==================== F11LEV === TCL files with KEEP banks Those who wants to use KEEP data on IBM. Note, that the files containing mini-KEEP events (previously being written to J.Olsson's cartridges of the F11JOL.H01.BCKUPTCL family are now copied from dice2 to IBM and stored under the names HERA03.H1TCL.C9400001 etc. (last period is incrementing, presently there are 14 such files, up to C9400014) 23.05.1994 ==================== H1KFOM === CCvcs tuning ............. After first L.N.Starkov's fit it became clear that shift at Photon Arm spectra exists (-3.7%) - for events without VC-response (70th histo CCvcs tuning with Levonyan's method at LOOK-interactive mode put the next (+17%) correction for CCvcs. CCvcs = 5.057 MeV/FADC count. With high mentioned energy shift and with high mentioned CCvcs correction it was produced new release of 100th tuple for all events from Run 76345. This ntuple is kept at the next data set: H1KFOM.ALOOKQ1.R76345 FAST12 3010200E 00000 DASD This is the result of test from ETrec+PDrec histo LOOK peak finder (for ET*PD*VC-events) Runs 76345 (near 30K events) xetcut Mean Sigma 27.49 1.22 This is the result of test from ETrec+PDrec histo LOOK peak finder (for ET*PD*nVC-events) Runs 76345 (near 47K events) xetcut&vcdepcut Mean Sigma 27.48 0.82 From contents of this 100th ntuple it were produced 'standard' set of PDrec spectra for different H1Lumi trigger conditions (50-53,60-63, 70-73 and 80-83) which are kept at the next LOOK-binary data set: H1KFOM.BLOOKQ1.R76345 FAST13 3010200E 00000 DASD Asking to L.N.Shtarkov to make PhotonArm Energy Spectra fits with his tool. 23.05.1994 ==================== H01LNS === PDFIT BLOOKQ1.R76345 ..... A.F. has updated BLOOKQ -> BLOOKQ1 for (ep) run R76345. The updated spectra BLOOKQ1 were PDFITted as (ep) (!). The results were selected with (Probability > 1%) . Star(*) the next line for Fit results: LIST 'H01LNS.JPDFIT.BLOOKQ1.R76345.EP' Pay attention to the (hidden) rightmost parts of the fit-results-lines. 23.05.1994 ==================== H1KJKU === Lumi RUN# 378 ............ Start lumi run378 date: 23/5/94 Collision time: 17:27:17 - 22:24:53 Currents (mkA): Ie= 15600.00, Ip= 19400.00 Peak luminosity: 705.576 mb-1 s-1 Peak spec.lumi : 462.104928 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: 6397.298097 mkb-1 H1 Run total lumi: 3680.603063 mkb-1 H1 data taken lumi: 2053.410427 mkb-1 H1 Runs: 76531 - 76568 HERA - physics: 5856.055501 mkb-1 H1Run - physics: 3673.504212 mkb-1 H1data - physics: 2049.571159 mkb-1 H1 Runs: 76551 - 76568 Tot curr/rate factor: 1.73% C/R F H1Run gated: 1.65% Rand.C.F: 1.01% RCF Run gated: 0.93% Relative ET trigg accept.: 0.3370 24.05.1994 ==================== H1KJKU === Lumi RUN# 379 ............ Start lumi run379 date: 24/5/94 Collision time: 1:41:46 - 4:09:03 Currents (mkA): Ie= 10283.00, Ip= 19300.00 Peak luminosity: 350.847 mb-1 s-1 Peak spec.lumi : 382.03812 mb-1 s-1 mA-2 Number of collided b.: 72 Number of e-filled b.: 82 Number of p-filled b.: 170 Number of e-pilot b.: 10 Number of p-pilot b.: 98 HERA total lumi: 2359.490744 mkb-1 H1 Run total lumi: 1986.193618 mkb-1 H1 data taken lumi: 1260.457893 mkb-1 H1 Runs: 76586 - 76595 HERA - physics: 2138.868636 mkb-1 H1Run - physics: 1592.951283 mkb-1 H1data - physics: 888.083638 mkb-1 H1 Runs: 76588 - 76595 Tot curr/rate factor: 0.39% C/R F H1Run gated: 0.4% Rand.C.F: 2.2% RCF Run gated: 2.19% Relative ET trigg accept.: 0.3132 24.05.1994 ==================== H1KJKU === Lumi RUN# 380 ............ Start lumi run380 date: 24/5/94 Collision time: 4:54:33 - 8:05:21 Currents (mkA): Ie= 21107.00, Ip= 19100.00 Peak luminosity: 622.358 mb-1 s-1 Peak spec.lumi : 359.36956 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: 6380.648114 mkb-1 H1 Run total lumi: 6134.196704 mkb-1 H1 data taken lumi: 4245.724211 mkb-1 H1 Runs: 76596 - 76601 HERA - physics: 3121.851169 mkb-1 H1Run - physics: 2319.771965 mkb-1 H1data - physics: 1471.419134 mkb-1 H1 Runs: 76597 - 76601 Tot curr/rate factor: 1.48% C/R F H1Run gated: 1.5% Rand.C.F: 1.9% RCF Run gated: 1.89% Relative ET trigg accept.: 0.3242 24.05.1994 ==================== F11LEV === Explain run summaries!... Can somebody define new values appearing in the run summaries: Tot curr/rate factor: 1.48% C/R F H1Run gated: 1.5% Rand.C.F: 1.9% RCF Run gated: 1.89% Relative ET trigg accept.: 0.3242 ---> Only Igor Sheviakov can explain this new values (A.F.) At OnLine RunSummary there are more detail abbreviation of high mentioned values: Tot curr/rate factor --> Rate/Current Factor % C/R F H1Run gated --> R/C F. H1 run gated % Rand.C.F. --> Random coinc. factor % RCF Run gated --> R.C.F. H1 run gated % Relative ET trigg accept ---> blank area As seems these values are connected with long time ago Egor's proposed alternative method of Luminosity measurements (rate method). First two digits reflect difference (at %) of our standard method (which is writting to LRTL-bank) measured Integral Luminosity Values with rate method. The next two values - attempt to measure Random Coincidence Factor (as seems). Last value (Relative ET trigg accept) - something new. 24.05.1994 ==================== H1KFOM === Night Usik's remarks...... A.Usik wrote some remarks from his tonight shift: 1) e48 is not presented at reference histos at L4; 2) due to LRTN-gap presence histos Edep-Etrig histos at L4 are looking for as sum of real Edep-Etrig with Edep only. May be it is needed to fill this histo only if LRTN is presented at current event; 3) not all shifts knows temporary method of "strugle" with RunStart Record problems at H1Lumi (reboot H1CTRIG FIC) - may be it is needed to add (temporary) some strings into H1Lumi Operation Guide 4) once it was fixed very old problem again: during moving of Movable Platforms into Parking Positions both FIC's were crashed (as You remember this situation was due to using of the same power supply boxes at room 101). Long time ago this problem was resolved (Autumn92?) - may be it is random coincidence factor? 5) e-beam which was presented at HERA during 379th Lumi RUN was dumped due to HERA people resolved some problems with PETRA and it will be possible to work with more large e-beam currents. Lumi RUN #380 - first Lumi Run with more large Ie (Ie total after end of e-injection was near 22.5 mA). So we must wait record Lumi- nosity values soon. 24.05.1994 ==================== H1KSOL === Lumi RUN# 381 ............ Start lumi run381 date: 24/5/94 Collision time: 15:09:53 - 15:31:27 Currents (mkA): Ie= 17731.00, Ip= 23700.00 Peak luminosity: 742.542 mb-1 s-1 Peak spec.lumi : 344.158056 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: 963.514352 mkb-1 H1 Run total lumi: 886.087268 mkb-1 H1 data taken lumi: 831.575861 mkb-1 H1 Runs: 76655 - 76656 HERA - physics: 453.612886 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 76656 - 76656 Tot curr/rate factor: 0.99% C/R F H1Run gated: 0.96% Rand.C.F: 2.29% RCF Run gated: 2.3% Relative ET trigg accept.: Not calc. P.S. p-beam was lost at 15:30. e-beam was dumped at 15:50. H1 Main Magnet during this Lumi RUN was at DumpCondition. Technical Problems were reported at HERA TV-screen after both beams were dumped. 24.05.1994 ==================== H1KFOM === RunStartRecord Problem.... As You can see at today H1RUN pinboard: ".... CDAQ The timeout of the lumi run start and the subsequent hangup of the DAQ is presently the most severe limitation to smooth data taking. The problem is however not in the lumi system, but the limit on the CDAQ side has to be increased. ...." Today after consultation with Bill E.Elsen and M.Zimmer had tuned timeout for RunStartRecord building at H1CDAQ. Let's hope that problem (firstly appeared at 23.04.94) may be resolved. 24.05.1994 ===== dice2 ======== H1KFOM === Test Of H1Lumi-data ...... For different checks of H1Lumi data at H1DataFlow it were made two LOOK-binary data sets from tonight #379th Lumi Run (Runs 76586-76593). H1KFOM.LOOK.R76586 FAST04 3010200E 00000 DASD H1KFOM.LOOKA.R76586 FAST12 3010200E 00000 DASD Time interval was selected from 01:48:23 up to 03:10:43 (near 80 min). It is possible to look for different H1Lumi Trigger rates (from LUMM-bank) - VC,ET,PD,PD1,PD2,ET&PD,ET&PD&nVC,PD&nVC,eTAG - at the next vectors from first LOOK-binary data set: 20000,30000,40000, 50000,60000,70000,80000,90000,100000. It is possible to look for PhotonArm Energy Histos (LUMM-bank) at 200001-200433 histos. It is possible to make the different distributions from contents of 100th ntuple (e48,vcs and vcv are included into 100th tuple). There are reasonable ETrec+PDrec histos for pure Lumi events and for rough Lumi events. Energy spectrum for ETrec for eTAG events is looking as reasonable too (near 6500 entries). We checked again VC-efficiency as ratio (RatePD-RatePDnVC)/RatePD and calculated value near 0.82 (at 01:48 time slice). Ratio of vcs-response/vcv-response is now as 1/6. Second LOOK-binary data set useful for LRTL-bank contents checking. Vector 3000 at the second LOOK-binary data sets shows TotalET*PD rate from Egor's HW counter. There is no evidence on non-standard behaivour of this counter rate as S.Levonian reported today from SHOWLUMI analyze. P.S. It is now also ok in SHOWLUMI. It was bad (Rate = 12125 kHz constantly during ca. 300 min) yesterday, 24/05 from 3:00 till 10:00 (S.Levonian) P.S. I checked LRTL-contents at Runs 76593-76594 (HERA04.H1RAWD.C9400 868 - cartridge) - from 03:10:29 up to 03:35:15. It was not looked for situation with ET&PD Total Trigger rate as Sergey wrote. Rate was changed from 13.7 kHz up to 11.0 kHz. Anybody can see 3000th vector at the next LOOK-binary data set: H1KFOM.LOOKA.R76593 FAST16 3010200E 00000 DASD 25.05.1994 ==================== H1KSOL === VETO & NC Thresholds..... Yesterday evening VETOs and VETOv thresholds were tuned to lower values,namely: VETOv = 1.25 Gev, VETOs = 0.75 GeV. The main reason of these changes is that the efficiency of VETO seems to be not enough high,and on the other hand the changing of HV would cause the new VETO calibration. Threshold on NC-trigger element was set on 15.0 GeV value due to Prof.Felst's request. So the Lumi Run 382 data were taken with new values of thresholds. 25.05.1994 ==================== H1KJKU === Lumi RUN# 382 ............ Start lumi run382 date: 24/5/94 Collision time: 23:55:50 - 4:25:55 Currents (mkA): Ie= 11604.00, Ip= 13700.00 Peak luminosity: 338.449 mb-1 s-1 Peak spec.lumi : 536.520603 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: 3236.456056 mkb-1 H1 Run total lumi: 1729.407155 mkb-1 H1 data taken lumi: 1432.671254 mkb-1 H1 Runs: 76750 - 76780 HERA - physics: 3166.180702 mkb-1 H1Run - physics: 1490.494125 mkb-1 H1data - physics: 1205.149733 mkb-1 H1 Runs: 76753 - 76780 Tot curr/rate factor: 0.58% C/R F H1Run gated: 0.58% Rand.C.F: 0.9% RCF Run gated: 0.91% Relative ET trigg accept.: 0.3175 25.05.1994 ==================== H1KFOM === SHOWLUMI test at IBM...... READMAIL message stored : WED, 25 MAY 94 15:49:37 MESZ Date: WED, 25 MAY 94 15:27:55 +0200 From: Zbigniew Szkutnik Subject: re: showlumi problem To: Alexander Fomenko Hallo, You probably have a file H1KFOM.TCPIP.DATA which is needed for tpwrite, tpwread, stage e.t.c. run on dice2. This file is needed if Ultranet path is used to/from the IBM. Unfortunately, if you have this file, then the name resolving mechanism is partially switched off and only names listed in the so called local names list are known. dice2 is mentioned in that list as dice2.desy.de and not just dice2 which is used by Sergey. One way out is to temporarily rename H1KFOM.TCPIP.DATA to, say, H1KFOM.TCPIP.DATAx. Then SHOWLUMI will work in your IBM LOOK session but tpwrite, e.t.c. will fail on dice2. On longer term this is, of course, not acceptable. Since we can not expect the general Ultranet addres resolver problem to be fixed soon on the IBM, Sergey will have to change dice2 to dice2.desy.de in his LOOK code (when he is back). Regards, Z.Szkutnik A.F. --> really after temporary rename of H1KFOM.TCPIP.DATA on another name all is OK now - SHOWLUMI works. But this is temporary decision. 25.05.1994 ===== dice2 ======== H1KFOM === Lumi=1.0*10**30 cm-2s-1... It was checked contents of today written first H1RAWD-cartridge with data from Lumi RUN #383 (HERA04.H1RAWD.C9400899) with Runs 76836-76844. It was produced the next data LOOK-binary data set: H1KFOM.LOOKA.R76836 FAST20 3010200E 00000 DASD From vector 903 it is possible to see that at 14:24 today it was fixed Current Luminosity value near 1.0*10**30 cm-2s-1 (t0=14:08). Time slice of different parameters at 14:24: Ie total = 11.7 mA Ee= 27.520 GeV Ip total = 21.65 mA Ep=819.920 GeV = +1.2 cm VC total rate = 460 kHz = +0.4 cm PD total rate = 87 kHz = 0.88 ET total rate = 75 kHz ET&PD total rate = 36 kHz PD1total rate = 115 kHz ET&PD background rate = 9.2 kHz PD2total rate = 33 kHz Specific Lumi = 6*10**29 cm-2s-1mA-2 ET&PD total rate = 36 kHz Number of collided bunches - 153 ET&PD&nVC total rate= 4.7 kHz Number of p-pilot bunches - 17 PD&nVC total rate = 12.5 kHz Number of e-pilot bunches - 15 eTAG total rate = 36 kHz Number of e-bunches - 168 Number of p-bunches - 170 VCeff = (PD rate - PD&nVC rate)/PDrate = 0.865(may be Y.S. thresholds changing effect - see message of H1KSOL from 25.05.94) Bunch structures: (10+1)*6 + (0+11) + (10+1)*6 + (0+5) + (10+1)*5 + (0+6) + (0+10) p-beam ( 9+2)*6 + (9+ 2) + ( 9+2)*6) +(3+2) + ( 9+2)*5 + (0+6) + (3+ 7) e-beam It is possible to see all high mentioned H1Lumi Trigger elements and bits rates from 20000,30000,40000,....,100000th vectors at time slice 18 min at the next LOOK-binary data set: H1KFOM.LOOKB.R76836 FAST12 3010200E 00000 DASD 25.05.1994 ==================== wittek === Lumi RUN# 383 ............ Start lumi run383 date: 25/5/94 Collision time: 14:13:58 - 18:20:30 Currents (mkA): Ie= 15757.00, Ip= 21800.00 Peak luminosity: 813.509 mb-1 s-1 Peak spec.lumi : 457.249731 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: 7379.830412 mkb-1 H1 Run total lumi: 5933.91319 mkb-1 H1 data taken lumi: 3432.712597 mkb-1 H1 Runs: 76837 - 76866 HERA - physics: 6937.922341 mkb-1 H1Run - physics: 5363.281395 mkb-1 H1data - physics: 3111.530762 mkb-1 H1 Runs: 76844 - 76866 Tot curr/rate factor: 1.79% C/R F H1Run gated: 1.74% Rand.C.F: 1.06% RCF Run gated: 1.02% Relative ET trigg accept.: 0.3366 25/5/94 ======================= wittek === Lumi RUN# 384 Start lumi run384 date: 25/5/94 Collision time: 21:26:54 - 21:30:25 Currents (mkA): Ie= 18665.00, Ip= 21600.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: 22.9212 mkb-1 H1 Run total lumi: 18.848959 mkb-1 H1 data taken lumi: 17.275425 mkb-1 H1 Runs: 76872 - 76873 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 76873 - 76873 Tot curr/rate factor: 4.82% C/R F H1Run gated: 5.01% Rand.C.F: 3.85% RCF Run gated: 4.18% Relative ET trigg accept.: Not calc. 26/5/94 ======================= === Lumi RUN# 385 Start lumi run385 date: 26/5/94 Collision time: 0:36:19 - 5:23:08 Currents (mkA): Ie= 11939.00, Ip= 21500.00 Peak luminosity: 602.464 mb-1 s-1 Peak spec.lumi : 437.558329 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: 5766.158464 mkb-1 H1 Run total lumi: 3895.993686 mkb-1 H1 data taken lumi: 2812.249825 mkb-1 H1 Runs: 76877 - 76902 HERA - physics: 5554.18829 mkb-1 H1Run - physics: 3320.496672 mkb-1 H1data - physics: 2403.554871 mkb-1 H1 Runs: 76881 - 76902 Tot curr/rate factor: 0.68% C/R F H1Run gated: 0.65% Rand.C.F: 0.73% RCF Run gated: 0.72% Relative ET trigg accept.: 0.3252 26/5/94 ======================= === Lumi RUN# 386 Start lumi run386 date: 26/5/94 Collision time: 6:17:07 - 11:55:58 Currents (mkA): Ie= 16099.00, Ip= 21000.00 Peak luminosity: 617.216 mb-1 s-1 Peak spec.lumi : 369.302717 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: 4854.918171 mkb-1 H1 Run total lumi: 3102.014285 mkb-1 H1 data taken lumi: 2537.122883 mkb-1 H1 Runs: 76911 - 76960 HERA - physics: 4422.778946 mkb-1 H1Run - physics: 1890.542025 mkb-1 H1data - physics: 1370.191729 mkb-1 H1 Runs: 76918 - 76960 Tot curr/rate factor: 0.46% C/R F H1Run gated: 0.6% Rand.C.F: 1.02% RCF Run gated: 1.05% Relative ET trigg accept.: 0.3260 27.05.1994 ==================== H1KFOM === H1LumiRuns 77109-77112.... Today during last phase of Lumi RUN #387th it were recorded 3 H1LumiRuns for possible tuning of HV at VetoCounter (Y.Soloviev request). Each Run consits of near 50 K events (last - 42K due to HERA announced end of e-filling). At all Runs it were involved 5 H1Lumi subtriggers (s91-s95) and Random Trigger with very low rate. Prescales were tuned on more or less equal rates from all needed H1Lumi's triggers - PD1,VC,ET&PD&nVC,ET&PD&VC Thresholds values was not changed: VCv = 1.25, VCs = 0.75, PD = 0.75 PD1 = 0.5, ET = 5.5 (all thresholds units at GeV). Remember that thresholds for PD are at 'strange' units now (see 02.05.94 problem with PD thresholds at LL8). Run 77110 - HVvcv = 970 V, HVvcs = 670 V - 'standard' values Run 77111 - HVvcv =1070 V, HVvcs = 770 V - 'investigated' values Run 77112 - HVvcv =1020 V, HVvcs = 770 V - 'investigated' values After end of Run 77112 HVvcv and HVvcv was returned to 970/670 values. 27.05.1994 ===== dice2 ======== H1KFOM === H1LumiRuns 1st processing. I made first attempt to process Runs 77110 and 77111 which are written at HERA04.H1RAWD.C9400924 cartridge. Run 77112 is written at the next (925th) permanent cartridge and is not accessible at DESY IBM yet. Data from Run 77109 was combined with data from Run 77110 due to same HV-status at both Runs (only prescale gaps were different). It were produced 100th tuples for two high mentioned data samples which are kept at the next LOOK-binary data sets: H1KFOM.ALOOKQ.R77109 FAST14 3010200E 00000 DASD H1KFOM.ALOOKQ.R77111 FAST07 3010200E 00000 DASD These are first data with new H1Lumi Subtrigger setting - so at 2nd attempt of processing I shall try to add all new subtriggers and all new trigger elements into 100th tuple. But for first estimation and conclusions it is possible to use high mentioned data sets: 1) there is evidence that our calibration not good for data from high mentioned samples (Relation Coefficients was got the same as at H1DataBase, Global Energy Shifts - the same as at H1DataBase (-3.0% for all ETchannels and +3.5% for all PD channels), CCvc was got from H1Data base too (5.0 MeV/FADC unit). Runs 77109 - 77110 (ET&PD&nVC-sample - near 11.7K) all events xetcut vcdepcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma Mean Sigma 0 27.40 0.90 27.32 0.86 27.30 0.92 27.39 0.87 Runs 77109 - 77110 (ET&PD&VC-sample - near 18.0K) all events xetcut Step Mean Sigma Mean Sigma 0 27.08 1.29 27.19 1.23 Run 77111 (ET&PD&nVC-sample - near 5K ) all events xetcut vcdepcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma Mean Sigma 0 27.36 0.95 27.28 0.89 27.32 0.95 27.28 0.88 Runs 77111 (ET&PD&VC-sample - near 10.0K) It is impossible to see anything reasonable due to large changing of HV at both VC channels (on 100 V both). Which are the reasons of bad calibration (mainly mean values have enough large shifts) I do not know - may be beam conditions, may be beam position, may be beam currents(?) may be something else. 2) in principle we can produce calibration coefficients for this samples and to make all needed tuning etc. but it is large work and I am not shure that it will be useful; 3) may be better to collect all data with ET&PD&nVC and ET&PD&VC from all H1Runs which were recorded during last 13 Lumi Runs and to make some 'averaging' calibration - but I cannot find MONITRIG cartridges at IBM storage - really we must make selection only from MONITRIG-cartridges with class 24 selection). From another hand yesterday R.Gerhards reported that all H1Runs which were recorded during last LumiRuns are processed - it meens that at some place (may be at dice2-environment) - these data sets must be kept. 4) there is evidence that VC calibration coefficient was changed on factor near 3.0 after incrementing of HV at both VC's PHEU on 100V and is near 1.7MeV/FADCc (VCdep spectrum is finishing near 25-26 GeV for events ET&PD&VC-trigger). As You remember ordinary (visible at linear scale VCdep energy spectrum) high energy boundary was near 12 GeV. 27/5/94 ======================= === Lumi RUN# 387 Start lumi run387 date: 27/5/94 Collision time: 6:42:49 - 11:38:17 Currents (mkA): Ie= 18545.00, Ip= 12200.00 Peak luminosity: 21.538 mb-1 s-1 Peak spec.lumi : 32.388067 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: 1154.870634 mkb-1 H1 Run total lumi: 836.338258 mkb-1 H1 data taken lumi: 434.919139 mkb-1 H1 Runs: 77092 - 77111 HERA - physics: 1092.060276 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 77111 - 77111 Tot curr/rate factor: 0.58% C/R F H1Run gated: 0.64% Rand.C.F: 0.65% RCF Run gated: 0.68% Relative ET trigg accept.: 0.3194 P.S. From start of e-filling HERA-people used for tuning yesterday file with H1 Magnet Off. Today morning H1 Magnet was ON and conditions for Lumi optimization at H1 IP were another. Only near 09:10 it was obtained more or less good Lumi values at H1 IP. 27.05.1994 ===== dice2 ======== H1KFOM === H1LumiRuns 2nd processing. I changed the structure of early used 100th ntuple due to appearence of new H1Lumi's trigger elements and H1Lumi's Subtriggers: NAM(1)='ETREC' ET reconstructed energy (GeV) NAM(2)='PDREC' PD-arm reconstructed energy (GeV) NAM(3)='VCDEP' VetoCounter deposited energy (GeV) NAM(4)='XET' Xet - reconstructed coordinate (cm) NAM(5)='YET' Yet - reconstructed coordinate (cm) NAM(6)='XPD' Xpd - reconstructed coordinate (cm) NAM(7)='YPD' Ypd - reconstructed coordinate (cm) NAM(8)='TIME' time at minutes from start of first H1Run at data sample NAM(9)='BUNCH' - bunch number NAM(10)='LI' - value of trigger element Lum_int (PD2 now) NAM(11)='PDL' - value of trigger element PD_low (PD1 now) NAM(12)='LC' - value of trigger element Lcal (ET&PD&nVC now) NAM(13)='ET' - value of trigger element ElDet NAM(14)='PD' - value of trigger element PhotDet NAM(15)='VC' - value of trigger element WatVet NAM(16)='ETAG' - value of trigger element eTAG NAM(17)='NC' - value of trigger element NC NAM(18)='RUN' - H1 Run Number NAM(19)='S86' - value of trigger bit s86 NAM(20)='S89' - value of trigger bit s89 NAM(21)='S91' - value of trigger bit s91 NAM(22)='S92' - value of trigger bit s92 NAM(23)='S93' - value of trigger bit s93 NAM(24)='S94' - value of trigger bit s94 NAM(25)='S95' - value of trigger bit s95 2-values at s86,s89,s91,s92,s93,s94,s95 elements mean Random Trigger 999.-values at ETrec,PDrec,Xpd,Ypd,Xet,Yet mean bad reconstruction First this type 100th ntuples are kept at the next data sets: H1KFOM.ALOOKQ1.R77109 FAST05 3010200E 00000 DASD H1KFOM.ALOOKQ1.R77111 FAST01 3010200E 00000 DASD It were used H1DataBase's values of Relation Coefficients set, Global Energy Shift constants and Calibration Coefficient for VCs. 27.05.1994 ===== dice2 ======== H1KFOM === VetoCounter efficiency.... As it was proclaimed earlier there is another method of VetoCounter efficiency calculating and (as seems) permanent monitoring: VCeff = (RatePD-RatePDnVC)/RatePD RatePD and RatePDnVC values are disposed at LUMM-bank. It was processed all LUMM-banks which are kept at HERA04.H1RAWD.C9400 924 - cartridge (Runs 77108-77111) and it was produced LOOK-binary data set: H1KFOM.LOOK.R77108 FAST14 3010200E 00000 DASD There is 100003th vector at this histo which shows behaivour of VCeff during near 55 min. VCeff = 0.77 with 'standard' VC HV setup and VCeff = 0.86 with first 'investigated' VC HV setup. Result is unwaitable - Yura and me waited that VCeff with 'standard' VC HV must be the same as it was proclaimed at my message from 25.05.94 (0.865) and a little better (between 0.86 and 0.9) with first 'investigated' VC HV setup. May be VCeff is changing during Lumi Run or with time or something else.But at any case we can now make monitoring of this value with time and account this value at offline processing if it is needed to anybody 28/5/94 ======================= wittek === Lumi RUN# 388 Start lumi run388 date: 28/5/94 Collision time: 5:23:06 - 12:10:10 Currents (mkA): Ie= 18800.00, Ip= 32500.00 Peak luminosity: 1190.385 mb-1 s-1 Peak spec.lumi : 411.77781 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: 9813.063058 mkb-1 H1 Run total lumi: 7868.42883 mkb-1 H1 data taken lumi: 5880.738497 mkb-1 H1 Runs: 77212 - 77236 HERA - physics: 9562.332123 mkb-1 H1Run - physics: 6931.603831 mkb-1 H1data - physics: 5135.798556 mkb-1 H1 Runs: 77214 - 77236 Tot curr/rate factor: 0.47% C/R F H1Run gated: 0.48% Rand.C.F: 1% RCF Run gated: 0.98% Relative ET trigg accept.: 0.3413 28.05.1994 ==================== H01LNS === L4 data for VC-HV ........ For the experiments on VC-HV, for Runs R077110,R077111,R07112, see upper LLO H1KFOM 27.05.94, I have done the histos from L4. It is seen that there have changed fig.18534 "ET+PD+VC for LUMI trigger". Unfortunately, I dont yet know, what means "L4 LUMI trigger". For R077111 there appiered "a shoulder" at 30 - 40 GeV. Nothing of that there appiered at R077112. Certainly, the shapes of spectrum at L4 are much broder. Then parameters have changed: N Run N in mean sigma sigma/ sqrt(N) R077110 28023 27.64 4.9 0.03 R077111 17907 29.50 5.4 0.04 R077112 19442 28.63 5.5 0.04 The values are different from on-line, see LLO H1KFOM. It is evident, that 29.50 is because of "the shoulder". L.Shtarkov, DESY. 28.05.1994 ==================== H1KFOM === Problems ................. It is needed to report some problems which were appeared during last (388th) and current (389th) Lumi RUNs: 1) SHOWLUMI- problem; 2) HERA-produced Integral lumi value problem; 3) Problem of not updating of Integrated Lumi values at H1 Run Summary. 1) today during 388th Lumi RUN (near 11:07) Total ET&PD-trigger rate at one from SHOWLUMI vectors was fixed as value near 120 MHz (this is familiar situtaion from some days ago - see LLC 24.05.94 - Test of H1Lumi data). Up to now (16:37) SHOWLUMI presents wrong picture and at the next (389th) Lumi RUN. I checked contents of LRTL-bank at On-Line Monitoring tool - all is OK with 221-word of LRTL-bank which is the source for high mentined vector contents. 2) today after EndOfRamping of e-ring (during first some minutes when Current Luminosity value was around zero) HERA produced Integral Luminosity value became -NAN(173) value. I put zero into C2-contents and all was OK during near 80 min. Near 15:16 I found -NAN(173) value again at HERA produced Integral value. As temporary decision (due to this value is reproducing at all H1Lumi pictures anywhere) I put value 3.8*10**33 into C2 and printed vector 71 from SHOWLUMI for possible hand calculation 'real' value of C2 at 15:16 today from start of 389th Lumi RUN. After calculation I got value of HERA Produced Luminosity as 3.7695*10**33 - as seems correction (randomly) was good. But: this is new problem of H1Lumi operation (never seen before). Not right value of HERA-produced Int.Lumi value was retranslated through LRTL-bank into H1Data Flow ( be careful) - but it were not fixed similar problems at this periods with another two Integrated values (H1 Gated and H1 Data Taken). 3) today during 389th Lumi RUN's H1Runs the H1Lumi's FIC#1 was crashed (sometimes this situation is happening - see above messages) After reboot of FIC#1 something happened with updating of H1Run Integrated Values at H1 Run Summary which is made with H1 Supervisor Program. On the request of H1 Run Coordinator it was checked that LRTL-banks are retranslating into H1DataFlow and SHOWLUMI shows reasonable and updated values (exept 71st vector). May be this problem of H1 Supervisor Program. It was seen that units of Int.Luminosity at H1 Run Summary are not right - must be mkb-1 (there are nb-1 units but presented mkb-1 values). 28/5/94 ====================== v.riech === Lumi RUN# 389 Start lumi run389 date: 28/5/94 Collision time: 13:48:39 - 18:47:31 Currents (mkA): Ie= 17343.00, Ip= 32300.00 Peak luminosity: 923.958 mb-1 s-1 Peak spec.lumi : 342.319886 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: 8844.503868 mkb-1 H1 Run total lumi: 7199.239514 mkb-1 H1 data taken lumi: 4859.066929 mkb-1 H1 Runs: 77252 - 77279 HERA - physics: 8057.460637 mkb-1 H1Run - physics: 6369.566214 mkb-1 H1data - physics: 4142.648429 mkb-1 H1 Runs: 77258 - 77279 Tot curr/rate factor: 0.51% C/R F H1Run gated: 0.53% Rand.C.F: 1.01% RCF Run gated: 1.01% Relative ET trigg accept.: 0.3357 P.S. e-beam after finish of Luminosity Run for H1 existed almost 2 hours for ZEUS Roman Pots investigations. 28.05.1994 ==================== H1KFOM === first MONITRIG-cartridges. Today after talking with J.Olsson and R.Gerhards it became clear that first H1DataTaking'94 MONITRIG-cartridges had appeared at HERA03-dire- ctory. Its are (for today) (see HERA05.H1POT2.MONITRIG.LOG-data set): 1)HERA03.H1POT2.MONITRIG.C9400117 76846 679 76846 18362 ..... 20)HERA03.H1POT2.MONITRIG.C9400136 76989 286 76990 3293 These cartridges keep monitoring trigger events from Lumi Runs #383 - #386th (from 25/05/94 15:02:40 up to 26/05/94 13:04:39)- 20 cartridges per one day(!!!). 28.05.1994 ==================== H1KFOM === TCL files with KEEP banks Additional information to 23.05.94 S.Levonyan's message at LLC: Those who wants to use KEEP data on IBM. Log data for TCL-files is kept at HERA05.H1TCL.LOG - data set. Today Ralf Gerhards started to fill this data set. 28.05.1994 ===== dice2 ======== H1KFOM === 100th ntuple for Run 77112 It was produced 100th ntuple with new structure (which was yesterday described at LLC) for data from Run 77112. LOOK-data set with this 100th ntuple is kept at DESY IBM storage with name: H1KFOM.ALOOKQ1.R77112 FAST07 3010200E 00000 DASD First view on contents of this tuple put the similar results as at previous one (not very good existing calibration). Runs 77112 (ET&PD&nVC-sample - near 6K) all events xetcut vcdepcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma Mean Sigma 0 27.36 0.96 27.39 0.88 27.32 0.92 27.40 0.85 Estimated value of CCvcs is near 2.5 MeV/FADC count. 28.05.1994 ===== dice2 ======== H1KFOM === VetoCounter efficiency.... It was produced new LOOK-data set with 100003rd vector for VCeff monitoring with time at H1Lumi Runs which were recorded with 'standard' and 'investigated' HVvcv,vcs setups. H1KFOM.LOOK.R77109 FAST08 3010200E 00000 DASD It is possible to see that the next VCeff were fixed at this Runs: Run 77110 - HVvcv = 970 V, HVvcs = 670 V - VCeff = 0.78 CCvcs=5.0 Run 77111 - HVvcv =1070 V, HVvcs = 770 V - VCeff = 0.86 CCvcs=1.7 Run 77112 - HVvcv =1020 V, HVvcs = 770 V - VCeff = 0.83 CCvcs=2.5 29/5/94 ======================= H01WIL === Lumi RUN# 390 Start lumi run390 date: 28/5/94 Collision time: 23:55:22 - 5:35:17 Currents (mkA): Ie= 18532.00, Ip= 31900.00 Peak luminosity: 947.973 mb-1 s-1 Peak spec.lumi : 319.60434 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: 9474.281975 mkb-1 H1 Run total lumi: 4755.564796 mkb-1 H1 data taken lumi: 3258.797651 mkb-1 H1 Runs: 77288 - 77315 HERA - physics: 8775.763834 mkb-1 H1Run - physics: 2638.591704 mkb-1 H1data - physics: 2027.035448 mkb-1 H1 Runs: 77303 - 77315 Tot curr/rate factor: 0.8% C/R F H1Run gated: 0.84% Rand.C.F: 1.24% RCF Run gated: 1.25% Relative ET trigg accept.: 0.3293 29/5/94 ======================= === Lumi RUN# 391 Start lumi run391 date: 29/5/94 Collision time: 8:23:38 - 11:33:21 Currents (mkA): Ie= 15689.00, Ip= 31500.00 Peak luminosity: 584.059 mb-1 s-1 Peak spec.lumi : 223.308874 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: 5324.5304 mkb-1 H1 Run total lumi: 3561.3672 mkb-1 H1 data taken lumi: 2561.8211 mkb-1 H1 Runs: 77315 - 77331 HERA - physics: 5097.149371 mkb-1 H1Run - physics: 2782.398794 mkb-1 H1data - physics: 1936.797378 mkb-1 H1 Runs: 77317 - 77331 Tot curr/rate factor: 0.64% C/R F H1Run gated: 0.64% Rand.C.F: 1.18% RCF Run gated: 1.19% Relative ET trigg accept.: 0.3257 P.S. e-beam was lost at 11:15 p-beam (as seems) have bad emittance and will be dumped (Ip=31.1) p-beam was dumped near 13:00. 29.05.1994 ===== dice2 ======== H1KFOM === Lumi=1.2*10**30 cm-2s-1... It was checked contents of 28.05 written two H1RAWD-cartridges with data from Lumi RUN #388 (HERA04.H1RAWD.C9400930,..931) with Runs 77212- -72217. It was produced the next data LOOK-binary data set: H1KFOM.LOOKA.R77212 FAST12 3010200E 00000 DASD From vector 903 it is possible to see that at 05:43 28.05.94 it was fixed Current Luminosity value near 1.2*10**30 cm-2s-1 (t0=05:43). Time slice of different parameters at 05:43: Ie total = 12.7 mA Ee= 27.520 GeV Ip total = 32.4 mA Ep=819.920 GeV = +0.7 cm VC total rate = 660 kHz = -0.5 cm PD total rate = 129 kHz = 0.93 ET total rate = 95 kHz ET&PD total rate = 48 kHz PD1total rate = 170 kHz ET&PD background rate = 16 kHz PD2total rate = 50 kHz Specific Lumi = 4*10**29 cm-2s-1mA-2 ET&PD total rate = 48 kHz Number of collided bunches - 153 ET&PD&nVC total rate= 6.1 kHz Number of p-pilot bunches - 17 PD&nVC total rate = 16.5 kHz Number of e-pilot bunches - 15 eTAG total rate = 40 kHz Number of e-bunches - 168 Number of p-bunches - 170 VCeff = (PD rate - PD&nVC rate)/PDrate = 0.87 At this moment VCeff had maximal value and was permanently changed up to 0.78 value at the end of e-filling. Bunch structures: (10+1)*6 + (0+11) + (10+1)*6 + (0+5) + (10+1)*5 + (0+6) + (0+10) p-beam ( 9+2)*6 + (9+ 2) + ( 9+2)*6) +(3+2) + ( 9+2)*5 + (0+6) + (3+ 7) e-beam It is possible to see all high mentioned H1Lumi Trigger elements and bits rates from 20000,30000,40000,....,100000,100003rd vectors at time slice 0. min at the next LOOK-binary data set: H1KFOM.LOOK.R77212 FAST18 3010200E 00000 DASD 29.05.1994 ===== dice2 ======== H1KFOM === first MONITRIG-cartridges. Today I tested selection of H1Lumi's MONITRIG events from first MONITRIG-cartridges (from 16 cartridges): from HERA03.H1POT2.MONITRIG.C9400120 up to ...C9400136 (exept 125th). It was produced data set: H1KFOM.H1LUMI.M120136.A00 K37033 78048081 00001 ACS-E-C with 12.5 Mbyte of information and with 8887 events from Runs 76847- - 76924). Selection was made with using of SELECT CLASS=24 option. At dice2-environment selection from 8 MONITRIG cartridges is made with 2.5 min CPU. H1Lumi Monitoring events got only 0.4% of cartridge space for all H1 MONITRIG-events at high mentioned 16 MONITRIG-cartridges. Produced data set was stageouted from dice2 to IBM-storage. It was made 100th ntuple with last structure (with new trigger ele- ments and bits) from this sample data. This ntuple is kept at the next LOOK-binary data set: H1KFOM.ALOOKQ.R76847 FAST10 3010200E 00000 DASD It were checked energy distributions ETrec+PDrec for pure and rough Luminosity events: Runs 76847 - 76924 (ET&PD&nVC-sample - near 4K events) all events xetcut vcdepcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma Mean Sigma 0 27.29 0.95 27.34 0.88 27.33 0.92 27.39 0.88 Runs 76847 - 76924 (ET&PD&VC-sample - near 1K events) all events xetcut Step Mean Sigma Mean Sigma 0 27.07 1.28 27.38 1.18 As You can see - the same problem with not good calibration exists and for this sample (the same as early reported for H1LumiRuns 77110- 77112). 29.05.1994 ==================== H1KFOM === Problems ................. Today again was fixed situation with -NAN(172) at HERA produced Luminosity value. I put value 8*10**33 value into C2 (address B0A5E134) at 20:40. Tomorrow I shall try to check this value for current 392nd Lumi RUN (and correct it at RunSummary). 30.05.1994 ==================== H1KSOL === H1TV monitor ............ Today at 9 o'clock meeting U.Strauman said that yesterday evening he had a talk with W.Bialowamce concerning Lumi value at H1 IP, which was 10% lower than at Zeus. Strauman looked on the H1TV monitor and had seen that Lumi values on it are 10% higher than on HERA monitor. He informed Bialowance about it. How long we will discuss the same matter: If you had prepared a new application for HERA with new constants and so on,P L E A S E take care that old applications are using the same constants etc.!!! Such kind of "mistakes" cause misunderstanding with HERA people, and break a trust to our LUMI monitor. I think there are no doubts to whom this message is addressed. 29/5/94 ======================= === Lumi RUN# 392 Start lumi run392 date: 29/5/94 Collision time: 17:05:50 - 21:43:26 Currents (mkA): Ie= 17647.00, Ip= 22900.00 Peak luminosity: 1059.013 mb-1 s-1 Peak spec.lumi : 518.855181 mb-1 s-1 mA-2 Number of collided b.: 151 Number of e-filled b.: 165 Number of p-filled b.: 171 Number of e-pilot b.: 14 Number of p-pilot b.: 20 HERA total lumi: 8971.118049 mkb-1 <-- MUST BE RECALCULATED A.F H1 Run total lumi: 6880.759141 mkb-1 H1 data taken lumi: 4715.26994 mkb-1 H1 Runs: 77360 - 77393 HERA - physics: 8579.156851 mkb-1 <-- MUST BE RECALCULATED A.F H1Run - physics: 6074.695803 mkb-1 H1data - physics: 4257.618453 mkb-1 H1 Runs: 77364 - 77393 Tot curr/rate factor: 0.22% C/R F H1Run gated: 0.25% Rand.C.F: 1.07% RCF Run gated: 1.13% Relative ET trigg accept.: 0.3454 30/5/94 ======================= === Lumi RUN# 393 Start lumi run393 date: 29/5/94 Collision time: 23:16:15 - 3:22:13 Currents (mkA): Ie= 19613.00, Ip= 22800.00 Peak luminosity: 700.779 mb-1 s-1 Peak spec.lumi : 294.163525 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 167 Number of p-filled b.: 171 Number of e-pilot b.: 14 Number of p-pilot b.: 18 HERA total lumi: 9589.0962 mkb-1 <--- must be recalculated A.F. H1 Run total lumi: 1276.507749 mkb-1 <--- NOT RIGHT A.F. H1 data taken lumi: 714.068788 mkb-1 <--- NOT RIGHT A.F. H1 Runs: 77399 - 77424 HERA - physics: -21424964.816644 mkb-1 <-- must be recalculated A.F H1Run - physics: -165.991601 mkb-1 <-- must be recalculated A.F H1data - physics: 1.584816 mkb-1 <-- must be recalculated A.F H1 Runs: 77407 - 77424 Tot curr/rate factor: 0.72% C/R F H1Run gated: 0.88% Rand.C.F: 1.24% RCF Run gated: 1.39% Relative ET trigg accept.: 0.3392 30/5/94 ======================= === Lumi RUN# 394 Start lumi run394 date: 30/5/94 Collision time: 4:11:06 - 4:27:57 Currents (mkA): Ie= 17235.00, Ip= 22700.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.: 171 Number of e-pilot b.: 0 Number of p-pilot b.: 171 HERA total lumi: 555.168918 mkb-1 H1 Run total lumi: 401.298565 mkb-1 H1 data taken lumi: 239.611376 mkb-1 H1 Runs: 77431 - 77433 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 77433 - 77433 Tot curr/rate factor: 1.67% C/R F H1Run gated: 1.74% Rand.C.F: 2.09% RCF Run gated: 2.06% Relative ET trigg accept.: Not calc. 30.05.1994 ==================== F11LEV === SHOWLUMI on IBM........... LOOK has been recompiled with HOST="dice2.desy.de" for SHOWLUMI coomans according to reccomendation of Z.Szkutnik. That means, private NETRC files at DESY IBM must be corrected. First line must look like follows: machine dice2.desy.de Content of LUMI bank created in TCL job and used for SHOWLUMI display still from time to time gets corrupted(?) Namely, something happens with value of column #7 (which is filled from LRTL(221)=total rate). Last time it happens around 6:44 today, as one can see at SHOWLUMI fig.74: before 6:44 fig.74 showed rate ca. 27 kHz and then suddenly changed to 1212498258 (in 0.1Hz units) If LRTL is correct (according to Fomenko) then R.Gerhards should look into his TCL job at SGI and find a reason. Also in our run summaries many strange values. E.g. in RUN #393: HERA - physics: -21424964.816644 mkb-1 H1Run - physics: -165.991601 mkb-1 or in #394: 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.: 171 Number of e-pilot b.: 0 Number of p-pilot b.: 171 HERA total lumi: 555.168918 mkb-1 30/5/94 ======================= === Lumi RUN# 395 Start lumi run395 date: 30/5/94 Collision time: 5:34:40 - 10:52:28 Currents (mkA): Ie= 18938.00, Ip= 22600.00 Peak luminosity: 872.642 mb-1 s-1 Peak spec.lumi : 402.79385 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 171 Number of e-pilot b.: 15 Number of p-pilot b.: 18 HERA total lumi: 7529.691179 mkb-1 H1 Run total lumi: 4214.588679 mkb-1 H1 data taken lumi: 2979.37266 mkb-1 H1 Runs: 77433 - 77447 HERA - physics: 6982.250253 mkb-1 H1Run - physics: 2209.378964 mkb-1 H1data - physics: 1418.145366 mkb-1 H1 Runs: 77436 - 77447 Tot curr/rate factor: 1.05% C/R F H1Run gated: 1.07% Rand.C.F: 1.46% RCF Run gated: 1.47% Relative ET trigg accept.: 0.3348 30.05.1994 ==================== H1KSOL === Run Summaries ............ Comment to Run Summaries for run#393,394: 1. During Run #393 a value NAN (undefinite) appeared in the HERA produced value of LUMI. Why this value is corrupted last few days is not clear yet. The digits with suffics physics are calculated using HERA produced value. 2. In the Run#394 the Lumi e beam was lost befor Lumi Run was declared,so the peak Lumi value eq.0. 30/5/94 ======================= kuznik === Lumi RUN# 396 Start lumi run396 date: 30/5/94 Collision time: 13:13:16 - 15:59:52 Currents (mkA): Ie= 19509.00, Ip= 22301.00 Peak luminosity: 800.706 mb-1 s-1 Peak spec.lumi : 360.98782 mb-1 s-1 mA-2 Number of collided b.: 150 Number of e-filled b.: 165 Number of p-filled b.: 171 Number of e-pilot b.: 15 Number of p-pilot b.: 21 HERA total lumi: 4975.261531 mkb-1 H1 Run total lumi: 3195.457522 mkb-1 H1 data taken lumi: 2603.246571 mkb-1 H1 Runs: 77483 - 77492 HERA - physics: 4448.088936 mkb-1 H1Run - physics: 3072.985892 mkb-1 H1data - physics: 2587.121363 mkb-1 H1 Runs: 77486 - 77492 Tot curr/rate factor: 0.83% C/R F H1Run gated: 0.65% Rand.C.F: 1.62% RCF Run gated: 1.47% Relative ET trigg accept.: 0.3457 30.05.1994 ===== FIC#2 ======== H1KFOM === H1LumiOnLine release ..... Today it was prepared and involved into operation at 18:07 30.05.94 (after Run 77506) new release of H1LumiOnLineFIC2-program. Creation date/time: 30.05.94 18:07. It were made changings at LumiMonitoring.f-subroutine at those places which (as seems) were responsible for production of NAN-values at HERA produced luminosity values. 31/5/94 ======================= H01GOG === Lumi RUN# 397 Start lumi run397 date: 31/5/94 Collision time: 1:52:15 - 7:37:55 Currents (mkA): Ie= 19274.00, Ip= 20200.00 Peak luminosity: 848.054 mb-1 s-1 Peak spec.lumi : 404.415285 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: 9061.61418 mkb-1 H1 Run total lumi: 8225.309 mkb-1 H1 data taken lumi: 5812.6896 mkb-1 H1 Runs: 77529 - 77555 HERA - physics: 8946.124843 mkb-1 H1Run - physics: 7817.395867 mkb-1 H1data - physics: 5500.126874 mkb-1 H1 Runs: 77531 - 77555 Tot curr/rate factor: 0.27% C/R F H1Run gated: 0.27% Rand.C.F: 1.28% RCF Run gated: 1.27% Relative ET trigg accept.: 0.3398 31.05.1994 ===== dice2 ======== H1KFOM === First View on CC-changing Yesterday it was processed part of last TCL-cartridge: HERA03.H1TCL.C9400018 B13568 78048081 00001 ACS-E-C and it was produced 14 Mbyte LOOK-binary data set with set of vectors for LRTL-bank contents check and LRPC-,LREC-banks check. Its name is H1KFOM.LOOKA.R77290 FAST16 3010200E 00000 DASD All high mentioned cartridge includes 51486 events (RUN DATA) from H1 Run Range 77195-77330. It were processed RUN DATA from H1 Run Range 77290 - 77330 (3073 LRTL-banks, 2856 LREC-,LRPC-banks). Time period: from 29.05.94 00:05 up to 29.05.94 11:15 (Lumi RUNs #390 and #391). It is possible to see at vectors 3000 that all is OK with 221st word of LRTL-bank. Vector 903 shows Current Luminosity behaivour with time. Vectors 802-805 shows beam position behaviour with time. Vector 806 shows ACCC-beahaivour with time. Histos 6001-6025 shows behaivour of CCpd with time and 5001-5049 - CCet with time ( % from start value). Vector 6026 shows (firstly) CCvcs behaivour with time etc. These two Lumi Runs were with good and stable beams with good and stable specific Lumi value and it is very interesting that value was changed during 390th Lumi RUN on 1.0cm(!!!) - from +0.6 to -0.4. And it was not fixed any influence on Specific Lumi value. First view on CC behaivour with time put the next results: 1) there is enough large changing of some calibration coefficients with time (maximal are p13 (-15%), e22 (-12%)). 2) behaivour with time shows that (as seems) dividers and PHEU are responsible for this changings (mainly); 3) firstly it was seen behaivour with time of CCvcs - not more then 8% from start value at both Lumi RUNs - as seems all is OK with relative calibration of vcs (absolute values must be checked - may be famous Usik's 3.89 factor was not accounted). 31.05.1994 ==================== H01LNS === L4 data are strange ...... Looking at L4 histos for LUMI: Its seems, that something is wrong with LUMI, I would like to be mistaken, I hope so. Looking is made here BACK from this moment ~12.00 31.05.94. Below are referenced mainly the following L4-histos: f 18514 = Edep-Etrig for ET f 18524 = Edep-Etrig for PD f 18534 = ET+PD+VC for LUMI trigger f 18535 = ET for Etag triffer 1. Now, that should run the Lumi RUN# 398: All is looking as if NOT working, at least, histos for LUMI trigger and for ET trigger are empty. 2. LUMI RUN# 397 IS LOOKING BAD FROM THE VERY BEGINNING TO THE END: a) ET+PD+VC for LUMI trigger is about empty, b) In Edep-Etrig for ET there is none of the main peak ar Zero, c) Strangely, that in Edep-Etrig for PD there is none of right part. 3. Lumi RUN# 396 is normal at the beginning, but bad at the end. As if something were getting broken along the time of this RUN# 396. 4. Lumi RUN# 395 is looking about the same as the previous RUN#: Normal at start, bad at the end. Dont know what was in the middle. 5. Fortunately, in the contrary to the previous, Lumi RUNS# 393 and 392 are looking well at the starts, and the ends. Sorry, I am not strong at L4, I hope, all this is only miss-understanding, but better be safer. Somebody should check these suspections. Lollii Shtarkov. 31/5/94 ======================= === Lumi RUN# 398 Start lumi run398 date: 31/5/94 Collision time: 12:18:01 - 13:21:13 Currents (mkA): Ie= 19426.00, Ip= 20000.00 Peak luminosity: 832.07 mb-1 s-1 Peak spec.lumi : 441.612301 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: 2576.057606 mkb-1 <--- 2661.1 mkb-1 (A.F.) H1 Run total lumi: 2101.840391 mkb-1 H1 data taken lumi: 1613.311306 mkb-1 H1 Runs: 77602 - 77611 HERA - physics: 1531.10495 mkb-1 <--- 1616.1 mkb-1 (A.F.) H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 77611 - 77611 Tot curr/rate factor: 0.94% C/R F H1Run gated: 0.98% Rand.C.F: 1.95% RCF Run gated: 2% Relative ET trigg accept.: 0.3387 P.S. HERA total lumi was corrected (incremented on 85 mkb-1) due to non-standard Reset Integrated Lumi values procedure. 31.05.1994 ==================== H01LNS === L4 for RUN# 398 is ? ..... Looking at L4 histos for LUMI: Now, that Lumi RUN# 398 has ended, I'v cheched L4 Lumi histos for the start of RUN#, for Run077602. They are about the same as for the start of the previous RUN# 397, that is, they are looking BAD. In any case these histos are differing from the "regerence", more important - they differ from the ones 3 - 5 RUNS# before. Compare this with my LLO two steps upstairs ... PS: If anybody would help me to understand such L4 histos - Thanks. Lollii Shtarkov. 31.05.1994 ==================== H1KFOM === L4 Histos for 399th Run... I checked contents of Lumi histos at L4 for Run 77620 at H1CDAQ. As seems all is OK (as ordinary last time). Really there are some differences with Reference plots for ep: 1) VCs hits is not so offen as at reference (18525 histo) - factor 3 (may be it is due to another H1 Trigger Coctail now); 2) e48 (it was remarked earlier at LLC) - histo 18515; 3) peak at ETrec+PDrec+VCdep is around 27 GeV (not around 26 GeV) - it is understandable (histo 18534); 4) ETrec for eTAG trigger is another (maximal value is shifted on 3 GeV into large values as at reference) - may be due to new ET-geometry; 5) ETrec-ETtrig and PDrec-PDtrig are looking as always at last time (mix of more statistical 'zero' peak and 'pure' ETdep or PDdep - this is OK due to LRTN-prescale factor 10. 6) VCdep histos seems OK. 31.05.1994 ==================== H01LNS === L4 for Run 77620 ? ....... For Run 77620 exactly there are NO histos from L4 at hera03 ! I dont know, how to understand the previous LLO of A.F. Why not look at the histos refered in my LLO as being BAD ? These refered histos are needed to be checked and understand . 31.05.1994 ==================== H01LNS === L4 for Run 77625 OK! ..... Just now I have look'ed at the last Run, Run 77625. I dont believe, but all histos became back OK ! So, something has been changing the last time. To check me its necessary to look at the L4 histos from the shifts, e.g., A.Usik made a copy from somewhere ? The most wrong was Lumi RUN# 397, Runs 77531, 77555, Look at them ! It's were strange, that the shifters had not noticed the effect. 31.05.1994 ==================== H1KFOM === Lumi values for 392,393... As You remember I promised to recalculate Integral Lumi Values for Lumi RUNs 392 and 393 which were corrupted with NAN-problem: Lumi RUN #392: "..... Start lumi run392 date: 29/5/94 Collision time: 17:05:50 - 21:43:26 HERA total lumi: 8971.118049 mkb-1 <-- MUST BE RECALCULATED A.F H1 Run total lumi: 6880.759141 mkb-1 H1 data taken lumi: 4715.26994 mkb-1 H1 Runs: 77360 - 77393 ...." HERA total lumi: 8899.2 mkb-1 <-- Recalculated value Lumi RUN #393: ".... Start lumi run393 date: 29/5/94 Collision time: 23:16:15 - 3:22:13 HERA total lumi: 9589.0962 mkb-1 <--- must be recalculated A.F. H1 Run total lumi: 1276.507749 mkb-1 <--- NOT RIGHT A.F. H1 data taken lumi: 714.068788 mkb-1 <--- NOT RIGHT A.F. H1 Runs: 77399 - 77424 ..." HERA total lumi: 7017.9 mkb-1 <--- recalculated value H1 Run total lumi: 5190.492 mkb-1 <--- recalculated value H1 data taken lumi: 3645.964 mkb-1 <--- recalculated value I used 903rd vectors from the next LOOK-binary sets for 'reconstruction' of HERA produced Lumi values: H1KFOM.LOOKA.R77360 FAST14 3010200E 00000 DASD H1KFOM.LOOKA.R77398 FAST18 3010200E 00000 DASD For 'reconstruction' of H1 Run Total lumi and H1 Data Taken Lumi values it were used data from last LRTL-banks at each H1Run at high mentioned Lumi Runs. I checked (for any case) H1 Run Total Lumi and H1 Data Taken Lumi for Lumi RUN #392 (which were not corrupted) and was very surprized that 'reconstructed' values are less then values at Egor's RunSummary: RunSummary's value: H1 Run total lumi: 6880.759141 mkb-1 H1 data taken lumi: 4715.26994 mkb-1 'Reconstructed' values from Luminosity at tapes (from LRTL-banks): H1 Run total lumi: 5701.601 mkb-1 H1 data taken lumi: 4008.187 mkb-1 Igor used for Run Summaries the same data as H1LumiOnLineFIC2-program This large difference will be expalined with accounting of Luminosity during WarmStart(as version). We can check it. 31.05.1994 ==================== H1KFOM === Neutron Counters ......... From yesterday it was installed thresholds value for NC-triigger element as 10 GeV (before this it was installed 15 GeV value). Today I had first contacts with Olaf Duenger(F22OLA) who will be responsible for off line check and analize of LRNA-bank. He got all needed start information. Prescale factor for s89 now is very high (20 value) - we had on 100000 H1 events only 80 events eTAG&n cntr. E.Elsen promised to install it on zero value. 31.05.1994 ==================== H1KFOM === s95 is Monitrig now....... Today I looked for that s95 trigger bit is MONITRIG now (E.Elsen changed it at current H1CTRIG-monitoring program). We must be shure that s95-triggered events will appear at MONITRIG cartridges (may be it is needed to update some codes or table at L5-code?). 31/5/94 ======================= kuznik === Lumi RUN# 399 Start lumi run399 date: 31/5/94 Collision time: 14:43:57 - 19:29:32 Currents (mkA): Ie= 19692.00, Ip= 19800.00 Peak luminosity: 863.11 mb-1 s-1 Peak spec.lumi : 419.583241 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: 7640.218094 mkb-1 H1 Run total lumi: 5735.563058 mkb-1 H1 data taken lumi: 3529.05069 mkb-1 H1 Runs: 77615 - 77628 HERA - physics: 7075.94189 mkb-1 H1Run - physics: 5489.39393 mkb-1 H1data - physics: 3344.81834 mkb-1 H1 Runs: 77617 - 77628 Tot curr/rate factor: 0.29% C/R F H1Run gated: 0.38% Rand.C.F: 1.47% RCF Run gated: 1.23% Relative ET trigg accept.: 0.3210 1/6/94 ======================= kuznik === Lumi RUN# 400 Start lumi run400 date: 31/5/94 Collision time: 22:18:54 - 2:51:03 Currents (mkA): Ie= 17499.00, Ip= 19000.00 Peak luminosity: 457.669 mb-1 s-1 Peak spec.lumi : 257.304901 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 167 Number of p-filled b.: 170 Number of e-pilot b.: 14 Number of p-pilot b.: 17 HERA total lumi: 5127.662227 mkb-1 H1 Run total lumi: 4166.6763 mkb-1 H1 data taken lumi: 3397.8049 mkb-1 H1 Runs: 77644 - 77662 HERA - physics: 4990.848825 mkb-1 H1Run - physics: 3969.128154 mkb-1 H1data - physics: 3225.572246 mkb-1 H1 Runs: 77648 - 77662 Tot curr/rate factor: 0.65% C/R F H1Run gated: 0.62% Rand.C.F: 1.11% RCF Run gated: 1.05% Relative ET trigg accept.: 0.3280 1/6/94 ======================= h01gog === Lumi RUN# 401 Start lumi run401 date: 1/6/94 Collision time: 12:15:29 - 16:39:02 Currents (mkA): Ie= 19889.00, Ip= 21000.00 Peak luminosity: 795.217 mb-1 s-1 Peak spec.lumi : 425.300905 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: 7635.209937 mkb-1 H1 Run total lumi: 4918.585804 mkb-1 H1 data taken lumi: 3757.429255 mkb-1 H1 Runs: 77703 - 77730 HERA - physics: 6089.040104 mkb-1 H1Run - physics: 3089.441804 mkb-1 H1data - physics: 1980.778055 mkb-1 H1 Runs: 77706 - 77730 Tot curr/rate factor: 0.6% C/R F H1Run gated: 0.62% Rand.C.F: 1.37% RCF Run gated: 1.4% Relative ET trigg accept.: 0.3321 02.06.1994 ===== FIC#1 ======== H1KFOM === H1Lumi's FER ............. 01.06.94 Eckhard Elsen investigated FER-times from different branches and put for us the some monitoring pictures from H1CTRIG-application: 1) histo of FER-time from Luminosity branch (time from 0.8 msec up to 2.2 msec) - 94/06/01 12.25; 2) plot (Brunch number VS MaxFER-time) - 94/06/01 10:43; 3) plot ((L1ALL-L1ACTIVE) VS PL1ACTIVE) - 94/06/01 11:20; 4) bands from (3) plot for different PL1ACTIVE-regions: (from 3.0 up 4.2 and from 4.2 up to 100) - 94/06/01 11:13. We had attempt to understand this pictures: (1) - most of statistics is disposed at large peak around 1.55 msec near 10% of statistics is disposed around 1.75 msec and little part around 1.92 msec. - as seems first peak reflects most often Luminosity branch FER- time (without ReadOut of Trigger Sums). - second peak reflects FER-time when Trigger Sums are included into Readout (10% of events with LRTN-banks); - third peak (1.92) - no any ideas. (2) - for 9th branch (Luminosity branch) there is some population of FER-time at region from 25 msec up to 100 msec - without any peaks. - it is possible to explain this population with situations at H1Lumi's Readout which early were proclaimed as overflow situations and after June 93 (after last Egor's upgrade) Lumi- nosity branch does nod send FER into H1CTRIG before posibility of readout into first free buffer (from 8 busy buffers at L2Keep appearence moment). - ILevela.f subroutine which makes all needed processing of read data (decoding, linearization, making of FADC-counts, creation of BOS-banks) really can free one from 8 buffers for period around 10 msec (due to near 100 Hz dead line for Luminosity branch); - sometimes KEEP-banks are connecting to current L2keep-events (LRTL,LUMM,LREC,LRPC) and some additional time it is needed to Ilevela.f - subroutine for procedure of making buffer as free - in general 100 msec FER-time seems as ubnormal (may be some algorithm problems) - I would wait not more then 20 msec MAXFER from Luminosity branch. (3) - L1ALL-L1ACTIVE at E.Elsen terminology is H1 Dead Time PL1ACTIVE - is unknown variable (may be procent L1ACTIVE/L1ALL?) - at high mentioned plot there are 3 statistics population area with different H1 Dead Time regions: a) most statistics is at band from PL1ACTIVE from 2.3 up to 2.8 (H1 Dead Time is up to 170 msec) b) 2nd statistics is at band from PL1ACTIVE from 2.8 up to 4.2 (H1 Dead Time is up to 100 msec) c) 3rd statistics is at band from PL1ACTIVE from 4.2 up to 100.0 (H1 Dead Time is up to 50 msec) (4) - there are two histos (as seems its are 2 projections of (b) and (c) bands on H1 Dead Time axis Some conclusions: a) almost all situations at FER-time distribution from Luminosity branch are clear and as seems more or less reasonable; I don't know which is part of FERMAX-time ststistics population for Luminosity branch (as seems it must be negligable but who knows); b) Statistics population with MAXFER from 20 msec up to 100 msec will be decremented or (may be) will disappear if our FIC#1 will be replaced on the more quick model (8231 as example) c) FER-time distributions will be better for more fast FIC#1 (may be factor 2 - as Bill promised); d) I am not shure that it is needed to change FIC#1 immediately (E.Elsen proposed to make this changing at one of the nearest gaps between LUMI Runs, Bill proposed to make the same 2 weeks ago - when RunStartRecord acknoledge problem was at critical stage Igor Sheviakov today recommended to wait of shutdown for FIC#1 replace. We must be shure that Luminosity branch is really critical part of H1 for getting of more Luminosity for H1 at 94 for immediately actions. S.Burov had prepared for any case FIC8231 with floating point coprocessor and is waiting of our and E.Elsen decision. 02.06.1994 ==================== H1KFOM === Veto Counter HV Changing.. Today Yura Soloviev had changed HV status at both VC's PHEU: a) HVvcv = 1020 V HVvcs= 770 V. b) it was made before H1Run 77804. c) S.Levonyan was asked by Yura to put new value of CCvcs into H1DataBase for data after H1Run 77803 - CCvcs was got from estimation of CCvcs at Run 77212 (see earlier). d) the reason of changing - some Yura's investigations of VC-eff and beahaivour of VC-trigger element at last Lumi Runs. PS LFRC bank was modified by CCv=2.5 instead of previous 5.0 starting from the run 77804 on. Its version is 21. (S.L.) 02.06.1994 ==================== H1KFOM === Neutron Counters ......... Yesterday R.Felst and O.Duenger put to me and Yura some pictures from off-line analyze of LRNA-bank contents and asked to change Shift Constant for 11th FADC from 143 on 140. Yura made this changing through Egor's NeutronCounters window and LRNA-banks after H1 Run 77804 were written with this new shift constant. Later I shall put this constant into default value (for reboot FIC#1 situations). Today during Lumi RUN #402 (H1 Run 77817) H1Lumi's FIC#1 was crashed and after reboot first 3.5 minutes of H1 Run 77818 data were written with old '143' shift value. 02.06.1994 ===== FIC#1 ======== H1KFOM === H1LumiOnLineRelease ...... Today it was prepared (not tested yet) new release of H1LumiOnLineFIC1 program with high mentioned changing of default value for 11th FADC Shift (143--->140). Data and time of creation: 02.06.94 14:41. 2/6/94 ================= schwab/h01gog === Lumi RUN# 402 Start lumi run402 date: 2/6/94 Collision time: 11:28:51 - 16:16:28 Currents (mkA): Ie= 19248.00, Ip= 24200.00 Peak luminosity: 853.383 mb-1 s-1 Peak spec.lumi : 368.782505 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: 10949.1851 mkb-1 --> 8593.2mkb-1 (corr. by S.L.) H1 Run total lumi: 9897.464 mkb-1 H1 data taken lumi: 3141.1247 mkb-1 H1 Runs: 77809 - 77828 HERA - physics: 10580.354795 mkb-1 --> 8224.4mkb-1 (corr. by S.L.) H1Run - physics: 8528.370834 mkb-1 H1data - physics: 2971.844428 mkb-1 H1 Runs: 77815 - 77828 Tot curr/rate factor: 0.08% C/R F H1Run gated: 0.07% Rand.C.F: 1.57% RCF Run gated: 1.54% Relative ET trigg accept.: 0.3326 P.S. - it were fixed 2 spikes at Current Luminosity values at this Lumi RUN (first spike put near 2 nb-1 into all Integrated Lumi values, second one not so large) - A.F. - as it was calculated (preliminary) HERA produced Lumi value at this Lumi RUN must be reduced on 2.358 nb-1, H1 Run total must be reduced on the same value (due to Run 77816 existed during 1st spike and Run 77819 - during 2nd spike). H1 Data taken must be corrected with account of Dead Time at high mentioned Runs. 02.06.1994 ==================== H01LNS === L4 LUMI monitoring........ I should report of some activity connected to L4-monitoring: - I AM PLOTTING OBLIGATORY THE LUMI-L4-HISTOS FOR ALL LUMI RUNS#, NOW IT IS DONE TWICE - FOR THE STARTING AND THE ENDING RUNS OF RUN#. IN ANY CASE, THIS INFORMATION IS SAVED AND READY FOR ANYBODY ANALYSIS. - One "effect" is well seen from time to time, as if randomly - thas is disapierence of the peak at ZERO for Edep-Etrig, and sometimes disapierence of the "shoulder" to the right of ZERO. I have reported about this problem in a number of LLO's, find ===== H01LNS L4. - The shifters have not commented these cases. The less, the better. - It seems, that this "effect" is connected with changing prescalers. Unfortunately, the shifters reported of changing prescalers not in any case, and NEVER(!) reported of the old/new values of prescaling. - For that reason, only for LUMI and for LUMI RUNs#, I have done "fishing-out" of prescalers from H1 DataBase, via numbers of Nrun. It seems, that there is correlation between the above "effect" and changing prescalers, but systematic analysis has not yet done. - I have prepared a Table of the "fished-out" prescalers for our RUNs#, Put star(*) at the next line if you are interested in prescalers: LIST 'H01LNS.LUMI.PRESCAL' The date of job is 01.06.94, the file will be updated. See, that the lines are longer 72, up to 130 to the right. I dont like the format of the Table, it will be improoved. - I have prepared some changing of L4-LUMI-sofware, will deliver it. - Much more interesting are Q's of extending of L4-LUMI-software, first of all for LUMI-triggering, then for det's efficiencies, etc. I am trying to understand what can be done to LUMI-L4, not yet ready. - Motivation of the above activity: S.Levonian's and R.Gerhards's. Lollii Shtarkov, from DESY. 3/6/94 ======================= h01gog === Lumi RUN# 403 Start lumi run403 date: 2/6/94 Collision time: 21:26:38 - 1:25:41 Currents (mkA): Ie= 19754.00, Ip= 23700.00 Peak luminosity: 824.837 mb-1 s-1 Peak spec.lumi : 344.081505 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: 5435.831936 mkb-1 H1 Run total lumi: 3385.9809 mkb-1 H1 data taken lumi: 2647.4266 mkb-1 H1 Runs: 77866 - 77894 HERA - physics: 4959.195965 mkb-1 H1Run - physics: 2913.657731 mkb-1 H1data - physics: 2597.153476 mkb-1 H1 Runs: 77870 - 77894 Tot curr/rate factor: 1.17% C/R F H1Run gated: 1.07% Rand.C.F: 1.64% RCF Run gated: 1.48% Relative ET trigg accept.: 0.3353 03.06.1994 ==================== H1KFOM === H1Run PB's message remark I would like to put some comments to last message at H1RUN PB: ".... 000510 - 94/06/02 - gerhards --- data quality and reconstructi ------ H1RUN == .... Lumi L.Shtarkov no terrible problems, some questions, few per cent difference on different lumi monitors, not understood, integrated lumi sometimes nonsense (visitor effect), no effect on real lumi, monitor trigger tapes requested for analysis, subtrigger 95 should become monitor trigger, L4 histograms show some changes since yesterday for unknown reason, Prosi suggested due to corrupted lumi bank, difficult to get lumi plots on L5, increased activity between online and offline lumi groups recommended ..... ..." 1) few percent difference on different lumi monitors, not understood: not correct - understood and corrected by Usik; 2) integrated lumi sometimes nonsense (visitor effect): a) NAN-problem is resolved; b) 3 times fixed unwaitable Reset Integrated values during Lumi RUN (not resolved - very rare situation); c) spikes effect (as example 402nd Lumi Run - 2 spikes - more then 2 nb-1 additional not produced Lumi)-not resolved at OnLine (rare situation - 5-6 spikes at all collection94) d) difference between Integrated Lumi at LLC RunSummary and at collection of Integrated Lumi on cartridge - it was looked for one case of large difference - not resolved - additional analize required. e) visitor effect - not correct. 3) no effect on real lumi: a) correct if this remark means Current Luminosity value at LRTL- bank (exept spike problem); 4) L4 histograms show some changes since yesterday for unknown reason, Prosi suggested due to corrupted lumi bank: a) as seems unknown reason became clear (see L.N.Shtarkov's last message); b) Prosi's remark is not random one - I promised to correct BOS- structure errors which sometimes appear at LRPP and LREP banks (they are banks without preliminary check of BOS structure - - old problem of 'zero' corrupted banks - see LL8). But at this case this suggestion is not correct. 5)increased activity between online and offline lumi group recommended a) as seems - not correct - we have LLC for this type contacts. It is very good and time keeping communication facility. b) as I know any reguests and questions from offline people were resolved or discussed - what else? 3/6/94 ======================= h01dbl === Lumi RUN# 404 Start lumi run404 date: 3/6/94 Collision time: 5:52:48 - 11:09:21 Currents (mkA): Ie= 19949.00, Ip= 19400.00 Peak luminosity: 618.54 mb-1 s-1 Peak spec.lumi : 295.090742 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: 9117.302035 mkb-1 H1 Run total lumi: 6306.685746 mkb-1 H1 data taken lumi: 4552.792181 mkb-1 H1 Runs: 77899 - 77916 HERA - physics: 9087.248094 mkb-1 H1Run - physics: 6254.171213 mkb-1 H1data - physics: 4511.682401 mkb-1 H1 Runs: 77900 - 77916 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 5.25% RCF Run gated: 5.3% Relative ET trigg accept.: 0.3002 P.S. Usik made new tool for finding of Peak Lumi Values for current Lumi RUN at OnLine, as example for Lumi RUN #404: Igor's values: Peak luminosity: 618.54 mb-1 s-1 Peak spec.lumi : 295.090742 mb-1 s-1 mA-2 Usik's values (Off Line check put the same values): Peak luminosity: 1140.00 mb-1 s-1 Peak spec.lumi : 559.00 mb-1 s-1 mA-2 Asking to Igor - when it will be possible replace please at Your RunSummary Maker these(very useful) values on Usik's variables: Peak Luminosity: contents of address B09E540C (float) cm-2sec-1 Peak spec.lumi : contents of address B09E5410 (float) cm-2sec-1mA-2 A.F. 03.06.1994 ==================== F11LEV === LUMI L1/L4/L5 ........... Few comments on several last messages by Shtarkov and Fomenko. 1) LUMI measurements. Occasional spikes in online Lumi (seen e.g. in SHOWLUMI) are most likely due to the currents transfer problem between CT and LUMI. This means, lumi values in LRTL are wrong in that cases, however for the database (banks LH1R,LH1T) they are automatically corrected because I use only rates from LRTL, but currents from TCUR. Note also, that HERA produced lumi for the TV monitors after these spikes gets artificially larger. Thus after some time there will be a significant difference between my values in offline lumi summary table and online monitors (like it was last year). 2) L4 histograms are known to be outdated and must be uptated. Reasons - changed banks set (prescaled LRTN mode), modified bank content (LREE(48), LRPE(26), veto calibration etc). I shall go through LUMMON code and see what should be modified. Some proposals of L.N.Shtarkov will be definitely taken, but not all. Unfortunately, we are not allowed to create as many histos as we would like, but only most important and informative from the point of view of the system operation. 3) LREC module (at least at L4) also produces a lot of errors now. Again, most likely - changed banks. I shall fix this as soon as possible. 4) Permanent data quality monitoring at L4/L5 levels (presently done by Shtarkov) must go on with regular reports on the general H1 data quality meetings (called by Ralf Gerhards and Jan Olsson). Any proposals for the new useful histos at L5 are welcome. 5) Ideally, these checks should also include some "physics". Namely, the behaviour of different eTAG physics subtriggers (s80-s86), event classification (min.bias eTAG - class 19) etc. 6) Finally, an automatic procedure for L4/L5 data control is desired (analyse in some robust way histogram content and create warnings/ alarms in case of abnormal behaviour). Could L.N. also start to think on that project? 7) Very important: cross check our basic lumi estimate by other methods I mentioned this already 10 times, but would like to repeat again. We are producing and outputing a large amount of information, sufficient for at least 3 different LUMI estimates. On the other hand, we have now also sufficient manpower for that (L.N.S., Andreev, Nelly, Soloviev) All of them have some other duties, but combining their efforts it must be fairly easy to do. P.S. Why don't you call a local meeting, work out a strategy and distribute tasks for that particular item? 03.06.1994 ==================== H1KFOM === Non-Right Lumi Measurement At collection of Lumi RUNs 94 there is one example of Non-Right Luminosity Measurements (Lumi RUN #393). Near 02:40 30 May 1994 Usik found that there is message at H1Lumi's Monitoring Tool "Bunch currents are not updated" - it means that no problems with LAN-communication between H1Lumi MacII and H1CTRIG MacII but H1CTRIG FIC's program does not refresh bunch current values at its storage (may be due to problems with Calo at this Lumi RUN and very often WarmStart). As seems this message (SlowControl Alarm) appeared long time ago - due to after refreshing of bunch current SpecificLumi became better on factor 1.5 without any tuning from HERA-people side. It is needed to remark that TCUR-bank contents was not updated too and Off-line correction of Luminosity values is impossible. But (very interesting) - it was not fixed any jump at Current Lumino- nosity value behaiviour with at 02:40 - may be Luminosity calculated right (we use not absolute values of bunch currents but its ratios). Two days ago John Coughlan said that at his last release of H1CTRIG program he made some changings and during WarmStart bunch currents will be updated too (it was after high mentioned situation). 03.06.1994 ==================== H01LNS === for RUN# Summaries ....... A little proposal for LUMI RUN# Summaries written in LLO: In RUN# Summaries there are two lines with IDENTICAL names "H1 Runs:" after which two Run-numbers follow, that can be NOT IDENTICAL. This leads to MIS-UNDERSTANDING in some cases, e.g. for "find", etc. I propose to use the two different names, in the style of Summary: "H1 total Runs:" and "H1 physics Runs:" . 03.06.1994 ==================== H01LNS === comments on DQ-meeting.... In connection with A.F.'s comments on DQ-meeting (see up): In general, I agree with the A.F.'s comments, with the exception of point 5), because the relevant to 5) text was issued by R.Gerhards, and does not correspond to my own words. That does not matter at all. Just to avoid the possible mis-understanding: At the time af the DQ-meeting all the 1)-4) reported LUMI errors really EXISTED at LUMI, and this had been already WELL KNOWN to H1. Only AFTER the DQ-meeting were made all the improovements reported by A.F. for LLO, and they should be reported for the NEXT DQ-meeting. Sorry for waisting the LLO space for such a comment, Lollii Shtarkov. P.S. You must not ask an excuse for a space: LLO just designed to exchange information/opinions. Anywhow, the space used by You and everybody else, all together is negligible compared to the stuff produced by A.Fomenko (S.L.) 3/6/94 ======================== h01usa === Lumi RUN# 405 ............ Start lumi run405 date: 3/6/94 Collision time: 13:55:36 - 18:25:51 Currents (mkA): Ie= 22800.00, Ip= 19300.00 Peak luminosity: 1045.802 mb-1 s-1 Peak spec.lumi : 459.702684 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: 7057.7352 mkb-1 H1 Run total lumi: 3508.728776 mkb-1 H1 data taken lumi: 2204.079597 mkb-1 H1 Runs: 77927 - 77953 HERA - physics: 6666.008848 mkb-1 H1Run - physics: 2935.688358 mkb-1 H1data - physics: 1806.183787 mkb-1 H1 Runs: 77939 - 77953 Tot curr/rate factor: 0.67% C/R F H1Run gated: 0.42% Rand.C.F: 1.78% RCF Run gated: 1.4% Relative ET trigg accept.: 0.3292 03.06.1994 ==================== H01LNS === NO L4 for R77939 RUN#405.. There is NO L4 histos for R77939 that was declared as the starting Run in LUMI RUN#405. On the contrary R77953 (the last in #405) is OK. 1) I dont understand what means absence of L4 (Lumi-value?). 2) Looking at the L4 histos for some SELECTED Runs is ~ nonsence. 03.06.1994 ==================== H1KFOM === Class 24 Selection........ I made attempt to select H1Lumi monitoring events from part of huge quantity of HERA03.H1POT2.MONITRIG.C9400XXX-cartridges family: a) first data set was collected from XXX=117 up to XXX=200 H1KFOM.H1LUMI.M117200.A00 K41592 78048081 00001 ACS-E-C it were recorded 137390 events with 193 Mbytes from H1 Run 76846 up to H1 Run 77224 from 25.05.94 15:02:40 up to 28.05.94 07:44:44 (Lumi RUNs #383-388) Note that data from H1Lumi Runs 77110,77111 and 77112 are included into high mentioned data set b) 2nd data set was collected from XXX=414 up to XXX=452 H1KFOM.H1LUMI.M414452.A00 K41511 78048081 00001 ACS-E-C it were recorded 23006 events with 32.7 Mbytes from H1 Run 77511 up to H1 Run 77533 from 30.05.94 18:25:56 up to 31.05.94 02:57:00 (Lumi RUN #397) It were selected only RAWD-banks (no any reconstruction banks). There are 384 MONITRIG-cartridges produced from Run 76846 up to ???? (from Lumi RUN #383 up to ????) for today: HERA03.H1POT2.MONITRIG.C9400117 L06453 78048081 00005 ACS-E-C .... HERA03.H1POT2.MONITRIG.C9400500 K39374 78048081 00001 ACS-E-C I selected H1Lumi MONITRIG events from 123 cartridges (32%). 4/6/94 ======================== h01gog === Lumi RUN# 406 Start lumi run406 date: 3/6/94 Collision time: 19:51:26 - 0:10:18 Currents (mkA): Ie= 22256.00, Ip= 19000.00 Peak luminosity: 723.454 mb-1 s-1 Peak spec.lumi : 347.765268 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: 5967.430929 mkb-1 H1 Run total lumi: 4945.836513 mkb-1 H1 data taken lumi: 2686.395347 mkb-1 H1 Runs: 77958 - 77991 HERA - physics: 5294.088689 mkb-1 H1Run - physics: 3584.157313 mkb-1 H1data - physics: 2576.579247 mkb-1 H1 Runs: 77966 - 77991 Tot curr/rate factor: 0.73% C/R F H1Run gated: 0.74% Rand.C.F: 1.95% RCF Run gated: 1.77% Relative ET trigg accept.: 0.3276 04.06.1994 ==================== F11LEV === Absence of L4 histos...... An answer to L.N.S. "... 1) I dont understand what means absence of L4 (Lumi-value?)": If H1 run is aborted rather than ended normally, then L4 histograms are absent (as well as some other information coming with the RunEnd record). Therefore, a standard request to all shifts in NH: try always "Stop the Run", not "Abort the Run". However, in a real life a system may hang up and then only "Abort Run" is possible. 4/6/94 ======================== h01gog === Lumi RUN# 407 Start lumi run407 date: 4/6/94 Collision time: 3:48:13 - 9:45:33 Currents (mkA): Ie= 18400.00, Ip= 18500.00 Peak luminosity: 549.613 mb-1 s-1 Peak spec.lumi : 313.493834 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: 5502.485049 mkb-1 H1 Run total lumi: 3588.5075 mkb-1 H1 data taken lumi: 2527.5307 mkb-1 H1 Runs: 77994 - 78022 HERA - physics: 5177.868997 mkb-1 H1Run - physics: 3087.291774 mkb-1 H1data - physics: 2469.791035 mkb-1 H1 Runs: 77996 - 78022 Tot curr/rate factor: 0.42% C/R F H1Run gated: 0.51% Rand.C.F: 1.32% RCF Run gated: 1.42% Relative ET trigg accept.: 0.3125 04.06.1994 ==================== H1KFOM === CCvc is Changing with Time It was made 100th ntuple with data from MONITRIGevents from more fresh data set: H1KFOM.H1LUMI.M414452.A00 K41511 78048081 00001 ACS-E-C with data from Lumi RUN #397. This 100th ntuple is kept at the next LOOK-binary data set: H1KFOM.ALOOKQ.R77511 FAST20 3010200E 00000 DASD There is first evidence that CCvcs is changing with time. It were tested 2 samples from high mentioned 100th ntuple: ET&PD&nVC-events (3518 events) and ET&PD&VC-events (927 events): These are the results of high mentioned test from ETrec+PDrec histo LOOK peak finder: Runs 77514 - 77533 (ET&PD&nVC-sample - 3.5K) all events xetcut vcdepcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma Mean Sigma 0 27.32 0.98 27.42 0.92 27.37 0.98 27.46 0.92 Runs 77514 - 77533 (ET&PD&VC-sample - 1.0K) all events xetcut Step Mean Sigma Mean Sigma 0 26.76 1.31 26.62 1.23 After correction of VCDEP-energy on factor 1.333(it means that really CCvcs=5.0*1.333 = 6.665 MeV/FADC count) the next results were obtained Runs 77514 - 77533 (ET&PD&VC-sample - 1.0K) all events xetcut Step Mean Sigma Mean Sigma 0 27.45 1.28 27.52 1.28 It means that Y.Soloviev's supposition (from OnLine evidence) that VC-response became too low at last time is right. HV changing at VC's PHEUs was in time - may be CCvcs must be corrected at H1DataBase (as seems incremented on factor 1.333). It would be good that we ask of H1 Run Coordinator to get little (not more then 15-20 min at start period of any Lumi Run) H1Lumi Run for more detail calibration. As seems it is possible to see this changing at CCvcs from OnLine Calibration procedure (may be relative values). 04.06.1994 ==================== H01LNS === ET_overflows at L4 ....... Warning: ET_L4_OVERFLOWS -> 71/594 ~ 12% (!) at end of #407, R78022. Of ET_tot=71: 22 in 49ch.; and spectrum in ch's 28,36,38,42,44,46,47. A usial level of L4_Overflows was ~ 0.1% before this observation. Unfortunately, there was no statistics done before now. Added:By A.F.'s request (bellow) was checked R78021 (before Overflowed) There were Zero(!) Overflows for ET=704 and PD=309. 04.06.1994 ==================== H1KFOM === Run 78022 (last at #407th) One of possible explanations of 12% overflow at H1Lumi channels during Run 78022 (from 09:43:36 up to 09:49:51) is that at this period (after lost of large part of p-beam - near 70%) something was not good with beam conditions (we looked for this type overflows during beam lost and earlier). As seems this is not alarm only warning and evidence. 70% of p-beam were lost at 09:40. Run 78022 was started at 09:43:36.p-beam was lost during previous (78021 Run) from 18.1 mA up to 4.1 mA. L.S. comment: see Up. 04.06.1994 ==================== H1KFOM === CCvc is Changing with Time It was processed more statistical data sample from Lumi RUN #397: H1KFOM.H1LUMI.M414469.A00 K11608 78048081 00001 ACS-E-C This data set was collected from MONITRIG-tapes from XXX=414 up to 469 It was produced 100th ntuple with these data. This 100th ntuple is kept at LOOK-binary data set: H1KFOM.ALOOKQ2.R77511 FAST02 3010200E 00000 DASD These are the results of high mentioned test from ETrec+PDrec histo LOOK peak finder: Runs 77514 - 77543 (ET&PD&nVC-sample -12.0K) all events xetcut vcdepcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma Mean Sigma 0 27.25 0.97 27.30 0.93 27.25 0.95 27.31 0.89 Runs 77514 - 77543 (ET&PD&VC-sample - 3.0K) all events xetcut Step Mean Sigma Mean Sigma 0 26.51 1.39 26.49 1.38 After correction of VCDEP-energy on factor 1.430(it means that really CCvcs=5.0*1.430 = 7.150 MeV/FADC count) the next results were obtained Runs 77514 - 77543 (ET&PD&VC-sample - 3.0K) all events xetcut Step Mean Sigma Mean Sigma 0 27.46 1.31 27.55 1.29 4/6/94 ======================== h01gog === Lumi RUN# 408 Start lumi run408 date: 4/6/94 Collision time: 15:07:10 - 21:20:58 Currents (mkA): Ie= 20359.00, Ip= 19801.00 Peak luminosity: 1009.783 mb-1 s-1 Peak spec.lumi : 489.881292 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 168 Number of e-pilot b.: 15 Number of p-pilot b.: 15 HERA total lumi: 8975.151327 mkb-1 H1 Run total lumi: 5363.614433 mkb-1 H1 data taken lumi: 3556.195279 mkb-1 H1 Runs: 78050 - 78071 HERA - physics: 8253.446178 mkb-1 H1Run - physics: 4219.833288 mkb-1 H1data - physics: 3218.329861 mkb-1 H1 Runs: 78058 - 78071 Tot curr/rate factor: 0.74% C/R F H1Run gated: 0.74% Rand.C.F: 1.47% RCF Run gated: 1.48% Relative ET trigg accept.: 0.3410 5/6/94 ======================== h01gog === Lumi RUN# 409 Start lumi run409 date: 4/6/94 Collision time: 22:18:50 - 3:06:32 Currents (mkA): Ie= 18808.00, Ip= 19000.00 Peak luminosity: 662.804 mb-1 s-1 Peak spec.lumi : 367.867817 mb-1 s-1 mA-2 Number of collided b.: 138 Number of e-filled b.: 150 Number of p-filled b.: 168 Number of e-pilot b.: 12 Number of p-pilot b.: 30 HERA total lumi: 5977.883216 mkb-1 H1 Run total lumi: 4459.845505 mkb-1 H1 data taken lumi: 2390.79414 mkb-1 H1 Runs: 78074 - 78105 HERA - physics: 5465.64107 mkb-1 H1Run - physics: 3996.311105 mkb-1 H1data - physics: 2330.90384 mkb-1 H1 Runs: 78081 - 78105 Tot curr/rate factor: 0.24% C/R F H1Run gated: 0.29% Rand.C.F: 1.86% RCF Run gated: 1.78% Relative ET trigg accept.: 0.3250 5/6/94 ======================== h01gog === Lumi RUN# 410 Start lumi run410 date: 5/6/94 Collision time: 4:04:31 - 8:32:01 Currents (mkA): Ie= 16120.00, Ip= 18101.00 Peak luminosity: 438.512 mb-1 s-1 Peak spec.lumi : 295.958339 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 168 Number of e-pilot b.: 15 Number of p-pilot b.: 15 HERA total lumi: 3555.22985 mkb-1 H1 Run total lumi: 3212.467065 mkb-1 H1 data taken lumi: 2303.75316 mkb-1 H1 Runs: 78123 - 78137 HERA - physics: 3268.135571 mkb-1 H1Run - physics: 2610.199745 mkb-1 H1data - physics: 2185.281829 mkb-1 H1 Runs: 78128 - 78137 Tot curr/rate factor: 0.33% C/R F H1Run gated: 0.33% Rand.C.F: 1.03% RCF Run gated: 1.02% Relative ET trigg accept.: 0.3170 05.06.1994 ==================== H1KFOM === H1Lumi2 MacII crash....... Yesterday at moment of Lumi RUN #408 finishing (during attempt of return into standard H1Lumi2 MacII operation) H1Lumi2 MacII was seriously crashed. Before this Usik had ordinary at last time manipulation with development and tuning of his last SW products. It was made rare and dangerous (as S.Burov said) operation of 'Force Quit' from one of Usik's used tools. H1Lumi2 MacII was crashed and any attempts to reboot and to make H1Lumi2 MacII at operation mode were unsuccesful. HD_LPI disk was not seen at Startup procedure. After almost one hour of different attempts to see HD_LPI with using of discette Operation System, attempts of using different Disk_Aid-tools H1Lumi2 MacII was put into operation mode by Sergey Burov (after switched off and switch On again H1Lumi2 MacII's HD_LPI alived again). May be some previous actions had some influence - but as seems H1Lumi was born under happy star. All tools at H1Lumi2 were alived without any moving from backup files etc. As result of high mentioned crashed: a) it was not made step 4 of standard manipulation during end of Lumi RUN #408: - Luminosity measurement was not disabled; - Movable Platforms were not moved into Parking Positions; - new 12 GeV e-beam which was appeared during H1Lumi2 crash put some influence of Calibration Constants (Inhibit was Off); - some measurements of Luminosity with 12 GeV beam were fixed with bunch structure which were fixed at start of Lumi RUN #408 - RunSummary for Lumi RUN #408 was fixed onle one hour later. b) it is extremly needed to be ready for high mentioned situtations and at any case all needed H1Lumi On Line SW tools must be ready for installation and accessible at any time at some Backup-tools (disketes, may be files at Unix-computers or else anywhere). As seems it is needed to fix now used H1LumiOn- LineSW-tools on MacIIs and FICs and prepare current status of backup-files. 05.06.1994 ==================== H01LNS === L4 for RUN# 408-410 ...... 1. RUN#408: At R078071, the last Run of RUN#408, something was spoiled: Eet was dubbled - a greate peak at ~ 8 GeV has appiered; KABACK! Edep-Etrig for ET has mooved to ~ 8 Gev, KABACK! Check of the previous(!) Run R078070 showed - all was YET ~ OK. "~ OK" means that there was no "peak_at_zero' for (Edep-Etrig) ET. SORRY TO REPORT THIS "CRASH" AFTER A.F.'S REPORT (SEE UP). 2. RUN#409: There were no L4 histos for 3 first Runs, then appiered; At L4 histo (Edep-Etrig)ET again the was no "peak_at_zero" (why?) Overflows were at the level of ~15 promill - warrying (RUN#409). 3. RUN#410 - all was OK. Summary: 1) L4 histos has caught the cat for the tail, 2) Dissapierence of ET_(Edep-Etrig) is warrying, 3) Overflows at ET are ready to grow, also warrying. Lollii Shtarkov, from DESY. 05.06.1994 ==================== H1KFOM === Bad Situation with H1Lumi2 Today during start of Lumi RUN #411 H1 Shift Crew cannot make Standard Operation with Movable Platforms due to not enough memory problem. I found at H1Lumi2 MacII H1TV-application and H1LumiTVmonitor -application (old and new Usik's SW product). After quit of H1TV- application the same problem was fixed. After "quit" of T_MonitorNC -application it was possible with 'non-standard' action to open MovablePlatform application and move Movable platforms into Working Positions. H1Shift Crew reported that today morning H1Lumi2 MacII was rebooted and (as seems) all applications were started from Startup-file. It means that Usik must change Startup Procedure for H1Lumi2 MacII restart for posibility of standard operations at H1Lumi2 MacII. Me and Yura asked of Usik many times - after his development and tuning actions to make reboot H1Lumi2 MacII and be shure that all standard actions it will be possible to make by H1 Shift crew. 05.06.1994 ==================== H1KFOM === Lumi = 1.28*10*30 cm-2s-1 Today at start period of Lumi RUN #411 it was fixed Current Lumi- nosity value = 1.28*10**30 cm-2s-1. Almost 20 min very high Luminosity was produced by HERA (near 1.25* *10**30 cm-2s-1. Ie = 22.73 mA after EndOfRamping, Ip=20.40 mA. Max.Spec.Lumi was fixed near 5.4*10**29 cm-2s-1mA-2. 05.06.1994 ==================== H01LNS === L4 and Reference ......... 1. There is a difference of L4_histo_(Edep-Etrig) and its REFerence: At DATA_histo there is a peak+shoulder, but at REF_histo only peak. It is a puzzle for shifters, and the difference must be remooved, that can be done by changing either DATA_H, or REF_H. 2. I propose to change the DATA_H by REMOOVING the SHOULDER, since: - The main contents of THIS histo is exactly (Edep-Etrig), - The shoulder SPOILES this info, spoiles Mean and Sigma, - The info about the shoulder is in a special, OTHER histo. 3. In this connection, changing of the relevant Reference not needed. 4. It's resonable to change the limits of Histo_(Edep-Etrig), to make the peak_at_Zero broder and better looking. Lollii Shtarkov. 05.06.1994 ==================== F11LEV === L4 and Reference ......... It was mentioned already at least 4 times that the status of L4 histos is not up-to-date. There is no sence to compare LUMI Edep-Etrig figures with reference ones until correct version of LUMMON is running at L4, because in 90% of events there is no Etrig information (LRTN is absent) New code for LUMMON L4 is ready and waits for implementation on raid boards as soon as expert is around (Monday). This is not only for LUMI: also many other histograms (at least reference plots) must be updated as well. Work is in progress. Limits for Edep-Etrig histos are changed in new LUMMON. 5/6/94 ======================== h01gog === Lumi RUN# 411 Start lumi run411 date: 5/6/94 Collision time: 13:40:24 - 18:10:09 Currents (mkA): Ie= 22737.00, Ip= 20401.00 Peak luminosity: 1272.994 mb-1 s-1 Peak spec.lumi : 515.445834 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 165 Number of p-filled b.: 168 Number of e-pilot b.: 12 Number of p-pilot b.: 15 HERA total lumi: 8659.173315 mkb-1 H1 Run total lumi: 7887.9027 mkb-1 H1 data taken lumi: 4897.9032 mkb-1 H1 Runs: 78146 - 78159 HERA - physics: 8095.687035 mkb-1 H1Run - physics: 5149.939645 mkb-1 H1data - physics: 3729.756241 mkb-1 H1 Runs: 78149 - 78159 Tot curr/rate factor: 0.22% C/R F H1Run gated: 0.21% Rand.C.F: 2.03% RCF Run gated: 1.98% Relative ET trigg accept.: 0.3362 05.06.1994 ==================== H01LNS === ET_overflows in RUN#411 .. RUN#411 is OK at L4, but: Overflows at ET are ~ 3 % in tot, they seen for all the channels, esp. channels 49; 28,36, 38, 47. 05.06.1994 ==================== H1KFOM === MONITRIG-selection ....... It were selected events of 24th class from MONITRIG-cartridges: HERA03.H1POT2.MONITRIG.C9400362 K45080 78048081 00001 ACS-E-C ..... HERA03.H1POT2.MONITRIG.C9400499 K35545 78048081 00001 ACS-E-C and it were produced data sets with 171261 events with 241.6 Mbytes. H1KFOM.H1LUMI.M360499.A00 K11039 78048081 00001 ACS-E-C H1KFOM.H1LUMI.M360499.A01 K21856 78048081 00001 ARCHIVE-E-C It was produced 100th ntuple for high mentionedn events with 148379 entries. This 100th ntuple is kept at LOOK-binary dataset: H1KFOM.ALOOKQ.R77434 FAST13 3010200E 00000 DASD Size of this LOOK-binary data set is near 15 Mbytes. Today I had negoutiations with Uwe Kruener-Marquis about our problems with selection. He promised to think about posibility to make high mentioned selection at L5-level. Now there are 744 MONITRIG-data sets (up to 500 it were moved into IBM-storage) - and most fresh are kept at dice2-environment at non-accessible for users storage. For us it would be very good if Uwe decide to make class 24 selection at L5-level. It is huge work to make selection from all MONITRIG-tapes after its creation (class 24 keeps CPU-time during selection but there are a lot of problems with stagin-procedure etc.). 6/6/94 ======================== h01gog === Lumi RUN# 412 Start lumi run412 date: 5/6/94 Collision time: 19:09:31 - 0:54:38 Currents (mkA): Ie= 21682.00, Ip= 19700.00 Peak luminosity: 1049.259 mb-1 s-1 Peak spec.lumi : 458.702485 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 165 Number of p-filled b.: 168 Number of e-pilot b.: 12 Number of p-pilot b.: 15 HERA total lumi: 9109.284954 mkb-1 H1 Run total lumi: 7747.434274 mkb-1 H1 data taken lumi: 6000.554598 mkb-1 H1 Runs: 78160 - 78174 HERA - physics: 8550.646093 mkb-1 H1Run - physics: 6729.829965 mkb-1 H1data - physics: 5870.28342 mkb-1 H1 Runs: 78164 - 78174 Tot curr/rate factor: 0.6% C/R F H1Run gated: 0.59% Rand.C.F: 1.51% RCF Run gated: 1.48% Relative ET trigg accept.: 0.3282 06.06.1994 ==================== H01LNS === PD_overflows at L4 ....... RUN#412 is OK at L4, but: Overflows, now at PD, not huge, at the level of 1 %, all in ch 12. 06.06.1994 ===================== H1KSHE === ...explanations........... Here i'v tryed answer to L.S.V. , S,L,N and everybody who are interesting, sorry for delay. The explanations which given by A.M. are mostly correct. For Rate/Current factor: It shows integral difference between luminosity trigger rates (background is subtracted) calculated by usual way and accoding by my procedure(see LLO5). L.C.F = (LumiRate Cur.Norm. - LumiRate Rate.Norm)/LumiRate Cur.Norm I have some thought related with inaccounted background effects for which this value is probably sensitive. The Random Coincidence Factor is calculated by following way: LRET => Lumi Rate of ET (ET background is subtracted) LRPD => Lumi Rate of PD (PD background is subtracted) BRET => BackgRate of ET BRPD => BackgRate of PD TotETPD => Total ET,PD Lumi Rate (backgr is subtracted) R.C.F = {Rand.Coinc(LRET,BRPD) + Rand.Coinc(LRPD,BRET)}/TotETPD The Relative ET trigger acceptance is attempt to monitor one by using the relative trigger rates behaviour. But i had not possibility to ajust some options on the real beam conditios and check is it realy works or not. I will tune it in September. All values are included in run summary now basicaly for monitor purposes. 06.06.1994 === LPI-DESY === Congratulations for H1KSHE ================ The Russian Community of DESY-H1 0000 Hartly congratulates Marina and Igor Sheviakovi 0000 on the occassion of Birth of the Second Sun !!! 0000 Be happy, Have a long-long Life, and many more children !!! 0000 06.06.1994 ==================== H1KFOM === FIC#1 Replace Status..... Today during temporary access time period it was made attempt of FIC#1 replacement on more powerful (FIC8230--->FIC8231 with Motorola 68030 microprocessor on the board). Y.Soloviev,S.Burov and E.Elsen were involved into this procedure. Igor Sheviakov was at Pitomnik,Moscow at TSO DESYIBM and had phone talking before high mentioned attempt with Eckhard Elsen. He agreed that it is possible to try changing (may be temporary) and to look what happens. First H1Run with new FIC#1 (78229) was started at 11:14:38 and was finished with crash of H1LumiOnLineProgram (SPUR-exeption) at 11:15:27. It was colllected 741 events with L2Keep-rate near 15.1 Hz. Second Run (78230) was 'more succesful'. It was started at 11:18:21 and it was collected 10249 events up to crash of H1LumiOnLineFIC#1- program. This crash was more serious - as seems it was blocked H1Lumi's Master Crate VME-bus with VSB-access - it means that at this period both MacII had only BusErrors on any attempt of access to DPM-modules and no any memory was visible from H1Lumi MaCII. Attempt to reboot H1Lumi MacII does not help - memory was unseen from H1Lumi MacII. Attempt to reset H1Lumi's Master crate from Bill's button was unsucces- ful too. Only switching off and switching on again of master crate helped at this situtaion. After these attempts E.Elsen left our company for Off-Line analyze of data from Run 78230 (timing, etc.). He promised to inform us about investigated values. Luminosity branch was Off from H1CDAQ due to needs on some another important investigations at H1. Old H1Lumi's FIC#1 was back into H1Lumi Master Crate. At 13:35 Luminosity branch was ON at H1CDAQ and succesfully worked up to 14:24 (H1Runs 78247,78248,78249,78250 were finished with EndRunProcedure - we have LRTS-banks at RunEndRecords). During Running 78251 crash appeared at H1LumiOnLineFIC#1-program and Luminosity branch was Off from H1CDAQ again. L2Keep rates which were fixed at all high mentioned Runs: 78229 - 741 events / 49 sec / 15.1 Hz - SPUR exeption 78230 - 10249 events / 665 sec. / 15.4 Hz - VSB-blocked VME-access 78247 - 14187 events / 808 sec. / 17.6 Hz - OK 78248 - 12679 events / 688 sec. / 18.4 Hz - OK 78249 - 12314 events / 700 sec. / 17.6 Hz - OK 78250 - 6088 events / 336 sec. / 18.1 Hz - OK 78251 - 2665 events / 178 sec. / 15.0 Hz - crash of H1LumiOnLineFIC1 06.06.1994 ==================== H1KFOM === Integrated Lumi Problem.. Yesterday A.Usik fixed with his new tool (at picture with behaivours of Hera Produced, H1 Gated and H1 Data Taken with time) some strange situations during Lumi Run #412: a) near 20:00 H1 Gated and H1 Data Taken Integral Lumi values were decremented on value near 20-25 % (HERA Produced value was not decremented); b) near 21:40 H1 Gated and H1 Data Taken Integral Lumi values were decremented on value near 12-15 % (HERA Produced value was not decremented). Both these time periods (as seems) connected with Stop/Start H1 Run: a) Run 78167 from 19:55:54 up to 20:02:55; Run 78168 from 20:03:32 up to 20:21:40. b) Run 78170 from 21:21;20 up to 21:42:36; Run 78171 from 21:43:13 up to 21:53:08. As You can see no any WarmStart Runs were not fixed at this time periods. Today it was produced LOOK-binary data set: H1KFOM.LOOKA.R78164 FAST13 3010200E 00000 DASD after processing of H1RAWD-cartridges at dice2-environment (1171-1175) At 903 and 904 vectors which are kept at this data set it is possible to see that no any jumps (as it was seen at OnLine) presents at high mentioned time periods with H1 Gated and H1 Data taken Lumi values (additinal cross check was made with recalculation of these values from LRTN-bank values). No any significant discrepancies from LRTL- Integrated values. First two values of Inegrated Lumi are from LRTL-bank and next two two values are from recalculation procedure (difference at H1 Data Taken values (Eff.) is due to large fluctuated H1 Dead Time): 78167 940605 195554 940605 200255 0 1 42 0 0 0 0 0.000 Int.Lumi=30986753; Eff.=24266768;Int.=30170642;Eff.=26830702 78168 940605 200332 940605 202140 0 1 109 0 0 0 0 0.000 Int.Lumi=76007488; Eff.=61650787;Int.=74439334;Eff.=66631454 78170 940605 212120 940605 214236 0 1 126 0 0 0 0 0.000 Int.Lumi=54572394; Eff.=48694850;Int.=54714808;Eff.=48667671 78171 940605 214313 940605 215308 0 1 56 0 0 0 0 0.000 Int.Lumi=22137120; Eff.=16345416;Int.=22252076;Eff.=19792755 T0 at high mentioned vectors is 05.06.94 19:35:16. As seems registered at OnLine jumps at high mentioned values had not influence on value of these values at tapes. It is strange - due to getting of this information from the same place both for LRTL-bank and for Usik's and Egor's Show and RunSummary tools. 06.06.1994 ==================== H1KFOM === MONITRIG-selection....... Today no any progress with H1Lumi MONITRIG-selection was made due hard situation with stagin procedure at dice2 and very quickly disappearing of staged data sets from dice2- h1stage area. 06.06.1994 ==================== H1KFOM === FIC#1-replace status..... READMAIL message stored : MON, 6 JUN 94 20:10:49 MESZ Date: MON, 6 JUN 94 19:45:04 +0200 From: Eckhard Elsen Subject: re: replace of h1lumi fic#1 To: Alexander Fomenko Eckhard Elsen H1 Collaboration, DESY - FH1K - Notkestrasse 85, 22603 Hamburg, Germany Tel. (040) 8998-2565 (secr. ext. 3144, fax 3093) Dear Sascha, thank you for the detailed report. I have in the meantime analysed two runs, one with old FIC and one with new FIC. The result is that the improvement is really marginal. Run 1st FER rms(FER) Processor 78199 1.593 1.632+-0.001 0.071 68020 old 78230 1.574 1.619+-0.001 0.079 68030 new It is clear that the improvement is at the 1% level. The 68020 is already running at 25 MHz and we cannot gain much. In view of that we should switch back to 68020 processor as early as possible to have stable running. Thank you for the effort; do you see potential to optimize the program further? This seems to be the only way to reduce deadtime. Best regards, Eckhard 06.06.1994 ==================== F11LEV === Lumi value and dead time Two remarks on the earlier messages of Fomenko. 1) Integrated lumi value. I also have seen last time (2 days at least) that the integrated H1 lumi from the database is larger than that in the online Run summary I told this to Yura and sofar no explanation was found. 2) Concerning Eckhard's remark. Do you have an idea where the time is mainly spent? Can you for example to make a timing for the different procedures running during the standard data taking (lumi calibration if it influences dead time, readout, banks creation, supporting other systems (VETO, Roman Pots, Neutron counter), lumi calculation, reconstruction, histogramming etc.) It would be interesting and may show where one can improve. 07.06.1994 ==================== H1KFOM === H1Lumi's Dead Time...... Short answer on Sergey's remark about dead time: a) time is mainly spent at L2Keep.f-subroutine algorithm: - this subroutine is activated immediately after H1CTRIG's L2Keep- signal; - at this time all pipe-lines are stopped and it is possible to make reading of needed data (FADCs,GPTPs,SlowCard,FastCard etc.) H1 Dead Time is started. - after reading of all needed data for current H1 Events L2Keep.f- suroutine sends signal "FrontEndReady" (FER) to H1CTRIG. It means that Luminosity branch finished reading of needed data at stopped pipe-lines; - H1CTRIG after FERs receiving from all branches (11 now) 'starts' pipe-lines again up to new L2Keep-signal; - time between L2Keep-signal and 'All FER are received' is pure H1 Dead Time. b) sometimes (last Egor's93 update) FER from Luminosity branch is sent not from L2Keep.f subroutine but from IlevelA.f-subroutine (it means that sometimes Luminosity branch is issuing FER after 10 msec - due algorithm scheme and up to 100 msec at practice(not understandable yet)). But as seems it is negligable part of L2Keep-events with so large FER-time from Luminosity branch (see earlier explanations at LLC). c) main part of L2Keep-events have 1.6 msec FER-time (from L2Keep.f -subroutine) - see Eckhard's results; d) this time is spent on: 1) reading of 76 channels from 5 FADCs (49et + 25 pd + 2vc); LREE,LRPE,(LREF,LRPF) - banks 2) reading of SlowCard and FastCard data; TSTC-bank 3) reading of 2 GPTP-modules for VETE-bank contents for H1VetoWall; VETE-bank top area 4) reading of 1 GPTP-module for Roman Pots system; VETE-bank bottom area 5) reading of 12 channels from 1 FADCs (11nc + 1 spare). LRNA-bank. e) H1Lumi's trigger sums are reading once per 10 L2Keep-events and are not included into high mentioned 1.6 msec. LRTN,LRTF-banks. f) if we shall exclude VETE-bank and LRNA-bank from H1Lumi Readout we shall accelerate H1Lumi readout up to 1.0-1.1 msec (at first peak); g) Egor said that now is preparing for mass production new bit pipe- line modules (GPTP-type) with better readout procedures - it means that there are some hopes on improvements connected with GPTP- modules replace on new modules (at future - if it will be possible); h) as I know LRNA-bank is temporary presented at H1Lumi Data Flow - may be only at H1 Data Taking'94 - so there are some hopes at future on excluding readout for LRNA-bank; i) all H1Lumi KEEP-banks have not any influence on high mentioned first peak FER-time; j) calibration procedure, Luminosity measurements and all another processes at FIC#2-environment have no any influence on high mentioned FER-time too. k) bank creation which is made at IlevelA.f -subroutine have indirrect influence on part of events with large FER (number of FER from IlevelA.f can be more if now existed 10ms per L2Keep-event will be incremented) but there is no influence on first peak FER-time. l) IlevelA.f-subroutine algorithm is connected with H1Lumi dead line L2keep-events (now this digit is near 100-110 Hz - it means near 10 msec per all procedure for preparing of one event H1Lumi banks for H1Data Flow). 07.06.1994 ==================== H1KFOM === MONITRIG selection at IBM Today I tested rate of H1Lumi's MONITRIG events selection with CLASS= 24 option ( with the same options which were used at dice2). One HERA03.H1POT2.MONITRIG.C9400341-data set was processed 1min.08sec CPU time of DESY IBM (near 5 min.of calendar time). //H1KFOM06 JOB 00010221,CLASS=K,TIME=(00,00),MSGLEVEL=(2,0), // NOTIFY=H1KFOM,MSGCLASS=T //* SUBMITTED MEMBER: H1KFOM.MONITRIG($SELECT ) OPEN> File opened:H1KFOM.H1LUMI.M341341.A00 IEF375I JOB /H1KFOM06/ START 94158.1624 IEF376I JOB /H1KFOM06/ STOP 94158.1629 CPU 1MIN 08.36SEC SRB N 01.25 07.06.1994 ==================== H01LNS === Data-Quality Meeting ..... A copy of report made by L.Shtarkov, by request of S.Levonian: (Transparency) STATUS OF LUMI 31.05.94 - 07.06.94 After the last DQ-Meeting 1. All the LUMI errors that were reported at the last DQ-Meeting were already fixed during the next day. 2. Most of the time (see later) the Hardware+OnLine of LUMI were working OK, as it is seen at the L4 histos. Values of Luminosity and Summaries are issued as usially. 3. Some incident had happened at the end of Run 78071. One of the two Mac's had crashed at the standard operation, and the Run ending step 4 was not compleated. This incident was well detected at the L4 level: Energy peak of ET-detector was dubbled, and the peak of (Edep-Etrig) for ET was mooved from Zero to ~8Gev. 4. One of our problems has become selecting of LUMI- events from MONITRIG-cartriges, because, for checking the Data-Quality, we need all the Monitoring statistics. On the possibility to make this selection at the L5-level, there were talks of A.Fomenko and Uwe Kruener-Marquis. The point 4. was discussed, esp. by J.Olsson and R.Gerhards, It is necessary to ask H1 for help in this problem. 8/6/94 ======================== h01gog === Lumi RUN# 413 Start lumi run413 date: 8/6/94 Collision time: 0:29:57 - 3:47:02 Currents (mkA): Ie= 18445.00, Ip= 30600.00 Peak luminosity: 885.506 mb-1 s-1 Peak spec.lumi : 306.226718 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 168 Number of e-pilot b.: 15 Number of p-pilot b.: 15 HERA total lumi: 5059.205464 mkb-1 H1 Run total lumi: 2601.204042 mkb-1 H1 data taken lumi: 857.006686 mkb-1 H1 Runs: 78365 - 78392 HERA - physics: 4772.486339 mkb-1 H1Run - physics: 1912.127189 mkb-1 H1data - physics: 757.469269 mkb-1 H1 Runs: 78381 - 78392 Tot curr/rate factor: 0.45% C/R F H1Run gated: 0.39% Rand.C.F: 1.29% RCF Run gated: 1.17% Relative ET trigg accept.: 0.3336 8/6/94 ======================== i04zbk === Lumi RUN# 414 Start lumi run414 date: 8/6/94 Collision time: 4:51:47 - 7:31:44 Currents (mkA): Ie= 20631.00, Ip= 27400.00 Peak luminosity: 887.506 mb-1 s-1 Peak spec.lumi : 323.631504 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 168 Number of e-pilot b.: 15 Number of p-pilot b.: 15 HERA total lumi: 4254.580054 mkb-1 H1 Run total lumi: 3459.547749 mkb-1 H1 data taken lumi: 2191.271183 mkb-1 H1 Runs: 78397 - 78410 HERA - physics: 3915.604278 mkb-1 H1Run - physics: 2650.142889 mkb-1 H1data - physics: 1679.580797 mkb-1 H1 Runs: 78403 - 78410 Tot curr/rate factor: 0.64% C/R F H1Run gated: 0.64% Rand.C.F: 1.61% RCF Run gated: 1.58% Relative ET trigg accept.: 0.3535 8/6/94 ======================== === Lumi RUN# 415 Start lumi run415 date: 8/6/94 Collision time: 9:48:16 - 10:00:35 Currents (mkA): Ie= 8620.00, Ip= 25300.00 Peak luminosity: 309.427 mb-1 s-1 Peak spec.lumi : 277.348834 mb-1 s-1 mA-2 Number of collided b.: 152 Number of e-filled b.: 166 Number of p-filled b.: 168 Number of e-pilot b.: 14 Number of p-pilot b.: 16 HERA total lumi: 221.207952 mkb-1 H1 Run total lumi: 156.717915 mkb-1 H1 data taken lumi: 39.512889 mkb-1 H1 Runs: 78416 - 78418 HERA - physics: 183.896409 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 78418 - 78418 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 1.54% RCF Run gated: 1.51% Relative ET trigg accept.: Not calc. 8/6/94 ======================== === Lumi RUN# 416 Start lumi run416 date: 8/6/94 Collision time: 11:16:40 - 11:19:51 Currents (mkA): Ie= 10647.00, Ip= 24900.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.: 168 Number of e-pilot b.: 15 Number of p-pilot b.: 15 HERA total lumi: 28.7624 mkb-1 H1 Run total lumi: 28.762472 mkb-1 H1 data taken lumi: 0 mkb-1 H1 Runs: 78430 - 78430 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 78430 - 78430 Tot curr/rate factor: 0.92% C/R F H1Run gated: 0.92% Rand.C.F: 5.93% RCF Run gated: 5.93% Relative ET trigg accept.: Not calc. 08.06.1994 ==================== H1KFOM === New p-beam Bunch Structure Today it was fixed (firstly) new p-beam bunch structure - 3 zugs with 50 bunches each (as it was promised 2 weeks ago at ZEUSBEAM-pinboard). It was only attempt to use new p-beam bunch structure. At next Lumi RUNs it was used old one - 60 + 60 + 50. 09.06.1994 ==================== H01GOG === MONITRIG cartridges I have checked up the presence of MONITRIG cartridges in HERA03.H1POT2.MONITRIG.C9400XXX ( XXX = 200 - 952). Below is following the list of the tapes which are absent: HERA03.H1POT2.MONITRIG.C9400745, 748, 750, 752, 754, 758-764, 766, 768-769, 772, 774-777, 780, 783-787, 789, 791, 792, 795, 796, 798, 800, 801, 802, 805, 807, 811, 813, 817-820, 825-828, 831, 833, 837, 854-858, 942-944, 946. By the way, I have seen the movement of the tapes yesterday (08.06.94). Some tapes have appeared some have disappeared (763,786 854) 09.06.1994 ==================== H1KSHE === Speed up online Probably there are numerious versions for modernisation of LUMI system readout now. I'd like to know your opinion about my old suggestion which i give here. The problem of LUMIDAQ dead time was clear since ~93 after last CDAQ and CTRIG updates. It was also clear that the system must have some spare posibilites for future developments. From the number of suggestions to speed up the LUMIDAQ responce the most attractive for me is the following one. I had supposed that for the critical situation all time exist possibility to use the second FIC (or MAC II) to split the data control between two processors. For instance, half data reading and bank creation for one and half for second. To not destroy timing and sequence of operations one processor will have the master status as before with only difference: it will produce relevant level interruptions and may be some flags to control the second processor. This solution will not cause any unwaitable VME bus activity due to the second processor keep silence until new interrupt come. I think for speed up the factor ~2 can be reached. No any new specific hardware for this solution is need. In prin- ciple from H/W point of view just relevant interrupt handling procedures must be done properly. Finaly i'd like to emphasize the following features: 1. Speed up factor ~2 2. No any change in banks structure is need. 3. No any principle hardware changing. 4. Not need to change the basic readout and bank creation routines. 5. The old version of LUMIDAQ is not destroied(to come back just reloard the old version of programm) 6. The business is more less familiar and can be done soon. Because of our second FIC now is very busy by luminosity calculations it would be nice to have additional FIC(68020) (third in the system) for this purpose. 09.06.1994 ==================== H1KFOM === Speed up online As I know there are another proposals: b) to put some operations for H1Lumi-bank creation into L4-level; c) to try new GPTP-type modules; d) to try more internal buffers; e) proposal with zero-suppression of LRNA-bank; etc. Shortly about each proposal: a) Igor's proposal is very good but: now we have 4 processors which are operated with Master Crate VME-bus (FIC#1, FIC#2, H1Lumi2 MacII and H1Lumi MacII). Sometimes we can see 'bus errors' due to VME- bus busy status at lowest priority H1Lumi MacII. Priority distri- butions are the next - FIC#1-highest, H1Lumi MacII- lowest, between FIC#2 and H1Lumi2 MacII - FIC#2 less then FIC#1 and more then H1Lumi MacII and H1Lumi2 MacII is between FIC#2 and H1Lumi MacII. I am afraid that 5th processor at H1Lumi Master Crate can be the reason of bus-errors at all processors which will be with priority less then FIC#1a (FIC#2, H1Lumi2 MacII and H1Lumi MacII). Up to now we have not any protection from Bus Error situations at both FICs (Bus error at any from FIC will be finished with crash of FIC's program). Bill's VME-taxi module (as seems) can access to our VME-bus. Igor always said on this type remarks that it must be no problems with high mentioned bus errors situations if priorities of processors are distributed right - we far from dead line of VME-bus critical speed etc. But sometimes (may be due to specific data flows at each from high mentioned processors) I see that bus errors can appear and not due to some algorithm errors - due to 'overloading' of VME-bus. b) most attractive proposal (L4) - but: - no any influence on 1.6 msec FER-dead time - only (due to 10 msec must be reduced on factor 2-5) must be up dead line of Luminosity branch (from 100 Hz to 200-500(?)) and really must disappear situations with large FER - Luminosity branch can produce LREF and LRPF banks (which are source for LREE and LRPE - after linearization, pedestal substraction, FADC count making, bank creation etc.). Producing of LREE and LRPE-banks it will be possible to make at L4 level. But we must reject LREF and LRPF from H1DataFlow (or make its zero suppressed) at L4 level.Before this it was made at H1Lumi (we have special option for suppressing of LREF and LRPF-banks). - only high mentioned banks will be produced at L4 level (VETE, LRNA are made without any proccesing - only data moving). - in principal we have some mode for data transfer now - without LREE and LRPE creation and we can immediately test which will profit from L4-involving into LREE and LRPE-production; c) really must be tested and introduced - due to main influence on 1.6 msec FER-time; d) no any influnece on 1.6msec FER but really (may be) can decrement procent of event with large FER (but I am not shure); may be it is used all power of 68020 even for 8 internal buffers; it is seen from absence of any BG-operations at FIC#1; e) no any influence on 1.6 msec FER-time but will keep data storage (making of zero suppressed no so simple - it can incrememt 10msec time on bank preparing time - dead line of Luminosity branch (100H z) can decrement and it will be produce more procent of events wit large FER). May be it will be possible together with L4 - as it was proposed for case LREF,LRPF-->LREE,LRPE. 09.06.1994 ==================== H01GOG === MONITRIG selection I have selected the events of 24th class from MONITRIG cartridges: HERA03.H1POT2.MONITRIG.C9400201 ............................... ............................... ............................... HERA03.H1POT2.MONITRIG.C9400220 The following data sets were produced: 1/ H01GOG.H1LUMI.M201210.A00 ( input 10 cartridges C9400201-C9400210, 8368 events,11808720 bytes) 2/ H01GOG.H1LUMI.M211220.A00 ( input 1 cartridge C9400211, 679 events, 970200 bytes) 3/ H01GOG.H1LUMI.M212213.B00 ( input 2 cartridges C9400212-C9400213, 1206 events, 1718640 bytes) 4/ H01GOG.H1LUMI.M214220.A00 ( input 7 cartridges C9400214-C9400220, 3564 events, 5045040 bytes) 9/6/94 ======================== === Lumi RUN# 417 Start lumi run417 date: 9/6/94 Collision time: 7:57:27 - 8:05:54 Currents (mkA): Ie= 2997.00, Ip= 21001.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.: 168 Number of e-pilot b.: 0 Number of p-pilot b.: 168 HERA total lumi: 1.5861 mkb-1 H1 Run total lumi: 1.586121 mkb-1 H1 data taken lumi: 1.512289 mkb-1 H1 Runs: 78492 - 78492 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 78492 - 78492 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 20.34% RCF Run gated: 20.34% Relative ET trigg accept.: Not calc. 10/6/94 ======================= === Lumi RUN# 418 Start lumi run418 date: 9/6/94 Collision time: 21:48:51 - 2:54:56 Currents (mkA): Ie= 15555.00, Ip= 33101.00 Peak luminosity: 1279.763 mb-1 s-1 Peak spec.lumi : 479.743934 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 168 Number of e-pilot b.: 15 Number of p-pilot b.: 15 HERA total lumi: 12567.0296 mkb-1 H1 Run total lumi: 10057.647582 mkb-1 H1 data taken lumi: 8431.681921 mkb-1 H1 Runs: 78560 - 78612 HERA - physics: 11916.524438 mkb-1 H1Run - physics: 9060.851433 mkb-1 H1data - physics: 7560.660518 mkb-1 H1 Runs: 78576 - 78612 Tot curr/rate factor: 0.43% C/R F H1Run gated: 0.44% Rand.C.F: 1.05% RCF Run gated: 1% Relative ET trigg accept.: 0.3533 10.06.1994 ==================== H1KFOM === MONITRIG selection I have selected the events of 24th class from MONITRIG cartridges: HERA03.H1POT2.MONITRIG.C9400801 (800,802,805,807,811 data- ...............................sets were absent at IBM-storage) HERA03.H1POT2.MONITRIG.C9400854 The following data set was produced: H1KFOM.H1LUMI.M801854.A00 (input 50 cartridges C9400801-C9400854 exept high ment.,70209 events) I have selected the events of 24th class from MONITRIG cartridges: HERA03.H1POT2.MONITRIG.C9400340 ............................... HERA03.H1POT2.MONITRIG.C9400359 The following data set was produced: H1KFOM.H1LUMI.M340359.A00 (input 20 cartridges C9400340-C9400359 ,????? events) 10/6/94 ====================== charles === Lumi RUN# 419 Start lumi run419 date: 10/6/94 Collision time: 4:12:11 - 10:58:20 Currents (mkA): Ie= 15078.00, Ip= 32700.00 Peak luminosity: 972.33 mb-1 s-1 Peak spec.lumi : 402.855992 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 168 Number of e-pilot b.: 15 Number of p-pilot b.: 15 HERA total lumi: 14702.925966 mkb-1 H1 Run total lumi: 13603.6011 mkb-1 H1 data taken lumi: 9415.8592 mkb-1 H1 Runs: 78614 - 78635 HERA - physics: 13595.91111 mkb-1 H1Run - physics: 12324.147777 mkb-1 H1data - physics: 8260.089421 mkb-1 H1 Runs: 78617 - 78635 Tot curr/rate factor: 0.31% C/R F H1Run gated: 0.33% Rand.C.F: 0.96% RCF Run gated: 0.96% Relative ET trigg accept.: 0.3286 10.06.1994 ==================== H01GOG === MONITRIG selection on IBM It looks like that the MONITRIG selection procedure on IBM is more convenient and fast then on DICE2. I have selected events of 24th class from 139 MONITRIG cartridges (CLASS=L, PERPRI=LOW): HERA03.H1POT2.MONITRIG.C9400221 ............................... HERA03.H1POT2.MONITRIG.C9400359 Unfortunately, because of the time limit, 2 jobs failed (with input cartridges C9400261-C9400270. I have divided these cartridges in 3 jobs and submited them once again). The following data sets were produced: H01GOG.H1LUMI.M221225.A00 K10825 78048081 00001 ACS -C H01GOG.H1LUMI.M226230.A00 K22344 78048081 00001 ACS -C H01GOG.H1LUMI.M231235.A00 K10852 78048081 00001 ACS -C H01GOG.H1LUMI.M236240.A00 K14319 78048081 00001 ACS -C H01GOG.H1LUMI.M241245.A00 K40661 78048081 00001 ACS -C H01GOG.H1LUMI.M246250.A00 K42124 78048081 00001 ACS -C H01GOG.H1LUMI.M251255.A00 K39304 78048081 00001 ACS -C H01GOG.H1LUMI.M256260.A00 K41737 78048081 00001 ACS -C H01GOG.H1LUMI.M271275.A00 K45492 78048081 00001 ACS -C H01GOG.H1LUMI.M276280.A00 K12055 78048081 00001 ACS -C H01GOG.H1LUMI.M281285.A00 K45513 78048081 00001 ACS -C H01GOG.H1LUMI.M286290.A00 K10459 78048081 00001 ACS -C H01GOG.H1LUMI.M291295.A00 K33920 78048081 00001 ACS -C H01GOG.H1LUMI.M296300.A00 K35432 78048081 00001 ACS -C H01GOG.H1LUMI.M301305.A00 K35799 78048081 00001 ACS -C H01GOG.H1LUMI.M306310.A00 K36066 78048081 00001 ACS -C H01GOG.H1LUMI.M311315.A00 K35506 78048081 00001 ACS -C H01GOG.H1LUMI.M316320.A00 K35125 78048081 00001 ACS -C H01GOG.H1LUMI.M321325.A00 K10599 78048081 00001 ACS -C H01GOG.H1LUMI.M326330.A00 K10584 78048081 00001 ACS -C H01GOG.H1LUMI.M331335.A00 K35651 78048081 00001 ACS -C H01GOG.H1LUMI.M336340.A00 K36081 78048081 00001 ACS -C H01GOG.H1LUMI.M341345.A00 K36022 78048081 00001 ACS -C H01GOG.H1LUMI.M346350.A00 K13958 78048081 00001 ACS -C H01GOG.H1LUMI.M351355.A00 K14406 78048081 00001 ACS -C H01GOG.H1LUMI.M356359.A00 K13396 78048081 00001 ACS -C 10.06.1994 ==================== H1KFOM === MONITRIG Selection Status Status of intermediate data sets with H1Lumi MONITRIG-events on today (14:00) after tonight L-class LOW-priority jobs with 5 data sets per job which were submitted by Nelly and Yura. Into full list it were added H1KFOM-data sets which were proclaimed earlier and new ones: Digits at data sets names mean MONITRIG numbers range (from ... up..) H1KFOM.H1LUMI.M117200.A00 5 data sets were absent(125,147,148,192,193)-C 13 data sets were skiped (non Lumi RUN) 174-186 H01GOG.H1LUMI.M201210.A00 K12511 78048081 00001 ACS-E-C H01GOG.H1LUMI.M211220.A00 K10263 78048081 00001 ACS-E-C H01GOG.H1LUMI.M212213.B00 K19077 78048081 00001 ACS-E-C H01GOG.H1LUMI.M214220.A00 K10346 78048081 00001 ACS-E-C 2 from Nelly's jobs will be recalculated due to time limit was riched: H01GOG.H1LUMI.M221225.A00 K10825 78048081 00001 ACS-E-C H01GOG.H1LUMI.M226230.A00 K22344 78048081 00001 ACS-E-C H01GOG.H1LUMI.M231235.A00 K10852 78048081 00001 ACS-E-C H01GOG.H1LUMI.M236240.A00 K14319 78048081 00001 ACS-E-C H01GOG.H1LUMI.M241245.A00 K40661 78048081 00001 ACS-E-C H01GOG.H1LUMI.M246250.A00 K42124 78048081 00001 ACS-E-C H01GOG.H1LUMI.M251255.A00 K39304 78048081 00001 ACS-E-C H01GOG.H1LUMI.M256260.A00 K41737 78048081 00001 ACS-E-C H01GOG.H1LUMI.M271275.A00 K45492 78048081 00001 ACS-E-C H01GOG.H1LUMI.M276280.A00 K12055 78048081 00001 ACS-E-C H01GOG.H1LUMI.M281285.A00 K45513 78048081 00001 ACS-E-C H01GOG.H1LUMI.M286290.A00 K10459 78048081 00001 ACS-E-C H01GOG.H1LUMI.M291295.A00 K33920 78048081 00001 ACS-E-C H01GOG.H1LUMI.M296300.A00 K35432 78048081 00001 ACS-E-C H01GOG.H1LUMI.M301305.A00 K35799 78048081 00001 ACS -C H01GOG.H1LUMI.M306310.A00 K36066 78048081 00001 ACS -C H01GOG.H1LUMI.M311315.A00 K35506 78048081 00001 ACS -C H01GOG.H1LUMI.M316320.A00 K35125 78048081 00001 ACS -C H01GOG.H1LUMI.M321325.A00 K10599 78048081 00001 ACS -C H01GOG.H1LUMI.M326330.A00 K10584 78048081 00001 ACS -C H01GOG.H1LUMI.M331335.A00 K35651 78048081 00001 ACS -C H01GOG.H1LUMI.M336340.A00 K36081 78048081 00001 ACS -C H01GOG.H1LUMI.M341345.A00 K36022 78048081 00001 ACS -C H01GOG.H1LUMI.M346350.A00 K13958 78048081 00001 ACS -C H01GOG.H1LUMI.M351355.A00 K14406 78048081 00001 ACS -C H01GOG.H1LUMI.M356359.A00 K13396 78048081 00001 ACS -C H1KFOM.H1LUMI.M340359.A00 K17699 78048081 00001 ACS-E-C H1KFOM.H1LUMI.M360499.A00 16 data sets were absent (364,391-396,402-404-C H1KFOM.H1LUMI.M360499.A01 421,441,450,457,485,492)-C 3 from Yura's jobs will be recalculated due to time limit was riched: H1KSOL.H1LUMI.M647651.A00 * K30317 78048081 00001 ACS-E-C H1KSOL.H1LUMI.M652656.A00 * K42294 78048081 00001 ACS-E-C H1KSOL.H1LUMI.M657661.A00 K41800 78048081 00001 ACS-E-C H1KSOL.H1LUMI.M662666.A00 K31163 78048081 00001 ACS-E-C H1KSOL.H1LUMI.M667671.A00 K43849 78048081 00001 ACS-E-C H1KSOL.H1LUMI.M672676.A00 K31751 78048081 00001 ACS-E-C H1KSOL.H1LUMI.M677681.A00 K31437 78048081 00001 ACS-E-C H1KSOL.H1LUMI.M682698.A00 K32502 78048081 00001 ACS-E-C H1KSOL.H1LUMI.M699703.A00 * K30792 78048081 00001 ACS-E-C H1KFOM.H1LUMI.M801854.A00 5 data sets were absent(800,802,805,807,811)-C Comment:files with * mark have to be recalculated they will be removed from directory H1KSOL(Yu.S) 10.06.1994 ==================== H01GOG === MONITRIG cartridges I have checked up (11:57:15) the presence of MONITRIG cartridges in HERA03.H1POT2.MONITRIG.C9400XXX ( XXX = 117 - 988). For the time being only one tape is absent: HERA03.H1POT2.MONITRIG.C9400125 10.06.1994 ==================== H1KFOM === Data for e48-test........ Today S.Levonian proposed to collect H1DataFlow from current Lumi RUN #420 with LREF and LRPF banks for possible using of data from high mentioned Lumi RUN for e48-analysis. All previous collection and analyze of e48 response show that it is needed additional cut for e48-response analyse - front position of e48 pulse. During all H1Runs at Lumi RUN #420 it was switched ON LREF and LRPF banks. 10.06.1994 ==================== H1KFOM === Beam Currents Problem.... Before start of Lumi RUN #420 something happened with LAN-connection between H1CTRIG and H1Lumi MacIIs. Only switching on of spare H1CTRIG MacII(307 room) into BeamCurrent transmission process for H1Lumi MacII helped at this situation. Thanks to John Coughlan. Beam Current Transmiision alived only in 5 min. before e-beam ramping. It was sent message into HERA Control Room - "Problems with Beam Currents Server". As seems 'struggle' with high mentioned situation could start earlier but Usik closed Egor's application for his ordinary at last time development manipulatons at H1Lumi2 MacII and alarm was not seen at H1 Slow Control. As seems it is needed to keep H1Lumi2 MacII at standard operation mode at all important moments for preparing and tuning of Lumi at H1. 10/6/94 ====================== Fedotov === Lumi Run #420(with Mode1) Start lumi run420 date: 10/6/94 Collision time: 15:08:13 - 19:52:51 Currents (mkA): Ie= 14561.00, Ip= 30900.00 Peak luminosity: 740.596 mb-1 s-1 Peak spec.lumi : 339.805393 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 168 Number of e-pilot b.: 15 Number of p-pilot b.: 15 HERA total lumi: 8022.371653 mkb-1 H1 Run total lumi: 6838.438808 mkb-1 H1 data taken lumi: 5310.65289 mkb-1 H1 Runs: 78670 - 78686 HERA - physics: 7057.558801 mkb-1 H1Run - physics: 5988.437308 mkb-1 H1data - physics: 4516.58889 mkb-1 H1 Runs: 78673 - 78686 Tot curr/rate factor: 0.25% C/R F H1Run gated: 0.26% Rand.C.F: Not calc.% RCF Run gated: Not calc.% Relative ET trigg accept.: 0.3329 10.06.1994 ==================== H1KFOM === MONITRIG Selection Status I made compressing of some data sets and now status of intermediate data sets with H1Lumi's MONITRIG events is the next(20:40): H1KFOM.H1LUMI.M117260.A00 } 195559 events with 275 Mbytes -C H1KFOM.H1LUMI.M117260.A01 }5 data sets were absent(125,147,148,192,193)-C 13 data sets were skiped (non Lumi RUN) 174-186 H1LumiRuns 77110-77112 are included into this data set H1KFOM.H1LUMI.M271305.B00 39961 events with 56.5 Mbytes -C H01GOG.H1LUMI.M306310.A00 K36066 78048081 00001 ACS -C H01GOG.H1LUMI.M311315.A00 K35506 78048081 00001 ACS -C H01GOG.H1LUMI.M316320.A00 K35125 78048081 00001 ACS -C H01GOG.H1LUMI.M321325.A00 K10599 78048081 00001 ACS -C H01GOG.H1LUMI.M326330.A00 K10584 78048081 00001 ACS -C H01GOG.H1LUMI.M331335.A00 K35651 78048081 00001 ACS -C H01GOG.H1LUMI.M336340.A00 K36081 78048081 00001 ACS -C H01GOG.H1LUMI.M341345.A00 K36022 78048081 00001 ACS -C H01GOG.H1LUMI.M346350.A00 K13958 78048081 00001 ACS -C H01GOG.H1LUMI.M351355.A00 K14406 78048081 00001 ACS -C H01GOG.H1LUMI.M356359.A00 K13396 78048081 00001 ACS -C H1KFOM.H1LUMI.M360499.A00 16 data sets were absent (364,391-396,402-404-C H1KFOM.H1LUMI.M360499.A01 421,441,450,457,485,492)-C 3 from Yura's jobs will be recalculated due to time limit was riched: H1KSOL.H1LUMI.M647651.A00 * K30317 78048081 00001 ACS-E-C H1KSOL.H1LUMI.M652656.A00 * K42294 78048081 00001 ACS-E-C H1KSOL.H1LUMI.M657661.A00 K41800 78048081 00001 ACS-E-C H1KSOL.H1LUMI.M662666.A00 K31163 78048081 00001 ACS-E-C H1KSOL.H1LUMI.M667671.A00 K43849 78048081 00001 ACS-E-C H1KSOL.H1LUMI.M672676.A00 K31751 78048081 00001 ACS-E-C H1KSOL.H1LUMI.M677681.A00 K31437 78048081 00001 ACS-E-C H1KSOL.H1LUMI.M682698.A00 K32502 78048081 00001 ACS-E-C H1KSOL.H1LUMI.M699703.A00 * K30792 78048081 00001 ACS-E-C H1KFOM.H1LUMI.M801854.A00 5 data sets were absent(800,802,805,807,811)-C Comment:files with * mark have to be recalculated they will be removed from directory H1KSOL(Yu.S) 10.06.1994 ==================== H1KFOM === Integrated Lumi Problem.. Today A.Usik fixed with his new tool (at picture with behaivours of Hera Produced, H1 Gated and H1 Data Taken with time) some strange situation during Lumi Run #420 (same as it was fixed 06.06.94): - near 16:52 H1 Gated and H1 Data Taken Integral Lumi values were decremented on value near 15-20 % (HERA Produced value was not decremented); - so OnLine RunSummary Integrated Lumi Values are wrong for Lumi RUN #420 (exept HERA produced). 11.06.1994 ==================== H1KSOL === Monitrig reprocessing ... After reprocessing of Monitrig cart. the following data sets are available ( Carts C9400647 - C9400703): H1KSOL.H1LUMI.M647650.A00 K10868 78048081 00001 ACS-E -C H1KSOL.H1LUMI.M651653.A00 K18826 78048081 00001 ACS-E -C H1KSOL.H1LUMI.M654656.A00 K12841 78048081 00001 ACS-E -C H1KSOL.H1LUMI.M657661.A00 K41800 78048081 00001 ACS-E -C H1KSOL.H1LUMI.M662666.A00 K31163 78048081 00001 ACS-E -C H1KSOL.H1LUMI.M667671.A00 K43849 78048081 00001 ACS-E -C H1KSOL.H1LUMI.M672676.A00 K31751 78048081 00001 ACS-E -C H1KSOL.H1LUMI.M677681.A00 K31437 78048081 00001 ACS-E -C H1KSOL.H1LUMI.M682698.A00 K32502 78048081 00001 ACS-E -C H1KSOL.H1LUMI.M699701.A00 K18842 78048081 00001 ACS-E -C H1KSOL.H1LUMI.M702703.A00 K32264 78048081 00001 ACS-E -C 11.06.1994 ==================== F11LEV === Loss of LUMI information. It was found, that since 23:12 yesterday, LRTL bank was not transferred to SGI (offline). Therefore - no Lumi information in database for H1 runs after 78697 (ca. 4 hours of data taking). It seems, the reason is in LUMI DAQ program (LRTL was not created). Online monitor worked, so nobody realized that Lumi is no longer trans- mitted to offline. It was seen only in a Run Summary on DAQ supervisor. Conclusion: 1) Reason must be identifed and fixed. 2) Alarm (any kind) is needed for such situations 3) Responsible people must go to the raw data and try to recreate LRTL content from e.g. LRTN, or LUMM. This fact, together with other recent observations (decrementing of integrated lumi value, still persisting spikes, some not understood crashes and dangerous interference between many applications) shows once again, that the overall reliability of LUMI is not satisfactory. I think, we have to stop to play around with permanent modifications of the online software during the data taking and rather to concentrate on the reliability of the system. Due to the LRTL absence we lost approx. 2.2 nb-1 of good data. +---------------------------------------------------------------+ | remember, 1 nb-1 of HERA data costs approximately 4000 DM, | | so check your bank account before sacrifice any luminosity! | +---------------------------------------------------------------+ 11/6/94 ====================== Fedotov === Lumi RUN# 421 Start lumi run421 date: 10/6/94 Collision time: 21:23:07 - 3:19:09 Currents (mkA): Ie= 24470.00, Ip= 29100.00 Peak luminosity: 1133.817 mb-1 s-1 Peak spec.lumi : 314.764942 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 167 Number of p-filled b.: 168 Number of e-pilot b.: 14 Number of p-pilot b.: 15 HERA total lumi: 9091.418231 mkb-1 H1 Run total lumi: 7874.1921 mkb-1 H1 data taken lumi: 5082.217 mkb-1 H1 Runs: 78687 - 78710 HERA - physics: 8391.226753 mkb-1 H1Run - physics: 6450.973655 mkb-1 H1data - physics: 3776.965686 mkb-1 H1 Runs: 78691 - 78710 Tot curr/rate factor: 0.84% C/R F H1Run gated: 0.86% Rand.C.F: 1.57% RCF Run gated: 1.6% Relative ET trigg accept.: 0.3290 11.06.1994 ==================== H1KFOM === Integrated Lumi Problem.. Tonight A.Usik fixed with his new tool (at picture with behaivours of Hera Produced, H1 Gated and H1 Data Taken with time) some strange situation during Lumi Run #421 (same as it was fixed 06.06.94 & 10.06). - near 01:20 H1 Gated and H1 Data Taken Integral Lumi values were decremented on value near 9 -10 % (HERA Produced value was not decremented). - so OnLine RunSummary Integrated Lumi Values are wrong for Lumi RUN #421 (exept HERA produced). 11/6/94 ====================== Fedotov === Lumi RUN# 422 Start lumi run422 date: 11/6/94 Collision time: 13:36:51 - 16:05:19 Currents (mkA): Ie= 20572.00, Ip= 28800.00 Peak luminosity: 1434.545 mb-1 s-1 Peak spec.lumi : 474.920231 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 167 Number of p-filled b.: 168 Number of e-pilot b.: 14 Number of p-pilot b.: 15 HERA total lumi: 5962.672492 mkb-1 H1 Run total lumi: 5281.1663 mkb-1 H1 data taken lumi: 3791.6787 mkb-1 H1 Runs: 78727 - 78740 HERA - physics: 4921.985209 mkb-1 H1Run - physics: 4403.857274 mkb-1 H1data - physics: 3097.777872 mkb-1 H1 Runs: 78730 - 78740 Tot curr/rate factor: 0.53% C/R F H1Run gated: 0.6% Rand.C.F: 1.64% RCF Run gated: 1.66% Relative ET trigg accept.: 0.3586 11.06.1994 ==================== H1KFOM === MONITRIG Selection Status I made compressing of some data sets and now status of intermediate data sets with H1Lumi's MONITRIG events is the next(16:30): H1KFOM.H1LUMI.M117260.A00 } 195559 events with 275 Mbytes -C H1KFOM.H1LUMI.M117260.A01 }5 data sets were absent(125,147,148,192,193)-C 13 data sets were skiped (non Lumi RUN) 174-186 H1LumiRuns 77110-77112 are included into this data set H01GOG.H1LUMI.M261263.A00 K41085 78048081 00001 ACS-E-C H01GOG.H1LUMI.M264266.A00 K32854 78048081 00001 ACS-E-C H01GOG.H1LUMI.M267270.A00 K32821 78048081 00001 ACS-E-C H1KFOM.H1LUMI.M271305.B00 39961 events with 56.5 Mbytes -C H1KFOM.H1LUMI.M306499.A00 } 252298 events with 356.0 Mbytes -C H1KFOM.H1LUMI.M306499.A01 } 16 data sets were absent (364,391-396, 402--C -404,421,441,450,457,485,492)-C H1KSOL.H1LUMI.M647650.A00 K10868 78048081 00001 ACS-E -C H1KSOL.H1LUMI.M651653.A00 K18826 78048081 00001 ACS-E -C H1KSOL.H1LUMI.M654656.A00 K12841 78048081 00001 ACS-E -C H1KSOL.H1LUMI.M657661.A00 K41800 78048081 00001 ACS-E -C H1KSOL.H1LUMI.M662666.A00 K31163 78048081 00001 ACS-E -C H1KSOL.H1LUMI.M667671.A00 K43849 78048081 00001 ACS-E -C H1KSOL.H1LUMI.M672676.A00 K31751 78048081 00001 ACS-E -C H1KSOL.H1LUMI.M677681.A00 K31437 78048081 00001 ACS-E -C H1KSOL.H1LUMI.M682698.A00 K32502 78048081 00001 ACS-E -C H1KSOL.H1LUMI.M699701.A00 K18842 78048081 00001 ACS-E -C H1KSOL.H1LUMI.M702703.A00 K32264 78048081 00001 ACS-E -C H1KFOM.H1LUMI.M801854.A00 5 data sets were absent(800,802,805,807,811)-C It were found at Nelly's catalog next data sets with H1Lumi MONITRIG events (but not reported yet - may be it were fixed some problems with time limit riched or something else). For any case: H01GOG.H1LUMI.M901905.A00 K10038 78048081 00001 ACS-E-C H01GOG.H1LUMI.M906910.A00 K10250 78048081 00001 ACS-E-C H01GOG.H1LUMI.M911915.A00 K10286 78048081 00001 ACS-E-C H01GOG.H1LUMI.M916920.A00 K10395 78048081 00001 ACS-E-C H01GOG.H1LUMI.M921925.A00 K35304 78048081 00001 ACS-E-C H01GOG.H1LUMI.M926930.A00 K10644 78048081 00001 ACS-E-C H01GOG.H1LUMI.M931935.A00 K37284 78048081 00001 ACS-E-C H01GOG.H1LUMI.M936940.A00 K10759 78048081 00001 ACS-E-C H01GOG.H1LUMI.M941945.A00 K38059 78048081 00001 ACS-E-C H01GOG.H1LUMI.M946950.A00 K38141 78048081 00001 ACS-E-C H01GOG.H1LUMI.M951955.A00 K11709 78048081 00001 ACS-E-C H01GOG.H1LUMI.M956960.A00 K38397 78048081 00001 ACS-E-C H01GOG.H1LUMI.M961965.A00 K38447 78048081 00001 ACS-E-C H01GOG.H1LUMI.M966970.A00 K12036 78048081 00001 ACS-E-C H01GOG.H1LUMI.M971975.A00 K38578 78048081 00001 ACS-E-C H01GOG.H1LUMI.M976980.A00 K39470 78048081 00001 ACS-E-C H01GOG.H1LUMI.M981985.A00 K40217 78048081 00001 ACS-E-C H01GOG.H1LUMI.M986988.A00 K40979 78048081 00001 ACS-E-C It were selected H1Lumi's MONITRIG -events from data sets which had appeared later at IBM srorage (see comments about ...were absent..) H01GOG.H1LUMI.M147148.A00 K12782 78048081 00001 ACS-E-C H01GOG.H1LUMI.M192193.A00 K12790 78048081 00001 ACS-E-C H01GOG.H1LUMI.M364364.A00 K12795 78048081 00001 ACS-E-C H01GOG.H1LUMI.M391392.A00 K12811 78048081 00001 ACS-E-C H01GOG.H1LUMI.M393394.A00 K12016 78048081 00001 ACS-E-C H01GOG.H1LUMI.M395396.A00 K12832 78048081 00001 ACS-E-C H01GOG.H1LUMI.M402403.A00 K19443 78048081 00001 ACS-E-C 11.06.1994 ==================== H1KFOM === MONITRIG Selection Status I made compressing of some data sets and now status of intermediate data sets with H1Lumi's MONITRIG events is the next(20:30): H1KFOM.H1LUMI.M117499.A00 K41886 78048081 00001 ACS-E-C H1KFOM.H1LUMI.M117499.A01 516997 events K43376 78048081 00001 ACS-E-C H1KFOM.H1LUMI.M117499.A02 729.1 Mbytes K36499 78048081 00001 ACS-E-C H1KFOM.H1LUMI.M117499.A03 K43506 78048081 00001 ACS-E-C 5 data sets were absent(125,147,148,192,193)-C 16 data sets were absent (364,391-396, 402- -C -404,421,441,450,457,485,492)-C H1KFOM.H1LUMI.M647650.A00 60493 events K43524 78048081 00001 ACS-E-C (I am sorry for non-standard previous name - this data set includes H1Lumi's MONITRIG events from MONITRIG-cartridges 647-703). H1KFOM.H1LUMI.M801854.A00 70209 events K11444 78048081 00001 ACS-E-C 5 data sets were absent(800,802,805,807,811)-C All high mentioned Nelly's data samples are not ready for compression Its must be tested on time limit or some errors or something else. I am waiting for Nelly's OK. 11.06.1994 ==================== H01GOG === MONITRIG selection I have selected the events of 24th class from MONITRIG cartridges: HERA03.H1POT2.MONITRIG.C9400901 ............................... ............................... HERA03.H1POT2.MONITRIG.C9401000 and also from cartridges which were absent before: HERA03.H1POT2.MONITRIG.C9400147,148,192,193,364,391, 392,393,394,395,396,402,403,404,421,441,450,457,485, 492,800,802,805,807,811. The following data sets were produced: H01GOG.H1LUMI.M147148.A00 K12782 78048081 00001 ACS-E-C H01GOG.H1LUMI.M192193.A00 K13455 78048081 00001 ACS-E-C H01GOG.H1LUMI.M364364.A00 K12795 78048081 00001 ACS-E-C H01GOG.H1LUMI.M391392.A00 K11803 78048081 00001 ACS-E-C H01GOG.H1LUMI.M393394.A00 K23757 78048081 00001 ACS-E-C H01GOG.H1LUMI.M395396.A00 K12832 78048081 00001 ACS-E-C H01GOG.H1LUMI.M402403.A00 K19443 78048081 00001 ACS-E-C H01GOG.H1LUMI.M404404.A00 K43635 78048081 00001 ACS-E-C H01GOG.H1LUMI.M421421.A00 K20282 78048081 00001 ACS-E-C H01GOG.H1LUMI.M441441.A00 K20826 78048081 00001 ACS-E-C H01GOG.H1LUMI.M450450.A00 K24009 78048081 00001 ACS-E-C H01GOG.H1LUMI.M457457.A00 K36871 78048081 00001 ACS-E-C H01GOG.H1LUMI.M485485.A00 K43912 78048081 00001 ACS-E-C H01GOG.H1LUMI.M492492.A00 K23418 78048081 00001 ACS-E-C H01GOG.H1LUMI.M800800.A00 K36616 78048081 00001 ACS-E-C H01GOG.H1LUMI.M802802.A00 K43928 78048081 00001 ACS-E-C H01GOG.H1LUMI.M805805.A00 K11006 78048081 00001 ACS-E-C H01GOG.H1LUMI.M807807.A00 K43949 78048081 00001 ACS-E-C H01GOG.H1LUMI.M811811.A00 K29085 78048081 00001 ACS-E-C H01GOG.H1LUMI.M901905.A00 K10038 78048081 00001 ACS-E-C H01GOG.H1LUMI.M906910.A00 K10250 78048081 00001 ACS-E-C H01GOG.H1LUMI.M911915.A00 K10286 78048081 00001 ACS-E-C H01GOG.H1LUMI.M916918.A00 K12854 78048081 00001 ACS-E-C H01GOG.H1LUMI.M919921.A00 K43608 78048081 00001 ACS-E-C H01GOG.H1LUMI.M922923.A00 K43649 78048081 00001 ACS-E-C H01GOG.H1LUMI.M924925.A00 K43867 78048081 00001 ACS-E-C H01GOG.H1LUMI.M926930.A00 K10644 78048081 00001 ACS-E-C H01GOG.H1LUMI.M931935.A00 K37284 78048081 00001 ACS-E-C H01GOG.H1LUMI.M936940.A00 K10759 78048081 00001 ACS-E-C H01GOG.H1LUMI.M941945.A00 K38059 78048081 00001 ACS-E-C H01GOG.H1LUMI.M946948.A00 K12906 78048081 00001 ACS-E-C H01GOG.H1LUMI.M949950.A00 K43628 78048081 00001 ACS-E-C H01GOG.H1LUMI.M951955.A00 K11709 78048081 00001 ACS-E-C H01GOG.H1LUMI.M956960.A00 K38397 78048081 00001 ACS-E-C H01GOG.H1LUMI.M961965.A00 K38447 78048081 00001 ACS-E-C H01GOG.H1LUMI.M966970.A00 K12036 78048081 00001 ACS-E-C H01GOG.H1LUMI.M971975.A00 K38578 78048081 00001 ACS-E-C H01GOG.H1LUMI.M976980.A00 K39470 78048081 00001 ACS-E-C H01GOG.H1LUMI.M981985.A00 K40217 78048081 00001 ACS-E-C H01GOG.H1LUMI.M986988.A00 K40979 78048081 00001 ACS-E-C H01GOG.H1LUMI.M989991.A00 K31051 78048081 00001 ACS-E-C H01GOG.H1LUMI.M992994.A00 K37564 78048081 00001 ACS-E-C H01GOG.H1LUMI.M995997.A00 K37585 78048081 00001 ACS-E-C H01GOG.H1LUMI.M998000.A00 K38950 78048081 00001 ACS-E-C It seems everything is OK. Go ahead, Sasha! 12.06.1994 ==================== F11LEV === LUMI is corrected in DB... The luminosity information for the runs 78698-78709 (lost due to the absence of LRTL bank) is now recovered from the 10 raw data cartridges (using LRTN bank content). At the same time I found, that L value in LRTN is not always correct: in case of no lumi (e.g. runs 78710-78724) it contains still last measured value from the lumi run (in this case: L=1.543*10^29, not updated during 1.5 hours since the run 78709). Fomenko, please fix this bug. 12.06.1994 ==================== H01LNS === #413 - #422 ~OK at L4 .... Last message about L4-monitoring was at LLO 06.06.94, L RUN# 412. From that time on I was carefully watching at L4 for every RUN#. For most RUN#s, only START and END Runs have been checked (CPU!), and nothing special have happend, ALL L4 were ~OK, for all LUMI-RUN#s. The EXACT meaning and criteria of "L4 OK" have not yet worked out, in any case for me, but I am trying to understand the criteria. By the way, the incident with the bank LRTL (see F11LEV) could not be seen at L4, because L4 is not sensitive to this, and many other banks. It is to be sorryed. L.Shtarkov, DESY. 12.06.1994 ==================== H01LNS === for the next DQ-meeting .. Here are selected words from Jan-Erik Olsson's H1RUN-message: "The next meeting on Data Quality and Checks will take place * TUESDAY, JUNE 14, 1994 at 15-17:00 Sem.room 3 (1B) " " ALL reports should be reasonably detailed and be written on at least one transparency. Statements like "Everything OK", "Running stable", etc., will in general no longer be accepted without some proof, in form of plots, analysis results, etc.! Resolution and/or Efficiency should be known for all detector parts ! " The Thesises of the previous LUMI-report are written in this LLO, upper. It would be good to tell LLO or mail me about what to be better reported Moreover this meeting is one of the occassions to REMIND of our problems As for me, I am ready to report any from L4, and from LLO occassionaly. L.Shtarkov, DESY. 12.06.1994 ==================== F11LEV === LUMI report for DQ meeting What should be typically reported, on my opinion: 1) General status of the lumi data monitoring: - DAQ monitoring tool exists and used by LUMI experts, but: Not all LUMI info is being monitored now (example-LRTL accident) ==> s/w alarms must be added in all critical places of LUMI DAQ - L4 hist. status (now bad, expected to be finally updated on Monday, so before this meeting; if yes - than OK) - L5 histograms (sufficienf info? If not - propose better plots) - Automatic monitoring tool (does not exist for LUMI) - could be done? Ideas? Where? In logging job, at L5? 2) Monitoring sample(s): - LUMI monitor triggers sample problem/status (access to the data), - is amount sufficient/correct for all LUMI triggers? In other words, are all prescale gaps correct, or must be adjusted? 3) Summary on the data quality themselves: - Trigger efficiencies (VC, ET, PD - threshold plots) - ask e.g. Yura Soloviev what he has done - Calibration status: stability, abs.scale, resolution? You can add to this list what you want, but be reasonably short, clear and conclusive. This makes a good impression. To everybody: LUMI data quality and control is our COMMON task, we ALL are responsible for the proper system operation. So, please, combine efforts! Make your studies/results available for everybody in LUMI group. Report on ALL known to you problems, or not understood facts. 12.06.1994 ==================== H1KFOM === Integrated Lumi Problem.. Tonight A.Usik fixed with his new tool (at picture with behaivours of Hera Produced, H1 Gated and H1 Data Taken with time) some strange situation during Lumi Run #424 (same as it was fixed 06,10,11.06.94). - near 02:45 H1 Gated and H1 Data Taken Integral Lumi values were decremented on value near 9 -10 % (HERA Produced value was not decremented). - so OnLine RunSummary Integrated Lumi Values are wrong for Lumi RUN #424 (exept HERA produced). 11/6/94 ====================== Fedotov === Lumi RUN# 423 Start lumi run423 date: 11/6/94 Collision time: 17:04:38 - 23:01:14 Currents (mkA): Ie= 25815.00, Ip= 28701.00 Peak luminosity: 950.015 mb-1 s-1 Peak spec.lumi : 453.300957 mb-1 s-1 mA-2 Number of collided b.: 151 Number of e-filled b.: 163 Number of p-filled b.: 168 Number of e-pilot b.: 12 Number of p-pilot b.: 17 HERA total lumi: 11859.108897 mkb-1 H1 Run total lumi: 11460.4439 mkb-1 H1 data taken lumi: 8453.7946 mkb-1 H1 Runs: 78745 - 78762 HERA - physics: 10762.647983 mkb-1 H1Run - physics: 10127.658314 mkb-1 H1data - physics: 7159.501607 mkb-1 H1 Runs: 78747 - 78762 Tot curr/rate factor: 0.08% C/R F H1Run gated: 0.09% Rand.C.F: 1.21% RCF Run gated: 1.21% Relative ET trigg accept.: 0.3311 12/6/94 ======================= i04zbk === Lumi RUN# 424 Start lumi run424 date: 12/6/94 Collision time: 0:43:19 - 3:00:28 Currents (mkA): Ie= 25465.00, Ip= 28100.00 Peak luminosity: 1322.025 mb-1 s-1 Peak spec.lumi : 379.132451 mb-1 s-1 mA-2 Number of collided b.: 152 Number of e-filled b.: 166 Number of p-filled b.: 168 Number of e-pilot b.: 14 Number of p-pilot b.: 16 HERA total lumi: 5880.361388 mkb-1 H1 Run total lumi: 4418.7138 mkb-1 H1 data taken lumi: 3604.2856 mkb-1 H1 Runs: 78768 - 78784 HERA - physics: 4760.823259 mkb-1 H1Run - physics: 2597.9996 mkb-1 H1data - physics: 2027.8207 mkb-1 H1 Runs: 78774 - 78784 Tot curr/rate factor: 1.41% C/R F H1Run gated: 1.36% Rand.C.F: 2.37% RCF Run gated: 2.27% Relative ET trigg accept.: 0.3565 12/6/94 ======================= h1kuwe === Lumi RUN# 425 Start lumi run425 date: 12/6/94 Collision time: 5:10:32 - 9:36:13 Currents (mkA): Ie= 25956.00, Ip= 23701.00 Peak luminosity: 661.392 mb-1 s-1 Peak spec.lumi : 276.63548 mb-1 s-1 mA-2 Number of collided b.: 152 Number of e-filled b.: 167 Number of p-filled b.: 168 Number of e-pilot b.: 15 Number of p-pilot b.: 16 HERA total lumi: 5675.943369 mkb-1 H1 Run total lumi: 5393.586634 mkb-1 H1 data taken lumi: 4303.140212 mkb-1 H1 Runs: 78785 - 78802 HERA - physics: 4499.981462 mkb-1 H1Run - physics: 3978.710152 mkb-1 H1data - physics: 2942.350133 mkb-1 H1 Runs: 78788 - 78802 Tot curr/rate factor: 0.69% C/R F H1Run gated: 0.72% Rand.C.F: 2.1% RCF Run gated: 2.11% Relative ET trigg accept.: 0.3270 12.06.1994 ==================== H1KFOM === MONITRIG Selection Status I made compressing of some data sets and now status of intermediate data sets with H1Lumi's MONITRIG events is the next(13:00): H1KFOM.H1LUMI.M117499.A00 K41886 78048081 00001 ACS-E-C H1KFOM.H1LUMI.M117499.A01 516997 events K43376 78048081 00001 ACS-E-C H1KFOM.H1LUMI.M117499.A02 729.1 Mbytes K36499 78048081 00001 ACS-E-C H1KFOM.H1LUMI.M117499.A03 K43506 78048081 00001 ACS-E-C 5 data sets were absent(125,147,148,192,193) -C 16 data sets were absent (364,391-396, 402-404, -C 421,441,450,457,485,492)-C H1LumiRuns 77110-77112 are included into this data set H1KFOM.H1LUMI.M647650.A00 60493 events K43524 78048081 00001 ACS-E-C 88.0 Mbytes (I am sorry for non-standard previous name - this data set includes H1Lumi's MONITRIG events from MONITRIG-data sets 647-703). H1KFOM.H1LUMI.M801854.A00 70209 events K11444 78048081 00001 ACS-E-C 4 data sets were absent(802,805,807,811) -C H1KFOM.H1LUMI.M901000.A00 144477 events K20181 78048081 00001 ACS-E-C H1KFOM.H1LUMI.M901000.A01 204.7 Mbytes K19802 78048081 00001 ACS-E-C On this time it were produced new MONITRIG-data sets (90 data sets): HERA03.H1POT2.MONITRIG.C9401001 K18395 78048081 00001 ACS-E-C ..... HERA03.H1POT2.MONITRIG.C9401090 K19754 78048081 00001 ACS-E-C I did not make insertion of skipped data set into H1Lumi Monitrig data sets yet. Let's keep its for future. H01GOG.H1LUMI.M147148.A00 K12782 78048081 00001 ACS-E-C H01GOG.H1LUMI.M192193.A00 K13455 78048081 00001 ACS-E-C H01GOG.H1LUMI.M364364.A00 K12795 78048081 00001 ACS-E-C H01GOG.H1LUMI.M391392.A00 K11803 78048081 00001 ACS-E-C H01GOG.H1LUMI.M393394.A00 K23757 78048081 00001 ACS-E-C H01GOG.H1LUMI.M395396.A00 K12832 78048081 00001 ACS-E-C H01GOG.H1LUMI.M402403.A00 K19443 78048081 00001 ACS-E-C H01GOG.H1LUMI.M404404.A00 K43635 78048081 00001 ACS-E-C H01GOG.H1LUMI.M421421.A00 K20282 78048081 00001 ACS-E-C H01GOG.H1LUMI.M441441.A00 K20826 78048081 00001 ACS-E-C H01GOG.H1LUMI.M450450.A00 K24009 78048081 00001 ACS-E-C H01GOG.H1LUMI.M457457.A00 K36871 78048081 00001 ACS-E-C H01GOG.H1LUMI.M485485.A00 K43912 78048081 00001 ACS-E-C H01GOG.H1LUMI.M492492.A00 K23418 78048081 00001 ACS-E-C H01GOG.H1LUMI.M800800.A00 * K36616 78048081 00001 ACS-E-C H01GOG.H1LUMI.M802802.A00 K43928 78048081 00001 ACS-E-C H01GOG.H1LUMI.M805805.A00 K11006 78048081 00001 ACS-E-C H01GOG.H1LUMI.M807807.A00 K43949 78048081 00001 ACS-E-C H01GOG.H1LUMI.M811811.A00 K29085 78048081 00001 ACS-E-C (*)This data set can be deleted due to possible using of 800th data set at low mentioned future selection (704-800). All another intermediate data set it is possible to delete at Nelly's catalog and Yura's catalog at IBM storage. Asking to Nelly - make please selection of all needed H1Lumi monitrig events at MONITRIG numbers range: 500 - 646 704 - 800 855 - 900 1001 - 1002 1022 - 1090 MONITRIG data sets with number range 1003-1021 I shall select myself due to non-standard selection is required (LREF and LRPF-banks must be selected too for e48-study). Let's use the next names with 1XXX-family data sets: H01GOG.H1LUMI.N001010.A00 etc. -C 12/6/94 ======================= h1kuwe === Lumi RUN# 426 Start lumi run426 date: 12/6/94 Collision time: 10:32:17 - 15:44:04 Currents (mkA): Ie= 22889.00, Ip= 22601.00 Peak luminosity: 546.179 mb-1 s-1 Peak spec.lumi : 213.985187 mb-1 s-1 mA-2 Number of collided b.: 153 Number of e-filled b.: 168 Number of p-filled b.: 168 Number of e-pilot b.: 15 Number of p-pilot b.: 15 HERA total lumi: 5552.094704 mkb-1 H1 Run total lumi: 5191.9979 mkb-1 H1 data taken lumi: 3918.6298 mkb-1 H1 Runs: 78802 - 78817 HERA - physics: 5389.320704 mkb-1 H1Run - physics: 4988.764822 mkb-1 H1data - physics: 3761.293976 mkb-1 H1 Runs: 78808 - 78817 Tot curr/rate factor: 0.24% C/R F H1Run gated: 0.25% Rand.C.F: 1.54% RCF Run gated: 1.49% Relative ET trigg accept.: 0.3188 P.S. both beams were dumped (due to p-beam was used at 5 Lumi Runs). Now preparing for new p-beam injection. 12.06.1994 ===== dice2 ======== H1KFOM === H1Lumi MONITRIG for #420 It were selected H1Lumi's MONITRIG-events from MONITRIG-data sets which were produced from Lumi RUN #420 H1 Data: Banks LREF and LRPF were selected additinally to 'standard' set of H1Lumi and H1CTRIG banks at all H1Lumi MONITRIG-data sets. H1KFOM.H1LUMI.N003021.A00 K39346 78048081 00001 ACS-E-C HERA03.H1POT2.MONITRIG.C9401003 78632 26 78673 14522 ...... HERA03.H1POT2.MONITRIG.C9401021 78684 119282 78691 12694 Selection was made at dice2 environment with preliminary stagin of 19 data sets with H1MONITRIG-events. It is possible to use data set H1KFOM.H1LUMI.N003021.A00 for analyze of e48-response with additional check of pulse front position (may be for PDLow-trigger).There are 13669 events of CLASS=24 at high mentioned data set with 30.54 Mbyte. 13/6/94 ====================== Fedotov === Lumi Run# 427 Start lumi run427 date: 13/6/94 Collision time: 2:11:02 - 5:29:39 Currents (mkA): Ie= 23605.00, Ip= 20601.00 Peak luminosity: 1093.698 mb-1 s-1 Peak spec.lumi : 450.201906 mb-1 s-1 mA-2 Number of collided b.: 150 Number of e-filled b.: 165 Number of p-filled b.: 168 Number of e-pilot b.: 15 Number of p-pilot b.: 18 HERA total lumi: 6732.352629 mkb-1 H1 Run total lumi: 6062.5397 mkb-1 H1 data taken lumi: 4231.1065 mkb-1 H1 Runs: 78851 - 78858 HERA - physics: 6273.503376 mkb-1 H1Run - physics: 5294.61892 mkb-1 H1data - physics: 3525.072136 mkb-1 H1 Runs: 78853 - 78858 Tot curr/rate factor: 0.29% C/R F H1Run gated: 0.3% Rand.C.F: 1.8% RCF Run gated: 1.79% Relative ET trigg accept.: 0.3546 13.06.1994 ==================== H01LNS === the next DQ-meeting ...... Dear Cooleagues of LUMI, For the next DQ-meeting, to-Morrow 14.06.94 15-00, Highly desirable during THIS Day, because nothing have yet written, Remembering S.L.'s recomendations at LLO of 12.06.94, and your P.of.V: Could you mail me, L.S., some components for a DQ-report, in any form, but no longer than just a few (2-4) lines for an item(!), for example, Here is a List of Thesises: 1. PERFORMANCE and STATUS of LUMI for the previous week: Status of the Regular LUMI-VALUES H1-information (first of all!!!), Which Incident(s) have happened, LRTL disappiering(!), etc.. 2. Status of LUMI- TRIGGERS and PRESCALERS(!): Are you satysfide; Complaints, Requests, Proposals; a point of view. 3. Jobs of CALIBRATION: A very short(!) STATUS, OK or NOT, just for the first DQ-report(!), (I think, such items as Resolution, Syst.Errors, etc. - for Future) What is wanted for Calibration from H1(!): Beams,Time,Triggers,etc. 4. Jobs of L4-MONITORING: Summary on the L4-Histos, What is wanted for the Future. 5. Jobs of MONITRIGs: Summary of What have done, what have not yet done, What is wanted for jobs of MONITORING from the H1(!). x. What is wanted for different OTHER LUMI jobs from the H1. z. Better for Future: Any other LUMI ITEMS, or even H1 and HERA ITEMS. I am sure, this list is not compleat, but the time ... , I shall try to compile some Draft, by cutting and summing, up to to-Morrow Morning, and display it in LLO as a Draft THESISES. In the cases of no-new-information, I shall use the info from LLO-up. Certainly, We should remember, It is one of the first DQ-reports - Not all should be said JUST NOW, there is a time for the next reports. Sorry for beeng a little late, L.Shtarkov, DESY. 13/6/94 ====================== Fedotov === Lumi Run# 428 Start lumi run428 date: 13/6/94 Collision time: 6:41:12 - 10:59:15 Currents (mkA): Ie= 24300.00, Ip= 20500.00 Peak luminosity: 1004.857 mb-1 s-1 Peak spec.lumi : 416.228081 mb-1 s-1 mA-2 Number of collided b.: 152 Number of e-filled b.: 167 Number of p-filled b.: 168 Number of e-pilot b.: 15 Number of p-pilot b.: 16 HERA total lumi: 7263.824308 mkb-1 H1 Run total lumi: 6520.76096 mkb-1 H1 data taken lumi: 4826.061722 mkb-1 H1 Runs: 78860 - 78877 HERA - physics: 6388.690666 mkb-1 H1Run - physics: 4858.442094 mkb-1 H1data - physics: 3835.810773 mkb-1 H1 Runs: 78865 - 78877 Tot curr/rate factor: 0.34% C/R F H1Run gated: 0.34% Rand.C.F: 1.7% RCF Run gated: 1.65% Relative ET trigg accept.: 0.3357 P.S. both HERA beams were dumped. P-beam had bad situation with sattelite bunches. It was proclaimed temporary access. Restart about 3 hours. 13.06.1994 ==================== H01GOG === MONITRIG selection I have selected the events of 24th class from MONITRIG cartridges: HERA03.H1POT2.MONITRIG.C9400500 ............................... ............................... HERA03.H1POT2.MONITRIG.C9400560 The following data sets were produced: H01GOG.H1LUMI.M500502.A00 K38747 78048081 00001 ACS-E-C H01GOG.H1LUMI.M503504.A00 K40081 78048081 00001 ACS-E-C H01GOG.H1LUMI.M505508.A00 K41054 78048081 00001 ACS-E-C H01GOG.H1LUMI.M509512.A00 K41651 78048081 00001 ACS-E-C H01GOG.H1LUMI.M513516.A00 K41081 78048081 00001 ACS-E-C H01GOG.H1LUMI.M517520.A00 K18188 78048081 00001 ACS-E-C H01GOG.H1LUMI.M521524.A00 K26960 78048081 00001 ACS-E-C H01GOG.H1LUMI.M525528.A00 K41302 78048081 00001 ACS-E-C H01GOG.H1LUMI.M529532.A00 K18191 78048081 00001 ACS-E-C H01GOG.H1LUMI.M533536.A00 K42518 78048081 00001 ACS-E-C H01GOG.H1LUMI.M537540.A00 K41332 78048081 00001 ACS-E-C H01GOG.H1LUMI.M541544.A00 K28328 78048081 00001 ACS-E-C H01GOG.H1LUMI.M545548.A00 K29712 78048081 00001 ACS-E-C H01GOG.H1LUMI.M549552.A00 K36023 78048081 00001 ACS-E-C H01GOG.H1LUMI.M553556.A00 K36592 78048081 00001 ACS-E-C H01GOG.H1LUMI.M557560.A00 K43165 78048081 00001 ACS-E-C 13.06.1994 ==================== H1KFOM === HERA-clock Error ......... Today after 13:04 we had not HERA-clock at H1Lumi-subsytem due to John Coughlan made some manipulations with STC-cards. Up to now (13:50) HERA-clock is absent. H1CDAQ was switched on TEST-branch without any another branches. "Check Trigger Status" shows ClkErr. All manipulation connected with Lumi Local Timer are not operated. Our Slow Control Status shows "Synchronization: NO ERROR" - may be it means only Rate/Current synchronization (there are no any currents and no any rates now). New Usik's history pictures are not sensetive to absense of HERA- clock at H1Lumi subsystem. Bunch Currents Update absence put alarm into H1 Slow Control. Program at FIC#1 permanently reported about termination run - no any reaction on reboot manipulation - termination Run interrupts were continued permanently. 13.06.1994 ==================== H1KFOM === FADC Replacement for NC... Today at 17:30 it was replaced 11th FADC at H1Lumi FADC crate due to some problems with one of the FADC-channels (as O.Duenger said) at this FADC which is connected with NC-channels. Replacement was made by Gunter Eckerlin with care and all needed changings at the spare FADC card were made (all jumpers were installed as it was seen from original FADC card). Immediately after replacement we tested memory mapping - all is OK. It was written Run 78928 during p-beam injection (Ep=40 GeV Ip was changed from 1.0 up to 13.mA). It was used transparent mode and only 119 trigger element was unmasked Threshold value for NC-trigger element was installed on 5 GeV. After collection of near 10K events Run was stopped and threshold value for NC-trigger element was back on 10 GeV. P.S. One of today H1 Shift Crew persons said me that at Friday E.Elsen due to request of R.Felst made changing at s89-subtrigger (before this day it was etag&nc, now - it was added additional .AND. with one of tracker trigger elements). PPS. (S.L.) It is now: s89 eTAG && n_cntr && DCRPh_Ta v:0 f:0 14.06.1994 ==================== H1KSHE === speed up explain.......... I find small missunderstanding of my "speed up " message. 1. As i had mentiond no any additional VME bus activity is provided by my proporsal due to there is NO ADDITIONAL data flow but the same data flow just splited. The TOTAL VME BUS OVERLOARDING WILL DEPEND ON TOTAL RATE OF EVENTS ONLY AND THIS IS WILL BE TRUE FOR ANY CURRENT SPEED UP PROPOSALS INCLUDING "L4 SUPPORT". So NO ANY NEW VME BUS PROBLEMS IS FORESEEN. The buserror processing is oldest our task and we probably is alone system who not handle it on FIC level and this is disgrace of course. 2. I made suggestion for GLOBAL SPEED UP the system which not reject all other modifications including L4 and obvious replacement by more fast elements (new GPTP, ....) that will be done in any case. Simply we can have factor ~2 for any software extensions and modifications, i consider it will be very important for future development. 3. In absence other suggestions for global speed up the system i think it is simply stupidity to stop activity or keep inactivity in this field for this moment. If we will continue to make supports "stavit podporki" for old system we can very soon turn out in more critical situation than now. 4. I am very ask everybody, who are not indifferent to the problem, support this idea (or generate new which must be obviously better) please and inform about H1 community everythere it is need. I think this is help us to get additional FIC which will not be spare in any case. 14.06.1994 ==================== H01GOG === MONITRIG selection stat. For the time being the events of 24th class from almost all MONITRIG cartridges ( except last three, which have appeared at HERA03.H1POT2.MONITRIG.C940xxxx catalog just this morning - C9401131 - C9401133) have been selected: HERA03.H1POT2.MONITRIG.C9400855 ............................. HERA03.H1POT2.MONITRIG.C9400900 And HERA03.H1POT2.MONITRIG.C9401001 HERA03.H1POT2.MONITRIG.C9401002 HERA03.H1POT2.MONITRIG.C9401022 ............................... ............................... HERA03.H1POT2.MONITRIG.C9401130 The following data sets were produced: H01GOG.H1LUMI.M855858.A00 K17626 78048081 00001 ACS-E-C H01GOG.H1LUMI.M859862.A00 K32506 78048081 00001 ACS-E-C H01GOG.H1LUMI.M863866.A00 K27300 78048081 00001 ACS-E-C H01GOG.H1LUMI.M867870.A00 K17628 78048081 00001 ACS-E-C (the job with input cartridges C9400871-C9400874 was failed because of the time limit. So, I have divided it in 2 jobs and submited once again. Hoping to have the result very soon). H01GOG.H1LUMI.M875878.A00 K17641 78048081 00001 ACS-E-C H01GOG.H1LUMI.M879882.A00 K17644 78048081 00001 ACS-E-C H01GOG.H1LUMI.M883886.A00 K27363 78048081 00001 ACS-E-C H01GOG.H1LUMI.M887890.A00 K27590 78048081 00001 ACS-E-C H01GOG.H1LUMI.M891894.A00 K26730 78048081 00001 ACS-E-C H01GOG.H1LUMI.M895897.A00 K28349 78048081 00001 ACS-E-C H01GOG.H1LUMI.M898900.A00 K29121 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1001002.A00 K20223 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1022025.A00 K42759 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1026029.A00 K20226 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1030033.A00 K20228 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1034037.A00 K33541 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1038041.A00 K12758 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1042045.A00 K20241 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1046049.A00 K20799 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1050053.A00 K20284 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1054057.A00 K20831 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1058061.A00 K20832 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1062065.A00 K21123 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1066069.A00 K21448 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1070073.A00 K22434 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1074077.A00 K22765 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1078081.A00 K23185 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1082085.A00 K23523 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1086089.A00 K23624 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1090093.A00 K23629 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1094097.A00 K23710 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1098099.A00 K24350 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1100103.A00 K24356 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1104107.A00 K22804 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1108111.A00 K25052 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1112115.A00 K25993 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1116119.A00 K17612 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1120123.A00 K17619 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1124127.A00 K26949 78048081 00001 ACS-E-C H01GOG.H1LUMI.M1128130.A00 K27284 78048081 00001 ACS-E-C I have also compressed the unnormal amount of the produced tapes. The result will appear by the evening or by the next morning (at the latest). 14.06.1994 ==================== H1KFOM === Speed up online (E.Elsen) READMAIL message stored : TUE, 14 JUN 94 18:05:43 MESZ Date: Tue, 14 Jun 1994 18:03:06 +0200 (MET DST) From: Eckhard Elsen Subject: Lumi Readout Upgrades To: "A.M. Fomenko" Dear Igor and Sascha, thanks for your detailed reports on the possible improvements of the dead time situation. Here are my comments: You should use an additional new processor. I agree completely with the division of the activities between the dif- ferent processors. There will be no increase of the VME traffic.Even, I have operated myself VME crates in which 16 processors where COMPETING on the VMEbus. There has to be no problem; if so it is the problem of CES. There should be no problem in getting a new CPU. Either we have it already (we have to check with Eberhard Wuensch) or we buy one. However, since there might be some time for development, would you not want to try one of the 68040 processors? I think we have unused processors in the tracking area which should be available. This may be particularly interesting for the reformatting/ zero suppression. In that case you would be really prepared for the future. A scenario in which you start with a 68030 and then upgrade to 68040 would also be conceivable. Can you let me know your choice? Now to the other points: The new GPTP module (ATPM) is not yet ready. Even if it becomes available during the summer I do not know whether we want to take the risk of modifying the software during running. For next year it will improve your readout situation and you should replace the GPTP cards. More internal buffers may help. With the present beam situation the dynamics of the buffering is considerable. Eight is a rather small number and you should stay above the number of 10. 10 buffers are used by the central trigger and that should be the smallest number in the system. Can this be changed easily? If so, please do it, now. The tail of 50 ms is really very bad for dead time. I think it is not necessary to move the formatting of banks to L4. With using some of the (non standard Fortran 77) features of RTF one can avoid register reloading and it should introduce very little overhead to perform an online zero suppression. The main point is to have as little activity to the VMEbus as possible, especially when reading the GPTP modules. I am happy to look through the reformatting code to see whether it could still be optimized if you wish. Best regards, Eckhard 14.06.1994 ==================== H01LNS === for next DQ-meeting ...... Here are Thesises from Transparansy, ready-made for DQ-meeting. Only about 2/3 of reports were made, ours and others are postponded to the next meeting, so there is a good possibility to correct Text. In any case I shall try to improove it. STATUS of LUMI 07. - 14.06.94 1. PERFORMANCE: OK in General + Problems of minor importance, The LUMI-VALUES have been sent to Data-Base, The RUN SUMMARIES were written without delays, The CURRENT INFO were updated at DESY-monitors. 2. L4-MONITORING: L4 has prooved the OK status of LUMY, and showed a reasonable(?) STABILITY of Parameters. % Calibration and Resolution constants. % The real meaning of "?" is under more carefull analysis. Single L4-Pictures can be shown, but hardly interesting. 3. INCIDENTS: 11.06.94 S.Levonian discovered that LRTL bank was lost, %% and Lumi values were not in DataBase for R78698-R78709. On-line was OK and nobody realized the alarm situation. The lost info was recovered OK by efforts of S.Levonian. 4. MONI-TRIGs: Selecting of LUMI-events has been done at ibm, To make these jobs at SGI was not possible ...... UPDATING of LUMI-monitrigs is yet a problem ! 5. PRESCALERS: Shifters Never inform of the new PS values, it is bad. Not yet clear the possibility to make the PS's lower. 6. LUMI CALIBRATION: We need for some small, but REGULAR time to DO! 7. THE STATUS: OK in General + Minor problems. Compilated by LNS, via LLO, S.Levonian, A.Fomenko, ...Ù 14.06.1994 ==================== H01LNS === proposals for L4.......... Because of some small expierence with L4, I propose to update out L4-histos with the following three: 1. ALL of LUMI BANKS statistics, 2. ALL(!!) of LUMI TRIGGERS (including internal) statistics, 3. Some spectra for monitoring the main THRESHOLDS. I believe, this is an absolute minimum of L4-updating, There is a number of the other desires, but now - about minimum. It seems, that the job for 1 - 3 is not tremendous, but Who knows ... Sorry: Our main L4-spectrum for LUMI is having a bad L4-resolution, comparing to On-Line and our pretensies, better applay some L4-cuts. Sorry, L.Shtarkov, DESY. 15/6/94 ======================= h1kfom === Lumi RUN# 429 Start lumi run429 date: 14/6/94 Collision time: 21:06:13 - 1:19:50 Currents (mkA): Ie= 22188.00, Ip= 34601.00 Peak luminosity: 1812.538 mb-1 s-1 Peak spec.lumi : 479.983836 mb-1 s-1 mA-2 Number of collided b.: 151 Number of e-filled b.: 167 Number of p-filled b.: 167 Number of e-pilot b.: 16 Number of p-pilot b.: 16 HERA total lumi: 10607.844965 mkb-1 H1 Run total lumi: 9488.307632 mkb-1 H1 data taken lumi: 6706.575553 mkb-1 H1 Runs: 79045 - 79056 HERA - physics: 9235.279938 mkb-1 H1Run - physics: 6753.786933 mkb-1 H1data - physics: 4574.624646 mkb-1 H1 Runs: 79047 - 79056 Tot curr/rate factor: 0.6% C/R F H1Run gated: 0.6% Rand.C.F: 1.46% RCF Run gated: 1.45% Relative ET trigg accept.: 0.3593 15.06.1994 09:50 ============== H01LNS === L4 Warning for #429....... A little strange L4 for the LUMI RUN# 429: 1. There is NO L4-histos for R079047 - R079053, all from RUN# start, 2. Only for 3 Runs histos exist R079054 - R079056, for RUN# ending, 3. R079054 - R079055 are looking OK, 4. But for the Last run R079056 - There is NO Etag's ! I don't know the exact meaning of that, Maybe better wait for the next LUMI RUN# Summary ... PS at 11-45: Etag's appiered at the RUN# 430, OK. 15/6/94 ======================= oakden === Lumi RUN# 430 Start lumi run430 date: 15/6/94 Collision time: 2:49:45 - 9:04:10 Currents (mkA): Ie= 21331.00, Ip= 33800.00 Peak luminosity: 1401.483 mb-1 s-1 Peak spec.lumi : 397.511996 mb-1 s-1 mA-2 Number of collided b.: 152 Number of e-filled b.: 167 Number of p-filled b.: 167 Number of e-pilot b.: 15 Number of p-pilot b.: 15 HERA total lumi: 10000.0 mkb-1 <---- must be corrected H1 Run total lumi: 6734.3845 mkb-1 H1 data taken lumi: 3906.6075 mkb-1 H1 Runs: 79062 - 79128 HERA - physics: 8300.0 mkb-1 <---- must be corrected H1Run - physics: 6587.98893 mkb-1 H1data - physics: 3791.225196 mkb-1 H1 Runs: 79064 - 79128 Tot curr/rate factor: 0.43% C/R F H1Run gated: 0.45% Rand.C.F: 1.3% RCF Run gated: 0.92% Relative ET trigg accept.: 0.3440 P.S. At 04:20 something happened with value of HERA Produced Lumi (NAN-value appeared again - at this case at D2-value). We put (temporary) values 10 nb-1 for HERA produced total and 8.3 nb-1 for HERA produced for physics. These values will be reconstructed later and put into LLC. Values of HERA produced Lumi are corrupted at all LRTL-banks after 04:20. After reconstruction with Usik's history picture for Lumi RUN# 429: HERA total lumi: 14529.0 mkb-1 HERA - physics: 12738.0 mkb-1 15/6/94 ======================= oakden === Lumi RUN# 431 Start lumi run431 date: 15/6/94 Collision time: 9:56:42 - 13:53:34 Currents (mkA): Ie= 21500.00, Ip= 32700.00 Peak luminosity: 1003.279 mb-1 s-1 Peak spec.lumi : 270.956345 mb-1 s-1 mA-2 Number of collided b.: 151 Number of e-filled b.: 166 Number of p-filled b.: 167 Number of e-pilot b.: 15 Number of p-pilot b.: 16 HERA total lumi: 9530.30797 mkb-1 H1 Run total lumi: 8149.637544 mkb-1 H1 data taken lumi: 5446.860288 mkb-1 H1 Runs: 79134 - 79148 HERA - physics: 9043.360178 mkb-1 H1Run - physics: 7599.032344 mkb-1 H1data - physics: 5198.594088 mkb-1 H1 Runs: 79141 - 79148 Tot curr/rate factor: 0.34% C/R F H1Run gated: 0.35% Rand.C.F: 1.34% RCF Run gated: 1.25% Relative ET trigg accept.: 0.3398 15.06.1994 ==================== H01GOG === MONITRIG selection status By this moment (18:15) the selection of the events of 24th class from all MONITRIG cartridges ( HERA03.H1POT2.MONITRIG.C9400117 - HERA03.H1POT2.MONITRIG.C9401158, except C9400125, which is not appearing at the catalog up to now) was made. The final status of produced data sets is the following: H1KFOM.H1LUMI.M117499.A00 K41886 78048081 00001 ACS-E-C H1KFOM.H1LUMI.M117499.A01 K43376 78048081 00001 ACS-E-C H1KFOM.H1LUMI.M117499.A02 K36499 78048081 00001 ACS-E-C H1KFOM.H1LUMI.M117499.A03 K43506 78048081 00001 ACS-E-C (input cartridges C9400117 - C9400499) H01GOG.H1LUMI.C500560.A00 K45500 78048081 00001 ACS-E-C (input cartridges C9400500 - C9400560) H1KFOM.H1LUMI.M647650.A00 K43524 78048081 00001 ACS-E-C (input cartridges C9400647 - C9400703)! H01GOG.H1LUMI.C704800.A00 K47352 78048081 00001 ACS-E-C H01GOG.H1LUMI.C704800.A01 K18891 78048081 00001 ACS-E-C (input cartridges C9400704 - C9400800) H1KFOM.H1LUMI.M801854.A00 K11444 78048081 00001 ACS-E-C (input cartridges C9400801 - C9400854) H01GOG.H1LUMI.C855900.A00 K20521 78048081 00001 ACS-E-C (input cartridges C9400855 - C9400900) H1KFOM.H1LUMI.M901000.A00 K20181 78048081 00001 ACS-E-C H1KFOM.H1LUMI.M901000.A01 K19802 78048081 00001 ACS-E-C (input cartridges C9400901 - C9401000) H01GOG.H1LUMI.M1001002.A00 K20223 78048081 00001 ACS-E-C (input cartridges C9401001 - C9401002) H1KFOM.H1LUMI.N003021.A00 K39346 78048081 00001 ACS-E-C (input cartridges C9401003 - C9401021) H01GOG.H1LUMI.C1022112.A00 K43364 78048081 00001 ACS-E-C (input cartridges C9401022 - C9401130)! P.S. Jobs with the tapes C9401131 - C9401158 still in a queue are waiting for tape units. 15/6/94 ======================= andreev === Lumi RUN# 432 Start lumi run432 date: 15/6/94 Collision time: 14:51:34 - 20:14:25 Currents (mkA): Ie= 23771.00, Ip= 32701.00 Peak luminosity: 1201.572 mb-1 s-1 Peak spec.lumi : 316.539773 mb-1 s-1 mA-2 Number of collided b.: 151 Number of e-filled b.: 167 Number of p-filled b.: 167 Number of e-pilot b.: 16 Number of p-pilot b.: 16 HERA total lumi: 11066.080838 mkb-1 H1 Run total lumi: 9676.762674 mkb-1 H1 data taken lumi: 6851.288449 mkb-1 H1 Runs: 79148 - 79176 HERA - physics: 10346.73646 mkb-1 H1Run - physics: 6859.814284 mkb-1 H1data - physics: 4822.90949 mkb-1 H1 Runs: 79153 - 79176 Tot curr/rate factor: 0.37% C/R F H1Run gated: 0.39% Rand.C.F: 1.4% RCF Run gated: 1.39% Relative ET trigg accept.: 0.3363 17/6/94 =================== grindhammer === Lumi RUN# 433 Start lumi run433 date: 17/6/94 Collision time: 1:06:33 - 1:11:17 Currents (mkA): Ie= 11100.00, Ip= 38600.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: 1.347233 mkb-1 H1 Run total lumi: 2.871693 mkb-1 H1 data taken lumi: 2.727785 mkb-1 H1 Runs: 79377 - 79377 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 79377 - 79377 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 3.71% RCF Run gated: 3.71% Relative ET trigg accept.: Not calc. 17/6/94 =================== grindhammer === Lumi RUN# 434 Start lumi run434 date: 17/6/94 Collision time: 1:50:28 - 6:26:50 Currents (mkA): Ie= 23706.00, Ip= 38600.00 Peak luminosity: 818.948 mb-1 s-1 Peak spec.lumi : 185.272419 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: 13733.066869 mkb-1 H1 Run total lumi: 12612.4838 mkb-1 H1 data taken lumi: 7005.9465 mkb-1 H1 Runs: 79381 - 79391 HERA - physics: 13031.110662 mkb-1 H1Run - physics: 11211.690025 mkb-1 H1data - physics: 5792.754135 mkb-1 H1 Runs: 79383 - 79391 Tot curr/rate factor: 0.24% C/R F H1Run gated: 0.25% Rand.C.F: 1.48% RCF Run gated: 1.54% Relative ET trigg accept.: 0.3503 17.06.1994 ===== dice2 ======== H1KFOM === MONITRIG Selection Status All proclaimed at Nelly's message Data Sets with selected H1Lumi MONITRIG-events: bytes Data set name 200055240 H1KFOM.H1LUMI.M117499.A00 199999800 H1KFOM.H1LUMI.M117499.A01 199999800 H1KFOM.H1LUMI.M117499.A02 129064320 H1KFOM.H1LUMI.M117499.A03 87428880 H01GOG.H1LUMI.C500560.A00 87983280 H1KFOM.H1LUMI.M647650.A00 200055240 H01GOG.H1LUMI.C704800.A00 99015840 H1KFOM.H1LUMI.M801854.A00 118613880 H01GOG.H1LUMI.C855900.A00 200055240 H1KFOM.H1LUMI.M901000.A00 4712400 H1KFOM.H1LUMI.M901000.A01 2106720 H01GOG.H1LUMI.M1001002.A00 30547440 H1KFOM.H1LUMI.N003021.A00 152543160 H01GOG.H1LUMI.C1022112.A00 were compressed into the data sets(1264431 events and 1.8 GBytes): 260041320 H1KFOM.H1LUMI.M1171130.B00 260013600 H1KFOM.H1LUMI.M1171130.B01 259985880 H1KFOM.H1LUMI.M1171130.B02 260013600 H1KFOM.H1LUMI.M1171130.B03 259985880 H1KFOM.H1LUMI.M1171130.B04 260013600 H1KFOM.H1LUMI.M1171130.B05 239833440 H1KFOM.H1LUMI.M1171130.B06 I used diceS-queue for high mentioned compressing (30 min of SGI-CPU it were a little not enough). Task with final compressing was at diceS Running status from 21;12 up to 22:35 (due to making of 7 stageout procedure for output data sets). Stagin procedures for input data sets were made before submitting of final compressing job. It was put SPLITMB=260 FPACK options (as seems largest possible size of data set now at dice2). All final H1Lumi MONITRIG data sets were stageouted into IBM-cartridges H1KFOM.H1LUMI.M1171130.B00 K44121 78048081 00001 ACS-E-C H1KFOM.H1LUMI.M1171130.B01 K45487 78048081 00001 ACS-E-C H1KFOM.H1LUMI.M1171130.B02 K45667 78048081 00001 ACS-E-C H1KFOM.H1LUMI.M1171130.B03 K49753 78048081 00001 ACS-E-C H1KFOM.H1LUMI.M1171130.B04 K10983 78048081 00001 ACS-E-C H1KFOM.H1LUMI.M1171130.B05 K13419 78048081 00001 ACS-E-C H1KFOM.H1LUMI.M1171130.B06 K29619 78048081 00001 ACS-E-C 17.06.1994 ==================== H01LNS === Draft L4 conclusions...... DRAFT: Below are some Histos that were taken at the level of L4. They are not graphical, because they are for LLO, but they have an advantage to contain digital values, look at them. Are shown only the most interesting Pictures - see the titles. Sorry for waisting LLO space for Pictures, better to see them. The pictures were taken for ALL LUMI RUN#s (up to-day), but only for the selected SINGLE NRUNs, 1-st and last of RUN#. That means, they do not contain all the accumulated statistics, but do reflect all the accomulated time period of LUMI-RUN#s. ----------------------------------------------------------------------- DQ STARTED 16/06/94 15.09.47 1 HS 10001 0 51 Entries ------------ Min/Max Mean/Sigma Bins Low X-In High X 0.25 25.5969 60 3 45 3 37. 26.2614 MEAN of ET+PD+VC @ET*PD DQ 0 +L----+----L----+----L----+----L----+----L----+----L----+----+ 5. T X X T I X X X I I X X X X XX X I I X X X X XXXX X XXX I I XX X XXXX XXX XXXXXXXXXX X I 0. +L----+----L----+----L----+----L----+----L----+----L----+----+ 24.5 25.5 26.5 27.5 28.5 29.5 30.5 13 1 1314 511 2532131222 1 1 HS 10005 2 51 Entries ------------ Min/Max Mean/Sigma Bins Low X-In High X 5.44346 757.438 60 0 50 1 15672.2 2959.2 N_LUMI/H1Luminosity DQ 0 +L----+----L----+----L----+----L----+----L----+----L----+----+ 14. IX I IX I IX I IX I 10. TX T IX I IX I IX I IX I TX T IX X I IX XXX X I IX XXXX X X X I IX XX XXXXXXXXXX X X X X X X X XX XX X I 0. +L----+----L----+----L----+----L----+----L----+----L----+----+ 0. 1000. 2000. 3000. 4000. 5000. 6000. 1 4 11 1111124331 1 1 1 1 1 2 1 11 13 2 1 HS 10006 0 51 Entries ------------ Min/Max Mean/Sigma Bins Low X-In High X 0.0322581 0.793903 50 0 51 0 0.825342 0.672235 N_LUMI/N_PD == ACCEPT DQ 0 +L----+----L----+----L----+----L----+----L----+----+ 11. I X I 10. T X T I XX I I XX I I XX I I XX I T XXX T I XXXX I I X X XXXXX I I X X X XXXXXXX I I X XXX XXX XX X XXXXXXX I 0. +L----+----L----+----L----+----L----+----L----+----+ 0. 0.2 0.4 0.6 0.8 1. 1 1 211 121 11 3 3239154 ----------------------------------------------------------------------- DRAFT: A minimal SUMMARY: 1. For The MEAN Energy (ET+PD+VC) @ trigger ET*PD: - The MEAN Energy (ET+PD+VC) is 25.60 GeV, not 27.5 Gev, it's bad - The SIGMA of this Energy (now taken by eye) is ~+/-0.5 GeV - The Total Scattering of this Energy is from 0.25 till 37. GeV (!) - The unshown histos say that the scattering is RANDOM along the Time - You remember that Energy_Error of ~1 Gev is not yet too dangerous. 2. For The N_LUMI/H1Luminosity: - This is the Normalyzed value of the Bremsstrahlung_Events_Count, It is supposed to be about constant, and connected to sigma_vis - But: Only ~40% of Runs are grouped in a peak at ~1000.unitsÙ, SIGMA at the peak is ~+/-200. == ~+/-20%, it is too large - I am afraid that this %% should be compared with L_Systematic_Error - The Total Scattering at the picture is awfull: 0 - 1000 - 5000 (!) - I think that the most of this scattering is because of Prescalers, Than this picture (only this) would have changed seriously. 3. For N_LUMI/N_PD: - This value is supposed to be some kind of "Relative Acceptance", As this, it must be nearly the constant, connected to sigma_vis - A very good surprise (after point 2.) - a good peak is OK ! - In this peak ~3/4 == 75% of the values are accomulated - The MEAN of this peak is ~0.77, should be understood(!) - The SIGMA at the peak is ~ 0.2, relative is ~25%, too large - I am afraid that this %% should be compared with L_Systematic_Error - The Total scattering is yet large: from 0.03 till 0.82 - I am sure, the Total scattering can be decreased by cuts, but (?) DRAFT: An Overall CONCLUSION (at present): - The Mean Bremsstrahlung Energy (1.) is about satisfactory, - The "Relative Acceptance" (3.) is about satisfactory, but warrying, - The Normalyzed N_LUMI (2.) are not yet understood (at least by me). PS: Certainly, the info will be extended (a problem of cpu!). But a Question: Is it worth to show this at DQ-meeting ? L.Shtarkov, at DESY. 17.06.1994 ==================== H01LNS === for L4 REFerencies ....... After last update of Edep-Etrig 15.06.94, there were RUNS# 429-434. For every RUN#, histos were made for the start and the end Runs, and among them I see 4 candidats to L4_REFerencies that: 1) have a reasonable statistics 2) all have for ET_(Edep-Etrig) "a dubble_peak structure", 2) differ mostly in Etag_Energy_spectrum as it is shown: peak at peak at Entries ~17 Gev ~20 GeV for E_tag 1. RUN#431 R079141 no yes ~ 6000 2. RUN#431 R079144 yes yes ~ 2200 3. RUN#434 R079383 yes yes ~ 8000 4. RUN#434 R079390 yes no ~ 3600 I can'not make choice between them, Moreover I suspect that dubble-peaking is an important feature of Run. It is possible to make many more pictures, but it hardly worth doing. The relevant copies for 4 RUNs are made and are ready for inspection. I hope that S.Levonian will make choice between candidats. L.Shtarkov. 17.06.1994 ==================== F11LEV === L4 and L5(!) plots ....... Few very brief comments to L.N.S. messages. 1) Why only L4 histos are discussed so far? Often a comparison with L5 figures (from LREC module) are useful. Please inspect them also! 2) One example: E(e)+E(gamma). At L4 these are deposited energy, which should be typically by 5-6% less then reconstructed (leakage corr.) Thus it is not surprising, that at L4 the sum is < 27.5 GeV. 3) "Double peak" feature of e-tag has been discussed many-many times, also in LLO. More energetic "peak" - bgr. from off-momentum e-, a broad distribution between 8 and 20 GeV with the max. around 17GeV is photoproduction signal. Those relative amount depends on the bgr. conditions at H1 and strongly varying. 4) Distr. of E_dep-E_trig indicate the problem with calibration of the trigger sums, or normal energy calibration, or both. We discussed this with A.M. I personally believe, that it is most likely due to the trigger en.sums. As far as I know, Yura are going to investigate this. 5) Selection of runs. Only G and M ep runs with good statistics should be used. This can be seen typing H1EP at IBM and getting for each ep run: integrated lumi (~ to the statistics expected), and run quality (*G, *M, *P). Short runs ("active" time<10 sec) should be discarded. 6) Prescale factors for each run and each subtrigger are stored in DB and can be easily retrieved by a standard H1 utility written by S.Egli (in H1UTIL library). For the absolute rate comparison they of course MUST be taken into account. 7) There is no sence to discuss possible systematics at the level of technical check plots. They are only intended to see whether the system works more or less correctly or not. Quantitative analysis is only possible after serious study of all lumi monitor triggers and: - good offline calibration, - vell understood trigger threshold and efficiencies, - absolutely clean event selection (trigger, signal vs bgr...) What must be always checked - large (beyond 3 sigma) deviations from the expected average values (e.g. 0 compared to 1000). But stat.err. must be taken correctly. Checked means not just report: run 79888 has some value of 0 instead of expected 1000, but look into the run and understand why (what was trigger mixture used, how events looked in the Event Display, compare L5 plots, etc.) 18.06.1994 ==================== H01LNS === agree with comments ...... I fully agree with ALL of S.Levonian's comments in LLO (see upstairs). As for L4, it was recommended to use L4 - by S.V.L. and by DQ-meetings. I have made only the first steps at L4, and, I would like to continue. I stay sure, that even the Draft signals from L4 COULD be made usefull. L.Shtarkov, at DESY. 18.06.1994 ==================== H1KAND === Dedicated Lumi Runs ...... At this night three H1LUMI's Dedicated Runs were written DURING STANDALONE e_BEAM. Only Luminosity branch and Central Trigger branch were involved into data taking at these Runs. Lumi branch was used standard trigger's set with the next prescale factors: Trigger Prescale 86 e_Tag 128 s91 PD_low 32 s92 Lcal 1 s93 WatVet 64 s94 ET@PDnVC 1 s95 ET@PD@VC 8 Short Run Summary: Run Number 79494 Number of events 27883 Start Time 18.06.94 at 1:25:21 Stop Time 18.06.94 at 1:50:02 Run Number 79497 Number of events 40375 Start Time 18.06.94 at 3:04:16 Stop Time 18.06.94 at 3:41:01 Run Number 79499 Number of events 144700 Start Time 18.06.94 at 3:42:12 Stop Time 18.06.94 at 5:52:10 P.S. at all Runs it were recorded option H1Lumi banks:LREF,LRPF(mode1) Synchronisation was switched on e-beam as source of HERA-clock It means that timing is differ from all previous data - so local calibration is needed for all high mentioned H1 Runs. 17.06.1994 ===== dice2 ======== H1KFOM === Relation Coefficients SetA It were selected ET&PD&nVC-events from high mentioned H1Lumi Monitrig data sets: 248663 events with ET&PD&nVC trigger were got from all 7 data sets, 131129 first events were got for recalibration of H1Lumi ET and PD channels (from Run 76846 up tio Run 77803). After Run 77803 it was installed new HVvcs and ET&PD&nVC-events after this Run will be used for recalibration of more late period of H1DataTaking94. From 131129 events it were used for calibration 71890 events (after all cuts). It was made 3 steps of calibration (as ordinary). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 1.102 1.127 1.093 1.096 1.130 1.195 1.124 1.073 1.179 1.157 2.193 1.002 0.994 1.199 1.030 1.079 0.971 0.983 0.970 0.945 1.031 1.026 1.030 1.014 1.014 1.041 1.022 1.001 1.030 1.012 1.048 0.948 1.013 1.068 0.976 1.204 0.983 1.023 0.931 0.911 0.888 0.981 1.104 1.074 0.887 0.967 0.954 1.106 0.000 ==> Relation Coeff.Set for PD 1.490 1.050 1.039 1.167 0.941 1.014 0.997 1.001 1.017 1.027 0.960 1.017 1.003 0.992 0.991 0.960 0.980 0.992 0.986 0.982 1.142 1.027 0.996 0.966 0.934 ==> Sig. at Relation Coeff.Set for ET 0.000 0.002 0.001 0.006 0.003 0.003 0.001 0.003 0.022 0.022 0.063 0.032 0.008 0.016 0.028 0.027 0.024 0.029 0.015 0.034 0.025 0.014 0.017 0.017 0.014 0.019 0.020 0.013 0.024 0.015 0.012 0.011 0.007 0.011 0.019 0.061 0.061 0.019 0.015 0.014 0.005 0.010 0.000 0.072 0.020 0.018 0.020 0.003 0.000 ==> Sig. at Relation Coeff.Set for PD 0.084 0.033 0.025 0.039 0.006 0.024 0.014 0.022 0.018 0.021 0.014 0.039 0.015 0.023 0.017 0.018 0.022 0.026 0.014 0.014 0.062 0.015 0.021 0.036 0.001 ==> Ent. at Relation Coeff.Set for ET 8 23 2 7 35 43 11 17 34 22 54 17 19 16 2659 2257 774 643 601 766 315 20026 31302 23621 19152 16126 13536 6113 4251 3797 3579 3002 3512 3165 2368 68 57 120 168 143 76 63 5 26 36 88 59 12 0 ==> Ent. at Relation Coeff.Set for PD 136 89 119 140 10 1045 10120 22820 12142 1200 3882 28724 56727 34733 4909 527 4826 9752 6731 665 65 48 74 42 7 Runs 76846- 77803 (ET&PD&nVC-sample - near 131K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.44 0.86 27.45 0.83 27.47 0.81 It were used as start values of CC for Photoproduction branch ones which were produced after 3rd step of previous 22-23 May 94 calibration and CCvcs as 5.0 (from H1DataBase). P.S. this message was erased from LLC 17.06.94 - I put it again today It was happened during similateneous using of editn command by S.L. and me at evening 17.06.94 19.06.1994 ===== dice2 ======== H1KFOM === Relation Coefficients SetB It were selected ET&PD&nVC-events from high mentioned H1Lumi Monitrig data sets: 248663 events with ET&PD&nVC trigger were got from all 7 data sets, 95647 last events were got for recalibration of H1Lumi ET and PD channels (from Run 77804 up to Run 78870) with new HV at VC. From 95647 events it were used for calibration 63816 events (after all cuts). It was made 3 steps of calibration (as ordinary). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 1.104 1.140 1.092 1.119 1.144 1.197 1.128 1.069 1.316 1.136 2.478 0.956 1.030 1.192 1.188 0.920 1.039 0.985 1.032 0.962 1.049 1.058 1.072 1.068 1.065 1.099 1.087 1.079 1.050 1.092 1.002 1.039 1.052 1.098 1.008 1.139 0.968 1.170 1.031 0.976 0.975 1.035 1.056 1.052 0.895 0.981 1.003 1.092 0.000 ==> Relation Coeff.Set for PD 1.707 0.937 0.980 1.271 0.936 0.996 0.971 0.953 0.962 1.074 0.925 0.908 0.948 0.952 0.984 0.985 0.939 0.931 0.935 0.957 1.376 0.882 0.938 0.921 0.930 ==> Sig. at Relation Coeff.Set for ET 0.001 0.004 0.001 0.020 0.004 0.006 0.000 0.002 0.095 0.011 0.083 0.018 0.022 0.006 0.022 0.029 0.028 0.027 0.033 0.078 0.025 0.027 0.038 0.041 0.045 0.052 0.065 0.051 0.041 0.035 0.022 0.034 0.025 0.028 0.022 0.015 0.057 0.031 0.029 0.027 0.011 0.017 0.002 0.054 0.022 0.021 0.030 0.008 0.000 ==> Sig. at Relation Coeff.Set for PD 0.018 0.023 0.017 0.011 0.002 0.011 0.018 0.021 0.020 0.015 0.038 0.166 0.050 0.046 0.016 0.014 0.041 0.037 0.023 0.014 0.061 0.018 0.016 0.019 0.001 ==> Ent. at Relation Coeff.Set for ET 6 14 2 4 20 29 7 10 25 20 42 9 8 16 3984 994 886 537 658 557 221 17816 28410 21404 16983 14139 11826 5280 3409 3470 1950 2649 2585 2369 1643 52 48 152 191 172 94 45 2 19 29 77 65 12 0 ==> Ent. at Relation Coeff.Set for PD 107 49 65 86 7 711 5886 11744 5722 567 4427 26087 50186 29490 4159 1134 8633 16672 10128 1000 65 47 105 50 7 Runs 77804- 78870 (ET&PD&nVC-sample - near 95K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.43 0.89 27.42 0.86 27.45 0.86 It were used as start values of CC for Photoproduction branch ones which were produced after 3rd step of previous 17 May 94 calibration and CCvcs as 2.5 (from H1DataBase). 19.06.1994 ===== dice2 ======== H1KFOM === CCvcs Estimation A&B...... It was made preliminary estimation of CCvcs for both data samples which are divided with HV changing at boundary of H1Runs 77803-77804. Estimation was made with using of 100th ntuples which were produced with ETPDVC-events from both data samples: 1) for events Run 76846-77803 CCvcs = 5.0 * 1.33 = 6.65 MeV/FADCcount 2) for events Run 77804-78870 CCvcs = 2.5 * 1.12 = 2.80 MeV/FADCcount Runs 76846- 77803 (ET&PD&VC-sample - near 39K events) all events xetcut Step Mean Sigma Mean Sigma 0 27.53 1.21 27.50 1.18 Runs 77804- 78870 (ET&PD&VC-sample - near 49K events) all events xetcut Step Mean Sigma Mean Sigma 0 ??.?? ?.?? 27.52 1.113 Due to problems with connection dice2/ibm at Sunday afternoon it is impossible to move produced LOOK-binary data sets with 100th ntuples (NO TCPIP, NO ILKSNS2 until about Monday morning) on IBMstorage Next step must be done - Photon Shape Fitting of 70 histo (s91.eq.1. and.pdrec.lt.999.and.vcdep.lt.0.2). I prepared at dice2 data sample with s91=1 data with 240422 events from both samples. Due to absence of any connection between dice2 and desy ibm - lets wait of Monday. Final tuning of CCvcs must be done after correction factor getting on Global Energy Shift at Photon Arm spectra. 19.06.1994 ==================== H1KFOM === HERA p-beams ............. Today after finishing of DESY Open Day (18.06.94) HERA p-ring activity was started near 06:45 with injection of 10 bunches p- beam which was ramped up to 820 GeV and existed at HERA up to 12:45 without any attempt to make something with e-beam. At 12:45 this beam was dumped. The same situation was repeated again after 17:00 (injection of 10 bunches and ramping (slow ramping) up to 820 GeV). Now (19:00) - Ep=677 GeV Ip= 2.03 mA. 19.06.1994 ==================== H01GOG === Selection................. I have selected ET&PD&VC and ET&PD&nVC events from H1Lumi MONITRIG data sets ( .C9400117 - .C9401130) after class 24th selection. The result is: 102355 events for ET&PD&VC, which one can find on the tape: H01GOG.ETPDVC.TAPE1 K12255 78048081 00001 ACS-E-C and 203374 events for ET&PD&nVC, which one can find on the tape: H01GOG.ETPDNVC.TAPE1 K12342 78048081 00001 ACS-E-C 19.06.1994 ===== dice2 ======== H1KFOM === s91=1 processing ........ It were selected 240422 events of (s91=1 only) from 7 data sets with H1Lumi monitrig-events: a) 123106 events were collected during Run 76846-77803 (old HV VC); b) 75033 events were collected during Run 77804-78870 (new HV VC). 240422-(123106+75033) events were collected during 77110-77112 H1Lumi dedicated Runs and were skipped during 100th tuples making. It were produced 100th ntuples for each from high mentioned data samples (not moved into IBM due to net-problems). First view on contents of high mentioned 100th ntuples put next preliminary conclusions: Sample with events s91=1 from Runs 76846-77803: 1) Effective value of PD1-threshold is near 4.0 GeV;<--PD_Low 2) Effective value of PD -threshold is near 4.5 GeV; 3) Effective value of PD2-threshold is near 11.0 GeV; 4) Photon Arm Spectrum (as seems) OK; 5) VCDEP-energy spectrum (as seems) OK. Sample with events s91=1 from Runs 77804-78870: 1) Effective value of PD1-threshold is near 4.0 GeV; 2) Effective value of PD -threshold is near 4.5 GeV; 3) Effective value of PD2-threshold is near 9.5 GeV; (?!) 4) Photon Arm Spectrum (as seems) is shifted into low energy - it means that estimated CCvcs is nor right - must be corrected after getting of GlobalEnergy Shift constants. 5) VCDEP-energy spectrum (as seems) is shifted into high energy - some poulation of statistics exists after 12 GeV (more then ordinary 20.06.1994 ===== dice2 ======== H1KFOM === new set of PDREC-spectra.. Today after net-problem resolving I moved to IBM LOOK-binary data sets with 100th tuples for data samples with different HVvc (for events S91=1 only): H1KFOM.ALOOKQ4.R76846 FAST13 3010200E 00000 DASD H1KFOM.ALOOKQ4.R77804 FAST16 3010200E 00000 DASD At interactive LOOK-session it were produced 70th histos for both data sets and written into the next LOOK-binary data set: H1KFOM.BLOOKQ.R76846 FAST07 3010200E 00000 DASD H1KFOM.BLOOKQ.R77804 FAST13 3010200E 00000 DASD Asking to L.N.Shtarkov to make Photon Arm Energy Spectra Fitting of high mentioned two 70 histos (ep-option). 20.06.1994 12:35 ============== H01LNS === PDFIT R76846; R77804...... PDFITs have been made for the request of A.F.; only "70", only "ep". Star(*) the lines: LIST 'H01LNS.JPDFIT.BLOOKQ.R76846.EP' LIST 'H01LNS.JPDFIT.BLOOKQ.R77804.EP' Be carefull: Not take the lines with "infER" == infinite ERROR ! I would prefer the variants: R lrun fg emin emax np eX e fitFLchi2 prob% E_shift%%+- B_res%%+- Entr Evnt R76846 70 14.0 35.0 42 ep 0 fitOK 29 39.0% (-2.1+-0.4)% (15+- 2)% 6387 13528 27.515 -> 26.946 d(Emax)= -0.569 +/- 0.114 39.0% R77804 70 10.0 35.0 50 ep 0 fitOK 36 34.9% (-5.1+-0.5)% (13+- 2)% 5694 8146 27.515 -> 26.125 d(Emax)= -1.390 +/- 0.128 34.9% 20.06.1994 ==================== H1KFOM === 42mA HERA p-beam ........ Today early morning it was dumped 10 bunches HERA p-beam with Ip near 2.0 mA (near 04:45) and it was injected powerful p-beam with Ip=42.25mA It was made succesful ramping and up to now this p-beam exists at HERA p-ring (near 1/4 design value). e-beam injection was started near 09:00 today morning. First 3 attempts were unsuccesful. Third attempt with Ie=29.62 mA is in progress now (11:56). Ramping started. 20.06.1994 ==================== H1KFOM === Lumi = 2.0*10**30 cm-2s-1 Today during 3rd attempt of e-filling with powerful Ip=42mA it was measured firstly at H1 IP record value of Luminosity as 2.0*10**30 cm-2s-1. This event was fixed during Lumi Tuning phase during H1Run 79648 at 12:22 (during 5 neighbour Lumi measurements - almost 50 sec.). It was Lumi RUN# 435. 20.06.1994 ==================== H01GOG === Selection status.......... I have selected the events of 24th class from MONITRIG cartridges: HERA03.H1POT2.MONITRIG.C9401131 ............................... ............................... HERA03.H1POT2.MONITRIG.C9401185 The following data set was produced: H01GOG.H1LUMI.C1131185.A00 K13413 78048081 00001 ACS-E-C * * * * * The events from all MONITRIG tapes with Lumi runs, which where written by this moment (HERA03.H1POT2.MONITRIG.C9400117-C9401185), were selected for Et&PD&VC and ET&PD&nVC triggers. The following data sets were produced: ET&PD&VC H01GOG.ETPDVC.TAPE2 (114386 events) K26472 78048081 00001 ACS-E-C H01GOG.ETPDVC.C1131185.A00 (10912 events) K18592 78048081 00001 ACS-E-C ET&PD&nVC H01GOG.ETPDNVC.TAPE2 (248663 events) K11145 78048081 00001 ACS-E-C H01GOG.ETPDNVC.C1131185.A00 (13390 events) K21206 78048081 00001 ACS-E-C 20.06.1994 ==================== H1KFOM === Global Shifts and CCvcs... Today it was made attempt to define Global Energy Shifts Constants and CCvcs tuning. It were used 100th ntuples which are kept at the next data sets: H1KFOM.ALOOKQ2.R76846 FAST12 3010200E 00000 DASD H1KFOM.ALOOKQ2.R77804 FAST17 3010200E 00000 DASD H1KFOM.ALOOKQ3.R76846 FAST18 3010200E 00000 DASD H1KFOM.ALOOKQ3.R77804 FAST05 3010200E 00000 DASD LOOK-binary data sets of ALOOKQ2-family were produced for ET&PD&nVC- events and ALOOKQ3-family - for ET&PD&VC-events. ALOOKQ4 (see above ) - for PD_Low-events. All 100th tuples were produced with 17/19 June 1994 Relation Coeffici- ents Sets and with 'corrected' CCvcs: 1) for events Run 76846-77803 CCvcs = 5.0 * 1.33 = 6.65 MeV/FADCcount 2) for events Run 77804-78870 CCvcs = 2.5 * 1.12 = 2.80 MeV/FADCcount and with 'zero' Global Energy Shifts Constants. After some tuning procedure which are made at LOOK-interactive mode it were obtained the next value of Global Shifts and CCvcs: 1) for events Run 76846-77803 CCvcs=6.65*0.997 = 6.630 MeV/FADCcount Global Shift PD = +1.8% (1.018 factor) Global Shift ET = -1.31305% (0.98695 factor) 2) for events Run 77804-78870 CCvcs=2.80*1.055 = 2.954 MeV/FADCcount Global Shift PD = +4.7% (1.047 factor) Global Shift ET = -3.248% (0.96752 factor) The next final digits at ETrec+PDrec energy spectra were obtained: 1) for events Run 76846-77803: a) ET&PD&nVC sample with both Xet cut and VCdep cut: mean 27.51 GeV Sigma 0.81 GeV b) ET&PD&VC sample with Xetcut cut: mean 27.52 GeV Sigma 1.20 GeV 2) for events Run 77804-78870: a) ET&PD&nVC sample with both Xet cut and VCdep cut: mean 27.51 GeV Sigma 0.88 GeV b) ET&PD&VC sample with Xetcut cut: mean 27.52 GeV Sigma 1.15 GeV I shall try to produce new family of 100th ntuples with involving of non-zero Global Energy Shift Constants and new 'tuned' values of CCvcs. As seems it is needed to repeat Photon Arm Energy spectra fitting for checking of new situations at Photon Arm spectra. 20.06.1994 ===== dice2 ======== H1KFOM === 100th Ntuples for MONITRIG It were produced 100th tuples for some from H1Lumi monitrig-events: (ET&PD&nVC - at ZLOOKQ2-LOOK datasets, ET&PD&VC - at ZLOOKQ3 datasets, PD_Low - at ZLOOKQ3- datasets). All elements of these 100th tuples were calculated with Relation coefficients from 17/19.06.94 and today proclaimed Global Energy Shifts and CCvcs. H1KFOM.ZLOOKQ2.R76846 FAST07 3010200E 00000 DASD H1KFOM.ZLOOKQ2.R77804 FAST13 3010200E 00000 DASD H1KFOM.ZLOOKQ3.R76846 FAST16 3010200E 00000 DASD H1KFOM.ZLOOKQ3.R77804 FAST09 3010200E 00000 DASD H1KFOM.ZLOOKQ4.R76846 FAST13 3010200E 00000 DASD H1KFOM.ZLOOKQ4.R77804 FAST07 3010200E 00000 DASD It were prepared new 70th histos with Photon Arm Energy spectra which are kept at the next LOOK-binary data sets: H1KFOM.BLOOKQ1.R77804 FAST01 3010200E 00000 DASD H1KFOM.BLOOKQ1.R76846 FAST04 3010200E 00000 DASD Asking to L.N.Shtarkov - make please fitting of high mentioned 70th histos with the same manner as previous today histos. 20/6/94 ======================= H1ksol === Lumi RUN# 435 Start lumi run435 date: 20/6/94 Collision time: 12:03:49 - 17:05:55 Currents (mkA): Ie= 27362.00, Ip= 42100.00 Peak luminosity: 1369.889 mb-1 s-1 Peak spec.lumi : 432.295739 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: 11312.804731 mkb-1 H1 Run total lumi: 10401.6814 mkb-1 H1 data taken lumi: 8843.4286 mkb-1 H1 Runs: 79646 - 79659 HERA - physics: 7415.183574 mkb-1 H1Run - physics: 5462.772021 mkb-1 H1data - physics: 4199.815641 mkb-1 H1 Runs: 79652 - 79659 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 3.02% RCF Run gated: 2.93% Relative ET trigg accept.: 0.3279 P.S. really Peak Luminosity: 2000 mb-1 s-1 (see above). 20.06.1994 19:15 ============== H01LNS === new PDFIT R76846; R77804.. PDFITs have been made for the request of A.F.; only "70", only "ep". Star(*) the lines: LIST 'H01LNS.JPDFIT.BLOOKQ1.R76846.EP' LIST 'H01LNS.JPDFIT.BLOOKQ1.R77804.EP' Be carefull: Not take the lines with "infER" == infinite ERROR ! I would prefer the variants: R lrun fg emin emax np eX e fitFLchi2 prob% E_shift%%+- B_res%%+- Entr Evnt R76846 70 14.0 35.0 42 ep 0 fitOK 37 13.8% (-0.3+-0.4)% (16+- 2)% 6419 13667 R76846 70 16.0 35.0 38 ep 0 fitOK 26 39.3% (-0.1+-0.4)% (15+- 2)% 5514 13667 R76846 70 18.0 35.0 34 ep 0 fitOK 17 71.0% ( 0.0+-0.4)% (14+- 2)% 4636 13667 R77804 70 8.0 35.0 54 ep 0 fitOK 47 18.1% (-0.9+-0.5)% (15+- 2)% 6747 8234 20.06.1994 ==================== F11LEV === New calibration in DB..... Today new calibration banks for the two run periods described above were put into the database (banks LFRC and LESC): LESC 32 e-p data 406202109 76846 77803 3 940620 F11LEV 33 e-p data 406202110 77804 0 3 940620 F11LEV The following values were stored (ET-shift, PD-shift, VCsp) 76846-77803 = 0.987 1.021 6.60 77804-> now = 0.971 1.050 2.90 There is a large (ca 5-6%) difference in ET-spectrum for lumi data with this new calibration, and MC. That means, that either ET-position is wrong (6-7mm more from the beam pipe), or beam conditions has changed compared to 93 (shape by the way is OK, just overall shift). ==> Therefore, we need as soon as possible to verify actual ET-accep- tance from the data (monitrig files). For that one needs all VC (s93) and PD_low (s91) events to be reconstructed with the new CC from the database, and by standard LREC from H1REC. Could for example Nelly come to me and I explain what to do and give an example job for that. Sorry, it would be much easier if I do it, but: 1) I have now to prepare new sigma-tot value for Glasgow (93-data) 2) The knowledge anyway must be propagated such that it is not lost when I could no longer contribute seriously to LUMI support. 20/6/94 ====================== andreev === Lumi RUN# 436 ............ Start lumi run436 date: 20/6/94 Collision time: 19:02:53 - 20:26:07 Currents (mkA): Ie= 23707.00, Ip= 40700.00 Peak luminosity: 892.208 mb-1 s-1 Peak spec.lumi : 221.132295 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: 2959.73411 mkb-1 H1 Run total lumi: 2705.781798 mkb-1 H1 data taken lumi: 2420.198044 mkb-1 H1 Runs: 79664 - 79670 HERA - physics: 1755.667235 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: -1 - 79670 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 6.16% RCF Run gated: 6.29% Relative ET trigg accept.: 0.3302 PS:Integrated Lumi for this Run was not reset. See comment to the Lumi Run #437 (Yu.S) 20/6/94 ====================== andreev === Lumi RUN# 437 ............ Start lumi run437 date: 20/6/94 Collision time: 20:26:49 - 20:55:42 Currents (mkA): Ie= 13247.00, Ip= 38800.00 Peak luminosity: 684.862 mb-1 s-1 Peak spec.lumi : 296.379418 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: 4238.989272 mkb-1 H1 Run total lumi: 3816.229484 mkb-1 H1 data taken lumi: 3504.870232 mkb-1 H1 Runs: 79671 - 79672 HERA - physics: 203.679069 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 79672 - 79672 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 4.6% RCF Run gated: 4.74% Relative ET trigg accept.: 0.3359 PS: Runs 436 437 were taken during the same e-fill. The reason was very hard background condition in H1 IP, and H1 shift crew had asked HERA CR to tune p beam. Before tuning was started run#436 was completed,and then new Lumi Run was started. Integrated Lumi is for the two Runs. Then e beam was lost,and afterwards p beam too. There was a overheating alarm from PD,we decided to switch HV off. "Investigations" showed that it was false alarm,as it disappeared after moving platforms down. But these "investigation" costed about 30 min of Luminosity. "Fortunately" Lumi for H1 did not suffer of this accident,because there were no data taking due to very bad condition for H1.(Yu.S) 21.06.1994 ==================== F11LEV === Misuse of LLC/LL0......... Some people still use EDIT command instead of LIST just to read this logbook. This increase a risk of overwriting the content. I already asked people to modify their commands (see F11LEV.CLIST(LL0)) for reading. Please, H01BPS, H1KMAL - do it. 21.06.1994 ===== dice2 ======== H1KFOM === Statistics from MONITRIG.. There are some digits from analyze of H1Lumi Monitrig events.As seems its can be useful for somebody at H1Lumi team. Only data which are written at early mentioned 7 data sets are presented (eTAG=1 and VC=1 events are not analyzed yet): PD_Low 240422 - overall statistics (including Runs 77110-77112) 123106 - statistics at 1st sample (76846-77803) 75033 - statistics at 2nd sample (77804-78870) *) 1.2 - percent of ovfl situations at p11-element -1st sample 0.5 - percent of ovfl situations at p11-element -2nd sample 74.4 - percent of entries into 100th ntuple (it means that there is good reconstruction at one or both H1Lumi Arm) at 1st sample 64.7 - percent of entries into 100th ntuple (it means that there is good reconstruction at one or both H1Lumi Arm) at 2nd sample ETPDnVC 248663 - overall statistics (including Runs 77110-77112) 131129 - statistics at 1st sample (76846-77803) 95647 - statistics at 2nd sample (77804-78870) 0.2 - percent of ovfl situations at p11-element -1st sample 0.1 - percent of ovfl situations at p11-element -2nd sample 99.3 - percent of entries into 100th ntuple (it means that there is good reconstruction at one or both H1Lumi Arm) at 1st sample 99.4 - percent of entries into 100th ntuple (it means that there is good reconstruction at one or both H1Lumi Arm) at 2nd sample 54.8 - percent of events which were used for calibration after all cuts (coordinates and energy) at 1st sample; ***) 66.7 - percent of events which were used for calibration after all cuts (coordinates and energy) at 2nd sample; ETPDVC 114386 - overall statistics (including Runs 77110-77112) **) 40678 - statistics at 1st sample (76846-77803) 60010 - statistics at 2nd sample (77804-78870) 0.03- percent of ovfl situations at p11-element -1st sample 0.01- percent of ovfl situations at p11-element -2nd sample 96.6 - percent of entries into 100th ntuple (it means that there is good reconstruction at one or both H1Lumi Arm) at 1st sample 95.4 - percent of entries into 100th ntuple (it means that there is good reconstruction at one or both H1Lumi Arm) at 2nd sample *) p11-element is element with max quantity of ovfl situations at all samples (may be excluding eTAG events - due to antiPD); **) remember that s95 trigger bit was proclaimed as MONITRIG not from start of first sample. ***) trigger ET&PD&nVC became more 'right' with new VC HV setting. 21.06.1994 ===== dice2 ======== H1KFOM === Selected Monitrig Events.. I stageouted some data sets which were used for calibration procedure from dice2-environment into IBM-storage (for any case). Nelly made this step at IBM (a little later) nevetheless I made this step for any case (cross check): H1KFOM.ETPDNVC.M1171130.C00 K41947 78048081 00001 ACS-E-C H1KFOM.ETPDNVC.M1171130.C01 K13275 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M1171130.C00 K42256 78048081 00001 ACS-E-C H1KFOM.S91.M1171130.C00 K18761 78048081 00001 ACS-E-C H1KFOM.S91.M1171130.C01 K18877 78048081 00001 ACS-E-C ETPDNVC - data sets - 248663 events <-- the same as at Nelly's tape ETPDVC - data set - 114386 events <-- the same as at Nelly's tape S91 - data sets - 240422 events. I shall try to select VC=1 events and eTAG events and create new data sets at IBM-storage with these events later. 21.06.1994 ==================== H1KFOM === Problems with Calibration You can see from previous messages the next strange difference at some obtained at Calibration Procedure digits: "..... 1) for events Run 76846-77803: a) ET&PD&nVC sample with both Xet cut and VCdep cut: mean 27.51 GeV Sigma 0.81 GeV <-- 0.81 2) for events Run 77804-78870: a) ET&PD&nVC sample with both Xet cut and VCdep cut: mean 27.51 GeV Sigma 0.88 GeV <-- 0.88(?) ..." OR 1) for events Run 76846-77803: ".... ==> Sig. at Relation Coeff.Set for ET 0.000 0.002 0.001 0.006 0.003 0.003 0.001 0.003 0.022 0.022 0.063 0.032 0.008 0.016 0.028 0.027 0.024 0.029 0.015 0.034 0.025 0.014 0.017 0.017 0.014 0.019 0.020 0.013 <- <0.02 0.024 0.015 0.012 0.011 0.007 0.011 0.019 0.061 0.061 0.019 0.015 0.014 0.005 0.010 0.000 0.072 0.020 0.018 0.020 0.003 0.000 ==> Sig. at Relation Coeff.Set for PD 0.084 0.033 0.025 0.039 0.006 0.024 0.014 0.022 0.018 0.021 0.014 0.039 0.015 0.023 0.017 <-- <0.04 0.018 0.022 0.026 0.014 0.014 0.062 0.015 0.021 0.036 0.001 ...." 2) for events Run 77804-78870: "..... ==> Sig. at Relation Coeff.Set for ET 0.001 0.004 0.001 0.020 0.004 0.006 0.000 0.002 0.095 0.011 0.083 0.018 0.022 0.006 0.022 0.029 0.028 0.027 0.033 0.078 0.025 0.027 0.038 0.041 0.045 0.052 0.065 0.051 <- >0.02 0.041 0.035 0.022 0.034 0.025 0.028 0.022 0.015 0.057 0.031 0.029 0.027 0.011 0.017 0.002 0.054 0.022 0.021 0.030 0.008 0.000 ==> Sig. at Relation Coeff.Set for PD 0.018 0.023 0.017 0.011 0.002 0.011 0.018 0.021 0.020 0.015 0.038 0.166 0.050 0.046 0.016 <- >0.04 0.014 0.041 0.037 0.023 0.014 (especially p11) 0.061 0.018 0.016 0.019 0.001 ...." Detailed investigations of Relation Coefficients behaivour with time show the next interesting facts: a) at 1st sample (Runs 76846-77803) no any jumps were fixed at all 'hot' channel Relation Coefficients behaivours with time (only fluctuations around some mean value); b) at 2nd sample (Runs 77804-78870) it were fixed large 'jumps' at almost all 'hot' H1Lumi detrector channels Relation Coefficients behaivour with time. High mentioned 'jumps' were fixed during involving into calibration of ET&PD&nVC-events from Lumi RUN# 413 (Run 78381 etc.). as example: Relation Coefficient for p11 'jumped' from value near 1.0 into 0.4, p12: 0.98 --> 0.85,p13: 0.98 -->0.88 e21: 1.05 --> 1.10; e22 1.05 --> 1.15; e23:1.05 -->1.15 e24: 1.04 --> 1.15; e25 1.06 --> 1.18; e26:1.04 -->1.20 e27: 1.04 --> 1.20. After Run78381 Relation Coefficients were changed permanently without large jumps and became more or less stable after Run78797 and got new stable values: as examples: p11 0.93; p12 0.93; p13 0.97; e21 1.05; e22 1.07; e23 1.08; e24 1.08; e25 1.12; e26 1.12; e27 1.10. High mentioned 'non-stable' time period includes all Lumi RUNs from #413 up to #424. Stability with new values was fixed from Lumi RUN #425. Only single correlation was seen with high mentioned Relation Coefficients Set non-stability - huge p-beam. At Lumi RUN# 413 it was fixed Ip=30 mA and during all next Runs Ip was near or around 30 mA. At Lumi RUN# 425 Ip was fixed near 23 mA and RC stability returned again. Previous time period with large Ip (28/05/94) had not any influence on RC behaivour. Problem is under study. First conclusion - it is needed to divide 2nd sample on 3 subsumples (77804-78174,78381-78784,78785-78870) and to make recalibration. Last period had little weight at RC-defining for 2nd sample - so RC which are at H1DataBase for current data are not correct - due to its are working for all data from Run 77804 up to now and late. 21.06.1994 ==================== H01LNS === Data Quality Meeting ..... A compressed Copy of the Thesis-Transparensy, that was shown at Lumi-report at the last Data-Quality Meeting: STATUS of LUMI 07. - 21.06.94 1. LUMI PERFORMANCE: The LUMI-VALUES have been sent OK to Data-Base, The CURRENT INFO + RUN SUMMARIES were OK. A Good News 20.06.94: The Peak Luminosity had reached record of 2000 mb-1 s-1. Lumi apparatus not overloaded. 2. L4+L5 MONITORING: L4+L5 have shown the OK and STABILITY of Param's. Transp's: Single L4, L5-Pictures + Summary Pictures. 3. MONITRIGs: By the to-Day, ALL LUMI - Monitrigs were selected, OK. Transp's: A.Fomenko, All Mon's: (x,y)-e-beam; Brms-E. 4. LUMI CALIBRATION: On the basis of selected Monitrigs, Recalibration is made. S.Levonian put new calibration to DB, for 2 run periods. He noticed a differency of data and MC, To be analyzed. 5. An INCIDENT: One day S.Levonian discovered, LRTL bank was lost. The lost info was recovered OK, by efforts of himself. Z. THE PRESENT STATUS: Lumi Performance is OK. Then, there were shown 4 transparansies: 1 for L4 + 1 for L5 + 2 from A.Fomenko (n.3.). Nothing surprizing have happend at the report. L.Shtarkov, DESY. 21.06.1994 ===== dice2 ======== H1KFOM === Selected H1Lumi Monitrig.. It were selected events with (s86=1 only) and with (s93=1 only) from early mentioned 7 H1Lumi Monitrig data sets: 1) S86=1 only 98728 events from total 1264431 (141.5 MBytes) 2) S93=1 only 105277 events from total 1264431 (150.3 MBytes) Produced data sets were stageouted into IBM cartridges: H1KFOM.S86.M1171130.C00 K19743 78048081 00001 ACS-E-C H1KFOM.S93.M1171130.C00 K11677 78048081 00001 ACS-E-C Selection procedure got 1436 sec of SGI CPU for s86 and 1768 sec of SGI CPU for s93 (diceS-queues - small jobs - up to 03:00 hours of CPU). 21.06.1994 ===== dice2 ======== H1KFOM === 100th Ntuples for MONITRIG It were produced 100th tuples for some from H1Lumi monitrig-events: (VC=1 - at ZLOOKQ5-LOOK datasets, eTAG - at ZLOOKQ6 datasets) All elements of these 100th tuples were calculated with Relation coefficients from 17/19.06.94 and 20/06 by me proclaimed Global Energy Shifts and CCvcs. H1KFOM.ZLOOKQ5.R76846 FAST04 3010200E 00000 DASD H1KFOM.ZLOOKQ5.R77804 FAST08 3010200E 00000 DASD H1KFOM.ZLOOKQ6.R76846 FAST08 3010200E 00000 DASD H1KFOM.ZLOOKQ6.R77804 FAST08 3010200E 00000 DASD For events from Runs 76846-77803: 1) eTAG (27296 events, 26849 entries at 100th ntuple, 38 ovfl at e15) 2) VC=1 (19020 events, 6552 entries at 100th ntuple, 59 ovfl at p11) For events from Runs 77804-78870: 1) eTAG (71432 events, 69591 entries at 100th ntuple,144 ovfl at e15) 2) VC=1 (50157 events, 13782 entries at 100th ntuple, 33 ovfl at p11) P.S. I am sorry but I found at eTAG samples situations with eTAG=1 and PD=1 (?!) - 5 situations at 1st sample and 20 at 2nd eTAG=1 and VC=1 (?!) - 4 situations at 1st sample and 18 at 2nd May be it is my error. I found at VC=1 samples situations with eTAG=1(?!): VC=1 and eTAG =1 - 4 situations at 1st sample and 1 at 2nd May be it is my error again. 21.06.1994 ===== dice2 ======== H1KFOM === 48 mA p-beam.............. Today evening at 20:20 into HERA p-ring it was injected huge p-beam. Ip total is a little more then 48 mA. There are 170 bunches with 337 mkA max bunch current. Ramping started and in progress now (20:27) 21/6/94 ======================= andreev === Lumi RUN# 438............. Start lumi run438 date: 21/6/94 Collision time: 4:15:16 - 4:18:41 Currents (mkA): Ie= 0.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.: 0 Number of p-filled b.: 0 Number of e-pilot b.: 0 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: 79694 - 79694 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 79694 - 79694 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. 22/6/94 ======================= rick === Lumi RUN# 439............. Start lumi run439 date: 22/6/94 Collision time: 3:20:35 - 4:15:28 Currents (mkA): Ie= 23450.00, Ip= 42300.00 Peak luminosity: 1847.924 mb-1 s-1 Peak spec.lumi : 395.971213 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: 5707.6578 mkb-1 H1 Run total lumi: 5076.786463 mkb-1 H1 data taken lumi: 3753.173528 mkb-1 H1 Runs: 79828 - 79832 HERA - physics: 3940.554398 mkb-1 H1Run - physics: 2932.601656 mkb-1 H1data - physics: 1752.917486 mkb-1 H1 Runs: 79831 - 79832 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 3.42% RCF Run gated: 3.27% Relative ET trigg accept.: 0.2883 22/6/94 ======================= rick === Lumi RUN# 440............. Start lumi run440 date: 22/6/94 Collision time: 5:23:06 - 8:20:17 Currents (mkA): Ie= 24278.00, Ip= 42100.00 Peak luminosity: 1981.817 mb-1 s-1 Peak spec.lumi : 361.584932 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: 12238.245838 mkb-1 H1 Run total lumi: 6361.389 mkb-1 <---? H1 data taken lumi: 5111.0248 mkb-1 <---? H1 Runs: 79836 - 79852 HERA - physics: 11888.216234 mkb-1 H1Run - physics: 4025.675862 mkb-1 <---? H1data - physics: 2879.455142 mkb-1 <---? H1 Runs: 79839 - 79852 Tot curr/rate factor: 0.41% C/R F H1Run gated: 0.42% Rand.C.F: 1.78% RCF Run gated: 1.72% Relative ET trigg accept.: 0.3617 PS: H1Run and H1data Lumi values dropped down at ~7.15 by about 2.5 nb-1. So these values in the Run Summary have to be corrected. (Yu.S) 22/6/94 ======================= Shtarkov=== Lumi RUN# 441 ............ Start lumi run441 date: 22/6/94 Collision time: 10:11:40 - 12:04:51 Currents (mkA): Ie= 23108.00, Ip= 41600.00 Peak luminosity: 1849.169 mb-1 s-1 Peak spec.lumi : 422.519053 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: 8671.103301 mkb-1 H1 Run total lumi: 5771.036411 mkb-1 <--? H1 data taken lumi: 3403.256237 mkb-1 <--? H1 Runs: 79863 - 79877 HERA - physics: 6777.204068 mkb-1 H1Run - physics: 3245.343309 mkb-1 <-- ? H1data - physics: 1588.923045 mkb-1 <-- ? H1 Runs: 79868 - 79877 Tot curr/rate factor: 0.73% C/R F H1Run gated: 0.75% Rand.C.F: 2.03% RCF Run gated: 1.99% Relative ET trigg accept.: 0.3565 PS:H1Run and H1data Lumi values have to be recalculated-the reason the same as in prevoius Run(jump was at 11.04). (Yu.S) PS1: Today at 11:37 it was fixed spike at Current Luminosity Value So - all Integrated Lumi values at our Run Summary are non- correct and must be recalculated (a.f). 22.06.1994 ==================== F11LEV === LUMIMON files ............ From today on an automatic selection of all LUMI events is running at SGI data logging job (first run: ~79930). That means we do not need any more to spend our time for selection and copying of our monitoring events. We have however to test, that everything is ok (no losses and no extra non-lumi events appear). As soon as we verify that, class 24 will be used for other purposes in future! A list of selected banks: SELECT LMONI BLOCK = HEAD HEAR TEL1 TLV1 TSTC ZRCT & LRTN LREE LRPE LREP LRPP LRTF LREF LRPF & LETR LPDR LRXY An average event size is then ~ 1kb. As soon as 100 Mb of these data are collected on SGI disk - they are copied to IBM cartridges under the names: HERA03.H01.LUMIMON.C9400001 etc. If it will continue as it goes now, a first file will appear on IBM tomorrow. 22.06.1994 ==================== F11LEV === errors in integrated lumi Since almost two weeks (or even more) we observe from time to time an errors (steps to the smaller values) in the integrated lumi. Online people seems to stay cool and just inform about the error, instead of trying to fix the bug. Is anybody looking into the problem??? P.S. Do not worry - all will be OK but not so soon (a.f.). P.P.S. YOU should worry - I was already warned by the Run coordinator about this "LUMI feature". If you don't want that at each H1 meeting, or pinboard this bug would be mentioned again and again. (S.L.) 22.06.1994 ===== dice2 ======== H1KFOM === Relation CoefficientsSetB1 Due to yesterday mentioned conclusion about need to divide 2nd data om 3 subsamples today it was made attempt to obtain Relation Coefficients Set for 1st subsample of the 2nd sample (events from Runs 77804-78174). It were got 51927 ET&PD&nVC from these Runs and it were used for calibration 33966 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 1.099 1.136 1.092 1.108 1.140 1.187 1.128 1.069 1.246 1.129 2.395 0.968 1.001 1.193 1.164 0.906 1.047 0.960 0.978 0.971 0.982 1.037 1.040 1.032 1.024 1.053 1.031 1.034 1.041 1.113 1.001 1.022 1.032 1.072 0.990 1.142 0.979 1.123 0.981 0.945 0.962 1.011 1.055 1.077 0.856 0.939 0.949 1.096 0.000 ==> Relation Coeff.Set for PD 1.680 1.015 0.996 1.277 0.935 1.005 1.003 0.970 0.968 1.081 0.968 1.006 0.991 0.986 0.998 0.999 0.957 0.977 0.962 0.969 1.387 0.876 0.967 0.937 0.932 ==> Sig. at Relation Coeff.Set for ET 0.000 0.001 0.001 0.000 0.004 0.002 0.000 0.000 0.085 0.008 0.035 0.011 0.021 0.006 0.013 0.033 0.011 0.021 0.014 0.019 0.029 0.012 0.019 0.016 0.011 0.019 0.016 0.022 0.050 0.020 0.017 0.033 0.018 0.021 0.016 0.015 0.041 0.035 0.025 0.028 0.012 0.018 0.002 0.059 0.019 0.016 0.013 0.007 0.000 ==> Sig. at Relation Coeff.Set for PD 0.011 0.019 0.015 0.010 0.003 0.012 0.015 0.019 0.012 0.008 0.018 0.038 0.013 0.024 0.010 0.015 0.022 0.016 0.012 0.009 0.058 0.023 0.015 0.018 0.000 ==> Ent. at Relation Coeff.Set for ET 1 8 2 2 11 15 2 3 13 13 25 7 3 10 2238 492 514 271 288 237 82 9309 14965 11426 9046 7544 6284 2836 1878 2108 1206 1624 1647 1561 1040 37 36 93 113 110 66 25 3 13 15 47 33 7 0 ==> Ent. at Relation Coeff.Set for PD 37 24 37 53 2 309 3173 7570 4144 425 1851 13299 26863 16900 2454 342 2876 6474 4175 338 20 21 34 17 1 As You can see all is OK with sigma values for each from 'hot' cells Relation Coeff. histos - not so large as earlier. Runs 77804- 78174 (ET&PD&nVC-sample - near 52K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.46 0.85 27.46 0.82 27.48 0.81 As You can see all is OK with sigma values at ETrec+PDrec spectra. (almost 10% less then earlier). It were used as start values of CC for Photoproduction branch ones which were produced after 3rd step of previous 17 May 94 calibration and CCvcs as 2.954 (from H1KFOM's 20.06.94 message at LLC). 22.06.1994 ===== dice2 ======== H1KFOM === new set of PDREC-spectra.. Today it was produced 100th ntuple for S91=1 events from earlier mentioned 1st subsample of the 2nd sample (Runs 77804-78174): H1KFOM.YLOOKQ4.R77804 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.R77804 FAST05 3010200E 00000 DASD Asking to L.N.Shtarkov to make Photon Arm Energy Spectra Fitting of high mentioned 70th histo (ep-option). After this it will be possible to define Global EnergyShifts Constants and CCvcs value. 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.R77804 FAST16 3010200E 00000 DASD H1KFOM.YLOOKQ3.R77804 FAST18 3010200E 00000 DASD 22/6/94 ====================== Shtarkov === Lumi RUN# 442 Start lumi run442 date: 22/6/94 Collision time: 13:55:23 - 18:08:07 Currents (mkA): Ie= 20800.00, Ip= 40700.00 Peak luminosity: 1305.034 mb-1 s-1 Peak spec.lumi : 305.036857 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: 12640.793448 mkb-1 H1 Run total lumi: 10159.8122 mkb-1 <--- ? H1 data taken lumi: 8355.7941 mkb-1 <--- ? H1 Runs: 79897 - 79917 HERA - physics: 11721.749272 mkb-1 H1Run - physics: 9387.999396 mkb-1 <--- ? H1data - physics: 7665.447748 mkb-1 <--- ? H1 Runs: 79905 - 79917 Tot curr/rate factor: 0.83% C/R F H1Run gated: 0.81% Rand.C.F: 1.15% RCF Run gated: 1.11% Relative ET trigg accept.: 0.3539 PS: Again,there was drop of Int.Lumi at 15.00 (Yu.S) 22/6/94 ====================== Shtarkov === Lumi RUN# 443 Start lumi run443 date: 22/6/94 Collision time: 19:33:22 - 20:12:03 Currents (mkA): Ie= 24450.00, Ip= 39001.00 Peak luminosity: 1451.816 mb-1 s-1 Peak spec.lumi : 299.622803 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: 2736.011405 mkb-1 H1 Run total lumi: 2485.947984 mkb-1 H1 data taken lumi: 2154.211162 mkb-1 H1 Runs: 79929 - 79932 HERA - physics: 2273.746111 mkb-1 H1Run - physics: 1591.949735 mkb-1 H1data - physics: 1279.996735 mkb-1 H1 Runs: 79929 - 79932 Tot curr/rate factor: 1.78% C/R F H1Run gated: 1.81% Rand.C.F: 2.73% RCF Run gated: 2.72% Relative ET trigg accept.: 0.3419 23.06.1994 ==================== H1KFOM === Speed up online........... This is part of Minutes of last Trigger Meeting on which I was invited due to discussed problem with Luminosity branch FER-problem: "..... Eckhard then turned back to the detailed dead time analysis of the above run. The FrontEndReady time distributions still show tails, most pronounced in the fowrward tracker branch, where 10 ms occur on the percent level. Two deadtime distributions were shown: the first for the 90% of events where the readout time is limited by the front end. It shows a spike at about 2.5 ms and very small tails however extending up to 100 ms, mainly due to the lumi branch. The second was for the other 10%, where the readout is limited by the amount of buffers available. In this case, by design the central trigger having the smallest number of buffers allocated holds the readout. The distribution shows a broad maximum around 10ms, the bulk extends to 40, the tails to 100 ms. This clearly shows that the current buffer depth of 10 is not sufficient to cope with the fluctuations in trigger rate and event size. It is not easy to attribute this bottleneck to a specific branch; the one giving the last FER may be responsible: in most cases this was the lumi branch agin. Here an improvement can be reached via the installation of a second readout processor board. ...." As You remember me and Egor wrote at LLC some explanations for mentioned at this piece of Trigger Meeting Minutes-see messages at LLC: 02.06.1994 H1Lumi's FER, 07.06.1994 H1Lumi's Dead Time...... 09.06.1994 Speed up online 14.06.1994 Speed up online (E.Elsen) 14.06.1994 speed up explain... 16.06.1994 Speed up online (S.Burov)int.message to H1KSHE,F11LEV,H1KSOL As seems it is needed to make some new remarks again: 1) About the next 'piece of part': First dead time distribution (readout time is limited by the frontend): ".. shows a spike at about 2.5 ms and very small tails however extending up to 100 ms, mainly due to the lumi branch.... " - Luminosity branch is issuing FER at L2Keep.f subroutine after 1.6 msec at most cases; - as I wrote earlier 10 msec interval must be maximal FER time from Luminosity branch (for enough rare overflow situations at L2Keep.f subroutine). Overflow situations mean absence of free H1Lumi internal buffer (we have 8 internal buffers now) - 10 msec is maximal LUMI FER time must be very rare (only when there is coincidence of two factors: IlevelA.f started 10 msec period of full processing of the next busy buffer and at this time it was appeared overflow situation at L2Keep.f-routine; - at most situations FER from IlevelA.f must be issued in time between 1.6 and 10 msec; - as seems this "very small tails however extending up to 100 ms,mainly due to the lumi branch" can be explained with the next versions: a) there is some bug (up to now not found) at Lumi internal buffer monitoring algorithm; b) there is some problems with interface to VMEtaxi-protocol: - this version exists due to 'non-zero' counters "Try again"- situations after CALL MEBREQ and CALL MEBREADY. - if 'Try Again" situation is correlated with overflow situation at L2Keep.f (it means delayed FER from IlevelA.f -subroutine) in principle it is possible to wait that FER from Luminosity branch will be issued after 10 msec interval. c) may be rare (once per 10 sec.) KEEP-banks (LRTL,LUMM,LREC,LRPC) are responsible for this tail? d) may be it is needed to test another Egor's constant for Overflow situation labeling at L2Keep.f routine ( now Egor had installed overvlow situation if 7th buffer is filled with ReadOut procedure at L2Keep-routine - may be we must return to situation 'if 8th buffer is filled'?). As seems tail must became less (due to more rare overflow). e) may be (for any case) we can try to change number of buffers which Luminosity branch requests at VME-taxi protocols for data trans- mission and to make its quantity equal to H1Lumi internal buffers; (now we have 20 Bill's buffers and 8 Internal buffers); f) may be (for some clearity) we can try some tests with H1CDAQ with short H1Lumi Data Flow from Luminosity branch and to see up to 100 msec tail behaivour (including KEEP-banks removing). 2) About incrementing of Lumi Internal buffers(today Elsen's proposal) Eckhard Elsen proposes to increment number of H1Lumi internal buffers and to look for what happens. Egor explained earlier and I agreed with his opinion that this simple and logical decision is not right due to simple evidence that background area at FIC#1-processor almost dead when L2Keep-interrupts rate is more then 45-50 Hz and absolutely dead with L2Keep-rate a little more then 100 Hz. It means that all processor power is distributed between ForeGround routines (L2Keep.f, L3Keep.f, L3Reject.f and IlevelA.f(lowest priori- ty). Incremention of Lumi internal buffer is not enough simple procedure due to each from 8 internal buffers has very long chain of additional buffers which are used at IlevelA.f routine (for Linearization, Pedestal Substraction,FADC counts making, BOS-bank creation etc.). It would be good if all this long chain of buffers will be disposed at FIC's Local DPM (memory access time is less then access through VME in/from additional DPM-modules). All local DPM memory at FIC#1 now is busy (lowest part with absolute address page, highest part with code). It is need to remove some part of code or remove some useful features of OnLine-program for finding of additional place for additional H1Lumi Internal buffers. 3) About future upgrade of Lumi readout: "..... Here an improvement can be reached via the installation of a second readout processor board..." Today after phone talking with Egor I asked of Sergey Burov to order for Luminosity branch additional FIC8231. Upgrade will be made at future shutdown. Now it is possible to start algorithmes development and program units making. Decision about future upgrade with more powerful microprocessor will be made later. As seems it is needed special stend for testing, studying, development etc. 23.06.1994 ==================== H01GOG === Selection news............ Sorry, it was a mistake in my message at 20.06.1994. I have repeated the selection of the events for ET&PD&VC and ET&PD&nVC triggers from the cartridge: H01GOG.H1LUMI.C1131185.A00 K13413 78048081 00001 ACS-E-C The following data sets were produced: ET&PD&VC H01GOG.ETPDVC.C1131185.A00 (11782 events) K31871 78048081 00001 ACS-E-C ET&PD&nVC H01GOG.ETPDNVC.C1131185.A00 (16415 events) K31959 78048081 00001 ACS-E-C * * * * * * * * * * * * * * I have selected the events of 24th class from MONITRIG cartridges: HERA03.H1POT2.MONITRIG.C9401186 ............................... HERA03.H1POT2.MONITRIG.C9401233 The following data sets were prodused: H01GOG.H1LUMI.C1186211.A00 K18769 78048081 00001 ACS-E-C H01GOG.H1LUMI.C1212233.A00 K10594 78048081 00001 ACS-E-C H01GOG.H1LUMI.C1212233.A01 K10600 78048081 00001 ACS-E-C Tomorrow, when the last cartridge ....C9401242 with run 79930 will appear in a catalog ( as Uwe Kruener-Marquis promised just now), I'll finish the events selection of 24th class from MONITRIG cartridges. It will be done automaticaly afterwards. Very good! 23.06.1994 20:20 ============== H01LNS === new PDFIT for R77804 Q2... PDFITs have been made for the request of A.F.; only "70", only "ep". Star(*) the line: LIST 'H01LNS.JPDFIT.BLOOKQ2.R77804.EP' Be carefull: Not take the lines with "infER" == infinite ERROR ! I would prefer the variants: (statisticaly, they are the same) R lrun fg emin emax np eX e fitFLchi2 prob% E_shift%%+- B_res%%+- Entr Evnt R77804 70 10.0 35.0 50 ep 0 fitOK 40 25.6% (-0.4+-0.6)% (12+- 3)% 3120 4586 R77804 70 12.0 35.0 46 ep 0 fitOK 31 41.9% (-0.3+-0.6)% (12+- 3)% 2559 4586 R77804 70 16.0 35.0 38 ep 0 fitOK 20 59.9% (-0.1+-0.6)% (11+- 3)% 1834 4586 R77804 70 18.0 35.0 34 ep 0 fitOK 17 55.3% ( 0.0+-0.7)% (11+- 3)% 1525 4586 23.06.1994 ===== #FIC1 ======== H1KFOM === H1LumiOnLineRelease ...... It was made new release of H1LumiOnLineProgram. Creation data/time are 23.06.94 20:07. It were made only 2 changings: 1) it was made update of main-program with hope that problem of decrementing of H1 Gated and H1 Data Taken Integrated Lumi values at boundaries of H1Lumi Runs (as it was fixed 7-8 times at H1Data Taking 94) will be removed; 2) it were changed L2Keep.f and IlevelA.f subroutines for labeling overflow situation only if 8th buffer is filled. It is possible to wait that percent of 'tailed' events (more then 1.6 msec FER) will be decremented. Release was tested at H1Runs 79992-79994 with all branches and with Random trigger different rates (50 Hz,1kHz and 10kHz) with little HERA p-beam. 23/6/94 ======================= rick === Lumi RUN# 444 ............ Start lumi run444 date: 23/6/94 Collision time: 22:37:50 - 22:44:29 Currents (mkA): Ie= 27976.00, Ip= 20700.00 Peak luminosity: 1107.174 mb-1 s-1 Peak spec.lumi : 367.192296 mb-1 s-1 mA-2 Number of collided b.: 151 Number of e-filled b.: 168 Number of p-filled b.: 166 Number of e-pilot b.: 17 Number of p-pilot b.: 15 HERA total lumi: 433.179302 mkb-1 H1 Run total lumi: 433.179135 mkb-1 H1 data taken lumi: 426.565464 mkb-1 H1 Runs: 80007 - 80007 HERA - physics: 78.009095 mkb-1 H1Run - physics: 11.409464 mkb-1 H1data - physics: 11.245669 mkb-1 H1 Runs: 80007 - 80007 Tot curr/rate factor: 1.06% C/R F H1Run gated: 1.06% Rand.C.F: 5.56% RCF Run gated: 5.56% Relative ET trigg accept.: Not calc. 24/6/94 ======================= rick === Lumi RUN# 445 ............ Start lumi run445 date: 23/6/94 Collision time: 22:46:20 - 4:17:39 Currents (mkA): Ie= 25874.00, Ip= 20700.00 Peak luminosity: 1470.902 mb-1 s-1 Peak spec.lumi : 504.761408 mb-1 s-1 mA-2 Number of collided b.: 151 Number of e-filled b.: 168 Number of p-filled b.: 166 Number of e-pilot b.: 17 Number of p-pilot b.: 15 HERA total lumi: 8638.971747 mkb-1 H1 Run total lumi: 3282.561891 mkb-1 <--- H1 data taken lumi: 2793.345481 mkb-1 <--- H1 Runs: 80008 - 80014 HERA - physics: 8577.243764 mkb-1 H1Run - physics: 2886.314018 mkb-1 <--- H1data - physics: 2441.593835 mkb-1 <--- H1 Runs: 80010 - 80014 Tot curr/rate factor: 0.23% C/R F H1Run gated: 0.22% Rand.C.F: 1.59% RCF Run gated: 1.51% Relative ET trigg accept.: 0.3430 PS : Integrated H1 Lumi dropped down at 2.50 by abou 5nb-1 during H1 RUN #80014.(Yu.S) PS 1: As seems this is another situation only firstly observed at our system. All Usik's history pictures show at 02:50 'negative' spikes at all variables connected with Rate Calculations. Situation is fixed and under investigation for possible protection from similar situation at future . (a.f.). 24/6/94 ======================= rick === Lumi RUN# 446 ............ Start lumi run446 date: 24/6/94 Collision time: 5:18:52 - 8:33:36 Currents (mkA): Ie= 20937.00, Ip= 19900.00 Peak luminosity: 802.456 mb-1 s-1 Peak spec.lumi : 493.484419 mb-1 s-1 mA-2 Number of collided b.: 151 Number of e-filled b.: 168 Number of p-filled b.: 166 Number of e-pilot b.: 17 Number of p-pilot b.: 15 HERA total lumi: 3690.664517 mkb-1 H1 Run total lumi: 3137.040294 mkb-1 H1 data taken lumi: 2899.359831 mkb-1 H1 Runs: 80016 - 80022 HERA - physics: 3017.718677 mkb-1 H1Run - physics: 2225.173268 mkb-1 H1data - physics: 2027.039363 mkb-1 H1 Runs: 80019 - 80022 Tot curr/rate factor: 0.28% C/R F H1Run gated: 0.3% Rand.C.F: 1.04% RCF Run gated: 1.01% Relative ET trigg accept.: 0.3521 24/6/94 ======================= ?????? === Lumi RUN# 447 ............ Start lumi run447 date: 24/6/94 Collision time: 10:25:?? - 15:45:?? Currents (mkA): Ie= 24000.00, Ip= 19000.00 Peak luminosity: 1080.000 mb-1 s-1 Peak spec.lumi : 452.000000 mb-1 s-1 mA-2 Number of collided b.: 151 Number of e-filled b.: 168 Number of p-filled b.: 166 Number of e-pilot b.: 17 Number of p-pilot b.: 15 HERA total lumi: 9400.000000 mkb-1 H1 Run total lumi: 8300.000000 mkb-1 H1 data taken lumi: 7400.000000 mkb-1 H1 Runs: 80041 - 80063 HERA - physics: ????.?????? mkb-1 H1Run - physics: ????.?????? mkb-1 H1data - physics: ????.?????? mkb-1 H1 Runs: ????? - 80063 Tot curr/rate factor: ?.??% C/R F H1Run gated: ?.?% Rand.C.F: ?.??% RCF Run gated: ?.??% Relative ET trigg accept.: 0.???? P.S. T_MonitorNC was crashed with Lruns file corruption - due to this we cannot to make standard manipulations with moving of H1Lumi RunSummary from H1Lumi2 MacII into DESY IBM. For any case we tryed to estimate all possible digits from Usik's pictures and to fill all possible digits at RunSummary (Yu.S.,a.f) P.S.1: At 15:05 it was fixed 'drop' Integral Lumi values on values of collected Integral Lumi at previous Run (it means that new release of H1LumiProgramFIC#1 cannot strugle with 'drop'-situations with Integral Lumi values. As seems it is needed to move call Integral Lumi subroutine from FIC#1 environment into FIC#2 environment. 25/6/94 ====================== Shtarkov === Lumi RUN# 448 ........... Start lumi run448 date: 25/6/94 Collision time: 0:12:46 - 0:37:39 Currents (mkA): Ie= 23292.00, Ip= 39101.00 Peak luminosity: 2178.209 mb-1 s-1 Peak spec.lumi : 457.420313 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: 2495.733645 mkb-1 H1 Run total lumi: 2355.507432 mkb-1 H1 data taken lumi: 1944.520925 mkb-1 H1 Runs: 80117 - 80120 HERA - physics: 1959.87632 mkb-1 H1Run - physics: 425.718732 mkb-1 H1data - physics: 227.578125 mkb-1 H1 Runs: -1 - 80120 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 3.7% RCF Run gated: 3.71% Relative ET trigg accept.: 0.3476 25.06.1994 ===== dice2 ======== H1KFOM === Relation CoefficientsSetB2 Due to at 21.06.94 mentioned conclusion about need to divide 2nd data om 3 subsamples today it was made attempt to obtain Relation Coefficients Set for 2nd subsample of the 2nd sample (events from Runs 78381-78784). It were got 26907 ET&PD&nVC from these Runs and it were used for calibration 18156 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 1.102 1.138 1.087 1.135 1.148 1.181 1.128 1.070 1.397 1.156 2.424 0.941 1.028 1.187 1.193 0.939 1.055 0.963 1.014 0.881 0.998 1.033 1.039 1.024 1.020 1.048 1.040 1.012 0.989 1.068 1.022 1.021 0.996 0.981 1.033 1.122 0.896 1.068 0.991 0.961 0.923 1.050 0.000 1.015 0.874 0.904 0.984 1.084 0.000 ==> Relation Coeff.Set for PD 1.699 0.931 1.039 1.288 0.000 0.998 0.955 0.981 1.011 1.062 0.952 1.013 0.992 0.987 1.004 0.972 0.942 0.981 0.968 0.956 1.455 0.929 0.960 0.958 0.930 ==> Sig. at Relation Coeff.Set for ET 0.000 0.005 0.001 0.021 0.002 0.002 0.000 0.000 0.007 0.021 0.010 0.008 0.008 0.003 0.014 0.016 0.008 0.025 0.028 0.011 0.022 0.013 0.021 0.019 0.013 0.022 0.021 0.011 0.027 0.007 0.011 0.009 0.009 0.018 0.012 0.000 0.038 0.020 0.018 0.015 0.001 0.013 0.000 0.036 0.013 0.018 0.036 0.003 0.000 ==> Sig. at Relation Coeff.Set for PD 0.003 0.014 0.013 0.002 0.000 0.012 0.017 0.017 0.011 0.004 0.013 0.051 0.022 0.025 0.010 0.013 0.026 0.022 0.015 0.010 0.026 0.008 0.010 0.023 0.000 ==> Ent. at Relation Coeff.Set for ET 4 5 2 3 16 13 4 5 10 2 9 4 4 5 1164 410 345 180 258 184 89 5071 8009 6059 4797 4015 3458 1517 842 1107 678 741 593 479 491 8 11 45 59 43 24 12 0 5 10 23 17 5 0 ==> Ent. at Relation Coeff.Set for PD 16 11 16 21 0 136 1099 2091 916 83 1031 7489 14182 8537 1242 255 2602 6055 4107 460 11 4 31 22 3 As You can see all is OK with sigma values for each from 'hot' cells Relation Coeff. histos - not so large as earlier. Runs 78381- 78784 (ET&PD&nVC-sample - near 26K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.44 0.86 27.47 0.84 27.47 0.84 As You can see all is OK with sigma values at ETrec+PDrec spectra. (almost 4% less then earlier). Runs 78381- 78784 (ET&PD&VC-sample - near 22K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.48 1.15 27.47 1.11 It were used as start values of CC for Photoproduction branch ones which were produced after 3rd step of calibration with 1st subsample of 2nd sample (Runs77804-78174) and CCvcs as 2.954. (from H1KFOM's 22.06.94 message at LLC). 25.06.1994 ===== dice2 ======== H1KFOM === new set of PDREC-spectra.. Today it were produced 100th ntuple for S91=1 events from earlier mentioned 2nd subsample of the 2nd sample (Runs 78381-78784): H1KFOM.YLOOKQ4.R78381 FAST04 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.R78381 FAST08 3010200E 00000 DASD Asking to L.N.Shtarkov to make Photon Arm Energy Spectra Fitting of high mentioned 70th histo (ep-option). After this it will be possible to define Global EnergyShifts Constants and CCvcs value. 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.R78381 FAST09 3010200E 00000 DASD H1KFOM.YLOOKQ3.R78381 FAST01 3010200E 00000 DASD 25.06.1994 ===== dice2 ======== H1KFOM === Selected H1Lumi Monitrig.. It were selected events with (s86=1 only),with (s93=1 only),with (s91=1 only), with ET&PD&VC=1 and with ET&PD&nVC from last produced by Nelly data sets with H1Lumi MONITRIG events: H01GOG.H1LUMI.C1131185.A00 K13413 78048081 00001 ACS-E-C H01GOG.H1LUMI.C1186211.A00 K18769 78048081 00001 ACS-E-C H01GOG.H1LUMI.C1212233.A00 K10594 78048081 00001 ACS-E-C H01GOG.H1LUMI.C1212233.A01 K10600 78048081 00001 ACS-E-C It were produced at dice2-environment next data sets and moved into IBM cartridges with stageout procedures: H1KFOM.ETPDNVC.M1131233.C00 K30295 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M1131233.C00 K30552 78048081 00001 ACS-E-C H1KFOM.S86.M1131233.C00 K31618 78048081 00001 ACS-E-C H1KFOM.S91.M1131233.C00 K18989 78048081 00001 ACS-E-C H1KFOM.S93.M1131233.C00 K31288 78048081 00001 ACS-E-C 1) S86=1 only 58713 events from total 299226 ( 87.4 MBytes) 2) S93=1 only 72753 events from total 299226 (108.3 MBytes) 3) S91=1 only 59135 events from total 299226 ( 88.2 MBytes) 4) ET&PD&VC 76187 events from total 299226 (114.2 MBytes) 5) ET&PD&nVC 49633 events from total 299226 ( 73.1 MBytes) Selection procedure got next SGI CPU times for different selections: 1) S86=1 only 437 sec. 2) S93=1 only 453 sec. 3) S91=1 only 446 sec. 4) ET&PD&VC 467 sec. 5) ET&PD&nVC 425 sec. At all high mentioned data sets H1Lumi dedicated Runs which were recorded by V.Andreev are presented (Runs 79494,79497 and 79499). At Nelly's data sets the next quantities of H1Lumi monitrig events from Vova's H1Runs are presented: Run 79494 - 27870 events Run 79497 - 40359 events Run 79499 -144636 events. All data from this H1Runs were recorded with only HERA e-beam presence at HERA and with e-beam synchronisation and with another timing. Due to equal prescale gaps for s92 and s94 (see Vova's message from 18 June 1994 at LLC) s92-trigger bit did not produce additional statistics for ET&PD&nVC-events - so we have non-standard situation with quantities ratio N(ET&PD&nVC)/N(ET&PD&VC). 25.06.1994 ===== dice2 ======== H1KFOM === Bad H1Runs for calibration During attempt of first step of calibtration with ET&PD&nVC-events from H1Runs 78785-79666 it was found that there are large 'jumps' at Relation Coefficient for p11 (from 1.03 to 1.7 and from 1.03 to 2.1) for H1Runs 78814 and 78874-79047. It was decided to skip events from these Runs for calibration. 25.06.1994 ===== dice2 ======== H1KFOM === Test of LUMIMON-datasets.. Today I found first data sets with H1Lumi MONITRIG-events which were produced with standard job prepared by S.Levonyan at dice1- -environment: HERA03.H01.LUMIMON.C9400001 B02858 78048081 00001 ACS-E-C HERA03.H01.LUMIMON.C9400002 B13067 78048081 00001 ACS-E-C It were selected events with (s86=1 only),with (s93=1 only),with (s91=1 only), with ET&PD&VC=1 and with ET&PD&nVC from these data sets: 1) S86=1 only 18163 events from total 130114 ( 27.6 MBytes) 2) S93=1 only 19199 events from total 130114 ( 27.7 MBytes) 3) S91=1 only 9523 events from total 130114 ( 14.3 MBytes) 4) ET&PD&VC 15436 events from total 130114 ( 25.6 MBytes) 5) ET&PD&nVC 15644 events from total 130114 ( 26.0 MBytes) At these data sets data from Runs 79913 up to 80058 are presented (not from 79930 as S.Levonyan promised but a little earlier). Selected data were written into the next data sets at DESY IBM: H1KFOM.ETPDNVC.M12.C00 K19475 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M12.C00 K19482 78048081 00001 ACS-E-C H1KFOM.S91.M12.C00 K19501 78048081 00001 ACS-E-C H1KFOM.S93.M12.C00 K18403 78048081 00001 ACS-E-C H1KFOM.S86.M12.C00 K18477 78048081 00001 ACS-E-C 26.06.1994 08:40 ============== H01LNS === === PDFIT for Q2.R78381... PDFITs have been made for the request of A.F.; only "70", only "ep". Star(*) the line: LIST 'H01LNS.JPDFIT.BLOOKQ2.R78381.EP' Be carefull: Not take the lines with "infER" == infinite ERROR ! I would prefer the variants: (statisticaly, they are the same) PD_FIT STARTED 26/06/94 08.36.25 l_text1,4: nt(100)(pdrec) s91.eq.1.and.pdrec.lt.999.and.vcdep.lt.0.2 R lrun fg emin emax np eX e fitFLchi2 prob% E_shift%%+- B_res%%+- Entr Evnt R78381 70 10.0 35.0 50 ep 0 fitOK 31 56.2% (-1.1+-1.0)% (11+- 5)% 1358 1928 R78381 70 12.0 35.0 46 ep 0 fitOK 29 41.6% (-0.9+-0.9)% (10+- 5)% 1168 1928 R78381 70 14.0 35.0 42 ep 0 fitOK 27 31.7% (-0.5+-0.9)% ( 7+- 5)% 986 1928 26/6/94 ======================= h.jung === Lumi RUN# 449 ....... Start lumi run449 date: 26/6/94 Collision time: 11:03:27 - 11:30:19 Currents (mkA): Ie= 21723.00, Ip= 31900.00 Peak luminosity: 128.933 mb-1 s-1 Peak spec.lumi : 38.561927 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: 238.570726 mkb-1 H1 Run total lumi: 277.002452 mkb-1 H1 data taken lumi: 254.50372 mkb-1 H1 Runs: 80217 - 80218 HERA - physics: 14.58077 mkb-1 H1Run - physics: 1.182826 mkb-1 H1data - physics: 0.948143 mkb-1 H1 Runs: 80218 - 80218 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 3.73% RCF Run gated: 3.74% Relative ET trigg accept.: 0.3031 26/6/94 ======================= h.jung === Lumi RUN# 450 ....... Start lumi run450 date: 26/6/94 Collision time: 11:37:08 - 13:43:50 Currents (mkA): Ie= 18415.00, Ip= 31900.00 Peak luminosity: 1369.389 mb-1 s-1 Peak spec.lumi : 507.765794 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: 5990.226038 mkb-1 H1 Run total lumi: 5386.7251 mkb-1 H1 data taken lumi: 4328.0791 mkb-1 H1 Runs: 80219 - 80224 HERA - physics: 4970.169696 mkb-1 H1Run - physics: 4591.855834 mkb-1 H1data - physics: 3741.786113 mkb-1 H1 Runs: 80222 - 80224 Tot curr/rate factor: 0.16% C/R F H1Run gated: 0.2% Rand.C.F: 1.2% RCF Run gated: 1.18% Relative ET trigg accept.: 0.3705 26.06.1994 ==================== H1KSOL === PS to the R#449-450... 1. Both Lumi Runs were taken at the same e-fill,I did not understand explanations of shifts crew why they did it. Integrated Lumi was reset after Run#449. 2.At the beginning of the LRun#449 HERA did not get our monitor updated,this problem was solved by Ph.Biddulph in Hera CR. 3.But right after this problem was solved another came: Both Usik's applications (in H1CR and in HERACR) showed infinite values of Lumi and Specific Lumi,so Hera did not tune Lumi for H1 though they could do it with the Lumi Trigger Rates but they said to shift crew that they dont know which curve that should watch. I was called in about 40 min after beginning of this (too late) and the problems turned out to be that the value of sigma for bremmstralung in Usik's application was set to 0 (!?!). Due to this H1 loose about 40 min of Lumi (when I came I hint to G.Lopez that Hera can optimize Lumi by Lumi Rates and they did it). 4.I discovered that responce of VETOs increased by about 20% in these LRuns. Earlier the tail of VETOs signal was spread up to 20 GeV,now it is at about 25 GeV,the tail of PD responce which include VETOs increased too.There were no complains from shift crew abot L4 histogramm but I suspect that they changed in the same manner. 26.06.1994 ===== dice2 ======== H1KFOM === Relation CoefficientsSetB3 Due to at 21.06.94 mentioned conclusion about need to divide 2nd data om 3 subsamples today it was made attempt to obtain Relation Coefficients Set for 3rd subsample of the 2nd sample (events from Runs 78785-79666). It were got 34350 ET&PD&nVC from these Runs and it were used for calibration 21742 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for PD 1.717 0.969 1.011 1.303 0.000 0.961 1.005 1.008 0.969 1.043 0.965 1.020 0.999 0.989 1.067 1.028 0.955 0.981 0.991 0.976 1.491 0.938 1.037 0.987 0.929 ==> Sig. at Relation Coeff.Set for ET 0.000 0.001 0.000 0.000 0.001 0.003 0.005 0.024 0.049 0.005 0.025 0.023 0.032 0.017 0.039 0.014 0.027 0.021 0.065 0.086 0.047 0.014 0.019 0.022 0.013 0.027 0.022 0.014 0.019 0.025 0.018 0.016 0.019 0.021 0.042 0.006 0.027 0.012 0.020 0.012 0.009 0.018 0.000 0.016 0.017 0.014 0.038 0.000 0.000 ==> Sig. at Relation Coeff.Set for PD 0.019 0.020 0.018 0.006 0.000 0.020 0.023 0.017 0.014 0.023 0.020 0.021 0.019 0.032 0.021 0.022 0.035 0.024 0.017 0.029 0.053 0.020 0.013 0.007 0.000 ==> Ent. at Relation Coeff.Set for ET 1 6 0 3 5 9 3 6 7 6 16 6 3 3 1321 449 444 284 385 101 100 6218 9775 7280 5839 4861 4054 1773 875 810 809 748 756 488 604 18 13 27 40 34 19 8 0 10 9 14 15 1 0 ==> Ent. at Relation Coeff.Set for PD 37 12 16 11 0 376 2410 3371 880 67 2635 12352 16529 6792 701 724 4407 6283 2790 223 35 29 47 14 2 As You can see all is OK with sigma values for each from 'hot' cells Relation Coeff. histos - not so large as earlier. Runs 78785- 79666 (ET&PD&nVC-sample - near 39K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.49 0.89 27.50 0.86 27.52 0.86 As You can see all is OK with sigma values at ETrec+PDrec spectra. (almost 2% less then earlier). Runs 78785- 79666 (ET&PD&VC-sample - near 27K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.38 1.19 27.41 1.16 It were used as start values of CC for Photoproduction branch ones which were produced after 3rd step of calibration with 2nd subsample of 2nd sample (Runs78381-78784) and CCvcs as 2.954. (from H1KFOM's 25.06.94 message at LLC). 26.06.1994 ===== dice2 ======== H1KFOM === new set of PDREC-spectra.. Today it were produced 100th ntuple for S91=1 events from earlier mentioned 3rd subsample of the 2nd sample (Runs 78785-79666): H1KFOM.YLOOKQ4.R78785 FAST18 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.R78785 FAST08 3010200E 00000 DASD Asking to L.N.Shtarkov to make Photon Arm Energy Spectra Fitting of high mentioned 70th histo (ep-option). After this it will be possible to define Global EnergyShifts Constants and CCvcs value. 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.R78785 FAST18 3010200E 00000 DASD H1KFOM.YLOOKQ3.R78785 FAST02 3010200E 00000 DASD P.S. All 100th ntuples include data from H1Lumi Dedicated Runs: 79494, 79497 and 79499 which were recorded with HERA e-beam only by V.Andreev.70th histo does not include high mentioned data samples. it was made additional cut for filling of 70 histo - rr. 26/6/94 ======================= h.jung === Lumi RUN# 451 Start lumi run451 date: 26/6/94 Collision time: 16:43:42 - 17:00:06 Currents (mkA): Ie= 23417.00, Ip= 31500.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: 829.405487 mkb-1 H1 Run total lumi: 651.7863 mkb-1 H1 data taken lumi: 613.3085 mkb-1 H1 Runs: 80230 - 80230 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 80230 - 80230 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 5.55% RCF Run gated: 6.3% Relative ET trigg accept.: Not calc. 26/6/94 ======================= === Lumi RUN# 452 Start lumi run452 date: 26/6/94 Collision time: 18:08:39 - 18:16:52 Currents (mkA): Ie= 22721.00, Ip= 31301.00 Peak luminosity: 1547.417 mb-1 s-1 Peak spec.lumi : 406.404864 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: 646.408264 mkb-1 H1 Run total lumi: 556.7582 mkb-1 H1 data taken lumi: 520.2163 mkb-1 H1 Runs: 80232 - 80232 HERA - physics: 395.641988 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 80232 - 80232 Tot curr/rate factor: 0.79% C/R F H1Run gated: 0.78% Rand.C.F: 4.06% RCF Run gated: 4.12% Relative ET trigg accept.: Not calc. 27/6/94 ================== swanenberger === Lumi RUN# 453 Start lumi run453 date: 26/6/94 Collision time: 19:07:33 - 1:10:53 Currents (mkA): Ie= 21106.00, Ip= 31100.00 Peak luminosity: 1523.275 mb-1 s-1 Peak spec.lumi : 445.037818 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: 16251.859647 mkb-1 H1 Run total lumi: 12321.6402 mkb-1 H1 data taken lumi: 9341.6337 mkb-1 H1 Runs: 80243 - 80262 HERA - physics: 15566.120858 mkb-1 H1Run - physics: 10448.773201 mkb-1 H1data - physics: 7649.055259 mkb-1 H1 Runs: 80248 - 80262 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 1.56% RCF Run gated: 1.45% Relative ET trigg accept.: 0.3360 27/6/94 ====================== nicholls === Lumi RUN# 454 Start lumi run454 date: 27/6/94 Collision time: 2:33:07 - 3:31:41 Currents (mkA): Ie= 20615.00, Ip= 30000.00 Peak luminosity: 962.11 mb-1 s-1 Peak spec.lumi : 329.675112 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: 2935.878672 mkb-1 H1 Run total lumi: 2629.2766 mkb-1 H1 data taken lumi: 2091.6985 mkb-1 H1 Runs: 80262 - 80267 HERA - physics: 1719.776019 mkb-1 H1Run - physics: 1209.426321 mkb-1 H1data - physics: 752.3935 mkb-1 H1 Runs: 80265 - 80267 Tot curr/rate factor: 0.08% C/R F H1Run gated: 0.1% Rand.C.F: 1.87% RCF Run gated: 1.87% Relative ET trigg accept.: 0.3696 27.06.1994 10:50 ============== H01LNS === PDFIT for Q2.R78785....... PDFITs have been made for the request of A.F.; only "70", only "ep". Star(*) the line: LIST 'H01LNS.JPDFIT.BLOOKQ2.R78785.EP' Be carefull: Not take the lines with "infER" == infinite ERROR!(absent) I would prefer the variants: (statisticaly, they are the same) PD_FIT STARTED 27/06/94 10.36.49 l_text1,4: nt(100)(pdrec) pdrec.lt.999.and.vcdep.lt.0.2.and.rr R lrun fg emin emax np eX e fitFLchi2 prob% E_shift%%+- B_res%%+- Entr Evnt R78785 70 16.0 35.0 38 ep 0 fitOK 18 77.9% (-1.6+-1.2)% (28+- 8)% 1480 3457 R78785 70 18.0 35.0 34 ep 0 fitOK 17 61.5% (-1.5+-1.2)% (27+- 8)% 1153 3457 R78785 70 20.0 35.0 30 ep 0 fitOK 10 85.4% (-1.2+-1.3)% (26+- 8)% 925 3457 I would like to notice that "Resolution"=="B_res%%" is ~ 27 %. 27.06.1994 ==================== H1KFOM === Network Problems ......... Today near 11:50 when e-filling was finished and ramping was ready to be finished it was found that there are problems with connection between H1Lumi2 MacII and Hera Control Room MacII. Yura phoned to HERA people and recommended to reboot MacII but this manipulation did not help. Yura went from H1 Control Room to HERA Control Room for expertize making. At this time HERA people phoned to H1 Run Coordinator and reported that there are common network problem at HERA Control Room area and there are no any information about Lumi behaivour at ZEUS and H1 IP. Only H1Lumi black/white TV screen was used for Luminosity tuning and phone contacts between ZEUS Control Room and HERA people helped for Luminosity tuning at start of Lumi RUN# 455. I looked for at Usik's screen the Current Luminosity value near 2.0*10**30cm-2s-1 (H1 Run was stopped at this period and no information about this fact at off-line). Now Luminosity Run is proclaimed and Lumi RUN# 455 in progress now. 27.06.1994 ==================== H1KSOL === ET threshold.............. Sorry for late but ET threshold (HW) was changed before Lumi Run #451, due to the fact that it became a bit higher than nesessary. It was 5.25 GeV from Run451 on 5.00 GeV 27/6/94 ====================== G.Winter === Lumi RUN# 455 Start lumi run455 date: 27/6/94 Collision time: 11:40:42 - 15:45:46 Currents (mkA): Ie= 20893.00, Ip= 39200.00 Peak luminosity: 1362.322 mb-1 s-1 Peak spec.lumi : 326.481479 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: 17564.083029 mkb-1 H1 Run total lumi: 15440.847891 mkb-1 H1 data taken lumi: 12550.490425 mkb-1 H1 Runs: 80286 - 80296 HERA - physics: 17102.674141 mkb-1 H1Run - physics: 15068.819491 mkb-1 H1data - physics: 12245.558125 mkb-1 H1 Runs: 80289 - 80296 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 1.43% RCF Run gated: 1.36% Relative ET trigg accept.: 0.3365 P.S. ET&PD-background rate had only 10% quota of ET&PD -total rate. 27.06.1994 ==================== F11LEV === LPI meeting July,2 ....... In view of approaching: 1) visit of bosses and 2) my vacations (10/7-20/8 in Moscow) i propose to meet on Saturday, July 2 from 18 pm. till 19 pm. as usual in seminar room 3 (lab. 1b) in order to 1) briefly summarize present status 2) update task list and names attached to them 3) discuss an overall strategy for future More detailed discussion can be arranged for later if needed... 27/6/94 ========== L. Shtarkov, H. Jung === Lumi RUN# 456 Start lumi run456 date: 27/6/94 Collision time: 17:41:43 - 21:08:43 Currents (mkA): Ie= 24203.00, Ip= 38900.00 Peak luminosity: 1716.271 mb-1 s-1 Peak spec.lumi : 351.956176 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: 11622.165738 mkb-1 H1 Run total lumi: 9861.5878 mkb-1 H1 data taken lumi: 8091.496534 mkb-1 H1 Runs: -1 - 80310 HERA - physics: 11031.770531 mkb-1 H1Run - physics: 9861.5878 mkb-1 H1data - physics: 8091.496534 mkb-1 H1 Runs: 80301 - 80310 Tot curr/rate factor: 0.04% C/R F H1Run gated: Not calc.% Rand.C.F: 1.23% RCF Run gated: 1.02% Relative ET trigg accept.: 0.3624 27/6/94 ========== L. Shtarkov, H. Jung === Lumi RUN# 457 Start lumi run457 date: 27/6/94 Collision time: 22:05:41 - 22:08:37 Currents (mkA): Ie= 21696.00, Ip= 38500.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: 80.885 mkb-1 H1 Run total lumi: 80.885032 mkb-1 H1 data taken lumi: 79.776504 mkb-1 H1 Runs: 80311 - 80311 HERA - physics: -0.000032 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 80311 - 80311 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 4.19% RCF Run gated: 4.19% Relative ET trigg accept.: Not calc. 28/6/94 ============= C. Schwanenberger === Lumi RUN# 458 Start lumi run458 date: 28/6/94 Collision time: 3:37:59 - 5:14:04 Currents (mkA): Ie= 22829.00, Ip= 36101.00 Peak luminosity: 2067.092 mb-1 s-1 Peak spec.lumi : 498.47498 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: 7877.6311 mkb-1 H1 Run total lumi: 7203.9118 mkb-1 H1 data taken lumi: 3255.3974 mkb-1 H1 Runs: 80317 - 80326 HERA - physics: 7376.73103 mkb-1 H1Run - physics: 4760.64534 mkb-1 H1data - physics: 1232.762443 mkb-1 H1 Runs: 80323 - 80326 Tot curr/rate factor: 0.38% C/R F H1Run gated: 0.38% Rand.C.F: 1.77% RCF Run gated: 1.72% Relative ET trigg accept.: 0.3418 28/6/94 ============= C. Schwanenberger === Lumi RUN# 459 Start lumi run459 date: 28/6/94 Collision time: 6:27:37 - 7:06:44 Currents (mkA): Ie= 25265.00, Ip= 36000.00 Peak luminosity: 1571.693 mb-1 s-1 Peak spec.lumi : 363.44378 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: 3778.8356 mkb-1 H1 Run total lumi: 3112.9685 mkb-1 H1 data taken lumi: 2134.6355 mkb-1 H1 Runs: 80329 - 80332 HERA - physics: 2403.470298 mkb-1 H1Run - physics: 938.5076 mkb-1 H1data - physics: 150.6557 mkb-1 H1 Runs: 80332 - 80332 Tot curr/rate factor: 2.21% C/R F H1Run gated: 2.43% Rand.C.F: 3.02% RCF Run gated: 3.08% Relative ET trigg accept.: 0.2977 28.06.1994 ==================== H1KFOM === Cooling Water Problem..... Today near 11:20 it were switched off all H1Lumi equipment at r.101 (exept Movable Platform Koublers) by H1 Shift Crew. CAEN were switched off too (by hand of H1 Shift Crew). Reason was - absence of cooling water at r.101. Only FADC-crate uses this water - all another equipment were switched off not right (especially CAEN HV - switching off by hand can damage detectors). Yura is making all needed work for aliving of H1Lumi HW at r.101. 28/6/94 =================== s.robertson === Lumi RUN# 460 Start lumi run460 date: 28/6/94 Collision time: 8:27:54 - 10:36:23 Currents (mkA): Ie= 21050.00, Ip= 35900.00 Peak luminosity: 1797.446 mb-1 s-1 Peak spec.lumi : 463.861461 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: 10296.0709 mkb-1 H1 Run total lumi: 9519.9948 mkb-1 H1 data taken lumi: 6967.4367 mkb-1 H1 Runs: 80338 - 80348 HERA - physics: 9607.713086 mkb-1 H1Run - physics: 8452.559903 mkb-1 H1data - physics: 5995.197524 mkb-1 H1 Runs: 80339 - 80348 Tot curr/rate factor: 1.38% C/R F H1Run gated: 1.38% Rand.C.F: 1.58% RCF Run gated: 1.59% Relative ET trigg accept.: 0.2917 29.06.1994 ==================== H1KSOL === Lumi Problems ...... There are now two main Lumi problems related to Lumi measurements: 1. Integrated Lumi sometimes dropped down during Run Start after Abort of previous H1 Run. There was one event when Int,Lumi dropped down during H1 Run by about 4.5nb-1. 2. A big jumps of instantenous Lumi in LRTL banks (showlumi). Online Lumi did not show this Jumps. But today morning R.Gerhards showed me showlumi picture from current Lumi Run#461,and there was a big jump up in Instantenous Lumi about 33 nb-1. We have checked online Lumi measurements and found that Integrated Lumi for H1 jumped up at the same time (at 9.10) by 17.4nb-1 for H1gated Lumi and 15.4nb-1 for H1datataken Lumi,but the instantenous Lumi value did not show any jumps. The informati on was taken from H1LumiMonitor (History). The second problem seems to be related with Lumi data corruption, during calculation of Int.Lumi and preparing LRTL bank. Request to A.Fomenko to fix the problems. 29.06.1994 ==================== H1KFOM === re: Lumi Problems ........ As seems all high mentioned facts are known very long time ago and it is no any needs to repeat its again and make requests to Fomenko if somebody else at H1 had discovered its for himself. I cannot fix reasons of this problems. Collection of this facts is not so large. Each fact is fixed and it was made attempt to understand it. But up to now some situations are not understandable. Actions 'Let's make it immediately'-type can put additional back- ground for bug or mistake fixing. 29/6/94 ======================= === Lumi RUN# 461 Start lumi run461 date: 29/6/94 Collision time: 9:10:14 - 13:55:14 Currents (mkA): Ie= 21400.00, Ip= 41200.00 Peak luminosity: 1513.324 mb-1 s-1 Peak spec.lumi : 333.251561 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: 15944.599728 mkb-1 <-- must be checked H1 Run total lumi: 32237.5902 mkb-1 <-- must be recalculated H1 data taken lumi: 26408.3426 mkb-1 <-- must be recalculeted H1 Runs: 80516 - 80528 HERA - physics: 15039.344655 mkb-1 <-- must be checked H1Run - physics: 11052.188421 mkb-1 H1data - physics: 8122.167251 mkb-1 H1 Runs: 80519 - 80528 Tot curr/rate factor: 0.45% C/R F H1Run gated: 0.45% Rand.C.F: 1.15% RCF Run gated: 1.15% Relative ET trigg accept.: 0.3629 P.S. As seems it is new situation with spike at Current Luminosity value (no influence on HERA produced Inegrated Lumi). 29.06.1994 ==================== H1KSOL === re:re Lumi Problems ..... It is very nice position: "...all high mentioned facts are known very long time ago and it is no any needs to repeat its again and make requests ..." and it is the matter of taste to consider that "...Collection of these facts is not too large..." Maybe it would be better to look into code,I am ready to help by all means that I can. P.S. I am agree that position is really nice (a.f.) 30/6/94 ======================= rybicki === Lumi RUN# 462 Start lumi run462 date: 30/6/94 Collision time: 4:24:32 - 11:23:22 Currents (mkA): Ie= 17500.00, Ip= 42501.00 Peak luminosity: 1466.764 mb-1 s-1 Peak spec.lumi : 458.113792 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: 11569.546423 mkb-1 H1 Run total lumi: 9665.1391 mkb-1 <--- H1 data taken lumi: 8404.4611 mkb-1<--- H1 Runs: 80598 - 80614 HERA - physics: 11030.961169 mkb-1 H1Run - physics: 8930.056594 mkb-1<--- H1data - physics: 7776.160908 mkb-1<--- H1 Runs: 80601 - 80614 Tot curr/rate factor: 0.2% C/R F H1Run gated: 0.2% Rand.C.F: 0.53% RCF Run gated: 0.53% Relative ET trigg accept.: 0.3418 PS : H1 Lumi values are underestimated because H1 integr.Lumi dropped down two times during the Lumi Run.(Yu.S) PS by H01LNS: L4 histos for this run# are OK, at least qualitatively. PS by H01LNS: L5 histos for this run# are OK, at least qualitatively. 30/6/94 ===================== Gogitidze === Lumi RUN# 463 ......... Start lumi run463 date: 30/6/94 Collision time: 13:36:17 - 14:42:57 Currents (mkA): Ie= 21809.00, Ip= 41900.00 Peak luminosity: 1618.814 mb-1 s-1 Peak spec.lumi : 347.218448 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: 4879.794873 mkb-1 H1 Run total lumi: 4178.412494 mkb-1 H1 data taken lumi: 2965.690052 mkb-1 H1 Runs: 80624 - 80634 HERA - physics: 3896.648758 mkb-1 H1Run - physics: 2367.561069 mkb-1 H1data - physics: 1636.204473 mkb-1 H1 Runs: 80633 - 80634 Tot curr/rate factor: 0.38% C/R F H1Run gated: 0.37% Rand.C.F: 1.77% RCF Run gated: 1.75% Relative ET trigg accept.: 0.3615 PS by H01LNS: L4 histos for this run# are OK, at least qualitatively. PS by H01LNS: L5 histos for this run# are OK, at least qualitatively. 30.06.1994 15:50 ============== H01LNS === PDFIT for Q3.R78785 ====== PDFITs have been made for the request of A.F.; only "70", only "ep". Star(*) the line: LIST 'H01LNS.JPDFIT.BLOOKQ3.R78785.EP' Be carefull: Not take the lines with "infER" == infinite ERROR!(absent) I would prefer the variants: (statisticaly, they are the same) PD_FIT STARTED 30/06/94 15.38.54 l_text1,4: nt(100)(pdrec) cut.and.cut1 R lrun fg emin emax np eX e fitFLchi2 prob% E_shift%%+- B_res%%+- Entr Evnt R78785 70 12.0 35.0 46 ep 0 fitOK 16 99.1% (-1.9+-1.3)% (33+- 8)% 1864 2968 R78785 70 14.0 35.0 42 ep 0 fitOK 14 98.6% (-1.8+-1.3)% (32+- 8)% 1574 2968 R78785 70 16.0 35.0 38 ep 0 fitOK 9 99.6% (-1.5+-1.3)% (30+- 8)% 1287 2968 Notice that "Resolution"=="B_res%%" is ~ 32 %. P.S. cut=(s91.eq.1.and.pdrec.lt.999.and.vcdep.lt.0.2); cut1-> excluding of data from H1Runs 78814-78816,78874-79050, and 79494-79499 at which effect 'p11' was very large(a.f.) 30.06.1994 ===== dice2 ======== H1KFOM === Selected H1Lumi Monitrig.. Today I found 6 data sets with H1Lumi MONITRIG-events which were produced with standard job prepared by S.Levonyan at dice1- -environment: HERA03.H01.LUMIMON.C9400001 B02858 78048081 00001 ACS-E-C ...... HERA03.H01.LUMIMON.C9400006 K31551 78048081 00001 ACS-E-C It were selected events with (s91=1 only),with ET&PD&VC=1 and with ET&PD&nVC from these data sets: 1) S91=1 only 27553 events from total 391400 ( 42.6 MBytes) 2) ET&PD&VC 48370 events from total 391400 ( 80.2 MBytes) 3) ET&PD&nVC 48380 events from total 391400 ( 80.4 MBytes) At these data sets data from Runs 79913 up to 80525 are presented. Selected data were written into the next data sets at DESY IBM: H1KFOM.ETPDNVC.M16.C00 K35559 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M16.C00 K43787 78048081 00001 ACS-E-C H1KFOM.S91.M16.C00 K43808 78048081 00001 ACS-E-C 30/6/94 ===================== Gogitidze === Lumi RUN# 464 Start lumi run464 date: 30/6/94 Collision time: 16:05:09 - 18:31:40 Currents (mkA): Ie= 10252.00, Ip= 37400.00 Peak luminosity: 619.46 mb-1 s-1 Peak spec.lumi : 307.917138 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: 5802.267194 mkb-1 <--- must be corrected H1 Run total lumi: 5384.462 mkb-1 <--- must be corrected H1 data taken lumi: 4482.7814 mkb-1 <--- must be corrected H1 Runs: 80635 - 80645 HERA - physics: 3606.554229 mkb-1 H1Run - physics: 2898.037009 mkb-1 H1data - physics: 2416.691039 mkb-1 H1 Runs: 80639 - 80645 Tot curr/rate factor: 0.12% C/R F H1Run gated: 0.11% Rand.C.F: 0.45% RCF Run gated: 0.45% Relative ET trigg accept.: 0.3336 P.S. at Lumi RUN# 464 it was fixed spike at Current Luminosity value near 16:04 (200 mkb-1s-1). This value with multiplication om 10 sec put additional Integral Luminosity values into H1 Gated and H1 Data taken (Run 80635) on values near 2.2 nb-1 and 1.7 nb-1. PS by H01LNS: L4 histos for this run# are OK, at least qualitatively. PS by H01LNS: L5 histos for this run# are OK, at least qualitatively. 30.06.1994 ===== dice2 ======== H1KFOM === p11-problem............. It was found during first step of calibration with latest ET&PD&nVC events sample (Runs 79913-80525) that during Run 80230 something happened with Relation Coefficient value for p11-elements. Its value jumped from ordinary value near 1.0 into value near 2.0 (!). As seems high mentioned sample will be divided on little parts for calibration. 30.06.1994 ==================== H01GOG === LUMIMON data processing Dear friends, since few days a special job is processing each LUMIMON file and creating n-tuple NT(1) for further analysis with the format described below. NAM(1) = 'RUN' ! run number NAM(2) = 'RQ' ! run quality: 1=G, 2=M, 3=P, 0=unknown NAM(3) = 'BUNCH' ! bunch number (0-219) NAM(4) = 'BTYPE' ! bunch type (see JBUNCH in H1UTIL) NAM(5) = 'ATRIG' ! actual trigger (bit packed: ! 0 - eTAG, 1 - PD_low, ! 2 - WatVet, 3 - ET*PD*!VC ! 4 - ET*PD*VC, 5 - L_cal ) ! ATRIG = -1 for random triggers! * NAM(6) = 'ESTRIG' ! total trigger energy [GeV] NAM(7) = 'EETRIG' ! ET trigger energy [GeV] NAM(8) = 'EPTRIG' ! PD trigger energy [GeV] * NAM(9) = 'EE' ! reconstructed electron energy [GeV] NAM(10)= 'EP' ! reconstructed photon energy [GeV] NAM(11)= 'EV' ! energy deposit in Water Veto [GeV] * NAM(12)= 'XE' ! x(ET) reconstructed [cm] NAM(13)= 'YE' ! y(ET) reconstructed [cm] NAM(14)= 'XP' ! x(PD) reconstructed [cm] NAM(15)= 'YP' ! y(PD) reconstructed [cm] * NAM(16)= 'TEL1' ! Lumi trigger elements (bit packed: ! bits 0-7 copied from 112-119 TEL1 bits NAM(17)= 'ARTST' ! Artificial subtriggers (from HEAR(17)) ! included from the file C9400005 on Input: HERA03.H01.LUMIMON.C94000xx /lumi moni events Output: H01GOG.MLOOK.C94000xx /look files /xx = 01 etc. Note the following: 1) Default reconstruction results are used (meaning default calibration from database), just all necessary LUMI banks are unpacked and n-tuple is then filled; no LREC re-reconstruction is made in the job! 2) Trigger energies are taken from LRTN bank, but only when it is present (i.e. in ca. 10% of all events), otherwise -1.0 are filled into VEC(6), VEC(7), VEC(8) Please use these LOOK files for various analyses. Here is a summary table for the first files processed so far: ---------------------------------------------------------------------- File H1 runs Events Actual triggers (xx) s86 s91 s92 s93 s94 s95 ---------------------------------------------------------------------- 01 79848-79852 23314 79913-80014 41895 6130 4738 2762 9621 4642 5131 02 80014-80058 64906 9787 4461 2723 9563 5114 5514 03 80058-80258 65675 8069 4997 2701 12036 5076 5832 04 80258-80293 65372 5928 4333 2613 9857 4903 5179 ---------------------------------------------------------------------- 30.06.1994 ==================== F11LEV === LUMIMON files ............ I guess, LUMIMON files are reasonably well packed with only relevant (for us) information. An average event size, as measured on the first four files is 1.5 kb only, so reading must be fast. Therefore, there is no need to duplicate information further, selecting e.g. specific triggers on separate tapes. This only blows up the catalog on IBM and does not bring a real advantage. If people do not know how to select during reading, an example job can be provided. 30.06.1994 ===== dice2 ======== H1KFOM === CC Behaivour with Time... For last sample ET&PD&nVC-events (Runs79913-80525) it was built vectors with CC behaivour with time (from LRPP and LREP-banks). For first study it were built only vectors for most hot channels: p10-p14 and e21-e27. First view on high mentioned pictures put the next preliminary results a) vector with CC behaivour for p11 shows that at start of Lumi RUN# 452 (Run80232) CCp11 was changed on 56% (!!!) from previous value into low direction. This low value was kept during 7 next Lumi RUNs (up to #460th). During start of Lumi RUN# 461 CCp11 was changed into high direction on 50%. b) CCp13 is very sensetive for each start of Lumi RUN - at all start periods CCp13 is changing up to 25% into high direction and slowly is coming back to 'start' value; c) CCe22 - the same behaivour as CCp13 (jumps - up to 15%); d) CCe23 - up to 10%; e) CCe25 - up to 5%; f) CCe26 - up to 5%; g) CCe21,CCe24,CCe27,CCp12,CCp14 - are almost not sensetive to new e-fillings. CCvcs is changing up to 25% from start value (at start of Lumi Run #449th for example). Ordinary jumps are up to 15-20% into low value at this sample. 1/7/94 ===================== Gogitidze === Lumi RUN# 465 Start lumi run465 date: 30/6/94 Collision time: 22:33:33 - 3:28:58 Currents (mkA): Ie= 22702.00, Ip= 38100.00 Peak luminosity: 1850.821 mb-1 s-1 Peak spec.lumi : 475.268253 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: 16978.363967 mkb-1 H1 Run total lumi: 16309.3165 mkb-1 H1 data taken lumi: 13717.6537 mkb-1 H1 Runs: 80661 - 80674 HERA - physics: 15141.559786 mkb-1 H1Run - physics: 14102.900572 mkb-1 H1data - physics: 11594.976916 mkb-1 H1 Runs: 80663 - 80674 Tot curr/rate factor: 0.29% C/R F H1Run gated: 0.29% Rand.C.F: 0.94% RCF Run gated: 0.93% Relative ET trigg accept.: 0.3564 PS by H01LNS: L4 histos for this run# are OK, at least qualitatively. PS by H01LNS: L5 histos for this run# are OK, at least qualitatively. 01.07.1994 ==================== F11LEV === pd(11) and calibration.... This is my first reaction on the Fomenko's intension to split samples on many small pieces for the calibration, because of the pd(11) problem. First, a similar evidence have been observed in the analysis of the LUMI monitoring events, processed as described in Nelly's message from yesterday. More detailed information will be presented in one of our LPI meetings. It seems, pd(11) has real problems, but in average only in few % of all events. Therefore, my opinion is: 1) try to identify more precisely the reason 2) if it is hardware related instability, the channel must be either replaced, or exchanged with less important in the position (e.g. pd(24)) 3) DON't split calibration sample, but rather exclude these "bad" events! CC defined from small samples are statistically non- significant. The procedure, how to identify "bad" events must be developped. Note, if these are really bad events (incorrect pd(11) responce) then inclusion of them to the calibration produces wrong result! The same is true, and even more dangerous, for the permanently running online calibration, where these events also may seriousely deteriorate the result of the calibration procedure. 4) Continue permanently to monitor CC behaviour in time! 01.07.1994 ===== #FIC1,2 ====== H1KFOM === H1LumiOnLineReleases..... It were made new releases of H1LumiOnLinePrograms. Creation data/time are 01.07.94 10:21 for H1LumiOnLineFIC1 and 01.07.94 10:48 for H1LumiOnLineFIC2. A) H1LumiOnLineFIC1: It were made only 2 changings: 1) it was made update of main-program with hope that problem of decrementing of H1 Gated and H1 Data Taken Integrated Lumi values at boundaries of H1Lumi Runs (as it was fixed 7-8 times at H1Data Taking 94) will be removed; 2) it were changed IlevelA.f subroutine for accelerating of FER- responce fron its environment. It is possible to wait that percent of 'tailed' events (more then 1.6 msec FER) will be decremented. B) H1LumiOnLineFIC2: It was made only 1 changing: 1) it was made update of LumiMonotoring.f subroutine with hope that large spikes at Current Luminosity value will be removed. Both releases were booted into FICs today near 11:50 and were tested at Run 80701 with CentralTrigger and Luminosity branches only with Random 1 kHz trigger. There is hope that situation with FER-time will become better due to we looked for L2Keep-rate 112 Hz (not 102-103 as at previous releases) 1/7/94 ====================== willard === Lumi RUN# 466 Start lumi run466 date: 1/7/94 Collision time: 5:33:55 - 11:14:52 Currents (mkA): Ie= 23144.00, Ip= 37300.00 Peak luminosity: 1646.216 mb-1 s-1 Peak spec.lumi : 424.766138 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: 17263.868239 mkb-1 H1 Run total lumi: 16097.063372 mkb-1 H1 data taken lumi: 11905.02251 mkb-1 H1 Runs: 80676 - 80698 HERA - physics: 15903.847475 mkb-1 H1Run - physics: 11687.715562 mkb-1 H1data - physics: 8585.105029 mkb-1 H1 Runs: 80677 - 80698 Tot curr/rate factor: 0.39% C/R F H1Run gated: 0.38% Rand.C.F: 0.96% RCF Run gated: 0.98% Relative ET trigg accept.: 0.3562 P.S. At 06:32 it was fixed drop of H1 Gated and H1 Data Taking Integrated Luminosity on 2.6 nb-1 and 1.7 nb-1. At high mentiomed Run summary all corrections were made. It was looked for correlation of this situation with Stop H1 Run requested by Forward Muon Branch (ordinary H1Shift crew push on buttons for StopRun and Abort Run). This firstly observed correlation as seems is real reason of all previous drop at RunSummary's value of H1Gated and H1Data- Taking Integrated Lumi. At new release this situation foreseen now. PS by H01LNS: L4 histos for this run# are OK, at least qualitatively. PS by H01LNS: L5 histos for this run# are OK, at least qualitatively. 01.07.1994 ==================== H1KFOM === SystemSoftware Memory.... It was fixed many times strange behaivour of SystemSoftware Memory om both H1Lumi and H1Lumi2 MacIIs. As seems SystemSoftware Memory is incremented permanently and only reboot of MacIIs can help at this situtaion. This situation does not allow (enough often) to make standard manipualtion by H1 Shift Crew. As seems this situation is connected with activity of different Usik's Applications at the boards of both MacII. As example today morning it were fixed the next digits: H1Lumi MacII - SSWM - 3.801 Mbytes H1Lumi2 MacII - SSWM - 3.926 Mbytes After reboot of both MacII: H1Lumi MacII - SSWM - 2.600 Mbytes H1Lumi2 MacII - SSWM - 2.600 Mbytes Attempts to quit subsequently all applications did not help. 01.07.1994 12:45 ============== H01LNS === Proposal for ON-line ===== Proposal for Lumi-ON-line, In connection with the last msg of A.Fomenko: TO INSTALL AN AUTOMATIC REBOOT AT SOME SUTABLE MOMENTUM, PROBABLY, BETWEEN END AND START OF EVERY(!) LUMI-RUN#. Certainly, it is proposal of an amateur, but why not to try? During the shifts of my own I met this situation many times. L.Shtarkov, DESY. 01.07.1994 ==================== H1KFOM === Different Lumi at OnLine. Today it was found that Current Luminosity value which is calculated at FIC#2 -environment is more on 10-12% then one calculated at Usik's application. May be this difference is so large due to today 'non- -central' beam position (=-0.5cm,=+0.6). ACCC=1.008 at this case. During enough large time me and Yura fixed high mentioned difference and cannot understand this situation. Attempt to play with buttons on Control-window (switching On/Off ACCC and TrEff) did not change this situation. As seems soon we must hear new replics from HERA-people why Luminosity from H1Lumi is different at different places Who (exept me) can recommend to Usik to make something for removing of early mentioned situtaion? P.S. If acceptance correction ACCC=1.008, that can only explain 0.8% difference and not 10%. Real reason must be different. (S.L.) P.S1: Just now (14:50) Jura was at HERA Control Room and we again fixed the same difference. As seems it is possible to make diagno ze of high mentioned situation after processing of LUMM-bank contents for Lumi RUN# 467. As variant - may be Usik uses Total ET&PD trigger rate (not collided+pilot) etc. We can reproduced all possible variants of Luminosity calculation from data which are kept at LUMM and LRTL-banks. Let's wait TCL-cart- ridge with data from Lumi RUN# 467.(a.f.) 1/7/94 ====================== willard === Lumi RUN# 467 ......... Start lumi run467 date: 1/7/94 Collision time: 12:21:06 - 16:40:25 Currents (mkA): Ie= 23292.00, Ip= 36201.00 Peak luminosity: 1322.065 mb-1 s-1 Peak spec.lumi : 365.730724 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: 8295.816304 mkb-1 H1 Run total lumi: 7735.1851 mkb-1 H1 data taken lumi: 6879.0767 mkb-1 H1 Runs: 80711 - 80720 HERA - physics: 7149.304367 mkb-1 H1Run - physics: 6387.792977 mkb-1 H1data - physics: 5629.637126 mkb-1 H1 Runs: 80714 - 80720 Tot curr/rate factor: 0.4% C/R F H1Run gated: 0.38% Rand.C.F: 1% RCF Run gated: 0.92% Relative ET trigg accept.: 0.3517 PS by H01LNS: L4 histos for this run# are OK, at least qualitatively. PS by H01LNS: L5 histos for this run# are OK, at least qualitatively. 02.07.1994 ==================== H1KFOM === Speed up online (E.Elsen) READMAIL message stored : SAT, 2 JUL 94 14:07:31 MESZ Date: SAT, 2 JUL 94 13:53:31 +0200 From: Eckhard Elsen Subject: re: upgrade of fer-issuing from ilevela.f To: Alexander Fomenko Eckhard Elsen H1 Collaboration, DESY - FH1K - Notkestrasse 85, 22603 Hamburg, Germany Tel. (040) 8998-2565 (secr. ext. 3144, fax 3093) Dear Sascha, This is a success. The Lumi DAQ response is now much better and I want to discuss the details with you in the near future. I looked at 2 runs: 80701 There is no extreme tail! and the typical FER is < 2 ms as before. Only if the second trigger comes too quickly the response is 4ms (or even less frequent 6 ms). This effect is small and we should discuss its origin. The buffering is ok because if input rate is too high, CTrig (with only 10 buffers) is limiting the trigger rate as it should be. 80719 Phase 4. There is a small tail, but at a much reduced level (few per mille). The average DT is now at the level of 3 ms! The DT is now dominated by trackers. My wish: If the readout program is ok, please leave it running also for phase 3. We have to get more experience and it looks like a big improvement. I would like to show you a few distributions. Monday may be a good time. Good luck, Eckhard 02.07.1994 ==================== H1KFOM === H1Lumi Banks for #467..... It were selected all needed for analyze H1Lumi and H1CTRIG BOS-banks from first 4 H1RAWD-data sets from 9 which were recorded during Lumi RUN# 467. All needed banks including KEEP-banks were selected on the next data set: H1KFOM.H1LUMI.R467.C00 K45551 78048081 00001 ACS-E-C 61522 events are kept at this data set. Data from H1Runs 80700-80715 are included into this data set. Data which were collected from 11:55:15 up to 13:57:41 (a little more then 2 hours) are included into this data set. Data from 5 H1 Runs (80711-80715) with non-zero integrated Luminosity are included into this data set. Some interesting digits from first view on this data: Time slice 12:25:39 01.07.94 (start of H1 Run 80711): Ie total = 21.5 mA Ee= 27.520 GeV Ip total = 36.2 mA Ep=819.920 GeV = -0.2 cm VC total rate =1020 kHz = +0.7 cm PD total rate = 166 kHz = 1.003 ET total rate = 105 kHz PD1total rate = 220 kHz PD2total rate = 68 kHz Current Lumi value = 1430 mb-1s-1 ET&PD total rate = 63 kHz Number of collided bunches - 153 ET&PD&nVC total rate= 8.0 kHz Number of p-pilot bunches - 17 PD&nVC total rate = 21.5 kHz Number of e-pilot bunches - 15 eTAG total rate = 35 kHz Number of e-bunches - 168 Number of p-bunches - 170 = (PD rate - PD&nVC rate)/PDrate = 0.870 Bunch structures: (10+1)*6 + (0+11) + (10+1)*6 + (0+5) + (10+1)*5 + (0+6) + (0+10) p-beam ( 9+2)*6 + (9+ 2) + ( 9+2)*6) +(3+2) + ( 9+2)*5 + (0+6) + (3+ 7) e-beam It is possible to see all high mentioned H1Lumi Trigger elements and bits rates from 20000,30000,40000,....,100000th vectors at time slice 30 min at the next LOOK-binary data set: H1KFOM.LOOK.R80700 FAST16 3010200E 00000 DASD First attempts to find some algorithm of Lumi calculation for getting of Lumi on 10-15% less (as it was made at Usik's algorithm yesterday) were unsuccesful. Only it is possible to suppose that (may be) it was overestimated ET&PD-background rate. 03.07.1994 ==================== H1KFOM === NAN-Value at HERA Produced Today morning at 07:43 it was fixed NAN-value at HERA Produced Luminosity cell. H1 Gated anf H1 Data Taken Integrated Luminosity values were not corrupted. It means that all is OK with Integrated Lumi values at H1DataFlow. I had attempt to find some correlation with H1CDAQ status at this period. It was found that at 07:42 Run 80835 was stopped on request of Central Tracker Branch (before this it was fixed Inavalid VME taxi response). At 07:43:32 it was started set of WarmStarts (5 attempts in 15 min.) and at 07:58 H1CDAQ was alived again with Run 80842. I cannot explain yet this correlation but fact is fixed. It was found that corrupted cell is C2 (absolute address of this cell is B0A5E134 as it seen from MacII. I 'reconstructed' HERA-produced Luminosity value from Usik's history for Current Luminosity value behaivour with time (status 09:24). It was found that from 06:16 up to 09:24 it were collected 8.669 nb-1. At 09:44 I put value 8.6694e+22 into high mentioned cell. P.S. I hope, you saved a value of 8.6694e+33 ??? (S.L.) P.S. I really mistaked with order - I put 8.6694e+22 but it was needed to put 8.6694e+21 (due to normalization coefficient value 1.0e+12) At 11:15 I put value 1.0e+22 into high mentioned cell(preliminary) At 12:34 I put new 'reconstructed' value from Usik's history as 12.8024 nb-1 (1.28024e+22).(a.f.) 03.07.1994 ==================== H1KFOM === Different Lumi at OnLine. Today it were checked again Current Luminosity value which was pro- duced with FIC#2 and one which was produced with Usik's application. Situation the same as it was seen 01.07.94 during Lumi RUN #467. Time FIC#2's value Usik's Value Difference 09:20 0.532*10**30 0.456*10**30 14.4% 10:30 0.412*10**30 0.346*10**30 17.3% As seems it is permanent feature of Usik's Application. It is pity but it is difficult to check this situtaion at off-line immediately due to corrupted TCUR-bank (as I found at Lumi RUN# 467).e-beam bunch currents after 185 bunch as seems are corrupted (bottom of TCUR-bank).It is pity that namely last e-beam bunch current (209-211) are pilot e-bunches. E.Elsen was asked to test TCUR-bank contents at Lumi RUN #467. P.S. As you might remember, in one of my applications which produces RLOOK history files, I create history plots both for direct online luminosity values and recalculated ones (e.g. fig.15), where lumi is calculated using LRTL rates and TCUR banks. One can see, that for the RUN #467 both figures coinside, so this particular problem is NOT related to TCUR content. (S.L.) 3/7/94 ===================== Gogitidze === Lumi RUN# 468 Start lumi run468 date: 3/7/94 Collision time: 1:17:21 - 5:24:22 Currents (mkA): Ie= 20795.00, Ip= 31500.00 Peak luminosity: 1202.125 mb-1 s-1 Peak spec.lumi : 388.64794 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: 10003.819122 mkb-1 H1 Run total lumi: 9802.693077 mkb-1 H1 data taken lumi: 7220.28905 mkb-1 H1 Runs: 80805 - 80822 HERA - physics: 8598.917803 mkb-1 H1Run - physics: 6850.923877 mkb-1 H1data - physics: 4731.48535 mkb-1 H1 Runs: 80809 - 80822 Tot curr/rate factor: 0.18% C/R F H1Run gated: 0.2% Rand.C.F: 1.2% RCF Run gated: 1.21% Relative ET trigg accept.: 0.3385 PS by H01LNS: L4 histos for this run# are OK, at least qualitatively. PS by H01LNS: L5 histos for this run# are OK, at least qualitatively. 3/7/94 ===================== Gogitidze === Lumi RUN# 469 Start lumi run469 date: 3/7/94 Collision time: 6:16:56 - 12:53:48 Currents (mkA): Ie= 21909.00, Ip= 31301.00 Peak luminosity: 1245.499 mb-1 s-1 Peak spec.lumi : 374.240963 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: 13058.287969 mkb-1 H1 Run total lumi: 10775.7065 mkb-1 H1 data taken lumi: 7851.0987 mkb-1 H1 Runs: 80824 - 80866 HERA - physics: 11950.916374 mkb-1 H1Run - physics: 9307.738891 mkb-1 H1data - physics: 6501.945062 mkb-1 H1 Runs: 80826 - 80866 Tot curr/rate factor: 0.44% C/R F H1Run gated: 0.4% Rand.C.F: 0.95% RCF Run gated: 0.92% Relative ET trigg accept.: 0.3334 PS by H01LNS: L4 histos for this run# are OK, at least qualitatively. PS by H01LNS: L5 histos for this run# are OK, at least qualitatively. 03.07.1994 ==================== F11LEV === Minutes of the LPI meeting Place: DESY Time: 2/07/94 18-20 pm. Participants: Andreev, Baranov, Belousov, Eliseev, Fomenko, Gogitidze, Gorbov, Levonian, Mezenin, Soloviev 1) Shifts in NH. Note, that participation in the shifts is one of the obligatories for all H1 authors. Note also, that experts supporting the system in NH may be released from the shifts, since they anyhow spend a major part of the time there. In a summary table I tried to reconstruct the whole history. It might be that something is still missing. Please let me know in such a case. 1994 ---- 13/04 - 19/04 S. Kotelnikov 7/05 - 14/05 S. Rusakov 15/05 - 22/05 Yu.Soloviev 31/05 - 6/06 N. Gogitidze 3/06-17/06 S. Levonian (RC) 13/06 - 20/06 V. Andreev 22/06 - 29/06 L. Shtarkov 30/06 - 7/07 N. Gogitidze 8/07 - 15/07 P. Baranov 16/07 - 23/07 A. Fomenko 9/08 - 16/08 A. Lebedev 28/08 - 3/09 Ya.Vazdik 4/09 - 11/09 S. Levonian Summary ------- ----------------------------------------------------------------------- NN Name 1992 shifts 1993 shifts 1994 shifts 1995 shifts ----------------------------------------------------------------------- 1 Andreev V.F. 6 2. Baranov P.S. 6 3. Belousov A.S. 4. Fomenko A.M. 6 6 5. Gogitidze N. 6 6+6 6. Kotelnikov S.K. 6+6 6 7. Lebedev A.I. 6 6 8. Levonian S.V. 6 6+6+RC RC+6 9. Malinovski E.I. 10. Rusakov S.V. 6 6 11. Sheviakov I.P. 12. Shtarkov L.N. 6 13. Smirnov P.A. 6 14. Soloviev Yu.V. 6 6 15. Usik A.P. 6 16. Vazdik, Ya.A. 6 ----------------------------------------------------------------------- 2) Overall task list for LUMI group. Names mentioned there are those who presently are involved in one of the listed tasks. ################################################################### ## ## ## LUMI GROUP TASK LIST. LAST UPDATE 27-June-94 by S.L. ## ## ## ################################################################### 1) Low-y gamma-p tagging ------------------------- Aim: Extend acceptance of the present e-tagger to lower y region (HQ triggering, elastic VM, RP calibration) Solutions: a) KRS-calorimeter at z=-110-180 m b) Gas Cherenkov counter at z=-37m + description of e-beamline till z=-200m (V.Andreev) + acceptance studies for KRS (V.Andreev) + acceptance studies for gas Cherenkov (S.Levonian) o modifications of the beampipe (S.L., V.A.) o preparation of the detectors (A.Belousov+?) o study of the gas Ch responce (V.A., A.F.) o trigger for gas Ch prototype (I.Sheviakov) o written proposal (Sept-94) (S.L.) o infrastructure (platform, cables,...) (?) 2) Lumi online improvements --------------------------- o overall reliability (A.F., A.U., I.Sh) o DAQ upgrade (improve time response) (A.F., I.Sh.) o stable version of data presentation (A.U.) o preparation to higher rates (I.Sh,A.F.,A.U.,Yu.S.) 3) Calibration -------------- o standartize the tool (A.Fomenko, S.L.?) + define CC offline (A.F., N.G.) + global energy shift (L.Shtarkov) + update database (S.L.) o study CC behaviour (time, rates, lumi) (A.F., Yu.S) o from LUMM data to automatic procedure (A.F., S.L., L.S.) 4) Data quality checks ---------------------- + prepare/update L4/L5 histograms (S.L., L.S.) + regular checks of L4/L5 plots, reports (L.Shtarkov) o tool for automatic hist. checks (S.L., L.S.) + trigger efficiencies, thresholds (S.L.,Yu.S.,L.S.,N.G.) 5) LUMI cross check ------------------- + lumi monitoring events (S.L., N.G., A.F.) + VC, PD, ET efficiency (S.L., N.G.) + determination of real ET-acceptance (S.L., N.G.) o tuning of the MC to the real conditions (S.L.) o integrated lumi for G+M runs from gamma (S.L.) 6) LUMI data for physics analysis --------------------------------- + banks, tools (S.L.) + RLOOK history files (S.L.) + integrated lumi summary table, plots (S.L.) + corrections for online errors (S.L.) o description (H1 note) (S.L.) 7) Alternative LUMI estimates ----------------------------- o gamma-rate method (S.L., N.G.) o gamma-flux method (V.A.) + limited ET-acceptance (S.L., N.G., A.F.) o LUMM data ? (A.F.) 8) E-tagger in H1SIM -------------------- o interface for the real acceptance (S.L.) o new tagger(s) (S.L., V.A.) Standard off-line actions necessary for the correct physics analysis -------------------------------------------------------------------- 1) Select LUMI monitoring events/banks (now automatic) 2) Prepare n-tuple and make first quick analysis a) LUMIMON files -> LOOK n-tuples (S.L., N.G.) b) trigger statistics, thresholds, efficiencies (S.L., N.G.) c) energy spectra -> check trigger/rec calibration (S.L., N.G.) 3) Make absolute calibration a) define RC set from ET*PD*!VC monitoring sample (A.F., N.G.) b) create E_gamma distribution (LREC -> LOOK fig.) (A.F.) c) define global E-shift (fit dn/dE, or E*dn/dE) (L.S.) d) define VC calibration from ET*PD*VC sample (A.F.) e) update database (LFRC, LESC banks) (S.L.) 4) When necessary, repeat step 2) including LREC(new CC) (S.L., N.G.) 5) Define corrections to the online lumi estimate a) ET*PD method: use |x_ET| people have to think over how to use this time in a most efficient way. E.g. to reinstall gas Cherenkov closer to the beampipe. 2) Possible change in the ET-acceptance due to slightly different optics for e+ compared to e- mode. -> New constants for online lumi estimate. Andreev has to keep in touch with the machine people to get from them possible modifications for the beam-line in the region from IP to -24m (contact persons: Brinkmann, Bialowans, Kose) 3) Higher rates are expected due to higher e+ currents/lumi -> new calibration and other known consequences... 07.07.1994 ==================== F11LEV === Special announcement...... This is a global H1lumi summary table for full time of physics at HERA _______________________________________________________________ | | | | | HERA ep-collisions 1992-1994 | | ------------------------------ | | | | Integrated Luminosity (HERA-total) : 1.81 pb-1 | | Integrated Luminosity (HERA-physics): 1.59 pb-1 | | Integrated Luminosity (H1-gated) : 1.00 pb-1 | | Integrated Luminosity (H1-physics) : 0.92 pb-1 | | | |_____________________________________________________________| Last night a shift crew: Jan Olsson Nelly Gogitidze Lidia Goerlich Gerhard Knies has collected 8 nb-1 and thus reached 1 pb-1 of H1-gated luminosity! We still have a chance to get 1 pb-1 of physics data (G+M quality) before HERA will switch to the positrons. 07.07.1994 ==================== H1KFOM === No Answer from H1RunCoord. Yesterday I sent e-mail to H1 Run Coordinator (15:04) and up to now no any answer (13:06). There is no any comments at H1 Morning Meeting. This is the text of my mail: "..... SENDMAIL message to Braunschwe Date: WED, 6 JUL 94 15:04:06 +0200 From: Alexander Fomenko Subject: Asking To: W. Braunschweig A.M. Fomenko, DESY -FH1K- Notkestrasse 85, D 2000 Hamburg 52 Tel. (040) 8998-2568(121 1b),-4356(Hera Nord), -2433(125 1c) (permanent address: Lebedev Phys.Inst., Moscow, Russia) NODE: DHHDESY3 USERID: H1KFOM Dear Dr.Braunschweig, H1Lumi team is testing now the Cherenkov Gas Counter as prototype of future upgraded eTAG. We had first data taking for its testing at Lumi RUN #420. Now first data are processed and it is clear that it is needed to make new data taking with new HV set. What is Your opinion - is it possible to make this data taking during nearest Lumi RUNs? For this data taking we need only another mode of H1Lumi Data Flow with full set of H1Lumi banks (Mode 1). Standard operation is made with cutted set of H1Lumi Banks (Mode 6). Size of Luminosity branch data piece at each H1 Event will be incremented on factor 1.7-2 at Mode 1. If You will agree with this proposal let me know. At this (possible) period of data taking it would be good if somebody from H1Lumi experts were at H1 Control Room. Sincerely, Alexander Fomenko ...." What it means? Who knows? S.L.: That means, the run coordinator is busy with other more urgent problems. I think, there is no need to create a heavy mail traffic on each tiny question. This is in a scope of our own expertize to decide whether or not we need to take these data, and if yes, just switch the corresponding mode. Lumi expert should be of course around to ensure that everything works smoothly. At most - just inform shift leader to make a corres- ponding entry in the H1 logbook (But explain correctly what does it mean, because sometimes people think that any small change means - a special data, not to be used for the physics analysis. In our case this is not true). 07.07.1994 ===== dice2 ======== H1KFOM === Relation CoefficientsSetB3 Due to at 21.06.94 mentioned conclusion about need to divide 2nd data om 3 subsamples and due to bad situation with Photon Arm Energy distribution Fit with 2C-sample (see messages of H01LNS from 27.06 and 30.06.94) it was decided to make some changings at 2C-sample: a) it were excluded data from P-marked H1 Runs (see H1EP); b) 2C-data sample was incremented with more late data up to H1 Run 80224 which were collected at S.Levonyn's LUMIMON-cartridghes; c) it were excluded so called 'obviously bad' data from the next H1Runs: 1) 78786-78688 2) 78814-78854 3) 78875-79050 4) 80010-80016 5) 80218-80223 d) it were excluded data from H1Lumi Dedicated Runs (79494,79497,79499 - see Vova's message 18.06.94). After all high mentioned 'cleaning' of 2C-data sample it were collected 39292 events with ET&PD&nVC trigger 30705 events with ET&PD&VC trigger 24459 events with S91-trigger. It were got 39292 ET&PD&nVC from these Runs and it were used for calibration 25188 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 1.103 1.135 0.000 1.073 1.141 1.188 1.127 1.059 1.247 1.117 2.345 0.897 1.001 1.128 1.114 0.951 1.040 0.990 1.044 0.779 0.966 1.030 1.040 1.009 1.008 1.036 1.016 0.989 0.934 0.924 1.016 0.952 1.001 0.985 1.143 1.121 0.885 0.968 0.963 1.065 0.926 1.044 0.000 1.018 0.900 0.881 0.957 1.078 0.000 ==> Relation Coeff.Set for PD 1.720 0.967 1.015 1.312 0.904 0.972 1.018 0.990 1.021 1.041 0.980 1.024 1.010 0.997 1.048 1.064 0.996 0.978 1.004 0.975 1.496 0.957 1.061 0.994 0.929 ==> Sig. at Relation Coeff.Set for ET 0.000 0.001 0.000 0.032 0.007 0.010 0.000 0.024 0.045 0.018 0.025 0.023 0.022 0.004 0.039 0.029 0.031 0.023 0.059 0.126 0.048 0.015 0.017 0.020 0.014 0.022 0.020 0.016 0.019 0.028 0.020 0.016 0.028 0.020 0.039 0.005 0.031 0.014 0.021 0.018 0.008 0.016 0.000 0.025 0.017 0.015 0.031 0.000 0.000 ==> Sig. at Relation Coeff.Set for PD 0.023 0.019 0.023 0.009 0.000 0.022 0.023 0.023 0.023 0.016 0.017 0.015 0.017 0.031 0.024 0.024 0.035 0.021 0.018 0.027 0.051 0.019 0.016 0.021 0.000 ==> Ent. at Relation Coeff.Set for ET 1 7 0 4 9 10 1 5 8 9 19 6 6 5 1246 554 522 325 444 107 142 7186 11219 8435 6757 5706 4798 2032 1042 1020 1094 863 1024 632 718 25 10 23 41 34 20 8 0 12 7 14 11 1 0 ==> Ent. at Relation Coeff.Set for PD 38 14 21 19 1 433 3277 4862 1652 129 2716 13538 19354 8692 1000 682 4051 5787 2908 232 31 26 44 15 2 As You can see all is OK with sigma values for each from 'hot' cells Relation Coeff. histos - not so large as earlier (may be e19 only?). Runs 78785- 80224 (ET&PD&nVC-sample - near 39K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.49 0.88 27.48 0.85 27.52 0.85 As You can see all is OK with sigma values at ETrec+PDrec spectra. (a little less then earlier). Runs 78785- 80224 (ET&PD&VC-sample - near 31K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.34 1.21 27.42 1.15 It were used as start values of CC for Photoproduction branch ones which were produced after 3rd step of calibration with 3rd subsample of 2nd sample (Runs78785-79666) and CCvcs as 2.954. (from H1KFOM's 26.06.94 message at LLC). 07.07.1994 ===== dice2 ======== H1KFOM === new set of PDREC-spectra.. Today it were produced 100th ntuple for S91=1 events from earlier mentioned 3rd subsample of the 2nd sample (Runs 78785-80224): H1KFOM.XLOOKQ4.R78785 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.BLOOKQ4.R78785 FAST12 3010200E 00000 DASD Asking to L.N.Shtarkov to make Photon Arm Energy Spectra Fitting of high mentioned 70th histo (ep-option). After this it will be possible to define Global EnergyShifts Constants and CCvcs value. It were prepared 100th tuples with ET&PD&nVC and ET&PD&VC-events for procedure of defining Global Energy Shifts and CCvcs: H1KFOM.XLOOKQ2.R78785 FAST02 3010200E 00000 DASD H1KFOM.XLOOKQ3.R78785 FAST12 3010200E 00000 DASD 7/7/94 =================== N.Gogitidze === Lumi RUN# 480 Start lumi run480 date: 7/7/94 Collision time: 5:43:46 - 12:38:46 Currents (mkA): Ie= 24588.00, Ip= 46400.00 Peak luminosity: 1753.204 mb-1 s-1 Peak spec.lumi : 292.730118 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: 19917.2362 mkb-1 H1 Run total lumi: 13551.095908 mkb-1 H1 data taken lumi: 9909.0163 mkb-1 H1 Runs: 81138 - 81172 HERA - physics: 19436.186765 mkb-1 H1Run - physics: 9394.394872 mkb-1 H1data - physics: 7705.737523 mkb-1 H1 Runs: 81157 - 81172 Tot curr/rate factor: 0.01% C/R F H1Run gated: 0.01% Rand.C.F: 1.18% RCF Run gated: 0.86% Relative ET trigg accept.: 0.3459 PS by H01LNS: L4 histos for this run# are OK, at least qualitatively. PS by H01LNS: L5 histos for this run# are OK, at least qualitatively. 07.07.1994 ==================== H1KFOM === Global Shifts and CCvcs B3 It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 1.0035 for PD Channels (exept VCs), 0.999 for ET channels. Correction factor for CCvcs is 1.058. So CCvcs = 2.954*1.058=3.125Mev/ FADCcount. These digits are valid for H1Lumi events from Run 78875 up to 80224 (exept H1Runs mentioned at today my message earlier). Runs 78785- 80224 (ET&PD&nVC-sample - near 39K events) xetcut&vcdepcut Step Mean Sigma 0 27.52 0.88 Runs 78785- 80224 (ET&PD&VC-sample - near 31K events) xetcut Step Mean Sigma 0 27.52 1.17 P.S. Relation Coefficients Set see at 07.07.94 message. 07.07.1994 ==================== H1KFOM === Global Shifts and CCvcs B1 It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 1.00 for PD Channels (exept VCs), 1.002 for ET channels. Correction factor for CCvcs is 1.056. So CCvcs = 2.954*1.056=3.119Mev/ FADCcount. These digits are valid for H1Lumi events from Run 77804 up to 78174 Runs 77804- 78174(ET&PD&nVC-sample - near 52K events) xetcut&vcdepcut Step Mean Sigma 0 27.52 0.81 Runs 77804- 78174 (ET&PD&VC-sample - near 27K events) xetcut Step Mean Sigma 0 27.52 1.16 P.S. Relation Coefficients Set see at 22.06.94 message. 07.07.1994 ==================== H1KFOM === Global Shifts and CCvcs B2 It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 1.009 for PD Channels (exept VCs), 0.9945 for ET channels. Correction factor for CCvcs is 1.017. So CCvcs = 2.954*1.017=3.004Mev/ FADCcount. These digits are valid for H1Lumi events from Run 78381 up to 78784 Runs 78381- 78784(ET&PD&nVC-sample - near 27K events) xetcut&vcdepcut Step Mean Sigma 0 27.52 0.85 Runs 78381- 78784 (ET&PD&VC-sample - near 22K events) xetcut Step Mean Sigma 0 27.52 1.13 P.S. Relation Coefficients Set see at 25.06.94 message. 08.07.1994 ===== dice2 ======== H1KFOM === Selected H1Lumi Monitrig.. Today I found 14 data sets with H1Lumi MONITRIG-events which were produced with standard job prepared by S.Levonyan at dice1- -environment: HERA03.H01.LUMIMON.C9400001 B02858 78048081 00001 ACS-E-C ...... HERA03.H01.LUMIMON.C9400014 K13137 78048081 00001 ACS-E-C It were selected events with (s91=1 only),with ET&PD&VC=1 and with ET&PD&nVC from these data sets: 1) S91=1 only 63080 events ( 97.5 MBytes) 2) ET&PD&VC 113013 events (186.9 MBytes) 3) ET&PD&nVC 115376 events (191.6 MBytes) At these data sets data from Runs 79913 up to 81164 are presented. Selected data were written into the next data sets at DESY IBM: H1KFOM.ETPDNVC.M114.C00 K42150 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M114.C00 K20427 78048081 00001 ACS-E-C H1KFOM.S91.M114.C00 K22063 78048081 00001 ACS-E-C P.S. (for Levonyan) As seems this selection is needed. You can see that I can use only one data set for calibration steps or ntuple making but not all 14 (it is difficult to make preliminary stagin of 14 data set or waiting for 14 stagin-end inside dice2 batch job - at last case my job can block diceX-queue for another users - we have only 2 batch job of X-class simultaneous at dice2 (ordinary). P.S.1: First view on this large(3rd) sample put the next (preliminary) conclusions: a) data from 30 Lumi RUNs are presented at this data sample (from #451 up to #480th); b) 3rd data sample includes data from H1Run 80230 (not succesful #451th Lumi RUN) up to Run 81164 (last #480th Lumi RUN for today). These data were collected from 26.06.94 16:43 up to 07.07.94 12:06 (almost 11 days). c) as seems this data sample it will be needed to divide on 2 subsample (3A and 3B): 3A) from Run 80230 up to 80528 (near 28.6K ET&PD&nVC events), 11 Lumi Runs (from #451 up to #461); 3B) from Run 80598 up to 81164 (near 66.8K ET&PD&nVC events). 19 Lumi Runs (from #462 up to #480); This fact is defining from observing of CC-behaivour with time and RC-behaivour with time. Vectors with CC and RC behaivours with time are kept at the next LOOK-binary data sets: H1KFOM.ZLOOKQ6.R80225 FAST16 3010200E 00000 DASD H1KFOM.CLOOK1.R80225 FAST01 3010200E 00000 DASD At first data set You can see contents of 10021-10027 vectors and 20010-20014 vectors as % of changing CC from first fixed value (at start of Run 80230) for most hot H1Lumi detector cells. At 2nd data set You can see contents of 1021-1027 vectors and 2010-2014 vectors as changing with time of absolute value of Relation Coefficient for the same 'hot' cells. As time I used number of event at sample (from 0 up to 95403). As example - Lumi RUN #461st is finished at 28624th event (Run80528) - and You can see at all vectors (especially on 20011 and 2011 which are connected with p11-element) large jumps - these jumps are good evidence on something changed at H1Lumi-hot channels (mainly at p11) - and it is obviously that this is the clear boundary for calibration subsamples. 08.07.1994 ==================== H1KFOM === Answer from H1RunCoord. READMAIL message stored : FRI, 8 JUL 94 19:27:34 MESZ Received: from DSYIBM.DESY.DE by DSYIBM.DESY.DE (IBM MVS SMTP V2R2.1) with BSMTP id 0345; Fri, 08 Jul 94 16:51:00 MET Date: FRI, 8 JUL 94 16:43:40 +0200 From: Wolfgang Braunschweig Subject: re: asking To: Alexander Fomenko Dear Alexander, You are very welcome to do these measurements; please let me know some more details, how many different HV settings, duration of the measurement at each setting, any special conditions like low or high currents etc., so that we can plan it in more detail. Best regards Wolfgang Braunschweig 09.07.1994 ==================== H1KFOM === Neutron Counter H1Runs.... Yesterday from 16:21 up to 18:06 it were collected some data for Neutron Counter investigation. Only Central Trigger and Luminosity branches were involved into H1CDAQ. Neutron Counter Team used T_MonitorNC for threshold tuning for NC-trigger element for different HERA p-beam energies. It were recorded 16 H1 Runs during so called 'slow ramping' of HERA p-ring: H1Run Ep(GeV) Ip(mA) Time Events L2KeepRate(Hz) 81274 59.811 47.6 16:21 5592 21.8 81275 118.001 47.6 16:26 33565 46.3 81276 149.984 47.6 16:40 18294 78.9 81277 256.869 47.6 16:46 105 17.5 81278 256.869 47.6 16:46 50149 107.8 81279 447.970 47.6 17:01 368 40.9 81280 447.970 47.6 17:02 38669 104.8 81281 447.970 47.6 17:10 1298 7.0 81282 481.961 47.6 17:14 57069 111.2 81283 560.342 47.6 17:23 23193 112.0 <- max possible 81284 611.192 47.6 17:27 71302 109.0 81285 677.377 47.6 17:38 11708 106.0 81286 677.377 47.6 17:41 78631 109.7 81287 801.120 47.6 17:54 30463 109.2 81288 819.919 47.6 17:59 14347 106.3 81289 819.919 47.6 18:03 20844 105.3 09.07.1994 ===== dice2 ======== H1KFOM === Relation CoefficientsSet3A Due to at 08.07.94 mentioned conclusion about need to divide 2nd data on 2 subsamples it was decided to make 3A subsamples with the next cuts: a) it were excluded data from P-marked H1 Runs (see H1EP); b) it were excluded so called 'obviously bad' data from the next H1Runs: 1) 80344-80525 After all high mentioned 'cleaning' of 3A-data sample it were collected 17576 events with ET&PD&nVC trigger 17150 events with ET&PD&VC trigger 8998 events with S91-trigger. It were got 17576 ET&PD&nVC from these Runs and it were used for calibration 11058 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 0.000 1.133 0.000 1.118 1.141 1.224 0.000 1.030 1.204 1.113 2.402 0.861 1.010 1.137 0.970 0.968 1.066 0.821 1.012 0.417 0.933 1.041 1.046 1.017 1.025 1.052 1.034 0.983 0.925 0.995 0.964 0.895 0.971 0.942 1.106 1.124 0.902 0.991 0.994 0.998 0.923 1.050 1.017 0.974 0.892 0.915 0.897 1.066 0.000 ==> Relation Coeff.Set for PD 1.758 0.966 1.009 1.325 0.967 0.996 1.007 1.006 1.028 1.026 0.973 1.013 0.997 0.994 1.005 0.986 1.031 0.973 1.004 0.997 1.577 0.962 1.074 0.998 0.000 ==> Sig. at Relation Coeff.Set for ET 0.000 0.000 0.000 0.000 0.003 0.000 0.000 0.000 0.001 0.000 0.019 0.000 0.007 0.008 0.007 0.003 0.012 0.006 0.005 0.005 0.008 0.013 0.022 0.016 0.014 0.023 0.018 0.010 0.006 0.012 0.006 0.004 0.005 0.008 0.006 0.000 0.000 0.011 0.003 0.007 0.002 0.001 0.000 0.000 0.002 0.004 0.007 0.000 0.000 ==> Sig. at Relation Coeff.Set for PD 0.002 0.006 0.006 0.005 0.000 0.007 0.017 0.019 0.014 0.001 0.012 0.033 0.018 0.043 0.009 0.003 0.008 0.014 0.005 0.009 0.014 0.019 0.003 0.008 0.000 ==> Ent. at Relation Coeff.Set for ET 0 2 0 1 6 4 0 3 6 3 8 1 2 3 308 258 308 68 191 10 65 3212 4967 3722 2905 2452 2065 870 535 599 457 353 399 260 296 7 2 8 18 22 15 3 1 1 2 8 8 2 0 ==> Ent. at Relation Coeff.Set for PD 25 13 11 5 1 259 1930 3148 1141 77 896 5182 8662 4636 634 76 659 1207 1059 93 6 3 9 8 0 As You can see all is more or less OK with sigma values for each from 'hot' cells Relation Coeff. histos. Runs 80225- 80343 (ET&PD&nVC-sample - near 17K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.46 0.88 27.47 0.87 27.49 0.86 Runs 80225- 80343 (ET&PD&VC-sample - near 17K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.52 1.18 27.51 1.13 It were used as start values of CC for Photoproduction branch ones which were produced after 3rd step of calibration with 3rd subsample of 2nd sample (Runs78785-80224) and CCvcs as 3.125. (from H1KFOM's 07.07.94 message at LLC). 09.07.1994 ===== dice2 ======== H1KFOM === new set of PDREC-spectra.. Today it were produced 100th ntuple for S91=1 events from earlier mentioned 1st subsample of the 3rd sample (Runs 80225-80343): H1KFOM.YLOOKQ4.R80225 FAST19 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.R80225 FAST04 3010200E 00000 DASD Asking to L.N.Shtarkov to make Photon Arm Energy Spectra Fitting of high mentioned 70th histo (ep-option). After this it will be possible to define Global EnergyShifts Constants and CCvcs value. 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.R80225 FAST17 3010200E 00000 DASD H1KFOM.YLOOKQ3.R80225 FAST04 3010200E 00000 DASD 09.07.1994 ===== dice2 ======== H1KFOM === Relation CoefficientsSet3B Due to at 08.07.94 mentioned conclusion about need to divide 2nd data on 2 subsamples it was decided to make 3B subsample with the next cut: a) it were excluded data from P-marked H1 Runs (see H1EP); After all high mentioned 'cleaning' of 3B-data sample it were collected 53217 events with ET&PD&nVC trigger 50311 events with ET&PD&VC trigger 26678 events with S91-trigger. It were got 53217 ET&PD&nVC from these Runs and it were used for calibration 33676 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 1.102 1.122 1.081 1.126 1.143 1.238 1.097 1.033 1.195 1.090 2.327 0.857 0.970 1.127 1.058 0.962 0.940 0.940 1.062 0.455 0.985 1.041 1.046 1.030 1.031 1.056 1.045 1.021 1.019 1.038 1.034 0.978 1.002 1.034 1.055 1.056 0.933 1.060 0.950 1.034 0.926 1.019 1.017 1.068 0.870 0.871 0.932 1.058 0.000 ==> Relation Coeff.Set for PD 1.998 0.996 0.999 1.476 0.985 1.016 0.954 0.975 0.996 1.049 0.944 1.005 0.987 0.988 0.981 1.065 0.992 0.951 0.985 1.035 1.574 0.934 1.006 0.987 0.000 ==> Sig. at Relation Coeff.Set for ET 0.000 0.006 0.000 0.002 0.001 0.005 0.031 0.001 0.004 0.014 0.024 0.005 0.010 0.002 0.022 0.027 0.046 0.031 0.022 0.017 0.051 0.014 0.024 0.022 0.021 0.021 0.021 0.015 0.028 0.028 0.032 0.033 0.022 0.034 0.027 0.025 0.057 0.028 0.024 0.024 0.004 0.023 0.000 0.076 0.009 0.026 0.028 0.002 0.000 ==> Sig. at Relation Coeff.Set for PD 0.103 0.027 0.024 0.028 0.000 0.023 0.020 0.020 0.027 0.015 0.020 0.028 0.022 0.036 0.019 0.034 0.043 0.035 0.018 0.033 0.004 0.024 0.021 0.005 0.000 ==> Ent. at Relation Coeff.Set for ET 3 10 1 7 11 10 4 6 17 14 35 3 5 5 1620 837 638 408 584 32 176 9614 15190 11335 8798 7449 6327 2716 1595 1683 1228 1054 1216 1069 831 32 29 74 78 72 46 23 2 13 23 44 21 5 0 ==> Ent. at Relation Coeff.Set for PD 60 27 31 45 1 715 4792 8015 2956 241 2803 16119 26382 13876 1834 365 2947 5198 3751 412 17 18 30 11 0 As You can see all is more or less OK with sigma values for each from 'hot' cells Relation Coeff. histos. Runs 80601- 81164 (ET&PD&nVC-sample - near 53K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.47 0.90 27.49 0.87 27.52 0.87 Runs 80601- 81164 (ET&PD&VC-sample - near 50K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.54 1.21 27.53 1.16 It were used as start values of CC for Photoproduction branch ones which were produced after 3rd step of calibration with 3rd subsample of 2nd sample (Runs78785-80224) and CCvcs as 3.125. (from H1KFOM's 07.07.94 message at LLC). 09.07.1994 ===== dice2 ======== H1KFOM === new set of PDREC-spectra.. Today it were produced 100th ntuple for S91=1 events from earlier mentioned 2nd subsample of the 3rd sample (Runs 80601-81164): H1KFOM.YLOOKQ4.R80601 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.R80601 FAST13 3010200E 00000 DASD Asking to L.N.Shtarkov to make Photon Arm Energy Spectra Fitting of high mentioned 70th histo (ep-option). After this it will be possible to define Global EnergyShifts Constants and CCvcs value. 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.R80601 FAST01 3010200E 00000 DASD H1KFOM.YLOOKQ3.R80601 FAST04 3010200E 00000 DASD 09.07.1994 ==================== H1KFOM === Global Shifts and CCvcs 3B It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 1.024 for PD Channels (exept VCs), 0.9834 for ET channels. Correction factor for CCvcs is 1.005. So CCvcs = 3.125*1.005=3.141Mev/ FADCcount. These digits are valid for H1Lumi events from Run 80601 up to 81164 Runs 80601- 81164(ET&PD&nVC-sample - near 53K events) xetcut&vcdepcut Step Mean Sigma 0 27.52 0.87 Runs 80601- 81164 (ET&PD&VC-sample - near 50K events) xetcut Step Mean Sigma 0 27.52 1.18 09.07.1994 ==================== H1KFOM === Global Shifts and CCvcs 3A Due to very poor statistics of PD&nVC events at 70th histo (812 entri- es) for Photon Arm Energy Distribution fit it is proposed to use Global Shift Constants and CCvcs the same as for data sample 2C. 1.0035 for PD Channels (exept VCs), 0.999 for ET channels. CCvcs=3.125 Mev/FADCcount 09.07.1994 ==================== H01GOG === Useless LUMIMON cartridges The following LUMIMON cartridges contain no Lumi events. They only were selected to LUMIMON stream because of the presence of the Neutron counter trigger bit (bit 119 = n_cntr). Since Levonian's routine in SGI logging job selects only LUMI and general trigger banks (and not LRNA) there is no useful information on these cartridges whatsoever. Don't use them - it will be waste of computing time! HERA03.H01.LUMIMON.C9400015 K24009 78048081 00001 ACS-E-C HERA03.H01.LUMIMON.C9400016 K30304 78048081 00001 ACS-E-C HERA03.H01.LUMIMON.C9400017 K31225 78048081 00001 ACS-E-C HERA03.H01.LUMIMON.C9400018 K35193 78048081 00001 ACS-E-C HERA03.H01.LUMIMON.C9400019 K36499 78048081 00001 ACS-E-C HERA03.H01.LUMIMON.C9400020 K26020 78048081 00001 ACS-E-C Just now another file appears (C9400021). Please wait until it will be checked. 9/7/94 ============== P.Baranov H01BPS === Lumi RUN# 481 Start lumi run481 date: 9/7/94 Collision time: 19:34:27 - 22:47:51 Currents (mkA): Ie= 21441.00, Ip= 38700.00 Peak luminosity: 2165.425 mb-1 s-1 Peak spec.lumi : 527.621986 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: 15979.529587 mkb-1 H1 Run total lumi: 14912.197175 mkb-1 H1 data taken lumi: 11600.474747 mkb-1 H1 Runs: 81352 - 81362 HERA - physics: 14288.281105 mkb-1 H1Run - physics: 12997.911716 mkb-1 H1data - physics: 9861.144454 mkb-1 H1 Runs: 81355 - 81362 Tot curr/rate factor: 0.22% C/R F H1Run gated: 0.23% Rand.C.F: 1.34% RCF Run gated: 1.34% Relative ET trigg accept.: 0.3569 P.S. Peak Luminosity from ShowLumi - near 2.3*10**30 cm-2s-1 (a.f.) PS by H01LNS: L4 histos for this run# are OK, at least qualitatively. PS by H01LNS: L5 histos for this run# are OK, at least qualitatively. 09.07.1994 ==================== H1KFOM === New RC Sets in H1DataBase As final action of all last calibration and recalibration 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: 22.06.1994 ----- dice2 -------- H1KFOM --- Relation CoefficientsSetB1 25.06.1994 ----- dice2 -------- H1KFOM --- Relation CoefficientsSetB2 07.07.1994 ----- dice2 -------- H1KFOM --- Relation CoefficientsSetB3 09.07.1994 ----- dice2 -------- H1KFOM --- Relation CoefficientsSet3A 09.07.1994 ----- dice2 -------- H1KFOM --- Relation CoefficientsSet3B 07.07.1994 -------------------- H1KFOM --- Global Shifts and CCvcs B1 07.07.1994 -------------------- H1KFOM --- Global Shifts and CCvcs B2 07.07.1994 -------------------- H1KFOM --- Global Shifts and CCvcs B3 09.07.1994 -------------------- H1KFOM --- Global Shifts and CCvcs 3A 09.07.1994 -------------------- H1KFOM --- Global Shifts and CCvcs 3B Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LFRC (_501) 24 e-p data 407092305 77804 78380 77 940709 H1KFOM 25 e-p data 407092311 78381 78784 77 940709 H1KFOM 26 e-p data 407092314 78785 80224 77 940709 H1KFOM 27 e-p data 407092318 80225 80600 77 940709 H1KFOM 28 e-p data 407092325 80601 0 77 940709 H1KFOM Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LESC (_582) 34 e-p data 407092305 77804 78380 3 940709 H1KFOM 35 e-p data 407092311 78381 78784 3 940709 H1KFOM 36 e-p data 407092314 78785 80224 3 940709 H1KFOM 36 e-p data 407092318 80225 80600 3 940709 H1KFOM 37 e-p data 407092325 80601 0 3 940709 H1KFOM P.S. for this moment - all collected with Luminosity branch data from start of H1 Data Taking'94 up to Lumi RUN #480 are calibrated. 10.07.1994 ==================== H1KFOM === Zero Pedestals Yesterday Vova Andreev tested data sample with LREF and LRPF-banks which was got from Lumi RUN #420 for possible zero pedestal situations finding at most hot channels of H1Lumi Detectors(p11,p12,p13,e21,e22). Zero pedestals in principle exist but its percent is negligable yet. 10.07.1994 ==================== H1KFOM === 100th ntuples for LMONI ============= Overflow Status From 14 first LUMIMON-data sets it were selected the next 5 data sets: H1KFOM.ETPDNVC.M114.C00 K42150 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M114.C00 K20427 78048081 00001 ACS-E-C H1KFOM.S86.M114.C00 K37117 78048081 00001 ACS-E-C H1KFOM.S91.M114.C00 K22063 78048081 00001 ACS-E-C H1KFOM.S93.M114.C00 K20402 78048081 00001 ACS-E-C Data which are recorded at this data sets are divided on 3 subsamples due to different calibration constants at H1DatsBase. It were produced 5 x 3 100th ntuples for different data subsamples: a) first subsample at 1-14 Lumi Monuitrig data sets: H1 Runs 79913-80224 (all coefficients from H1DataBase) H1KFOM.TLOOKQ2.R79913 ETPDnVC FAST10 3010200E 00000 DASD H1KFOM.TLOOKQ3.R79913 ETPDVC FAST13 3010200E 00000 DASD H1KFOM.TLOOKQ4.R79913 S91 FAST04 3010200E 00000 DASD H1KFOM.TLOOKQ5.R79913 S93 FAST08 3010200E 00000 DASD H1KFOM.TLOOKQ6.R79913 S86 FAST18 3010200E 00000 DASD Events at subsample and entries into 100th ntuple: ETPDnVC: 17407 ---> 17321 (99.51%) ETPDVC: 17496 ---> 16412 (93.80%) S91: 10774 ---> 6309 (58.56%) S93: 23868 ---> 4837 (20.27%) S86: 21171 ---> 19627 (92.71%) Overflow: ETPDnVC: 4 - p05, 3 - e22, 1 - e21,e23,e35 max= 0.02% ETPDVC: 1 - p05, 5 - e22, 4 - e25, 2 - e23,e24 max= 0.03% S91: 4 - p10, 1 - p16,e22,e35 max= 0.04% S93: 1 - p05,p16 max= 0.004% S86: 37 - e15, 3 - e22, 2 - e35,e37 max= 0.17% b) second subsample at 1-14 Lumi Monitrig data sets: H1 Runs 80225-80600 (all coefficients from H1DataBase) H1KFOM.TLOOKQ2.R80225 ETPDnVC FAST08 3010200E 00000 DASD H1KFOM.TLOOKQ3.R80225 ETPDVC FAST09 3010200E 00000 DASD H1KFOM.TLOOKQ4.R80225 S91 FAST13 3010200E 00000 DASD H1KFOM.TLOOKQ5.R80225 S93 FAST04 3010200E 00000 DASD H1KFOM.TLOOKQ6.R80225 S86 FAST02 3010200E 00000 DASD Events at subsample and entries into 100th ntuple: ETPDnVC: 29004 ---> 28784 (99.20%) ETPDVC: 29274 ---> 27491 (93.91%) S91: 15770 ---> 9754 (61.85%) S93: 33806 ---> 7701 (22.78%) S86: 25869 ---> 22750 (88.35%) Overflow: ETPDnVC: 55 - p11, 7 - p05, 1 - p10,p12 max= 0.19% 3 - e22, 2 - e15,e35, 1 - e25 ETPDVC: 14 - p11, 1 - p05,p10 max= 0.05% 5 - e22, 4 - e15, 3 - e35, 2 - e25, 1 - e23,e24 S91: 119 - p11, 2 - p10, 1 - p05,p16 max= 0.75% 2 - e15, 1 - e22,e25 S93: 66 - p11, 1 - p05,p16 max= 0.20% 2 - e35, 1 - e15 S86: 6 - p11, 1 - p06 (!!!! for antiPD-trig)max= 1.18% 304 - e15, 5 - e35, 2 - e37, 1-e21,e23,e46 P.S. this subsample is selected from another ones due to jump at CCp11 from 3.2 on 1.6 MeV/FADCcount (overflow at p11 - as result of this jump). c) third subsample at 1-14 Lumi Monitrig data sets: H1 Runs 80601-81164 (all coefficients from H1DataBase) H1KFOM.TLOOKQ2.R80601 ETPFnVC FAST09 3010200E 00000 DASD H1KFOM.TLOOKQ3.R80601 ETPDVC FAST13 3010200E 00000 DASD H1KFOM.TLOOKQ4.R80601 S91 FAST04 3010200E 00000 DASD H1KFOM.TLOOKQ5.R80601 S93 FAST08 3010200E 00000 DASD H1KFOM.TLOOKQ6.R80601 s86 FAST18 3010200E 00000 DASD Events at subsample and entries into 100th ntuple: ETPDnVC: 66399 ---> 65702 (98.95%) ETPDVC: 63629 ---> 60040 (94.36%) S91: 35175 ---> 22316 (63.44%) S93: 70802 ---> 15166 (21.42%) S86: 47601 ---> 41647 (87.49%) Overflow: ETPDnVC: 17 - p05, 2 - p01,p16, 1 - p02,p13,p17 max= 0.03% 5 - e22, 3 - e21, 2 - e25, 1 - e24,e15,e37,e45 ETPDVC: 5 - p05, 1 - p10,p16 max= 0.02% 12 - e22, 5 - e15, 4 - e21, 3 - e23,e35 2 - e24,e25 1 - e26 S91: 11 - p05, 8 - p16, 6 - p10 2 - p14, max= 0.03% 1 - p13,p15,p20 3 - e22, 1 - e21,e15,e23 S93: 10 - p16, 3 - p10 3 - p05 max= 0.01% 1 - e21,e15 S86: no ovfl at PD max= 0.41% 197 - e15, 2 - e35, 1 - e10,e21,e26,e37,e45 11.07.1994 ==================== H1KFOM === Calibration Data Samples ============= Proposal PD1&nVC as s92 As You can see from previous messages connected with calibration procedure of H1Lumi Detectors there are 3 main data samples for calib- ration: a) ET&PD&nVC-events sample b) ET&PD&VC-events sample c) PD1&nVC as subsample of PD1 (PD_low or S91) sample. Today I checked one of the Nelly's made 1st ntuples (for 6th LUMIMON data set) and made the next digits: a) ET&PD&nVC-events sample: 6962 events from 55000 - 12.7% of events at LUMIMON-data sets; - there are 4 sources for this data sample: 1. S94 Lumi Monitrig (63.4%) 2. S92 Lumi Monitrig (33.8%) 3. S91 Lumi Monitrig ( 1.9%) 4. other H1 triggers ( 0.9%) b) ET&PD&VC-events sample: 7072 events from 55000 - 12.9% of events at LUMIMON-data sets; - there are 4 sources for this data sample: 1. S95 Lumi Monitrig (68.1%) 2. S93 Lumi Monitrig (12.3%) 3. S91 Lumi Monitrig (13.8%) 4. other H1 triggers ( 5.8%) c) PD1&nVC subsample from S91 (432 from 3576) from 55000 - 0.8% (!!!) of events at LUMIMON-data sets; - there is 1 source for this data sample: 1. S91 Lumi Monitrig (100%) - S91 sample itself gets only 6.5% of all events at LUMIMON-data set and subsample PD1&nVC - only 12.1% from this digit. So - proposal: a) let's change s92 H1 trigger bit setting from ET&PD&nVC as it was up to now from 22.05.94 to new setting - PD1&nVC; S92 trigger bit is retranslated from L_Cal trigger element. H1Lumi Trigger elements: Lum_int PD2 (not changed) PD_low PD1 (not changed) Lcal PD1&nVC (before this it was ET&PD&nVC) ElDet ET (not changed) PhotDet PD (not changed) WatVet VC (not chnaged) eTAG ET&nPD&nVC (not changed) NC NC (not changed) At H1 Central Trigger the next H1Lumi subtriggers will be presented: s86 - eTAG s89 - eTAG&NC (made at H1 Central Trigger Logic from eTAG and NC) s91 - PD_low s92 - Lcal (as PD1&nVC) s93 - WatVet s94 - ET&PD&nVC (made at H1 Central Trigger Logic from ET,PD,VC) s95 - ET&PD&VC (made at H1 Central Trigger Logic from ET,PD,VC) b) let's ask of Eckhard Elsen to tune s92 prescale gap on new value due to changing of s92 trigger setting. 11.07.1994 ==================== H01LNS === On Lumi Subtriggers ====== In accordance with A.Fomenko's proposal on a new Lumi-sub-trigger: It is necessary to discuss pro and contra, and just to wait a little, it is highly unreasonable to harry with any new proposal on triggers. I am convinced, that the most important Lumi-demand for subtriggers is having some Lumi-Subtrigger that is at any time identical (!!!) to the On-Line trigger that is beeng used for the Lumi-calculations. Shame on me, but I am not sure that such a Lumi-subtrigger exists now, If I am mistaken, better say this in a more definite way, to be sure. The other demand (desire), is getting some kind of over-determination, probably, having ET&PD = ET&PD&VC + ET&PD&nVC (m.b. the same as above). And the next: Its highly desireable to have the H1-Prescaler-conditions to be imposed exactly on the "On-Line-Lumi-counters", not on a mixture. A bad example - Off-Line comparing of ET before/after L4, and On-Line. L.Shtarkov, Moscow. 11.07.1994 ==================== H1KFOM === Preparing Injection Today at 16:30 HERA Shift Crew made anounce that "problem solved. preparing injection" and made 'massage' of HERA p-ring "O-->820-->0--> -->40GeV" (histeresis connected loop). At 16:42 - 'please switch Your HV off'. At 17:17 - 'injection'. At 17:46 - Ip total near 3.4 mA with life time 3 hours, 10 bunches, phase tuning, preliminary injection. At 17:48 - preliminary injected p-beam was dumped. At 17:50 - start of standard p-beam injection (60 first bunches). At 19:06 - Ip total = 39.4 mA, start of ramping. At 19:12 - p-beam was lost. 11.07.1994 ==================== H1KFOM === Positron Operation This is part of message at ZEUSBEAM about positron operation: "..... Summary of the HERA Coordination Meeting 11.07.94 .... Positron operation Luminosity running will stop next Monday in order to prepare the machines for positron operation. The polarity of components in DESY III (kicker), PETRA (have to switch between proton and positron operation), beam transport lines and HERA will be changes. The whole switch over is estimated to take 3 weeks. The third week will already be used to set up for luminosity running and for luminosity test runs. The expected improvement of the electron lifetime is a factor of two. Provided that positron operation is significatnly better, the present understanding is that HERA will continue with proton positron collisions until the electron ring vacuum system is modified, e.g. most likely for about 1 1/2 years. Uwe Schneekloth ...." 12.07.1994 ==================== H1KFOM === Spike of Currrent Lumi Tonight (12.07.94 at 0:46) during start of Luminosity measurement it was fixed spike at Current Luminosity value (near 9*10**30 cm-2s-1) It was fixed 'jump' at H1gated and H1datataken on value near 22 nb-1. It means that from RunStart up to first Luminosity measurement only a little more then 2 sec. were fixed. Only 2 sec after reset of all counters for Luminosity measurement. 12/7/94 ======================= === Lumi RUN# 482 Start lumi run482 date: 12/7/94 Collision time: 0:46:36 - 3:54:25 Currents (mkA): Ie= 21327.00, Ip= 34700.00 Peak luminosity: 1324.003 mb-1 s-1 Peak spec.lumi : 358.313656 mb-1 s-1 mA-2 Number of collided b.: 140 Number of e-filled b.: 168 Number of p-filled b.: 159 Number of e-pilot b.: 28 Number of p-pilot b.: 19 HERA total lumi: 8527.51204 mkb-1 H1 Run total lumi: 36198.2044 mkb-1 <---- to be corrected H1 data taken lumi: 34966.2334 mkb-1 <---- to be corrected H1 Runs: 81485 - 81491 HERA - physics: 8003.463298 mkb-1 H1Run - physics: 6519.991916 mkb-1 H1data - physics: 5405.716698 mkb-1 H1 Runs: 81486 - 81491 Tot curr/rate factor: 0.67% C/R F H1Run gated: 0.66% Rand.C.F: 1.13% RCF Run gated: 1.1% Relative ET trigg accept.: 0.3679 P.S. New p-beam bunch structure, new number of e-pilot bunches. Spike at Current Lumi Measurement (first measurement) - see previous message. PS by H01LNS: L4 histos for this run# are OK, at least qualitatively. PS by H01LNS: L5 histos for this run# are OK, at least qualitatively. 12/7/94 ============= J.Cvach,P.Baranov === Lumi RUN# 483 Start lumi run483 date: 12/7/94 Collision time: 4:45:14 - 8:47:03 Currents (mkA): Ie= 21423.00, Ip= 34100.00 Peak luminosity: 1230.394 mb-1 s-1 Peak spec.lumi : 326.822875 mb-1 s-1 mA-2 Number of collided b.: 140 Number of e-filled b.: 168 Number of p-filled b.: 159 Number of e-pilot b.: 28 Number of p-pilot b.: 19 HERA total lumi: 11385.761507 mkb-1 H1 Run total lumi: 10684.2564 mkb-1 H1 data taken lumi: 8545.8268 mkb-1 H1 Runs: 81496 - 81510 HERA - physics: 11063.032966 mkb-1 H1Run - physics: 10039.538516 mkb-1 H1data - physics: 7956.37219 mkb-1 H1 Runs: 81498 - 81510 Tot curr/rate factor: 1.33% C/R F H1Run gated: 1.3% Rand.C.F: 1.07% RCF Run gated: 1.06% Relative ET trigg accept.: 0.3606 PS by H01LNS: L4 histos for this run# are OK, at least qualitatively. PS by H01LNS: L5 histos for this run# are OK, at least qualitatively. 12.07.1994 ==================== H1KSOL === HV for El.#48.Mode 1.... For Lumi Run#484 Mode 1 and HV = 2100V on El#48 was set. 12/7/94 ==================== P.Baranov === Lumi RUN# 484 (with Mode1) Start lumi run484 date: 12/7/94 Collision time: 10:15:30 - 10:50:06 Currents (mkA): Ie= 24862.00, Ip= 33800.00 Peak luminosity: 1361.549 mb-1 s-1 Peak spec.lumi : 335.306931 mb-1 s-1 mA-2 Number of collided b.: 140 Number of e-filled b.: 168 Number of p-filled b.: 159 Number of e-pilot b.: 28 Number of p-pilot b.: 19 HERA total lumi: 2190.916274 mkb-1 H1 Run total lumi: 1791.6877 mkb-1 H1 data taken lumi: 1150.589 mkb-1 H1 Runs: 81524 - 81527 HERA - physics: 1506.070875 mkb-1 H1Run - physics: 615.384543 mkb-1 H1data - physics: 196.599624 mkb-1 H1 Runs: 81526 - 81527 Tot curr/rate factor: 3.62% C/R F H1Run gated: 3.88% Rand.C.F: 2.77% RCF Run gated: 2.85% Relative ET trigg accept.: Not calc. P.S. Mode 1 and new HV set for e48 element (see previous message). 12.07.1994 ==================== H1KSOL === PD Thresholds Changes Today during Lumi RUN# 485 it were changed thresholds at PD and PD1 trigger elements. New threshold setting is right after Run 81539. Before this thresholds had next values (at Egor's units): PD = 0.75 PD1 = 0.5 After changing: PD = 0.50 PD1 = 0.25 Changing was made at 13:10 12.07.94 (see LUTR-bank) before Start H1 Good Runs at this Lumi RUN. There was not fixed more or less significant change at this period at Current Luminosity values. 12/7/94 ==================== P.Baranov === Lumi RUN# 485 (with Mode1) Start lumi run485 date: 12/7/94 Collision time: 12:55:37 - 15:33:19 Currents (mkA): Ie= 19429.00, Ip= 33100.00 Peak luminosity: 1235.601 mb-1 s-1 Peak spec.lumi : 408.813842 mb-1 s-1 mA-2 Number of collided b.: 137 Number of e-filled b.: 165 Number of p-filled b.: 159 Number of e-pilot b.: 28 Number of p-pilot b.: 22 HERA total lumi: 6332.125885 mkb-1 H1 Run total lumi: 3402.720501 mkb-1 + 232.0 mkb-1 (a.f.) H1 data taken lumi: 1858.551568 mkb-1 + 41.5 mkb-1 (a.f.) H1 Runs: 81538 - 81565 HERA - physics: 5640.028298 mkb-1 H1Run - physics: 3194.682301 mkb-1 + 232.0 mkb-1 (a.f.) H1data - physics: 1664.988068 mkb-1 + 41.5 mkb-1 (a.f.) H1 Runs: 81540 - 81565 Tot curr/rate factor: 1.41% C/R F H1Run gated: 1.39% Rand.C.F: 1.36% RCF Run gated: 1.34% Relative ET trigg accept.: 0.3573 P.S. Mode 1 was kept for all H1Runs at Lumi RUN# 485. New PD and PD1 thresholds were installed (see previous message). P.S.1It were fixed 2 little spikes at Current Luminosity values 1st - at 14:05:19 from 0.7*10**30 to 1.0*10**30 cm-2s-1 2nd - at 15:21:28 from 0.4*10**30 to 0.72*10**30 cm-2s-1 Both spikes are explained with spikes at Total ET&PD Rate 1st - from 26 kHz to 40 kHz 2nd - from 15 kHz to 28 kHz Next 'false' Integrated Lumi was added into Integral Lumi values: 1st - near 3.0 mkb-1 2nd - near 3.2 mkb-1 (a.f.) P.S.2 During this Lumi Run (at 13:55) it was fixed decremention of Integrated Lumi values (both H1 Gated and H1 Data taken but not HERA produced) at 13:55. There was Run 81544 at this time. Run 81544 was started at 13:42:55 and was stoppped (ordinary Run Stop procedure) at 14:00:19. SHOWLUMI shows last 'good' value of integrated Lumi at 13:59:58, Usik's history shows decremention at 13:55 (?). If suppose that all collected Integrated Luminosity values at Run 81544 were not added to H1Lumi Summary digits: H1 Gated Lumi must be incremented on 232.0 mkb-1 H1 Data Taken must be incremented on 41.4 mkb-1. H1DataBase Integrated Lumi values as ordinary at this case are not corrupted. (a.f.) Possible reason of high mentioned decremention - BG-area of FIC#1 program was not operated between StopRun 81544 and StartRun81545. Zeroing of previous Run Integrated Lumi is made immediately after adding of Run Integrated Lumi values to C2-value at BG-area at 2 possible loops (large and little). May be it is reasonable to add the same procedure into FIC#2 program. Zeroing is made (and it is right) during StartRun - interrupt routine operation (without adding - due to impossibility of floating point opera- tions at FG-area of FIC). P.S.3 Lumi RUN was ended with unwaitable p-beam lost. PS by H01LNS: L4 histos for this run# are OK, at least qualitatively. PS by H01LNS: L5 histos for this run# are OK, at least qualitatively. 12.07.1994 ==================== H1KFOM === HERAp-beam bunch structure Starting with Lumi RUN #482 HERA-people use new p-beam bunch structure (one of the 10 bunch train at first 60 bunches is skipped) and it were added 219 p-bunch. Number of p-filled bunches - 159. Before Lumi RUN #482 number of p-filled bunches was 170. Number of e-pilot bunches is 28 now. 12.07.1994 ==================== H1KFOM === H1Lumi Monitrig (E.Elsen) Today at J.Olsson's Data Quality meeting it was happened discussion between Eckhard Elssen and H1Lumi people about need of decremention of H1Lumi Monitrig at H1DataFlow. Eckhard Elsen proposed to decrement prescale factors at H1Lumi Monitrig on factor 10. One of arguments was presented that it was fixed maximal rate near 1.0 Hz for H1Lumi Monitrigs. Yura explained that really at first phase of any Lumi RUN rates of H1Lumi monitrigs are larger (may be significantly large) then at middle and final phase of Lumi Run. Eckhard agreed on factor 3 decrementing. Yura proclaimed our proposal about s92 trigger setting changing on PD&nVC. Ekchard promised to tune new prescale for S92 after new trigger setting. May be tomorrow. 12.07.1994 ==================== H1KSOL === TCL tool on SGI..... The tool for making N-tuple (S.Levonian) from J.Olsson TCL files is now on SGI. You can find (and use) examples for the job in following directories: for stagein: /home/dice/soloviev/stage/tclstage source :........../soloviev/lumi/lumi94/ludata.f makefile:........../soloviev/lumi/lumi94/ludata.mkfile FPACK :........../soloviev/lumi/lumi94/ludata.fpack qsub :........../......../lumi/lumi94/ludata.q This tool uses the CMZ load library libh1tools.a (from S.Levonian) the path of that is indicated in ludata.mkfile file. 13/7/94 ============ M.Besancon H1KMRC === Lumi RUN# 486 Start lumi run486 date: 13/7/94 Collision time: 2:42:51 - 6:23:09 Currents (mkA): Ie= 22446.00, Ip= 31300.00 Peak luminosity: 1756.818 mb-1 s-1 Peak spec.lumi : 485.774083 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: 12745.591482 mkb-1 H1 Run total lumi: 11137.141936 mkb-1 H1 data taken lumi: 6105.735439 mkb-1 H1 Runs: 81589 - 81600 HERA - physics: 11943.386679 mkb-1 H1Run - physics: 9962.437013 mkb-1 H1data - physics: 4973.043255 mkb-1 H1 Runs: 81590 - 81600 Tot curr/rate factor: 0.35% C/R F H1Run gated: 0.35% Rand.C.F: 1.4% RCF Run gated: 1.39% Relative ET trigg accept.: 0.3365 PS.h01lns: L4 histos for this run# are OK, at least qualitatively. PS.h01lns: L5 histos for this run# are OK, at least qualitatively. 13.07.1994 ==================== H1KFOM === H1Lumi Dedicated Runs Today at morning H1 coordination meeting it was made remark that we were not right when yesterday put Mode 1 into our DAQ-mode. H1 Run Coordinator said that special decision was made (after consultation with U.Straumann and E.Elsen) to make H1Lumi Dedicated Runs at the finishing stage of nearest Lumi RUN for Cherenkov Gas counter prototype investigation. Immediately after 9:00 meeting H1 Run Coordinator decided to make H1Lumi Dedicated Runs with 2 HV setting on 20 min. each. Both Runs were written with Central Trigger and Luminosity branches involved into H1 CDAQ operation. Felix Sefkow had tuned prescales for s91-s95 trigger bits. L2KeepRate was near 55Hz (dead line for Mode 1 is 89-90 Hz). First Run - 81611 - with HVchgas=2100 V (#2nd crate 26th channel 2nd Run - 81612 - with HVchgas=2200 V (#2nd crate 26th channel 13.07.1994 ==================== H1KFOM === HERAp-beam bunch structure Starting from Lumi RUN #486 HERA-people use old standard bunch structure for p-beam with 170 p-bunches. Number of e-pilot bunches is 15 now. 13/7/94 ======================= J.Cvach === Lumi RUN# 487.......... Start lumi run487 date: 13/7/94 Collision time: 7:11:25 - 10:35:34 Currents (mkA): Ie= 21663.00, Ip= 31200.00 Peak luminosity: 1242.542 mb-1 s-1 Peak spec.lumi : 346.502396 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: 9605.493199 mkb-1 H1 Run total lumi: 8700.8221 mkb-1 H1 data taken lumi: 7296.9466 mkb-1 H1 Runs: 81600 - 81615 HERA - physics: 9349.078939 mkb-1 H1Run - physics: 8097.415492 mkb-1 H1data - physics: 6729.468975 mkb-1 H1 Runs: 81601 - 81615 Tot curr/rate factor: 0.47% C/R F H1Run gated: 0.49% Rand.C.F: 1.33% RCF Run gated: 1.37% Relative ET trigg accept.: 0.3439 PS.h01lns: L4 histos for this run# are OK, at least qualitatively. PS.h01lns: L5 histos for this run# are OK, at least qualitatively. 13.07.1994 ==================== H1KFOM === H1Lumi Dedicated Runs I found at H1DATA the next H1Runs which were recorded today as H1Lumi Dedicated Runs (first 2 Runs were written during F.Sefkow's prescale gap tuning procedure as temporary logged): At Full RunSummary (we can be shure that LREF and LRPF are presented at H1DataFlow) 81609 71 0 4FFFFFFF 940713 92712 940713 92806 4C524546:LREF 49 137 118 148 4C525046:LRPF 49 75 67 79 81610 25210 0 4FFFFFFF 940713 93052 940713 93536 4C524546:LREF 25072 137 106 148 4C525046:LRPF 25072 76 55 79 81611 324 0 320 940713 93555 940713 93605 4C524546:LREF 317 138 112 148 4C525046:LRPF 317 76 67 79 81611 52390 315 4FFFFFFF 940713 93605 940713 95232 4C524546:LREF 51902 138 109 148 4C525046:LRPF 51902 76 58 79 81612 66013 0 4FFFFFFF 940713 95319 940713 101301 4C524546:LREF 65412 138 106 148 4C525046:LRPF 65412 76 55 79 at Short RunSummary: RUN 81609 EVS 71 ( 0-4FFFFFFF) XI 202 B=11373 H1RAWD.C9401721 81609 TRG1-2,0-3: 9C0140 6000300 0 0 F8000000 0 RUN 81610 EVS 25210 ( 0-4FFFFFFF) XI 202 B=11373 H1RAWD.C9401721 81610 TRG1-2,0-3: 9C0140 6000300 0 0 F8000000 0 RUN 81611 EVS 324 ( 0- 320) XI 202 B=11373 H1RAWD.C9401721 81611 TRG1-2,0-3: 9C0140 6000300 0 0 F8000000 0 RUN 81611 EVS 52390 ( 315-4FFFFFFF) XI 202 B=11373 H1RAWD.C9401722 81611 TRG1-2,0-3: 9C0140 6000300 0 0 F8000000 0 RUN 81612 EVS 66013 ( 0-4FFFFFFF) XI 202 B=11373 H1RAWD.C9401722 81612 TRG1-2,0-3: 9C0140 6000300 0 0 F8000000 0 These data can be used for calibration too not only for e48-investi- gation and for zero pedestal status check. All Data were collected from 09:27:12 up to 10:13:01 during Lumi RUN #487. Ie total at this period was changed from 6.2 mA up to 5.0 mA. Ip total had value 31.0 mA all high mentioned time period. p- and e-gated H1Vetowall rates were ar level near 8 kHz. ET*PD-total rate was near 25kHz-->20kHz. Background ET*PD-trigger rate was estimated as near 10% of total rate VCrate was near was near 140kHz-->120kHz. Trigger bits s91-s95 with more or less equal quotas were sources of L2Keep-triggers (as it was agreed earlier). 13/7/94 ======================= J.Cvach === Lumi RUN# 488......... Start lumi run488 date: 13/7/94 Collision time: 12:52:00 - 13:29:19 Currents (mkA): Ie= 5742.00, Ip= 30901.00 Peak luminosity: 0.082 mb-1 s-1 Peak spec.lumi : 0.213316 mb-1 s-1 mA-2 Number of collided b.: 148 Number of e-filled b.: 163 Number of p-filled b.: 170 Number of e-pilot b.: 15 Number of p-pilot b.: 22 HERA total lumi: 3.313145 mkb-1 H1 Run total lumi: 2.655588 mkb-1 H1 data taken lumi: 2.639368 mkb-1 H1 Runs: 81626 - 81628 HERA - physics: 0.018157 mkb-1 H1Run - physics: 0.003858 mkb-1 H1data - physics: 0.003836 mkb-1 H1 Runs: 81628 - 81628 Tot curr/rate factor: 1.41% C/R F H1Run gated: 2.11% Rand.C.F: 0.09% RCF Run gated: 0.28% Relative ET trigg accept.: Not calc. 14/7/94 ============== P. Palmen F34PAL === Lumi RUN# 489......... Start lumi run489 date: 14/7/94 Collision time: 8:25:06 - 8:29:05 Currents (mkA): Ie= 3602.00, Ip= 31400.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.044305 mkb-1 H1 Run total lumi: 0.044305 mkb-1 H1 data taken lumi: 0.044051 mkb-1 H1 Runs: 81687 - 81687 HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 81687 - 81687 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. 14.07.1994 ==================== H1KFOM === LRTL-banks Missing Today morning at start of Lumi RUN# 490 it was fixed missing of LRTL-banks at H1DataFlow. After reboot of both FICs (between Run 81699 and Run 81700) LRTL banks alive again at H1DataFlow. Last LRTL-bank at H1DataFlow was fixed today morning at 06:09 - so no any information about unsuccesful Lumi RUN# 489 anywhere at H1 Data set. As seems it is needed to make SlowControl Alarm as it was made for FIC#1 or FIC#2 dead situation. Making of this alarm at L4-level is possible too but anybody who will make this alarm must be shure that LRTL-bank really must be presented at H1DataFlow (as example - LRTL-bank is suppressed at H1DataFlow for Ie=0 situation). 14.07.1994 ==================== H1KFOM === HV Trips at H1Lumi Today morning due to water leackage H1 Main magnet was set into Dump Condition. During Lumi RUN #490 (near 10:15) it was fixed its strong influence on e-beam orbit. As Yura said beam position was very far from standard (picture is drowed and kept). Rates of all sensitive to non-standard e-beam position were extremly high (as example - VetoWall fixed rate near 6 MHz). Our detectors were overloaded with super high rates too. As result - 4 HV trips at PD and 2 HV trips at ET Yura was at this moment at H1 Control Room and immediately reacted on this situation with HV ON again. During almost half hour this situation was presented at H1 IP. Near 10:45 Luminosity was fixed again at H1 IP but BG condition were bad. Specific Lumi is low. Analyze of LUMM-bank will show all single rates at this period at H1Lumi (VC,ET,PD etc.). 14.07.1994 ==================== H1KFOM === ZEUS vs H1 Lumi difference Yesterday H1 Run Coordinator said that there is proposal from ZEUS Run Coordinator to make some new steps on understanding of difference at ZEUS and H1 Lumi Measurements. He recommended to contact with ZEUS Lumi team and as detail as possible to check procedures of Current Luminosity calculation: Yesterday I sent mail to Uwe Schneekloth with proposal to find some contact person of this. This is his amnswer: "..... READMAIL message stored : THU, 14 JUL 94 11:24:30 MESZ Date: THU, 14 JUL 94 11:10:49 +0200 From: Uwe Schneekloth Subject: re: mail from h1kfom at dhhdesy3 To: Alexander Fomenko Uwe Schneekloth DESY F1 / ZEUS Notkestrasse 85 22603 Hamburg tel 004940/8998/2007 fax 004940/8998/3092 Hello Alexander, yes this was the reason I asked you for your luminosity of this run a few days ago. I gave your information to our lumi group. I think it would be useful if you talked to Danka Kisielewska or Krzystof Piotrzkowski to do a more thorough comparison of the online and offline numbers. I had actually suggested this to our lumi group. Regards, Uwe ...." 14.07.1994 ==================== H1KFOM === e25 problem At 11:50 Yura reported that he is looking for at two-dimensional xET vs yET on-line plot non-standard behaivour of e25-element. "e25-place" at plot is empty (it seems as HV at e25 is Off). HV was checked - all is OK. On-line tool shows enough large quantity of overflow situtaion at e25. LREC- LRPC- banks contents shows that calibration coefficient at e25 became less on factor near 2. And - as Yura reported - as seems always when e25 is main element at shower registration - it is overflowing. ET-trigger sum had additinal peak at high energy region. As first recept it is discussing decremention of HV at e25. Lumi tuning is made at this period. H1 Magnet is switching On. Yura made the decremention of HV at e25, tested it with test pulse, came back to old HV and as seems problem disappeared. 14/7/94 =============== P.Palmen F34PAL === Lumi RUN# 490 Start lumi run490 date: 14/7/94 Collision time: 9:23:26 - 13:04:54 Currents (mkA): Ie= 26268.00, Ip= 31400.00 Peak luminosity: 1808.168 mb-1 s-1 Peak spec.lumi : 472.44427 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: 7906.109278 mkb-1 H1 Run total lumi: 4642.4092 mkb-1 H1 data taken lumi: 2738.6805 mkb-1 H1 Runs: 81697 - 81706 HERA - physics: 7218.774562 mkb-1 H1Run - physics: 3949.398616 mkb-1 H1data - physics: 2106.628676 mkb-1 H1 Runs: 81700 - 81706 Tot curr/rate factor: 1.23% C/R F H1Run gated: 1.54% Rand.C.F: 28.92% RCF Run gated: 28.58% Relative ET trigg accept.: 0.3492 P.S. Problems with H1 Magnet ---> non-standard e-beam orbit --> HV trips at H1Lumi detectors ----> e25 problem ----> some period of incorrect Luminosity measurements (a.f.) At the finish of Lumi Run all became more or less OK. H1Runs were not written very long period before Lumi RUN finishing. H1 Main magnet was ON at the end of Lumi Run. PS.h01lns: WARNING: for #490 L4/L5 are "bad" at least from NRUN 81701: - Broad spectra for both E-differencies; - Overflows in ET,PD,VC (in ET at ch.25 or 26); - Broad spectra for ET+PD+VC @LUMI, both L4, and L5. 14.07.1994 ==================== H1KFOM === s92 new setting (E.Elsen) READMAIL message stored : THU, 14 JUL 94 15:24:22 MESZ Date: THU, 14 JUL 94 14:46:38 +0200 From: Eckhard Elsen Subject: re: s92 new setting To: Alexander Fomenko Eckhard Elsen H1 Collaboration, DESY - FH1K - Notkestrasse 85, 22603 Hamburg, Germany Tel. (040) 8998-2565 (secr. ext. 3144, fax 3093) Dear Sascha, yes you can go ahead with the redefinition of the trigger element LCal. I am oncall this evening and can even adjust the prescaling from home, if necessary. At the same time I shall adjust the prescaling for the other monitor triggers and will do this separately for phase 3 and 4. Could you please inform the shift crew to call me for the first lumi run after your change? Best regards, Eckhard 14.07.1994 ==================== H1KFOM === s92 new setting Today at pause between Runs 81715 and 81716 it was changed trigger setting of L_Cal H1Lumi Trigger element and connected with it subtrig ger s92 (one of 6 H1Lumi Monitrigs). Rates were checked before new setting and after: before (Hz) after (Hz) existing prescale Gap s91 0.23 the same 500000 s92 0.18 0.53 30000 s93 0.37 the same 500000 s94 0.32 the same 160000 s95 0.32 the same 100000 L_Cal now is PD&nVC (note - not PD1&nVC as it was proposed earlier). 14/7/94 ======================= Glazov === Lumi RUN# 491 Start lumi run491 date: 14/7/94 Collision time: 14:32:39 - 16:19:06 Currents (mkA): Ie= 22905.00, Ip= 30700.00 Peak luminosity: 1041.103 mb-1 s-1 Peak spec.lumi : 339.052804 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: 5263.027262 mkb-1 H1 Run total lumi: 4929.1852 mkb-1 H1 data taken lumi: 3640.4991 mkb-1 H1 Runs: 81711 - 81718 HERA - physics: 4318.416583 mkb-1 H1Run - physics: 3716.608541 mkb-1 H1data - physics: 2451.612354 mkb-1 H1 Runs: 81713 - 81718 Tot curr/rate factor: 0.57% C/R F H1Run gated: 0.54% Rand.C.F: 2.38% RCF Run gated: 2.41% Relative ET trigg accept.: 0.3590 P.S. Alexander Glazov (Nuclear Problems Laboratory, Dubna, now at Max Klien group at Zeuten, Link SW) - first person from JINR at H1 P.S.1 - this Lumi RUN is first Lumi RUN with new s92 setting PS.h01lns: L4 histos for this run# are OK, at least qualitatively. Overflows at ~2% in ET-16 and ET-26. PS.h01lns: L5 histos for this run# are OK, at least qualitatively. 14/7/94 ====================== J. Cvach === Lumi RUN# 492 Start lumi run492 date: 14/7/94 Collision time: 16:24:10 - 16:27:41 Currents (mkA): Ie= 1866.00, Ip= 30500.00 Peak luminosity: 110.685 mb-1 s-1 Peak spec.lumi : 364.437054 mb-1 s-1 mA-2 Number of collided b.: 150 Number of e-filled b.: 163 Number of p-filled b.: 170 Number of e-pilot b.: 13 Number of p-pilot b.: 20 HERA total lumi: 33.793062 mkb-1 H1 Run total lumi: 13.912341 mkb-1 H1 data taken lumi: 11.434195 mkb-1 H1 Runs: 81718 - 81720 HERA - physics: 20.097242 mkb-1 H1Run - physics: 13.912341 mkb-1 H1data - physics: 11.434195 mkb-1 H1 Runs: 81718 - 81720 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 0.25% RCF Run gated: 0.25% Relative ET trigg accept.: Not calc. P.S. this Lumi RUN was made with the same e-filling as it was at Lumi RUN# 491 after lost of large quota of e-beam. 14.07.1994 ==================== H1KFOM === ZEUS vs H1 Lumi difference SENDMAIL message Date: THU, 14 JUL 94 14:00:24 +0200 From: Alexander Fomenko Subject: ZEUS and H1 Lumi Measurements Difference To: Danuta Kisielewska A.M. Fomenko, DESY -FH1K- Notkestrasse 85, D 2000 Hamburg 52 Tel. (040) 8998-2568(121 1b),-4356(Hera Nord), -2433(125 1c) (permanent address: Lebedev Phys.Inst., Moscow, Russia) NODE: DHHDESY3 USERID: H1KFOM Hello, Dear Danuta, Yesterday H1 Run Coordinator recommended me to contact with ZEUS Lumi team (as it was proposed by ZEUS Run Coordinator yesterday) for attempts to understand difference at Current Luminosity measurements by ZEUS Lumi and H1 Lumi Monitors. Today I had e-mail contacts with Uwe Schneekloth and he recommended to contact with You and Krzystof Piotrzkowki. I am at DESY up to 31 July. From 16 up to 22 July I will be busy as H1 Shift Crew member. I am ready to get Your proposal on possible first steps of high mentioned activity. I am person who wrote program at FrontEndProcessor which calculates OnLine Current Luminosity values each 10 sec., collects Integrated Luminosity values (HERA produced, H1 Gated and H1 Data taken) and retranslates this values together with all needed values for Lumi recalculation or correction at OffLine into H1DataFlow. OffLine correction (if it is needed) is made by Sergey Levonyan. He is at Veksler's Memorial Conference at Dubna-Moscow now and after it up to 20 August will be at vacation at Moscow.He is accessible nevetheless through e-mail (F11LEV@DSYIBM.DESY.DE). I am waiting for Your reply. Sorry for long mail. Sincerely, Alexander Fomenko READMAIL message stored : THU, 14 JUL 94 17:31:50 MESZ Received: from VXDSYA.DESY.DE by DSYIBM.DESY.DE (IBM MVS SMTP V2R2.1) th TCP; Thu, 14 Jul 94 17:10:43 MET Date: Thu, 14 Jul 1994 17:10:40 +0100 From: KISIELEWSKA@vxdesy.desy.de Subject: Re: ZEUS and H1 Lumi Measurements Difference To: H1KFOM@DSYIBM.DESY.DE Dear Alexander, Thank you very much for your letter. Unfortunately I am living DESY July 18-th, but Krzysztof Piotrzkowski and our on line experts will be all the time here. We have got from Uwe your results from long run on July 9 th and realythe our values are higher about 15% for this time period. I think that at first we should have greater evidence for comparison. Could you please give us numbers or plots (luminosity, spec.luminosity, time period) for more runs. I prefer to meet you and organize some meeting our people with you at last week of July. If you will be at DESY sometime please give me a call(24-09, 32-04). I know where is your office. Best regards Danka P.S. S.Levonyan recommended to be presented at Danka's mentioned end of July meeting with team Y.Soloviev, N.Gogitidze and me(a.f) 14.07.1994 ==================== H1KFOM === ZEUS vs H1 Lumi (F11LEV) Sergey Levonyan recommended: "....... You have to compare L-Lsp behaivour in time in details ----- ^ This I did not recommed. What is L-Lsp? Just L_sp (S.L.) Also do we have a clear understanding of our own trig.eff. coeff. (sometimes as low as 0.8)? Look into one of the figures produced by Nelly (ratio of |x(ET)|_cut events to the corresponding B-H cross section. Ideally, it must be constant as a function of dx, but it is not, and typically, without cut it seems we underestimate lumi by ca. 5% (S.L.) 1) How exactly do they calculate it (formulas)? 2) time dependence/stability in H1 vs ZEUS IP It is not excluded also that 5-10% could be a real difference 3) How do they control online calibration stability and trigger thresholds behaivour? ......." P.S. L-Lsp means Current Luminosity value and Specific Luminosity value (I am sorry "L" was added by me after ZEUS-Lumi interest to both pictures). (a.f.) 14.07.1994 ==================== H1KFOM === Digits from Dedicated Runs It were prepared 3 data set for possible calibration from H1Lumi Dedicated Runs and nearest H1Runs (from Run 81607 up to 81213): H1KFOM.ETPDNVC.R81609.C00 39.3Mb 27928ev K39167 78048081 00001 ACS-E-C H1KFOM.ETPDVC.R81609.C00 55.1Mb 39101ev K40078 78048081 00001 ACS-E-C H1KFOM.S91.R81609.C00 57.0Mb 40573ev K40319 78048081 00001 ACS-E-C As it was found some days ago that this data can be read only at dice2- environment (but can be kept at DESY IBM).Jan Olsson explained possible reason of this situation. It were prepared 100th ntuples at the next LOOK binary data sets: H1KFOM.TLOOKQ2.R81607 FAST07 3010200E 00000 DASD H1KFOM.TLOOKQ3.R81607 FAST16 3010200E 00000 DASD H1KFOM.TLOOKQ4.R81607 FAST19 3010200E 00000 DASD All high mentioned ntuples were prepared with Relation Coefficients set with Global Energy Shifts constants and CCvcs which are kept now at H1DataBase. Bank LFRC 28 e-p data 407092325 80601 0 77 940709 H1KFOM Bank LESC 37 e-p data 407092325 80601 0 3 940709 H1KFOM The next digits it is possible to look for at these ntuples: Runs 81607- 81613 (ET&PD&nVC-sample - near 30K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 0 27.51 0.97 27.51 0.93 27.57 0.93 Runs 81607- 81613 (ET&PD&VC-sample - near 39K events) all events xetcut Step Mean Sigma Mean Sigma 0 27.51 1.26 27.51 1.25 P.S. As seems Sigmas at these energy distributions got non best values. May be its will be better after calibration with H1Lumi Dedicated Runs data. Shift at mean value at (xetcut&vcdepcut)cutted energy distribution for ET&PD&nVC-sample seems enough large (50 MeV). P.S.1 At L4/L5-histos which were printed by L.N.Shtarkov from Moscow on H01PS3 printer on my asking it were found the next digits from H1LumiDedicated Runs: Run 81611 : histo 40 (E_rec in LUMI ET+PD+VC) Mean Sigma Entries 27.48 1.13 28261 histo 18534 (ET+PD+VC for LUMI trigger) Edep as seems Mean Sigma Entries 26.35 1.38 27774 Run 81612 : histo 40 (E_rec in LUMI ET+PD+VC) Mean Sigma Entries 27.55 1.12 63712 (?)<-- as seems + Run 81611 histo 18534 (ET+PD+VC for LUMI trigger) Edep as seems Mean Sigma Entries 26.42 1.34 34903 P.S.2 preliminary estimated Global Energy Shift at 70th histo which are kept at the next LOOK binary data set: H1KFOM.BLOOKQ2.R81607 FAST07 3010200E 00000 DASD is near (-0.1)-(-0.3)+-0.6% and resolution is near 10-11%. As seems it is good result of existing at H1DataBase calibration constants. 14/7/94 ====================== J. Cvach === Lumi RUN# 493 Start lumi run493 date: 14/7/94 Collision time: 16:30:34 - 16:55:23 Currents (mkA): Ie= 1771.00, Ip= 30501.00 Peak luminosity: 98.298 mb-1 s-1 Peak spec.lumi : 346.329467 mb-1 s-1 mA-2 Number of collided b.: 147 Number of e-filled b.: 160 Number of p-filled b.: 170 Number of e-pilot b.: 13 Number of p-pilot b.: 23 HERA total lumi: 121.986785 mkb-1 H1 Run total lumi: 117.654117 mkb-1 H1 data taken lumi: 109.97237 mkb-1 H1 Runs: 81720 - 81721 HERA - physics: 101.698577 mkb-1 H1Run - physics: 96.373675 mkb-1 H1data - physics: 90.144068 mkb-1 H1 Runs: 81720 - 81721 Tot curr/rate factor: 0.25% C/R F H1Run gated: 0.26% Rand.C.F: 0.2% RCF Run gated: 0.2% Relative ET trigg accept.: Not calc. 14.07.1994 ==================== H1KFOM === Spike at CurrentLumiValue Today evening during start of Lumi RUN# 494 it was fixed (again during first measurement) spike at Current Luminosity value. It was fixed value 19 mkb-1s-1. Into H1 Gated and H1 Data Taken Integrated Luminosity values it were added 6.57 nb-1 and 6.70 nb-1(?) It is not understandable. As seems HERA produced value is OK. Time of this single 'measurement' is 22:22:09 14/07/94. 14/7/94 ============ J.Cvach,R.Starosta === Lumi RUN# 494 Start lumi run494 date: 14/7/94 Collision time: 22:22:25 - 22:41:29 Currents (mkA): Ie= 22000.00, Ip= 30000.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: 1111.011041 mkb-1 H1 Run total lumi: 7789.000055 mkb-1 <- must be decremented on 6700 H1 data taken lumi: 7482.149276 mkb-1 <- must be decremented on 6570 H1 Runs: 81761 - 81761 (a.f.) HERA - physics: 0 mkb-1 H1Run - physics: 0 mkb-1 H1data - physics: 0 mkb-1 H1 Runs: 81761 - 81761 Tot curr/rate factor: 2.02% C/R F H1Run gated: 2.02% Rand.C.F: 3.61% RCF Run gated: 3.61% Relative ET trigg accept.: Not calc. P.S. e-beam was lost. 14.07.1994 ==================== H01GOG === An old selection... A very old information is coming below ( better later then never!) I have selected the events of 24th class from MONITRIG cartridges: HERA03.H1POT2.MONITRIG.C9401234 ............................... HERA03.H1POT2.MONITRIG.C9401242 The following data set was prodused: H01GOG.H1LUMI.C1234242.A00 K27444 78048081 00001 ACS-E-C The selection of the events for ET&PD&VC and ET&PD&nVC triggers from this and previous data sets was also done: ET&PD&VC H01GOG.ETPDVC.C1186233.A00 K20636 78048081 00001 ACS-E-C H01GOG.ETPDVC.C1234242.A00 K11991 78048081 00001 ACS-E-C ET&PD&nVC H01GOG.ETPDNVC.C1186233.A00 L09664 78048081 00003 ACS-E-C H01GOG.ETPDNVC.C1234242.A00 K30193 78048081 00001 ACS-E-C 14.07.1994 ==================== H1KFOM === Incident Investigation Today it were fixed huge rates at all H1Lumi Trigger elements and trigger bits (we never looked for these rates). It was happened during Lumi RUN# 490. History (as it was possible to reconstruct it from Jan Olsson's Time Bcurrent Ie Ip Ee Ep ADCcounts mA mA GeV GeV 08:10:16 5456 22.9 31.4 15.7 820 ramping before Lumi RUN# 489 08:25:06 start of Lumi RUN# 489(nLRTL 08:29:05 stop of Lumi RUN# 489 start of Dump Condition H1Mg 08:56:13 4910 13.1 31.4 12.0 820 e-inj. before Lumi RUN# 490 08:56:51 4850 13.7 31.4 12.0 820 09:19:44 3273 26.7 31.4 19.3 820 ramping before Lumi RUN# 490 09:22:24 3152 26.4 31.4 27.5 820 09:23:26 start of Lumi RUN# 490 09:32:54 2576 24.8 31.4 27.5 820 start of Run 81699 (no LRTL) 09:45:04 1970 22.9 31.3 27.5 820 start of Run 81700 (LRTL on) 09:49:57 1788 22.1 31.3 27.5 820 start of Run 81701 10:04:41 1151 19.9 31.2 27.5 820 10:07:04 first 'huge' background start 10:19:25 636 17.7 31.1 27.5 820 10:25:14 485 16.7 31.1 27.5 820 10:30:56 333 16.2 31.0 27.5 820 10:34:02 212 15.8 31.0 27.5 820 10:35:00 stop 1st 'huge' BG conditions 10:41:13 90 14.9 31.0 27.5 820 10:46:27 stop of Run 81703 10:47:00 2nd 'huge' BG conditions 10:52:00 stop 2nd 'huge' BG conditions ??:??:?? stop of Dump Condition H1Mg ??:??:?? start Ramping Up H1Mg 11:29:56 121 8.1 30.9 27.5 820 start of Run 81705 11:30:59 272 8.1 30.9 27.5 820 11:32:00 3rd 'huge' BG conditions 11:37:00 stop 3rd 'huge' BG conditions 11:55:55 2394 6.8 30.9 27.5 820 start of Run 81706 11:59:55 stop of Run 81706 (last Run) 13:04:54 stop of Lumi RUN# 490 14:02:18 5456 8.2 30.7 12.0 820 e-inj. before Lumi RUN# 491 14:08:23 5456 12.3 31.4 12.0 820 start of Run 81710 14:32:39 start of Lumi RUN# 491 It were fixed 3 periods with 'huge' BG conditions due to some influence of H1 Main Magnet Dump Conditions and Ramping Up Conditions on 27.5 GeV e-beam orbit at H1 IP. 1) from 10:07 up to 10:35 (28 min.) 2) from 10:47 up to 10:52 ( 5 min.) 3) from 11:32 up to 11:37 ( 5 min.) The next Rate values of different H1Lumi trigger elements and trigger bits were fixed at LUMM bank during high mentioned periods with 'huge' background conditions: Trigger element/bit Maximal Rate Mean Rate VC 7.0 MHz 6.0 MHz PD 2.5 MHz 1.9 MHz ET 2.5 MHz 1.7 MHz PD1 2.7 MHz 2.1 MHz PD2 1.9 MHz 1.3 MHz ET&PD 1.7 MHz 0.9 MHz ET&PD&nVC 0.072 MHz 0.035 MHz PD&nVC 0.170 MHz 0.090 MHz eTAG 0.170 MHz 0.140 MHz These digits were got from Rates behaivours with time at 1st period. Less rates were fixed at another 2 periods (factor 2-4 less). I did not find any information about Lumi HV bad conditions at Jan's RunSummary. It means that may be trips are not fixed - only Off status or may be trips were happened during gaps between H1Runs. All vectors with behaivours of Rates with time it is possible to find at the next LOOK-binary data set: H1KFOM.LOOK.R81700 FAST12 3010200E 00000 DASD (see vectors 20000,30000,40000.50000,60000,70000,80000,90000 & 100000) t0=09:45:04 14.07.94 at all vectors. Time scale at min. Full scale near 135 min. (up to 11:59). Histos 11,21,30 and 40 show 'corrupted' energy distributions (ETrec, PDrec,VCdep and ETrec+PDrec). 15/7/94 ===================== P.Baranov === Lumi RUN# 495 Start lumi run495 date: 15/7/94 Collision time: 4:15:11 - 10:02:24 Currents (mkA): Ie= 19949.00, Ip= 29301.00 Peak luminosity: 1751.76 mb-1 s-1 Peak spec.lumi : 600.877088 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: 17189.494381 mkb-1 H1 Run total lumi: 14899.6088 mkb-1 + 911.0 mkb-1 (a.f.) H1 data taken lumi: 13284.0606 mkb-1 + 842.0 mkb-1 (a.f.) H1 Runs: 81824 - 81840 HERA - physics: 16286.702928 mkb-1 H1Run - physics: 14833.9377 mkb-1 H1data - physics: 13274.2234 mkb-1 H1 Runs: 81827 - 81840 Tot curr/rate factor: 0.4% C/R F H1Run gated: 0.39% Rand.C.F: 1.16% RCF Run gated: 1.14% Relative ET trigg accept.: 0.3368 P.S. H1 Gated and H1 Data Taken were dropped at 04:34 HERA Produced got NAN value at 05:34 PS.h01lns: L4-warning: L4 histos for this run# are empty(!), but: PS.h01lns: L5 histos for this run# are OK, at least qualitatively. Background above the usial for BS-spectrum at ~10 and ~20 Gev. 15.07.1994 ==================== H1KFOM === Integrated Lumi Problem.. Tonight (or today early morning) during Lumi RUN#495 it was fixed again negative jump at H1 Gated and H1 Data Taking. It happened at 04:34 between Run 81825 and 81827 - so all accumulated Integrated Lumi at Run 81825 was not added to values for H1Lumi Run Summary. H1 data taken - near 0.842 nb-1, H1 Gated on 7-10% more. Possible reason - crash of FIC#1-program at 04:32 - Luminosity appears dead. 15.07.1994 ==================== H1KFOM === NAN value at HERA produced Today it was record day with NAN value appearing at HERA produced Luminosity value: 1) at 05:34 during Lumi RUN #495 it was fixed first NAN-value - this value was corrected by Y.Soloviev at 08:40 with putting of value near 15.0 nb-1 into cell with address B0A5E13C with normalization coefficient accounting --> 1.5000e+20 (D2) 2) at 11:04 during Lumi RUN# 496 it was fixed NAN value at another cell connected with HERA Produced Lumi Calculation (C2). This value was corrected by me at 11:24 with putting of value near 1.5 nb-1 into cell with address B0A5E134 with accounting of normalization coefficient ---> 1.5000e+21 (C2) 3) at 12:05 during Lumi RUN# 496 it was fixed NAN value at same cell connected with HERA Produced Lumi Calculation (C2). This value was corrected by me at 12:13 with putting of value near 6.0 nb-1 into cell with address B0A5E134 with accounting of normalization coefficient ---> 6.0000e+21 (C2) It were made some attempts to find correlation of high mentioned HERA Produced values corruption with some activity at H1CDAQ: 1) Run 81830 (05:20-05:33:30) was stopped due to Muon Bus Error; Run 81831 (05:33:40 - 05:34:30) Muon TimeOut - No Start Run Prep.Ac Run 81832 (05:34:32 - 05:34:43) OK 2) Run 81845 (11:00-11:02:07) at 11:01:58 - First Stop or Abort Run Run 81846 (11:02:15 - 11:02:52) Calo Warm Start Needed Run 81847 (11:03:32 - 11:05:43) Warm Start Run 81848 (11:06:14 - 11:09:47) OK 3) Run 81852 (11:48-12:06:47) at 12:04:47 - Lumi dead at 12:05:03 - Lumi alive again (reboot) 15/7/94 ======================= burke === Lumi RUN# 496 Start lumi run496 date: 15/7/94 Collision time: 11:01:51 - 16:10:40 Currents (mkA): Ie= 21477.00, Ip= 28901.00 Peak luminosity: 1358.701 mb-1 s-1 Peak spec.lumi : 412.222743 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: 13592.954541 mkb-1 H1 Run total lumi: 12933.8134 mkb-1 H1 data taken lumi: 11109.1778 mkb-1 H1 Runs: 81845 - 81859 HERA - physics: 13592.619141 mkb-1 H1Run - physics: 12664.507944 mkb-1 H1data - physics: 10867.972083 mkb-1 H1 Runs: 81848 - 81859 Tot curr/rate factor: 0.4% C/R F H1Run gated: 0.4% Rand.C.F: 1.3% RCF Run gated: 1.23% Relative ET trigg accept.: 0.3471 P.S. twice it was corrupted HERA Produced Lumi value (see earlier) PS.h01lns: L4 histos for this run# are OK, at least qualitatively. Overflows ~ 1% at ET-15. PS.h01lns: L5 histos for this run# are OK, at least qualitatively. Background above the usial for BS-spectrum at ~10 and ~20 Gev. 15.07.1994 ==================== H01GOG === LUMIMON data processing Here is a continuation of a summary table (see message in LLO at 30.06.94) for the files processed till 15.07.94. ---------------------------------------------------------------------- File H1 runs Events Actual triggers (xx) s86 s91 s92 s93 s94 s95 ---------------------------------------------------------------------- 05 80293-80338 64959 5575 4809 3144 10032 5753 6041 06 80338-80525 65280 4661 4368 2757 8766 5150 5525 07 80525-80643 65370 5156 5061 3326 10236 5732 6207 08 80643-80679 64842 4635 4826 3200 9424 5864 6256 09 80679-80809 64936 4812 4565 3084 9615 5679 5728 10 80809-80898 65767 6296 4839 3066 10705 5572 6074 11 80898-80925 64780 4661 3888 2806 7811 5164 5215 12 80925-80944 64915 6089 4417 3144 9718 5739 5656 13 80944-81126 65698 5219 4825 2698 14721 4891 5301 14 81126-81164 65021 4474 4560 3062 10346 5636 5435 15 81164-81275 73277 133 167 129 315 241 211 16 81275-81280 73606 0 0 0 0 0 0 17 81280-81282 73606 0 0 0 0 0 0 18 81282-81284 73626 0 0 0 0 0 0 19 81284-81286 73639 0 0 0 0 0 0 20 81286 73629 0 0 0 0 0 0 21 81286-81353 75518 122 307 84 1455 127 174 22 81353-81490 65645 4104 4448 2595 10419 4719 5294 23 81490-81543 58502 4962 3905 2412 9760 4394 4735 24 81543-81610 59065 4441 5965 2451 11779 4419 4953 25 81610-81611 40593 0 16496 4591 24694 4591 6526 26 81611-81612 39707 0 13117 8708 9868 8708 8024 27 81612 39717 0 13178 8694 9832 8694 8026 28 81612-81701 52746 1545 8760 5178 10080 5932 6593 29 81701-81761 64084 3571 3636 3105 6082 4460 4586 Corresponding n-tuples NT(1) have been created. 15/7/94 ======================= andrieu === Lumi RUN# 497 Start lumi run497 date: 15/7/94 Collision time: 17:24:17 - 21:08:49 Currents (mkA): Ie= 18670.00, Ip= 28500.00 Peak luminosity: 711.249 mb-1 s-1 Peak spec.lumi : 246.227734 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: 9451.50971 mkb-1 H1 Run total lumi: 7921.2243 mkb-1 H1 data taken lumi: 5965.5311 mkb-1 H1 Runs: 81870 - 81883 HERA - physics: 9380.704095 mkb-1 H1Run - physics: 7707.881173 mkb-1 H1data - physics: 5828.895201 mkb-1 H1 Runs: 81871 - 81883 Tot curr/rate factor: 0.26% C/R F H1Run gated: 0.27% Rand.C.F: 1.2% RCF Run gated: 1.16% Relative ET trigg accept.: 0.3474 p.s. again NAN-value at HERA Produced Lumi was fixed at this RUN. NAN-value had appeared at 17:54. At 18:20 I put value 5.1nb-1 into C2-value with accounting of 10**12 scale factor - 5.1*10**11 Ordinary H1Run operated at this period without any 17:54 problems Run 81874 from 17:47:10 up to 18:03:40. Peak Lumi value (SHOWLUMI) = 1.2*10**30 cm-2s-1 PS.h01lns: L4-warning: Strongly decreased all N_Entries per run, but: L4 histos for this run# are OK, at least qualitatively. PS.h01lns: L5-warning: Strongly decreased all N_Entries per run, but: L5 histos for this run# are OK, at least qualitatively. 15.07.1994 ==================== H1KFOM === CC changing at Incident. Today it were checked online CC behaivours with time for Runs 81164- -81840 (LMONI- data sets 15-30) and found the next changes at CC values during yesterday proclaimed incident at 490th Lumi RUN. CCe21 was incremented on 18% CCp10 was incremented on 10% CCe22 was incremented on 35% CCp11 was incremented on 44% CCe23 was incremented on 30% CCp12 was incremented on 20% CCe24 was incremented on 27% CCp13 was incremented on 40% CCe25 was decremented on 45% CCp14 was incremented on 4% CCe26 was decremented on 25% CCe27 was incremented on 22% CCvcs was incremented on 60% Up to Run 81840 all CC were not come back to values before incident. Sigma at ETrec+PDrec histo became 1.02 GeV at OnLine (before incident Sigma was 0.93). Anybody can see behaivours CC with time at 10021-10027 and 20010-20014 ,20025 vectors at the next LOOK binary data set: H1KFOM.ZLOOKQ6.R81164 FAST16 3010200E 00000 DASD 16/7/94 ======================= andrieu === Lumi RUN# 498 Start lumi run498 date: 16/7/94 Collision time: 4:53:03 - 9:25:41 Currents (mkA): Ie= 22988.00, Ip= 30400.00 Peak luminosity: 1538.21 mb-1 s-1 Peak spec.lumi : 447.723486 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: 13096.167455 mkb-1 H1 Run total lumi: 11872.7057 mkb-1 H1 data taken lumi: 9397.4941 mkb-1 H1 Runs: 81901 - 81910 HERA - physics: 12175.24325 mkb-1 H1Run - physics: 10665.775535 mkb-1 H1data - physics: 8266.663213 mkb-1 H1 Runs: 81902 - 81910 Tot curr/rate factor: Not calc.% C/R F H1Run gated: Not calc.% Rand.C.F: 1.85% RCF Run gated: 1.53% Relative ET trigg accept.: 0.3326 PS.h01lns: L4-warning: Looking decreased all N_Entries per run, but: L4 histos for this run# are OK, at least qualitatively. Overflows ~1% for ET-15, not for the first RUN#. PS.h01lns: L5-warning: Looking decreased all N_Entries per run, but: L5 histos for this run# are OK, at least qualitatively. 16.07.1994 ==================== H1KFOM === H1 Lumi More then ZEUSLumi Today near 11:25 it was found that H1Lumi measured Luminosity value is more then ZEUSLumi measured one. It was happened after Luminosity tuning near 11:20 during Lumi RUN# 499. From 10:40 up to 11:10 it were fixed very bad BG-conditions at both interaction points. H1 Good Runs were started only at 11:22 after HERA produced Luminosity near 3.5nb-1. At 11:25 Lsp(H1) =4.6*10**29 cm-2s-1mA-2 Lsp(ZEUS)=4.0*10**29 cm-2s-1mA-2 H1 Shift Leader wrote this fact into H1 LogBook. But at 11:32 situation was changed: At 11:32 Lsp(H1) =4.4*10**29 cm-2s-1mA-2 Lsp(ZEUS)=5.0*10**29 cm-2s-1mA-2 16.07.1994 ==================== H01LNS === warning from Pitomnik ==== Warnings from the Site of Pitomnik: 1. For more than a week the Link to FIAN has been 'broken==slow_down':: - Working at the DESY-mashines is impossibly slow, - Not possible to work with LOOK via FIAN-then-sattelite, - Graphical access to DESY's from X-terminals does not work at all!!! - In particular, there were delays with L4/L5 work after RUN#489 (!). 2. Printing "from DESY" at our Printer at Pitomnik does not work, - Help Good, well known "Pasha" & Lvova have "cleaned" that Printer. 3. On Friday 16.07.94 the RISK WS stopped - as if Disk crashed again. 4. There were crashes with the "Wire Link". Help Good, Its working yet. PS: Request to our bosses - to spend more attention to Pitomnik Links. L.Shtarkov, Moscow, Pitomnik. 16.07.1994 ==================== H1KFOM === T_MonitorNC crash Today before start of Lumi RUN# 499 (a little before end of ramping) during attempt to push button "Detector Position" H1Lumi2 MacII was crashed. After rebooting it was proclaimed impossibility to work with current TMonitorNC-program and it was recommended to use BackUp-one. I made copy of BackUp-program and involved into operataion. HERA had received in time all needed info for Lumi tuning. It is 3rd case at H1DataDaking94 of this type TMonitorNC-program crash. 16.07.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.C9400015 L08613 78048081 00002 ACS-E-C HERA03.H01.LUMIMON.C9400021 L08726 78048081 00004 ACS-E-C ...... HERA03.H01.LUMIMON.C9400030 K40897 78048081 00001 ACS-E-C It were skipped data sets 16-20 which are filled with events for Neutron Counter investigation (H1Lumi Trigger Bit - NC was presented at this data sets - LRNA bank is absent - see S.Levonyan's message about BOS bank list at LUMIMON-data sets from 22.06.94). It were selected events with (s91=1 only),with ET&PD&VC=1 and with ET&PD&nVC from these data sets (as ordinary) from 631431 events: 1) S91=1 only 63638 events (137.0 MBytes) 2) ET&PD&VC 77347 events (167.6 MBytes) 3) ET&PD&nVC 66262 events (138.5 MBytes) At these data sets data from Runs 81164 up to 81840 are presented. Time period for this data samples - from 07.07.94 11:00 up to 15.07.94 10:00 (almost 8 days). These data samples include data from H1Lumi Dedicated Runs (81609- -81612). During collection of this data sets S92 trigger setting was changed (Run 81716). It is interesting that data from temporary logged Runs 81609-81610 are presented at this data sets (as I know at H1 MONITRIG data sets are presented only data from permanent logged h1Runs). As seems it is good. Selected data were written into the next data sets at DESY IBM (only for temporary keeping up to finishing of calibration procedures and only readable at dice2-environment and not readable at DESY IBM - see earlier message 14.07.94 "Digits.."). H1KFOM.ETPDNVC.M1530.C00 K25807 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M1530.C00 K25947 78048081 00001 ACS-E-C H1KFOM.S91.M1530.C00 K26000 78048081 00001 ACS-E-C Firstly it were selected H1Lumi Monitrig s92 with trigger setting PD&nVC which will be useful for Global Energy Shifts defining. These events were got only from last two last LUMIMON-data sets (29th and 30th) and only from data starting from Run81716. From 71235 LUMIMON- data it were selected 10305 of S92-triggered events. It means that S92 prescale gap was not tuned yet for new trigger setting and quota of this events at H1Lumi Monitrig sample enough large. Yesterday I received mail from E.Elsen at which he said that only yesterday evening he installed new prescale gap value for s92 and at the same time he made manipulation on decremention of all H1Lumi Monitrig at H1Data Flow. He asked me to test quantity ef needed for calibration events after installing of new prescale gaps and be shure that good base for permanent H1Lumi calibration is not destroed. S92-triggered events from Runs 81716-81840 are kept at data set: H1KFOM.S92.M2930.C00 K26272 78048081 00001 ACS-E-C 16.07.1994 ==================== H1KFOM === 1pb-1 HERA Produced Lumi Yesterday at 19:45 HERA-team announced that at this year HERA had produced 1.0 pb-1 of Integrated Luminosity. H1Lumi measured HERA Produced Lumi value is less on 12.7% then ZEUS. After end of Lumi RUN# 497 it was fixed value 0.873 pb-1 (21:08). 16/7/94 ======================= H1KFOM === Lumi RUN# 499 Start lumi run499 date: 16/7/94 Collision time: 10:29:48 - 16:06:25 Currents (mkA): Ie= 22919.00, Ip= 29600.00 Peak luminosity: 1504.101 mb-1 s-1 Peak spec.lumi : 422.510369 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: 12123.062076 mkb-1 H1 Run total lumi: 10984.4855 mkb-1 H1 data taken lumi: 9676.4454 mkb-1 H1 Runs: 81915 - 81931 HERA - physics: 11689.535253 mkb-1 H1Run - physics: 8268.632138 mkb-1 H1data - physics: 7340.580959 mkb-1 H1 Runs: 81921 - 81931 Tot curr/rate factor: 0.08% C/R F H1Run gated: 0.09% Rand.C.F: 1.28% RCF Run gated: 1.23% Relative ET trigg accept.: 0.3368 P.S. It was fixed period with H1Lumi more then ZEUSLumi (11:20). PS.h01lns: L4-warning: Looking decreased all N_Entries per run, Some of histos are empty, not understandable, but: L4 histos for the LAST NRun are OK, at least qualitatively. PS.h01lns: L5-warning: Looking decreased all N_Entries per run, but: L5 histos for the LAST NRun are OK, at least qualitatively. 16.07.1994 ==================== H1KFOM === Spikes at CurrentLumiValue Today evening at 19:50:37 it was fixed a little spike at Current Lumi- nosity value from 0.53*10**30 to 0.89*10**30 cm-2s-1 (Lumi RUN# 500). This spike is explained by spike at ET&PD total rate from 21 kHz to 36 kHz. Near 3.6mkb-1 'false' Integrated Lumi was added into Integral Lumi (HERA produced and H1 Gated). The next spike at the same Lumi RUN #500 was registered at 21:14:06 from 0.35*10**30 up to 0.60*10**30 cm-2s-1. 'False' additional innteteg rated Lumi value is estimated as 2.5mkb-1. At this case it was not registered any spikes at ET*PD total rate at this time. 16/7/94 ======================= andrieu === Lumi RUN# 500 (jubileum) Start lumi run500 date: 16/7/94 Collision time: 17:20:32 - 22:22:41 Currents (mkA): Ie= 21046.00, Ip= 25801.00 Peak luminosity: 1075.708 mb-1 s-1 Peak spec.lumi : 401.838649 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: 9857.484674 mkb-1 H1 Run total lumi: 9361.8982 mkb-1 H1 data taken lumi: 7938.7804 mkb-1 H1 Runs: 81936 - 81953 HERA - physics: 8859.062264 mkb-1 H1Run - physics: 8343.36184 mkb-1 H1data - physics: 6930.021665 mkb-1 H1 Runs: 81938 - 81953 Tot curr/rate factor: 0.15% C/R F H1Run gated: 0.16% Rand.C.F: 1.48% RCF Run gated: 1.47% Relative ET trigg accept.: 0.3306 P.S. Both beams were dumped after end of Lumi RUN# 500. PS.h01lns: L4-warning: Looking decreased all N_Entries per run, Some of histos are empty, not understandable, but: L4 histos for the LAST NRun are OK, at least qualitatively. L4-warning: Sometimes Overflows at ET-15 are ~10%(!). PS.h01lns: L5-warning: Looking decreased all N_Entries per run, but: L5 histos for the LAST NRun are OK, at least qualitatively. 17.07.1994 ==================== H01LNS === about L4/L5 comments ===== I have realized, that writting L4/L5-comments "in a style of "PS"" is sometimes inefficient - people do not look at the old Run-Summaries. Later I shall improove this comments writting, but now you can see these comments in the "bodies" of the relevant Run-Summaries. What was warned in the "last" LUMI-RUN#s (from the p.o.v. of L4/L5): THE N-ENTRIES ARE LOOKING AS IF STRONGLY DECREASED SOME TIME AGO (SEE); OVERFLOWS AT ET-15 ARE OFTEN ~1%, AND SOMETIMES ARE EVEN GREATER (SEE). And PS: I hope to write into LLO some explanations on "qualitatively". 17.07.1994 ==================== H1KFOM === NAN value at HERA produced Today it was fixed again Not-A-Number (NAN) -value at Hera Produced Luminosity value: - at 12:47 during Lumi RUN #501 it was fixed NAN-value - H1ShiftCrew called me by telephone and asked to correct this value - this value was corrected by me at 13:58 with putting of value near 6.5 nb-1 into cell with address B0A5E134 with normalization coefficient accounting --> 6.5000e+21 (C2) - the next manipulations were fixed at H1 Supervisor's Message Log at this period: 12:43:16 - Start of Run 81972 12:47:07 - Run stop sent to CDAQ 12:47:27 - First Stop or abort RUN (it means that somebody pushed Start Run button without waiting of Real Stop Run) 12:47:32 - Run 81972 Stoppped -------------------------------- 12:47:54 - Start of Run 81973 12:53:09 - Run stop sent to CDAQ 12:53:34 - Run 81973 Stoppped (as seems - no any correlations - only First Stop or Abort Run - this situation was fixed at previous NAN-case - see line 10341 at this LogBook - but it is almost impossible to image influence of this action on appearence of NAN-value at HERA-produced Lumi - but who knows - lets wait new NAN and fix all actions of H1ShiftCrew at this periods through H1 Supervisor Message Log). 17.07.1994 ==================== H1KFOM === D.Lueke's Proposals Dieter Lueke (Dortmund) was one of H1 Shift Crew member today. He proposes to have at room 301 (not at 307) large MacII screen with the same colour pictures as at HERA Control Room. Black/white screen as he said not so good for H1Shift crew. We had very long discussion about data flows which are now exist around H1Lumi MacIIs. He is shure that H1 Shift Crew must have fefore their eyes the same picture as HERA team (with the same window and pictures disposition). He said me that he will say with H1 Technical Coordinator about this. May be it is needed to install the same application as at HERA Control Room's MacII at any from disposed at r.301 MacIIs - at H1EventDisplay MacII may be additinal Large screen for one of the MacII at r.301 (H1 Central Trigger, H1 Slow Control, H1CDAQ-monitoring MacII) may be additional MacII with Large Screen etc. I put to him Usik's e-mail addresses for possible direct contact with responsible person for H1Lumi Presentation and Data Transfer. Let's see what will follow. 17.07.1994 ===== dice2 ======== H1KFOM === Relation CoefficientsSet4 Today it was made Relation Coefficient defining for data sample 4 - - data from H1Runs 81164-81840: a) it were excluded data from P-marked H1 Runs (see H1EP) and non- -marked with any P or M or G letters; b) it were excluded data from H1Lumi Dedicated Runs (81609-81612); After all high mentioned 'cleaning' of 4A-data sample it were collected 28830 events with ET&PD&nVC trigger 26980 events with ET&PD&VC trigger 16082 events with S91-trigger. It were got 28830 ET&PD&nVC from these Runs and it were used for calibration 17660 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 1.102 1.117 1.080 1.129 1.164 1.282 0.000 1.033 1.174 1.054 2.220 0.842 0.987 1.120 0.946 1.105 0.926 0.883 0.966 0.432 1.012 1.034 0.987 0.992 0.986 1.046 0.993 0.956 0.991 1.150 0.907 0.926 0.908 0.942 0.956 1.020 0.903 0.984 0.952 0.957 0.915 1.123 1.026 1.073 0.857 0.825 0.907 1.051 0.000 ==> Relation Coeff.Set for PD 2.073 0.934 1.074 1.547 0.978 0.963 1.027 1.032 0.982 1.024 0.981 1.053 1.045 1.044 1.018 1.173 0.993 0.995 1.015 1.116 1.556 0.959 0.965 0.981 0.000 ==> Sig. at Relation Coeff.Set for ET 0.000 0.000 0.000 0.000 0.001 0.012 0.000 0.000 0.003 0.011 0.030 0.000 0.006 0.009 0.025 0.014 0.038 0.022 0.089 0.010 0.025 0.020 0.028 0.029 0.024 0.068 0.033 0.015 0.033 0.029 0.035 0.022 0.015 0.025 0.018 0.010 0.017 0.017 0.014 0.016 0.004 0.033 0.000 0.015 0.007 0.017 0.005 0.003 0.000 ==> Sig. at Relation Coeff.Set for PD 0.008 0.033 0.060 0.007 0.000 0.039 0.059 0.033 0.029 0.021 0.045 0.048 0.018 0.044 0.027 0.032 0.064 0.030 0.026 0.036 0.002 0.018 0.034 0.028 0.000 ==> Ent. at Relation Coeff.Set for ET 1 7 2 1 8 10 0 5 7 5 9 1 3 6 1022 1383 489 230 254 20 126 5184 7739 5978 4639 3857 3241 1362 932 1060 372 466 462 415 381 15 15 17 33 37 23 16 1 11 9 11 13 6 0 ==> Ent. at Relation Coeff.Set for PD 20 13 14 16 1 290 2058 2593 594 56 1792 9144 13778 6417 730 333 2379 4591 2590 277 9 12 24 6 0 As You can see some of sigma values are enough large for some channels (p06,p10,p11,p13,p16 and e18,e25,e26). Runs 81164- 81840 (ET&PD&nVC-sample - near 29K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.48 0.99 27.47 0.95 27.48 0.94 Runs 81164- 81840 (ET&PD&VC-sample - near 27K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.35 1.39 27.45 1.34 It were used as start values of CC for Photoproduction branch ones which were produced after 3rd step of calibration with 3B sample of (Runs80601-81164) and CCvcs as 3.141. (from H1KFOM's 09.07.94 message at LLC). As seems it is needed to repeat calibraton with combined statistics from 3B-sample and part of 4th sample(up to incident at Lumi RUN#490). Something happened during incident with CC and with Relation Coeffici- ents. The rest of 4th sample must be combined with future data samples. 17.07.1994 ===== dice2 ======== H1KFOM === new sets of PDREC-spectra. Today it were produced 100th ntuple for S91=1 events from earlier mentioned 4 sample(Runs 81164-81840): H1KFOM.ZLOOKQ4.R81164 ( 7406 entries) FAST17 3010200E 00000 DASD Firstly it was prepared 100th ntuple for S92=1 events for events from Run 81716 up to Run 81164: H1KFOM.YLOOKQ4.R81164 (10229 entries) FAST17 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.R81164 1689 entries into 70h FAST08 3010200E 00000 DASD H1KFOM.BLOOKQ3.R81716 9095 entries into 70h FAST04 3010200E 00000 DASD First attempt to fit 70th histo at BLOOKQ2-data set shows that very poor statistics presents at 70th histo. First attempt to fit 70th histo at BLOOKQ3-data set put firstly another sign of Global Energy Shift at Photon Arm (+2.5%) and bad resolution digits (20-22%). As seems it is effect of statistics combining before incident and after. 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.R81164 FAST09 3010200E 00000 DASD H1KFOM.ZLOOKQ3.R81164 FAST08 3010200E 00000 DASD 17/7/94 ================= link, H1KFOM === Lumi RUN# 501 Start lumi run501 date: 17/7/94 Collision time: 12:39:36 - 18:07:52 Currents (mkA): Ie= 21400.00, Ip= 34200.00 Peak luminosity: 2042.914 mb-1 s-1 Peak spec.lumi : 529.178439 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: 14949.496276 mkb-1 H1 Run total lumi: 14472.9411 mkb-1 H1 data taken lumi: 11559.415 mkb-1 H1 Runs: 81971 - 81989 HERA - physics: 14501.096412 mkb-1 H1Run - physics: 13603.896693 mkb-1 H1data - physics: 10774.797143 mkb-1 H1 Runs: 81973 - 81989 Tot curr/rate factor: 0.09% C/R F H1Run gated: 0.09% Rand.C.F: 1.32% RCF Run gated: 1.3% Relative ET trigg accept.: 0.3361 P.S. NAN-value at HERA produced Lumi was fixed once during this Run (see earlier message). PS.h01lns: L4-warning: VC is as if Threshold mooved higher 0.5-1.GeV. Other L4 histos for this run# are OK, at least qualitatively. Overflows at ET-15 are ~ 0.6 - 1.%, other ch's are much less. PS.h01lns: L5 histos for this run# are OK, at least qualitatively. 17.07.1994 ==================== H1KFOM === NAN value at HERA produced Today it was fixed again Not-A-Number (NAN) -value at Hera Produced Luminosity value: - at 19:27 during Lumi RUN #502 it was fixed NAN-value - this value was corrected by me at 19:30 with putting of value near 0.9 nb-1 into cell with address B0A5E134 with normalization coefficient accounting --> 9.0000e+20 (C2) - the next manipulations were fixed at H1 Supervisor's Message Log at this period: 19:25:25 - Start of Run 81993 19:25:41 - Central Trigger Mode nonzero STC Calo 19:25:41 - Run 81993 Stoppped -------------------------------- 19:25:58 - Start of Run 81994 (Warm Start) 19:28:09 - Run 81994 Stoppped (Calo needs again WarmStart) -------------------------------- 19:30:00 - Start of Run 81995 (Warm Start) 19:31:09 - Run 81995 Stopped (OK) WarmStart situtaion was seen during appearence of NAN-value at previous evidence on correlation with activity H1CDAQ (see lines 7762 and 10343 at current LogBook). 17.07.1994 ===== dice2 ======== H1KFOM === Rel. Coeff. for Dedicated Today it was made Relation Coefficient defining for data sample from H1Lumi Dedicated Runs (81609-81612). Collection of sample consists of: 27963 events with ET&PD&nVC trigger 39131 events with ET&PD&VC trigger 40552 events with S91-trigger. It were got 27963 ET&PD&nVC from these Runs and it were used for calibration 17108 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 1.102 1.114 1.077 0.000 1.162 1.291 1.071 1.084 1.204 1.052 2.241 0.000 0.000 1.136 0.842 0.989 0.838 0.960 1.110 0.424 1.021 1.054 1.009 1.013 0.996 1.022 0.998 0.972 0.909 1.157 0.871 0.972 0.854 0.941 0.971 1.045 0.880 1.005 0.954 1.002 0.916 1.038 0.000 1.069 0.846 0.861 0.907 1.048 0.000 ==> Relation Coeff.Set for PD 2.132 0.965 1.024 1.541 0.000 1.076 1.096 1.025 1.048 1.053 0.962 1.037 1.030 1.033 1.003 1.062 1.078 0.981 0.989 1.056 1.557 1.033 0.974 1.003 0.000 ==> Sig. at Relation Coeff.Set for ET 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.014 0.005 0.000 0.010 0.000 0.000 0.000 0.004 0.009 0.008 0.004 0.004 0.001 0.005 0.010 0.014 0.011 0.013 0.006 0.008 0.006 0.003 0.008 0.019 0.009 0.008 0.007 0.006 0.003 0.000 0.003 0.004 0.004 0.000 0.000 0.000 0.000 0.004 0.001 0.001 0.000 0.000 ==> Sig. at Relation Coeff.Set for PD 0.000 0.002 0.004 0.001 0.000 0.004 0.009 0.008 0.012 0.001 0.007 0.010 0.010 0.012 0.006 0.005 0.009 0.006 0.005 0.004 0.000 0.008 0.001 0.000 0.000 ==> Ent. at Relation Coeff.Set for ET 2 6 1 0 3 3 2 2 7 6 7 0 0 2 474 427 239 330 365 11 111 4975 7688 5939 4583 3757 3126 1336 647 1225 318 557 366 310 338 13 9 12 17 18 7 3 0 7 5 9 8 1 0 ==> Ent. at Relation Coeff.Set for PD 19 8 16 16 0 230 2291 2909 609 35 1547 9729 13995 5445 351 211 2389 3836 1584 83 5 12 19 6 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 81607- 81613 (ET&PD&nVC-sample - near 28K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.48 0.93 27.46 0.93 27.49 0.91 Runs 81607- 81613 (ET&PD&VC-sample - near 39K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.46 1.26 27.46 1.23 It were used as start values of CC for Photoproduction branch ones which were produced after 3rd step of calibration with 3B sample of (Runs80601-81164) and CCvcs as 3.141. (from H1KFOM's 09.07.94 message at LLC). 17.07.1994 ===== dice2 ======== H1KFOM === PDREC-spectrum for Dedic. Today it were produced 100th ntuple for S91=1 events from earlier mentioned sample with H1Lumi Dedicated Runs (Runs 81607-81613): H1KFOM.ZLOOKQ4.R81607 (24224 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.BLOOKQ3.R81607 5169 entries into 70h FAST13 3010200E 00000 DASD First attempt to fit 70th histo at BLOOKQ3-data set put positive sign of Global Energy Shift at Photon Arm (+1.7%) and enough good resolution digits (11-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.R81607 FAST13 3010200E 00000 DASD H1KFOM.ZLOOKQ3.R81607 FAST05 3010200E 00000 DASD 17.07.1994 ==================== H1KFOM === Global Shifts,CCvcs Dedic. It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 0.983 for PD Channels (exept VCs), 1.014 for ET channels. Correction factor for CCvcs is 0.9963 So CCvcs = 3.141*0.9963=3.129Mev FADCcount. These digits are valid for H1Lumi events from Run 81607 up to 81613 Runs 81607- 81613(ET&PD&nVC-sample - near 28K events) xetcut&vcdepcut Step Mean Sigma 0 27.52 0.91 Runs 81607- 81613 (ET&PD&VC-sample - near 39K events) xetcut Step Mean Sigma 0 27.52 1.22 17.07.1994 ==================== H1KFOM === Spike at CurrentLumiValue Spike at Current Lumi value (Lumi RUN #502) was registered at 19:43:14 from 1.56*10**30 up to 2.37*10**30 cm-2s-1. 'False' additional integ- rated Lumi value is estimated as 8.1mkb-1. At this case it was not registered any spikes at ET*PD total rate at this time. Only single measurement was with this value. 18/7/94 ======================= H1KFOM === Lumi RUN# 502 ........ Start lumi run502 date: 17/7/94 Collision time: 19:05:00 - 0:17:33 Currents (mkA): Ie= 24800.00, Ip= 31300.00 Peak luminosity: 1676.158 mb-1 s-1 Peak spec.lumi : 453.695115 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: 15315.817508 mkb-1 H1 Run total lumi: 14346.0826 mkb-1 H1 data taken lumi: 11987.5159 mkb-1 H1 Runs: 81992 - 82007 HERA - physics: 14434.756897 mkb-1 H1Run - physics: 13178.86323 mkb-1 H1data - physics: 10930.824584 mkb-1 H1 Runs: 81996 - 82007 Tot curr/rate factor: 0.49% C/R F H1Run gated: 0.47% Rand.C.F: 1.48% RCF Run gated: 1.44% Relative ET trigg accept.: 0.3398 PS.h01lns: L4-warning: VC is as if Threshold mooved higher 0.5-1.GeV. Other L4 histos for this run# are OK, at least qualitatively. Overflows at ET-15 are ~ 0.6 - 1.%, other ch's are much less. PS.h01lns: L5 histos for this run# are OK, at least qualitatively. 18.07.1994 ==================== H1KFOM === ZEUS vs H1 Lumi Difference Today at 07:00 Temporary Access was announced at all HERA screens. It was started preparing of HERA e-ring for positron operation. HERA team had proclaimed HERA Produced Integrated values which were measured by H1 and ZEUS on moment 00:27 18.07.94. Difference is from 13.3% up to 15.2% (in dependence who is more right at Lumi measurements). #D=1994-07-18-09:11:19#K=HERATXT1#T=3#V=Temporary Access: 12-18h #U=#E= #D=1994-07-18-09:11:19#K=HERATXT2#T=3#V=H1: 938 nb-1, ZEUS: 1081 nb-1 #U=#E= #D=1994-07-18-09:11:21#K=READY #T=4#V=1994-07-18-09:11:21#U=#E= 18.07.1994 ==================== H1KFOM === New Position of ChGasCntr Today during Temporary Access into HERA tunnel it was made reinstal- lation of Cherenkov Gas Counter Prototype into new position (back side of ET, near 1.5 m far from IP then frontal side of ET). Reinstallation was made from 12:00 up to 14:00 by Yura Soloviev, Vova Andreev,A.S.Belousov and P.S.Baranov. Prototype was installed on special support which was prepared yesterday by Lev Gorbov and Yura Soloviev. Reinstallation geometry was got from recomendations of MC calculations which were made by Vova Andreev. At Wednesday when it is waiting first e+beam it will be possible to make first data collection with Mode1 for investigation of ChGasCntr behaivour at new position (HV was installed on 1800V). As seems it will be needed to put only PD into working position and to collect some data with VC and PD_Low triggers. May be before it (or after) it will be needed to collect some data with both detectors at Working Positions for first calibration with e+beam. 18.07.1994 ===== dice2 ======== H1KFOM === Relation Coeff.Set 3B+4A Today it was made Relation Coefficient defining for data samples 3B+4A - data from H1Runs 80601-81700 (all data before incident at Lumi RUN # 490): a) it were excluded data from P-marked H1 Runs (see H1EP) and non- -marked with any P or M or G letters; b) it were excluded data from H1Lumi Dedicated Runs (81609-81612); After all high mentioned 'cleaning' of 3B+4A-data samples it were collected: 71561 events with ET&PD&nVC trigger 68459 events with ET&PD&VC trigger 37058 events with S91-trigger. It were got 71561 ET&PD&nVC from these Runs and it were used for calibration 45022 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 1.102 1.123 1.080 1.138 1.148 1.249 1.096 1.037 1.194 1.101 2.286 0.857 0.994 1.117 1.041 0.981 0.939 0.927 1.074 0.466 1.030 1.040 1.037 1.025 1.025 1.053 1.036 1.013 1.060 1.045 1.028 0.984 0.996 1.051 1.049 1.013 0.939 1.087 0.976 1.031 0.929 1.040 1.020 1.070 0.878 0.869 0.958 1.056 0.000 ==> Relation Coeff.Set for PD 1.932 0.989 0.983 1.488 0.987 1.013 0.961 0.976 0.998 0.998 0.950 1.009 0.994 0.993 0.989 1.071 0.996 0.963 0.981 1.059 1.564 0.933 0.966 0.995 0.000 ==> Sig. at Relation Coeff.Set for ET 0.000 0.006 0.001 0.002 0.007 0.020 0.031 0.000 0.009 0.019 0.026 0.005 0.011 0.007 0.076 0.032 0.041 0.030 0.024 0.019 0.063 0.015 0.028 0.024 0.023 0.022 0.023 0.019 0.038 0.031 0.031 0.030 0.029 0.033 0.027 0.023 0.052 0.031 0.022 0.023 0.006 0.021 0.005 0.063 0.009 0.027 0.028 0.006 0.000 ==> Sig. at Relation Coeff.Set for PD 0.102 0.026 0.021 0.035 0.000 0.021 0.025 0.020 0.027 0.015 0.023 0.029 0.025 0.038 0.018 0.029 0.046 0.032 0.019 0.038 0.011 0.022 0.021 0.007 0.000 ==> Ent. at Relation Coeff.Set for ET 4 16 3 8 13 16 4 9 21 16 43 3 6 9 2383 1274 894 567 829 45 280 12847 20171 15184 11792 9949 8438 3626 2602 2186 1579 1413 1546 1456 1120 35 39 90 99 96 63 33 3 19 29 52 29 7 0 ==> Ent. at Relation Coeff.Set for PD 66 35 37 53 1 854 5727 9239 3284 232 3802 21665 35301 18290 2360 565 4738 8775 5784 642 26 30 48 15 0 As You can see all sigma values for 'hot' H1Lumi cahnnels RC histos have more or less reasonable values (may be p13 a little more then ordinary). Runs 80601- 81700 (ET&PD&nVC-sample - near 72K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.51 0.92 27.52 0.89 27.51 0.88 Runs 81164- 81840 (ET&PD&VC-sample - near 68K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.54 1.25 27.57 1.21 It were used as start values of CC for Photoproduction branch ones which were produced after 3rd step of calibration with 3B sample of (Runs80601-81164) and CCvcs as 3.141. (from H1KFOM's 09.07.94 message at LLC). 18.07.1994 ===== dice2 ======== H1KFOM === PDREC-spectrum for 3B+4A. Today it were produced 100th ntuple for S91=1 events from earlier mentioned 3B+4A sample with events from Runs 80601-81700: H1KFOM.ZLOOKQ4.R80601 (23842 entries) FAST16 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.BLOOKQ4.R80601 4010 entries into 70h FAST12 3010200E 00000 DASD First attempt to fit 70th histo at BLOOKQ3-data set put negative sign of Global Energy Shift at Photon Arm (-3.0%) and enough good resolution digits (14-15%). 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.R80601 71143 entries FAST08 3010200E 00000 DASD H1KFOM.ZLOOKQ3.R80601 64624 entries FAST04 3010200E 00000 DASD 18.07.1994 ==================== H1KFOM === Global Shifts,CCvcs 3B+4A It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 1.030 for PD Channels (exept VCs), 0.976 for ET channels. Correction factor for CCvcs is 1.031 So CCvcs = 3.141*1.031 =3.238Mev FADCcount. These digits are valid for H1Lumi events from Run 80601 up to 81700 Runs 80601- 81700(ET&PD&nVC-sample - near 72K events) xetcut&vcdepcut Step Mean Sigma 0 27.52 0.89 Runs 80601- 81700 (ET&PD&VC-sample - near 68K events) xetcut Step Mean Sigma 0 27.52 1.23 Test fit after accounting of correction factors for CCpd and CCvcs produced near zero Global Shift Constant value. 18.07.1994 ==================== H1KFOM === New RC Sets in H1DataBase As final action of all last calibration and recalibration 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: 17.07.1994 ----- dice2 -------- H1KFOM --- Rel. Coeff. for Dedicated 17.07.1994 -------------------- H1KFOM --- Global Shifts,CCvcs Dedic. 18.07.1994 ----- dice2 -------- H1KFOM --- Relation Coeff.Set 3B+4A 18.07.1994 -------------------- H1KFOM --- Global Shifts,CCvcs 3B+4A Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LFRC (_501) 29 e-p data 407182309 80601 81606 77 940718 H1KFOM 30 e-p data 407182322 81607 81613 77 940718 H1KFOM 31 e-p data 407182328 81614 0 77 940718 H1KFOM Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LESC (_582) 38 e-p data 407182309 80601 81606 3 940718 H1KFOM 39 e-p data 407182322 81607 81613 3 940718 H1KFOM 40 e-p data 407182328 81614 0 3 940718 H1KFOM 19.07.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.C9400015 L08613 78048081 00002 ACS-E-C HERA03.H01.LUMIMON.C9400021 L08726 78048081 00004 ACS-E-C ...... HERA03.H01.LUMIMON.C9400033 K13471 78048081 00001 ACS-E-C It were skipped data sets 16-20 which are filled with events for Neutron Counter investigation (H1Lumi Trigger Bit - NC was presented at this data sets - LRNA bank is absent - see S.Levonyan's message about BOS bank list at LUMIMON-data sets from 22.06.94). It were selected events with (s91=1 only),with ET&PD&VC=1, with ET&PD&nVC and with s92=1 only from these data sets (as ordinary): 1) S91=1 only 75960 events (156.0 MBytes) 2) ET&PD&VC 96395 events (199.1 MBytes) 3) ET&PD&nVC 82951 events (166.2 MBytes) 4) S92=1 only 25850 events ( 40.9 MBytes) (from 29-33 datasets) H1KFOM.ETPDNVC.M1533.C00 K21500 78048081 00001 ACS-E-C H1KFOM.ETPDVC.M1533.C00 K22086 78048081 00001 ACS-E-C H1KFOM.S91.M1533.C00 K21305 78048081 00001 ACS-E-C H1KFOM.S92.M2933.C00 K22122 78048081 00001 ACS-E-C 19.07.1994 ===== dice2 ======== H1KFOM === Relation Coeff.Set 4B Today it was made Relation Coefficient defining for data sample 4B - data from H1Runs 81701-81977 (all data after incident at Lumi RUN # 490): 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 4B-data samples it were collected: 24994 events with ET&PD&nVC trigger 25433 events with ET&PD&VC trigger 15674 events with S91-trigger. 23896 events with S92-trigger (after Run81716) It were got 24994 ET&PD&nVC from these Runs and it were used for calibration 14477 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 1.102 1.113 0.000 1.152 1.167 1.289 0.000 1.038 1.172 1.044 2.194 0.842 0.993 1.099 0.962 0.945 0.918 1.005 0.933 0.419 1.022 1.069 1.034 1.030 1.031 1.064 1.045 1.066 0.894 1.151 1.036 0.968 0.950 0.998 0.980 0.972 0.887 1.079 0.966 0.965 0.927 1.070 1.025 1.062 0.870 0.862 0.955 1.050 0.000 ==> Relation Coeff.Set for PD 2.061 0.957 1.108 1.512 0.980 0.943 0.989 0.984 1.051 0.995 0.944 1.002 0.987 1.001 0.961 1.043 0.929 1.007 0.982 1.119 1.552 0.930 0.914 0.965 0.919 ==> Sig. at Relation Coeff.Set for ET 0.000 0.004 0.000 0.000 0.000 0.001 0.000 0.000 0.001 0.004 0.002 0.000 0.003 0.003 0.009 0.006 0.032 0.017 0.018 0.003 0.005 0.016 0.026 0.030 0.023 0.046 0.037 0.024 0.011 0.007 0.006 0.004 0.015 0.013 0.011 0.000 0.012 0.002 0.008 0.011 0.004 0.002 0.000 0.002 0.002 0.003 0.012 0.000 0.000 ==> Sig. at Relation Coeff.Set for PD 0.041 0.012 0.014 0.007 0.000 0.008 0.020 0.020 0.017 0.008 0.023 0.026 0.026 0.034 0.012 0.010 0.014 0.026 0.027 0.016 0.001 0.005 0.011 0.003 0.000 ==> Ent. at Relation Coeff.Set for ET 1 4 0 1 4 7 0 3 3 5 6 1 3 5 531 740 301 198 234 13 87 4173 6371 4911 3905 3233 2724 1150 447 711 609 412 442 337 284 7 7 12 28 27 10 9 1 3 3 13 13 4 0 ==> Ent. at Relation Coeff.Set for PD 29 24 29 20 3 365 2924 4032 1273 81 1431 7825 11420 4901 478 161 1200 2438 1133 96 4 9 16 10 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 a little more then ordinary). Incident is incident. Something happened. Runs 81701- 81977 (ET&PD&nVC-sample - near 25K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.48 0.99 27.51 0.98 27.43 0.97 Runs 81701- 81977 (ET&PD&VC-sample - near 25K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.38 1.27 27.41 1.22 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 3B+4A sample of (Runs80601-81700) and CCvcs as 3.238. (from H1KFOM's 18.07.94 message at LLC). 19.07.1994 ===== dice2 ======== H1KFOM === PDREC-spectra for 4B Today it were produced 100th ntuple for S91=1 events from earlier mentioned 3B+4A sample with events from Runs 80601-81700: H1KFOM.ZLOOKQ4.R81701 ( 9295 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.R81701 1950 entries into 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 (-3.0%) and not very good resolution digits (18-22%). It was produced 100th ntuple with S92=1 events only from 4B sample of events (after Run 81716): H1KFOM.ZLOOKQ5.R81701 (21220 entries) FAST04 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.R81701 17031 entries into 70hFAST05 3010200E 00000 DASD First attempt to fit 70th histo at BLOOKQ3-data set put negative sign of Global Energy Shift at Photon Arm (-2.7%) and a little more good resolution digits (18-19%). 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.R81701 24866 entries FAST07 3010200E 00000 DASD H1KFOM.ZLOOKQ3.R81701 24039 entries FAST19 3010200E 00000 DASD 19.07.1994 ==================== H1KFOM === Global Shifts,CCvcs 4B It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 1.027 for PD Channels (exept VCs), 0.980 for ET channels. Correction factor for CCvcs is 1.0736 So CCvcs = 3.238*1.0736=3.476Mev FADCcount. These digits are valid for H1Lumi events from Run 81701 up to 81977 Runs 81701- 81977(ET&PD&nVC-sample - near 25K events) xetcut&vcdepcut Step Mean Sigma 0 27.52 0.96 Runs 81701- 81977 (ET&PD&VC-sample - near 25K events) xetcut Step Mean Sigma 0 27.49 1.23 Test fit after accounting of correction factors for CCpd and CCvcs produced near zero Global Shift Constant value. Calibration is made for all recorded up to now H1data. 20.07.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.07.1994 ----- dice2 -------- H1KFOM --- Relation Coeff.Set 4B 19.07.1994 -------------------- H1KFOM --- Global Shifts,CCvcs 4B Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LFRC (_501) 32 e-p data 407192142 81701 0 77 940719 H1KFOM Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LESC (_582) 41 e-p data 407192142 81701 0 3 940719 H1KFOM 20.07.1994 ==================== H1KFOM === Lumi Measurement Crisis . Yesterday it was fixed something as panic before Glasgow Conference due to Brinkmann's report at HERA Machine Meeting. These are messages from ZEUSBEAM and H1NEWS pinboards: "...... 0000426 = 94/07/19 = F01SNE ----------------------------- ZEUSBEAM == Summary of HERA Meeting 19.07.94 HERA continued luminosity running with reasonable efficiency until Monday morning. There was some down time because of problems with the He cryo system. The total delivered integrated luminosities are 1080 nb-1 and 938 nb-1 measured by the ZEUS and H1 luminosity monitors. This is all luminosity (online values) seen by the monitors including beam tuning and periods of unstable and bad background conditions. R. Brinkmann presented a study of the expected specific luminosities. Using the machine parameters, beta functions and beam emittances, and the vertical electron beam size measured by the luminosity photon detectors, the expected specific luminosities are 5.27*10**29 cm-2 s-1 mA-2 (H1) and 5.39*10**29 cm-2 s-1 mA-2 (ZEUS). Determining the beam size by scanning the electron beam accross the proton beam gives Lsp = 5.29*10**29 in both interaction regions. The specific luminosity measured by H1 and ZEUS was 4.18and 4.92*10**29 cm-2 s-1 mA-2. 001975 = 94/07/19 = H1KADR ---- LUMI ----------------------- H1NEWS = = Received by DHHDESY3 (H1NEWS)id 06833 19 JUL 20:03 from H1KADR@DHHDESY3 SUBJECT:LUMI C 19/07/94 407191937 MEMBER NAME LUMI (PHYSICS.) M FVS Note on the H1 lumi ------------------- Rumours are spreading that the H1 luminosity measurement is wrong by perhaps 20%. Therefore, some clarification: It is correct that the machine has done an exercise last weekend to determine the beam size in our interaction region. The result was that ZEUS and H1 apparently have the same beamsize (and hence are expected to see the same specific lumi). However there has been an outstanding difference of 10-15 % between the lumi claims of the 2 experiments sofar. From the machine exercise last weekend it appears that the problem could be the H1 measurement. This claim is at this stage not accepted by our experts. Checks are being done in order to get to understand this better. Note also that we have in our experement 4-5 different methods which determine the luminosity, giving agreement on the 5% level for the '93 data. E.g. one method (QED compton) does not use at all the lumi system. Also, our F2 would look rather unphysical when shifted by 15-20%. In all our people feel sofar still confident on their measurement for the 93 data. It is not excluded that, if a problem is present, it is related to the 94 data taking (Physics groups: check event rates/lumi unit for 93 and 94!!!!) Hence panic is at this stage premature, but caution is necessary. For the conference in Glasgow the F2 group decided to be cautious and quote an overall preliminary normalization uncertainty of 10% instead of 5%. This only untill the matter has been clarified,which will happen hopefully soon. A. De Roeck -------------------------------------------- Levonyan's Intervention . ICH70001I H1KFOM LAST ACCESS AT 14:37:10 ON TUESDAY, JULY 19, 1994 H1KFOM LOGON IN PROGRESS AT 15:35:01 ON JULY 19, 1994 MESSAGE FROM F11LEV SENT AT 19/07/94 1512 (WILL N O T BE PRINTED): Sorry, I was talking with 4 people together, and it was difficult to answer all of them. Just now Albert de Roeck called to FIAN and I explained him my point of view. 1) I do not believe in 1% accuracy of absolute L made by Brinkmann 2) for 1993 I am sure that our lumi is ok within 5% (3% too low online measurement, 3.3% correction in other direction due to the satellite bunches) 3) For this year I have only as a first estimate 7% too low from online (if calibration is OK) And again, satellite bunch correction for 1994 is larger: 4-8% (needs more study for precise value). 4) Whatever they tell us, we need as usual CORRECT OFFLINE CALIBRATION. Then I can cross check ET*PD method by PD-only. 5) There still can be REAL difference between H1 and ZEUS in average (Brinkmann made just ONE scan) 20.07.1994 ==================== F11LEV === Fomenko, please stop! .... Dear, Alexander, could I ask you: please stop copy to this logbook everything from everywhere! 1) Your private mails (with full addresses etc, increasing space) 2) Well known pinboards (H1NEWS etc.) - everybody have access to this information anyway. 3) Internal information, exchanged rather for the discussion and further thoughts, than for the wide distribution. etc., etc., etc. P.S. OK. (a.f.) 20.07.1994 ==================== H1KFOM === e+ injection attempts Today at 12:25 it were fixed first attempts of e+ injection into HERA e-ring. Ie total was fixed not more then 10 mkA. Only H1VetoWall e-Background was sensitive to these injections - some jumps at rates up to 2kHz were fixed. At 14:03 it were injected 3 bunches Ie+ total near 120 mkA. Life time was fixed near 5.9 hours.At 14:13 e+ beam was dumped or lost VC rates were seen at first 3 bunches. 20.07.1994 ==================== H01GOG === LUMIMON data processing Here is a continuation of a summary table (see messages in LLO at 30.06.94 and 15.07.94) for the files processed till 20.07.94. ---------------------------------------------------------------------- File H1 runs Events Actual triggers (xx) s86 s91 s92 s93 s94 s95 ---------------------------------------------------------------------- 30 81761-81840 64577 4116 4652 9379 7443 5342 4952 31 81840-81876 64649 4354 4443 9082 7685 5335 4773 32 81876-81921 65328 7501 4034 4144 5779 3410 4245 33 81921-81977 65383 7235 4229 2788 6165 2874 4419 34 81977-82322 65298 7632 4028 2667 5367 2801 4306 21.07.1994 ==================== H1KFOM === e+ injection attempts Today morning it was found that at HERA e-ring there is enough large 12 GeV e+ beam with Ie total near 8.1mA. e+ beam injection is in progress now. Life time of e+ beam is enough good - 4.8 hours. #D=1994-07-21-07:47:49#K=HEMAGEN #T=2#V=-1.19699826E1 #U=[GeV/c]#E= #D=1994-07-21-07:47:49#K=HPMAGEN #T=2#V= 0 #U=[GeV/c]#E= #D=1994-07-21-07:47:49#K=HESUCURR#T=2#V= 8.10000000E0 #U=[mA] #E= #D=1994-07-21-07:47:49#K=HPSUCURR#T=0#V= #U= #E= #D=1994-07-21-07:47:49#K=HESULIFE#T=2#V= 4.77500000E0 #U=[h] #E= #D=1994-07-21-07:47:49#K=HERATXT2#T=3#V= INJECTION #U=#E= 21.07.1994 ==================== H01LNS === a Point of view on Info == In connection with LLO 20.07.94 F11LEV, Sorry for being a little late: I am strongly against the S.Levonian's "asking" for A.Fomenko "to stop" and especially against stopping of "3) Internal information...",see up. I admit that S.L. is not so interested in this kind of info, as me, for if he were really interested, he had better propose something better. L.Shtarkov, Moscow, Pitomnik 21.07.1994 ==================== H1KFOM === First e+beam ramping Today near 10:00 it was firstly fixed e+ beam ramping up to 27.52 GeV energy. Ramping was succesful without lost of beam current. Ie+ total at 10:00 was near 24.5 mA.Now (11:40) Ie+total equal 14.47mA. Life Time is near 5.54 hours. Now 'Machine Studies' announcement exists at HERA TV screen. Movable Platforms at Working Positions from end of ramping. LUMM-banks from Run 82322 and latest Runs can show H1Lumi Trigger elements and bits Rates behaivours with time. It were fixed 3 stages at current e+ filling: a) bad Y-position (very far at high direction from center of PD); b) good beam position (10:27-10:37) c) "shifted" H1 IP (as seems) (10:37 up to now) - low ET*PD rates; At 'b'-period it were fixed more or less reasonable ET*PD and VC rates and its ratio. Only one strange effect was fixed - coordinate distri- bution at ET ( as seems population of statistics at right part of ET (nearest to e27)is less then we ordinary looked for with e-beam) May be it is evidence on another visible cross-section(?). Another effect was looked - population of statistics at ETcoordinate distribution at 'right' region is changed vice versa - if You remember we had population at up direction - now - at low. ==> This is very interesting. Do you know what was H1 mag.field status during this exercise? On? if yes, then the polarity? The same as in e-p case? (S.L.) Can you next time (or for this data, offline) plot x-y scatter plot at ET (XY, not HD) and send me together with LUMM data, I asked yesterday via Nelly? ==> P.S. H1 main Solenoid was ON. Nobody talked about H1 Main Magnet polarity changing for positron operation. I shall try to ask of H1 Run Coordinator. Really before today Magnet was Off - may be somebody made repolarity? ==> P.S.1 Yura had talk with Derek Darvill who is main responsible person for H1 Main Solenoid. He said that it was not changed polarity of H1 Magnet (it is very large work and this type of work must be proclaimed at some of meetings or pinboards or somewhere else) (a.f. 22.07.94) At 11:55 ET Movable Platform was put into Parking Position - Yura is investigating at on-line behaivour of e48. At 12:25 ET Movable Platform was put into Working Position again. 21.07.1994 ==================== H1KFOM === H1Lumi Dedicated Run Today it was decided to make first attempts to collect some data for Ch.Gas Investigation. It was decided firstly to get some calibra- tion data and after this - put ET into parking position and collect data with PD-Arm triggers for Ch.Gas Counter Investigation. Our plans were made only on 1/2. We got good sample for calibration but e+beam was dumped or lost at 13:21 and Runs with ET at down positi- tion were not recorded - so no any data for e48 investigation yet. As ordinary with HERA e-clock H1Lumi timing was changed on near 20 ns and it were changed FADC shifts for both subbranches: Lumi: ET(147-->149), PD(91-->93) Phot: ET(199-->201), PD(143-->145) It was installed Mode 1 for posibility to write LREF and LRPF banks. It was recorded Run 82343 with near 120K events with more or less equal quotas from all 6 H1Lumi Monitrigs. Run was written during c-phase (see earlier) and ET*PD rate had strange value for this type of e+beam current ( only near 1 kHz at the end of Run for example but VC rate was near 30 kHz). 21.07.1994 ==================== F11LEV === H1 LUMI measurement ..... Few remarks on the Brinkmann's scan result (16/07/94). 1) In general, the method and final figures look very clean and convincing. However, there might be several reasons for systema- tic errors in his result (see below). All of them seem to be of the order of 2-3%, but further clarification is needed to make a definite conclusion. Questions (could Yura ask Brinkmann on a,b,c,d?): a) how well a horisontal scale on B's figures is known? In other words, how precise is their device calibrated, which measure the beam deflection in IP? No systematics at all? I mean how do they know their units (is 1mm indeed 1mm and not e.g. 1.1mm?) So far an answer was: a precision of few %, but I understand this as a relative calibration, not an ABSOLUTE (cm) b) How well was a longitudinal adjustment of the beams during the scan (including possible non-zero angle of p-beam in IP)? c) L_sp (meas. in H1/ZEUS) was used for the comparison, where L(meas) L_sp = --------------- Sum{I(e)I(p)} Could it be that the denominator estimate was too high? E.g. because of the satellite p-bunches? (Note, that L_sp for satellites = 0.7*L_sp(IP), so if 10% of p-current is sitting in satellites, this gives 3% correction in the right direction) ==> Question: what was satellite structure during this scan? Large? Small? Typical? Please, check with K.Flamm or J.Lopez d) looking on the Brinkmann's figures I realized, that there is another difference between H1 and ZEUS behaviour. Namely, the maxima of L_sp for horizontal(x) and vertical(y) scans are the same in case of ZEUS (4.92*10^29) and different in case of H1 (4.2 and 4.0 * 10*29), where the difference is 5% What does this mean? Why the best adjustment is different in H1 by 5%? Unstable conditions? Or not the best tuning? e) Is this ep-run "typical" in a sence that H1 Lumi measurement was as usual? Remember, an accident during ep-run 490, when after huge rates seen by the Lumi Monitor the calibration and gain factors were screw up? Was there any significant influence on Lumi measurements after this (e.g. change of the effective trigger thresholds)? Therefore, I asked Fomenko to produce and send me this information (LUMM bank rates vs time for run 499 compared to others, especially before run #490) f) There is a remark in Brinkman's table for L_sp(H1): L_sp(L.Mon.)=4.18, "on-line 3-7% higher". Who knows what does it mean? 2) Facts. a) There is a permanent difference between H1 and ZEUS ONLINE (!) lumi measurement, of the order of 12%. This is true both for 1993 and 1994. Is this difference a real one, ore one of the experiments (or both) measure L systematically wrong? Brinkmann's result suggests, that H1 measurement is off by ca. 20% and ZEUS by ca. 6% b) In H1, for 1993 data we made several (partly) independent cross checks: PD-rate method (using lumi monitor events), Compton events (independent on Lumi Monitor), overlap method. All of them agree within 5-10% and definitely, no 12% under- estimate was found. Moreover, Compton method even gives lower value compared to the online measurement. c) It is also clear, that ET-acceptance calculation in MC is very sensitive to the beam conditions, so a priori expected ET*PD cross section taken from MC, may be wrong by +-10%. We decided therefore, to use real measured ET-acceptance for L measurement for physics. It is difficult however, to im- plement it online. d) There are other reasons for error in L measurement: - leakage over the ET boundaries (various |X_cut| subsamples can be and are used to control/estimate this effect) - trigger inefficiency/thresholds (found to be 1% in 1993, 3-6% in the beginning of 1994, and 2-2.5% in July'94) All together, in the first crude attempt it was estimated preliminary (see DQ meeting, 28/06/94) that H1 online L is of the order of 7% too low. e) To compare H1 vs ZEUS. For the future LUMI groups meeting (still in the agenda?): - compare background subtraction results in several ep-runs (including this famous #499). Is lumi_bgr/lumi_tot ratio similar in both experiments? - for 1993, do their final offline Lumi the same as online, no significant corrections? - did they try independent mathods (e.g. Compton events)? result? f) There is another well known effect: satellite bunches. This year, they amounts to 10% in several runs, but an average value is not known to me yet. This means, that finally for physics another correction has to be made, of the order of 3-8% in different direction. Therefore, it was decided to do all corrections together, once they are known and reliably estimated. 22.07.1994 ==================== H1KFOM === Rates History at #486,#499 It were processed TCL-data sets for preparing H1Lumi Trigger Elements and trigger bits Rates History at Lumi RUN# 486 and Lumi RUN# 499 (as it was requested by S.Levonyan). There are 2 LOOK binary data sets: H1KFOM.LOOK.R81589 Lumi RUN# 486 FAST13 3010200E 00000 DASD H1KFOM.LOOK.R81915 Lumi RUN# 499 FAST05 3010200E 00000 DASD There are families of vectors with rates history for different trig- ger elements and bits: 20000,20001,20002 - VC total, VC collided+pilot, VC pilot 30000,30001,30002 - PD total, PD collided+pilot, PD pilot 40000,40001,40002 - ET total, ET collided+pilot, ET pilot 50000,50001,50002 - PD1 total, PD1 collided+pilot, PD1 pilot 60000,60001,60002 - PD2 total, PD2 collided+pilot, PD2 pilot 70000,70001,70002 - ET&PD total, ET&PD collided+pilot, ET&PD pilot 80000,80001,80002 - ET&PDnVC total, ET&PD&nVC collided+pilot, pilot 90000,90001,90002 - PD&nVC total, PD&nVC collided+pilot, PD&nVC pilot 100000,100001,100002 - eTAG total, eTAG collided+pilot, eTAG pilot Vectors XX0001-family includes both - collided+pilot and pilot only (dott line) rates history. At first data set (Lumi RUN# 486) there are some periodical spikes at pilot rates behaivours - I do not know its nature. It must be understood. As seems spikes did not connected with real rates - may be problems with rate calculation at OnLine - may be HW(?). LUMM bank contents now is under study and investigations. Sorry for temporary misunderstanding of something at its contents. For me it was very unwaitable that our eTAG-trigger bit was almost non sensitive to Brinkmann's manipulation with e-beam during his measurements at Lumi RUN# 499. It means that very large percent of eTAG-triggered events has beam-gas nature. At vectors 100001 You can see that quoata of beam-gas events at eTAG-triggered events is very large. As seems after Lumi RUN# 490 (early mentioned incident) only VC-rate and connected with nVC rates were changed. There are no significant changing at ET&PD-rates which are basis for H1Lumi measurements. 22.07.1994 ==================== H1KFOM === HERA e+ beam activity Today early morning it was fixed e+ injection into HERA e-ring. Ie+ total max was fixed near 10 mA. Injection was fixed between 05:00 and 06:30 22.07.94. 22.07.1994 ==================== H01GOG === TCL cartriges ===== Here is an information concerning HERA03.H1TCL.C94000XX cartriges. I have started with tape C9400036. By this moment the last tape is C9400045. --------------------------------------------------------------------- Tape * Lumi * H1 * LOOK- Number * RUNs * Runs * files --------------------------------------------------------------------- C9400036 466-469 80688-80823 H01GOG.RLOOK.EP466 C9400037 469-474 80823-80944 H01GOG.RLOOK.EP469 C9400038 474-477 80944-81112 H01GOG.RLOOK.EP474 C9400039 477-480 81112-81250 H01GOG.RLOOK.EP477.N C9400040 480-482 81250-81419 H01GOG.RLOOK.EP480.N C9400041 482-486 81419-81593 H01GOG.RLOOK.EP482 C9400042 486-495 81593-81720 H01GOG.RLOOK.EP486 C9400043 495-498 81781-81908 H01GOG.RLOOK.EP495 C9400044 498-501 81908-81987 H01GOG.RLOOK.EP498 C9400045 501-502 81988-82184 H01GOG.RLOOK.EP501 -------------------------------------------------------------------- An information about previous runs one could find at Sergey's files : F11LEV.RLOOK.EPxxx 22.07.1994 ==================== H01GOG === Lumi Monitor Triggers After discussion, E.Elsen have reduced the rates of Lumi Monitor Triggers. At the table following below there are the values of prescale factors before and after reduction in phases 3 and 4 for each Lumi Subtrigger. ------------------------------------------------------------------- SubTrig. * Prescale * (Red.) * Prescale * (Red.) * factors (Ph3) * * factors (Ph4) * ------------------------------------------------------------------- s91 500000->1000000 (2) 500000 (-) s92 30000->180000 (6) 30000->90000 (3) s93 500000->1500000 (3) 500000->1000000 (2) s94 160000->500000 (~3) 160000->300000 (~2) s95 100000->200000 (2) 100000 (-) 22.07.1994 ===== dice2 ======== H1KFOM === Relation Coeff.Set R82343 Today it was made Relation Coefficient defining for H1Lumi Dedicated Run data sample. After selection it were produced the next numbers of events: 23649 events with ET&PD&nVC trigger 24454 events with ET&PD&VC trigger 20671 events with S92-trigger. It were got 23649 ET&PD&nVC from these Runs and it were used for calibration 14013 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 1.101 1.120 1.073 1.158 1.151 1.296 1.119 1.107 1.203 1.055 2.229 0.800 0.996 1.090 0.933 0.812 0.859 0.898 0.862 0.437 0.984 1.041 1.024 0.992 0.921 1.029 1.053 0.963 1.017 0.940 0.992 1.052 0.981 0.906 1.485 0.996 0.856 1.065 0.971 0.972 0.000 1.074 1.027 1.044 0.857 0.851 0.932 0.000 0.000 ==> Relation Coeff.Set for PD 1.965 0.885 1.019 1.459 0.983 0.978 1.055 0.978 0.990 0.993 0.915 1.002 1.037 1.045 1.022 0.930 1.409 1.013 1.037 1.074 1.599 1.033 0.950 1.005 0.917 ==> Sig. at Relation Coeff.Set for ET 0.000 0.001 0.000 0.000 0.003 0.001 0.000 0.005 0.001 0.002 0.002 0.000 0.000 0.002 0.005 0.008 0.037 0.006 0.012 0.002 0.006 0.009 0.007 0.009 0.012 0.011 0.011 0.014 0.010 0.006 0.008 0.013 0.000 0.000 0.001 0.002 0.001 0.001 0.000 0.000 0.000 0.000 0.000 0.001 0.000 0.000 0.000 0.000 0.000 ==> Sig. at Relation Coeff.Set for PD 0.001 0.006 0.004 0.012 0.000 0.003 0.010 0.011 0.005 0.002 0.010 0.010 0.010 0.009 0.006 0.016 0.014 0.006 0.004 0.003 0.001 0.000 0.007 0.001 0.000 ==> Ent. at Relation Coeff.Set for ET 2 19 3 10 51 30 7 21 29 13 27 6 4 2 2198 963 503 200 88 23 23 9019 10362 3661 1145 397 151 47 3946 1354 493 179 36 4 9 46 8 17 5 5 0 2 4 9 6 7 1 0 0 ==> Ent. at Relation Coeff.Set for PD 8 8 15 20 2 20 189 912 1191 160 195 2405 9156 10187 2723 50 902 4065 5123 763 2 6 13 18 1 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 82341- 82343 (ET&PD&nVC-sample - near 24K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.55 1.16 27.59 1.11 27.56 1.10 Runs 82341- 82343 (ET&PD&VC-sample - near 24K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.99 1.63 28.11 1.56 Sigma values are significantly more then at ep-Runs sample. It is possible to explain with another timing with HERA e-clock and using of another FADC shifts (see earlier). Luminosity Subbranch was not enough calibrated (we looked for at OnLine ETrec_PDrec histo for ET&PD&nVC events Sigma value near 1.98-1.96). CCvcs was changed significantly as seems (from ET&PD&VC-sample digits into more ow 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). 22.07.1994 ===== dice2 ======== H1KFOM === PDREC-spectrum for R82343 Today it were produced 100th ntuple for S92=1 events from earlier mentioned H1Lumi Dedicated Run with events from Runs 82341-82343: H1KFOM.ZLOOKQ4.R82341 (12177 entries) FAST16 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.R82341 11353 entries into 70hFAST04 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 not very good resolution digits (25-27%). 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.R82341 23319 entries FAST13 3010200E 00000 DASD H1KFOM.ZLOOKQ3.R82341 23137 entries FAST17 3010200E 00000 DASD 22.07.1994 ==================== H1KFOM === Global Shifts,CCvcs R82343 It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 1.010 for PD Channels (exept VCs), 0.986 for ET channels. Correction factor for CCvcs is 0.841 So CCvcs = 3.476*0.841=2.923Mev FADCcount. These digits are valid for H1Lumi events from Run 82341 up to 82343 Runs 82341- 82343(ET&PD&nVC-sample - near 24K events) xetcut&vcdepcut Step Mean Sigma 0 27.52 1.10 Runs 82341- 82343 (ET&PD&VC-sample - near 24K events) xetcut Step Mean Sigma 0 27.53 1.44 23.07.1994 ==================== H1KFOM === Dedicated Run samples For detail analyze of H1Lumi behaivour with first 27.52 GeV positrons at HERA e-ring it were got all LUMM-bank contents which were recorded on the next two H1RAWD-data sets: HERA04.H1RAWD.C9401902 B13687 78048081 00001 ACS-E-C HERA04.H1RAWD.C9401903 B13591 78048081 00001 ACS-E-C Data which were recorded at this data sets include the next Runs: Runs 82321-82361 (21.07.94 09:19:52 - 15:11:44) It was prepared 20000,30000,40000,50000,60000,70000,80000,90000,100000 vectors with behaivour with time different H1Lumi trigger elements and rates (VC,PD,ET,PD1,PD2,ET&PD,ET&PD&nVC,PD&nVC,eTAG). These vectors are kept at the next LOOK bibary data set. H1KFOM.LOOK.R82321 FAST04 3010200E 00000 DASD For calibration and another needs it were selected next data sets from high mentioned H1RAWD-data sets: A B C D E F 37560600 H1KFOM.ETPDNVC.R82341.A00 23649 23530 23317 ET&PD&nVC=1 38863440 H1KFOM.ETPDVC.R82341.A00 24454 24037 23168 ET&PD&VC=1 32765040 H1KFOM.S92.R82341.A00 20671 20539 12036 s92 only 49951440 H1KFOM.S86.R82341.A00 31568 25002 24529 s86 only 36618120 H1KFOM.S91.R82341.A00 23114 22712 11304 s91 only 46929960 H1KFOM.S93.R82341.A00 29676 29006 2566 s93 only A - data set size (bytes) B - data set name C - number of events D - number of events for Runs 82341-82343 (H1 Lumi Dedicated Runs) E - number of entries into 100th ntuple F - data sample trigger It were produced 100th ntuples for each from high mentioned samples with using of Relation Constants, CCvcs and Global Energy Shifts which were defined for H1Lumi Dedicated Run 82343. 100th ntuples are kept at the next data LOOK-binary data sets: H1KFOM.YLOOKQ2.R82341 ETPDnVC FAST17 3010200E 00000 DASD H1KFOM.YLOOKQ3.R82341 ETPDVC FAST04 3010200E 00000 DASD H1KFOM.YLOOKQ4.R82341 S92 FAST16 3010200E 00000 DASD H1KFOM.YLOOKQ5.R82341 S86 FAST01 3010200E 00000 DASD H1KFOM.YLOOKQ6.R82341 S91 FAST19 3010200E 00000 DASD H1KFOM.YLOOKQ7.R82341 s93 FAST07 3010200E 00000 DASD Some facts from view on these data: a) very low ET&PD acceptance (measured) - very good sample for under- standing why sometimes ET&PD rate too low (earlier we proclaimed that 'bad e-beam' or 'shifted H1 IP' or something else); b) very good sample for understanding - why sometimes ET-rate more (and significantly more) then PD-rate; c) this sample - one of possible explanation why sometimes there are so called ET&PD-inefficiency (not 100 % efficiency at some PDrec energy region - as seems - this is not 'trigger inefficiency' - this is not accounting of ACCC at attempts of acceptance measure- ment (trigger is good - but PhotonArm cannot see some photons due to collimator or another things at Photon way to H1Lumi Ph.Arm) d) good sample for investigation Xet,Yet plot for positrons at HERA e-ring (another populations at plot - vice versa etc.); e) at this sample it is possible to check VC-efficiency with PhArm energy and to be shure that 0.87-0.9 digits exist fir this value; f) it is possible to check Thresholds values for PD,PD2(eff.) etc. (preliminary PDthr=3.75 GeV, PD2=11.25 GeV); g) very interesting distribution - Xet vs ETrec - for eTAG sample. (more clear presence at plot of offmomentum positrons). h) etc. 23.07.1994 ===== #FIC1,2 ====== H1KFOM === H1LumiOnLine BackUp Files It was made procedure of BackUp-file producing at dice2-environment for H1LumiOnLineFIC1 and H1LumiOnLineFIC2 programs. There are 3 directory at /home/dice2/fomenko - directory: [dice2] fomenko $ ls -l total 85 drwxr-xr-x 2 fomenko h1 512 Jul 23 18:51 InfoFolder drwxr-xr-x 8 fomenko h1 512 Jul 23 14:07 ProgramForFIC1_H1CDAQ drwxr-xr-x 6 fomenko h1 512 Jul 23 16:09 ProgramForFIC2_LUMI First directory keeps executable modules H1LumiOnLineFIC1 and H1LumiOnLineFIC2 and all needed files for booting its into FIC's environments. It keeps files with DPM Memory Mapping. Second directory - full copy of H1Lumi MacII directory with program units for creating of H1LumiOnLineFIC1-program (exept object files). Lib1-Lib4 libraries are presented as binary backup files. Third directory - full copy of H1Lumi MacII directory with program units for creating of H1LumiOnLineFIC2-program (exept object files). Lib1-Lib6 libraries are presented as binary backup files. It was made (firstly) printing of all sources into paper (with a2ps-command - 4 pages per one A4-format). All printed sources will be kept at Room 1b-121 at one of the folders at our shelf. 23.07.1994 ==================== H1KFOM === HERA p-beam activity Today evening HERA p-beam alived again. It was injected near 4.0 mA p-beam and it was made ramping attempt. #D=1994-07-23-20:16:17#K=HEMAGEN #T=2#V= 0 #U=[GeV/c]#E= #D=1994-07-23-20:16:17#K=HPMAGEN #T=2#V= 6.89471848E1 #U=[GeV/c]#E= #D=1994-07-23-20:16:17#K=HPSUCURR#T=2#V= 3.89999999E0 #U=[mA]#E= #D=1994-07-23-20:16:17#K=HPSULIFE#T=2#V= 8.17375000E1 #U=[h]#E= #D=1994-07-23-20:18:39#K=HERATXT2#T=3#V= MACHINE STUDIES #U=#E= At 21;10 p-beam was dumped or lost (after achievement of more then 800 GeV energy). 24.07.1994 ==================== H1KFOM === HERA p-beam activity Tonight from 23:00 up to 06:00 it was made 4 attempts to inject protons into HERA p-ring. Ip total was fixed not more then 4 mA. 24.07.1994 ==================== H1KFOM === HERA p-beam activity Today after 16:00 HERA p-beam alived again. It was injected Ip total near 4 mA. 24.07.1994 ==================== H1KFOM === One-Element p11 Clusters Today it was found that p11-channel of PD-detector sometimes produces one-element clusters. S.Levonyan some weeks ago looked for this one-element clusters at sample of events PD_low when he tryed to find the reason of inefficiency ET&PD-triggered events (when top of PDrec-spectra for ET.eq.1 at sample PD_low did not 'touch' to PDrec spectra top line for all PD_Low events). Today due to Vova Andreev's investigation of possibility to use PD,PD1 and PD2 rates for Luminosity calculations it was found that at all samples connected with PD-triggers (PD_Low and especially PD&nVC) there are clear evidence of large quantity of one-element cluster at p11 (You can see Xpd and Ypd spectra and to be shure that there are spikes at spectra at X=2.0cm and Y=0.0cm). These spikes are produced only one-element cluster with p11. It was checked 100th ntuple with s86 as PD_low for Run73989 which was recorded 02 May 1994 before incrementing of HV at p11 (see LL8 03.05.94). At Run 73989 no any spikes at Xpd-spectra. It was checked 100th ntuple with s86 as PD_Low for Run74078 which was recorded 03 May 1994 (after HV changing at p11). There are high mentioned spikes at Xpd and Ypd distributions. It were checked 100th ntuple for H1Lumi Dedicated Runs - 81607-81612 and these spikes were found too (PD_Low sample). It were checked 100th ntuple for last H1Lumi Dedicated Runs - 82341- 82343 and these spikes were found too (PD_Low sample). As seems this problem (one-element p11 cluster) was born 02.05.94 after incremention of High Voltage at p11 on 50 V and exist up to now. There is question - why up to now nobody did not fix this problem? As seems due to next fact: at all 100th ntuples it were made xy-plots of Xpd vs PDrec and it was found that 'one-element' p11-clusters exist only for PDrec between 2-11 GeV - so for events ET&PD&nVC or ET&PD&VC which were good samples for beam profile check this effect is not seen (only PD_low triggered events and especially PD&nVC triggered events produce this 'one-element' clusters); As seems this effect had not influence on ET&PD-rates (or not significantly has influence) - so Luminosity measurements were right. Else one fact - for VC-triggered events this effect is not seen. Possible version of this behaivor of p11: - large response on little shower (for example 2Gev shower seems as 12 Gev) - it seems as large unlinearity at 2-12 Gev region. 25.05.1994 ==================== H1KSOL === P11 HV lowered ..... Today morning HV on PD11 el was lowered by 50 V i.e. to the previous value which was before 3.05.94 - 1740 V. 25.05.1994 ==================== H1KSOL === Meeting with Brinkmann After the discussion with Brinkmann I got the following answers on Levonian questions: a)there can be systematic uncertainties during measurements of beam position displaycement by correction coils but he expects this uncertainty of order 1-3%.He said they will do recalibration of correction coils before next scan. b) longitidual allignment of p-beam does not affect on this method if the angle is not 0 we will see less Lumi and on the other hand the effective beams cross section will be large. The formula for L_sp estimation is valid in this case. c) Unfortunately I did not find precise value of satellite bunches for this Lumi Run but after speaking with P.Newmann who was shift leader during scan it became clear that satellite bunches were at the level of 5-7% so ordinary value. On the other hand we overestimate Rates due to the presence of satellites so the correction seems to be even much smaller. d) the measurements started with vertical scan so it is just a bad luck of us that we had different values of maxima for Lumi for vert. and horiz. scan. If look at picture with hor. scan you will see that at 0 X beam position Lumi value is 3.9. f) "There is a remark in Brinkman's table for L_sp(H1): L_sp(L.Mon.)=4.18, "on-line 3-7% higher". Who knows what does it mean? " This remark seems to be was done during discussion with R.Felst,U.Straumann,A.De Roeck and W.Krasny. PS: There is also one point which can give about 10% correction for effective beam cross section measured by scan method and which can be applied only for coincidence method of Lumi measurement. ET acceptance depends on the e beam position in IP and if f.e. we had initial XOFF for e-beam = 0 relative to the reference orbit we will get ~10 % correction to the right direction. 25.05.1994 ==================== H1KSOL === VETOv got noisy........ First of all once more request to Lumi community: PLEASE DONT USE EDIT OF LUMI LOGBOOK IF YOU DONT INTEND TO WRITE ANYTHING BUT JUST TO INSPECT! In this case you force other people to write some messages at least twice,as it was in last case - I must to write this message second time. This morning it was found that VETOv got noisy (120 Hz rate without beams,before it was about 2-5 Hz). Such a behavior was observed earlier for the case of Machine Studies but increasing of rate was factor 2. Last increasing of rate was at about 12.00 yesterday from about 60 to 120 Hz (without any visible reason). So we must wait and watch the behaviour of VETOv. 25.07.1994 ==================== H1KFOM === HERA p-beam activity Tonight p-beam was injected into HERA p-ring twice - after midnight and after 03:30. Second filling was more succesful - Iptotal was fixed near 24 mA before ramping. Almost 1/2 of p-beam was lost during ramping and Iptotal near 13.3 mA lived at HERA p-ring up to 09:30. 26.07.1994 ==================== H1KFOM === HERA p-beam activity More or less large HERA p-beam exists now (12:50) at HERA p-ring Iptotal is near 35 mA. At 10:30 it was proclaimed "stable p-beam" announcement. This p-beam was injected today early morning near 04:30 and was succesfully ramped up without large lost of Ip total. 26.05.1994 ==================== F11LEV === To Brinkman's scan..... Yura wrote: PS: There is also one point which can give about 10% correction for effective beam cross section measured by scan method and which can be applied only for coincidence method of Lumi measurement. ET acceptance depends on the e beam position in IP and if f.e. we had initial XOFF for e-beam = 0 relative to the reference orbit we will get ~10 % correction to the right direction. My question: who has estimated these ~10% to ET-acceptance? I doubt, because a shift of a maximum of 0.3mm in hor. direction, at least according to MC, has very small effect. A change of 10% needs ~2mm shift... 26.07.1994 ==================== H1KSOL === Re:To Brinkmann's scan... Yes,shift of +-0.3 mm gave very small effect,but during scan the shift to the "-"region in HERA coordinate system (that corresponds to the "+"region in H1 coordinate system) was of value 0.5mm. The dependence of ET acceptance is more sharp in "+" region (H1 system of coord.) for examp. shift +0.5 mm gave about 6% decreasing of ET acceptance. What was done - I corrected the values of H1 Lumi on Brinkmann's picture for horiz. scan,most affected points were in the "-" region (in HERA system) and the "+" region stayed practically the same, the max. shift in this region is 0.3mm. Then I estimated the changing of effective beam cross section and it turned out that after corrections sigma* became value of 0.285 mm instead of 0.257 mm, so expected L_sp in H1 changed to 4.77 from 5.27. Of course this estimation is rough. Shift to "-" means in HERA system - inside of the ring. 26.07.1994 ==================== H1KFOM === Preparing e+ Injection It was proclaimed "preparing e+ injection" today evening. Early mentioned today early morning injected and succesffully ramped up and 'stable p-beam' announcemented HERA p-beam exists up to now at HERA p-ring. #D=1994-07-26-19:00:25#K=HEMAGEN #T=2#V= 1.19699826E1 #U=[GeV/c]#E= #D=1994-07-26-19:00:25#K=HPMAGEN #T=2#V= 8.19919813E2 #U=[GeV/c]#E= #D=1994-07-26-19:00:25#K=HESUCURR#T=2#V= 0 #U=[mA] #E= #D=1994-07-26-19:00:25#K=HPSUCURR#T=2#V= 3.46599999E1 #U=[mA] #E= #D=1994-07-26-19:00:25#K=HPSULIFE#T=2#V= 9.99900000E1 #U=[h] #E= #D=1994-07-26-19:00:25#K=HERATXT1#T=3#V= preparing e+ injection #U=#E= Near 21:00 announcement 'preparing e+ injection' was changed on 'stable p-beam' again. At 23:30 this p-beam was dumped. 27.07.1994 ==================== H1KFOM === HERA p-beam activity Today early morning at 04:30 injection of new p-beam was finished and this p-beam was succesfully ramped up to 820 GeV. Ip total near 40 mA. Life time is large (more then 100 hours). Now 'stable p-beam' announcement exists at HERA TV-screens (9:13): #D=1994-07-27-09:13:37#K=HEMAGEN #T=2#V= 1.19699826E1 #U=[GeV/c]#E= #D=1994-07-27-09:13:37#K=HPMAGEN #T=2#V= 8.19919813E2 #U=[GeV/c]#E= #D=1994-07-27-09:13:37#K=HESUCURR#T=2#V= 0 #U=[mA] #E= #D=1994-07-27-09:13:37#K=HPSUCURR#T=2#V= 4.03900000E1 #U=[mA] #E= #D=1994-07-27-09:13:37#K=HPSULIFE#T=2#V= 9.99900000E1 #U=[h] #E= #D=1994-07-27-09:13:37#K=HERATXT1#T=3#V=Stable proton beam #U=#E= 27.07.1994 ==================== H01LNS === My Lumi Questions to ZEUS= My Lumi Questions to ZEUS: 1.) The variety of Lumi Measurements: - The status of p-only and pe-coincidence methods - The status of On-line and Off-line measurements - The status of any complementory measurements - The status of Electon-Tagging for Photoproduction - ... 2.) The Data Flow of the Lumi Events: - Time Duration for Lumi-Sampling - System of Lumi-Triggers - Background Subtraction Procedure - The Values of Background(s) *) - Lumi Event Reconstruction - Lumi Event Format - Off-line Lumi Data Flow - ... 3.) The Kinds of Lumi Values Presentation: - Basic Definitions of Luminosity Values - Basic Definitions of HERA/ZEUS Runs *) - Lumi Values per different kind of Run *) - Lumi Values at different kinds of Gating *) - ... 4.) The Information that is available to H1: - The publicated materials on the ZEUS Lumi measurements - Reports on Lumi-ZEUS Technology, Hardware and Software - Any Information that is Computer Available to H1 - Any Information in a form of Log-files Available to H1 - Lumi Values per Run(s) that are Computer Available to H1 *) - ... PS: - My collection of questions is Draft, for I am short of time. - The Starred (*) questions are the most interesting for myself. - If some questions would be answered by LPI(!) expert(s) and are not to be questioned to ZEUS, I would like to recieve the relevant answers in any way, by personal mail or via LLO. L.Shtarkov, Moscow, Pitomnik. 27.07.1994 ==================== H1KFOM === Meeting with ZEUS Lumi Today from 10:00 up to 11:15 it was held meeting of ZEUS and H1 Lumi people at 1b-121. ZEUS Lumi team was presented by L.Suszycki and K.Pio- trzkowski.H1Lumi team was presented by Y.Solviev,V.Andreev, N.Gogitidze and me. L.Suszycki presented some digits from comparison of H1Lumi and ZEUS measured Luminosity and Specific Luminosity values at some time slices. He used our pictures which were prepared by Nelly with Lumi and SpLumi. There are difference from 16 up to 28 percents at some time slices. It was proclaimed that it is enough rough (from pictures) comparizon. At all presented time slices ZEUS Lumi was more then H1 Lumi. K.Piotrzkowski answered on question about cross checks Luminosity measuremnts at ZEUS (as I understood - there are no cross check with Compton events and with overlap method). There is some independent method with the same PhArm Rate Ideology but with using of different registration HW. There is no significant difference. K.Piotrzkowski at discussion about positive and negative sides of Photon Arm Rate method and Coincidence Rate method proclaimed the same '+' and '-' of both methods as it was proclaimed by S.Levonyan at Autumn'93 LPI meeting. He said that problem of calibration is solved (they have 1-2% changing of calibration constants during Lumi RUN with significamtly changed rates). New photomultipliers were installed before Start of HERA activity at 94. ZEUS Lumi channels became more stable with high rates. ZEUS Lumi did not look for so large changings at beam positions as H1 looked for at most of Lumi RUNs94 (Xpd had been changed up to 1 cm for 5-6 hours Lumi RUN). At most cases ZEUS OnLine Luminosity mainly is used for further using as final or official digits. Off-line corrections (2 different passes) are made but without significant influnce on Integral Results. Only some accidents with very high rates are corrected with sifnificant correction factors. Enough large part of time was put into discussion around Brinkmann's scan. Yura can write more detail about this discussion. As I understood they do not agree with conclusion of Brinkmann's that Luminosity at both IP of HERA is lower then it must be really. Both sides agreed that at future for each(!) Lumi RUN we shall exchange with ASCII-files with time slice per each minute of Lumi RUN with : time, Current Luminositu value, Specific Luminosity value, Beam Profile parameters, Ie values (total, pilots) which were used for calculations, Total and background rates of basic Lumi Measurements trigger (ET*PD for H1 and PD for ZEUS). These ASCII files will be send by mail to L.Suszycki into VAX from our side and ZEUS ASCII files will be send to our side - to one from contact persons. 27.07.1994 ===== #FIC1 ======== H1KFOM === H1LumiOnLineRelease It were made new release of H1LumiOnLineFIC1. Creation data/time are 27.07.94 14:57 for H1LumiOnLineFIC1. It were made only 2 changings (due to S.Levonyan's request): 1) it was made update of ReadOutEvent.f subroutines (assembler code) - CreateBanksLRPE_LRPF, CreateBankLRPE and CreateBankLRPF with hope that all will be ok with miniheaders at LRPE and LRPF-banks; 2) it was made update of InitConstant2.f subroutine with hope that all will be OK with miniheader at VETE-banks. Release was booted into FIC#1 near 15:10 today and will be tested after H1Run 82793. 27.07.1994 ==================== H1KSOL === ZEUS about scan... There are mainly two points which ZEUS Lumi consider as a week ones in Brinkmann's scan: 1. Measurements were made for displacement of e-beam of value +-1sigma or even less (f.e. for Y shift),and then a assumption was done that the shape is gaussian. 2.Brinkmann compared result of two methods and in the first one he assumed that the distribution of gamma beam shape is also gaussian and the width is proportional to 1/GAMMAe. That is not correct. And then he claimed that both methods gave the same results. But these corrections may will help ZEUS to understand the dicreapancy of their mrasurements compare to Brinkmann's ones,and not for us. 27.07.1994 ==================== H01GOG === ZEUS/H1 Lumi and Lumi_sp ZUES_LUMI people have compared the values of Lumi and Lumi_sp ( using only the plots we gave them ) for ZEUS and H1 measurements. They chose H1 Lumi Runs 466-469. ZEUS H1 ZEUS/H1 1Jul 14:30 L = 5.12 4.0 1.28 L_sp= 3.53 2.8 1.26 15:00 L = 4.19 3.6(*) 1.16 L_sp= 3.36 2.9 1.16 3Jul 2:00 L = 1.32 1.07 1.23 L_sp= 5.25 4.3 1.22 (*) - at this time it was the tuning and some jump of Luminosity value (it should be about 3.4 in fact, so the ratio would be about 1.23) 27.07.1994 ===== #FIC1 ======== H1KFOM === H1LumiOnLineRelease Test of today new H1LumiOnLineFIC1 Release was unsuccesful (during Runs 82794-82797)- it was fixed errors at BOS-structure of LRPE-banks. It were made new release of H1LumiOnLineFIC1. Creation data/time are 27.07.94 16:37 for H1LumiOnLineFIC1. It were made only 2 changings: 1) it was returned to old release of ReadOutEvent.f subroutines; 2) it was made update of OutBanks.f subroutine with hope that all will be OK with miniheader at LRPE-banks. Release was booted into FIC#1 near 16:39 today and will be tested after H1Run 82817.