Difference between revisions of "Doing a calibration run"
From PREX Wiki
Jump to navigationJump to search| Line 29: | Line 29: | ||
**Request MCC send 140uA - wait for bpm1H04AX,Y and 4EX,Y to stabilize on the strip chart, take at least 1min of data. if beam trips, wait for beam to return and positions to stabilize, then take 1min of stable data. | **Request MCC send 140uA - wait for bpm1H04AX,Y and 4EX,Y to stabilize on the strip chart, take at least 1min of data. if beam trips, wait for beam to return and positions to stabilize, then take 1min of stable data. | ||
*End Parity Run | *End Parity Run | ||
| + | *RETURN BPM IOCS TO AUTOGAIN: gain controls screen, for iocse9 and iocse10, change 'GainsOff' to ---> 'AutoGain' | ||
*(note if beam is unstable, you can take fewer points, we need at least 2 where the beam position has 'stabilized') | *(note if beam is unstable, you can take fewer points, we need at least 2 where the beam position has 'stabilized') | ||
Revision as of 17:30, 10 December 2019
UNSER-type BCM Calibration
- Beam OFF (target can be out / HOME)
- Start Parity DAQ run - label as calibration
- (note that you can request MCC automate the currents they send you in a current ramp if you want, if the beam is stable. Otherwise make individual calls to MCC for each current)
- Request MCC send 150uA - take 30sec of data (if the beam trips, countinue taking data at 150uA until you really have 30sec of beam on data at 150)
- Request MCC BEAM OFF - take 30sec of data with no beam (this is the UNSER pedestal)
- Request MCC send 130uA - take 30sec of data
- Request MCC BEAM OFF - take 30sec of data with no beam (this is the UNSER pedestal)
- Repeat above beam on/beam off data taking for the following currents:
- Decreasing: 0uA, 150uA, 0uA, 130uA, 0uA, 110uA, 0uA, 90uA, 0uA, 70ua, 0uA, 50uA, 0uA, 30uA, 0uA
- Increasing: 0uA, 20uA, 0uA, 40uA, 0uA, 60uA, 0uA, 80uA, 0uA, 100uA, 0uA, 120uA, 0uA, 140uA, 0uA
- End Parity DAQ Run
- (Note if beam is super unstable, you can take fewer points, as long as current is set to 0uA for 30sec-1min in between currents.
BPM calibration
- type 'jmenu' in terminal
- type 'forced gain' in jmenu search bar
- Select 'SEE ioc gain controls'
- Request from MCC channel access to 'iocse9' and 'iocse10'
- Request 150uA (target can be out / HOME), wait 1min for beam positions to stabilize (on stripchart 1H04AX,4AY,4EX,4EY)
- On, gain controls screen, for iocse9 and iocse10, change 'AutoGain' to ---> 'GainsOff'. This MUST be done only when 150uA is in the Hall.
- Start a Parity DAQ Run - label as calibration
- Take 1min of data a 150uA
- Request MCC send 130uA - wait for bpm1H04AX,Y and 4EX,Y to stabilize on the strip chart, take at least 1min of data. if beam trips, wait for beam to return and positions to stabilize, then take 1min of stable data.
- Request MCC send 110uA - wait for bpm1H04AX,Y and 4EX,Y to stabilize on the strip chart, take at least 1min of data. if beam trips, wait for beam to return and positions to stabilize, then take 1min of stable data.
- Request MCC send 120uA - wait for bpm1H04AX,Y and 4EX,Y to stabilize on the strip chart, take at least 1min of data. if beam trips, wait for beam to return and positions to stabilize, then take 1min of stable data.
- Request MCC send 140uA - wait for bpm1H04AX,Y and 4EX,Y to stabilize on the strip chart, take at least 1min of data. if beam trips, wait for beam to return and positions to stabilize, then take 1min of stable data.
- End Parity Run
- RETURN BPM IOCS TO AUTOGAIN: gain controls screen, for iocse9 and iocse10, change 'GainsOff' to ---> 'AutoGain'
- (note if beam is unstable, you can take fewer points, we need at least 2 where the beam position has 'stabilized')
