CuCu @ 200 GeV

6TD11 is going yellow often
day date/hour first run what was done , who consequences for off-line/DB
001 before jan 1 6001001 load HV_v_B assume timing of all crates is wrong
011 Jan 11 6011004 ped run , Jim, eLog#833
011 Jan 11 6011007-14 TW cr timing scan(1), Jim, eLog#833
012 Jan 12 6nnnkkk ACCESS, Will, eLog#834 only dead box=6S3, all TW boxes OK.
013 Jan 13 6013016-22 TW cr timing scan(2), Will, eLog#835
014 jan 14 6nnnkkk magnet crash, 6S3 self fixed, EEMC recovered all 6+48 boxes are working
unstable 8TA07 red/green HV,
014 jan 14 P-plot has recent fee peds
014 jan 14 6014076+77 no beam,ped runs, 76=HVoff, 77=HVon will be used for DB
014 jan 14 6014085-114 MAPMT timing scan(1), Murad, eLog#837
016 jan 16 6016068 4ch in 8P1: noise in ped, P-plot p.56 mark sth in DB
018 jan 18 6018032+ load HV_v_C , only tower are new, Jason new TW gains, timing is still not set
018 jan 18 6018065 ETOW TCD phas changed 32 --> 12 ?
ESMD TCD pahse by 15 ns
FEE peds loaded (R6011004)
gains changed for ETOW & ESMD
019 jan 19 ACCESS added delay to TCD

fixed some signal fibers for MAPMT
fixed some trigger cables
eLog#845, Jim
all timing is new, gains are different
024 jan 24 6nnnkkk towers masked in FEE: cr1/ch97 + cr4/chan117
in reality , Renee
nnn jan 25 6nnnkkk dsm spectra in P-plot fixed, JB
026 jan xx 6026071 loaded HV set D (new towers)
DSM spctra fixed by Renee
new tower gains
tw crate delays: 15,5,85,80,45,35
026 jan 26 6026090 Paul fixed address of
fee peds in GUI
DSM spectra better
027 jan 27 6027049 6TA03 masked in FEE
new fee peds loaded, RF
almost perfect DSM spectra
028 jan 28 6028024 new Tw timing: 15,10,90,80,45,35 new tower gains,OK
nnn feb 1 6nnnkkk ACCESS, DSM Cr6-Crd1-J1 fixed, Jim only one patch is bad
34 feb 3 6nnnkkk problem with LV in 6P1, jim
035 feb 4 6035106=only new HV v_E, one run
only changed 4S1-3, Jim
new SMD gain in sector 4
36 feb 05 6nnnkkk cr1 has stuck ADC's in ch 1-20?, Jim, -->listA no clue
041 feb xx 6nnnkkk rampTrigger, EHT6 lot of events w/o TPC
nnn feb xx 6nnnkkk example no clue
044 feb xx 6044047+few ? loaded HV set F , Renee final SMD/pre/post HV, towers as in setD
nnn feb 12 6nnnkkk hot tower 6/31=10TB12 crat6 problem
044 broken Mapmt pixles found, Julie see ListC
nnn feb 13 ,10am 6nnnkkk 6TD11 alarms every 10-15 minutes, Murad
nnn feb 14 , 6 am 6nnnkkk Endcap out of data due to alarms no clue
nnn feb 16 6047045- ACCESS Steve:
* replaced cr1 brd1 (ListA fixed)
* fixed SMD strips ~ 12V150
*new signal cables 7TB03 & 7TB09
different cr1 peds, new fee ped4
1TC06=cr1/118 has only ped _after_ this access
nnn feb 16 604758 wrong(=old) fee ped4, cr3 brd2 stuck ADC ignore EHT events, wrong Pplot peds
nnn feb 17 6048028+ cr3 brd2 fixed all works for <24 hours
nnn feb 17 6048051 ETOW not configured properly ignore ETOW
nnn feb 17 604841 new MAPMT timing, 3P1 still wrong,Scott ,eLog#883 new MAPMT gains
nnn feb 17 6048079 good fee ped4 loaded,
cr6 stuck ADC few hours later
EHT works
049 feb 18 6049038 cr6 is sick- whole mornng?, Jan tower problem
049 feb 18 ?? Mapping in sector 1 & 8 have been corrected backwards in DB onlPed are redone from this day
nnn feb 18 6049084 3P1 timing fixed all ETOW & ESMD & EHT wrorks. Pplot peds old
049 feb 18 6049102 Pplot ped & ped4 reloaded all freq Pplots are correct
nnn feb 20 6050132- myrenet & L2 failure, eLog, Scott ETOW & ESMD corrupted
nnn feb 21 6nnnkkk HVsys is yellow for MAPMTs, Jim
nnn feb 22 6053012-39
6053083,94
6054019
eeSpy: 2xff in some ETOW & ESMD in some runs
nnn feb 23 6nnnkkk beam studies, probmels with cr1 &2, SEV
nnn feb 25 R6056005,6,10 2xfff in box 105,106
nnn feb 25 R6056017 -33 10S2=box105 is hot, 2xfff
nnn feb 25 R6056034-55 2xfff in box 96-111
056+ feb 25+ R6056061-
R6057048
2xfff in box 70-111 ,turned off 2/3 last night ,Jim
57+ feb 26+ R6057058-
R6058087
2xfff in box 72=2S1
nnn feb 28 6nnnkkk new hot towes:
3/81=3TD05 & 4/46=6TD11
*10S2 remains at 36C.
new Trig mask (see ListB, eLog895)
060 mar 1 606005-29 2xfff in box 96-111, power off.
060 mar 1 606030 no ESMD, next
061,2 mar2-3 ACCESS longer
nnn mar x 6062008-12 Zero-filed runs w/ laser not use those
nnn mar x 6nnnkkk example no clue
nnn mar 3 6nnnkkk new fee peds in crates, not changed in P-plots
Jason, eLog 896
063 mar 4-5 6063053 9pm,cr109 lost confg,
was off for next ~16 hours
64 mar 5 6064084 new fee ped4 in Pplot
64 mar 5 6064062-64 dead box=109

CuCu @ 62 GeV

day date/hour first run what was done , who consequences for off-line/DB
nnn mar 7 setup
073 mar 14 6073016-36? box83=4P1 is off (2xfff)
074 mar 15 6074035 -87 test ENERGY 22 GeV
just this one day
sort separatley
mar 16 ACCESS swapped tower FEE board #3 in crate #6
try to fix trigger patch #13 HT , FAILED
new peds are needed
081 mar 22 6081062 last run

CuCu @ 22 GeV

day date/hour first run what was done , who consequences for off-line/DB
081 mar 22 6081074 first run
nnn mar x 6nnnkkk example no clue
nnn mar x 6nnnkkk example no clue
nnn mar x 6nnnkkk example no clue

pp @ 200 GeV

list of masked EEMC towers at the start of pp200 run

 # format: crate channel towerName
 1 97  12TC05
 3 81  03TD05  was warking later
 4 46  06TD11  intermittent problems
 4 18  06TA03
 4 117 07TC05
day date/hour first run what was done , who consequences for off-line/DB
n83 mar 24 pp200 started
097 apr 7 6097037+ new Tower HV
set HV G
see ListD
098 apr 8 4S2 and 5S3 :low on the base 3V is around 1.1V still work fine
nnn apr 9 6nnnkkk from Mei: switch to a "... 056x056pmpm_ppmm pattern."
pmpm in Blue and ppmm in Yellow.
nnn Apr 11 6nnnkkk DAQ was disrupted in the morning, lots of corruption and 5S2
nnn Apr 11 I got an access and changed the the nominal 4V
it helped the boxes like 4S2
now 4S3, 4P1 and 5S1 are reading 2.7 to 2.9 V , Jim
nnn Apr 11 4P1 is needing to be reconfigure quite often, Jim
nnn Apr 12 LUT are not right LUT & ped4 are too old.
103 Apr 13 6103022-46 HT & JP trig test
large beam background
do not use for physics
104 Apr 14, 1 pm EDT 6104052+ new ped4 loaded to fee
Jason, eLog 909
pPlot peds not updated
106 Apr 16 ,4am - 10 am 6106014-23 SpyCopyCat: ESMD crate=74,75,76,77,79, 92,98,103,106 : big problems
Also ETOW cr=2 is sick, wrong LUT & FEE peds
do not use this data
107 Apr 17 on PMT of BBC has new HV
Lum low of 3.5 *10^30
107 Apr 17, 5am - 10am R6107007-38 SpyCopyCat: ESMD crate=71,98,103,106 : small 4-chan losses data are ~fine
108 Apr 16 ,0am - 10 am 6108003-6 SpyCopyCat: ESMD crate=71,98,103,106 : small 4-chan losses data are ~fine
108 Apr 18, 3 am 6nnnkkk TPC gas purge drift vel discontinuity
108 Apr 18 6108018+ peds loaded to Pplot Pplot is in sync with FEE (Apr 14)
nnn Apr 21 6nnnkkk back to 4-10 cogging see listG
108+ Apr 18 6108037-9021 4-chan copyCat box=71,98,99,103,106 minor problem
108 Apr 18 6108037 JP3 TP3 was at 62, Renee
was masked in subsequent runs
109 Apr 19 6109026-40 4-chan copyCat box=97,102
109+ Apr 19 6109093-1005 4-chan copyCat box=103
110 Apr 20 6110006 JP3 TP3 unmasked, Renne
110 Apr 20 6110012+ unmasked 6TD11 and 3TD05, Renee
110+ Apr 20+ 6110012-1074 4-chan copyCat box=103
111 Apr 21 4-46-06TD11 starts to be hot but is not masked
111 Apr 21 6nnnkkk back to 4-10 cogging see listG
112 Apr 22 ppEmcCheck trig mix is setup
112 Apr 22 6112004-12 cr2 bad ch46-64
4-chan copyCat box=89,103
wrong tower data
112+ Apr 22+ 6112013-3078 4-chan copyCat box=89,103
113 Apr 23 6113018 4-46-06TD11 masked again, Renne
113 Apr 23 6113055 tower cr2-ch98=2TC06 is hot and _not_ masked careful with EHT events
113 Apr 23 6113079-81 cr3 is garbage
4-chan copyCat box=89,103
some towers wrong
114 Apr 24 6114006-12 4-chan copyCat box=67,103
114 Apr 24 6114021 crates 3-6 are sick garbage run
114 Apr 24 6114026+ masked cr2-ch98=2TC06, Renee, see listH 6 masked total: 12TC05 06TA03 07TC05 06TD11 02TC06 12TC05
114 Apr 24 6114022-30 4-chan copyCat box=103
114+ Apr 24+ 6114031-5015 4-chan copyCat box=71,103
114 Apr 24 . ~9 hours gap for cdev & EEMC epics monitoring due to sc3 reboot,JB
115 Apr 25 . about midnight onlsun1 went down
see listI
run: 6968 time stamp: 1114392680
no cdev,epic monitoring
115 Apr 25 . eraly hours: EEMC was going crazy so I had to fix that. Renee data may be sick
115 Apr 25 . changed Pplot setup so 02TC06 & 06TD11 will be marked as hot
115 Apr 25 R6115030+ box 103 has SpyCopyCat for chan 1,2,3,4 ,JB it is permanent problem
box 103 will not report it any more
115+ Apr 25+ 6115055-60134-chan copyCat box=101103
116 Apr 26 . about 6 am onlsun1 went down again no cdev,epic monitoring for 3 hours
117 Apr 27 . EMCAL crates 1 and 2,Took them out of the trigger.
118 Apr 28 . Trig thresh change:
EJP1 threshold change from 63 -> 61
BJP2 change from 96 --> 77 (4.9GeV)
EJP0 th = 54, BJP0 th = 46 (2 GeV for both)
new offline Trig ID
120 Apr 30 612006-17 copyCat box=93 & 103 is all the time
120 Apr 30 612017,19,50,53 ETOW corruption 2xfff,
120 Apr 30 612023 ETOW fires trig like mad
120 Apr 30 612032-49 copyCat box=93,103,110
121 May 1 6121006-22 copyCat box=93,100,102,103,110 + cr=1 ETOW is bad
121 May 1 BBC rate =100K, pol 51% for blue and Yellow
121 May 1 6121043,45 copyCat box=103 + cr=1 ETOW is bad
122 May 2 J/Psi trigger is now in express stream
123 May 3 6123004-28 copyCat box=83,103,107
123 May 3 6123015 1st test of adjJP , "jet topo" parameter set equal to "2", meaning adj was operative for eemc only (e.g., 0=off, 1=bemc,2=eemc,3=both),
123 May 3 100k ppProdMinBias with BTOW, ETOW, ESMD during CNI measurement. By George Igo is it good ?
123 May 3 .at ~20:00 with ~125k BBC and and ~50% polarization.
124 May 4 . 8 hours ACCESS
126 May 6 6126069- by accident prescale favores EJP1 5x , day 125+6
126 May 6 F7079 has > 60 bXing, CNI pol timing changed
126 May 6 6126028 FEE pedestal for one of the towers in TP14 in JP6 caused EHT1 trigger to count high
126 May 6 6126032-52 box=72,103 -copyCat
126 May 6 6126071+ eeSpy is sensitive to JP ped and min/max
126 May 6 6126079 during pol measur, huge beam bckg<
127 May 7 17:42 - STAR magnet trip, bckg high
127+ May 7+ 6127054-8015 copyCat 4 chan for box 97,103
128 May 8 6128015-52 10S2 overhitted, MAPMT unstable
128 May 8 TPC in purge from 18:50, magnet trip 22:45
129 May 9 6129029 sick EJP DSM spectra
129 May 9 MAPMT is stable again
130 May 10 ,2am 6130007 Tw crate 5 has copyCut for 19 chan, chan=46-64 this persist, will not be reported as well as 4 copyCat in box 103
130 May 10 magnet trip 8 am
130 May 10 6130054-71 copyCat 4 chan for box: 103,110, cr5
130 May 10 6130057 LUT lost for crate 4
130 May 10 6123059 2nd test of adjJP , "jet topo=3", the rate was ~100Hz @ 100KHz BBC
131 May 11 6131007,9 high beam bckg
131 May 11 6131032 MAPMT corruption
131 May 11 6131092-98 ETOW cr 3 & 4 failure, to hot in WAH
132 May 12 6132014 ETOW cr 4 JP ped=61.ne.45
132 May 12 magnet current not archived since 1:30 am
133 May 13 3 hours ACCESS @ 6:30 am, Mapmt burped, WJ
133 May 13 6133047-51 ETOW & ESMD failure - see eeSpy
134 May 14 6134010 ESMD failure
134 May 14 6134021,61,62,84-86 huge beam bckg 5:1
135 May 15 6135033-38 huge beam bckg 5:1
135 May 15 6135051-53 huge copyCat in box 77, box 103 just 4, cr5 standard 19, large beam bckg
136 May 16 6136108 EJP5 ped at 40
136 May 16 6136065+ EJP2 DSM change from 65 to 69 higher EJP2 thresh
136 May 16 evening, serious troubles with DAQ/Trigger , spurious tokens
137 May 17 6137034-47 ETOW and MAPMT boxes are sick run is probably garbage
137 May 17 6137058 EJP6 ped at 0
137 May 17 evening, troubles with DAQ/Trigger persist
138 May 18 6138010-12 EJP min/max <0.5
138 May 18 ~2 am crash of magnet in Brahms, BEMC and EEMC crate nedded configurations
138 May 18 ACCESS 8 am WJ replaced FEE board 2 in crate 5, within a day we get all fixed in software too
138 May 18 6138031+ copyCat from ETOW crate 5 is gone !
138 May 18 6138031+ ETOW cr 5 has wrong FEE peds, ignore triggers form crate 5
138 May 18 6138031-46 Will plays with data and hardware trash
138 May 18 6138047 good FEE ped run to be used in the future
138 May 18 6138062+ FEE ped4 loaded for all 6 ETWO crates all ETOW triggers are usable ,Pplot is not updated
139 May 19 6139005+ new tower peds in Pplot, I forgot MAPT peds - is trash
139 May 19 6139053+ ETOW+ESMD Pplot peds are good now, I used run 6139013, 'onlped' loaded to DB as well
139+ May 19+ 6139068-40017 Scott is playing with unmasking of TP10 in JP5 , he did it at the end. ETOW trig is fully functional
140 May 20 6140020,21 EJP min/max<0.5
140 May 20 At 2:55 p.m. the STAR magnet quenched.
140 May 20 6140047+ SpyCopyCat: ESMD crate=71 : 101,102,103,104
crate=103: 1,2,3,4
continuous, will not be reported here
140 May 20 6140077 SpyCopyCat: ESMD crate=71 is gone, only crate 103 remains in this state
141 May 21 6141004-9 JP6_sum xMax=42 not at 45
141 May 21 6141030 SpyJPfreq: min/max=0.411 ± 0.072 (Nmin=46 Nmax=112)
141 May 21 6141046-49 ESMD corruption , EEMC JP ratio <0.5, see eeSpay
141 May 21 6141050-69 SpyCopyCat: ESMD crate=68 : 65,66,67,68; +crate=103
141 May 21 6141050-74 Yellow polarization dropped throughout the run.
142 May 22 6142025 We saw a deadtime problem in the first ppProduction run
142 May 22 61colspan=2> 42074-82 ESMD corruption
142 May 22 additional real time monitor for our BG see listK
143 May 23 R6143012-14 min/max=0.345 ± 0.064 (Nmin=39 Nmax=113)
143 May 23 1 hours access
144 May 24 R6144009-26 min/max=0.328 ± 0.061 (Nmin=38 Nmax=116)
144 May 24 6144051-67 min/max=0.314 ± 0.059 (Nmin=37 Nmax=118)
SpyCopyCat: ESMD crate=79 , bad channels: 17,18,19,20; +crate=103
144 May 24 tower 01TB10 (crate 1, FEE channel 69) masked by Steve V.
145 May 25 , noontower 01TB10 is good unmasked by Steve V.
145 May 25 6145008,9 JP6_sum xMax=165 not at 45
145 May 25 6145013-28 min/max=0.137 ± 0.033 (Nmin=20 Nmax=146)
145 May 25 6145037-38 SpyJPpedestal: JP1_sum xMax=27 not at 45
JP2_sum xMax=102 not at 45
146-8 May 26+ 6146020-8002 SpyCopyCat: ESMD crate=108 : 81,82,83,84; +crate=103
146 May 26 . Access
146 May 26 . rhis fill # not recorded in STAR DB for ~24 h, fixed later by Michael.
147 May 27 MCR have started to change the spin pattenrs today see list
148 May 28 R6148012-19 min/max=0.382 ± 0.069 (Nmin=42 Nmax=110)
148 May 28 R6148046+ EEMC had 3 MAPMT boxes that did not configure properly,
148 May 28 R6148056-9004 min/max=0.422 ± 0.072 (Nmin=49 Nmax=116)
149 May 29 R6149047-50037 min/max=0.376 ± 0.067 (Nmin=44 Nmax=117)
SpyCopyCat: ESMD crate=91 : 97,98,99,100; +crate=103
150 May 30 Tower 8TA07 added to the list of dead tube/bases. , Steve
151 May 31 R6151007-32 only SpyCopyCat as above
151 May 31 R6151030 last run before change to 410 GeV

pp @ 410 GeV

day date/hour first run what was done , who consequences for off-line/DB
154 June 3 R6154005 First 410GeV pp collisions Polarizations are small
154 June 3 R6154045 Last 410GeV pp collisions

back to pp @ 200 GeV Long

day date/hour first run what was done , who consequences for off-line/DB
154 June 3 R6154051 First 20GeV pp collisions very bad background
155 June 3 R6155024 JP2_sum xMax=106 not at 45
156 June 4 . lost controll over Endcap and CANbus No EEMC data for next few days
156 June 4 . Problems w/ spin bits timing noticed by Akio, for fills 7238, 7240, 7241 and middle of 7249 It hapenned later as well. I (Jan) do not truts spin bits at all.
158 June 6 ,3 pm ACCESS Will fixed CANbus
158 June 6 R6157038+ . EEMC back in the game
159 June 7 .Fill at noon had a "longer AGS bunch length" Z-vertex distr.is "fatter"
158 June 8 ACCESS 8am fix of EMC CANBus
158 June 8 . perhaps hot tower ch98-cr2-2TC06 masked? for a short period
158 June 8 .pol infor not recorded in cdev for ~22 hours, till Jun-9-8am
161 June 10 R6161097-994P1 (aka #84) was dead, fixed in next run
161+ June 10+ R6161104, 20052a MPMPT box was dead, do not know which one
162 June 11 R6162030+ Change in v124 fine delays for spin bits.
165 June 14 R6165005 Last pp 200GeV Long ,F7281

pp200 GeV Transverse Polarization

day date/hour first run what was done , who consequences for off-line/DB
165 June 14 R6165031 First pp 200GeV Transverse ,F7293 ETOW broken,scaler broken
165 June 14 18:30 data taken during CNI pol measurement find runs and reject
166 June 15 R6166042+ powercycle pisos ETOW fixed
166 June 15 R6166056-66 ETOW crates 5 & 6 are bad do not use JP 5+6
166 June 15 R6166096-78 scaler data were lost
167 June 16 R6167082 some MAPMT boxes are sick
167 June 16 R6167085,86 16 MAPMT boxes [64-68], [70-79] are sick
167 June 16 R6167088 Last pp 200GeV Transverse ,F7296

pp200 GeV back to longitudinal polarization

day date/hour first run what was done , who consequences for off-line/DB
167 June 16 R6167088 First pp 200GeV long, F7300
167 June 16 -21 my personal runQA runs
171 June 20 6171030+ collspan=2> PPlot has been fixed and BTOW spectra are saved in .root files

pp200 GeV Test of larger beta*=1.1 @ STAR , Transverse Polarization

day date/hour first run what was done , who consequences for off-line/DB
172 June 21 R6172034-37 JP5_sum xMax=36 not at 45, ETOW create 5 is sick

pp200 GeV longitudinal Polarization , back beta*=0.9 @ STAR

day date/hour first run what was done , who consequences for off-line/DB
172 June 21 ? sc3 had disk full, cdev web pages were not updated for ~24 hours
172 June 21 ? Magnet problems
172 June 21 ? Btow crate 0x1c is down till end of the run


Auxiliary info
Crate 1, chan. 97 (high ped) => trigger mask for crate 1, board 4,
                                                  J1 -> 0x00fd 
Crate 4, chan. 117 (high "group" => hot tower) => trigger mask for
                                                 crate 4, board 4, J4 -> 0x00df 
To mask crate 6 ch31 do: cr6,  board 1, J3 from 0xf8f8 to 0x78f8. 

existing muDst

Format:
  run,    trigMix,nEve, nFile,comment, muEzt_location
 R6031040, minB, ?, ?, final timng for towers , balewski@HPSS
 R6031nnn,minB,43K,119, time scan for mapmt: towers OK , balewski@HPSS
------- day 032  EHT trigger is on --------
--------muEvent added to  muDst ------------
 6034014,cuProd,99K,181,034/, 
 6035106, cuProd,130K,, evaluation of HV set E 
 6041nnn, rampTrig, ~2M eve, large sample for evaluation of EHT6 trigger , balewski@HPSS
 6044054, prodCu, 130K, 200, final HV for ETOW & ESMD ,  balewski@HPSS
  ---  after ACCESS on 2/17 ---
6048024, prodMinB, 56K,88, only cr3brd2 has stuckADC ,eemcdb@data05 &  balewski@HPSS
6048028, emcPed, 3K - ped run , used for fee ped4,eemcdb@data05 &  balewski@HPSS
------ no EEMC setting has been change after this line ----
6049091, minB,99K,162, all works, eemcdb@data05 & balewski@HPSS
6049092, minB,63K,106, all works, eemcdb@data05 & balewski@HPSS

6049109, ramp, 380K, ~55, all works,eemcdb@data05 &  balewski@HPSS
6049126, minB,53K,~80, all works, eemcdb@data05 & balewski@HPSS
6049127, ramp, 1000K, ~80, all works,eemcdb@data05 &  balewski@HPSS
6049129, minB,108K,~175, all works,eemcdb@data05 &  balewski@HPSS
6049130, minB,32K,~46, all works,eemcdb@data05 &  balewski@HPSS
6049130, minB,33K,~48, all works,eemcdb@data05 &  balewski@HPSS
6049131, minB,32K,~50, all works,eemcdb@data05 &  balewski@HPSS

6060031, just zeroBias events,  balewski@HPSS

---- CuCu62----------
6073013,minB,198K,150+120, all works  , balewski@HPSS
6073016, minB, fraction, box=83=4P1 is off,  balewski@HPSS

MAPMT timing scan:
6073038,minB,100K,16, TCD phase=48,  balewski@HPSS
6073039,minB,100K,15, TCD phase=68,  balewski@HPSS
6073044,minB,100K,16, TCD phase=58 (default),  balewski@HPSS
6075014,minB,100K,14, TCD phase=78,  balewski@HPSS
6075015,minB,100K,15, TCD phase=38,  balewski@HPSS
6075016,minB,100K,15, TCD phase=58 (default),balewski@HPSS

EJP test by Renee
6081039,minB,142K,12, EJP thres 1 , balewski@HPSS
6081040,minB,111K,12, EJP thres 2,  balewski@HPSS

--------- pp200-------------------

6097036,testMinB,400K,80,all works except copyCat in ~5 MAPMTs
6101017,minB,sample,10, w/ TPC; all works except box83=2xfff; box98=headCorr40%

  E+B HT+JP tests, large beam bckg, skip first 100 eve in every muDst  
6103022,HT test, EHT1=5, 25K trig,    balewski@HPSS
6103025,HT test, EHT1=11, 1700 trig,   balewski@HPSS
6103029,HT test, EHT1=21, 400 trig,    balewski@HPSS
6103045,HT test, EHT1=25, balewski@HPSS
6103038,JP test, EJP1=60, balewski@HPSS
6103040,JP test, EJP1=76, balewski@HPSS
6103043,JP test, EJP1=88, balewski@HPSS

   runs with gradualy reduced beam background
6109018, ppPprod, 14K, 13,   , balewski@HPSS 
6109021, ppPprod, 98K, 25,  largest beam Bckg , balewski@HPSS
6110012, ppProd, 100K, 72, ppProd w/ J/Psi
6111021, ppPprod, 100K, 67, balewski@HPSS
6113004-6,51-53, 58,58,74 - varous runs, rather short
6114019, 21,30
61170117, emcCheck, 20K,5 


6121034, prodMinB, 200K, 20,   longer minB run
6139013, prodMinB, just 10 of 64 daq files


 

  


EEMC DSM math: E_T=0.24 GeV * (Dsm value -1) ; DSM ped =1
DSM thr=7 == 1.5 GeV = E_T=(7-1)*024 DSM thr=19 == 4.3 GeV E_T

BEMC DSM math: At the DSM level, this gives the following BTOW calibrations: ET = (HT DSM - 1) * 0.189 GeV ET = (JP DSM - 25) * 0.094 GeV

We are shifting the ADC data by 5 bits.  The PMT pedestals
are subtracted to give 0.25 channels as the trigger pedestal.
If I am reading your graphs correctly, this gives
32* 0.007032 = 0.225 GeV/ADC, so the high tower 18
trigger (which turns on at 19) = (19-0.25)*0.225 = 4.3 GeV.

The HT12 trigger turns on at 13, giving 2.9 GeV.

Stephen Trentalange


ListA towers affected by failure of crate 1 ch 13-31, February 5-14 ? 11TE10 1 13 11 E 10 36.603 12.56 17.01 0x0000 0x0000 P11TE10 10058 11TE11 1 14 11 E 11 38.643 16.75 20.75 0x0000 0x0000 P11TE11 10059 11TE12 1 15 11 E 12 40.415 23.61 28.71 0x0000 0x0000 P11TE12 10060 12TA01 1 16 12 A 1 19.035 9.50 14.10 0x0000 0x0000 P12TA01 11001 12TA02 1 17 12 A 2 20.846 19.02 24.07 0x0000 0x0000 P12TA02 11002 12TA03 1 18 12 A 3 22.702 20.27 23.87 0x0000 0x0000 P12TA03 11003 12TA08 1 19 12 A 8 32.725 20.01 23.56 0x0000 0x0000 P12TA08 11008 12TA09 1 20 12 A 9 34.629 6.68 10.83 0x0000 0x0000 P12TA09 11009 12TA10 1 21 12 A 10 36.603 17.72 21.62 0x0000 0x0000 P12TA10 11010 12TA11 1 22 12 A 11 38.643 14.83 19.18 0x0000 0x0000 P12TA11 11011 12TA12 1 23 12 A 12 40.415 11.98 15.88 0x0000 0x0000 P12TA12 11012 12TB01 1 24 12 B 1 19.035 10.51 15.21 0x0000 0x0000 P12TB01 11013 12TB02 1 25 12 B 2 20.846 12.33 15.88 0x0000 0x0000 P12TB02 11014 12TB03 1 26 12 B 3 22.702 14.73 19.23 0x0000 0x0000 P12TB03 11015 12TB08 1 27 12 B 8 32.725 21.01 25.56 0x0000 0x0000 P12TB08 11020 12TB09 1 28 12 B 9 34.629 12.11 15.31 0x0000 0x0000 P12TB09 11021 12TB10 1 29 12 B 10 36.603 13.67 17.72 0x0000 0x0000 P12TB10 11022 12TB11 1 30 12 B 11 38.643 16.25 19.55 0x0000 0x0000 P12TB11 11023 12TB12 1 31 12 B 12 40.415 20.92 24.47 0x0000 0x0000 P12TB12 11024

  ListB  Feb 28 
This morning 
Renee set up masks to block them out.

Up till now the channels masked out were

crate    ch
1        97
4       117
4        18
CuCu62 trigID 76007 = minB zdc based, 76011=minB BBC based
Note that currenlty cr 4 ch 18 does not look hot.  We decided not
to make a change and leave.  We did not have time to look back very
far and see when it had gone away.

The new problems are

Crate   ch     tube      jumper      old mask     new mask
3       81    3TD05      jp3b3         0xooff       0x00fd
4       46    6TD11      jp1b2         0xf8f8       0xb8f8

Renee has  loaded these and made them the default.

 listC Broken Mapmt pixels from Julie, data from day 44
 * 12S2 ch 38 & 39 - stuck bits 5 & 7
 * 12S3 ch 72-75 stuck bit 0
 * 2S1 ch 108-111 stuck bit 4?
 * 3S2 ch 177 too high ped
 * 6S2 ch 0-3 -multiple peaks

CuCu62 trigID 76007 = minB zdc based, 76011=minB BBC based

listD NeW HV for some towers for pp 200

slopes form run 6073013 were used.
tower  tube  oldGain  newGain  gChngFact  oldHV  newHv  hvChngFact
01TA05  P01TA05  5.7  7.47  1.31  871.5  900.3  1.03
02TE02  P02TE02  5.9  7.26  1.23  674  691  1.03
05TD10  P05TD03  12.6  9.2  0.73  730.3  703.1  0.96
06TD11  P06TD11  17  9.86  0.58  782.7  733  0.94
06TE04  P06TE04  6.5  7.6  1.17  672.9  685.7  1.02
07TA01  P07TA01  5.9  6.84  1.16  706.4  719.1  1.02
07TB09  P07TB09  14.1  8.74  0.62  800  755.2  0.94
07TC11  P07TC11  7.9  9.8  1.24  681.9  699.8  1.03
07TE02  P07TE02  6.3  7.31  1.16  702.4  715.1  1.02
07TE06  P07TE06  6.2  7.87  1.27  698.2  718.6  1.03
08TA11  P08TA11  8.3  9.79  1.18  732.1  746.8  1.02
08TC03  P08TC03  6.4  7.55  1.18  790.6  806.5  1.02
08TC07  P08TC07  9.8  8.13  0.83  832.1  813.6  0.98
08TD08  P08TD08  9.8  8.23  0.84  852.6  834.9  0.98
08TD09  P08TD09  7.3  8.69  1.19  856.6  874.7  1.02
09TE02  P09TE02  6.2  7.25  1.17  715.5  729.2  1.02
09TE08  P09TE08  7  8.26  1.18  699.5  713.6  1.02
10TA09  P10TA09  11.6  8.7  0.75  777.1  750.6  0.97
12TD01  P12TD01  8.4  6.8  0.81  837.9  816.9  0.97
12TD09  P12TD09  7.5  8.7  1.16  674.6  686.8  1.02

Legend:
'old' means current HV set F
'new' means proposed in this iteration (HV set G)

summary of the Heavy Ion data set we collected this year, you can find one on the STAR Operations page, or via the following link: http://www.star.bnl.gov/STAR/ops_l/summaryFY05-cucu-run.pdf Bill Christie
pp200 - BBC rate, by Jim
The BBC AND rate was 10kHz
there was 15x1011 in yellow
and 23x1011 in blue

Max they expect to store in a bucket is 1x1011 (Mei quotes .9)

so the max is ~56x1011 per beam so this means the 10kHz yesterday
was 11% (23x15/562) of the max possible with 56 bunches.  Thus
the max bbc rate we can get is 90kHz with 56 bunches.  Thus your
requirement of 110kHz BBC rate requires them to start developing
more than 56 bunches before we go to physics running.  Maybe that
is the direction you want to push them?  or maybe we are happy 
getting going on minbias with 80kHz?

Fast detector rates
I then ran BTOW, ETOW separately and then with ESMD added in.
The DAQ rates were

ETOW alone 3,000Hz
BTOW alone 1,800Hz
ETOW+ESMD  1,500Hz

Jim

HT & JP thresholds , take 2
In the endcap we use a pedestal of 1 on each tower so 

EEMC  HT Eth=(DSM-1)x.24GeV/ch
EEMC  JP Eth=(DSM-45)x.24GeV/ch

I think Oleg and Oleksander went to a similar scheme so that

BEMC  HT Eth=(DSM-1)x.192GeV/ch
BEMC  JP Eth=(DSM-25)x.096GeV/ch

Are these correct? Jim

bemc-ht2-mb uses threshold BHT2 etc... the "mb" triggers are the ones to use, as they include the BBC coincidence. Results --> emc2-hn , April 13 High Tower Trigger Rate Scan Results > ---------------------------------------- > N.B. Set BHT Th0 = EHT Th0 = 1 > Set BHT Th2 = 32 > Set EHT Th2 = 26 > All Run numbers below should have 61030 pre pended. > > Run# mb rate(Hz) BHT rate(Hz) EHT rate(Hz) BHT Th1 EHT Th1 > 22 55 k 1073 866 6 5 > 23 55 k 310 207 8 7 > 24 55 k 106 73 10 9 > 25 55 k 43 33 12 11 > 26 54 k 20 19 14 13 > 27 54 k ?? 13 16 15 > 28 53 k 2.3 5 18 17 > 29 53 k > 1.6 2.8 22 21 > 30 53 k 1 2 24 23 > 31 52 k 1950 2000 5 4 > 45 47 k 0.5 1 26 25 > 46 47 k 0.2 .4 28 27 > > Jet Patch Rate Scan Results > ---------------------------- > N.B. BJP Th0 = EJP Th0 = 1 > BJP Th2 = EJP Th2 = 500 > > Run# mb rate(Hz) BJP rate(Hz) EJP rate(Hz) BJP Th1 EJP Th1 > 38 49 k 220 120 60 60 > 39 49 k 51 22 70 68 > 40 48 k 16 7 80 76 > 41 48 k 6 4 90 80 > 42 48 k 2.8 2.8 100 84 > 43 48 k 1.3 1.5 110 88 > 44 48 k 0.7 0.9 120 92 > >

CNI problems summary, resolved?, April 19
 
Hello spinners--We had four problems with the carbon CNI
polarimeters that we did not understand, all solved this evening:

1. Blue cross section had slope larger than e^(-60t).  This was due
to the target.  When we changed to a different vertical target, the
slope was then 60.  We actually then lost that target, changed to a
horizontal target, and also observed a slope of 60.  The target
position changes the slope because of the sharp energy dependence
of multiple scattering.

2. The yellow polarization at flattop was low.  This was not seen by
the local polarimeters at Star and Phenix, where the polarization of
blue and yellow appeared to be about the same.  This was due to a
maximum energy cut in the CNI carbon code used by the FPGAs.  The
energy was too high, 3.2 MeV, instead of the usual 1.4 MeV.  This
apparently allowed prompts to block elastics.  And apparently yellow
flattop has more prompts than yellow injection or blue, both injection
and flattop.  We do not yet understand why the effect is so large for
the online.  However, we have verified the effect by switching back to
the incorrect maximum energy, getting lower polarization, then going
back to the correct max., getting the high polarization again.

3. We were also puzzling over why the AGS showed higher polarization
than RHIC at injection.  They appear to be equal now, but this is only
two measurements.

4. We did not understand why the offline number of events for the CNI
measurements was lower than online (20% to 40%) for the same cuts, and the
offline polarization was higher.  With the correct energy maximum, the
numbers of events and polarization are the same, online and offline.
We do not yet understand the reason that the online and offline are
affected differently.  (The offline is still affected by the maximum
energy cut, but less.)

Conclusion: tonight we measure about 45% polarization for blue and yellow
at flattop.  (This uses the jet result for A_N at flattop.)  We also
measured about 50% polarization at injection for blue and yellow (this
uses the A_N from E950 at 22 GeV).  We will be exploring the effect of
the maximum energy cut this evening, but we expect that the (more) correct
measurements use the lower maximum energy cut, mainly because of 4.

We have decided to change only the yellow detectors tomorrow, that have 
very high leakage currents, but not blue.

     Gerry and Sandro


listG beam cogging for pp200
Run2-4 pp runs, we had 4-10 o'lcokc cogging
During CuCu run, and pp till last week, it was 2-8 o'clock cogging
Last friday, PHRNIX requested 4-10 and STAR agreed, so they did.
2 days ago night/yesterday morning, CAD moved backto 2-8 w/o asking us
Yesterday night/this morning, we are back to 4-10
Hopefully they don't change it any more

2-8 cogging = yellow bunch1 and blue bunch1 collide at 2 and 8 o'clock
4-10 cogging = yellow bunch1 and blue bunch1 collide at 4 and 10 o'clock
OGAWA, 
---------
In principle cdev's patternRotationM has the cogging, 0 being 4/10 and 60 being 2/8.  In practice this entry was not updated in time when the cogging shifted on day 106.  It is one of several reasons why I have and keep scaler time distributions and scan them for the positions of the abort gaps (among other features).

Ernst 


BTOW calibration for run 5
Hi all, 
I passed this around in March, here it is again:

The result of the tower-by-tower MIP calibration is posted at:

http://www.star.bnl.gov/protected/spin/mmiller/emc/calibration/cucu/run5_cal.eps
--> 27.35 GeV / 4066 / sin(theta)

the 4066 is assuming that we have ~30 counts in the average pedestal.

If I assume that the MIP--> electron calibration, which really cleans up
the last 2-3 eta rings, is the same in 2005 as what it was in 2003 and
2004, then I get this:

http://www.star.bnl.gov/protected/spin/mmiller/emc/calibration/cucu/eshifted_run5_cal.eps
--> 24.21 GeV/4066/sin(theta)

So, the upshot is the calibration is probably ~24GeV/4066/sin(theta)

I doubt that the difference between 27.35 and 24.21 is even resolvable
at the DSM level. -Mike


Ernst BBC background measure http://spin.lbl.gov/STAR/spin/monitor/background contains background fractions by run as determined from the abort-gaps in BBC scalers.
BG-Y-11 and BG-B-11 add up to the total BG-11. Same for -12. The difference is if the BBC coincidence bit is read out from board 11 or 12. So this effectively reduces the 6 numbers to 2, give or take some details. I define Y to mean that the yellow beam collides with empty blue and B to mean that the blue beam collides with empty yellow. I tend to expect that the sum is all you need.


BEMC DSM spectra added by Alex 1. Pedestal for each Jet patch. They are calculated every 10 events, discarding the highest jet pacth 2. Jet patch value vs. patch id. This is the 2D histograms with the spectrum for each jet patch 3. Same as 2 but fill only the highest jet patch in the event 4. Jet patch frequency. a 1D histogram where we fill which jet patch would trigger the event.


listH mask out tower 2TC06, April 24 I have decided to mask out tower 2TC06: crate 2, chan 98 (crate 2, board 4, j1-> 0x00ff->0x00fb) This configuration with new LUTS is loaded and will be used in the next fill (no beam now). I spent some time this afternoon trying to debug and decide if the problem was really a tower or a FEE problem. Several iterations of power cycling and hard FEE resets (you can see this going on in pPlots between 4:30 - 6pm) did not solve the problem so I decided to mask. Please let me know if I have gotten the calculation incorrect. For future QA purposes I tried to figure out when this hot tower popped up. 1) Not present Friday evening shift (21st). 2) Saturday morning owl we ran all night with no pPLots 3) First run on Saturday evening (22nd) shows hot tower 6113055 4) I was called Saturday night ~10:30 for crate failure/reload but beam was dumped soon afterward and I could not tell from panitkin if problem was solved. 5) No beam on owl Sunday morning. 6) Hot tower back this afternoon -> decided to mask So runs after 6113055 and before the first run of this fill should be flagged as having a hot tower. The tower was not so hot as to cause runaway EEMC rates in DAQ.


listI crash on onlsun1 , April 24+5 RunLog a bit trickier. Stuff was being sent from DAQ (event info) but nobody receiving it. Michael working with Jeff L. to restore some of this information. Unclear what all can be easily restored. Missing info: * event counts * trigger mix Could also be retrieved from DAQ data files too if necessary.


B & E EMC calibration take 3

ET = (BHT DSM - 1) * 0.189 GeV
     = (BJP DSM - 25) * 0.094 GeV
     = (EHT DSM - 1) * 0.234 GeV
     = (EJP DSM - 45) * 0.234 GeV

Under the assumption that the triggers "turn on" 1 DSM channel above
threshold (i.e., requirement for setting bit is > threshold), the effective
thresholds are presently (April 27) as follows:

System    Threshold      DSM Value      ET equivalent
--------   ----------      ------------      --------------
BTOW       JP0                 65                   3.85 GeV
BTOW       JP1                 66                   3.95 GeV
BTOW       JP2                 96                   6.77 GeV

ETOW       JP0                 60                    3.74 GeV
ETOW       JP1                 63                    4.45 GeV
ETOW       JP2                 65                    4.91 GeV

BTOW       HT0                 6                     1.13 GeV
BTOW       HT1               13                     2.46 GeV
BTOW       HT2               17                     3.21 GeV

ETOW       HT0                 6                      1.40 GeV
ETOW       HT1               11                      2.57 GeV
ETOW       HT2               13                      3.04 GeV


more bunches not implemented yet (May 4) MCR may switch to this patter starting next fill this afternoon. It seems like we get 4 extra bunch crossing (52 to 56). Also we may have some inbalance in 4 spin configrations (let me check this again). Akio's collection
Please have a look if this is acceptable.
The 120 shown locations in the file are
separated by 3 buckets (108ns).

Wolfram

   Collision offset: 0
YELLOW   BLUE
No of Bunches   : 61 No of Bunches   : 61
Polarization    : ON Polarization    : ON
  1 1 1    81 1 1
  2 0 0    82 0 0
  3 1 1    83 1 -1
  4 0 0    84 0 0
  5 1 -1   85 1 1
  6 1 -1   86 1 -1
  7 0 0    87 0 0
  8 1 1    88 1 1
  9 0 0    89 0 0
 10 1 1    90 1 -1
 11 0 0    91 0 0
 12 1 -1   92 1 1
 13 0 0    93 0 0
 14 1 -1   94 1 -1
 15 1 1    95 1 1
 16 0 0    96 0 0
 17 1 1    97 1 -1
 18 0 0    98 0 0
 19 1 -1   99 1 1
 20 0 0   100 0 0
 21 1 -1  101 1 -1
 22 0 0   102 0 0
 23 1 1   103 1 1
 24 0 0   104 0 0
 25 1 1   105 1 -1
 26 1 -1  106 1 1
 27 0 0   107 0 0
 28 1 -1  108 1 -1
 29 0 0   109 0 0
 30 1 1   110 1 1
 31 0 0   111 0 0
 32 1 1   112 0 0
 33 0 0   113 0 0
 34 1 -1  114 0 0
 35 1 -1  115 0 0
 36 0 0   116 0 0
 37 1 1   117 0 0
 38 0 0   118 0 0
 39 1 1   119 0 0
 40 0 0   120 0 0

 41 1 -1    1 1 1
 42 0 0     2 0 0
 43 1 -1    3 1 -1
 44 0 0     4 0 0
 45 1 1     5 1 1
 46 1 1     6 1 -1
 47 0 0     7 0 0
 48 1 -1    8 1 1
 49 0 0     9 0 0
 50 1 -1   10 1 -1
 51 0 0    11 0 0
 52 1 1    12 1 1
 53 0 0    13 0 0
 54 1 1    14 1 -1
 55 1 -1   15 1 1
 56 0 0    16 0 0
 57 1 -1   17 1 -1
 58 0 0    18 0 0
 59 1 1    19 1 1
 60 0 0    20 0 0
 61 1 1    21 1 -1
 62 0 0    22 0 0
 63 1 -1   23 1 1
 64 0 0    24 0 0
 65 1 -1   25 1 -1
 66 1 1    26 1 1
 67 0 0    27 0 0
 68 1 1    28 1 -1
 69 0 0    29 0 0
 70 1 -1   30 1 1
 71 0 0    31 0 0
 72 1 -1   32 1 -1
 73 0 0    33 0 0
 74 1 1    34 1 1
 75 1 1    35 1 -1
 76 0 0    36 0 0
 77 1 -1   37 1 1
 78 0 0    38 0 0
 79 1 -1   39 1 -1
 80 0 0    40 0 0

 81 1 1    41 1 1
 82 0 0    42 0 0
 83 1 1    43 1 -1
 84 0 0    44 0 0
 85 1 -1   45 1 1
 86 1 -1   46 1 -1
 87 0 0    47 0 0
 88 1 1    48 1 1
 89 0 0    49 0 0
 90 1 1    50 1 -1
 91 0 0    51 0 0
 92 1 -1   52 1 1
 93 0 0    53 0 0
 94 1 -1   54 1 -1
 95 1 1    55 1 1
 96 0 0    56 0 0
 97 1 1    57 1 -1
 98 0 0    58 0 0
 99 1 -1   59 1 1
100 0 0    60 0 0
101 1 -1   61 1 -1
102 0 0    62 0 0
103 1 1    63 1 1
104 0 0    64 0 0
105 1 1    65 1 -1
106 1 -1   66 1 1
107 0 0    67 0 0
108 1 -1   68 1 -1
109 0 0    69 0 0
110 1 1    70 1 1
111 0 0    71 0 0
112 0 0    72 1 -1
113 0 0    73 0 0
114 0 0    74 1 1
115 0 0    75 1 -1
116 0 0    76 0 0
117 0 0    77 1 1
118 0 0    78 0 0
119 0 0    79 1 -1
120 0 0    80 0 0

Beam separation pattern  in IRs: 0 1 0 0 1 1


listK
additional real time monitor for our BG.

Yellow V124 (new,2nd set)  tick delay 80
 ch7 revtick(bunch1) pattern, pulse width 24(RF tick)

Blue V124 (new,2nd set) tick delay 195
 ch7 revtick(bunch1) pattern, pulse width 24(RF tick)

At DAQ room, these 2 signals from v124 is timed to be "abort gap"
signal for BBC coincidence singal & delayed coincidences through
giga-link. Then go RHIC scaler:

ch5  = sisScaler.6a-star.4 = blue AG * BBC yellow BG (west delayed)
ch9  = sisScaler.6a-star.8 = blue AG * BBC coincidence (collision)
ch10 = sisScaler.6a-star.9 = yellow AG * BBC coincidence (collision)
ch11 = sisScaler.6a-star.10= yellow AG * BBC blue BG (east delayed)

Please note that ch# difference of 1 in ch# and how software call it.
Also I checked yellow AG*BBC yellow BG and blue AG*BBC blue BG.
Those 2 counts very slow (a good thing), so I'm almost sure the
timing is right. Yet I'll be re-checking once the current fill
is cogged.

Also made a gpm monitor page:

 /operations/app_store/Gpm/RHIC/Experiments/Star/star-ag-2005.mon

As we discussed at 2pm meeting, Angelika is going to make a page
out of existing old page + 3 new ones I made, and let both STAR
and MCR operator know, so that we look at the same plot at MCR
and STAR.

Full map of the scaler now look like:

ch
1 zdc coincidence (include killer bits)
2 zdc west
3 zdc east
4 zdc coincidence
5 blue AG * BBC yellow BG
6 zdc west (include killer bits)
7       zdc east ((include killer bits)
8 CTB multiplicity >1
9 blue AG * BBC coincidence
10 yellow AG * BBC coincidence
11 yellow AG * BBC blue BG
12 bbc coincidence
13 bbc east
14 bbc west
15 bbc east delayed coincidence (blue BG)
16 bbc west delayed coincidence (yellow BG)


For example, you can use a command:

/star/u/akio/afs/db/bin/bbcbg 6144009


OGAWA, akio  


listL
Dear all

 As we agreed, we start to rotate the spin pattern from store to store. 
The 4 patterns are defined as the following

 P1: (blue: +-+-...)(yellow:++--...)

P2: (blue: -+-+...)(yellow:++--...)

P3: (blue: +-+-...)(yellow:--++...)

P4: (blue: -+-+...)(yellow:--++...)

 And this information will also be broadcast on the TV screen. The normal format we are using right now is: bunchnumberPi, with i=1,2,3,4.

 So, all the fills till 7142 are P1 pattern, 7143 is P2 pattern and the current store 7151 is P3 pattern. 

 Best regards,

 Mei

ListM
Hi Jan:
Ad 1) BG-Y-11 and BG-B-11 add up to the total BG-11. Same for -12. The difference is if the BBC coincidence bit is read out from board 11 or 12. So this effectively reduces the 6 numbers to 2, give or take some details. I define Y to mean that the yellow beam collides with empty blue and B to mean that the blue beam collides with empty yellow. I tend to expect that the sum is all you need.
Ad 2) I have all values from the start of pp this year, but they are not yet web-downloadable (in a way that I would want to support). Basically, it is on my list (just below some LBL admin) to put archiving in place for all quantities in one go and in a way that will not cause me much work afterwards. First half of next week.
Ernst
ListN :
STAR bXing masks
- status as of Wed Oct 19 09:49:25 EDT 2005
If we define for a given run :
bx7 coming out of event and
off7 coming out of spinDb

then bxStar=(bx7+off7)%120
and we need to kick out:
 bx7=0
 bx7=119
 bxStar=20 (time bucket 61 in yellow, counting: 1-360)
 bxStar=60 (time bucket 61 in blue, -//-, cogging 2-8 )
or
 bxStar=100 (time bucket 61 in blue, -//-, cogging 4-10)

So far Julie found only off7=6 and the picture is simple:
'normal' cogging 2-8 :
^^^^^^^^^^^^^^^^^^^^^^
kick out  bx7={0,14,54,119} or alternatively
kick out  bxStar={6,20,60,5}

'other' cogging 4-10 :
^^^^^^^^^^^^^^^^^^^^^^
kick out  bx7={0,14,94,119} or alternatively
kick out  bxStar={6,20,100,5}