NEXT
User name spwells
Log entry time 09:44:30 on April 01, 2004
Entry number 81093
keyword=Run Plan 1 April Day through 2 April Owl
Run Plan
Guidance
-
From now on we will run with the GMS enabled all of the time. The normal
DAQ configuration should include the following:
-
PS5 (laser events) = 0
-
PS6 (source events) = 30
-
GMS mask should be on and spinning
When the GMS is working you should be able to see a finite number of
event
type 5s in the realtime monitor.
-
We have reconfigured the DMCHs so that the order of 1-4 are reversed.
This
means that from now on we should be using the following DMCH
configuration:
"Reference_FiB_Buddy". The configuration "Reference_FiB_Buddy" should no
longer be used.
-
Take one 120 Hz run per day, on day shift.
-
If beam will be gone for more than an hour, then take French DNL and
pedestal
difference data (procedure discussed below).
-
Maintain beam current at 40 uA (on LH2). MCC reads the MPS BCM to
determine
the beam current. This BCM reads a couple of µA higher than our BCM
so it may be necessary to request a beam current of 42 µA to get
the 40 µA we want.
-
Maintain beam position at 3H00A, G0, and G0B. 3H00C appears to no longer
be reading correctly so we should ignore it for now.
-
IHWP is now IN.
-
MCC is taking our abrubpt halo change from two days ago seriously, and
wants to investigate.
Detailed Procedure
-
MCC will take beam at 9:00 for beam studies until 12:00, and will access
the injector to install the Hall A Laser from 12:00-13:00.
-
When beam returns, we should spend at most 2 hours investigating
halo.
At the end of swing shift on 3/31/04 a vertical adjustment was made at
the G0 BPM's to lower the beam position there by about 0.5 mm, which gave
lower halo rates, back to near their nominal values. Some investigation
should be done to understand why this occurred. This should be
coordinated
closely with MCC. Some things to try:
-
- Remove 6mm hole and verify
that halo rates are reduced
-
- Reduce raster size to 1 mm
X 1mm, lower beam current to 10 uA, and verify that halo rates are
reduced
(scaled by beam current).
-
- Verify that Moeller systems
are in normal mode (MCC can do this):
-
# check Moeller raster is off
-
# check that Moeller kicker is off
-
# is Moeller wire target broken and hanging in the beam? (May require
setting
up Moeller run with wire target - no rate could mean wire target not
getting
hit, LAST RESORT due to time involved)
-
- Have MCC perform Harp scans
upstream with and without raster on
-
- Have MCC look into
optics
downstream of Lambertson separator
-
- Have MCC look into AC
components
of beam (DC component is claimed to be OK).
-
IF THE CAUSE OF THE CHANGE CANNOT BE DETERMINED WITHIN 2 HOURS,
CONTINUE
WITH RUN PLAN BELOW, WITH G0 BPM POSITIONS: G0 (-0.65, -0.275), G0B
(-1.1,
1.0).
-
After halo studies and stable beam returns in the correct
positions,
etc., we would like to perform another BCM calibration. A detailed
procedure
is outlined in the G0 Howto book, but involves a simultaneous calibration
of BPM's and BCM's. Due to the flakiness of BPM 3H00C, it is probably
best
to perform a BCM calibration on its own. Jianglai has agreed to be the
expert for this procedure, so page him when you are ready.
-
After the BCM calibration, we want to reestablish parity quality beam.
First, however, we will perform "Wells" plot scans (I make one simple
plot
looking for deadtime, and somehow my name is attached!). So, before this,
we should zero out the charge asymmetry by performing a RHWP scan to find
the zero crossing in the Hall C charge asymmetry. Then, perform 1/2 hour
runs at IA voltages of 5 V, 1 V, and 9 V, manually changing the IA
voltage.
For assistance, page Kaz.
-
It has also been requested to generate energy modulation data. In
previous
attempts to perform this, the detector response slopes w.r.t. energy were
very small, and it is believed that MCC had some energy lock or fast
energy
feedback system operating during this attempted scan. To do this, we only
need roughly a 5 minute run with the energy being modulated. However,
coordinate
this effort with MCC to ensure that all energy lock or energy feedback
systems are turned off. See below for detailed energy modulation
procedure.
-
At this point, we should reestablish parity quality beam with feedback
on. Contact Kaz, perform an RIP scan to get new feedback slopes, and get
feedback operational.
-
From this point on, take 1 hour long asymmetry runs on LH2
until
9:00 when MCC will take beam away for beam studies again.
New Considerations
-
The target FSD box has been wired into its own reboot box and can be
rebooted
from the GUI on cdaqs1. If the MCC gets errors claiming that the target
is in motion when it really isn't then it probably means the FSD box
needs
to be reset.
-
It has been observed that rebooting the Musson box can cause reboots of
the target FSD box and the target IOC. Exercise caution when performing
a Musson box reboot.
-
The Y readings at BPM 3H00C no longer appear to be sensible. The beam can
be right on at the other three BPMs we use (3H00A, G0, and G0A) and still
be off at 3H00C by a half a millimeter or me. For now, it is okay to
ignore
3H00C when tuning up beam and monitoring beam positions.
-
If G0 realtime monitor indicates that the Musson box has lost its sync
then use the following procedure to recover:
-
Press 'Reset All' on G0 realtime monitor. If this does not clear the
error
then proceed to the next step.
-
Ask MCC to take the beam away for 10 seconds.
-
Press 'Reset All' on G0 realtime monitor.
-
Error should clear and Musson box should resync.
Repeat procedure if necessary to clear error. If unable to clear error,
then contact the DAQ expert (P. King).
Beam conditions
-
Halo target(6 mm hole): IN.
-
2x2 mm raster ON
-
Check the nominal beam positions reproduced below.
|
3H00A |
3H00C |
G0 |
G0B |
X [mm] |
-0.45 |
-0.6 |
-0.65 |
-1.1 |
Y [mm] |
-0.8 |
-0.2 |
-2.2 |
1.5 |
NOTE THAT TO REDUCE HALO LAST NIGHT, THE Y POSITIONS IN G0 AND G0B
HAVE
BEEN LOWERED BY 0.5 mm EACH FROM THE ABOVE "NOMINAL" VALUES.
We request that MCC maintain these with a tolerance of +/-0.2
mm. Do not allow the beam to deviate by more than 0.5 mm. Ensure
that there is NO lock on 3C20 (check with MCC when position is off
and search for a reason)
-
Check the Halo rates MCC has the same Halo rate monitor GUI on their
screen
as we do. They should be using it for beam tuning. The following table
is about the best that has ever been seen for the rates. Since Friday
02/13,
the rates have been typically 2 times higher on 5 and 6 and up to 4 times
higher on 3 and 4. This may be due to increased "background" rather than
increased halo. The principal monitor is Halo3, which generally should
be no more than 10kHz. The rule of thumb for the fraction of beam hitting
the halo is to subtract the "no halo" rate from the "6 mm halo target
rate"
for Halo3 and then to multiply by 0.66 ppm per kHz. For example, the 40
uA data below yields 0.96 ppm.
Monitor |
No halo target [Hz/uA] |
6mm Halo target [Hz/uA] |
No halo target@40uA [Hz] |
6mm halo target@40uA [Hz] |
Halo3 |
18 |
25 |
1440 |
2080 |
Halo4 |
20 |
30 |
1600 |
2880 |
Halo5 |
250 |
300 |
20000 |
28000 |
Halo6 |
140 |
170 |
11200 |
16000 |
The 11 mm hole position is at -41.35 mm (stepper motor position on the
GUI), and the 6 mm hole position is at -57.8 mm. Out Position is "Home"
or 0 mm.
Always use the 6 mm hole target except when doing coil modulation.
If rates are too large, ask MCC to improve on beam quality.
-
Watch Herbert's paddle and associated anode current It should be giving
a value of about 3280 nA for 40 uA of beam with LH2 (see Paddle).
General settings for asymmetry
runs
Beam Current
-
I_beam = 20uA for G0 empty target (Gas Hydrogen).
-
I_beam = 15uA for G0 target frame (Aluminium)
-
I_beam = 40uA for G0 full target (Liquid Hydrogen)
High Voltage
-
The nominal HV file is the proton reduced gain file
(HV.halfgain_2nd_engineering_run.hvc).
-
A separate file is used to restore lumi and halo settings
(HV.2003-12-09-22.lumi_halo_on.hvc).
-
Check to make sure that HV is on after a long period down especially
following
a magnet fast dump or Moeller run.
DAQ Settings
-
Here are the default DAQ settings that should always be used unless a run
plan specifically calls for something different.
-
Configuration mode in RunControl GUI should be "ts_full2"
-
G0 DAQ Configuration Tool GUI
-
On the "TS and Prescales" tab:
-
30 Hz mode enabled.
-
Fastbus prescaler (PS4) = 5000
-
FastClear Disabled
-
GMS laser prescaler (PS5) = 0
-
GMS source prescaler (PS6) = 30
-
On the "CFD & DMCH Setting" tab: `
-
NA CFD threshold setting = 7
-
NA CFD width setting = 0
-
DMCH Reference Config = Reference_FiB_Buddy
-
DMCH Threshold: 50mV
-
On the "Coil Modulations Settings" tab:
-
Modulation Enable: ON
-
Modulation Pattern: Sequential
-
Beam Energy Modulation: OFF
-
For other configurations (Fastbus, DNL, ...) go to e-log entry #69965(Config)
Miscellaneous
-
When beam is being restored after a long period down make sure that the
MCC tunes to the correct position at the four BPMs in the hall (posted
on the X-terminal adjacent to the DAQ computers). Tuning to within
0.3-0.5
mm is acceptable.
-
Shift crews should watch the LTDs (visible on the TV above the DAQ
computer
in the counting house) to make sure the red error lights are not
flashing.
The lights in the electronics cage have to be off, which should be the
default state, for these lights to be visible. If there are LTD errors
contact the NA electronics expert immediately.
Instructions for Taking GMS Data
Detailed instructions can be found in the GMS
How-To, a copy of which should be in the binder.
-
Turn on the GMS mask. The control box is located towards the bottom of
the second rack in the 2nd floor G0 electronics cage.
-
Turn the switch labelled "Motor" on.
-
Check to make sure the LEDs on the box are flashing.
-
If lights are not flashing, then crank the 20 turn pot up until they are
flashing.
-
Use the pot to set a current between 180 and 200.
-
In the G0 DAQ configuration tool set the following prescale values:
-
PS5 (laser events) = 0
-
PS6 (source events) = 30
-
Start runs normally; label them as GMS on.
-
When the desired amount of GMS data has been taken then set the
prescalers
back to maximum by pushing the "Set prescales to maximum" button.
-
Turn off the GMS mask by flipping the "Motor" switch to the off
position.
Instructions for Coil Modulation and Energy
Modulation Data Taking
Setting up to Modulate (whatever)
-
Check with General Tool that the fast position feedback is OFF.
-
From the Monticello screen, open the modulation coil response screen by
doing the following from the Accelerator Main Menu :
-
Under Magnet, Open "magnet commander"
-
Open "3C"
-
Open "3 C Position Modulation"
-
"Hall C Position/Energy Modulation" is displayed
-
Note that this item is just to check the Coil modulation is turned
ON
-
Find the terminal window people are using for modulation, or open it
yourself
by:
-
Log into gzerol3 as gzero.
-
cd into either ~/bin or ~/users/rutledge
Coil Modulation
-
Start a run and fill out the comments cases in the "pink window" with:
"coil pulsing run"
-
Ask MCC to retract the Halo target (home position or 0 mm). In the
mean time Start a run.
-
Run the shell script ./gridmodulation (for grid pattern coil
modulation).
-
To see it working look on the G0realtimemonitor beamline screen.
-
Once the run ends, call MCC to return the halo target to the 6 mm hole
position.
Energy Modulation
-
Start a run and fill out the comments cases in the "pink window" with:
"energy pulsing run"
-
Run the shellscrpt: ./energymodulation
-
Lastly: I have seen, burried in the monticello controls *somewhere* a
panel
with controls relating to switching this Energy Modulation access to and
from Hall A/ Hall C. IF energy modulation does not work, I would have to
first dig through Monticello and find this screen, then make sure MCC had
set it to Hall C control of E mod.
-
To see it working (in theory) watch BPM 3C12_X,Y.
NOTE: Energy modulation affects ALL halls -For
the time being, we are notifying the Hall B shift crew before taking a
coil modulation run. I expect to get their permission to take them
without
notice in the near future.
NOTE: if you experience a long (more than 2 minutes)
beam
trip during the data taking, the data are useless. In order to save time,
the best is to keep the run going and just restart Gary's script. The
script
will repeat the grid 20 times, so shoft RF trips should be fine.
Instructions for 120 Hz data taking and
analysis
Data Acquisition Procedure
-
Change G0 DAQ Configuration in the GUI Tool
-
120 Hz mode enabled (don't forget to submit this change)
-
Fastbus prescaler (PS4) = To be set on Maximum (hit the key)
-
FastClear Disabled
-
GMS prescaler (PS5) = maximized
-
NA CFD threshold setting = 7
-
NA CFD width setting = 0
-
DMCH Reference Config = Reference_FiB_Buddy
-
DMCH Threshold: 50mV
-
When you are done use the Configuration GUI to :
-
Go back to 30 Hz
-
PS4 back to 5000 (manually)
-
Be sure to "Reset" g0realtime. Otherwise the "miscellaneous" display will
show evtype=2 events and the counts for the two helicity states will not
be equal when you resume normal (non-120 Hz) running.
Analysis Procedure
When the 120 Hz analyzer produces a root file called
~/scratch/root/G0Scaler120Hz.#####.root,
perform the following steps to log the results:
-
Use Jason's script to extract the 60 Hz noise, and multiples thereof. To
do this, type '~/G0Analysis/G0Scripts/extract60Hz #####'.
-
MAKE A LOGENTRY containing the run number and the relevant text
output from extract60Hz.
-
Inform the shift leader, especially if the values are out of spec.
For more info about the 120 Hz analysis, see logentry #70368 (120Hz-analysis).
Things To Do During Shift
-
Check whether the feedback is still working. If it fails, call the RC and
Kaz.
-
Check the IA, PZTX, and PZTY strip charts to be sure they are not railed,
or oscillating wildly. These strip charts are created with data of rather
poor statistics so do not try to draw conclusions about feedback
convergence
from them. Instead perform the next step.
-
After about two hours of data has been taken with the feedback turned on,
run Kaz's script to do the integrated charge and position asymmetries
check.
Log the results.
-
If the feedback is not converging, notify MCC that the beam is
unacceptable
because the feedback is not working; you should call Kaz, who will
probably
instruct you to try a set of IA and PZT scans. If the slopes are less
than
~150-200 nm/V for the PZTX and PZTY or less than 300 ppm/V for the IA,
or one or more of the devices do not give a zero crossing, the feedback
cannot be made to converge; Kaz will provide further guidance on what to
try if it is needed.
-
Also use G0Integrity to see if beam parity quality parameters are within
the specifications
-
Shift crew should watch the LTDs (visible on the TV above the DAQ
computer
in the counting house) to make sure the red error lights are not
flashing.
-
The lights in the electronics cage have to be off, which should be the
default state, for these lights to be visible. If there are LTD errors
contact the NA electronics expert immediately.
-
Use g0realtimemonitor to check :
-
beam parity quality
-
Detector health (CFD_TDC, MT_TDC, TOF, ...)
-
Once an hour, look at the last complete g0Integrity file.
-
After each run, update the purpose of each run within Good_for GUI.
-
Once a shift, don't forget to fill out the check list (normally this the
job of the shift worker).
-
Check once a shift and (especially after beam restoration, reboot of IOC
SE20 etc.) that the Halo target position hasn't changed
Things to Do When There is No Beam
Reminders
General
-
Moeller solenoid should be ON.
-
Hall C fast feedback energy lock is ON (requested by PD since Hall
A is down).
-
Hall C position fast feedback is OFF
-
MCC can view the Halo monitor GUI. Maintaining a low halo rate (see
below)
is part of beam tuning.
-
G0 girder correctors are physically disconnected
-
Whenever there is an IOC crash (particularly for IOCSE20), check that the
survey
offsets are properly restored by running the "check_offsets" script
on jeffylab and comparing the printed results to the numbers below the
screen. Perform this check whenever the beam position changes
significantly.
Also check the position of the halo target, because when the IOC that
controls
the halo target re-boots, it withdraws the target -- so you will need to
put it back in place.
Useful Links
-
The 6 mm hole target is in use.
-
Automated procedure for IA/PZT scan
-
See Kaz's entry #76387 (IA/PZT).
-
Shift worker should perform the 120 Hz file analysis
-
See Lars' entry #76401 (120Hz)
-
Shift worker should also make an entry of Feedback system
results
-
Shift worker (yes again) should
-
Report the results of G0Integrity check
-
See an example in entry #76794 (G0Integ-report)
Contacting the RC
Current RC: Steve Wells
-
Cell: 876-1791
-
Pager: 584-5574
-
%Office Phone: x5192
-
Hotel Phone: ???-????988-1687
-
E-mail: wells@phys.latech.edu