20190320-Analyzer-Mtg

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

1. runlist
   • What do we need to do before we're ready to respin all of the concurrent running
     • Look at the event cuts---Tao
     • SAM pedestals---Tao and Devi (Tao has found different beam-dependent pedestals, should we use those or just the beam-off peds?)
     • Do we need to mess with beamline pedestals? Not for this pass.
     • We'd like to have a run-summary tree---Cameron
     • We want to have the post-pan regression feeding in into the run-summary tree (or friend-able)---Cameron
2. "Operations" branch
   • Get local panguin changes pushed up to git hub
   • When doing merge of operations into develop, keep the develop panguin sources if there are conflicts
3. Pull requests
   • We'll merge from operations ot develop soon
   • Also soon merge from develop back to master; but first need the online mode updated to be merged into develop
4. online plots
5. pair analysis
6. regression analysis
7. feedback
   • Amali has a version that does accumulate the asymmetry and can prepare changes for the 8 pockels cell settings
8. Aggregation
   • Cameron is working on a script to develop a "run-average" rootfile from the mul tree
   • He will later work on pulling the
9. VQWK adcs
10. DAQ issues
    • bmwClient has issues with not pausing when CODA isn't in progress, being stopped and restarted, and to have parameters changed
    • greenmonster: there needs to be ways to set all the VQWKs/timing boards/etc consistently.
11. Other issues
    • Can we set a short integration window (50-100 us) and then scan the VQWK gate delay to find the tune-mode beam, or would we need to use the timing board for this purpose?

Bob's DAQ tasklist

 TO-DO list for Parity DAQ
   updated Jan 4, 2019

Cameron & Bob: 1, 2, 4, 5, 6, 11, 12, 13
Tao & Cameron: 8, 9
Bob: 3, 6, 10
Cip, Cameron, Tao: 13  
1 Doing - Timing: mostly understood, still small mysteries (LNE)
2 Doing - Synchronization-check system. w/help from Ed Jastrzembski
5 To Do - Clean up cabling, labels, fasteners - First need to examine all signals
6 Clean up CRL -- eliminate so-called "dirty trick"
7 Check the 7200 scaler setup at injector, find a spare 7200.
8 Doing - Pedestal studies, aka cross-talk.  
10 Green Monster maintenance.
11 Doing - Test spares.  Repair bad modules.
12 Doing - Document everything.  Circuit diagrams, cable map, "how to".
13 Online software, a bit undefined since software is changing.
    (a) automatic production of run-dependent database
    (b) alarms like end-of-run voice (Bob)
    (c) feedback
    (d) coil-pulsing aka modulation aka dithering (Victoria)
    (e) panguin (GUI showing real-time plots)
    (f) prompt analysis
    (g) e-logbook entries 
    (h) archiving EPICs data