Main INDEX
Monthly INDEX
PREV
NEXT
User name spwells
Log entry time 09:02:03 on April 07, 2004
Entry number 81655
keyword=Run Plan for 7 April Day through 8 April Owl
Run Plan
Aside from taking LH2
production
runs, the main task to accomplish today is Moller measurements and
removal
of the IHWP. Matt Polker informs us that the Hall C laser attenuator is
near the end of its range, and the laser spot will need to be moved. He
had tentatively planned to move it tomorrow (Thursday). Because the beam
polarization in general changes when the laser spot is moved, we will
need
to make Moller measurements both before and after the spot is moved. I
have tried to coordinate the laser spot move for this afternoon after our
normally scheduled Moller measurement but before the Hall A commissioning
time scheduled for 18:00 to 21:00 this evening. In an ideal scenario from
a scheduling point of view, we would perform the Moller measurement at
16:00, remove the IHWP, then have Matt spend his 1 hour (esitmated
time for moving laser spot an retuning injector) before the 18:00
Hall
A commissioning begins. After beam is back in the Hall at 21:00, we would
then perform our post-(spot move + IHWP state change) Moller measurement,
at which time Kaz will be close to being on shift for RIP scans if
necessary
to get feedback operational. After the 13:30 meeting this afternoon, I
will have more details on a firm schedule for these tasks.
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) = 150
-
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".
-
Take one 120 Hz run per day, on day shift. Because the DMCH interface box
will not work for 120 Hz running, a new configuration for 120 Hz which
will allow NA 120 Hz to work but not the FR 120 Hz to work (essentially
disabling ROC3) will be implemented. Please contact Paul to get this
configuration
correct.
-
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.
-
Note: If MCC needs to reboot IOCse20 (the one that contains
information
from our BPM/BCM monitors), make sure that they reinstall the halo target
ladder with the 6 mm hole in place.
Detailed Procedure
-
Take hour long LH2 runs until MCC takes beam away this morning at 10:00
for beam studies.
-
Continue with hour long LH2 runs until 16:00.
-
Setup for and perform Moller measurement at 16:00.
-
Take out IHWP.
-
Give beam to Matt Polker to move laser spot on crystal, and whatever
injector
tuning is necessary.
-
MCC will take beam at 18:00 for Hall A commissioning, during which time
we will probably not get parity quality beam in the hall.
-
After beam returns at 21:00, perform another Moller measurement.
-
Perform a RHWP scan to zero out charge asymmetry.
-
Check feedback operation.
-
If feedback does not converge, perform a RIP scan to get new feedback
parameters,
and get feedback operational.
-
Take hour long LH2 runs through Owl shift and into tomorrow's Day
shift.
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).
The "new" DMCH interface box has been installed. A new configuration for
running 120 Hz for the NA electronics needs to be implemented. Please
contact
Paul.
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 |
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. After the
retune in Hall C changing quads to change the beam shape on 4/2/04, the
halo rates have returned to the values in this table. 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, although we want the beam position to be within 0.2 mm
at each x and y position.
-
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
THE
FOLLOWING WILL CHANGE DUE TO THE NEW DMCH INTERFACE BOX. PLEASE CONTACT
PAUL KING.
-
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-5474
-
%Office Phone: x5192 (NA)
-
Hotel Phone: 873-2266, Room 305.
-
E-mail: wells@phys.latech.edu