C 2/06/93 607081222 MEMBER NAME EDITFILE (SAT.S) M *********************************************************************** * * * PART 13 PART 13 * * H1 LUMI LOGBOOK * * * * WINTER SHUT DOWN 1996 * * * * * * Enter command LLC under NEWLIB in order to add new information * * Press PF3 button when finish your editting to save the file. * * If you don't yet have LLC command defined, copy it from the * * 'F11LEV.CLIST(LLC)' into your clist member 'userid.CLIST(LLC)' * * * * Use command: F ===== to find all messages, and then select * * those you are interested in * * * * The following commands allow to inspect earlier logbook parts: * * * * LL1 ........ list Part 1 of the Lumi Logbook: Jun'91 - Aug'91 * * LL2 ........ list Part 2 of the Lumi Logbook: Aug'91 - Dec'91 * * LL3 ........ list Part 3 of the Lumi Logbook: Jan'92 - May'92 * * LL4 ........ list Part 4 of the Lumi Logbook: Jun'92 - Aug'92 * * LL5 ........ list Part 5 of the Lumi Logbook: Aug'92 - Nov'92 * * LL6 ........ list Part 6 of the Lumi Logbook: Nov'92 - Jun'93 * * LL7 ........ list Part 7 of the Lumi Logbook: Jun'93 - Nov'93 * * LL8 ........ list Part 8 of the Lumi Logbook: Nov'93 - May'94 * * LL9 ........ list Part 9 of the Lumi Logbook: May'94 - Jul'94 * * LL10........ list Part10 of the Lumi Logbook: Jul'94 - Nov'94 * * LL11........ list Part11 of the Lumi Logbook: Nov'94 - Apr'95 * * LL12........ list Part12 of the Lumi Logbook: May'95 - Jan'96 * * * * S.Levonian Opened: 30/01/96 at 15:00 * * Closed: 08/07/96 at 12:00 * * * *********************************************************************** 30.01.1996 ================= F11LEV === Warning! Chapter # 13 !! .... I was a bit reluctant to continue "LLO service" by two reasons: 1) Fast downgrading of IBM, which seems really to phase out, and on the other hand -- a possibility to use WWW, Unix news grops etc. in a more advanced way. 2) We reach a chapter number 13 ! However, the response on the proposal to stop Lumi logbook, was mostly negative, so we will continue. Keep your fingers crossed, that this "special" number does not bring to H1 lumi community a bad luck. You can inspect earlier parts by the commands LL1-LL12, where LL12 = LIST 'F11LEV.H1.LUMI.LOGBOOK.PART12' 31.01.1996 ================= F11LEV === VC in 95 and 96 ............. There were 2 Veto counters installed in 1995 in the photon arm: 1) A new "standard" 1X0 long (moving) -- for Veto and E measurement options, and 2) A small monitoring counter, just after the filter. According to Usik's drawings (see LUMI www-pages, "On-line news") the length of this second Veto = 6cm, which is additional ~0.23X0 of material. The questions: was it widely known, and taken into account properly everywhere? (At least not yet in H1SIM). What are the plans for 96 in that respect? Is anybody studying in all details a performance of the new Veto? 31.01.1996 ================= H01usa === VC in 95 and 96 (answer)..... It is not additional material (6 cm fixed water counter), because movabl e counter has now the smaller size. If take into account 4 counter walls (0.5 mm of Fe each) - it will be ~ the same 1 Xo. But of course it is mo re right to use in MC the new geometry precisely. All required data are available in mentioned www pages. PS (S.L.) Still, there is a non-negligible difference: Old scheme - 2.0 X0 (dead material) + 1.0 X0 (active VC) New scheme - 2.2 X0 (dead material) + 0.8 X0 (active VC) ==> a) min. E_gamma visible by the photon arm icreased from ~120 MeV to ?? (needs simulation; from the 2-gamma overlap probability seen in real 95 data it is ~150-180 MeV or. so) b) the overall E-resolution is different for the two schemes and a special study is necessary to show whether it became better (as it was atnicipated). 06.02.1996 ================= H1KFOM === Calibration Tests with LREC It were made calibration tests with LREC 7.00/03. Results are the next 1 2 3 4 6 7 -------------------------------------------------------------------- 1A 105252 27.48 0.886 5186 35.5 ----- H1 Main Magnet is Off ---------------------------------------- ----- at this time Huge rates at 17-18.06 were fixed at H1Lumi ----- 1B 108822 - - - - ----- at this time new timing was installed at H1 (H1CTRIG upgrade)- ----- H1 Main Magnet is ON ---------------------------------------- 1C 110407 27.48 1.335 825 8.0 ----- at this time new FADC shifts installed at H1Lumi ------------- 1D 111538 27.63 1.042 2295 38.8 ----- at this time selection of G+M H1Runs was made for calibration- 1E 112624 27.59 1.078 7706 57.0 ----- at this time new FADC shifts installed at H1Lumi (PhotonArm)-- 2A 113524 27.60 1.105 16175 70.6 ----- at this time Huge rates at 27.07 were fixed at H1Lumi -------- 2B 114471 27.59 1.184 8673 66.2 2C 115049 27.60 1.116 6914 58.8 3A 116309 27.55 1.132 6451 73.6 3B 117655 27.50 1.068 6083 82.1 3C 118020 27.60 1.082 10616 79.2 3D 118504 27.51 1.111 11258 83.0 3E 119318 27.52 1.092 25294 80.3 3F 119724 27.53 1.103 28975 76.5 ----- access with switching off HV at 301 room --------------------- 4A 120594 27.52 1.122 28001 77.0 4B 121497 27.51 1.098 31774 72.2 4C 122735 27.55 1.169 31421 72.6 4D 123443 27.51 1.144 26120 73.6 ----- access with making et01 as dead channel (ET44) --------------- 5A 124089 27.52 1.132 30058 69.7 5B 124868 27.53 1.120 33047 70.3 ----- access with switching off HV at 301 room (intervention ET32)-- 6A 126442 27.52 1.110 25883 81.7 6B 127007 27.53 1.109 24119 75.0 6C 128229 27.52 1.128 24517 74.1 ----- shifted vertex (+70cm) data ---------------------------------- 7A 129462 27.55 1.089 30216 682.8 7B 129645 27.50 1.117 28266 609.3 7C 129836 27.51 1.128 26871 425.4 ----- shifted vertex (-70cm) data ---------------------------------- 8A 129974 27.51 1.062 23006 645.5 8B 130146 27.39 1.058 21271 744.5 ----- nominal vertex ----------------------------------------------- 9A 130401 27.57 1.147 24250 84.6 :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: all samples together: 27.53 1.115 545254 where: 1 - sample 'name'; 2 - start H1Run of data sample for calibration; 3 - ETrec+PDrec spectrum mean value(LOOK peak finder, bins 200 22 32, abs(Xet)<6.0cm&|EVeto|<0.2GeV) - for ET&PD&nVC-sample (G+M H1Runs) 4 - ETrec+PDrec spectrum sigma value(LOOK peak finder,bins 200 22 32, abs(Xet)<6.0cm&|EVeto|<0.2GeV) - for ET&PD&nVC-sample (G+M H1Runs) 5 - Number of ET&PD&nVC-events at Data Sample (G+M H1Runs) (entries into mentioned at (3),(4) histos). 6 - Number of ETPDnVC events at G+M H1Runs per 1nb-1 Int.Lumi (H1DB) P.S. As seems calibration with sample 8B is not good (enough large difference betweeen 27.54 and 27.39GeV) (may be it is mistake during calibration or mistake with H1DataBase update for 8B). Mentioned analize was made with 100th n-tupel which is kept at next LOOK-binary set at DESY IBM: H1KFOM.LOOK.ETPDNVC.GM.F2252711 FAST10 3010200E 00000 DASD It's size is near 43 Mbytes (for example lread at dice2 gets 12 min of dice2 CPU). It's contents is next: NAM(1)='ETR' - ET32 reconsructed energy (GeV) NAM(2)='PDR' - PhotonArm reconstructed energy (GeV) NAM(3)='VCD' - VC deposited energy (GeV) NAM(4)='XPD' - Xpd of hit at PD (cm) NAM(5)='YPD' - Ypd of hit at PD(cm) NAM(6)='XET' - Xet of hit at ET32 (cm) NAM(7)='YET' - Yet of hit at ET32 (cm) NAM(8)='RUN' - H1 Run number 9999. values at ETR,PDR,VCD,XPD,YPD,XET and YET mean bad reconstruc- tion labels. Only G+M H1 Runs were got for making of this 100th n-tupel. 1340276 ETPDnVC events from G+M H1Runs 105288-131045 have entries into this 100th n-tupel. make Your own analize if You want with this interesting n-tupel. 07.02.1996 ================= F11LEV === Lumi-95 (offline analysis)... A note, describing all the details and the results of the offline luminosity-95 determination is finished and given to R.Eichler for proof reading. It must appear by the beginning of the next week as an official H1 note: N.Gogitidze, S.Levonian "An Offline Luminosity Determination for the 1995 H1 e+p data" (21 page, 11 figs., 7 tables) P.S.(8/02) A final draft (up to possible small English corrections) is available also on LPI SGI in the directory ~f11lev/papers/lumi95/lumi95.ps 09.02.1996 ================= H1KFOM === Calibration Tests with LREC It were made calibration tests with LREC 7.00/03. Results are the next 1 2 3 4 5 6 7 8 9 10 -------------------------------------------------------------------- 1A 105252 27.48 0.886 5186 35.5 27.46 1.041 10523 72.0 ----- H1 Main Magnet is Off ---------------------------------------- ----- at this time Huge rates at 17-18.06 were fixed at H1Lumi ----- 1B 108822 - - - - - - - - ----- at this time new timing was installed at H1 (H1CTRIG upgrade)- ----- H1 Main Magnet is ON ---------------------------------------- 1C 110407 27.48 1.335 825 8.0 25.13 1.757 1637 15.8 ----- at this time new FADC shifts installed at H1Lumi ------------- 1D 111538 27.63 1.042 2295 38.8 27.45 1.125 5415 91.6 ----- at this time selection of G+M H1Runs was made for calibration- 1E 112624 27.59 1.078 7706 57.0 27.52 1.153 14517 107.3 ----- at this time new FADC shifts installed at H1Lumi (PhotonArm)-- 2A 113524 27.60 1.105 16175 70.6 27.50 1.127 27454 119.9 ----- at this time Huge rates at 27.07 were fixed at H1Lumi -------- 2B 114471 27.59 1.184 8673 66.2 27.62 1.287 15275 116.5 2C 115049 27.60 1.116 6914 58.8 27.60 1.248 13661 116.1 3A 116309 27.55 1.132 6451 73.6 27.63 1.258 13808 157.6 3B 117655 27.50 1.068 6083 82.1 27.67 1.218 12410 167.4 3C 118020 27.60 1.082 10616 79.2 27.60 1.111 22754 169.8 3D 118504 27.51 1.111 11258 83.0 27.59 1.188 21853 161.0 3E 119318 27.52 1.092 25294 80.3 27.58 1.145 44562 141.4 3F 119724 27.53 1.103 28975 76.5 27.57 1.182 55942 147.8 ----- access with switching off HV at 301 room --------------------- 4A 120594 27.52 1.122 28001 77.0 27.59 1.190 58831 161.7 4B 121497 27.51 1.098 31774 72.2 27.55 1.183 64674 147.0 4C 122735 27.55 1.169 31421 72.6 27.54 1.194 62810 145.0 4D 123443 27.51 1.144 26120 73.6 27.58 1.199 52017 146.5 ----- access with making et01 as dead channel (ET44) --------------- 5A 124089 27.52 1.132 30058 69.7 27.59 1.178 60408 140.1 5B 124868 27.53 1.120 33047 70.3 27.53 1.206 66669 141.8 ----- access with switching off HV at 301 room (intervention ET32)-- 6A 126442 27.52 1.110 25883 81.7 27.57 1.196 47567 150.1 6B 127007 27.53 1.109 24119 75.0 27.58 1.210 46038 143.2 6C 128229 27.52 1.128 24517 74.1 27.56 1.193 47186 142.5 ----- shifted vertex (+70cm) data ---------------------------------- 7A 129462 27.55 1.089 30216 682.8 27.54 1.159 40305 910.7 7B 129645 27.50 1.117 28266 609.3 27.54 1.167 44842 966.6 7C 129836 27.51 1.128 26871 425.4 27.59 1.206 96208 1523.0 ----- shifted vertex (-70cm) data ---------------------------------- 8A 129974 27.51 1.062 23006 645.5 27.67 1.164 32726 919.1 8B 130146 27.39 1.058 21271 744.5 27.56 1.151 30565 1070.0 ----- nominal vertex ----------------------------------------------- 9A 130401 27.57 1.147 24250 84.6 27.57 1.207 59185 206.5 :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: all samples together: 27.53 1.115 545254 27.57 1.186 1069872 where: 1 - sample 'name'; 2 - start H1Run of data sample for calibration; 3 - ETrec+PDrec spectrum mean value(LOOK peak finder, bins 200 22 32, abs(Xet)<6.0cm&|EVeto|<0.2GeV) - for ET&PD&nVC-sample (G+M H1Runs) 4 - ETrec+PDrec spectrum sigma value(LOOK peak finder,bins 200 22 32, abs(Xet)<6.0cm&|EVeto|<0.2GeV) - for ET&PD&nVC-sample (G+M H1Runs) 5 - Number of ET&PD&nVC-events at Data Sample (G+M H1Runs) (entries into mentioned at (3),(4) histos); 6 - Number of ETPDnVC events at G+M H1Runs per 1nb-1 Int.Lumi (H1DB) which were used for final calibration steps (after Xet and Eveto cuts); 7 - ETrec+PDrec spectrum mean value(LOOK peak finder, bins 200 22 32, abs(Xet)<6.0cm - for ET&PD&VC-sample (G+M H1Runs); 8 - ETrec+PDrec spectrum sigma value(LOOK peak finder,bins 200 22 32, abs(Xet)<6.0cm - for ET&PD&VC-sample (G+M H1Runs); 9 - Number of ET&PD&VC-events at Data Sample (G+M H1Runs) (entries into mentioned at (7),(8) histos); 10 - Number of ETPDVC events at G+M H1Runs per 1nb-1 Int.Lumi (H1DB) which were used for final calibration steps (after Xet cuts); P.S. a) for ET&PD&nVC-samples: --------------------- 1) As seems calibration with sample 8B is not good (enough large difference betweeen 27.54 and 27.39GeV) (may be it is mistake during calibration or mistake with H1DataBase update for 8B). 2) Mentioned analize was made with 100th n-tupel which is kept at next LOOK-binary set at DESY IBM: H1KFOM.LOOK.ETPDNVC.GM.F2252711 FAST10 3010200E 00000 DASD It's size is near 43 Mbytes (for example lread at dice2 gets 12 min of dice2 CPU). It's contents is next: NAM(1)='ETR' - ET32 reconsructed energy (GeV) NAM(2)='PDR' - PhotonArm reconstructed energy (GeV) NAM(3)='VCD' - VC deposited energy (GeV) NAM(4)='XPD' - Xpd of hit at PD (cm) NAM(5)='YPD' - Ypd of hit at PD(cm) NAM(6)='XET' - Xet of hit at ET32 (cm) NAM(7)='YET' - Yet of hit at ET32 (cm) NAM(8)='RUN' - H1 Run number 9999. values at ETR,PDR,VCD,XPD,YPD,XET and YET mean bad reconstruc- tion labels. Only G+M H1 Runs were got for making of this 100th n-tupel. 1340276 ETPDnVC events from G+M H1Runs 105288-131045 have entries into this 100th n-tupel. make Your own analize if You want with this interesting n-tupel. b) for ET&PD&VC-samples: --------------------- 1) As seems calibration with sample 3B and 8A are not good due large difference betweeen 27.54 and 27.67GeV) (may be it is mistake during calibration or mistake with H1DataBase update for 3B,8A) 2) VCs signal was absent at 1C-sample (see LL12 messages); 3) Mentioned analize was made with 100th n-tupel which is kept at next LOOK-binary set at DESY IBM: H1KFOM.LOOK.ETPDVC.GM.F2252711 FAST10 3010200E 00000 DASD It's size is near 44 Mbytes (for example lread at dice2 gets 12 min of dice2 CPU). It's contents is the same as high mentioned 100th n-tupel for ETPDnVC events. Only G+M H1 Runs were got for making of this 100th n-tupel. 1388580 ETPDVC events from G+M H1Runs 105288-131045 have entries into this 100th n-tupel. make Your own analize if You want with this interesting n-tupel. 13.02.1996 ================= F11LEV === Online Lumi-96 ............ After several discussions recently at DESY with various people, it become more and more clear, that majority of H1 tends to "vote" for a single photon method to be used also online (i.e. single PD-rate). There could be two possibilities: 1) To start lumi runs (at high rates) with the coincidence method, and switch to the photon method "on fly", during stable period. This proposal was not strongly supported however. 2) Another possibility - try to parametrize photon arm trigger response (threshold) as a function of most important parameters, such as a global rate for example. This looks better for most of people concerned. Therefore, be prepared to the official request from Biddulph. It may come late, and no time will left for playing around, so begin all necessary preparations NOW. 14.02.1996 ================= H1KFOM === Calibration Tests with LREC It were made calibration tests with LREC 7.00/03. Results are the next 1 2 3 4 5 6 7 -------------------------------------------------------------------- 1A 105252 -0.50 15-21 6-22 4371 29.9 ----- H1 Main Magnet is Off ---------------------------------------- ----- at this time Huge rates at 17-18.06 were fixed at H1Lumi ----- 1B 108822 - - - - - ----- at this time new timing was installed at H1 (H1CTRIG upgrade)- ----- H1 Main Magnet is ON ---------------------------------------- 1C 110407 - - - 536 5.2 ----- at this time new FADC shifts installed at H1Lumi ------------- 1D 111538 -1.24 35 8-22 1503 25.4 ----- at this time selection of G+M H1Runs was made for calibration- 1E 112624 -0.98 25-35 6-22 3471 25.7 ----- at this time new FADC shifts installed at H1Lumi (PhotonArm)-- 2A 113524 -0.57 25-35 6-22 6676 29.1 ----- at this time Huge rates at 27.07 were fixed at H1Lumi -------- 2B 114471 +1.14 35 8-22 3767 28.7 2C 115049 -0.49 26-33 8-22 3139 26.7 3A 116309 -1.51 35 6-22 3062 34.9 3B 117655 +0.39 20-22 8-22 2442 32.9 3C 118020 -0.42 23-26 6-22 4044 30.2 3D 118504 -0.72 27-29 12-22 4501 33.2 3E 119318 -1.10 32-35 8-22 10957 34.8 3F 119724 -0.05 23-24 8-22 14597 38.6 ----- access with switching off HV at 301 room --------------------- 4A 120594 -0.64 31-34 8-22 11646 32.0 4B 121497 -0.38 21-23 8-22 13093 29.8 4C 122735 +0.17 23-25 6-22 13507 31.2 4D 123443 -0.46 20-25 8-22 10494 29.6 ----- access with making et01 as dead channel (ET44) --------------- 5A 124089 -1.30 23 8-16 11852 27.5 5B 124868 -0.16 23-26 6-22 14711 31.3 ----- access with switching off HV at 301 room (intervention ET32)-- 6A 126442 -0.32 22-23 8-22 11838 37.4 6B 127007 +0.12 17-18 6-22 9991 31.1 6C 128229 -0.12 22-24 6-22 10310 31.1 ----- shifted vertex (+70cm) data ---------------------------------- 7A 129462 -0.35 22-25 8-22 13527 305.6 7B 129645 -0.32 22-25 8-22 13277 285.1 7C 129836 +0.15 26-28 8-22 11889 188.2 ----- shifted vertex (-70cm) data ---------------------------------- 8A 129974 -3.87 29-31 6-22 10731 301.1 8B 130146 -2.41 29-30 8-20 10254 358.9 ----- nominal vertex ----------------------------------------------- 9A 130401 +0.33 22-24 6-22 8950 31.2 :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: all samples together: -0.28 25-26 8-22 239411 where: 1 - sample 'name'; 2 - start H1Run of data sample for calibration; 3 - Global Energy Shift for PD-channels (exept VCs) - at % units must be around zero; 4 - Resolution value from fit PDnVC-spectra -at % units - (good if less then 20%); 5 - Min values at PDrec histos (6,8,10,12,14,16.18,20,22 -> 6-22) which were used for Global Shift determination; 6 - Number of S92-events at G+M H1Runs which were used for final calibration steps (abs(Eveto)<0.3GeV) - entries into histo for fit making; 7 - Number of S92-events at G+M H1Runs which were used for final calibration steps (abs(Eveto)<0.3GeV) per 1nb-1 Int.Lumi(H1DB). P.S. Samples 8A and 8B show enough large (-3.8% and -2.4%) difference from zero. As seems this effect exists due to S.Levonyan's intervention into LESC-banks contents namely for 8A and 8B samples. As seems this intervention can explain earlier proclaimed problems at ETPDnVC and ETPDVC-samples. P.P.S. It seems, that your samples are quite different from our s91 selection, but only for the -70cm data. While in other samples PD-arm fit gave comparable results, for this one it was observed a significant (+3.2%) shift towards higher energies, which therefore was corrected in database. After that the energy distribution in gamma-arm for s91 sample looks fine. Why there exists such a big difference depending on the event selection is not clear to me for the moment, however the most important for L corrections was s91 and its consistent treatment. (S.Levonian) 15.04.1996 ================= H1KSOL === News from Underground... Etag33 and Etag44 are installed in HERA tunnel. The geometry of Etag33 is new for 96 year. Namely the distance from e beam axis to the center of Etag33 is now 155.3 mm instead of 159.9 for 95 year.The distance from e beam pipe wall to the the center of Etag33 is 123.4 mm.Moreover Etag33 is now parallel to the e beam axis (+- 2 mrad). The wall of the Etag44 case wich is close to the beam pipe was replaced by a thiner one (in 95 it was 2 mm now 0.8 mm) and assembly of crystals was moved to the new wall. The distance between beam pipe wall and center of crystal assembly is 25.8 mm (if one can trust the mark made by Malinovsky). One can find the sketchs for Etag33 and Etag44 geometry on dice2 in directory /home/dice/soloviev/lumi_pub/.They are in xfig format and if someone like to print it,first export file to ps format and then print it on printer you like. 21 dosimeters were installed on Etag33,Etag44,Etag7 and Photon arm. The map of dosimeters one can find in /home/dice/soloviev/lumi_pub/ in file dosimtr96.fig. 17.04.1996 ================= F11LEV === For LPI meeting ........ 1) It is a good idea to have a LUMI group meeting on a regular basis. Say, once per 2 weeks. On the first view, it may look as too much troubles/spending time. However, the advantage is that such meetings become short and efficient as soon as important problems are regularly discussed and not postponed until there are too many (as usually with our previous LPI meetings). There are several similar examples in H1 (muon group, Spacal group etc.) which are successful. There might be two options: a) Establish an official "be-weekly Lumi group meeting" and hold it regularly with the announcement via H1DATES. Advantage: other H1 interested/knowledgeble people (outside LPI) can participate and contribute. Drawback: it must be then held in English, not in Russian! b) Keep it inofficial, for LPI community only, with opposite adv/drawbacks. In any case the organization of such meetings require at least minimal work and responsibility. It should be 1-2 persons nominated to take care of this task, including writing at least short minutes. 2) Some more points for discussion on the next meeting. o the proposal above, including the name(s) of responsibles o ZEUS experience: - thiner filter in front of PD (1X0? -W.Krasny's remark) - use of empty bunches for pulsing calibration (?) - else? o methods for online lumi-96 (see LLO, 13-02-96) o LUMIMON selection: - remove "garbage" data and agree on useful trigger rates - define now or keep empty slots for new triggers in classific. o LREC-96: - what has to be included (new banks/detectors, dead ch.list) - improvements in various places (see LL12, 8-Nov-95) 23.04.1996 ================= H01GOG === LUMI Working Group meeting ################################################################ ##### ##### ##### Minutes of the first LUMI Working Group Meeting ##### ##### 19.04.1996 ##### ##### ##### ################################################################ Present: V.Andreev, A.Fomenko, N.Gogitidze, Yu.Soloviev, A.Usik, Ya.Vazdik (part of time). Meeting was called by N.G. After discussion with LUMI working group members the proposed agenda looked as follows: 1. The use of Lumi Detectors (ET,ET44+Coord.Det,ET8,PD,VC) in 1996 -- Thinner filter in front of PD (1X0?)? -- New Trigger Elements, New Subtriggers -- New banks (name, format), Changes in Old banks -- Online s/w (DAQ, calibration,...) - use of empty bunches for pulsing calibration? -- Offline s/w (reconstruction, calibration,...) - LREC-96 ---- what has to be included (new banks/detectors, dead ch.list) ---- improvements in various places (see LL12, 8-Nov-95) - LUMIMON selection 2. Methods for Online Luminosity measurements -- Coincidence -- Single photon 3. LUMI pool on dice 4. L4 - histos 5. Up-to-date information in WWW 6. Lumi - Logbook 7. LUMI Group Meeting? 8. ......??????...... The discussion started from the last point of the agenda. ##### Lumi Working Group meeting -------------------------- The decision was taken to have an internal LUMI working group meeting two times every month, and in addition in case of any extraordinary situation. The meeting will be held in Russian and outside working hours. It will be called by N.G. and announced in the Lumi Logbook. The minutes will be written in the Logbook as well. Everybody who is interested is invited to participate and contribute to the point. Useless chatter is not foreseen. ##### Lumi Logbook ------------ Since IBM will be available till March 1997, it was decided to keep Lumi Logbook on IBM till the end of this year. Meanwhile, A.U. will move all parts of the Logbook from IBM to RISC (LPI machine in Moscow), and from the next year we'll continue the Logbook on RISC. ##### Up-to-date information in WWW ----------------------------- Everybody was reminded to keep up to date the part of information in WWW, which he/she is responsible for. The general changes in the LUMI page should be done via LUMI Web Master - S.L. ##### L4 histos --------- Because of the new Coordinate Detector, installed in front of ET44, and because of position changes of ET, ET44, the new reference histograms will be provided this year by Yu.S. The possibility to add a new L4 histogram for Coordinate detector was also considered. ##### LUMI pool on dice ----------------- New information from R.Gerhards was presented by N.G. Thus, a new LUMI pool is created on dice: /acs/data/96/lumi where all useful LUMI information will be kept, namely: - LUMIMON files ( acs/data/96/lumi/LUMIMON.C9600xxx), - files with selected data for calibration and offline luminosity corrections, - files with selected data useful for physics analyses, - etc. Apart from the volume needed for the LUMIMON files (~100-150 GB) we can have in addition about 30-40 GB for other useful Lumi information. Everybody is kindly asked not to store anymore in the user pool /acs/user/userid any kind of Lumi information for internal and general use. It is not foreseen, as well, to use the LUMI pool for personal files. Be aware, that such files will be removed at once. LUMIMON files with 95-data (as well as TCL files) are stored presently in archive. To get these data out is possible via a request to R.Gerhards. After that it will take several days before the data will appear in the LUMI pool. Note, please, that all LUMIMON and TCL files with 1995 data are available on IBM. This will not be, however, the case for the 1996 data. ##### Methods for Online Luminosity measurements ------------------------------------------ After longer discussion the following points could be extracted: - In 1996 it is needed to involve into the H1LumiOnline envi- ronment the Luminosity calculation with the PhotonArm rate method (single photon method). The calculation should be presented to the HERA people. It seems that this problem can be solved in a simple way if in the H1LumiOnlineFIC2 one inserts some subroutine for background PhotonArm Rate estimate from the pilot bunches (as it is made for the coincidence method). One of the 4 TTL registers can be used. New values for the acceptance correction must be calculated and inserted into the H1LumiOnline environment. A.U.s "old" application (server), which was used for the calculation of the 'coincidence' Lumi value needs to be changed in only a few places: a) new addresses for background estimation; b) new VME address of total Rate (TTL register); c) new address for acceptance correction value; and d) new address for cross-section value. - The LRTL bank and all other banks connected with the coinci- dence method will not be changed. - The LUMM bank will be incremented with some new Lumi values: ACCC, Current Lumi Value and Integrated Luminosity values. - The cross-section for the new Lumi calculation will be pro- vided by V.A. from a H1Lumi dedicated run in the S93 data analysis. It is reasonable to keep the cross-section value stable during all Data Taking 1996. - The ACCC matrix can be calculated by V.A. and inserted into the H1LumiOnlineFIC2 by A.F. - The presentation of the "new" luminosity value is obligatory for the HERA people, but optional for the H1 people. (Yu.S. opinion is that we should show the "new" luminosity value for H1 people (on display in the room 301 and by H1LUMI command, as well) and keep the "old" value as optional for the using only on H1Lumi MAC, for example. This is to avoid the confusions.) - Which trigger should be used for the PhotonArm method? There are 2 possibilities: PD (maybe better PDLow(?)) and PD&&!VC. The PD&&!VC trigger is attractive because of the absence of 2-photons, 3-photons etc. (pileup). It is clear from last year (when 2-photon events correction was ~7%) that at the start of a LumiRun the 2-photon correction must be more significant and at the end almost unsignificant. For the absolute Lumi measurement with the Rate method it is impor- tant to remove the 2-, 3-, ...-photons effect from the OnLine Lumi calculation. With the involvement of the new VC from 95, it seems that the VC efficiency is predictable enough and stable. - A.U. promised to include "new" Lumi values (current and inte- grated) into his H1Lumi on-line presentation tools in the unix environment. - A.F. suggested that it would be good to use S92 events for the offline estimation of the PhotonArm luminosity, in order to cross-check the estimate of 2-,3-,...-photons background in the S91 sample. - A.U. reminded about the very old problem of a faster calcula- tion of the PD coordinates. The earlier H1Lumi could calcu- late coordinates not faster than 10 Hz. There are plans (A.U. and I.Sh.) to make it with 100 Hz rate. It is important for the HERA people to have a faster reaction from H1Lumi on changes of beam conditions connected with tilt. ##### The use of Lumi Detectors in 1996 --------------------------------- During last shutdown a new Coordinate Detector (ET44 strip) was installed in front of ET44. One more Electron Tagger (ET8) was prepared and installed at z~= -8 m. For the detailed information see WWW. -o- Thinner filter in front of PD (1X0?) ----------------------------------------- There was a question from W.Krasny: why do we use 2X0 filter in front of PD, while ZEUS uses only 1X0? The answer was given by Yu.S.: the minimum thikness of the filter used by ZEUS is 3X0. It consists of 2X0 of Carbon and 1X0 of Lead. Sometimes they used even thicker filter, up to 4.5X0. -o- New Trigger Elements, New subtriggers ------------------------------------------ This was discussed very preliminary, since the key-person I.Sh. is presently in Moscow and couldn't take part in the discussion. Anyhow, following is clear even without I.Sh.: - the 8th Lumi Trigger Element, which was used in previous years for NC (Neutron Counter), can now be used for internal Lumi needs (e.g. as ET8 trigger elem.), - it would be preferable to use for the first 7 Lumi TE's the same definition as in 1995 (for details see WWW), - it would be reasonable, taking into account the 1995 experience, to decrease the prescale factor for ST92 (PD&&!VC) and increase the prescale factor for ST95 (ET&&PD&&VC) let's say by factor of 2. The possibility of increasing ET44&&VC-events at H1Flow, which are used for calibration of ET44, was discussed. As one of possibilities the changing of the definition of ST90 from ET44 to ET44&&VC, was proposed by A.F. It is not yet clear whether we'll have a new monitoring ST for ET8 (e.g ET8&&VC or just ET8), which could be used for calibration of two calo channels in ET8. All these and related questions will be a matter of the discussion in the next meeting, somewhen at the beginning of May. -o- New banks (name, format), Changes in Old banks --------------------------------------------------- One new bank in H1Lumi Data Flow already appeared. The name of the bank is LFNC and it belongs to Forward Neutron Calori- meter. The content and format of this bank were defined by FNC people from Heidelberg. The length of the bank is ~10K in the test mode and ~2K in the ordinary mode. I.Sh. have made a first release of TwinFIC1 and TwinFIC1slave programs with readout of 10 FADC of FNC. The bank was written for runs 134488 and 134489. As Igor observed, the H1Lumi Dead time was almost not increased and remains within 800 microsec. Most likely, 2-3 new banks will be necessary for handling the new detectors: - bank with 'ET44 Tracker'-data (8bits readable from a new GPTP module from 8 neighbouring bunch-crossings around T0), - bank with 'ET8 Tracker/Veto'-data (13 bits readable from the same new GPTP from 4 neighbouring bunch-crossings around T0), - bank with 'ET8 Calo'-data (from 2 channels), the format of this bank could look like the format of LREF/LRPF/LR1F/LRNA banks. First 2 banks are small enough and could be united into one bank. The names and contents of the banks have to be discussed now and will be summed up at the next meeting. The LUMM bank will be changed because of the reasons mentioned above (Online Luminosity measurements). Could be that LRNA bank will be excluded from H1LumiDataFlow. Some changes could be in LRTN and LRTF banks because of the new ET8, etc. All these questions are open now for discussion. Please, write your suggestions, opinions into the Logbook. -o- Online s/w (DAQ, calibration,...) -------------------------------------- The following points were discussed ( the text is provided by A.F.): - Realization of above-mentioned changes in bank list, bank contents must be done (DAQ); - All possible optimization of readout for new detectors must be done too (DAQ); - Maybe it would be good to decide problem of individual VC- pulse reading (ordinarily this pulse is shifted 40-50 nsec from PD-pulses). Sometimes it is important (see experience of last year - when VC-pulse 'disappeared' from readout FADC window) (DAQ); - It is possible that calibration of two calo ET8-channels will be made in the same manner as calibration for ET44, ET32 and PD channels.It is not clear yet - is it needed to make permanent calibration of ET8-channels in Luminosity subbranch (FIC2) or these channels will be more stable and it will be enough to make only off-line calibration without Relation Coefficients set defining (calibration); - As seems no significant change in on-line ET44,ET32,PD,VC - calibration procedures (calibration); - Problem of installation of latest release of H1Lumi reconstruction package in FIC2-environment is under discussion (calibration). The question about using empty bunches for pulsing calibration was returned back to S.L. with a new question: what do you actually mean? -o- Offline s/w (reconstruction, calibration,...) -------------------------------------------------- The problem of bad coordinate reconstruction was discussed (especially, bad PD coordinate reconstruction in ETPDVC-sample). Everybody is aware of this problem and agreed that more detailed discussion together with S.L. is necessary, after which the changes could be done by V.A. and A.F. The selection code for LUMIMON data will be changed (by N.G.) so that some "garbage" will be removed. E.g., only data with standard trigger set will be written, etc. The changed code will be presented in one of the next meetings and in WWW. ##### I would like to thank A.F. for help in several points of the minutes. N.Gogitidze 24.04.1996 ================= H1KFOM === FADCs Pulses Investigation It was made analyze of FADCs pulses from hot channels at ET32,PD,ET44 and VC at H1Run 114330 (H1LumiDedicated Run with LREF,LRPF,LR1F-banks) with Ie+ total near 12 mA and p-beam lost. This Run was written 26.07.1995 after end of LumiRUN #768. The next global characteristics of FADC pulses are presented at LREF,LRPF,LR1F-banks: 1) max value (amplitude) of channel response pulse is disposed at 5th bin of ten bins FADC window for ET-channels; 4th bin of ten bins FADC window for PD-channels; 9th bin of ten bins FADC window for VCs-channel; 5th bin of ten bins FADC window for ET44-channels. 2) pedestal values of channel response pulse are disposed at: 1st,2nd and 3rd bins of ten bins FADC window for ET-channels; 1st bin of ten bins FADC window for PD-channels; 1st,2nd,3rd,4th and 5th of ten bins FADC window for VCs-channel; 1st,2nd and 3rd bins of ten bins FADC window for ET44-channels. P.S. It means that for ET and ET44 channels it was possible to decrement so called FADC shifts on 2 units: ET: 195->193; ET44: 186->184; PD: kept as 138. VCs: 138->134 (if it will be implemented VCs-reading). 3) situations with zero pedestals are seen at each channel. These are rough percents of zero pedestal events per channel at 49907 ETPDnVC events of Run 114330 at hot channels: e35= 1.6% e36= 3.6% e37= 1.0% e38= 4.0% e39=10.0% e40= 4.0% e41=4.0% e28= 2.6% e29= 2.0% e30= 4.0% e31= 2.2% e32=12.0% e33= 2.8% e34=4.4% e21= 1.6% e22= 2.4% e23= 1.6% e24= 1.6% e25= 3.0% e26= 4.0% e27=3.0% p15= 0.4% p16= 0.6% p17= 1.2% p18= 2.0% p19= 2.0% p10= 0.8% p11= 0.2% p12= 0.3% p13= 1.5% p14= 2.2% p05= 1.2% p06= 0.6% p07= 2.0% p08= 2.8% p09= 3.0% vcs= 2.4%(sample with ETPDnVC) This zero pedestal situations must be investigated additionally event by event for understanding right nature of this 'zero' pedestals. For ET44-zero pedestal number estimation it was used ET44VC-sample from Run 114330 (3659 events): et02 = 8.4% P.S. enough large quantity of 'zero pedestals' events is fixed at e32 and e30 (more then 10%). It is interesting that for PD-channels there are (at aver.) less percents of 'zero pedestals' events. 4) FADC makes digitization of response pulse with 255-units unlinear scale. 255 value at FADC bin means overflow situation (at linear scale this value is 1968). For any case: Linearization formula - LinearResponse=LR, UnLinearResponse=ULR LR=int(483.6/(256/ULR-0.7582)) where ULR=1,2,...,255 For example for ULR=255 LR=1968. We have next characteristics for each from hot channels at 49K event ETPDnVC sample (percents of full scale using 0-1968): e28=52% e29=62% e30=48% e31=65% e32=53% e33=53% e34=57% e21=57% e22=70% e23=57% e24=63% e25=63% e26=48% e27=72% p15=?? p16=60% p17=54% p18=64% p19=?? p10=92% p11=52% p12=73% p13=60% p14=?? ?? - low statitistics p05=91% p06=66% p07=48% p08=60% p09=?? vcs=39% High mentioned measurements were made for 5th FADC window bin at ET- channels, for 4th FADC window bin at PD-channel and for 9th FADC window bin at VCs-channel. Overflow situations were seen at channels p05 (5 events) and p10 (6 events). For ET44-channel FADC scale using estim. it was used ET44VC-sample from Run 114330 (3659 events): et02= 75% P.S. There are a lot of channels with enough low percents of FADC scale using.As seems 75-85% are good values for these %s. May be 90-95% are possible due to overflow situations which had happened at p05 and p10-channels which have 91-92% values put negligable percents of overflow situations. May be better to investigate overflow situations (which could be mainly due to different overlaping of 2 or more responses at one channels) at another samples (S86 - for ET, S91 - for PD/VCs and S90 - for ET44. Some tests with ETPDnVC-sample from H1Run 114330 show that FADC-pulse degradation on 50% (with existing procedure of LREE/LRPE-banks contents making) DECREMENTS FINAL RESOLUTION VALUES at ETrec+PDrec distributions on 10%. So there is some dependence RESOLUTION=f(PERCENT OF FADC SCALE USING). The more Percent of FADC Scale Using the better final resolution values. Indirect evidence of this effect was experience of last year (at start of DataTaking'95 we had final resolution value near 0.89 GeV and after 2 Large Rate Presence at H1Lumi Detectors we had around 1.10 GeV resolution value). As seems resolution degradation is connected with channel response degradation. Experience of Data Taking'94 supported this supposition - at 1994 we had permanent response degradation at hot channels(at 1995 - there are no permanent degradations at channel responses - only 'jumps' due to overrates) and we looked for final resolution values permanent degradation too. It was last H1Lumi Dedicated Run at DataTaking'95 with LREF/LRPF/LR1F banks and all data after 26.07.95 were collected with the same FADC -pulses characteristics (as seems). It is pity but only this H1Run puts single samples for FADC-pulse investigation at all DataTaking'95 period. It would be good if at this year H1LumiDedicated Runs with LREF/LRPF and LR1F banks were written may be once per month if there will be not additional problems with timing changing or something else connected with FADC-pulses. It would be good if at future (nearest) release of H1REC it was excluded from LUREAD.f-subroutine the CALL LRAWD line for case of H1REC using inside L4-farm. As seems there are a lot of possible improvements at this area (FADC shifts, HV values or attenuators tuning, may be zero pedestal labeling at all hot channels or at some from hot channels etc.). 24.04.1996 ================= H1KFOM === Different DIGI Algorithmes It were tested different algorithmes of FADC counts making with using of ETPDnVC-sample from H1Run 114330 (near 49K events). It were tested 6 algorithmes 1) standard OnLine algorithm - first bin as pedestal and FADC count is integral of 2-10 bins without pedestal; 2)the same but without 10th bin (error on 1 unit at FADCshift setting investigation); 3) the same but without 9th and 10th bins ( error on 2 unit at FADC shift setting investigation); 4) Bin with max value without pedestal as FADC count; 5) integral of bins connected with forward front of FADC pulse; 6) integral of bins connected with backward front of FADC pulse. For 27.54 mean values at ETrec+PDrec distributions it was used procedure of ETrec/PDrec multiplication on correction coefficient (due to H1REC uses calibration coefficients from H1DataBase). Next results were obtained - mean,sigma at LOOK peak finder: Standard (2-10 for ET,2-10 for PD and 2-10 for VC) - 27.54 1.02 Coeff.corr = 1.00 Without 10th (2-9 for ET,2-9 for PD and 2-9 for VC) - 27.54 1.03 Coeff.corr = 1.048 Without 9,10th (2-8 for ET,2-8 for PD and 2-9 for VC) - 27.54 1.04 Coeff.corr = 1.104 Bin with max (amplitude) (5 for ET, 4 for PD,9 for VC - 27.54 1.86 Coeff.corr = 3.417 Forward front (2-5 for ET,2-4 for PD and 2-9 for VC) - 27.54 1.55 Coeff.corr = 1.7625 Backward front (5-10 for ET,4-10 for PD and 9-10 for VC) - 27.54 1.27 Coeff.corr = 1.2158 It means that selected 7 years ago algorithm of FADC counts making which is used at OnLine procedures of preparing LREE,LRPE and LR1E -banks is right and best as seems. Cuts of last one bin or 2 bins at FADC window (due to possible errors at FADC shifts setting for example as it was at 95 year) do not change significantly final resolution digits at ETrec+PDrec distributions. 29.04.1996 ===== OnLine ==== H1KFOM === OnLine Programs Development Today it was made new release of H1LumiOnLineFIC2 program (for FIC2- processor). One subroutine (PutIntoFTAB12.f) was updated due to old bug was found (INDIRECT COMMON problem). Old release which worked during all H1DataTaking'95 cannot reconstruct ETrec and worked more or less without problems only due to random coincidence (some data from INDIRECT COMMON block kept at FIC's DPM memory from previous releases - created before 09 Feb. 1995). These are creation dates and memory size of last release: H1LumiOnLineFIC2.......MPST MPS ....234354 Sun Apr 29, 18:49 1996 Release is kept at H1Lumi:HD_LPI5:MPW:FomenkoAfter15.04.96:Applications -directory. Current releases of TwinFIC1 and TwinFIC1slave programs are kept at the same directory. These releases can produce LFNC-bank and can read data from 'Trackers' of ET44 and ET8 but without creation of new banks with these data. Only 'cosmetic' update was made with TwinFIC1 and TwinFIC1slave programs (produced by Igor Sheviakov at first half of April 1996).It were deleted little bugs and tuned ReadFNCd.f-subroutine on full scale reading. These are creation dates and program sizes of last release: TwinFIC1...............MPST MPS .....89370 Sat, Apr 20, 14:29 1996 M TwinFIC1slave..........MPST MPS .....43462 Thu, Apr 18, 16:12 1996 M 30.04.1996 ===== OnLine ==== H1KFOM === OnLine Programs Development Today it was made new release of H1LumiOnLineFIC2 program (for FIC2- processor). One subroutine (InitConstant2.f) was updated and one subroutine (TenBunchNewPD.f) was added for making of interface for future Usik's server (PD counts at e+pilot bunches each 1.5 sec). These are creation dates and memory size of last release: H1LumiOnLineFIC2.......MPST MPS ....235276 Tue Apr 30, 17:59 1996 Release is kept at H1Lumi:HD_LPI5:MPW:FomenkoAfter15.04.96:Applications -directory, VME-addresses of 10 counters with Pilot Bunch PD-counts which are updated each 1.5 sec is $B012D3DC-400 as its are seen from MacII. 02.05.1996 ===== OnLine ==== H1KFOM === OnLine Programs Development Today it was made new release of H1LumiOnLineFIC2 program (for FIC2- processor). Two subroutines (InitConstant2.f and main-program) were updated and three subroutines were added for PhotonArm Rate Method Lumi calculation - Current value and Integral values (InitLumiMonitoringPD.f LumiMonitoringPD.f and TiltPD.f). TiltPD.f is preliminary release due to new ACCC-matrix for PD-acceptance is not ready yet. It was put preliminary estimated BH cross-section as 59.5 mb (from V.Andreev's investigation of LUMMbank contents from H1DataTaking'95). These are creation dates and memory size of last release: H1LumiOnLineFIC2.......MPST MPS ....244272 Thu May 02, 17:32 1996 Release is kept at H1Lumi:HD_LPI5:MPW:FomenkoAfter15.04.96:Applications -directory, It was made new release of TwinFIC1-program for making of needed for PD Integral Lumi values calculations (L2Keep.f and main program were updated). TwinFIC1...............MPST MPS .....89550 Thu, May 02, 17:06 1996 M There are new VME adresses for keeping and updating of current Lumi and integrated Lumi values calculated with Photon Arm method: Current Lumi value: $B0AB9A28 - A1 $B0AB9A2C - NCA1 H1 Run Gated Integrated Lumi: $B0AB9A30 - B1 - Lumi for Current H1 Run (zeroed only during EndRun) $B0AB9A34 - NCB1 $B0AC1040 - C1 - Lumi for previous H1Runs at current LumiRun $B0AC1044 - NCC1 $B0AC1050 - D1 - not used (spare) $B0AC1054 - NCD1 H1 data taken Integrated Lumi: $B0AB9A38 - B11 - Lumi for Current H1 Run (zeroed only during EndRun) $B0AB9A3C - NCB11 $B0AC1048 - C11 - Lumi for previous H1Runs at current Lumi RUN $B0AC104C - NCC11 $B0AC1058 - D11 - not used (spare) $B0AC105C - NCD11 HERA produced Integrated Lumi: $B0AB9A44 - B2 - Lumi for latest 180 sec period $B0AB9A48 - NCB2 $B0AB9A4C - C2 - Lumi without latest 180 sec period $B0AB9A50 - NCC2 $B0AC1060 - D2 - not used (spare) $B0AC1064 - NCD2 When Lumi RUN is finishing - with pushing on special button at TMonitor_NC - some Integrated Lumi Value must be zeroed: C1,C11 and B2,C2(?). B1 and B11 will be zeroed with H1 End Run. It were prepared 4 values for LUMM-bank filling: Current Lumi value, H1 Gated Lumi, H1 Data Taken Lumi and HERA Produced Lumi. ACCCPD-value can be put into LUMM-bank too. VME-address of ACCCPD is $B0ABD8A4. All VME-addresses are presented as its are seen from MacII. 03.05.1996 ===== OnLine ==== H1KFOM === OnLine Programs Development Today it was made new release of H1LumiOnLineFIC2 program (for FIC2- processor). Two subroutines (InitConstant1.f and LumiMonitoringPD.f) were updated for making of interface for SuperCard project and to LUMM bank contents making. These are creation date and memory size of last release: H1LumiOnLineFIC2.......MPST MPS ....244344 Fri May 03, 15:08 1996 Release is kept at H1Lumi:HD_LPI5:MPW:FomenkoAfter15.04.96:Applications -directory, It was made new release of TwinFIC1-program for making of needed for PD Rate Method calculated luminosity inserting into LUMMbank-contents. (OutBanks.f-subroitine was updated). It were removed two old bugs from OutBanks.f-subroutine (sometimes it was possible shift on 1 longword of LUMM-bank contents). These are creation date and memory size of last release: TwinFIC1...............MPST MPS .....90178 Fri, May 03, 17:06 1996 M Release is kept at H1Lumi:HD_LPI5:MPW:FomenkoAfter15.04.96:Applications -directory, LUMMbank contents was changed and now has length 736 longwords. At bottom of this bank it will be possible to find next values: ! ! BANKname BANKtype !Comments ! TABLE LUMM B32 ! LUmi_Measurements_with_alternative ! _Methods ! (non-event bank at KEEP-environment) ! ATTributes: ! ----------- ! ! negative values of the first 220 columns means technical problems ! with rate calculations ! !COL ATT-name FMT Min Max !Comments ! 1 PD1RT000 I -INF +INF ! Rate of Photon Arm Energy Trigger(PD1) ! in bunch 0, in 0.1 Hz units .................................. 729 LLTLSTPD I -INF +INF ! H1Lumi Local Timer value for last ! event at PDdep spectrum !----- Photon Arm (PD) Rate Lumi calculation area ------------------- 730 CTLVPD I 0 +INF ! Current Total Luminosity Value ! (averaged over the last 10 sec., in ! units of 10**25 cm-2s-1) 731 RUNLUMPD I 0 +INF ! Total Integrated Luminosity from the ! beginning of the run ! (in units 10**25 cm-2 = 0.01 mb-1) 732 RH1LUMPD I 0 +INF ! H1 Integrated Luminosity from the ! beginning of the run (during H1active) ! (in units 10**25 cm-2 = 0.01 mb-1) 733 HERALUMPDI 0 +INF ! HERA Produced Luminosity from the ! beginning of the current ep-collisions ! (in units 10**27 cm-2 = 1.0 mb-1) 734 ACCCPD I 0 1100 ! Acceptance correction coeff (in 0.001) ! (after analysis of the last 50 events) 04.05.1996 ===== OnLine ==== H1KFOM === OnLine Programs Development Today it was made new release of H1LumiOnLineFIC2 program (for FIC2- processor). Two subroutines (LUMMbankFill.f and TiltPD.f) were updated. Changings at LUMMbankFill.f connected with changing of PD1-bunch rates on PD-bunch rates. TiltPD.f was updated due to V.Andreev had finished the calculation of ACCCPD-matrix 17x17 points and this new matrix was inserted into this subroutine. These are creation date and memory size of last release: H1LumiOnLineFIC2.......MPST MPS ....243190 Sat May 04, 16:43 1996 Release is kept at H1Lumi:HD_LPI5:MPW:FomenkoAfter15.04.96:Applications -directory, It is needed to note that from Aug.95 up to End of H1DataTaking'95 the PD2-bunch rates (220) were written into LUMM-banks. PD1 was changed with PD2 at its place at HistoMemory five inputs and PD2 was changed with ET44 at its place at HistoMemory five inputs (so 4th input was PD2 and 5th input was ET44). Before Aug.95 - 4th input was PD1 and 5th input was PD2. Due to these communication switching the contents LUMM-bank was changed (another bunch rates (PD1->PD2), PD1 Rates became as PD2 rates and PD2 rates became as ET44 rates). PD1 trigger bit was not included into 5 inputs of HistoMemory unit (1th=VC,2nd=PD,3rd=ET,4th=PD2,5th=ET44). 07.05.1996 ================= H01GOG === LUMI Working Group meeting The next Lumi Working group meeting will take place tomorrow, 8.05.96., at 15:00, in the small guest-room under the kantine. The main point of the discussion will be everything what is concerning the new TE's, ST's, banks. 07.05.1996 ===== OnLine ==== H1KFOM === OnLine Programs Development Today it was made new release of TwinFIC1 program (for FIC1-Master processor). Three subroutines were updated at this release: IntegralLumi.f (PhArmLumi involving); InitConstant2.f (LFNC bank Off/On involving - default value - LFNC-bank is ON); OutBanks.f (data from ET44 'Tracker' is added into 2 last (additional) longwords of LRE1-bank LRE1-bank became more on 2 longwords. These are creation date and memory size of last release: TwinFIC1...............MPST MPS .....90530 Tue, May 07, 13:16 1996 M Release is kept at H1Lumi:HD_LPI5:MPW:FomenkoAfter15.04.96:Applications -directory, Latest releases of TwinFIC1,TwinFIC1slave and H1LumiOnLineFIC2 programs were tested today with H1CDAQ (Run 137668). TwinFIC1slave..........MPST MPS .....43462 Thu, Apr 18, 16:12 1996 M H1LumiOnLineFIC2.......MPST MPS ....243190 Sat May 04, 16:43 1996 LUMM-bank at this Run has length on 5 LongWords more and LRE1-bank - on 2 LongWords more. LFNC-bank is presented firstly at H1Runs with right information at all bank body. These are selected lines from Run Summary for Run 137668: NRUN NrofEvts Ev.Fst Ev.Lst DATE TIME <---> DATE TIME 137668 2054 0 4FFFFFFF 960507 143841 960507 144241 ...... 4C554D4D:LUMM 24 736 736 736 ...... 4C523145:LR1E 2008 8 6 9 ..... 4C464E43:LFNC 2008 2594 2594 2594 ..... Output Data Set Name HERA04.H1RAWD.C9601259 Permanent You can compare lengths of LUMM- and LR1E-banks with latest Run of H1DataTaking'95 period. NRUN NrofEvts Ev.Fst Ev.Lst DATE TIME <---> DATE TIME 131045 2362 0 3672 951127 43001 951127 43211 ..... 4C554D4D:LUMM 14 731 731 731 ..... 4C523145:LR1E 2297 6 4 7 ..... Output Data Set Name HERA04.H1RAWD.C9508001 Permanent 08.05.1996 ===== OnLine ==== H1KFOM === OnLine Programs Development Today it was made new releases of TwinFIC1 and TwinFIC1slave programs for FIC1 Master and Slave processors. It were made changings at 7 subroutines (Master - main,PrepRunSub.f,OutBanks,ReadNC.f; Slave - ReadFNC.f,L2Keep.f,ReadNCS.f). Changings connected with LFNC-banks were made for posibility of monitoring and future H1SlowControl alarm of 'bad' situation with transmission of data for LFNC-bank from H1FNC-side (there will be no ReadOutError with LFNC-bank - only this bank will be absent at current H1Event with alarm at H1SlowControl). Length of LFNC-bank was decremented on 1 longword and became 2593 at test mode. LRNA-bank was removed (as seems forever) from H1LumiDataFlow. New H1Lumi bank was included into H1Lumi data flow. Its format is B16, its name is LR2F. Bank will be similar to LREF,LRPF,LR1F-family banks but for this year so called FADC window for each channel will consist of 22 10nsec bins (not 10 bins as at all F-banks). Bank has data from four channels (2 will be used for two ET8 calo channels and 2 will be free (spare)). At bottom of this bank it will be added 2 longwords with bits data from 4 neighbour bunch x-ings from ET8 'Tracker' and 'Veto' channels (two bytes per each time slice). These are creation dates and memory sizes of last releases: TwinFIC1...............MPST MPS .....91308 Wed, May 08, 14:05 1996 M TwinFIC1slave..........MPST MPS .....44118 Wed, May 08, 14:05 1996 M Release is kept at H1Lumi:HD_LPI5:MPW:FomenkoAfter15.04.96:Applications -directory. 08.05.1996 ================= H01GOG === LFIL - new Lumi bank in DB A new Lumi bank (LFIL) has been created for the purpose of being used in the dq-ntuple. The bank format is shown below. The bank containing the 1995-data was written yesterday (7.05.96) into the Data Base (MDB on dice, option RDB). Once 1996-data taking will start, the bank will be updated regulary. **************** *-- Author : Nelly Gogitidze 07/05/96 ! BANKname BANKtype ! Comments ! TABLE LFIL ! Lumi FILl numbers and associated info ! ! ATTributes: ! ----------- !COL ATT-name FMT Min Max ! Comments ! 1 FILNR I 200 100000 ! Lumi Fill number acc. to Lumi Group 2 RUNFS I 0 999999 ! First Run number in fill 3 RUNLS I 0 999999 ! Last Run number in fill 4 FILDAT I 10100 311299 ! Date (of start) in form DDMMYY 5 HERPRO F 0.0 9999.9 ! Hera total lumi in nb-1 (produced ! at final beam energies) 6 HERDEL F 0.0 9999.9 ! Hera delivered lumi in nb-1 (delivered ! for physics (during LUMI runs)) 7 H1GATE F 0.0 9999.9 ! H1 gated lumi in nb-1 (gated by H1 ! RunStart-RunStop, including DT) ! (for permanent runs only) 8 ECUR F 0.0 9999.9 ! Electron current in mA 9 PCUR F 0.0 9999.9 ! Proton current in mA 10 EFILNR I 1 99 ! Electron fill number during proton ! fill: 1 for first, 2 for second, etc. ! (for Lumi Fills only) END TABLE 08.05.1996 ================= H1KFOM === LR2F-bank Structure ....... Date: Wed, 8 May 1996 20:30:25 +0200 (MST) From: Alexandre Fomenko To: gerhards@dice2.desy.de Subject: New H1Lumi bank Dear Ralf, It is planning to involve new H1Lumi bank at H1DataFlow with format B16. I know that default bank format is B32 so before first appearence of this bank at H1DataFlow it would be good to inform You about this occasion for needed corrections or something else. Contents of this bank connected with ET8 Prototype. Preliminary stucture is next: ! BANKname BANKtype !Comments ! TABLE LR2F B16 ! Lumi_Response_electron_tagger_2_Fadc ! ATTributes: ! ----------- !COL ATT-name FMT Min Max !Comments ! 1 NCELL I 0 3 ! cell (channel) number 2 A0102 I 0 65535 ! 1-st (high byte) and 2-nd (low byte) ! bins of NCELL FADC window ! packed into B16 word 3 A0304 I 0 65535 ! 3rd and 4th bins of NCELL FADC window 4 A0506 I 0 65535 ! 5th and 6th bins of NCELL FADC window 5 A0708 I 0 65535 ! 7rd and 8th bins of NCELL FADC window 6 A0910 I 0 65535 ! 9th and 10th bins of NCELL FADC window 7 A1112 I 0 65535 !11th and 12th bins of NCELL FADC window 8 A1314 I 0 65535 !13th and 14th bins of NCELL FADC window 9 A1516 I 0 65535 !15th and 16th bins of NCELL FADC window 10 A1718 I 0 65535 !17th and 18th bins of NCELL FADC window 11 A1920 I 0 65535 !19th and 20th bins of NCELL FADC window 12 A2122 I 0 65535 !21th and 22th bins of NCELL FADC window END TABLE 09.05.1996 ===== OnLine ==== H1KFOM === OnLine Programs Development Today it was made new release of H1LumiOnLineFIC2 program (for FIC2- processor). Three subroutines were updated:TenBunchNew.f,FindPilotFIC.f and TenBunchNewPD.f. Changings at TenBunchNewPD.f are connected with involving of PhotonArm Background Rate estimation with using up to 20 pilot bunches (not 10 as earlier). PhotonArm Background Rate is nor- malized on sum of pilot bunch currents and is put into next VME-address B0AC1158 as it is seen from MacII. It was removed old bug with bus errors appearence at H1LumiOnLineFIC2 program after some crashes with power supply or something else connected with enough long switching off the H1Lumi Master VME crate. Protection against BERR involved into high mentioned subroutines which were responsible for this situation. These are creation date and memory size of last release: H1LumiOnLineFIC2.......MPST MPS ....243622 Thu May 09, 14:07 1996 Release is kept at H1Lumi:HD_LPI5:MPW:FomenkoAfter15.04.96:Applications -directory, 09.05.1996 ===== OnLine ==== H1KFOM === Tests with H1CDAQ ......... Today before Run 137859 (near 14:27) it were booted all latest releases of OnLinePrograms into FIC1s and FIC2: TwinFIC1...............MPST MPS .....91308 Wed, May 08, 14:05 1996 M TwinFIC1slave..........MPST MPS .....44118 Wed, May 08, 14:05 1996 M H1LumiOnLineFIC2.......MPST MPS ....243622 Thu May 09, 14:07 1996 LR2F-bank had appeared firstly at H1DataFlow. NRUN NrofEvts Ev.Fst Ev.Lst DATE TIME <---> DATE TIME 137859 94 0 4FFFFFFF 960509 142705 960509 143318 .... 4C523145:LR1E 56 8 7 9 ... 4C464E43:LFNC 56 2593 2593 2593 4C523246:LR2F 56 27 27 27 ... Output Data Set Name HERA04.H1RAWD.C9601317 Permanent 09.05.1996 ===== OnLine ==== H1KFOM === ET44- & ET8 'Trackers' Data As it was proclaimed earlier it was decided to write data from ET44 'Tracker' and ET8 'Tracker' and 'Veto' into bottom lines of LR1E and LR2F-banks (last 2 longwords). May be at future (after more or less succesful testing of these devices) it will be created new bank (VETE- or TEL1-type) with these data. Some details for these data disposition at banks: LR2F: (13 bits from ET8 'Tracker' and 'Veto' at each bunch x-ing) Bank has fixed length (27 longwords) and last 2 longwords (or 4 B16 words) can be described as next lines for example: NR*NC+1 TSM1 I 0 65535 ! status of ET8 'Tracker' & 'Veto' bits ! at t0-1 bunch x-ing NR*NC+2 TST0 I 0 65535 ! status of ET8 'Tracker' & 'Veto' bits ! at t0 bunch x-ing NR*NC+3 TSP1 I 0 65535 ! status of ET8 'Tracker' & 'Veto' bits ! at t0+1 bunch x-ing NR*NC+4 TSP3 I 0 65535 ! status of ET8 'Tracker' & 'Veto' bits ! at t0+2 bunch x-ing LR1E: (8 bits from ET44 'Tracker' at each bunch x-ing). Bank has non-fixed length and last 2 longwords (or 4 B16 words) can be described as next lines for example: NR*NC+1 TSM3M2 I 0 65535 ! status of ET44 'Tracker' bits at t0-3 ! bunch x-ing (high byte) and at t0-2 ! bunch x-ing (low byte) NR*NC+2 TSM1T0 I 0 65535 ! status of ET44 'Tracker' bits at t0-1 ! bunch x-ing (high byte) and at t0 ! bunch x-ing (low byte) NR*NC+3 TSP1P2 I 0 65535 ! status of ET44 'Tracker' bits at t0+1 ! bunch x-ing (high byte) and at t0+2 ! bunch x-ing (low byte) NR*NC+4 TSP3P4 I 0 65535 ! status of ET44 'Tracker' bits at t0+3 ! bunch x-ing (high byte) and at t0+4 ! bunch x-ing (low byte) Details of bits disposition at mentioned data (at which bits are disposed responses from 'Trackers' or 'Veto' elements) will be proclaimed later. T0-tuning will be made for GPTP-readout during tests with beams. 10.05.1996 ================= H01GOG === LUMI Working Group meeting ################################################################ ##### ##### ##### Minutes of the 2-nd LUMI Working Group Meeting ##### ##### 8.05.1996 ##### ##### ##### ################################################################ Present: V.Andreev, A.Fomenko, N.Gogitidze, I.Sheviakov, Yu.Soloviev, A.Usik. The discussion mostly concerned the new TE's, ST's, banks. - The 8th Lumi Trigger Element will be used for the new electron tagger ET_8 ( LU_ET8 ). The definition of the first 7 Lumi TE's will remain the same as in 1995. - There will be at least one monitoring ST for the ET-8. The definition and the number of this/these ST will be clear later, somewhen in June before the data taking starts. - The formats of 2 Lumi-banks ( LUMM, LR1E ) were changed, (extended), so that the 'ET44 Tracker' data will be available now as well in the H1 data stream. It has not been checked if LREC will run with these extensions. - One new Lumi bank (LR2F) for ET-8 data was created. The detailed information about these and other banks is given in our Logbook. The information has to be given to H.U. Martyn as well, for inclusion in the H1 DDL library. - The LUMIEC subroutine, which now runs in the L4 Farm code, has to be updated as soon as the new TE and ST are known. The new Lumi banks will then be included in the LUMIMON tapes. - There is no conclusion concerning the update of LREC, with respect to including the ET44 Tracker data in the ET44 re- construction. There is an ongoing discussion about the different methods of online Luminosity measurements and the presentation of Luminosi- ty values in the HERA and H1 Control Rooms. N.Gogitidze 11.05.1996 ===== Calibr ==== H1KFOM === Selection into Index-files It was tested new scheme of events selection needed for calibration of H1Lumi Detectors. One Index-file per calibration samples will be created from 30-40 LUMIMON data sets. Into this index file it will be selected all used for previous year calibration events: ETPDnVC,ETPDVC, ET44VC,S9291 and S93. Useful subsamples (ETPDnVC,ETPDVC etc) can be selected from this one data set enough quickly and can be used with ordinary H1Lumi calibration technology (calibration, n-tupel making etc.). New scheme was tested with last calibration sample(9A) of previous year. It is needed to note that only last FPACK-release can work with /acs/..-disposed input files (1.00/18). First step of selection is made directly from /asc/..-disposed LUMIMON-data sets and from 23 data sets (4600 Mbytes) produces only 3.8 Mbytes Index file. sfdir -p h1stage -u h1 | grep fomenko 3837600 May 11 15:05 H1KFOM.CALIBR.S9A.M511533 (class S) 238146 ev. Next steps of selection are made from anywhere disposed Index file which was produced at first stage and jobs for selection got 5-6 sec. of dice2 CPU. 1053000 May 11 16:15 H1KFOM.ETPDNVC.S9A.M511533 (5 sec.CPU) 64406 ev. 1450800 May 11 16:25 H1KFOM.ETPDVC.S9A.M511533 (5 sec CPU) 89296 ev. 1006200 May 11 16:35 H1KFOM.S9291.S9A.M511533 (5 sec.CPU) 61122 ev. 631800 May 11 16:56 H1KFOM.ET44VC.S9A.M511533 (5 sec.CPU) 38546 ev. 421200 May 11 17:06 H1KFOM.S93.S9A.M511533 (5 sec.CPU) 25186 ev. Jobs for calibration and n-tupels making are working with index-files of second generation (ETPDVC,ETPDVC,etc) and must be submitted at S- -class only due to work with cartridges. Main calendar time is spent on staging of LUMIMON-data sets (with internal osmcp calls) into h1stage pool. Calibration job (with 3 data set rewinds) gets at more or less free day (Saturday or Sunday) near 4 hours of total (calendar) time being at diceS Running Mode. Each from 3 NtupleMaker-jobs gets near 1 hours at diceS Running Mode. At ordinary day - it depends from queues on osmcp using. If we shall use this new scheme of selection of needed for calibration events we shall not produce enough large quantity of new data sets with data which are presented once at LUMIMON data sets. As You remember at last year near 0.5-1.0 GbYte of new data sets were produced from 3-4 GByte of LUMIMON data sets. There was the problem of keeping of this new data sets. Let's hope that at this year this problem will be decided with mentioned manner. 11.05.1996 ================= H1KFOM === Proposal for H1RECLUMI makers Experience of last year OnLine VC-calibration shows that it is time to involve Relation Coefficient for VCs channel too. As seems it is needed to make little changing at LUREAD.f subroutine at this region: ...... * ignore CC for veto, it is included in RELC (via LFRC) CCC = ATOMEV(3) * RELC(LCET+NCH+1) * CORREE(3) ..... It must be changed for example on the next line: CCC = CC * ATOMEV(3) * RELC(LCET+NCH+1) * CORREE(3) During first H1Lumi'96 calibration it would be written into LFRC-bank not Calibration Coefficient but Relation Coefficient for VCs channel. 12.05.1996 ===== Calibr ==== H1KFOM === Old RC Sets in H1DataBase(9A) Today it was made attempt to update LFRC and LESC banks contents at H1DataBase at dice2-environment. Some values at LESC-bank and LFRC-bank were not significantly changed in compare with 9A-sample values. Attempt was made only as test of updating tool at new environment. As First Run it was put Run Number 137000: Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LFRC (_501) 88 e-p data 512301358 130401 136999 83 951230 H1KFOM 90* e-p data 605121248 137000 0 83 960512 fomenk Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LESC (_582) 105 e-p data 512301358 130401 136999 4 951230 H1KFOM 109 e-p data 605121248 137000 0 4 960512 fomenk As seems old Levonian's tool is working inside dice2-environment too. 14.05.1996 ================= H1KFOM === First HERA p-beam'96 ....... Yesterday near 22:00 it was fixed first HERA p-beam'96. Proton beam studies was continued up to today morning (near 10:10). Ip total max during 12 hours HERA p-beam activity was not more then 0.9 mA. 16.05.1996 ===== Calibr ==== H1KFOM === VCs Relation Coefficient (9A) do '/xc=(xet>-6.0&xet<6.0)' do 'hs(200)=nt(100)(etrec*0.9993+(pdrec-vcdep)*1.01871+vcdep*1.243)@(xc)' mean = 27.51 GeV; Sigma =1.18 GeV --- CCvcs=5.098 at 8B-sample; 1,243 - correction factor for this value for getting of CCvcs for 9A-sample (see LL12 - 9A sample); --- CCV - value of CCvcs from OnLine VCs calibration; 1.03 - Relation Coefficient for VCs-channel at 9A sample. do '/vcd=((vcdep/(5.098))*(CCV)) do 'hs(201)=nt(100)(etrec*0.9993+(pdrec-vcdep)*1.01871+vcd*1.03)@(xc)' mean = 27.54 GeV; Sigma =1.18 GeV 16.05.1996 ===== Calibr ==== H1KFOM === CCe14 behaviour with time(95) Last value for CCe14 at OnLine was fixed as 26.348. Minimal value - 5.59. Strong degradation was fixed during 'second' high rate accident (July 1995) - near 100% and there was no relax behaviour as at another ET-channles Photomultipliers. From July up to November'95 it was fixed smooth degradation on the next 270%. DataTaking'95 was finished with et14 response decremented on factor 4.7 in compare with May'95 at Luminosity subbranch. It is needed to note that Relation Coefficient for this channel smoothly was changed from 0.730 to 0.233 (little less factor 3). It means that e14 response at photoproduction branch had degradation factor significantly less then et14 response at luminosity subbranch. May be at this case Photomultiplier is OK - may be something happened at another places. et14 is unique channel at ET - at this channel CC at luminosity subbranch changed on +370% (!) from start value - degradation factor 4.7 per 190 days. et14 is not hot channel and problem with this channel is not so important but there is some evidence on something not good at this channel. 16.05.1996 ===== Calibr ==== H1KFOM === Hot Channels CCet (95) There is set of most probable values of CCet produced with OnLine Calibration (MeV/FADCunit) - for Luminosity subbranch (hot channels): e21=8.198 e22=5.625 e23=6.514 e24=6.769 e25=6.429 e26=6.560 e27=6.042 e28=7.253 e29=4.942 e30=7.162 e31=5.286 e32=6.408 e33=6.350 e34=5.066 There is set of mean values of CCet produced with OnLine Calibration (MeV/FADCunit) - for Luminosity subbranch (hot channels): e21=7.781 e22=5.657 e23=6.606 e24=6.983 e25=6.736 e26=6.846 e27=6.098 e28=7.049 e29=5.764 e30=7.308 e31=5.292 e32=6.449 e33=6.662 e34=5.440 There is set of min values of CCet produced with OnLine Calibration (MeV/FADCunit) - for Luminosity subbranch (hot channels). This values at most of channels were fixed 22.05.1995: e21=6.233 e22=4.500 e23=5.459 e24=5.254 e25=4.444 e26=4.445 e27=4.663 e28=5.867 e29=4.019 e30=5.654 e31=4.204 e32=4.711 e33=4.855 e34=4.370 There is set of max values of CCet produced with OnLine Calibration (MeV/FADCunit) - for Luminosity subbranch (hot channels): This values at most of channels were after high rates accident 27.07.95 e21=9.114 e22=7.343 e23=8.460 e24=9.642 e25=8.993 e26=7.806 e27=7.977 e28=8.957 e29=7.205 e30=9.157 e31=8.285 e32=11.081 e33=9.462 e34=6.426 There is set of sigma values of CCet produced with OnLine Calibration (MeV/FADCunit) - for Luminosity subbranch (hot channels): e21=0.421 e22=0.206 e23=0.227 e24=0.370 e25=0.546 e26=0.487 e27=0.340 e28=0.374 e29=0.738 e30=0.290 e31=0.285 e32=0.603 e33=0.481 e34=0.443 For producing of high mentioned values it were used all 1.4 million ETPDnVC events from G- and M- H1Runs which were collected during 190 days from 22.05.1995 up to 27.11.1995 into LUMIMON-data sets. Most probable values were got from LOOK peak finder. Mean,sigma,min and max values were got from statparm of CCet-histos. With time stability criterium: Channels e22,e23,e27,e30,e31 and e32(?) are best from hot channels. Channel e29 is most bad from hot channels (most bad sigma). With response value criterium: Channels e31,e34,e22,e29 had smallest CCs from hot ET-channels (largest responses from hot ET channels)-mean value is less then 6 MeV/FADCunit. Channels e21,e30,e28 had largest CCs from hot ET-channels (smallest responses from hot ET channels)-mean value is more then 7 MeV/FADCunit. 17.05.1996 ================= H1KFOM === ETPDVC Bad Xpd-reconstruction As it was remarked earlier (see minutes of the First LUMI working group meeting) there is bad Xpd coordinate reconstruction for ETPDVC-samples during all period of work with new VC (1995 year). There is some evidence that "responsibility" for this situation brings some tuning constant (EVMINW) at LREC1.f-subroutine: At current release this threshold for switching on different the center of gravity coordinates algorithmes is installed on 1.5GeV value: PARAMETER (ERRM =0.20, FITCUT=0.1, W0=4.0, EVMINW=1.5) It means that if EVeto<1.5GeV then "small" shower in front of PD - use a single particle wgt.. else "heavy" shower - use center-of-gravity approximation. It was found with testing of different tuning constant values that the same as 1994 Xpdrec-coordinate distribution is produced with data from data'95 if EVMINW=3.0. 17.05.1996 ================= H1KFOM === Proposal to delete LUMIMONs96 As seems it would be reasonable to delete all produced at 1996 LUMIMON-data set (for today there are 51 data sets with 200Mbyte each - around 10GByte total garbage collection) and to delete all data sets which were written by anybody from H1Lumi-team into /acs/data/96/lumi- pool and to start new life. 17.05.1996 ===== OnLine ==== H1KFOM === OnLine Programs Development Today it was made new releases of TwinFIC1 and TwinFIC1slave programs for FIC1 Master and Slave processors. It were made changings at 3 subroutines (Master - ReadNC.f; Slave - ReadNCs.f, ReadVETEbankS.f) Changings are connected with assembler insertions into mentioned subroutines for decrementing as more as possible FER-delay from our branch. These are creation dates and memory sizes of last releases: TwinFIC1...............MPST MPS .....91288 Fri, May 17, 20:00 1996 M TwinFIC1slave..........MPST MPS .....43762 Fri, May 17, 20:00 1996 M Release is kept at H1Lumi:HD_LPI5:MPW:FomenkoAfter15.04.96:Applications -directory. Releases were tested with H1CDAQ (H1Run 138688) with Random Trigger Omega-Rate (part of Run with LFNC-bank off)-49 Hz/171Hz with Farm Off. 17.05.1996 ================= H1KFOM === First HERA p-beam'96 Ramping Today near 15:25 it were injected 9 p-bunches with Iptotal near 0.8mA (Injection Energy = 39.73 GeV). This p-beam was very slow ramped up to 70 GeV. Ramping was finished at 17:49 with Ip total 0.18 mA. Up to now (20:40) p-beam with 70 GeV protons is living at HERA p-ring with Ip total 0.07 mA. 21.05.1996 ===== OnLine ==== H1KFOM === OnLine Programs Development Today it was made new releases of TwinFIC1 and TwinFIC1slave programs for FIC1 Master and Slave processors. It were made changings at 8 subroutines (Master - L2KeepSub.f, IlevelA.f, OutBanks.f, InitConstant2 CreatePointers.f, Slave - IlevelA.f,InitConstant2.f,CreatePointers.f). It were added 2 new subroutines (ReadVC.f and DecodVC.f). Changings are connected with involving separate reading for VCs and VCv channels from all PD-channel (40nsec shifted FADC window) and some changings are connected with bug fixed for ET44/ET8 'Tracker' Data delivering into LRE1/LR2F-banks (OutBanks.f). These are creation dates and memory sizes of last releases: TwinFIC1...............MPST MPS .....92806 Tue, May 21, 16:33 1996 M TwinFIC1slave..........MPST MPS .....44274 Tue, May 21, 16:33 1996 M Releases are kept at H1Lumi:HD_LPI5:MPW:FomenkoAfter15.04.96:Applicati- ons-directory. Today it was made new release of H1LumiOnLineFIC2-program with updating of 4 subroutines (LumiBranch.f,LumiBranch44.f,PDdepMaker,f and Monitor.f). Changings are connected with involving separate reading for VCs and VCv channels from all PD-channel (40nsec shifted FADC window) and Monitor.f is updated by Egor at 19.05.96. H1LumiOnLineFIC2.......MPST MPS ....244448 Tue, May 21, 17:48 1996 All releases are not tested yet. 22.05.1996 ===== OnLine ==== H1KFOM === OnLine Programs Development Today it was made new releases of TwinFIC1 and TwinFIC1slave programs for FIC1 Master and Slave processors. It were made changings at 2 subroutines (Master - ReadOutVC.f, Slave - IlevelA.f). Changings are connected with bug fixing at mentioned subroutines. These are creation dates and memory sizes of last releases: TwinFIC1...............MPST MPS .....93334 Wed, May 22, 13:06 1996 M TwinFIC1slave..........MPST MPS .....44894 Wed, May 22, 13:06 1996 M Releases are kept at H1Lumi:HD_LPI5:MPW:FomenkoAfter15.04.96:Applicati- ons-directory. Today it was made new release of H1LumiOnLineFIC2-program with updating of 2 subroutines(ReadOutVCLUMI.f and Monitor.f-Egor's update). H1LumiOnLineFIC2.......MPST MPS ....244432 Wed, May 22, 13:06 1996 Releases were tested with H1CDAQ (Runs 139229,139236,139238). Sometimes LFNC-bank involving crashed work of programs. 24.05.1996 ===== OnLine ==== H1KFOM === OnLine Programs Development Today it was made new releases of TwinFIC1 and TwinFIC1slave programs for FIC1 Master and Slave processors. It were made changings at 4 subroutines (Master - IlevelA.f,InitConstant2.f; Slave - L2KeepSub.f, ReadFNC.f). Changings are connected with involving of monitoring tools for pulse disposition inside FADC windows for all detectors at Photoproduc- tion subbranch and involving of reaction on L3Reject-flag from H1CTRIG at FNC-readout chains. These are creation dates and memory sizes of last releases: TwinFIC1...............MPST MPS .....93816 Fri, May 24, 11:13 1996 M TwinFIC1slave..........MPST MPS .....44982 Fri, May 24, 12:43 1996 M Releases are kept at H1Lumi:HD_LPI5:MPW:FomenkoAfter15.04.96:Applicati- ons-directory and put as default releases wor WatchDog-service. Today it was made new release of H1LumiOnLineFIC2-program with updating of 5 subroutines (Main.f,InitConstant1.f,InitConstant2.f, LumiBranch44.f and PDdepMaker.f). Changings are connected with involving of new monitoring tools for pulses disposition inside FADC windows for ETPDnVC,ETPDVC,VCv and ET44VC-events at Lumi- subbranch. These are creation date and memory size of last release: H1LumiOnLineFIC2.......MPST MPS ....245856 Fri, May 24, 14:45 1996 All releases are not tested yet. 27.05.1996 ================= H1KFOM === First HERA e-beams'96 ....... At 25.05 near 20:20 it was fixed first HERA e-beam'96. Electron beam studies was continued up to today morning (near 08:00). Ie total max during 38 hours HERA e-beam activity was not more then 5.0 mA (at 22:20 26 May 1996). 27.05.1996 ===== OnLine ==== H1KFOM === LFNC-bank is Off (temporary). Due to some problems with FNC-readout at last time - this bank was Off from H1Lumi Readout chains. Last H1Run with LFNC-bank - 139705 (24.05.96 23:22). Luminosity branch is working at H1CDAQ with latest TwinFIC1-programs releases without LFNC-bank from H1Run 139852(26.05.96 10:52) up to now - H1Run 139969 (27.05.96 11:23) without problems. 27.05.1996 ===== OnLine ==== H1KFOM === OnLine Programs Development Today it was made new release of TwinFIC1 program for FIC1 Master processor. It were made changings only at one subroutine - OutBanks.f. Changings are connected with involving into LUMM-banks of 4 new variables connected with monitoring of PDdep/PDrec averaging values. These are creation date and memory size of last release: TwinFIC1...............MPST MPS .....94320 Mon, May 27, 13:53 1996 M Release is kept at H1Lumi:HD_LPI5:MPW:FomenkoAfter15.04.96:Applications -directory and put as default release for WatchDog-service. Today it was made new release of H1LumiOnLineFIC2-program with updating of 4 subroutines (InitConstant1.f,PDdepMaker.f,PDrecMaker.f and LUMMbankFill.f).It was added new subroutine MonitoringPDdepPDrec.f. These are creation date and memory size of last release: H1LumiOnLineFIC2.......MPST MPS ....246590 Mon, May 27, 14:15 1996 Release is kept at H1Lumi:HD_LPI5:MPW:FomenkoAfter15.04.96:Applications -directory and put as default release for WatchDog-service. All releases are booted into FICs today after 14:17 and not tested yet. LUMMbank is incremented now on 4 LongWords and has new lenght 740. Last 4 longwords can be described as the next lines: 735 PDDEP1 I 0 30000 ! Mean Value of Photon Arm Deposited ! Energy after analysis of the last 50 ! PDlow triggered events (MeV) 736 PDDEP2 I 0 30000 ! Mean Value of Photon Arm Deposited ! Energy after analysis of the last 1000 ! PDlow triggered events (MeV) 737 PDREC1 I 0 30000 ! Mean Value of Photon Arm Reconstructed ! Energy after analysis of the last 50 ! PDlow triggered events (MeV) 738 PDREC1 I 0 30000 ! Mean Value of Photon Arm Reconstructed ! Energy after analysis of the last 1000 ! PDlow triggered events (MeV) 30.05.1996 ===== OnLine ==== H1KFOM === OnLine Programs Development Today it was made new releases of TwinFIC1 and TwinFIC1slave programs for FIC1 Master and Slave processors. It were made changings at 5 subroutines (Master - L3Reject.f,L3Keep.f,OutBanks.f; Slave - L2Keep.f, ReadVETEbankS.f). Changings are connected with removing of L3Keep/L3Reject-interrupts from Slave processor - it will make possible to work with FNC-readout again. Bug was removed at OutBanks.f subroutine which produced BOS- structure errors at last release. These are creation dates and memory sizes of last releases: TwinFIC1...............MPST MPS .....94288 Thu, May 30, 12:22 1996 M TwinFIC1slave..........MPST MPS .....45022 Thu, May 30, 12:22 1996 M Releases are kept at H1Lumi:HD_LPI5:MPW:FomenkoAfter15.04.96:Applicati- ons-directory and put as default releases wor WatchDog-service. Releases were boot into FIC1s before H1Run 140382. LFNC-bank had appeared at H1DataFlow again and BOS-structure error messages disappeared from Message window at H1CDAQ Supervisor. 31.05.1996 ================= H1KFOM === H1Runs 140550,140551,140564 Today during HERA e-filling which existed from 16:10 up to 21:30 after end of e-beam ramping H1Lumi Movable Platforms were put into working position. FADC Shifts were tuned on standalone e-beam (shifted on 20 nsec): ET32 (195->197), PD (138->140), ET44 (186->188) at Photoproduction subbranch and ET32 (147->149), PD (91->93), ET44 (138->140) at Luminosity subbranch. It were recorded next H1Runs with S86,S90-S95-subtriggers: with CentralTrigger+Lumi only at ReadOut: 140550 16:35-16:40 Ie=11.2 mA 13285 events (prescale tuning) 140551 16:40-16:48 Ie=10.8 mA 34435 events (equal quota of each STs) with all availbale branches at ReadOut: 140564 17:14-17:15 Ie= 8.1 mA 2430 events. All mentioned H1Runs were recorded with temporary logging mode (975th and 976th temporary data sets of this year). 02.06.1996 ================= H1KFOM === H1Runs 140671-140674....... Tonight during HERA e-filling (22:30-23:50 01.06.96) H1Lumi Movable Platforms were put into working position and with corrected on 20 nsec FADC shifts (as it was made at previous H1Lumi Dedicated Runs - see message at LLO from 31.06.1996) it were recorded 4 H1Lumi Dedicated Runs with S86,S90-S95 subtriggers and with H1CentarlTrigger+Lumi only at ReadOut: 140671 23:27-23:30 Ie= 4.0 mA 286 events (default prescale gaps) 1.7Hz LogRate; LFNC On; Mode 1 140672 23:30-23:33 Ie= 4.0 mA 9133 events (zero prescale gaps) 50.0Hz LogRate; LFNC On; Mode 1 140673 23:34-23:52 Ie= 4.0 mA 153376 events (equal guotas of all Sbtrs and DeadTime 99.5%) 150.0Hz LogRate; LFNC Off; Mode 1 140674 23:52-23:53 Ie= 3.8 mA 6775 events (equal guotas of all Sbtrs and DeadTime 13.1%) 62.2Hz LogRate; LFNC Off; Mode 1 All mentioned H1Runs were recorded with temporary logging mode (from 986th up to 988th temporary data sets of this year). Farm and L4 were off due to (as it was found earlier) LREF,LRPF and LR1F-banks are killed at Farm. S.Levonian made correction of this situation before 1st May of this year but up to now this release of H1REC is not installed at L4. 02.06.1996 ===== Calibr ==== H1KFOM === H1Runs 140671-140674 Rel.Coef It were selected from 3 mentioned at previous message temporary data sets of this year (986th,987th and 988th) next events: ETPDnVC - 31075 events ETPDVC - 30125 events S9291 - 46636 events (15725=S92, 29981=S91 and 930 both S92&S91) ET44VC - 17396 events S93 - 34613 events. It was made attempt to produce Relation Coefficients Set for H1Runs 140461-140674 data sample. It were got 31075 ET&PD&nVC from these Runs and it were used for calibration 19423 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.924 0.521 0.960 2.315 0.730 0.999 0.998 0.203 0.566 0.951 0.564 0.746 0.556 0.939 0.811 0.966 0.790 0.841 0.960 0.969 0.804 0.776 1.109 0.892 1.012 0.911 0.926 1.027 1.985 0.623 1.093 0.735 0.788 1.431 0.876 0.996 0.945 1.018 1.181 0.971 1.023 0.000 ==> Relation Coeff.Set for PD 2.390 1.434 1.093 1.117 1.000 1.237 1.214 1.140 1.181 0.863 1.052 1.255 1.193 1.200 0.979 1.239 1.188 1.032 0.844 1.028 1.098 1.021 1.411 1.053 1.000 It were analized ETrec+PDrec energy distribution with using of these Relation Coefficients and CCvcs=2.581 MeV/FADCcount: Runs 140671-140674 (ET&PD&nVC-sample - near 31K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.34 1.66 27.22 1.68 27.49 1.69 Runs 140671-140674 (ET&PD&VC-sample - near 30K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.34 1.65 27.42 1.65 As start values of Calibration Coefficients for Photoproduction Branch were got ones from yesterday (not-proclaimed at LLO) attempt of calibration with data collected at H1Runs 140550,140551 and 140564. CCvcs value was got from the same sample CCvcs calibration procedure. (CCvcs start = 2.581 MeV/FADCcount). CCvcs became less (factor 2.5-3) in compare with last year due to FADC window for VCs-pulse is shifted on 40 nsec at this year and all VCs pulse is seen inside this window but not only forward front as it was earlier. May be due to this reason energy resolution for ETPDnVC and ETPDVC became more or less egual (see some investigations of energy resolution values from digitization mode - LLO 24.04.96). Attempt to make fit of PhotonArm Energy spectrum was non-standard due to very non-standard shape of this spectrum at this sample and at previous one (140550-140564) but (as seems) is right. Non-standard shape of PhotonArm Energy spectrum is connected with non-standard behaivour of VCeff=f(PhotonArmEnergy). Between 10.0 GeV and 18 GeV VCeff has values 0.95-0.99 (it means that nVC trigger significantly is changing PhotonArm Energy spectrum at this energy region - spectrum has "anti-peak" at this region. VCeff = 0.85 at all another energy regions up to threshold value and up to two-photons area (more then 28 GeV). May be with current e-beam conditions energy region 10-18 GeV is connected with 2 photons presence at Photon Arm (ordinary VCeff -> 1.0 if 2 photons presence probability is enough high). 02.06.1996 ===== Calibr ==== H1KFOM === PDREC-spectra for Run 140671 Today it were produced 100th ntuple for S92=1 events from earlier mentioned data sample with events from Runs 140671-140674: H1KFOM.LOOK.R140671.S9291 FAST09 3010200E 00000 DASD At interactive LOOK-session it was produced 70th histo for this data set and written into the next LOOK-binary data set: H1KFOM.BLOOKQ2.R140671 FAST02 3010200E 00000 DASD First attempt to fit 70th histo at BLOOKQ2-data set put positive sign of Global Energy Shift at Photon Arm (+0.75% ) and more or less good resolution digits (15-16%) for (20-22)-35GeV regions. It were prepared 100th tuples with ET&PD&nVC and ET&PD&VC-events for procedure of defining Global Energy Shifts and CCvcs: H1KFOM.LOOK.R140671.ETPDNVC FAST04 3010200E 00000 DASD H1KFOM.LOOK.R140671.ETPDVC FAST02 3010200E 00000 DASD CCvcs value was used as 2.581 MeV/FADCcount for Ntupels making. 02.06.1996 ===== Calibr ==== H1KFOM === Global Shifts,CCvcs Run140671 It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 0.9925 for PD Channels (exept VCs), 1.0192 for ET channels. Correction factor for CCvcs is 0.96. So CCvcs =2.581*0.96 =2.478Mev/ FADCcount. These digits are valid for H1Lumi events from Runs 140671-140674: Runs 140671-140674 (ET&PD&nVC-sample - near 31K events) xetcut&vcdepcut Step Mean Sigma 0 27.50 1.71 Runs 140671-140674 (ET&PD&VC-sample - near 30K events) xetcut Step Mean Sigma 0 27.50 1.67 P.S.Final values of Calibration Coefficients for ET,PD and VCs are next ==> ET Calibr.Coefficients Final Status e00= 4.139 4.609 4.199 3.408 4.061 2.997 3.333 4.470 5.470 5.281 6.641 5.756 4.310 5.525 6.689 2.806 4.935 4.393 2.950 4.579 4.649 5.710 4.691 5.140 5.452 5.458 5.966 4.290 4.786 5.114 5.834 4.437 4.818 4.981 4.679 9.025 4.381 3.231 6.244 4.755 7.568 5.031 e42= 4.277 4.099 4.380 5.184 4.242 4.391 4.285 p00= 2.474 3.170 1.898 2.109 2.915 1.882 2.724 3.742 2.990 1.340 2.377 4.250 3.647 3.409 2.597 3.404 3.062 3.044 2.322 2.388 p20= 2.380 1.792 3.063 2.817 2.908 vcs= 2.478 Energy spectrum VCdep is similar as it was seen at previous year - visible part of spectrum (at linear scale) is finishing near 6.5-7.0GeV P.S. HERA e-beam energy at all last e-fillings after ramping was fixed as 27.50 GeV. 02.06.1996 ================= H1KFOM === Overview of 140671 Data .... From view on data which were recorded at Runs 140671-140674 it is possible to proclaim next preliminary conclusions: 1) No any data from new detectors (ET8-calo signal cabels are not connected, 'ET8 Tracker' and 'ET44 Tracker' data are not seen at LR2F and LR1E-banks - at all 150K events collected during 30 min. no any non-zero status of any 8+13 bits at any from 4/8 bunch x-ings); 2) Thresholds values for PD, PDlow and PDhigh have next values: PDlow - near 6 GeV; PD - near 6.2 GeV; PDhigh - near 16 GeV; It means that almost the same values as at the end of Data Taking'95 3) VCs pulse now seen as full pulse at FADCwindow - not as only forward front of pulse as earlier - it is good. Pulse maximum is disposed at 5th bin of FADC window. CCvcs was decremented on factor 2-2.5 at both OnLine and OffLine Calibration procedures. For PD hot cells pulse maxima are disposed at next bins of FADC window: p15=5 p16=4 p17=6 p18=4 p19=5 p10=4 p11=3 p12=4 p13=3 p14=4 p05=3 p06=3 p07=3 p08=4 p09=4 For ET hot channels pulse maxima are disposed at next bins of FADC window: e28=4 e29=4 e30=4 e31=4 e32=4 e33=5 e34=5 e21=4 e22=5 e23=4 e24=5 e25=5 e26=5 e27=5 4) It was possible to make attempt of this data sample calibration. Problem was with PDrec-spectra from S92-subtrigger - see earlier proclaimed message - as seems - something not good at energy region 10-18GeV and it is connected with strange behaivour of VCeff=f(PhotonArmEnergy) at this energy range too. Final resolution values (1.71GeV for ETPDnVC and 1.67GeV for ETPDVC) are looking as enough pessimistic. May be it is connected with non-standard beam conditions, may be with something else. It is unwaitable that resolution values for ETPDVC-sample became better as for ETPDnVC-sample. May be it is connected with VCs-pulse moving, may be with non-standard beam conditions, may be with some- thing else. 5) Estimated ET32 and ET44 acceptances shapes and parameters are far from 'standard'. Estimation was made with S93-events after finishing of calibration steps. For example: 1)ET32-acceptance has sharp (non- plato) maximum on Ee=14 GeV and this maximum is not 1.0 value but only 0.85; 2) ET44-acceptance has sharp maximum on Ee=23.5GeV and maximum is not 0.5-0.6 value as at standard ep-beams conditions but only 0.25. As seems it is due to non-standard beam conditions. ET32 and ET44 coordinate distributions show poor statistics in compare with standard beam conditions at nearest to e-beam channels. Xet44 is achieving to zero value - it is similar as it was possible to wait when moving part of beam pipe with ET44 will be moved into Working Position at future. 03.06.1996 ================= H1KFOM === HERA e-beams and H1Lumi ..... Tonight during my last night H1Shift it were fixed 2 enough long and more or less stable HERA e-filling. First e-filling was started near 23:08 and finished 03:48, second one - from 03:56 up to 09:36. 1) First e-filling: - 23:08 - start of injections; - 00:00 - end of ramping (Ietot=12.4mA, Ee=27.50GeV); - 00:08 - H1Lumi Movable Platforms were put into working positions; - 00:27 - firstly at this year it was fixed 'bad' situation for future Lumi measurement - "Rate/Current Synchronisation Problem" - at this case - shift on 22 bunch X-ing of first bunch signal. This shift was kept up to end of this filling and during 2-nd filling from start to finish. First 20 minutes after first e-filling "end of ramping" there was not any shift. - 03:36 - H1Lumi Movable Platforms were put into Parking Positions due to HERA proclaimed preparing to beam dump; - 03:48 - e-beam was dumped (Ietot=6.3mA before dump). 2) Second e-filling: - 03:56 - start of injections; - 04:27 - end of ramping (Ietot=14.5mA, Ee=27.50GeV); - 04:36 - H1Lumi Movable Platforms were put into working positions; - 06:35 - firstly at this year it was fixed new 'bad' situation for future Lumi measurement - Bunch Currents were not received from H1Ctrig. This problem was resolved near 09:32. - 06:52 - H1Lumi Movable Platforms were put into Parking Positions due to end of my shift; - 09:36 - e-beam was dumped (Ietot=4.0mA before dump). During these two e-fillings it was continued OnLine calibration of ET, PD,VC and ET44-channels. H1 Data Logging was not operated from 21:20 02 June 1996 - so the set of H1 Runs with S90-S95 subtriggers was used for L4-histos checking.As seems histos are all right exept problem with VCdep-energy. As it was proclaimed earlier - for current H1Lumi data CCvcs is decremented on factor 2-2.5 and seems it is needed to update H1DataBase LFRC-bank with this new CCvcs value (as minimum). Egor's LongHistory-application operated this night and it is possible to see all H1Lumi trigger elements and subtriggers rate behaviours with time during both e-fillings (as seems more or less reasonable): 00:08 03:36 04:36 06:52 VCtotalRate(C0-scaler) 575kHz -> 144kHz 570kHz -> 173 kHz PDtotalRate(C8-scaler) 191kHz -> 54kHz 230kHz -> 68 kHz ETPDtotRate(C4-scaler) 60kHz -> 17kHz 78kHz -> 23 kHz ET32totRate 82kHz -> 22kHz 104kHz -> 30 kHz ET44totRate 68kHz -> 20kHz 87kHz -> 25 kHz 03.06.1996 ===== Calibr ==== H1KFOM === New CCvcs at H1DataBase(LFRC) Today it was updated LFRC banks contents at H1DataBase at dice2-envi- ronment. Only CCvcs value was changed at relation coefficients set of 9A-sample. It was written value 2.478 MeV/FADCcount as CCvcs value. Previous value was 6.336 MeV/FADCcount. As First Run it was put Run Number 140671: Bank-ID Rtyp Dtyp Version 1.Run L.Run Words Date Author Bank LFRC (_501) 91* e-p data 606032226 140671 0 83 960603 fomenk 04.06.1996 ================= H1KFOM === Ie-total = 22.0 mA .......... Yesterday after little day pause HERA e-beam activity alived again near 17:00. Up to today morning it were fixed 6 more or less long and stable e-fillings: 1) 17:49-19:03 Ietotmax=15.3 mA 74 min 3.8mA/hour Ie-degradation 2) 20:53-21:22 Ietotmax=18.2 mA 29 min 4.4mA/hour Ie-degradation 3) 00:39-02:15 Ietotmax=16.2 mA 96 min 4.2mA/hour Ie-degradation 4) 03:12-04:46 Ietotmax=18.1 mA 94 min 5.4mA/hour Ie-degradation 5) 06:15-07:43 Ietotmax=19.6 mA 88 min 5.6mA/hour Ie-degradation 6) 08:27-09:49 Ietotmax=22.0 mA 82 min 4.3mA/hour Ie-degradation 05.06.1996 ================= H1KFOM === HERA e-beams ................ From yesterday evening up to today morning it were fixed 5 more or less long and stable e-filling (all with e-beam ramping up to 27.50GeV) 1) 19:25-20.02 Ietotmax=16.2 mA 37 min 4.7mA/hour degradation 2) 21:58-00:09 Ietotmax=18.0 mA 131 min 4.0mA/hour degradation 3) 01:20-02:14 Ietotmax=20.3 mA 54 min 9.3mA/hour degradation 4) 02:58-04:29 Ietotmax=20.7 mA 91 min 6.2mA/hour degradation 5) 06:07-07:57 Ietotmax=19.6 mA 110 min 5.8mA/hour degradation 05.06.1996 ================= H1KFOM === Ie-total = 30.3 mA .......... From today morning up to today evening it were fixed 2 more or less long and stable e-filling (all with e-beam ramping up to 27.50GeV) 1) 11:12-13:04 Ie-totmax=28.7 mA 112 min 10.4mA/hour degradation 2) 16:52-18:56 Ie-totmax=26.9 mA 108 min 12.0mA/hour degradation Between these two more or less stable and long e-fillings it was injected and lived near 4 min. Ie-total=30.3mA (13:50 today). Without ramping this beam was lost. If You can see into last year e+beam history (for comparison): 20 November 1995; Lumi RUN#961; 12:41-13:56 Ie+totmax=37.7 mA 75 min 5.4mA/hour degradation 21 November 1995; Lumi RUN#962; 05:27-13:17 Ie+totmax=33.0 mA 470 min 3.0mA/hour degradation 25 November 1995; Lumi RUN#971; (Max.Lumi, Max Ie+total at 1995); 22:37-01:35 Ie+totmax=41.4 mA 178 min 3.8mA/hour degradation 06.06.1996 ===== OnLine ==== H1KFOM === OnLine Programs Development Today it was made new release of TwinFIC1slave program for Slave processor. It were made changings at 2 subroutines by I.Sheviakov at 03.06.96 (Slave - L2Keep.f, ReadFNC.f). Changings are connected with making length of LFNC-banks as non-fixed (only 2593 longwords) as it was earler. Changing of LFNC-length is made locally at FNC-readout (Test mode, Standard mode etc.). Simultaneously Igor updated DAQmonitor-application for monitoring of ReadOut Errors at FNC-ReadOut at H1Lumi MacII. These are creation date and memory size of last release: TwinFIC1slave..........MPST MPS .....45110 Thu, Jun 06, 12:15 1996 M Release is kept at H1Lumi:HD_LPI5:MPW:FomenkoAfter15.04.96:Applicati- ons-directory and put as default releases wor WatchDog-service from 03/06/96 18:21. Release was boot into FIC1s before H1Run 140761. LFNC-bank had appeared at H1DataFlow with new lenght (513 LongWords). H1Lumi Dead Time was decremented from 7 msec up to 1.6 msec. Nevetheless Luminosity branch has largest DeadTime at H1 again. 06.06.1996 ================= H1KFOM === HERA e-beams ................ From yesterday evening up to today morning it were fixed 3 more or less long and stable e-filling (all with e-beam ramping up to 27.50GeV) 1) 20:32-21.26 Ietotmax=24.0 mA 54 min 8.1mA/hour degradation 2) 22:38-23:21 Ietotmax=23.4 mA 43 min 12.1mA/hour degradation 3) 03.30-04:24 Ietotmax=25.9 mA 54 min 13.4mA/hour degradation 08.06.1996 ================= H1KFOM === HERA 12 GeV e-beams (Ie=31.7) From yesterday 07.06.1996 18:53 HERA electron beam mashine studies alived again.After short injections with Ie=0.8mA, 1.8 mA, 0.3 mA and 0.6 mA HERA e-team made little pause from 21:45 up to 00:48 and injected (enough slow) 31.7 mA electron beam. Injection was made from 00:48 up to 04:10: 00:48->01:36->01:50->02:45->03:30->03:40->03:50->04:00->04:10 0.4mA- 4.6mA- 9.1mA-11.7mA-15.0mA-19.7mA-24.7mA-28.4mA-31.7mA Ramping was not made and this 12 GeV electron beam lived up to 05:35 (85 minutes). At 05:35 electron beam with Ie=8.7mA was dumped. At this e-filling it was fixed record Ie-total for this year (31.7mA) and "anti-record" with degradation of e-beam current(16.2 mA per hour). 1) 04.10-05:35 Ietotmax=31.7 mA 85 min 16.2mA/hour degradation Problem of bad life time of electron beams with high currents is not resolved as seems. And this problem is not connected with electron beam energy (the same bad degradation factor exists with Ee= 12 GeV as it was fixed for Ee=27.50 GeV). From 05:35 new e-filling was started and from 06:37 during 29 min HERA electron beam with Ee=12 GeV (more or less stable) existed again: 2) 06.37-07:06 Ietotmax=15.7 mA 29 min 2.4mA/hour degradation From 07:42 up to now (12:35) it is making new electron filling. From 08:00 up to 12:00 the 12 GeV HERA e-beam with current near 4.5 mA existed at HERA e-ring with good life time and near 12:00 new injections incremented this Ie-total up to 13.8mA. Machine Studies are in progress now. 09.06.1996 ================= H1KFOM === Ie-total = 33.7 mA (Ee=12GeV) Yesterday at 14:25 it was injected Ie-total=33.7mA. During next some minutes this e-beam was lost. Degradation of e-beam current during last injections is large yet. 1) 14:16-14:24 Ie-totmax=33.1 mA 8 min 23.6mA/hour degradation 2) 15:55-16:48 Ie-totmax=24.3 mA 53 min 12.4mA/hour degradation 3) 17:22-18:45 Ie-totmax=23.9 mA 83 min 13.4mA/hour degradation During (3) e-filling it was made attempt to make ramping - non- succesful - significant part of e-beam was lost. Electron beam studies were continued up to midnight. From 00:00 09/06/96 there are no high current e-beams at HERA e-ring. 10.06.1996 ================= H1KFOM === HERA e-beams ................ From yesterday evening up to today morning it were fixed 5 more or less long and stable e-filling (all with e-beam ramping up to 27.50GeV) 1) 16:37-17.56 Ietotmax=20.7 mA 79 min 9.1mA/hour degradation 2) 19:08-21:00 Ietotmax=25.8 mA 112 min 11.3mA/hour degradation 3) 23.30-00:33 Ietotmax=22.7 mA 63 min 14.2mA/hour degradation 4) 04:07-05:09 Ietotmax=26.9 mA 62 min 15.9mA/hour degradation 5) 07.43-08:05 Ietotmax=22.7 mA 22 min 7.9mA/hour degradation 10.06.1996 ================= H1KFOM === HERA e-beams & H1Lumi ....... Tonight during Yu.Sol. night H1Shift it were fixed 2 enough long and more or less stable HERA e-filling. First e-filling was started near 23:30 and finished 00:33, second one - from 04:07 up to 05:09. 1) First e-filling: - 23:30 - end of ramping (Ie-tot=22.7mA, Ee-=27.50GeV); - 23:35 - H1Lumi Movable Platforms were put into Working positions; - 23:50 - H1Lumi Movable Platforms were put into Parking Positions; - 00:33 - e-beam was dumped (Ietot=7.8mA before dump). 2) Second e-filling: - 04:07 - end of ramping (Ie-tot=26.9mA, Ee-=27.50GeV); - 04:12 - H1Lumi Movable Platforms were put into Working positions; - 04:22 - H1Lumi Movable Platforms were put into Parking Positions; - 05:09 - e-beam was dumped (Ietot=10.5mA before dump). Egor's LongHistory-application operated this night and it is possible to see all trigger elements and subtriggers rate behaivours with time during both e-fillings: 23:35 23:50 04:12 04:22 VCtotalRate(C0-scaler) 1300kHz -> 770kHz 1400kHz ->1100 kHz PDtotalRate(C8-scaler) 595kHz -> 290kHz 706kHz -> 440 kHz ETPDtotRate(C4-scaler) 252kHz -> 130kHz 78kHz -> 23 kHz ET32totRate 432kHz -> 197kHz 560kHz -> 350 kHz ET44totRate 242kHz -> 108kHz 290kHz -> 180 kHz Today morning during last e-filling at 08:05 significant part of e-beam was lost (19.8mA->3.6mA - near 80%) and at this period it were fixed huge rates at some of H1Lumi Detectors: Monitoring Counter: 08:03 - 3.8 kHz (nominal) 08:05 - 1600.0 kHz (start of accident) 08:07 - 2100.0 kHz 08:15 - 2.5 kHZ (back to nominal) 09:10 - e-beam was dumped ET44: 08:03 - 82.0 kHz (nominal) 08:05 - 950.0 kHz (start of accident) 08:10 - 500.0 kHz 08:13 - 250.0 kHz 08:26 - 25.0 kHZ (back to nominal) 09:10 - e-beam was dumped It were fixed high rates at VC and ET32 which were at Parking Positions at this time(08:05-08:07): VCrate(08:05) - 278 kHz; ETrate(08:05) - 53 kHz. PD-rate was zero. As it became clear later - the accident was connected with ramping of H1 solenoid and compensator. 11.06.1996 ================= H1KFOM === HERA p beams ................ From yesterday 15:00 Mashine Study with protons had started. HERA team makes some exersizes with 10 bunch p-beam with Iptotal not more then 0.5 mA. Today morning 0.5 mA p-beam was ramped up to 70 GeV. 14.06.1996 ===== OnLine ==== H1KFOM === OnLine Programs Development At 11.06.96 it was made new release of TwinFIC1slave program for Slave processor. It were made changings at 1 subroutines by I.Sheviakov (Slave - ReadFNC.f). Changings are connected with tuning of FNC-ReadOut on less value of total H1Lumi Dead time. These are creation date and memory size of last release: TwinFIC1slave..........MPST MPS .....45088 Tue, Jun 11, 15:42 1996 M Release is kept at H1Lumi:HD_LPI5:MPW:FICtwin:Inside10thBranch: - -directory and put as default release for WatchDog-service from 11/06/96 16:04. H1Lumi Dead Time was decremented from 1.6 msec up to 1.2 msec. 14.06.1996 ================= H1KFOM === 84 First LUMIMON'96 Scratched Today it were scratched first 84 LUMIMON'96 data sets from /acs/data/ /lumi/96-pool as completely unuseful data. 8.4 Gbytes is free for new LUMIMON'96 collection. Each LUMIMON'96-data set got 100 MBytes of disc/cartridge space (not 200 MBytes as it was at 1995). 16.06.1996 ================= H1KFOM === Iptotal = 36.2 mA ........... Today early morning (from 04:34 up to 04:52) during 18 minutes Iptotal = 36.2 mA was injected into HERA p-ring with three injections. This current lived at HERA p-ring during 40 minutes and at 05:31 was dumped. 17.06.1996 ================= H1KFOM === Iptotal = 40.0 mA ........... Yesterday afternoon near 16:00 HERA had some attempts to deliver stable p-beam for the experiments. First attempt was started at 16:15 when during 20 min (up to 16:35) Iptotal=40.0mA was injected with three injections. This beam was ramped up and when Ep=300 GeV (near 17:15) this p-beam was lost. During ramping it were collected some data for FNC-calibration (H1Runs 142890-142898) with Central Trigger and Luminosity branch only at ReadOut. P-beam lived near 40 minutes after end of injection. Second attempt was started at 20:27 when during 20 min (up to 20:46) Ip total=30.0mA was injected with three injections. After 42 min. p-beam was lost at 21.27 from Ip=27.8mA when Ep=230 GeV. Third (and last) attempt to create stable p-beam conditions was started after midnight (at 01:23) when during 27 min (up to 01:50) Iptotal=29.0mA was injected with three injectins. This p-beam lived up to 02:30 and was lost from Ip=23.0 mA (40 min.) when Ep=300 GeV. So - only not more 300 GeV protons were dilivered for experiments and only some study for p-ramping period was possible for H1 subdetectors. There was no stable p-beam conditions for experiments yesterday before today/tomorrow temporary access period. 20.06.1996 ================= H1KFOM === First e+beams After Access .. Yesterday near 20:20 first positron beam had appeared at HERA e-ring after last access (17-18.06.1996). During 12 hours (up to 08:50) e+beam existed at HERA e-ring with Ie+total not more then 0.5 mA. 20.06.1996 ================= H1KFOM === FNC-ReadOut is Temporary Off. Today morning (near 07:20) FNC ReadOut was temporary off from H1Lumi ReadOut due to some problems at local FNC ReadOut. It was made during H1 Run 143533. 21.06.1996 ================= H1KFOM === First e+beam Ramping'95 .... Today from 13:25 HERA e+beam activity had started. During first injection (at 13:25 Ie+total=2.2 mA with 30 bunches) e+beam was not ramped and was partly lost at 15:36 (from 1.8 mA to 0.1 mA) and existed up to 17:07 with this low current and Ee=12GeV. During second injection (at 17:24 Ie+ total = 2.5 mA with 21 bunches) e+beam was ramped (from 17:43). But at 18:27 when Ie+total was 2.3mA e+beam life time became bad and beam current degradated up to 1.4 mA during 25 min. At 18:52 more then half of e+beam current was lost (1.4mA->0.5mA). During 19:02-19:06 period something happened again (Ie+ 0.5mA->0.2mA) with large rates at Monitoring Cherenkov Counter and ET44 (333kHz and 281 kHz) during 4-5 minutes.Up to now (21:45) e+beam with Ie+=0.1mA and with Ee+=27.54 GeV exists at HERA e-ring. 22.06.1996 ================= H1KFOM === HERA e+beam Activity .... Tonight it were fixed two more or less long and enough high current e+fillings. First e+filling injections were started near 01:00 and at 01:59 Ie+ total was 18.3 mA. Ramping had finished near 02:04. At 02:20 significant part of Ie+ was lost (16.8 mA->2.7 mA). At 02:46 again part of e+beam was lost (1.7mA->0.5 mA). Second e+filling was started at 03:50 and at 04:47 Ie+total = 22.1 mA. At 05:00 ramping was finished. During more then 2 hours e+beam with Ee+=27.54GeV and Ie+ from 19 mA up to 12.7 mA existed at HERA e-ring.At 07:15 20% of e+beam was lost (12.7mA->9.8mA) and at 07:30 beam was dumped. 1) 01:59-02:20 Ietotmax=18.3 mA 21 min 4.3mA/hour Ie+degradation 2) 04:47-07:15 Ietotmax=22.1 mA 148 min 3.8mA/hour Ie+degradation 23.06.1996 ================= H1KFOM === HERA e+beam Activity & H1Lumi From yesterday 11:50 up to tonight 01:35 it were continued Machine studies with positron beams at HERA e-ring. It were fixed five positron fillings. First positron filling was started at 11:52 and at 12:14 Ie+total= 18.9mA. Ramping was finished at 12:20. This e+beam existed up to 14:14. H1Lumi Movable Platforms were put into Working Positions during this filling (from 12:59 up to 14:14). It was found that pipe-line is delayed on near 35 nsec (not 20 nsec as always with standalone e+beam). Beam position was far from nominal (right low corner at PD face). Two next e+fillings were with only 3 bunches and high bunch currents. Second filling was very short - only 6 minutes after end of e+ramping. Third e+filling was enough long - from 15:22 up to 18:47. H1Lumi Movable Platforms were moved into working positions during both fillings (from 14:42 up to 14:48 and from 15:30 up to 17:05) after finishing of e+rampings. At both e+fillings VC-rate was enough high and it was impossible to select 'genuine' ETPDnVC events for BeamPosition monitoring - only random coincidence ETPDnVC-events can be got at Luminosity subbranch. Rate of Monitoring Counter had constant level near 47.4 kHz. It can be explained with presence of VC-signal at each bunch-x-ing. It were fixed absence of correlation between bunch structure of beams and bunch rates at H1Lumi. Rates were presented only for 1st bunch from three bunch currents. It can be explained with far from standard beam conditions. 4th and 5th e+fillings were made without e+rampings (from 20:18 up to 23:11 and from 23:35 up to 00:52) with Ietotal up to 5.3mA. At 01:35 it was fixed last positrons at HERA and after some pause HERA crew began Machine Studies with protons today morning near 06:00. 23.06.1996 ================= H1KFOM === OnLine Lumi with PhotonArm At Friday 21.06.1996 V.Andreev presented first release of proposal for OnLine Luminosity Measurements Procedure with Photon Arm Rate method: I. Some important milestones: 1) it was proposed to install 'visible' cross section for PhArmLumiMeasurements as value 63.875 mb - calculated with MonteCarlo for effective threshold value 6.0GeV with so called threshold sharpness sigma as 0.65 GeV (309.72031 mb is total cross section) [zero tilt and zero beam offset]; 2) This effective threshold with mentioned sharpness characteristic is monitoring with so called average reconstructed energy at H1Lumi Photon Arm with PD-trigger (PD or PDlow type) with value =13.222 GeV (from Monte Carlo calculations); 3) P(ngamma) = near 3.2%*L from H1-02/96-471 for pile-up effect accounting. P(ngamma) - probabililty of presence at one bunch-crossing more then 1 gamma from bremstrahlung processes. L-value can be got from ET*PD-method. II. Procedure steps: 1) Pile-up effect shifts the average reconstructed energy at H1Lumi Photon Arm with PD-trigger (PD or PDlow type) [] on next value: y[%] = -0.015 + 0.269*P(ngamma) - 0.0025*(P(ngamma))**2 So from meas we make true less then meas true = meas/(1.+y) 2) there is some expression for correction of sigma visible on shifted threshold (due to non 13.222 GeV true): y = 4.331-0.371*true + 0.009*(true)**2 So - effective cross section visible: Sigmaeff = (63.875 mb)*y 3) Accounting of pile-up on the PD/PDlow-rate: a)P(ngamma) = near 3.2%*L; b)Rate(meas)=(1-P(ngamma))*Rate(true)+P(ngamma)*Rate(true)*delta = = Rate(true)*[1.+P(ngamma)*(delta-1)] delta is value more then 1. and accounts incrementing of Rate (meas) due to more then 1 brems.photon at one bunch x-ing; c)Rate(true)=Rate(meas)*(1./(1.+P(ngamma)*(delta-1))) = = Rate(meas)*DELTA; d) (delta-1)=0.1 for E=10 FeV; (delta-1)=0.05 for E=5 GeV; e) [mkb-1sec-1] [%] DELTA [0-1] 1. 3.2 0.998 2. 6.4 0.997 3. 9.6 0.995 4. 12.8 0.994 5. 16.0 0.992 6. 19.2 0.990 7. 22.4 0.989 8. 25.6 0.987 9. 28.8 0.986 10. 32.0 0.984 f)Rate(meas) means Rate(total)-Rate(bkgr). III. Acceptance correction with tilt changing was made earlier. P.S. Open questions: a) at OnLine we have PhotonArm Trigger for calculation of average reconstructed energy as VC (S93-analog) and (for LUMMbank) is calculated with Trigger PDlow*VC - it is needed to find some dependences between: PDlow = f(S93(PDlow)) and meas = PD = f(PDlow) b) at OnLine we have not GlobalEnergy Shifts defining - so from LUMM bank can be systematically shifted - it is needed to find some dependences between: S93(PDlow)online = f(S93(PDlow)offline) meas = PD = f(S93(PDlow)online) 24.06.1996 ================= H1KFOM === First e+p collisions'96 ... Today early morning it was made first at this year attempt to make e+p collisions. HERA produced first 0.01 nb-1. p-beam was lost at 06:19. 24/06/96 =================== A.Usik === Lumi RUN# 976 Start - End of Run 976: 24/6/96 5:48:26 - 6:20:52 Collision time for H1Run - physics: 6:20:43 - 6:20:52 Currents at the begining (mA): Ie= 5.45, Ip= 4.52 max lumi value, (last record): 0.012, (6.012) mkb-1 s-1 max sp.Lumi value, (last record): 0.026, (0.553) mkb-1 s-1 mA-2 collided bunches = 0 e+(-) bunches = 48, p-bunches = 0 e-pilot b. = 48, p-pilot b. = 0 HERA total lumi: 0.01 nb-1 HERA - physics: 0 nb-1 H1Run - physics: 0 nb-1 H1data - physics: 0 nb-1 H1 operation eff.: 0 % , DT corr.: 0 % , Tot eff.: 0 % H1 Runs: 144000 - 144002 25/06/96 =================== A.Usik === Lumi RUN# 977 Start - End of Run 977: 25/6/96 5:37:44 - 7:26:13 Collision time for H1Run - physics: 7:26:06 - 7:26:13 Currents at the begining (mA): Ie= 10.92, Ip= 31.52 max lumi value, (last record): 0.002, (6.012) mkb-1 s-1 max sp.Lumi value, (last record): 0.003, (0.553) mkb-1 s-1 mA-2 collided bunches = 0 e+(-) bunches = 0, p-bunches = 180 e-pilot b. = 0, p-pilot b. = 180 HERA total lumi: 0.01 nb-1 HERA - physics: 0 nb-1 H1Run - physics: 0 nb-1 H1data - physics: 0 nb-1 H1 operation eff.: 0 % , DT corr.: 0 % , Tot eff.: 0 % H1 Runs: 144150 - 144157 25.06.1996 ================= H1KFOM === Second e+p collisions'96 ... At last night before midnight (23:05) it was injected p-beam with Iptotal=41.0mA. This beam was ramped up to 820 GeV after enough long pause. At 03:49 e+beam injection was started and at 05:20 e+beam was ready with Ie+total=11.7 mA. At 05:35 e+beam ramping was finished and H1Lumi Movable Platforms were moved into Working positions. During almost 2 hours HERA team was finding of Luminosity at H1 IP but without success. At 07:20 e+beam was dumped. P-beam is living up to now (09:50). Luminosity at ZEUS IP was not seen too. Good news - PDtotal rates at HistoMemory and at C8-TTL-register had similar values during this e+filling (at previous Lumi RUN - PDtotal rate calculated from C8-TTL-register was more then PDtotal Rate calculated from HistoMemory on 7-10(16)%). It is important for involving of PhotonArm Rate Method of OnLineLumi calculation. 25.06.1996 ================= H1KFOM === Integrated Lumi Values(PhArm) During Lumi RUN#977 some Integrated Lumi with PhotonArm Method were collected. It is intersting to compare with coincidence method: PhArmRate Method ET*PD Rate Method HERA produced 9.127*10**30 cm-2 10.393*10**30 cm-2 H1 Gated 8.225*10**30 cm-2 9.118*10**30 cm-2 H1 Data Taken NAN 9.397*10**30 cm-2 All Integrated Lumi values calculated with PhArmMethod are less than ones calculated with coincidence method on 11-12%. It means (may be) that SigmaVisible (59.5mb) value is more than real - PD threshold is more then it was supposed. And from another hand - due to new ET-position (more closely to e-beam) - it is needed to recalculate visible BH cross-section for ET&PD-method and (as V.Andreev pridicts) this value will be more then existing on 5-6% (see message of Yu.Soloviev from 15.04.96). Today procedure of zeroing of Integral Lumi Values calculated with PhotonArmRate method was involved into "Reset Int.Lumi" button at T_MonitorNC-application. Struggle with NAN-values must be added too on some from monitoring applications. 25.06.1996 ===== OnLine ==== H1KFOM === OnLine Programs Development Today it was made new release of TwinFIC1slave program for Slave processor. It were made changings at 3 subroutines by I.Sheviakov (Slave - main.f,ReadFNC.f,L2KeepSub.f). Changings are connected with tuning of H1LumiReadOut on less value of "FNCReadOutReady" waiting time and on switching off LFNC-banks from H1LumiDatFlow at case of problems at FNC ReadOut. These are creation date and memory size of last release: TwinFIC1slave..........MPST MPS .....45088 Tue, Jun 25, 16:22 1996 M Release is kept at H1Lumi:HD_LPI5:MPW:FomenkoAfter15.04.96:Applicati- ons-directory and will be put as default release for WatchDog-service at nearest time. 25.06.1996 ===== OnLine ==== H1KFOM === OnLine Programs Development Today it was made new release of H1LumiOnLineFIC2-program with updating of 10 subroutines (InitConstant1.f,PDdepMaker.f,PDrecMaker.f, EETEPDMonit44.f, SumEnergy44.f, SumEnergyETPDVC.f, Calibration44.f, SumEnergy.f,InitConstant2.f and Calibration.f). Changings were connected with updating of numbers for averaging of PDDEP1, PDDEP2, PDREC1, PDREC2 values from 50/1000 events to 200/500 events as V.Andreev recommended from investigation of this values from LUMIMON'95-data sets and with removing of correction factor 1.18 for EVETO-energy at OnLine (see message from 21.03.1995 at LL11 about reasons of this correction involving at H1 Data Taking'95). Changings were made at main ET,PD-calibration chains connected with selection most 'pure' ETPDnVC-events for calibration and for monitoring at Energy_Hist-appliaction (abs(EVETO)<0.2GeV). These are creation date and memory size of last release: H1LumiOnLineFIC2.......MPST MPS ....246552 Tue, Jun 25, 18:51 1996 Release is kept at H1Lumi:HD_LPI5:MPW:FomenkoAfter15.04.96:Applications -directory and will be put as default release for WatchDog-service at nearest time. Last 4 longwords of LUMMbank can be described as the next lines: TABLE LUMM B32 ! LUmi_Measurements_with_alternative ! _Methods ! (non-event bank at KEEP-environment) ......... 735 PDDEP1 I 0 30000 ! Mean Value of Photon Arm Deposited ! Energy after analysis of the last 200 ! PDlow subsample events at VC-triggered ! OnLine sample (MeV) 736 PDDEP2 I 0 30000 ! Mean Value of Photon Arm Deposited ! Energy after analysis of the last 500 ! PDlow subsample events at VC-triggered ! OnLine sample (MeV) 737 PDREC1 I 0 30000 ! Mean Value of Photon Arm Reconstructed ! Energy after analysis of the last 200 ! PDlow subsample events at VC-triggered ! OnLine sample (MeV) 738 PDREC1 I 0 30000 ! Mean Value of Photon Arm Reconstructed ! Energy after analysis of the last 500 ! PDlow subsample events at VC-triggered ! OnLine sample (MeV) 25.06.1996 ===== OnLine ==== H1KFOM === OnLine Programs Development Today it was made new release of TwinFIC1 program for FIC1 Master processor. It were made changings at 1 subroutine (Master - OutBanks.f) Changings are connected with involving of LumiRUN number into LRTL- bank contents (as last 240th word). These are creation date and memory size of last release: TwinFIC1...............MPST MPS .....94426 Tue, Jun 25, 15:19 1996 M Release is kept at H1Lumi:HD_LPI5:MPW:FomenkoAfter15.04.96:Applicati- ons-directory and put as default release wor WatchDog-service together with early mentioned TwinFIC1slave and H1LumiOnLineFIC2-programs. Releases were boot into FIC1s before H1Run 144214. LRTL-bank has new (incremented on 1) length: TABLE LRTL B32 ! Lumi_Response_Trigger_Luminosity ! (non-event bank at KEEP-environment) ....... 240 LUMIRUN I 0 +INF ! Lumi RUN number 26.06.1996 ================= H1KFOM === HERA p-beam activity ...... Yesterday after end of Lumi RUN 977 it was proclaimed stable p-beam for exeperiments with Iptotal near 30mA and Ep=820 GeV (up to 12:00). Near 12:00 p-beam was dumped and after 4 hours pause (with access of HERA people into tunnel) new p-beam was injected with Ip=34.8 mA but during ramping this beam was lost near 18:00. Next attempt of prepare p-beam was succesful and near 20:30 it was injected p-beam with Iptotal = 32.9 mA. This p-beam was succesfully ramped up to 820 GeV and existed at HERA p-ring up to 01:00. From 02:30 up to 05:20 it were fixed some attempts to inject low current p-beam and at morning (at 06:50) p-beam with Iptotal=27.0mA was injected but life time of this beam is extremly low (5.5 mA per hour degradation - never seen before). This p-beam is not ramped and exists up to now (9:15) with Ip=14.2 mA and with Ep=39.745 (injection energy) and with 120 bunches. 26.06.1996 ===== OnLine ==== H1KFOM === OnLine Programs Development Today it was made new release of TwinFIC1 program for FIC1 Master processor. It were made changings at 1 subroutine (Master - OutBanks.f) Changings are connected with involving of two values into LUMM- bank contents. These two values are calculated at H1LumiTriggerMonitor codes and means 'mean effective PD energies' (old and new releases). These are creation date and memory size of last release: TwinFIC1...............MPST MPS .....94678 Wed, Jun 26, 13:55 1996 M Release is kept at H1Lumi:HD_LPI5:MPW:FomenkoAfter15.04.96:Applicati- ons-directory and will be put as default releases for WatchDog-service at nearest time. Length of LUMM bank is incremented on 2 longwords (742 longwords now) and last 2 longwords of LUMMbank can be described as the next lines: TABLE LUMM B32 ! LUmi_Measurements_with_alternative ! _Methods ! (non-event bank at KEEP-environment) ...... 739 PDETR1 I 0 30000 ! Mean Effective Photon Arm Energy1(MeV) 740 PDETR2 I 0 30000 ! Mean Effective Photon Arm Energy2(MeV) Today it was made new release of H1LumiOnLineFIC2-program with updating of 2 subroutines (InitLumiMonitoring.f and LUMMbankFill.f). Changings were connected with updating of visible cross section value for ET&PD-method of Luminosity measurements and with preparing of values for LUMMbank from Egor's cells (Real->Integer). New value of BH 'visible' cross section is 34.47 mb. This value was calculated by V.Andreev with zero tilt and zero beam offset beam condi- tions. Before today the BH 'visible' cross section was 32.38 mb and was set into OnLine-environment at 21 March 1994. A.Usik promised to change this value at his application too. Changing of this value is connected with new ET position at this year (more closely to e-beam - see message of Yu.Soloviev from 15.04.96). These are creation date and memory size of last release: H1LumiOnLineFIC2.......MPST MPS ....246552 Wed, Jun 26, 12:27 1996 Release is kept at H1Lumi:HD_LPI5:MPW:FomenkoAfter15.04.96:Applications -directory and put as default release for WatchDog-service together with early mentioned TwinFIC1-release. New releases are working before H1Run 144392. First H1Run with new LUMM-format is 144392 (26.06.96,15:10:41) 4C554D4D:LUMM 13 742 742 742 First H1Run with new LRTL-format is 144471 (27.06.96,04:20:18) when first e+beam had appeared after 26.06.96,15:10:41. 4C52544C:LRTL 13 242 242 242 26.06.1996 ================= H01GOG === LH1R bank After changing the LRTL bank, the LH1R bank was now also changed as well, so that it contains one more word.The changes in the TCL RunEnd job (subroutines LH1RU and LH1RS) were done by J.Olsson. A new description of this bank (see below) will soon appear on dice2, command 'lhb'. *-- Author : Sergej Levonian 14/01/93 ! BANKname BANKtype ! Comments ! TABLE LH1R ! Lumi related information for the ! H1 ep-runs ! ATTributes: ! ----------- !COL ATT-name FMT Min Max ! Comments ! 1 RTIME I 0 +INF ! total run time (msec) 2 ATIME I 0 +INF ! active run time (msec) 3 TLUMI I 0 +INF ! total run lumi (mb^-1) 4 GLUMI I 0 +INF ! H1 gated run lumi (mb^-1) 5 IPTOTAL I 0 +INF ! total p-current (mkA) 6 IPPILOT I 0 +INF ! pilot bunches p-current (mkA) 7 IETOTAL I 0 +INF ! total e-current (mkA) 8 IEPILOT I 0 +INF ! pilot bunches e-current (mkA) ! 9 PB0 I -INF +INF ! bit pattern for the p-bunches ( 0- 31) 10 PB1 I -INF +INF ! bit pattern for the p-bunches ( 32- 63) 11 PB2 I -INF +INF ! bit pattern for the p-bunches ( 64- 95) 12 PB3 I -INF +INF ! bit pattern for the p-bunches ( 96-127) 13 PB4 I -INF +INF ! bit pattern for the p-bunches (128-159) 14 PB5 I -INF +INF ! bit pattern for the p-bunches (160-191) 15 PB6 I -INF +INF ! bit pattern for the p-bunches (192-223) ! (0 - empty bunch, 1 - filled bunch) 16 EB0 I -INF +INF ! bit pattern for the e-bunches ( 0- 31) 17 EB1 I -INF +INF ! bit pattern for the e-bunches ( 32- 63) 18 EB2 I -INF +INF ! bit pattern for the e-bunches ( 64- 95) 19 EB3 I -INF +INF ! bit pattern for the e-bunches ( 96-127) 20 EB4 I -INF +INF ! bit pattern for the e-bunches (128-159) 21 EB5 I -INF +INF ! bit pattern for the e-bunches (160-191) 22 EB6 I -INF +INF ! bit pattern for the e-bunches (192-223) ! (0 - empty bunch, 1 - filled bunch) 23 LUFILL I 0 +INF ! Lumi Fill Number, as taken from LRTL END TABLE 26.06.1996 ================= H01GOG === LUMIMON tapes I have change today the code of LUMIEV routine which creates LUMIMON mini-events in the SGI logging job: 1)the new bank (LR2F) was added; 2) only events with standard trigger set (phase 2,3,4) will be written. All LUMIMON tapes (except 3 last) were deleted today, since they don't contain any useful imformation. 27/06/96 ================== I.Kenyon === Lumi RUN# 978 Start - End of Run 978: 27/6/96 8:47:40 - 10:04:17 Collision time for H1Run - physics: 10:04:09 - 10:04:17 Currents at the begining (mA): Ie= 11.61, Ip= 43.07 max lumi value, (last record): 0.004, (6.012) mkb-1 s-1 max sp.Lumi value, (last record): 0.003, (0.553) mkb-1 s-1 mA-2 collided bunches = 111 e+(-) bunches = 123, p-bunches = 180 e-pilot b. = 12, p-pilot b. = 69 HERA total lumi: 0.01 nb-1 HERA - physics: 0 nb-1 H1Run - physics: 0 nb-1 H1data - physics: 0 nb-1 H1 operation eff.: 0 % , DT corr.: 0 % , Tot eff.: 0 % H1 Runs: 144491 - 144493 P.S. Near 09:50 at ZEUS IP the Luminosity was found and existed only some minutes.Positron beam was lost. 27.06.1996 ================= H1KFOM === Lumi RUN# 978 (details) .... HERA p-beam was injected near 01:50 tonight and succesfully ramped up to 820 GeV with 180 bunches. Today morning e+injection was started at 04:20 and at 08:00 e+beam with Ietotal=17 mA and with 123 e+bunches was ready. Ramping of e+beam was finished near 08:22. H1Lumi Movable platforms were put into working positions at 08:46 by H1 Shift Crew. At 09:54 e+beam was lost and at H1 IP the Luminosity was not found. At ZEUS IP the Luminosity was found near 09:50 (Lspec near 0.3mkb-1s-1 mA=2) and existed only 4 minutes. Rates time slices at H1Lumi at this period: 08:46 09:22 09:54 Ie+total 11.8mA 10.2mA VCtotal 90.0kHz 61.5kHz 1700.0kHz PDtotal 24.6kHz 17.5kHz 15.5kHz ETtotal 24.6kHz 15.2kHz 13.6kHz ET44total 14.6kHz 10.4kHz 9.7kHz ET&PDtotal 9.3kHz 6.6kHz 6.0kHz near -0.5cm from -0.7 up to -1.7cm near -0.5cm around 0.0 cm PDtotal rate calculated with TTL-counter(C8) was more on 3.5-1.7% than calculated with HistoMemory. ET&PD total rate is the same at both calculations. After 09:22 (when tilt was changed on another ) VCtotal rate was significantly incremented. Radiation Monitor Rate near 09:54 was fixed as 11.9 kHz (short period) 27.06.1996 ================= H1KFOM === H1Lumi with 12 GeV e+beam .. Today after end of Lumi RUN #978 it was started new e+beam injection at 11:30. During injection period H1Lumi Movable Platforms were put into working positions (from 11:50 when Ie+total=1.1mA up to 13:07 when Ie+total became 6.4mA). ET and PD thresholds were installed on low value (PD - from 3'GeV' to 1.5'GeV' and ET from 5'GeV' to 3'GeV'). Rates time slice at H1Lumi at 13:00: 13:00 (Ie+total=6.4mA, Ip=43.2mA) VCtotal 24.3kHz PDtotal 9.5kHz (PDrate from C8 on 8% more) ETtotal 12.3kHz ET44total - (threshold was not changed) ET&PDtotal 4.5kHz Beam Position was fixed as always for 12 GeV beam - at upper part of face of PD. Reasonable energy histos were built (ETrec+PDrec, ETrec, PDrec etc.) - they are kept at Egor's history files. This e+filling was finished with e+lost during rampimg attempt. 27.06.1996 ================= H1KFOM === Else One Attempt to Make Lumi Last e+filling with existed from 01:40 p-beam was made from 13:50 up to 18:10. At this case H1Lumi Movable Platforms were put into Working Position but next Lumi RUN was not fixed. During last step of e+ramping something happened with p-beam and part of p-beam was lost with producing of huge background conditions at H1 IP (H1 VetoWall Rates were fixed up to 7 MHz, Radiation Monitor rate was more then 1kHz during 20 minutes with Peak Rate near 20kHz). H1Lumi Detectors were put into working positions after end of this accident. Luminosity was not found at both ZEUS and H1 interaction points. At 18:10 both beam were dumped. There are some evidences that PD-threshold became less then it was supposed - it is seen from and Egor's HW (You can check its at LUMM banks) and from Integrated Lumi Values calculated without 'real' Luminosity: PhArmRate Method ET*PD Rate Method HERA produced 5.437*10**31 cm-2 2.967*10**31 cm-2 and from decremention of hot cells OnLine Calibration Coefficients. Some problem was seen with H1 Gated Lumi value calculated with both methods (ET&PD and PhArm) - at 15:27 enough large portion of H1 Gated Lumi was added and H1 Gated Lumi became even more then HERA produced. May be this problem was connected with Warm Starts or some another non-standard H1Lumi interfaces with H1CDAQ at this moment. ETrec+PDrec OnLine Histo for ETPDnVC sample became more pure with absense of low energy ETrec+PDrec events (as seems reaction on last changings at OnLine Program). 28/06/96 ================== soloviev === Lumi RUN# 979 Start - End of Run 979: 28/6/96 5:14:13 - 10:15:27 Collision time for H1Run - physics: 7:01:56 - 10:15:27 Currents at the begining (mA): Ie= 6.07, Ip= 31.76 max lumi value, (last record): 0.436, (6.012) mkb-1 s-1 max sp.Lumi value, (last record): 0.456, (0.553) mkb-1 s-1 mA-2 collided bunches = 114 e+(-) bunches = 126, p-bunches = 180 e-pilot b. = 12, p-pilot b. = 66 HERA total lumi: 3.89 nb-1 HERA - physics: 1.84 nb-1 H1Run - physics: 1.68 nb-1 H1data - physics: 1.34 nb-1 H1 operation eff.: 86 % , DT corr.: 75 % , Tot eff.: 69 % H1 Runs: 144727 - 144734 28.06.1996 ================= H1KFOM === H1Lumi Dedicated Runs ....... Today early morning during Lumi RUN# 979 it was recorded set of H1Lumi Dedicated Runs. S90-S95 subtriggers were ON and Random Trigger with enough large quota was ON too. Farm was OFF for posibility of Raw Data H1Lumi banks transmission into H1DataFlow. FNC-readout was OFF for making of largest data taking rates. Only Luminosity and Central Trigger were at H1 CDAQ ReadOut from 06:25 up to 09:02. Mode 1 was ON at Luminosity branch (LREF,LRPF,LR1F banks were ON). Average logging rate during this period was near 100 Hz. 877341 events were recorded at these H1Runs.Ee+=27.54GeV and Ep=820GeV. 'Luminosity Run' was firstly proclaimed by HERA team at this year. Next H1Runs were recorded: 144729 3461 events Ie=5.6mA Ip=31.0 mA 144730 13916 events Ie=5.6mA Ip=30.9 mA 144731 6967 events Ie=5.5mA Ip=30.9 mA 144732 50597 events Ie=5.5mA Ip=30.9 mA 144733 802400 events Ie=5.4mA->4.3mA Ip=30.9 mA->30.3mA First Runs were recorded during prescale tuning. All these data were recorded on 1 temporary data set and on 8 permanent data sets (1787- -1794). From 09:02 up to end of Lumi RUN it was recorded else one H1Lumi Dedicated Run without Raw data(LREF,LRPF,LR1F) and with LFNC-bank with the same Trigger Setting: 144734 258034 events Ie=4.1mA->3.6mA Ip=30.2mA->30.1mA. Last Run was recorded on 1794-1797 Permanent data sets. 28.06.1996 ===== Calibr ==== H1KFOM === Selection from Dedicated Runs From H1RAWD.C9601787-1797 data sets (1122509 events) it were selected: ->183103 ETPDnVC 16.3% ->144075 ETPDVC 12.8% ->117433 S92 10.5% H1Runs 144730-144734 ->184538 S91 16.4% ->108970 S93 9.7% (2.87GBytes selected from 4.40GBytes) -> 69038 ET44VC 6.2% ->370375 Random 32.4% Selected samples temporary were placed into /acs/data/96/lumi-pool (only ETPDnVC-sample and its index-file), into /shift/dice2/data14/h1/ fomenko/user/fomenko-pool (ETPDVC,ET44VC and S93-samples) and into /shift/dice4/data1/h1/fomenko/user/fomenko-pool (S9291 and RND-samples) I am not sure that it is reasonable to keep all these data samples anywhere. May be after finishing of all attempts of calibration, finding of thresholds values, attempts to find some dependencies = f() = f() etc. it would be reasonable to erase all created additional files. Its always can be remade from H1RAWD-data sets if it will be needed to anybody at future. Selection of any sample gets not more then 30 min. dice3 CPU. 29.06.1996 ===== Calibr ==== H1KFOM === H1Runs 144730-144734 Rel.Coef It were selected from 11 mentioned at previous message permanent data sets of this year (1787th,1788th,...1797th) next events: ETPDnVC - 183059 events ETPDVC - 144075 events S9291 - 301881 events (117433=S92, 184538=S91) ET44VC - 69038 events S93 - 108970 events. It was made attempt to produce Relation Coefficients Set for H1Runs 144730-144734 data sample. It were got 183059 ET&PD&nVC from these Runs and it were used for calibration 111528 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.942 0.550 0.976 2.473 0.762 1.000 1.012 0.293 0.737 0.867 0.647 0.918 0.802 0.791 0.998 0.992 0.887 0.879 1.001 0.910 0.962 0.882 1.010 0.880 1.007 0.930 1.010 0.963 3.008 0.621 0.960 0.741 0.768 1.414 0.834 1.005 0.956 1.017 1.154 0.975 1.014 0.000 ==> Relation Coeff.Set for PD 2.610 1.225 0.885 1.122 0.818 1.020 1.130 1.062 1.077 0.913 1.020 1.022 1.050 1.060 1.083 1.118 1.012 1.075 1.050 1.100 1.107 1.071 1.317 0.977 0.823 It were analized ETrec+PDrec energy distribution with using of these Relation Coefficients and CCvcs=2.478 MeV/FADCcount: Runs 144730-144734 (ET&PD&nVC-sample - near 183K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.64 1.59 27.59 1.58 27.63 1.61 Runs 144730-144734 (ET&PD&VC-sample - near 144K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.05 1.33 27.03 1.25 As start values of Calibration Coefficients for Photoproduction Branch were got ones from calbration 02.06.1996 (see LLO) with data collected at H1 Runs 140671-140674. CCvcs value was got from the same sample CCvcs calibration procedure. (CCvcs start = 2.478 MeV/FADCcount). Attempt to make fit of PhotonArm Energy spectrum with S92-events was enough succesful with very good statistics. 29.06.1996 ===== Calibr ==== H1KFOM === PDREC-spectra for Run 144730 Today it were produced 100th ntuple for S92=1 events from earlier mentioned data sample with events from Runs 140671-140674: H1KFOM.LOOK.R144730.S9291 FAST09 3010200E 00000 DASD At interactive LOOK-session it was produced 70th histo for this data set and written into the next LOOK-binary data set: H1KFOM.BLOOKQ2.R144730 FAST09 3010200E 00000 DASD First attempt to fit 70th histo at BLOOKQ2-data set put positive sign of Global Energy Shift at Photon Arm (+1.657% ) and enough good resolution digits (18-19%) for (8-22)-35GeV regions. It were prepared 100th tuples with ET&PD&nVC and ET&PD&VC-events for procedure of defining Global Energy Shifts and CCvcs: H1KFOM.LOOK.R144730.ETPDNVC FAST05 3010200E 00000 DASD H1KFOM.LOOK.R144730.ETPDVC FAST09 3010200E 00000 DASD CCvcs value was used as 2.478 MeV/FADCcount for Ntupels making. 29.06.1996 ===== Calibr ==== H1KFOM === Global Shifts,CCvcs Run144730 It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 0.98343 for PD Channels (exept VCs), 1.012 for ET channels. Correction factor for CCvcs is 1.285. So CCvcs =2.478*1.285 =3.184MeV/ FADCcount. These digits are valid for H1Lumi events from Runs 144730-144734: Runs 144730-144734 (ET&PD&nVC-sample - near 183K events) xetcut&vcdepcut Step Mean Sigma 0 27.54 1.63 Runs 144730-144734 (ET&PD&VC-sample - near 144K events) xetcut Step Mean Sigma 0 27.54 1.25 P.S.Final values of Calibration Coefficients for ET,PD and VCs are next ==> ET Calibr.Coefficients Final Status e00= 4.139 4.609 4.199 3.408 4.061 2.997 3.333 4.546 5.607 5.362 6.806 5.908 4.312 5.530 7.303 2.072 4.400 4.165 2.799 4.610 4.016 6.635 4.413 5.357 4.956 4.554 5.433 4.266 4.191 4.733 5.901 4.222 4.805 4.939 4.292 13.875 4.266 2.765 6.219 4.759 7.413 4.838 e42= 4.318 4.159 4.375 4.912 4.259 4.346 4.285 p00= 2.681 3.108 1.414 2.083 2.926 1.630 2.730 3.260 2.748 1.383 2.166 2.818 3.199 2.956 2.521 3.345 3.103 3.100 2.273 2.581 p20= 2.379 1.998 2.678 2.583 2.908 vcs= 3.184 Energy spectrum VCdep is similar as it was seen at previous year - visible part of spectrum (at linear scale) is finishing near 6.5-7.0GeV P.S.1 HERA e-beam energy at all last e-fillings after ramping was fixed as 27.54 GeV. P.S.2 It is enough unwaitable than Sigma at Peak Finder for ETPDnVC events ETrec+PDrec spectrum is very large (1.63GeV) and Sigma for ETPDVC events is enough good (1.25 GeV) and resolution values from PhotonArmEnergy Fit is enough optimistic (18-19%). It is not uderstood yet. P.S.3 Something happened with e35-channel response at Photoproduction branch - You can see that 13.875 MeV/FADCcount means something as degradation response on factor 3-4. 29.06.1996 ===== OnLine ==== H1KFOM === OnLine Programs Development Today it was made new release of H1LumiOnLineFIC2-program with updating of 2 subroutines (ReplaceTextBanks.f and LUMMbankFill.f). Changings were connected with tuning of cuts at LRJCT.f-subroutine for decision of current problem with slow updating of beam position (problem was with ET-detector only with current beam optics) and with removing bug from LUMMbankFill.f subroutine connected with wrong retranslating of Egor's Mean Effective Energies. These are creation date and memory size of last release: H1LumiOnLineFIC2.......MPST MPS ....246616 Sat, Jun 29, 22:12 1996 Release is kept at H1Lumi:HD_LPI5:MPW:FomenkoAfter15.04.96:Applications -directory and put as default release for WatchDog-service. New release is working after H1Run 145269. 29/06/96 =================== kenyon === Lumi RUN# 980 Start - End of Run 980: 29/6/96 16:28:51 - 17:11:58 Collision time for H1Run - physics: 17:11:51 - 17:11:58 Currents at the begining (mA): Ie= 18.52, Ip= 41.04 max lumi value, (last record): 0.011, (6.012) mkb-1 s-1 max sp.Lumi value, (last record): 0.003, (0.553) mkb-1 s-1 mA-2 collided bunches = 0 e+(-) bunches = 0, p-bunches = 182 e-pilot b. = 0, p-pilot b. = 182 HERA total lumi: 0.03 nb-1 HERA - physics: 0 nb-1 H1Run - physics: 0 nb-1 H1data - physics: 0 nb-1 H1 operation eff.: 0 % , DT corr.: 0 % , Tot eff.: 0 % H1 Runs: 145084 - 145195 29/06/96 =================== kenyon === Lumi RUN# 981 Start - End of Run 981: 29/6/96 18:32:16 - 21:52:01 Collision time for H1Run - physics: 21:51:35 - 21:52:01 Currents at the begining (mA): Ie= 4.08, Ip= 40.85 max lumi value, (last record): 0.222, (6.012) mkb-1 s-1 max sp.Lumi value, (last record): 0.463, (0.553) mkb-1 s-1 mA-2 collided bunches = 106 e+(-) bunches = 116, p-bunches = 182 e-pilot b. = 10, p-pilot b. = 76 HERA total lumi: 1.76 nb-1 HERA - physics: 0.42 nb-1 H1Run - physics: 0 nb-1 H1data - physics: 0 nb-1 H1 operation eff.: 0 % , DT corr.: 0 % , Tot eff.: 0 % H1 Runs: 145221 - 145265 30.06.1996 ===== Calibr ==== H1KFOM === Global Shifts,CCvcs Run144730 Today it were tuned Global Shifts and CCvcs for data samples from H1Runs 144730-144734 due to Mean values at ETrec+PDrec histos were far from 27.54GeV after involving of early mentioned CCvcs and Global Shifts into last LREC-release (h1rec71301). Second Iteration(fine tuning) of mentioned parameters defining was made with using of ETrec+PDrec peak fit fith Gauss+ax+b. Next results were produced: CCvcs = 3.213 MeV/FADCunit (1.009 tuning constant for previous value) GlobalEnergyShift for PD-channels = 0.9751 (0.9915 - fine tuning) GlobalEnergyShift for ET-channels = 1.030(1.0177 - fine tuning) Results of fit: ETPDnVC-sample (xc&vcc): mean=27.54+-0.006 GeV; Sigma=1.49+-0.005 GeV LOOK peak finder: mean=27.54GeV Sigma=1.63GeV; ETPDVC-sample (xc): mean=27.54+-0.004 GeV; Sigma=1.24+-0.004GeV LOOK peak finder: mean=27.52GeV Sigma=1.25GeV; 01.07.1996 ===== Calibr ==== H1KFOM === Global Shifts,CCvcs Run144730 It was defined after 'fine tuning' that Global Shifts for both H1Lumi arms are: 0.9751 for PD Channels (exept VCs) 1.030 for ET Channels CCvcs =3.213MeV/FADCcount Runs 144730-144734 (ET&PD&nVC-sample - near 183K events) all events xetcut xetcut&vcdepcut Mean Sigma Mean Sigma Mean Sigma 27.58 1.57 27.54 1.55 27.55 1.63 <- PEAKPARM 27.54 1.53 27.52 1.45 27.54 1.49 <- FIT (gauss+ax+b) Runs 144730-144734 (ET&PD&VC-sample - near 144K events) all events xetcut Mean Sigma Mean Sigma 27.54 1.33 27.52 1.25 <- PEAKPARM 27.57 1.35 27.54 1.24 <- FIT (gauss+ax+b) P.S. bins 200 17 34 for ETPDnVC sample; bins 200 22 32 for ETPDVC-sample; fit boundaries (Xmin=22 GeV,Xmax=32 GeV); xetcut=(xet<6.0&xet>-6.0; vcdepcut=(vcdep>-0.2&vcdep<0.2) Photon Arm Global Energy Shift was defined after fine tuning and has next values (95899 events with S92-trigger at 70th histo): +0.03%+-0.2% (for all fit boundaries from 6-35 up to 20-35 GeV). Resolution Values are 18-19%+-0.8%. Mentioned earlier fine tuning results mean that calibration precision is fantasically good (due to huge statistics) -> 0.2%(!!!) We never before (and may be never after) achieved of this calibration precision. It were very good Dedicated Runs samples. Data from these Dedicated Runs were collected during 3 hours and 50 minutes. 01/07/96 ================== goerlich === Lumi RUN# 982 Start - End of Run 982: 1/7/96 0:16:24 - 2:51:55 Collision time for H1Run - physics: 1:12:30 - 2:51:55 Currents at the begining (mA): Ie= 5.5, Ip= 6.72 max lumi value, (last record): 0.022, (6.012) mkb-1 s-1 max sp.Lumi value, (last record): 0.084, (0.553) mkb-1 s-1 mA-2 collided bunches = 17 e+(-) bunches = 42, p-bunches = 50 e-pilot b. = 25, p-pilot b. = 33 HERA total lumi: 0.11 nb-1 HERA - physics: 0.08 nb-1 H1Run - physics: 0.05 nb-1 H1data - physics: 0.04 nb-1 H1 operation eff.: 27 % , DT corr.: 26 % , Tot eff.: 22 % H1 Runs: 145505 - 145573 01.07.1996 ================= H1KFOM === Cross Section for PhArmMethod V.Andreev estimated Cross Section of bremstrahlung for OnLine Photon Arm method Luminosity calculation. For PD-threshold value which was measured at last H1Lumi Dedicated Runs (144730-144734) this value is: Sigma = 65.523 mb (PDthresh=6.0 GeV; Shrp = 0.836 GeV). Sigma is estimated with beam tilt zero and beam offset zero. This value will be inserted into OnLine program at nearest time. 01.07.1996 ===== Calibr ==== H1KFOM === ET44 Rel.Coeff.Set Run144730 Today it were defined Relation Coefficients Set for ET44-channels at events from H1Runs 144730-144734. It were selected 69038 events with ET44VC from mentioned H1Runs which are temporary kept at /shift/dice2/data14/h1/fomenko/user/fomenko-directory (182MBytes). H1KFOM.ET44VC.M787792.C00 H1KFOM.ET44VC.M793797.C00 From these data sets it were selected 18819 events with VC=1 and with using of all earlier mentioned cuts. These events were used for calibration. Channel et01 became again as non-Dead channel. Next cuts were used: 1) Energy deposited at et1,et3 and et5 must be more then 0.60 GeV; 2) 19.1GeV To: "A.M. Fomenko" Subject: BOS errors Thanks for your letters. Concerning DAS4, you should know that this bank comes from Branch 4, CJC. I am quite sure that this error has nothing to do with the errors that occur in Branch 10, i.e. in Lumi. The way to proceed is to find out which banks in the Lumi system are normally coming after LFNC, and after LREP. These banks should be the reason. Probably the pointers to these banks are wrong, for some reason in your software, so that other data is picked up instead of the bank data proper. So, I think the DAS4 problem is a separate problem. But you are right, the errors seem not to be too often. This is both bad and good, bad because it makes the debugging much more difficult, good because not so many events are thrown away... Cheers, Jan ..." 02/07/96 =================== palmen === Lumi RUN# 983 Start - End of Run 983: 2/7/96 22:21:17 - 22:30:57 Collision time for H1Run - physics: 22:28:45 - 22:30:57 Currents at the begining (mA): Ie= 21.4, Ip= 34.10 max lumi value, (last record): 0, (6.012) mkb-1 s-1 max sp.Lumi value, (last record): 0, (0.553) mkb-1 s-1 mA-2 collided bunches = 0 e+(-) bunches = 0, p-bunches = 180 e-pilot b. = 0, p-pilot b. = 180 HERA total lumi: 0 nb-1 HERA - physics: 0 nb-1 H1Run - physics: 0 nb-1 H1data - physics: 0 nb-1 H1 operation eff.: 0 % , DT corr.: 0 % , Tot eff.: 0 % H1 Runs: 146060 - 146060 03/07/96 =================== kenyon === Lumi RUN# 984 Start - End of Run 984: 3/7/96 0:38:26 - 0:48:28 Collision time for H1Run - physics: 0:45:30 - 0:48:28 Currents at the begining (mA): Ie= 24.57, Ip= 33.71 max lumi value, (last record): 0, (6.012) mkb-1 s-1 max sp.Lumi value, (last record): 0, (0.553) mkb-1 s-1 mA-2 collided bunches = 0 e+(-) bunches = 0, p-bunches = 180 e-pilot b. = 0, p-pilot b. = 180 HERA total lumi: 0.02 nb-1 HERA - physics: 0 nb-1 H1Run - physics: 0 nb-1 H1data - physics: 0 nb-1 H1 operation eff.: 0 % , DT corr.: 0 % , Tot eff.: 0 % H1 Runs: 146071 - 146073 03/07/96 =================== kenyon === Lumi RUN# 985 Start - End of Run 985: 3/7/96 1:51:40 - 2:12:17 Collision time for H1Run - physics: 2:10:11 - 2:12:17 Currents at the begining (mA): Ie= 7.57, Ip= 32.63 max lumi value, (last record): 0.387, (6.012) mkb-1 s-1 max sp.Lumi value, (last record): 0.338, (0.553) mkb-1 s-1 mA-2 collided bunches = 0 e+(-) bunches = 0, p-bunches = 180 e-pilot b. = 0, p-pilot b. = 180 HERA total lumi: 0.21 nb-1 HERA - physics: 0 nb-1 H1Run - physics: 0 nb-1 H1data - physics: 0 nb-1 H1 operation eff.: 0 % , DT corr.: 0 % , Tot eff.: 0 % H1 Runs: 146073 - 146084 03/07/96 =================== kenyon === Lumi RUN# 986 Start - End of Run 986: 3/7/96 6:03:57 - 6:25:47 Collision time for H1Run - physics: 6:23:37 - 6:25:47 Currents at the begining (mA): Ie= 23.33, Ip= 44.56 max lumi value, (last record): 0.099, (6.012) mkb-1 s-1 max sp.Lumi value, (last record): 2.42, (2.42) mkb-1 s-1 mA-2 collided bunches = 123 e+(-) bunches = 178, p-bunches = 138 e-pilot b. = 55, p-pilot b. = 15 HERA total lumi: 0.11 nb-1 HERA - physics: 0 nb-1 H1Run - physics: 0 nb-1 H1data - physics: 0 nb-1 H1 operation eff.: 0 % , DT corr.: 0 % , Tot eff.: 0 % H1 Runs: 146104 - 146108 P.S. A new record instant. sp.lumi is reached 2.42 mkb-1 s-1 mA-2 03.07.1996 ===== OnLine ==== H1KFOM === OnLine Programs Development Today it was made new release of TwinFIC1-program for Master FIC1 with updating of 1 subroutines (OutBanks.f). Changing was connected with involving of Lumi RUN=-1 retranslation at LUMM-bank contents between neighbour Lumi RUNs. These are creation date and memory size of last release: TwinFIC1...............MPST MPS .....94642 Wed, Jul 03, 09:45 1996 Release is kept at H1Lumi:HD_LPI5:MPW:FomenkoAfter15.04.96:Applications -directory with name TwinFIC1new and will be put as default release for Watchdog-service at nearest time. P.S. Egor put this release as default release for Watchdog-service today at 17:50 (before H1Run 146351). 04/07/96 =================== kathage === Lumi RUN# 987 Start - End of Run 987: 3/7/96 18:05:45 - 6:21:40 Collision time for H1Run - physics: 19:51:40 - 6:21:40 Currents at the begining (mA): Ie= 11.3, Ip= 45.29 max lumi value, (last record): 0.344, (6.012) mkb-1 s-1 max sp.Lumi value, (last record): 0.277, (2.42) mkb-1 s-1 mA-2 collided bunches = 56 e+(-) bunches = 62, p-bunches = 180 e-pilot b. = 6, p-pilot b. = 124 HERA total lumi: 5.48 nb-1 HERA - physics: 4.45 nb-1 H1Run - physics: 3.38 nb-1 H1data - physics: 2.87 nb-1 H1 operation eff.: 74 % , DT corr.: 82 % , Tot eff.: 63 % H1 Runs: 146352 - 146544 04/07/96 =================== === Lumi RUN# 988 Start - End of Run 988: 4/7/96 11:20:07 - 11:31:52 Collision time for H1Run - physics: 11:31:45 - 11:31:52 Currents at the begining (mA): Ie= 23.98, Ip= 43.38 max lumi value, (last record): 0.005, (6.012) mkb-1 s-1 max sp.Lumi value, (last record): 0.003, (0.553) mkb-1 s-1 mA-2 collided bunches = 0 e+(-) bunches = 0, p-bunches = 180 e-pilot b. = 0, p-pilot b. = 180 HERA total lumi: 0 nb-1 HERA - physics: 0 nb-1 H1Run - physics: 0 nb-1 H1data - physics: 0 nb-1 H1 operation eff.: 0 % , DT corr.: 0 % , Tot eff.: 0 % H1 Runs: 146569 - 146569 04/07/96 =================== === Lumi RUN# 989 Start - End of Run 989: 4/7/96 13:16:18 - 14:34:54 Collision time for H1Run - physics: 14:34:46 - 14:34:54 Currents at the begining (mA): Ie= 20.11, Ip= 43.22 max lumi value, (last record): 0.48, (6.012) mkb-1 s-1 max sp.Lumi value, (last record): 0.264, (0.553) mkb-1 s-1 mA-2 collided bunches = 0 e+(-) bunches = 0, p-bunches = 180 e-pilot b. = 0, p-pilot b. = 180 HERA total lumi: 0.43 nb-1 HERA - physics: 0 nb-1 H1Run - physics: 0 nb-1 H1data - physics: 0 nb-1 H1 operation eff.: 0 % , DT corr.: 0 % , Tot eff.: 0 % H1 Runs: 146682 - 146689 05.07.1996 ================= H1KFOM === H1Lumi Dedicated Runs ....... Today evening during Lumi RUN# 989 it was recorded set of H1Lumi Dedicated Runs. S90-S95 subtriggers were ON. Random trigger was OFF. Farm was OFF for posibility of Raw Data H1Lumi banks trans- mission into H1DataFlow. FNC-readout was ON at first 7 H1Lumi Dedicated Runs and OFF at last (147094) Run. Only Luminosity and Central Trigger were at H1 CDAQ ReadOut from 18:02 up to 20:40. Mode 1 was ON at Luminosity branch (LREF,LRPF,LR1F banks were ON). Average logging rate during this period was near 70-80 Hz. 715824 events were recorded at these H1Runs.Ee+=27.54GeV and Ep=821.65GeV. Next H1Runs were recorded: 147087 497 events Ie=16.2mA Ip=47.0 mA 144088 16134 events Ie=16.0mA Ip=46.8 mA 144089 9471 events Ie=15.9mA Ip=46.8 mA 144090 5022 events Ie=15.8mA Ip=46.7 mA 144091 3812 events Ie=15.7mA Ip=47.6 mA 144092 5815 events Ie=15.7mA Ip=46.5 mA 144093 187293 events Ie=15.6mA->14.7mA Ip=46.5 mA->46.2mA 144094 487780 events Ie=14.7mA->11.0mA Ip=46.2 mA->45.2mA First Runs were recorded during prescale tuning. All these data were recorded on 9 permanent data sets (1926-1934). 06.07.1996 ===== Calibr ==== H1KFOM === Selection from Dedicated Runs From H1RAWD.C9601926-1934 data sets ( 715824 events) it were selected: ->223531 ETPDnVC 31.2% -> 82463 ETPDVC 11.5% -> 91416 S92 12.8% H1Runs 147087-147094 -> 38170 S91 5.3% ->286207 S93 40.0% (2.24GBytes selected from 3.60GBytes) -> 72264 ET44VC 10.1% You can see that summ of all selected samples (in %s) more then 100% It is due to overlapping(superposition) of some from samples. Selected samples temporary were placed into /acs/data/96/lumi-pool (only ETPDnVC-sample and its index-file), into /shift/dice2/data14/h1/ fomenko/user/fomenko-pool (ETPDVC,ET44VC and S93-samples) and into /shift/dice4/data1/h1/fomenko/user/fomenko-pool (S9291 samples). I am not sure that it is reasonable to keep all these data samples anywhere. May be after finishing of all attempts of calibration, finding of thresholds values, attempts to find some dependencies = f() = f() etc. it would be reasonable to erase all created additional files. Its always can be remade from H1RAWD-data sets if it will be needed to anybody at future. Selection of any sample gets not more then 17-19 min. dice3 CPU. 06/07/96 ================== goerlich === Lumi RUN# 990 Start - End of Run 990: 5/7/96 16:44:22 - 4:23:02 Collision time for H1Run - physics: 20:45:07 - 4:23:02 Currents at the begining (mA): Ie= 20.05, Ip= 47.24 max lumi value, (last record): 1.354, (6.012) mkb-1 s-1 max sp.Lumi value, (last record): 0.39, (0.553) mkb-1 s-1 mA-2 collided bunches = 171 e+(-) bunches = 186, p-bunches = 180 e-pilot b. = 15, p-pilot b. = 9 HERA total lumi: 27.49 nb-1 HERA - physics: 25.5 nb-1 H1Run - physics: 10.34 nb-1 H1data - physics: 8.35 nb-1 H1 operation eff.: 40 % , DT corr.: 79 % , Tot eff.: 32 % H1 Runs: 146968 - 147178 P.S. It was Lumi RUN with OnLine Photon Arm Rate Method of Luminosity calculation serious testing. Results are good. 06/07/96 =================== merkel === Lumi RUN# 991 Start - End of Run 991: 6/7/96 9:09:06 - 13:21:00 Collision time for H1Run - physics: 11:22:01 - 13:21:00 Currents at the begining (mA): Ie= 21.4, Ip= 53.38 max lumi value, (last record): 2.615, (6.012) mkb-1 s-1 max sp.Lumi value, (last record): 0.497, (0.553) mkb-1 s-1 mA-2 collided bunches = 176 e+(-) bunches = 189, p-bunches = 182 e-pilot b. = 13, p-pilot b. = 6 HERA total lumi: 27.72 nb-1 HERA - physics: 24.1 nb-1 H1Run - physics: 7.88 nb-1 H1data - physics: 4.95 nb-1 H1 operation eff.: 32 % , DT corr.: 62 % , Tot eff.: 20 % H1 Runs: 147236 - 147264 P.S. It was first Lumi RUN with Photon Arm Rate Method of Luminosity calculation showing for HERA people. Results are good. 06.07.1996 ===== Calibr ==== H1KFOM === H1Runs 147087-147094 Rel.Coef It were selected from 9 mentioned at previous messages permanent data sets of this year (1926th,1927th,...1934th) next events: ETPDnVC - 223531 events ETPDVC - 82463 events S9291 - 129580 events ( 91416=S92, 38170=S91) ET44VC - 72264 events S93 - 286207 events. It was made attempt to produce Relation Coefficients Set for H1Runs 147087-147094 data sample. It were got 223531 ET&PD&nVC from these Runs and it were used for calibration 127351 events (after all cuts). Final Relation Coefficient Set is the next: ==> Relation Coeff.Set for ET 0.000 0.000 0.000 0.000 0.000 0.000 0.000 1.191 1.388 1.816 1.546 1.841 1.069 1.471 0.715 0.991 1.272 1.162 1.217 1.185 1.180 1.187 1.156 1.071 1.093 1.175 1.087 1.191 0.983 1.086 1.033 1.047 1.054 1.071 1.098 2.013 1.042 0.468 1.594 1.088 1.836 1.274 1.076 1.046 1.091 1.281 1.106 1.081 0.000 ==> Relation Coeff.Set for PD 1.193 1.125 0.546 0.798 1.089 0.891 1.014 0.988 1.033 0.603 0.948 0.968 0.977 0.998 1.088 1.012 0.939 0.938 0.951 0.884 0.810 0.862 1.011 0.932 1.070 It were analized ETrec+PDrec energy distribution with using of these Relation Coefficients and CCvcs=3.213 MeV/FADCcount: Runs 147087-147094 (ET&PD&nVC-sample - near 224K events) all events xetcut xetcut&vcdepcut Step Mean Sigma Mean Sigma Mean Sigma 3 27.56 1.12 27.57 1.08 27.56 1.03 Runs 147087-147094 (ET&PD&VC-sample - near 82K events) all events xetcut Step Mean Sigma Mean Sigma 3 27.64 1.55 27.54 1.60 As start values of Calibration Coefficients for Photoproduction Branch were got ones from calbration 29.06.1996 (see LLO) with data collected at H1 Runs 144730-144734. CCvcs value was got from the same sample CCvcs calibration procedure. (CCvcs start = 3.213 MeV/FADCcount). Attempt to make fit of PhotonArm Energy spectrum with S92-events was enough succesful with very good statistics. 06.07.1996 ===== Calibr ==== H1KFOM === Global Shifts,CCvcs Run147087 It was estimated (preliminary) that Global Shifts for both H1Lumi arms are: 1.0003 for PD Channels (exept VCs), 1.0068 for ET channels. Correction factor for CCvcs is 1.016. So CCvcs =3.213*1.016 =3.264MeV/ FADCcount. These digits are valid for H1Lumi events from Runs 147087-147094: Runs 147087-147094 (ET&PD&nVC-sample - near 224K events) all events xetcut xetcut&vcdepcut Mean Sigma Mean Sigma Mean Sigma 27.49 1.11 27.48 1.07 27.50 1.03 <- PEAKPARM 27.53 1.16 27.55 1.11 27.54 1.04 <- FIT (gauss+ax+b) +-0.003 +-0.003 +-0.003 <- errors from fit Runs 144087-147094 (ET&PD&VC-sample - near 82K events) all events xetcut Mean Sigma Mean Sigma 27.48 1.58 27.48 1.60 <- PEAKPARM 27.55 1.46 27.53 1.53 <- FIT (gauss+ax+b) +-0.007 +-0.007 <- errors from fit P.S. bins 200 22 32 for ETPDnVC sample; bins 200 22 32 for ETPDVC-sample; fit boundaries (Xmin=22 GeV,Xmax=32 GeV); xetcut=(xet<6.0&xet>-6.0; vcdepcut=(vcdep>-0.2&vcdep<0.2) Photon Arm Global Energy Shift was defined after fine tuning and has next values (73768 events with S92-trigger at 70th histo): -0.1%+-0.2% (for all fit boundaries from 6-35 up to 20-35 GeV). Resolution Values are 17-18%+-0.8%. Mentioned earlier fine tuning results mean that calibration precision is fantastically good (due to huge statistics) -> 0.2%(!!!) P.S.Final values of Calibration Coefficients for ET,PD and VCs are next ==> ET Calibr.Coefficients Final Status e00= 4.139 4.609 4.199 3.408 4.061 2.997 3.333 4.599 5.572 7.215 7.643 6.911 4.320 5.617 7.686 2.206 4.937 4.696 3.102 4.715 4.351 6.749 4.524 5.677 5.184 4.678 5.587 4.643 4.510 4.751 5.809 4.213 4.840 4.999 4.283 7.935 4.140 2.235 6.430 4.643 7.402 5.189 e42= 4.320 4.298 4.382 5.227 4.479 4.345 4.285 p00= 3.108 2.979 1.206 2.065 2.961 1.494 2.662 3.301 2.619 1.375 2.361 3.047 3.262 3.083 2.434 3.315 2.870 3.251 2.289 2.376 p20= 2.153 1.981 2.596 2.589 2.909 vcs= 3.264 Energy spectrum VCdep is similar as it was seen at previous year - visible part of spectrum (at linear scale) is finishing near 6.5-7.0GeV 06.07.1996 ===== Calibr ==== H1KFOM === ET44 Rel.Coeff.Set Run147087 Today it were defined Relation Coefficients Set for ET44-channels at events from H1Runs 147087-147094. It were selected 72264 events with ET44VC from mentioned H1Runs which are temporary kept at /shift/dice2/data14/h1/fomenko/user/fomenko-directory (204MBytes). H1KFOM.ET44VC.M926934.C00 From this data set it were selected 21908 events with VC=1 and with using of all earlier mentioned cuts. These events were used for calibration. Channel et01 became again as non-Dead channel. Next cuts were used: 1) Energy deposited at et1,et3 and et5 must be more then 0.60 GeV; 2) 19.1GeV