20190123-Analyzer-Mtg

From PREX Wiki
Jump to: navigation, search

Back to Main Page >> Analyzer_Meeting

previous meeting << >> following meeting

Logistic information

Meeting room at JLab: CC F227

 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

github repository: JAPAN

Agenda

  1. online plots pullRequest
    • CG: pulled into develop.
    • WD: maybe we should put it into a separate repo to reap benefits from others work and contribute to Hall A. CG: we should seriously consider this and have one student to bring in the updates that Hall A previous experiments into place.
    • CC: the panguin/onl-tool that Tritium used was an offshoot of panguin and we should have their functionality. CG: maybe Tao can look into this and potentially integrate the work Tritium has for panguin
  2. regression analysis
    • PK: not quite ready because of backlog on the feedback.
  3. feedback
    • PK: compiled the sources but having trouble linking everything together in the package with cmake.
    • PK: we should bring in Amali to discuss what was done before and which variables are needed to push fwd with feedback.
    • WD: should we create an extension folder to contain panguin (unless we move it to a separate repo), feedback and so on? PK: sounds like a good plan.
  4. DAQ issues
  5. VQWK adcs
    • CC: Chris Cuevas is confident he can fix hardware issues.
  6. Other issues
    • Pull requests:
      • PK: we now we can use the podd FindRoot
      • WD: will look into further work on RPATH
      • PK: we have a new pull request for new trees. CG: will review shortly. WD: should we try to add some documentation text that can be visible from TBrowser? RR: will look at root documentation to see what the syntax for it should be.
    • CC: we should discuss the tracking and optics runs and maybe work with panguin to produce default plots. CG: this relates to panguin Tritium tools which worked with podd. We should revisit this next week at the workshop.
    • PK: we have new configuration files for the new runs and the runs from last year (because we reset the run numbers)
    • PK: we are working on connecting the ET system to create the mem-resident root file. If the analyzer is faster than the DAQ it will wait for the data as it streams, as opposed to analyzing a disk resident file where the analyzer will stop at the end of the file.
    • CG: what should we do about mock data? PK: Robert and I will take a look at it. WD: right now it’s hard coded the correlations between channels. I think we can’t just use the PREX config files.
    • PK: will setup a central japan repo and create a setup bash script for the environment.
    • KP: we should have a plan to take data semi-continuously. CG: will look to organize this.

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 Timing: mostly understood, still small mysteries (LNE)
2 Synchronization-check system. w/help from Ed Jastrzembski
3 File naming, reset run num, finalize configs (INJ, CH, ALL) 
4 Fix scalers on spectrometer crates.
5 clean up cabling, labels, fasteners.
6 Clean up CRL -- eliminate so-called "dirty trick"
7 Check the 7200 scaler setup at injector, find a spare 7200.
8 Pedestal studies, aka cross-talk.  
9 Test JAPAN. Need cable map & labels. Possibly maintain "pan" ?
10 Green Monster maintenance.
11 Test spares.  Repair bad modules.
12 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
Accomplished
 * Revive all crates.
 * Deploy all ADCs needed and test each channel.
 * Build various DAQ configs with subsets of the DAQ crates.
 * Timing diagram, check timing of external signals and readout.
 * ET system upgrade, test rate limits, ensure deadtime zero.
 * Implement Bank structure.

Present

Tao Y, Paul K, Robert R, Cameron C, Ciprian G, Sakib R, Wouter D, Jinlong Z, Devi A, Ye T, Kent P

Excused

Bob M,