Difference between revisions of "20190417-Analyzer-Mtg"
From PREX Wiki
Jump to navigationJump to searchCiprian Gal (talk | contribs) |
|||
| Line 15: | Line 15: | ||
#respin of APEX runs: [https://docs.google.com/spreadsheets/d/1lPRPk-IzzBdXKH4nujMcFYRrRwcvfKOMtl-omLCYO7M/edit?usp=sharing runlist] | #respin of APEX runs: [https://docs.google.com/spreadsheets/d/1lPRPk-IzzBdXKH4nujMcFYRrRwcvfKOMtl-omLCYO7M/edit?usp=sharing runlist] | ||
#* What output do we have? | #* What output do we have? | ||
| − | #** | + | #** TY: still working on the 30 uA runs (Adam volunteered). |
| + | #** DA: will investigate the 40 uA runs starting today | ||
#* Agregator? | #* Agregator? | ||
| − | #** | + | #** PK: working on the aggregator bug. Seems to be a problem with the post-pan outputs on top of the regular aggregator SR: the aggregator works, but not through panguin. created a separate wrapper. |
| + | #** PK: we need to have BCMs, BPMs, SAMs, yields and asymmetries/differences for the aggregators. | ||
#* Pair tree plots? | #* Pair tree plots? | ||
| − | #** | + | #** TY: already integrated in the current outputs |
#* Do we have a "process a run" analysis chain ready? Do we want to set it up as a script? >> This will develop into the prompt analysis script. | #* Do we have a "process a run" analysis chain ready? Do we want to set it up as a script? >> This will develop into the prompt analysis script. | ||
| − | #** | + | #** KP: we should change the ordering/design of the prompt summary to make it more readable. |
# "Operations" branch | # "Operations" branch | ||
#* | #* | ||
# regression analysis | # regression analysis | ||
| − | #* | + | #* PK: the lin-reg-blue and the data handlers work on the develop branch and Robert will compare with post-pan regression. |
| + | #* KP: will provide a grand correlator example. | ||
# feedback | # feedback | ||
| − | #* | + | #* PK: Amali is working on position feedback |
# Beam modulation | # Beam modulation | ||
| − | #* | + | #* PK: YT and I will make some changes to the bmwClient and Victoria is working on the decoded for the beam mod data in japan |
# VQWK adcs | # VQWK adcs | ||
| − | #* | + | #* PK: all ok. |
# EPICS run-start and fast logger (and EPICS decoder to slow tree) | # EPICS run-start and fast logger (and EPICS decoder to slow tree) | ||
| − | #* | + | #* RR: the epicsFastLogger is working will be enabled with the rest of the scripts at runStart. CG: you should first check the decoding in japan. RR: will do |
# bmwClient has issues with not pausing when CODA isn't in progress, being stopped and restarted, and to have parameters changed. This affects feedback as well and can change values when a CODA run is started with the gateway open. | # bmwClient has issues with not pausing when CODA isn't in progress, being stopped and restarted, and to have parameters changed. This affects feedback as well and can change values when a CODA run is started with the gateway open. | ||
#* | #* | ||
# Bob's DAQ tasklist | # Bob's DAQ tasklist | ||
#* Timing: mostly understood, still small mysteries (LNE) | #* Timing: mostly understood, still small mysteries (LNE) | ||
| − | #** PK: | + | #** PK: will check with Caryn when it would be a good time to work on timing |
#* Synchronization-check system. w/help from Ed Jastrzembski | #* Synchronization-check system. w/help from Ed Jastrzembski | ||
#** Cameron working on. | #** Cameron working on. | ||
#* Clean up cabling, labels, fasteners - First need to examine all signals | #* Clean up cabling, labels, fasteners - First need to examine all signals | ||
| − | #** CH crate has a preliminary cleanup and Caryn is | + | #** CH crate has a preliminary cleanup and Caryn is checking signals |
#* Clean up CRL -- eliminate so-called "dirty trick" | #* Clean up CRL -- eliminate so-called "dirty trick" | ||
#** ?? | #** ?? | ||
| Line 52: | Line 55: | ||
#** AZ: having a separate issue from bmw. | #** AZ: having a separate issue from bmw. | ||
#* automatic production of run-dependent database | #* automatic production of run-dependent database | ||
| − | #** | + | #** SP: working on firewall issues. The DB is already backfilled and we have scripts ready. |
#* alarms like end-of-run voice | #* alarms like end-of-run voice | ||
#** later | #** later | ||
| Line 60: | Line 63: | ||
== Present == | == Present == | ||
| − | + | Bob M, Devi A, Kent P, Tao Y, Paul K, Sakib R, Ye T, Ciprian G, Sakib R, Cameron C,Robert R, Sanghwa P | |
===Excused=== | ===Excused=== | ||
[[Category:Meetings]] | [[Category:Meetings]] | ||
[[Category:Analyzer_Meeting]] | [[Category:Analyzer_Meeting]] | ||
Latest revision as of 10:04, 19 April 2019
Back to Main Page >> Analyzer_Meeting
previous meeting << >> following meeting
Logistic information
Meeting room at JLab: CC L210A (entrance is in the lobby across from the 2nd floor auditorium entrance)
BlueJeans calling instructions: Toll-Free Number (U.S.& Canada): 888-240-2560 International toll number: 408-740-7256 Bluejeans CODE: 419 045 306 Bluejeans link: https://bluejeans.com/419045306
Agenda
- respin of APEX runs: runlist
- What output do we have?
- TY: still working on the 30 uA runs (Adam volunteered).
- DA: will investigate the 40 uA runs starting today
- Agregator?
- PK: working on the aggregator bug. Seems to be a problem with the post-pan outputs on top of the regular aggregator SR: the aggregator works, but not through panguin. created a separate wrapper.
- PK: we need to have BCMs, BPMs, SAMs, yields and asymmetries/differences for the aggregators.
- Pair tree plots?
- TY: already integrated in the current outputs
- Do we have a "process a run" analysis chain ready? Do we want to set it up as a script? >> This will develop into the prompt analysis script.
- KP: we should change the ordering/design of the prompt summary to make it more readable.
- What output do we have?
- "Operations" branch
- regression analysis
- PK: the lin-reg-blue and the data handlers work on the develop branch and Robert will compare with post-pan regression.
- KP: will provide a grand correlator example.
- feedback
- PK: Amali is working on position feedback
- Beam modulation
- PK: YT and I will make some changes to the bmwClient and Victoria is working on the decoded for the beam mod data in japan
- VQWK adcs
- PK: all ok.
- EPICS run-start and fast logger (and EPICS decoder to slow tree)
- RR: the epicsFastLogger is working will be enabled with the rest of the scripts at runStart. CG: you should first check the decoding in japan. RR: will do
- bmwClient has issues with not pausing when CODA isn't in progress, being stopped and restarted, and to have parameters changed. This affects feedback as well and can change values when a CODA run is started with the gateway open.
- Bob's DAQ tasklist
- Timing: mostly understood, still small mysteries (LNE)
- PK: will check with Caryn when it would be a good time to work on timing
- Synchronization-check system. w/help from Ed Jastrzembski
- Cameron working on.
- Clean up cabling, labels, fasteners - First need to examine all signals
- CH crate has a preliminary cleanup and Caryn is checking signals
- Clean up CRL -- eliminate so-called "dirty trick"
- ??
- Check the 7200 scaler setup at injector, find a spare 7200.
- Talked to Bob related to timing. Event counters
- Pedestal studies, aka cross-talk
- Tao will look into it soon.
- Green Monster rework: Adam.
- AZ: having a separate issue from bmw.
- automatic production of run-dependent database
- SP: working on firewall issues. The DB is already backfilled and we have scripts ready.
- alarms like end-of-run voice
- later
- e-logbook entries
- later
- Document everything. Circuit diagrams, cable map, "how to".
- Timing: mostly understood, still small mysteries (LNE)
Present
Bob M, Devi A, Kent P, Tao Y, Paul K, Sakib R, Ye T, Ciprian G, Sakib R, Cameron C,Robert R, Sanghwa P
