Last revised June 4, 2005
http://www.jlab.org/~lerose/e94107/E94-107Runplan2005.htm
June 2005 Hypernuclear Runplan
Documentation:
General
Overview
The
objective is to generate high resolution missing mass spectra for the reactions
16O(e,e’k+)16NΛ , 12C(e,e’k+)12BΛ, and 9Be(e,e’k+)9LiΛ. Problematic to the
endeavor are maintaining and verifying that the beam energy spread is small (σE ≤ 2.5 x 10-5) and
separating the kaons from the very large proton and pion background. The run
will be divided into four parts:
Preliminaries:
Detector checkout to be done in parallel with establishing beam, optics studies, and target thickness studies.
Establish beam, verify beam properties (details) (0-? days)
Optics Studies with 2-pass beam (details) (~1 day)
Establish beam, verify beam properties (details) (0-? days)
Establish and verify detector properties (details) (~2-3 shifts)
Waterfall target
thickness studies (details) (~1 shift)
Take calibration data on H2(e,e’k+)Λ, Sigma (details) (~1 day)
Production running on 16O(e,e’k+)16NΛ (~ 12 days @ 50%) (details)
If time permits one or both of the following:
Production running on 12C(e,e’k+)12BΛ (only if things go very well with 16O) (details)
Production running on 9Be(e,e’k+)9LiΛ (only if things go very well with 16O) (details)
Production Kinematics:
Einc =3.651 GeV; Pe=1.4414
GeV/c; Pk=1.96 GeV/c (Magnet settings)
(Analysis instructions):
These are NOT up to date!
(Special
note re “Tech-on-Call”)
(Septum Magnet
Controls) Must be updated
Mailing List: If you haven’t already done
so please subscribe to the e94107 mailing list (e94-107@jlab.org).
This will insure that you get all relevant e-mail news bulletins.
subscription is simple:
send an e-mail, with your e-mail
address as the sender, to majordomo@jlab.org
with:
subscribe e94-107
end
in the body of the message
General information/instructions for shift workers
At start of shift: Shift leader
should receive a shift leader information sheet from the previous shift. (shift_leaders.ps)
Before beginning check the beam conditions. The RF energy locks should be on (on the Hall A Tools page, check at the bottom in the "Beamline" box and see if "RF on" and "FB on" are both there and bothgreen. If not, call MCC and request that bean energy and orbit locks beturned on.
Beam Energy Spread: We have two
devices at our immediate disposal to monitor the beam energy spread, the OTR at
1C12 and the Synchrotron Light Interferometer (SLI) at the same place.
4/21/04: SLI at 1C12 has been calibrated by Arne Freyberger (see elog 1208080). Also, OTR at 1C12 tends to trip off the beam at high current. Use the SLI as a monitor of energy spread. If you observe an energy spread as reported by the SLI that is consistently >3x10-5 notify the Run Coordinator.
4/28/04: SLI is deemed fully operational (Freyberger message)
Beam position: 1H04A= (2,0).
1H04B=(-2,0). Beam size (note that it is not the
same thing as position) cannot be easily measured with high currents. Beam size
should be measured with a harp scan at 5 micro amps. Size should be less than
0.100 mm in x and y.
Raster size: We
are not running any raster on the carbon target. On the beryllium and
waterfall targets, use a raster size of 0.5x0.5mm2 in
SPOT++. Remember you need to have beam and
must have a CODA run going to use spot. Bob Michaels has
more instructions on the DAQ web page
for Hall A if you need additional documentation.
Beam Current: On the waterfall, carbon, and beryllium targets run
100 micro amps or as high as can be achieved. (120 works well)
Enter P0 and wait for things to settle (don’t forget to “cycle” Q2 and Q3 as per the white board)
As of 6/9/2005 septa are also set by typing in P0 as above (see below).
Septum Magnets:
Septum magnets are controlled by current.
For right septum the current can be calculated as I=92.58 * P0 where P0 is the spectrometer momentum in GeV/c and the current is in Amps.
For a right HRS momentum of 1.4414 GeV/c, the right septum should be at 133.44 Amps.
For left septum the current can be calculated as I=94.22 * P0 where P0 is the spectrometer momentum in GeV/c and the current is in Amps.
UPDATE 6/5/05:
Due to the fact that nobody bothers
to read any of this all the optics data were taken assuming that there was no
offset between the “set current” and the “magnet current”. As long as the
offsets don’t change this is not a disaster. For the duration of the 2005
e94-107 run we’ll set the septum magnets as they were set during the optics
runs. That is:
Right Septum “set current” = 92.58 * P0
Left Septum
“set current” = 94.22
* P0
For a left HRS momentum of 1.960
GeV/c, the left septum “set current” should be at 184.67 Amps.
For a right HRS momentum of 1.4414 GeV/c, the left septum “set current” should be at
133.44 Amps.
Update 6/9/2005 From
halog 145626
keyword=Septum
Setting is Now Automatic
The prescription for setting septum magnets is the same as described in halog 145128. However, thanks to Scott Higgins, the
controls have been changed so that henceforward, when you type in P0 on the
Hall A Tools GUI the set current for the septum in
that arm will be automatically updated. This is new, so shift workers should
still verify that this has been done correctly and make sure both the "set
current" AND "Magnet Current" are coming out properly (the
"Magnet Current" is slightly offset from the "set
current"). As with all the other spectrometer magnets, typing in the same
P0 as is already there will not update anything. Also, if you type a differnt set current in the septum magnet control GUI it
will override the one installed by the software the last time P0 was updated.
Be careful about typing in new P0's if someone is working on the magnets.
Read back current (labeled “Magnet Current” on the septum controls page or showing as the only
septum current on the Hall A tools page) should be within 0.5 Amps of this
value. (Conscientious and/or bored shift workers will double check
the arithmetic.)
NOTE:
Set current is a little different from magnet current. A good rule of thumb is
the following:
Right Septum: Magnet Current = Set Current - 2.2
Left Septum: Magnet Current = Set Current - 3.2
Targets: Target operational limits are as follows
(numbers for solid targets are with the cryotarget cold):
Prescales should be adjusted to give about 20 Hz of single arm T1, T3 each, and 40 Hz of T6 triggers. T2and T4 should be adjusted to give about 10 Hz each. Take all the T5 and T7 data possible.
On carbon, at 100 A, the trigger rates should be T1= 110 KHz, T2= 2.4KHz,T3=3KHz, T4=1.8 KHz, T5=600 Hz, T6=400 Hz, and T7= 5-10 Hz. The PS factors should be roughly 5000/ 230/ 150/ 170/ 1/ 10/ 1.
Check the prescales.
Analyze the first 50,000 events and see if the data looks good. (see analysis hints if needed).
Check the CODA GUI to see the event size. Event size should be 1.5-3 KB.
In case of start-run failure b/c of ROCS 12 and 16, follow these instructions:
(1) cancel start run in runcontrol(2) type reboot in the portserver windows for ROCS 12 and 16(3) wait and be patient(4) ROCS 12 and 16 will say they are now "booted"(5) wait and be patient(6) in runcontrol, hit Abort(7) wait and be patient(8) in runcontrol, hit Reset(9) wait and be patient ("transition Reset Succeeded")(10) in runcontrol, hit Configure and select WITHRICH(11) wait and be patient ("transition Configure succeeded")(12) in runcontrol, hit Download(13) wait and be patient ("transition Download succeeded")(14) try a start run again the key is to wait and be patient at each step. if this doesn't work, kcoda as usual, (kcoda, then follow the three steps list when you run kcoda) These instructions can also be found in: http://www.jlab.org/~adaq/halog/html/0404_archive/040423045635.html
RICH:
HV settings should be listed on the whiteboard.
Stop running and start a new one while ramping up HV,and another new run when HV is up and stable.
If there are frequent trips, contact the RunCoordinator or the RICH-on-call.
Run DAQ in "withrich" configuration
HALOG the strip chart once a shift
RICH pedestal run instructions:
(1) Take a run in RICHPED mode, nearly 5000 (five thousands) events,(2) login into adaql5 as a-onl,(3) go into ~/rich/getped/(4) edit run.list and update the last RICH-pedestal file(5) run getped12(6) rename pedestal1.out as rich_ped_top.dat and copy it into ~a-onl/C-RAM/ped/(7) remove pedestal2.out (8) run getped16(9) rename pedestal1.out as rich_ped_bottom.dat into ~a-onl/C-RAM/ped/(10) remove pedestal2.out(11) start a new run (DO NOT FORGET TO GO BACK INTO WITHRICH CONFIGURATION and to indicate it into the CODA pop-up window)