Difference between revisions of "Charge Feedback Parity DAQ"
From HallCWiki
Jump to navigationJump to search| (5 intermediate revisions by one other user not shown) | |||
| Line 23: | Line 23: | ||
=== Procedure to run the flipper script (from the Hall A VNC session) === | === Procedure to run the flipper script (from the Hall A VNC session) === | ||
| − | *This script | + | *This script needs to be run when the IHWP state changes and Hall A is not controlling our feedback. |
*Call Hall B at least 30 minutes before flipping to give them a heads up. | *Call Hall B at least 30 minutes before flipping to give them a heads up. | ||
*When ready to flip: | *When ready to flip: | ||
| − | **'''stop the run''' | + | **'''stop the CODA run''' for the parity DAQ (VNC open on HCDesk2 workspace 2). |
**Then call Hall B again to let them know the flip is about to start. | **Then call Hall B again to let them know the flip is about to start. | ||
**Then call MCC and ask them to flip the IHWP. | **Then call MCC and ask them to flip the IHWP. | ||
| − | * | + | *Confirm the IHWP has been flipped. |
| − | * <code> Open (or locate) a terminal in the VNC session. It should be running as apar@adaq2</code>. | + | * <code> Open (or locate) a terminal in the VNC session from above (VNC open on HCDesk2 workspace 2). It should be running as apar@adaq2</code>. |
* <code> cd ~/feedback2019</code> | * <code> cd ~/feedback2019</code> | ||
* <code> ./FlipPCvaluesHallC</code> You should see the hallc_IACell_setting variable change on the wall | * <code> ./FlipPCvaluesHallC</code> You should see the hallc_IACell_setting variable change on the wall | ||
| Line 36: | Line 36: | ||
*'''start a run''' (parity daq) | *'''start a run''' (parity daq) | ||
* Make an HCLOG entry | * Make an HCLOG entry | ||
| + | |||
| + | |||
| + | * Log entry with some extra information on restarting the processes if the IA Cell stops updating: https://logbooks.jlab.org/entry/3852609 | ||
== Contacts == | == Contacts == | ||
Latest revision as of 05:00, 21 September 2020
The Charge Asymmetry Feedback system is controlled by the Hall A Parity DAQ.
When Hall A is in production mode, the Hall A shift crew will manage the Parity DAQ and control feedback for both Hall A and Hall C beams.
If the Hall A Counting House is not staffed, then Hall C must negotiate with the Parity group to ensure that the Parity DAQ is still running.
- This must be running for all 3He production data! (And should be running in general.)
- The state of this system is monitored in the Hall C alarm handler, and can be overseen by the Hall C Shift crew using the stripchart on the left large wall display (see below).
Instructions
- Parity DAQ Running - with Hall C Feedback passively running (Aug 02, 2020 HClog entry)
- Bring up this vnc session using
go_parity_feedbackunder the cdaq account.
- Hall C running parity DAQ for charge feedback (Feb 12, 2020 HCLog entry) -- OLD, just for reference.
Useful Commands (on cdaq machines)
go_parityInjector parity settings (IHWP status, Hall Laser IA settings, etc)go_parity_feedbackBring up the Parity DAQ charge feedback VNC session (if Hall C is running alone; see below)go_Qasym_stripchartBring up the Hall C Charge Asym monitoring stripcharts (these should always be up on the big wall screens)
Procedure to run the flipper script (from the Hall A VNC session)
- This script needs to be run when the IHWP state changes and Hall A is not controlling our feedback.
- Call Hall B at least 30 minutes before flipping to give them a heads up.
- When ready to flip:
- stop the CODA run for the parity DAQ (VNC open on HCDesk2 workspace 2).
- Then call Hall B again to let them know the flip is about to start.
- Then call MCC and ask them to flip the IHWP.
- Confirm the IHWP has been flipped.
Open (or locate) a terminal in the VNC session from above (VNC open on HCDesk2 workspace 2). It should be running as apar@adaq2.cd ~/feedback2019./FlipPCvaluesHallCYou should see the hallc_IACell_setting variable change on the wall./checkPCvaules- start a run (parity daq)
- Make an HCLOG entry
- Log entry with some extra information on restarting the processes if the IA Cell stops updating: https://logbooks.jlab.org/entry/3852609
Contacts
- Bill Henry (Hall C)
- Cameron Clarke (Hall A)
- Caryn Palatchi (Hall A)
