<!-- Title: 14:59:45  Fri Sep 19 2003 -->
<!-- Crewchief: Karen Gibson -->
<!-- Op1: Alexy Ershov -->
<!-- Op2: Andy Foland -->
<!-- Op3: &nbsp; -->
<!-- Op4: &nbsp; -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
<pre>Beamline processing, now on production farm</pre>


<!-- Date: Fri Sep 19 15:12:46 2003 -->
<pre>Making PAD_PHYSICS_(SVX/COT)BEAM tables 10/10 for 5.1.0 Production processing: 
 
[cdfopr@fcdflnx3 5.1.0beamonly]$ ~cdfsoft/dist/releases/development/CalibDB/bin/PassTool.pl -c /@cdfonprd -p PAD_PHYSICS_COTBEAM -n 10 -w 
62 
success:index=63 process_name=PAD_PHYSICS_COTBEAM stream=A passname=10 
 
and  
 
[cdfopr@fcdflnx3 5.1.0beamonly]$ ~cdfsoft/dist/releases/development/CalibDB/bin/PassTool.pl -c /@cdfonprd -p PAD_PHYSICS_SVXBEAM -n 10 -w 
63 
success:index=64 process_name=PAD_PHYSICS_SVXBEAM stream=A passname=10 
</pre>
<!-- Author: Karen -->


<!-- Date: Fri Sep 19 16:18:09 2003 -->
<pre>Starting to update beamline pass for runs 138425 - 139300 
 
[cdfopr@fcdflnx3 5.1.0beamonly]$ Beamline/scripts/updBeamPassSvx.sh 138425 139300 |& tee mylog.txt</pre>
<!-- Author: Karen -->
<!-- Comment: Fri Sep 19 16;29;04 comment by...Karen -->
<pre>First attempt failed b/c BeamValidate doesn't run MakeUsedValidSet after making DB entries.  Will do by hand for now.</pre>


<!-- Date: Fri Sep 19 18:13:10 2003 -->
<pre>Had to move back to 4.9.1hpt3_beam to get UsedSetVersion to work... need to debug (later) 
 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/updBeamlinePassSvx_pass10.sh 138425 139300 | & tee updHC21_138425_139300.log 
 
which took ~0.5 hr.</pre>
<!-- Author: Karen -->
<!-- Comment: Fri Sep 19 19;08;41 comment by...Karen -->
<pre>[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/updBeamlinePassSvxWrite_pass10.sh 138425 139300 | & tee updHC21Write_138425_139300.log

which is instantaneous.</pre>


<!-- Date: Fri Sep 19 19:12:55 2003 -->
<pre>Now COT (already run, just putting commands in for reference later) 
 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/updBeamlinePassCot_pass10.sh 138425 139300 | & tee updHC21Cot_138425_139300.log 
 
and 
 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/updBeamlinePassCotWrite_pass10.sh 138425 139300 | & tee updHC21CotWrite_138425_139300.log 
 
Note: only 11 runs out of 34 had vxprim COT entries.  BeamValidate "interpolated" most of the ones missing entries, but it looks like updBeamlinePassCot ignored that and re-interpolated  the entries (which is what we want to do.)  this is not confirmed, but that's what it looks like from a cursory perusal of the updBeamlinePassCot log file.</pre>
<!-- Author: Karen -->


<!-- Date: Sat Sep 20 16:33:59 2003 -->
<pre>Interpolating runs 138617 and 139249 "by hand" (via a bad hack to updBeamlinePass*_pass10.sh) to PAD_PHYSICS_(SVX/COT)BEAM, as requested by Martin van der Mey.  These runs weren't added automatically b/c they don't appear in PROD_PHYSICS_CDF pass 10 (or pass 07, for that matter.) </pre>
<!-- Author: Karen -->
<!-- Comment: Sat Sep 20 17;15;45 comment by...Karen -->
<pre>correction:  Martin von der Mey</pre>


<!-- Date: Mon Sep 22 15:10:43 2003 -->
<pre>Discovered problem w/PAD_PHYSICS_SVXBEAM pass 09.  I had failed to run MakeUsedValidSet for HC20 before running the interpolation, etc., so all the entries for SVXBEAM pass 09 are wrong now (i.e. need to remake whole SVXBEAM table for HC20.) 
 
Retiring old table: 
 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ ~cdfsoft/dist/releases/development/CalibDB/bin/PassTool.pl -c /@cdfonprd -p PAD_PHYSICS_SVXBEAM -n 09 -w 
66 
success:index=67 process_name=PAD_PHYSICS_SVXBEAM stream=A passname=09 
 
Success!  First things first, make rest of COT entries for PAD_PHYSICS_COT pass 09 (which are correct) 
 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/updBeamlinePassCot_pass09.sh 168467 168892 &gt;& updBeamlinePassCot_pass09_164867_168892.log & 
</pre>
<!-- Author: Karen -->
<!-- Comment: Mon Sep 22 17;15;03 comment by...Karen -->
<pre>Oops, meant 

[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/updBeamlinePassCot_pass09.sh 164867 168892 &gt; & updBeamlinePassCot_pass09_164867_168892.log &</pre>


<!-- Date: Tue Sep 23 09:26:23 2003 -->
<pre>Making Used sets is taking a long time... the COT hadn't finished when I came in this morning.  Had to kill the job b/c the online DB is going down at 9:30.  Tried to run updBeamlinePassSvx_pass09.sh over several run ranges in parallel on fcdflnx2. The jobs seemed to be doing pretty well last night, but they seem to have all but trickled to a halt overnight.  Maybe DB issues?  Not sure.  After the DB come back online at 11:30, I'll try again, this time with only one range at a time...  </pre>
<!-- Author: Karen -->


<!-- Date: Tue Sep 23 10:03:01 2003 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=beamline&action=view&page=-76&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=beamline&action=view&page=-76' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=beamline&action=view&page=-77&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=beamline&action=view&page=-77' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=beamline&action=view&page=-78&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=beamline&action=view&page=-78' width='300'></a></center>
<!-- Author: Karen -->
<!-- Comment: Tue Sep 23 10;05;01 comment by...Karen -->
<pre>Some validation histograms for runs 138425 - 149716, the first alignment period.  These histograms include those runs which have been "interpolated" (i.e. copied) by JP's scripts from previous runs, so it's not a direct comparison with what we're used to seeing in validation w/only vxprim entries...</pre>


<!-- Date: Tue Sep 23 10:05:41 2003 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=beamline&action=view&page=-79&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=beamline&action=view&page=-79' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=beamline&action=view&page=-80&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=beamline&action=view&page=-80' width='300'></a></center>
<!-- Author: Karen -->
<!-- Comment: Tue Sep 23 10;08;25 comment by...Karen -->
<pre>Time dependence for runs 138425 - 149716 for SVX (left) and COT (right).  Clearly the COT does not track the SVX well.  I don't know how I found good agreement bet. SVX and COT time dep. originally, but that was clearly erroneous.  Turning off COT time dependence as default was definitely a good idea. </pre>


<!-- Date: Fri Sep 26 12:45:39 2003 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=beamline&action=view&page=-82&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=beamline&action=view&page=-82' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=beamline&action=view&page=-83&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=beamline&action=view&page=-83' width='300'></a></center>
<!-- Author: Karen -->
<!-- Comment: Fri Sep 26 12;46;26 comment by...Karen -->
<pre>HC21 SVX and COT plots respectively for 138425 - 149716 with *only* algo 20 entries plotted.</pre>


<!-- Date: Fri Sep 26 12:47:12 2003 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=beamline&action=view&page=-84&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=beamline&action=view&page=-84' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=beamline&action=view&page=-85&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=beamline&action=view&page=-85' width='300'></a></center>
<!-- Author: Karen -->
<!-- Comment: Fri Sep 26 12;49;16 comment by...Karen -->
<pre>HC21 SVX-COT diffences for run 139425 - 149716 in both scatter plot and histogram form (nice for stats and all.)</pre>
<!-- Comment: Fri Sep 26 12;49;50 comment by...Karen -->
<pre>Again *ONLY* entries w/algo 20 are plotted.</pre>
<!-- Date: Fri Sep 26 12:47:44 2003 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=beamline&action=view&page=-86&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=beamline&action=view&page=-86' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=beamline&action=view&page=-87&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=beamline&action=view&page=-87' width='300'></a></center>
<!-- Author: Karen -->
<!-- Comment: Fri Sep 26 12;50;35 comment by...Karen -->
<pre>Time-dep for HC21 algo 20 entries for 138425 - 149716.</pre>


<!-- Date: Fri Oct 10 12:08:15 2003 -->
<pre>We successfully finished adding runs 138425 - 168892 to PAD_PHYSICS_SVX/COTBEAM pass 10 (-&gt; PROD_PHYSICS_CDF pass 11) on Oct. 5, 2003 and the Production farm began running over Stream C with PROD pass 11 on Tuesday.  We decided to "patch" 26 runs w/non-optimal COT entries (either NULL entries or copied SVX entries w/o inflated errors) for users, so first retire current table, copy good entries from retired to new table, then re-run new, improved BeamValidate and updBeamlinePass*.sh over the 26 runs in question.   
 
Retiring PAD_PHYSICS_COTBEAM pass 10 to fix 26 runs in the first alignment period.   
 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ ~cdfsoft/dist/releases/development/CalibDB/bin/PassTool.pl -c /@cdfonprd -p PAD_PHYSICS_COTBEAM -n 10 -w 
 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ ~cdfsoft/dist/releases/development/CalibDB/bin/PassTool.pl -c /@cdfonprd -p PAD_PHYSICS_COTBEAM -n 10 -w 
71 
success:index=72 process_name=PAD_PHYSICS_COTBEAM stream=A passname=10 
</pre>
<!-- Author: Karen -->
<!-- Comment: Fri Oct 10 12;10;55 comment by...Karen -->
<pre>New table i=72, old table i=63.</pre>


<!-- Date: Fri Oct 10 12:11:46 2003 -->
<pre>List of runs to repair: 
 
141438 
141446 
141461 
143591 
143592 
143593 
143606 
145192 
145299 
145450 
145669 
147165 
147483 
148270 
149299 
149385 
149852 
149856 
149859 
149863 
149866 
149925 
150340 
153557 
155794 
167770</pre>
<!-- Author: Karen -->


<!-- Date: Fri Oct 10 14:24:28 2003 -->
<pre>Now copy over good entries: 
 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 72 63 138425 141437 &gt;& cpyCotBeam_pass10_138425_141437.log & 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 72 63 141439 141445 &gt; & cpyCotBeam_pass10_141439_141445.log & 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 72 63 141447 141460 &gt; & cpyCotBeam_pass10_141447_141460.log & 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 72 63 141462 143590 &gt; & cpyCotBeam_pass10_141462_143590.log & 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 72 63 143594 143605 &gt; & cpyCotBeam_pass10_143594_143605.log & 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 72 63 143607 145191 &gt; & cpyCotBeam_pass10_143607_145191.log & 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 72 63 145193 145298 &gt; & cpyCotBeam_pass10_145193_145298.log & 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 72 63 145300 145449 &gt; & cpyCotBeam_pass10_145300_145449.log & 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 72 63 145451 145668 &gt; & cpyCotBeam_pass10_145451_145668.log & 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 72 63 145670 147164 &gt; & cpyCotBeam_pass10_145670_147164.log & 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 72 63 147166 147482 &gt; & cpyCotBeam_pass10_147166_147482.log & 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 72 63 147484 148269 &gt; & cpyCotBeam_pass10_147484_148269.log & 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 72 63 148271 149298 &gt; & cpyCotBeam_pass10_148271_149298.log & 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 72 63 149300 149384 &gt; & cpyCotBeam_pass10_149300_149384.log & 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 72 63 149386 149851 &gt; & cpyCotBeam_pass10_149386_149851.log & 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 72 63 149853 149855 &gt; & cpyCotBeam_pass10_149853_149855.log & 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 72 63 149857 149858 &gt; & cpyCotBeam_pass10_149857_149858.log & 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 72 63 149860 149862 &gt; & cpyCotBeam_pass10_149860_149862.log & 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 72 63 149864 149865 &gt; & cpyCotBeam_pass10_149864_149865.log & 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 72 63 149867 149924 &gt; & cpyCotBeam_pass10_149867_149924.log & 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 72 63 149926 150339 &gt; & cpyCotBeam_pass10_149926_150339.log & 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 72 63 150341 153556 &gt; & cpyCotBeam_pass10_150341_153556.log & 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 72 63 153558 155793 &gt; & cpyCotBeam_pass10_153558_155793.log & 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 72 63 155795 167769 &gt; & cpyCotBeam_pass10_155795_167769.log & 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 72 63 167771 168892 &gt; & cpyCotBeam_pass10_167771_168892.log & 
 
From a cursory look, everything seems successful.</pre>
<!-- Author: Karen -->


<!-- Date: Fri Oct 10 18:54:01 2003 -->
<pre>Added the 26 runs to PAD_PHYSICS_COTBEAM pass 10.  Beamlines are finished up to September shutdown.</pre>
<!-- Author: Karen -->


<!-- Date: Wed Nov 12 17:11:39 2003 -->
<pre>Adding correct HC19 entries for 163463 and 163474.  
 
Retiring current table 
 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ ~cdfsoft/dist/releases/development/CalibDB/bin/PassTool.pl -c /@cdfonprd -p PAD_PHYSICS_SVXBEAM -n 08 -w 
80 
success:index=81 process_name=PAD_PHYSICS_SVXBEAM stream=A passname=08 
 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 81 55 122621 163462 | & tee copyBeamlinePass_122621_163462.log 
 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 81 55 163464 163473 | & tee copyBeamlinePass_163464_163473.log 
 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 81 55 163475 168892 | & tee copyBeamlinePass_163475_168892.log</pre>
<!-- Author: Karen -->


<!-- Date: Fri Jan 9 13:02:27 2004 -->
<pre>Problem fitting history 21 beamlines for run 177315 and 177339.  JP tracked the problem down to a Gaussian fitting function in the Beam Width calculation.  I'll skip these two runs by hand, finish the rest, then modify BeamValidate to exclude the width calculation for 177315 and 177339. </pre>
<!-- Author: Karen -->
<!-- Comment: Mon Jan 19 12;49;55 comment by...Karen -->
<pre>Also skipped width calculation for runs 

177342 
177363
177364
177370

and runs 177371 - 177491.  Stan modified BeamWidthModule.cc to fix the problem, so runs processed with BeamExe_5.1.3a_beam will not hang in BeamValidate.  
</pre>
<!-- Date: Mon Jan 19 11:35:07 2004 -->
<pre>By mistake, old version of BeamExe with maximum of 14 run segments instead of 30 was used to process runs 174996-177800. Fot huge runs this could cause the run-average beamline to be used for a latter portion of the run beyound 14 segments. 
Fortunately, we got lucky this time as there were so few  big runs in this period. We do not need to change any beamline values.  
I hand-checked all the runs with &gt;500 nb. 
There is only one run 177267 (1 pb-1)  that could have used 3 more segments (17 instead of 14). For this run we do not need to chane the entries. 
Beam position difference  between run average and the last 14th segment is deltaX = 4.6 um, deltaY= 6.6 um, deltaX' = 0.8 ur, deltaY'= 3.6 ur. 
Beam position difference  between 13th and  14th segment is deltaX = 4.7 um, deltaY= 5.3 um, deltaX' = 7.7 ur, deltaY'= 5.2 ur. 
</pre>
<!-- Author: ershov -->


<!-- Date: Mon Jan 19 11:37:18 2004 -->
<pre>By mistake, old version of BeamExe with maximum of 14 run segments instead of 30 was used to process runs 174996-177800. Fot huge runs this could cause the run-average beamline to be used for a latter portion of the run beyound 14 segments. 
Fortunately, we got lucky this time as there were so few  big runs in this period. We do not need to change any beamline values.  
I hand-checked all the runs with &gt;500 nb. 
There is only one run 177267 (1 pb-1)  that could have used 3 more segments (17 instead of 14). For this run we do not need to chane the entries. 
Beam position difference  between run average and the last 14th segment is deltaX = 4.6 um, deltaY= 6.6 um, deltaX' = 0.8 ur, deltaY'= 3.6 ur. 
Beam position difference  between 13th and  14th segment is deltaX = 4.7 um, deltaY= 5.3 um, deltaX' = 7.7 ur, deltaY'= 5.2 ur. 
 
</pre>
<!-- Author: ershov -->



<!-- Date: Mon Jan 19 12:53:15 2004 -->
<pre>Retiring old pass 08 SVXBEAM and 07 COTBEAM tables to remake used sets for runs 155393-155742, which had NULL entries originally filled in by Hartumut and Ray a year ago.  These runs had not been processed by the production farm until the September due to an incorrect trigger table. 
 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ ~cdfsoft/dist/releases/development/CalibDB/bin/PassTool.pl -c /@cdfonprd -p PAD_PHYSICS_COTBEAM -n 07 -w 
86 
success:index=87 process_name=PAD_PHYSICS_COTBEAM stream=A passname=07 
 
and 
 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ ~cdfsoft/dist/releases/development/CalibDB/bin/PassTool.pl -c /@cdfonprd -p PAD_PHYSICS_SVXBEAM -n 08 -w 
87 
success:index=88 process_name=PAD_PHYSICS_SVXBEAM stream=A passname=08 
 
</pre>
<!-- Author: Karen -->


<!-- Date: Mon Jan 19 13:36:51 2004 -->
<pre>Now copy over good entries from retired SVXBEAM table to new SVXBEAM table: 
 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 88 81 122621 155392 | & tee copyBeamlinePass_122621_155392.log 
 
and 
 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 88 81 155743 168892 | & tee copyBeamlinePass_155743_168892.log</pre>
<!-- Author: Karen -->


<!-- Date: Mon Jan 19 16:43:46 2004 -->
<pre>Copying the COT entries: 
 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 87 50 122621 155392 | & tee copyBeamlinePassCot_122621_155392.log 
 
and 
 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/copyBeamlinePass.sh 87 50 155743 168892 | & tee copyBeamlinePassCot_155743_168892.log</pre>
<!-- Author: Karen -->


<!-- Date: Mon Jan 19 16:44:54 2004 -->
<pre>Copying was successful, so make new entries for runs 155393 - 155742: 
 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/updBeamlinePassSvx.sh 155393 155742 &gt;& updBeamlinePassSvx_155393_155742.log &</pre>
<!-- Author: Karen -->
<!-- Comment: Mon Jan 19 17;49;28 comment by...Karen -->
<pre>[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/updBeamlinePassSvxWrite.sh 155393 155742 &gt; & updBeamlinePassSvxWrite_155393_155742.log &</pre>


<!-- Date: Mon Jan 19 17:50:25 2004 -->
<pre>Now on to COT entries: 
 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/updBeamlinePassCot.sh 155393 155742 &gt; & updBeamlinePassCot_155393_155742.log & 
</pre>
<!-- Author: Karen -->
<!-- Comment: Mon Jan 19 20;13;12 comment by...Karen -->
<pre>[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/updBeamlinePassCotWrite.sh 155393 155742 &gt; & updBeamlinePassCotWrite_155393_155742.log &</pre>


<!-- Date: Mon Jan 19 20:14:28 2004 -->
<pre>Now run checkBeamlinePass.sh to check for problems: 
 
[cdfopr@fcdflnx3 4.9.1hpt3_beam]$ Alignment/scripts/checkBeamlinePass.sh 122621 168892 19 svx 08</pre>
<!-- Author: Karen -->


<!-- Date: Wed Jan 21 11:44:59 2004 -->
<pre>BeamExe was upgarded from 5.1.1 to 5.1.3 starting with 177927. 
However,all the beamline DB entries for the 34 runs 177927-178080 will still show "5.1.1" instead of "5.1.3" as "algorithm name". This is not a problem for accessing beamlines. The "algorithm name" is only used as the comment field to keep track of the xecutable. What is important for accessing beamlines is that all 5.x beamline entries are are history code 21 .</pre>
<!-- Author: ershov -->


<!-- Date: Sun Jan 25 19:06:22 2004 -->
<pre>Run 178310 
Problem: 
SVX time-dependent beamline entries were created for only 7 out of 10 segments. Caused by production farm prematurely signalling that all the events were processed by BeamExe for this run. The production group is working on the fix to prevent this problem in the future. 
 
The problem is not serious - beam was not moving significantly during the run.  
Difference between run average and last segment values for 178310 
deltax = 2.9um, deltay=0.6um, deltax'=3.6ur, deltay'=3.0ur 
 Difference between run averages for run 178310 and previous run 178307 
deltax = 1.3um, deltay=4.3um, deltax'=2.6ur, deltay'=6.7ur 
  
No worries.No action is required. 
 
 
 
 
</pre>
<!-- Author: ershov -->


<!-- Date: Mon Jan 26 13:16:17 2004 -->
<pre>Run 178310  
Addendum to previious entry.  
Run 178310 has been fully processed by BeamExe. 
I ran BeamValidate to check whether we need to patch PAD_PHYSICS_SVX for this run to take care of the 3 missing segments (9-11). The beam did not move enough (~5um) to warrant any action.  
 
Segment x        y         x'        y'  
8  -0.268468 0.133866 0.000784863 0.000181923 
9  -0.268216 0.133927 0.000785004 0.000184789 
8-9   3 um     1 um       0 ur    3 ur     
10 -0.268002 0.133805 0.000790135 0.000175752 
8-10  5 um    1 um      5 ur    6 ur     
11 -0.267878 0.133568 0.000785765 0.0001761 
8-11  6 um    3 um      1 ur    6 ur     
 
------------------------------ 
Problem:  
SVX time-dependent beamline entries were created for only 7 out of 10 segments. Caused by production 
farm prematurely signalling that all the events were processed by BeamExe for this run. The 
production group is working on the fix to prevent this problem in the future.  
 
 
The problem is not serious - beam was not moving significantly during the run.   
Difference between run average and last segment values for 178310  
deltax = 2.9um, deltay=0.6um, deltax'=3.6ur, deltay'=3.0ur  
 Difference between run averages for run 178310 and previous run 178307  
deltax = 1.3um, deltay=4.3um, deltax'=2.6ur, deltay'=6.7ur  
 
No worries.No action is required. </pre>
<!-- Author: ershov -->


<!-- Date: Tue Feb 3 19:33:01 2004 -->
<pre>Run 178310: 
Disregard the previous 2 messages. Beamlines created for all the run segments.  
 
Run 178602 had the same problem, but now is fully repaired.  
The calibration tables point to the best complete beamline entries.   
 
I had to retire and re-create PAD_PHYSICS_SVXBEAM table to accomplish this goal. 
 
</pre>
<!-- Author: ershov -->