20190603-Analyzer-Mtg

From PREX Wiki
Revision as of 10:00, 3 June 2019 by Ciprian Gal (Talk | contribs) (Created page with "Back to Main Page >> Analyzer_Meeting previous meeting << >> following meeting == Logistic informatio...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

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

Analyzer code updates

  1. Recent branch activity & pull requests
  2. burpcuts
  3. miniruns & regression analysis
  4. feedback
  5. Beam modulation
    • Updates to the bmwClient
    • Decoding and BMOD tree extraction

Hardware/DAQ tasklist

  1. EPICS run-start and fast logger (and EPICS decoder to slow tree)
  2. Timing: mostly understood, still small mysteries (LNE)
  3. Synchronization-check system. w/help from Ed Jastrzembski
  4. Clean up cabling, labels, fasteners - First need to examine all signals
  5. Clean up CRL -- eliminate so-called "dirty trick"
  6. Pedestal studies, aka cross-talk
  7. Green Monster rework: Robert
  8. automatic production of run-dependent database
  9. alarms like end-of-run voice
  10. e-logbook entries
    • later
  11. Document everything. Circuit diagrams, cable map, "how to".
    • CC: will make circuit diagrams.
  12. Remote power supply cycling capability:

ReSpin of APEX runs

runlist

  1. Aggregator Sakib:
  2. Pass 2: Paul

Special meeting about Green Monster

  • We will use GreenMonster as the primary mode of setting electronics settings.
    • Green monster should also be able to write to files to store default settings which are used at boot. {Cameron}
    • We should remove the module setting routines from the CRL (actually just disable them). {Cameron}
    • Do we want to use the TB to set the scaler gates? BM and KP say yes.
      • Let's use the TB signal as the scaler gate, with a possible fiddling around to better align the TB gate with the VQWK integration. This might be through using an extra external gate, removing the VQWK internal delay, or other solutions. PK and CC to follow up on this on Monday.
      • Timing validation btween scaler gate and VQWK would have to be done by putting the scaler gate into a VQWK channel and scanning the VQWK timing settings.
    • Bob would like to see some kind of study where we check for transients and make sure we have a long enough T_settle.
      • Maybe we need to take a special run with beam where we start with zero TB delay and a very short VQWK integral and step the delay up to some nominal value. We (CC & PK) should prepare a test plan to be able to run at some convenient PQB opportunity.
    • We should add some alarms/alerts that the settings are "unusual" when starting a run

Present

Excused