20190403-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
     • New param files from operations are merged into develop, and stability/beam-trip cuts are working "better". See HAPLog/3708 for beam trip performance.
       • Did we get all the param file changes into operations that we had planned?
     • Possible other merges:
       1. Pair analysis: tree production is working, do not yet have pair-based running sums
       • • PK will add the pair-based running sum later today, then merge to develop. Pair analysis is enabled by being hardcoded.
       1. Prompt summary: Basic functionality is there, but formatting needed work.
       • • Sakib has added some formatting; he will change the number formatting to sci.notation
       1. Aggregator: Is this ready to be used on the respun runs?
       • • Yes, it should be merged and used. See notes below on how to call it. No, that's for the fancy panguin version. We will not call it directly as part of the respin, instead CC will be following the respin and doing the aggregation.

' cd rootScripts/aggregator ' source setup_camguin.tcsh ' ./panguin_wrapper.sh -r <run_number> -f analyze.cfg -n 1

1. • • 1. Post-pan regression: Is this ready to be used on the respun runs?
       • • This is a private repository; this is also compiled against ROOT5. Tao will be running this independently.
         • Let's try 5000 patterns for the starting size of the postpan miniruns
     • Do we have a "process a run" analysis chain ready? Do we want to set it up as a script?
       1. Respin the run, using new rootfile name
       2. Tao runs postpan
       3. CC runs aggregator on the japan rootfiles
       4. CC runs the aggregator on the postpan rootfiles
     • We will activate normalization on the SAMs.
2. "Operations" branch
   • I will be merging all the above the develop, then to master, then to operations
3. regression analysis
   • Robert has almost finished with a hardcoded
4. feedback
   • Amali is having some trouble with feedback and will contact PK soon
5. Beam modulation
   • Has there been any development on the BMOD tree?
6. VQWK adcs
   • The last one is being repaired now.
   • An extra one (each) will be installed in CHA and INJ crates
7. DAQ issues
   • EPICS run-start and fast logger (and EPICS decoder to slow tree)
     • Robert and CC will work on calling these from CODA. There ought to be an example EPICS decoder map file in "Analysis/prminputs", to show how to define the EPICS variables which will make it to the slow tree. If it is missing, PK can add one from the original QwAnalysis
   • bmwClient has issues with not pausing when CODA isn't in progress, being stopped and restarted, and to have parameters changed
     • PK was going to send an email with ideas, but hasn't

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

Present

P.King, Ciprian, Cameron, Tao, Ye, Devi, R.Radloff, Sakib