Log entry time 09:07:30 on April 18, 2004

Entry number 82448

Run Plan (Apr 18 to Apr 19)

Perform Angela's deadtime study during a day shift. Details can be found below.
Continue to take production data on LH2 until shutdown for CD-0 tour.
Take a 120Hz run during day shift.
No beam for 1+ hour? Take a green block DNL measurement. Maybe it is also possible to take a 2 hr green block run on Monday during the shutdown for the CD-0 tour.

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.
• 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 OUT.
• 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.
• If the IOC SE20 flatlines/crashes and gets rebooted make sure you restart Paul King's alarm program. See log-entry number 82375 for instructions.

Detailed Procedure

1. Sunday day shift: Angela Biselli (who will be shift leader over the weekend) will take 3 one-hour runs at three different currents Fastbus/TED interleaved.
2. Take production data on LH2 over the weekend. Note that the accelerator Fast Position Feedback is ON. Keep an eye on our Feedback and notify Kaz or the RC if there seems to be a problem.
3. If at any point we get "marginal" beam try to take data for Julie's PMT gain calibration: Take 6 one hr runs at 1 uA on lH2 target. If beam becomes usable during these 6 hours interrupt and take production data on lH2 at 40 uA. See instructions or call Julie for help. Note that the 6 runs do not have to be consecutive, so if beam becomes usable again during this period return to production running on LH2.
4. Shutdown for CD-0 tour Monday at 7am. Here is the current schedule:
   • 07:00 Beam OFF
   • 08:00 Sweep of the Hall
   • 10:00 - 11:00 Tour of the accelerator and the Hall
   • 11:00 Lock up and sweep of Hall(s) and machine
   • 12:00 Beam restoration
   • 13:00 Restore Physics program
5. Resume production data taking on LH2.

New Considerations

• IOC SE20 still seems to crash on a regular basis, even after the board was replaced . Keep an eye on the monitors and an ear on the new alarm (the sound byte is the Star Trek alarm)and stop the run if you notice that the EPICS graphs are flatlined. DO NOT FORGET TO RESTART IT AFTERWARDS. The PD will also ask the software people to put an alarm at the MCC as well. MCC will then hopefully) contact us as well when the IOC crashes. We will see how well this will works. Also make sure you write a note in the end-of-run comment and in the run summary that the IOC was rebooted at the end of the run. Data from a run can probably be salvaged if we notice a crash fast.
• Fast Position Feeback is ON. Note any changes in our feedback.
• 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:
1. Press 'Reset All' on G0 realtime monitor. If this does not clear the error then proceed to the next step.
2. Ask MCC to take the beam away for 10 seconds.
3. Press 'Reset All' on G0 realtime monitor.
4. Error should clear and Musson box should resync.
5. Repeat procedure if necessary to clear error. If unable to clear error, then contact the DAQ expert (P. King).
• The "newer" DMCH interface box has been installed. This box runs in 120Hz mode.

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 href="http://g0web.jlab.org/g0log/0312_archive/031207014128.html">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) = 150

• 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( href="http://g0web.jlab.org/g0log/0312_archive/031206211351.html">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

1. Turn on the GMS mask. The control box is located towards the bottom of the second rack in the 2nd floor G0 electronics cage.
1. Turn the switch labelled "Motor" on.
2. Check to make sure the LEDs on the box are flashing.
3. If lights are not flashing, then crank the 20 turn pot up until they are flashing.
4. Use the pot to set a current between 180 and 200.

2. In the G0 DAQ configuration tool set the following prescale values:
• PS5 (laser events) = 0
• PS6 (source events) = 150

3. Start runs normally; label them as GMS on.
4. 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.
5. 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)

1. Check with General Tool that the fast position feedback is OFF.
2. 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

3. 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

1. Start a run and fill out the comments cases in the "pink window" with: "coil pulsing run"
2. Ask MCC to retract the Halo target (home position or 0 mm). In the mean time Start a run.
3. Run the shell script ./gridmodulation (for grid pattern coil modulation).
4. To see it working look on the G0realtimemonitor beamline screen.
5. Once the run ends, call MCC to return the halo target to the 6 mm hole position.

Energy Modulation

1. Start a run and fill out the comments cases in the "pink window" with: "energy pulsing run"
2. Run the shellscrpt: ./energymodulation
3. 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.
4. To see it working (in theory) watch BPM 3C12_X,Y.

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

1. Use Jason's script to extract the 60 Hz noise, and multiples thereof. To do this, type '~/G0Analysis/G0Scripts/extract60Hz #####'.
2. MAKE A LOGENTRY containing the run number and the relevant text output from extract60Hz.
3. Inform the shift leader, especially if the values are out of spec.

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

• Take NA DNL runs with the white noise box (see procedure in the Beam How-to).
• Take FR DNL ("green block") runs. Use this procedure:
• Load the HV full gain file: HV.fullgain_2nd_engineering_calibrated.hvc from cvxwrks@cdaqs2:$EPG0HV/tk
• Select French configuration as FoB (using g0daq_config GUI) and set the threshold to 20 mV for French. 30 Hz, ps4 maximum, fastclear disabled.
• Take a long ~2hr DAQ run.
• Restore standard configuration (HV file and DAQ) when you are done

• Take hour long runs in the nominal DAQ mode to measure pedestal differences. The following IOCs must be in forced gain mode at the listed settings (see BPM/BCM Calibration section of Beam How-to):



IOC	X Gain	Y Gain
iocse14	1900	1900
iocse17	1850	1800
iocse18	1800	1800
iocse20	1900	1900

Make sure the IOCs get set back to auto gain when beam is restored to the hall.

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 href="http://hallcweb.jlab.org/g0log/0402_archive/040223172153.html">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.
• See references for href="http://g0web.jlab.org/g0log/0402_archive/040225000150.html">positions (#77721)and href="http://g0web.jlab.org/g0log/0402_archive/040213164014.html">rates (#76406).

• Automated procedure for IA/PZT scan
• See Kaz's entry #76387 ( href="http://g0web.jlab.org/g0log/0402_archive/040213113923.html">IA/PZT ).

• Shift worker should perform the 120 Hz file analysis
• See Lars' entry #76401 ( href="http://g0web.jlab.org/g0log/0402_archive/040213140336.html">120Hz )

• Shift worker should also make an entry of Feedback system results
• Use Kaz's script (posted on computer)
• See typical entry #76684 ( href="http://g0web.jlab.org/g0log/0402_archive/040215232923.html">Feedback-analysis )

• Shift worker (yes again) should
• Report the results of G0Integrity check
• See an example in entry #76794 ( href="http://g0web.jlab.org/g0log/0402_archive/040217040355.html">G0Integ-report )

Contacting the RC

1. Cell: 876-1791
2. Pager: 584-5474
3. %Office Phone: x5192 (N/A)
4. Hotel Phone: 5871, ResFac Room 11-D.
5. E-mail: kuhnj@jlab.org

A copy of this log entry has been emailed to: biselli@jlab.org, sew@uiuc.edu, breuer@enp.umd.edu, guillon@lpsc.in2p3.fr