Difference between revisions of "20190624-Analyzer-Mtg"

From PREX Wiki
Jump to navigationJump to search
(Created page with "Back to Main Page >> Analyzer_Meeting previous meeting << >> following meeting == Logistic informatio...")
 
 
(3 intermediate revisions by the same user not shown)
Line 15: Line 15:
 
=== Analyzer code updates ===
 
=== Analyzer code updates ===
 
# Recent branch activity & pull requests
 
# Recent branch activity & pull requests
 +
#*  Burst analysis development:  several pulls should be ready to merge, but my comparison to previous versions is not yet working because the print-runningsum doesn't work due to the runningsum changes.  Rakitha will look at it.
 +
#*  Burp cut:  Robert has pushed a set of changes that seems to work, and a quick comparison with previous results shows agreement.  May need a little further refinement.
 
# Activating the blinder
 
# Activating the blinder
−
#*  Tao was checking the EPICS variables the blinder needs to determine the sign
+
#*  All detector channels are currently marked as "not blindable".  When we reconnect the quartz into the parity DAQ, we will need to change the status of those channels to be blindable.
−
# burpcuts
+
#*  Offline/prompt analysis seems to be properly determining the blinder status from EPICS events
−
#*  Robert & Rakitha had been working on this
+
#*  Online analyzer doesn't get the EPICS data properly.  May either use EPICS calls directly, or an independent run-dependent blinder for the online displays
 
# miniruns & regression analysis
 
# miniruns & regression analysis
−
#*  A simple "uber regression" has been added.  Seems so far to have minimal impact on performance.
+
#*  The burst developments are a
−
#*  Minirun status---
 
 
# feedback
 
# feedback
−
#*  The engine now has the capability to catch run transitions, and can recieve a signal to restart the event loop.  Two changes need to be pulled from develop to feedback to enable that.
+
#*  Amali had been starting to look at adding the new variables; Rakitha can help
−
#*  Many new EPICS variables are intended to be written on the update cycle of the charge feedback to give diagnostic info to OPS
 
−
#**  C.G:  How many EPICS variables can we actually support writing to?  P.K.:  We'll have to test it and see how much of an impact it will have.  First step would be to add the capability to write to at least some of them, and then see how impacted the alayzer becomes
 
 
#  Beam modulation
 
#  Beam modulation
 
#*  Updates to the bmwClient
 
#*  Updates to the bmwClient
−
#**  Total rework to do the looping and EPICS calls from a Linux process and send data to VxWorks using cfSock:  Victoria & Rakitha
+
#**  Client is basically working now, may need some tuning
−
#**  Interaction with CODA will remain the same. '''There are changes to the VxWorks library needed to support this new system'''
 
−
#**  Hall C and Compton each have one cable ready to send the "FFB pause" or "modulation active" signals.  Hall B will just watch the EPICS variables
 
 
#*  Decoding and BMOD tree extraction
 
#*  Decoding and BMOD tree extraction
−
#**  New decoder has been comitted; needs to have cuts defined.
+
#**  New decoder is in operations.  May need to recheck channel map
−
#**  Post-production extractor is in progress
+
#**  Post-production extractor is done
−
#**  Still intend to do the extraction from JAPAN as part of first pass. ''Likely not ready at start of run''
+
#**  Still intend to do the extraction from JAPAN as part of first pass.
−
#**  P.K.:  which events should fail the BMOD cuts?  K.P.:  only the active modulation events; make sure there is a flag for the FFBpaused events though
 
  
 
=== Hardware/DAQ tasklist ===
 
=== Hardware/DAQ tasklist ===
Line 61: Line 57:
 
#* CC: will make circuit diagrams.  
 
#* CC: will make circuit diagrams.  
 
# Remote power supply cycling capability:
 
# Remote power supply cycling capability:
−
#* CC: trying to figure out how to use them (talked with Jack).
+
#* Most things we need on them are now on them.  The spectromater parity crates are not, due to power rating of the remote strips.
  
−
=== ReSpin of APEX runs ===
+
=== Prompt analysis toolchain ===
−
[https://docs.google.com/spreadsheets/d/1lPRPk-IzzBdXKH4nujMcFYRrRwcvfKOMtl-omLCYO7M/edit?usp=sharing runlist]
+
#*  The engine is run twice, and then several scritps are run to produce plots
−
# Aggregator Sakib:
+
#* Plots got to a web directory
−
#*  
+
#* What tools are we missing for the WAC?
−
# Pass 2: Tao
 
−
#*
 
  
 
== Present ==
 
== Present ==

Latest revision as of 11:51, 24 June 2019

Back to Main Page >> Analyzer_Meeting

previous meeting << >> following meeting

Logistic information

Meeting room at JLab: CH Conference room (on the accelerator side). 

 BlueJeans calling instructions:
 Toll-Free Number (U.S.&  Canada):  888-240-2560
 International toll number:         408-740-7256
 Bluejeans CODE:                  385 600 867
 Bluejeans link: https://bluejeans.com/385600867

Agenda

Analyzer code updates

  1. Recent branch activity & pull requests
    • Burst analysis development: several pulls should be ready to merge, but my comparison to previous versions is not yet working because the print-runningsum doesn't work due to the runningsum changes. Rakitha will look at it.
    • Burp cut: Robert has pushed a set of changes that seems to work, and a quick comparison with previous results shows agreement. May need a little further refinement.
  2. Activating the blinder
    • All detector channels are currently marked as "not blindable". When we reconnect the quartz into the parity DAQ, we will need to change the status of those channels to be blindable.
    • Offline/prompt analysis seems to be properly determining the blinder status from EPICS events
    • Online analyzer doesn't get the EPICS data properly. May either use EPICS calls directly, or an independent run-dependent blinder for the online displays
  3. miniruns & regression analysis
    • The burst developments are a
  4. feedback
    • Amali had been starting to look at adding the new variables; Rakitha can help
  5. Beam modulation
    • Updates to the bmwClient
      • Client is basically working now, may need some tuning
    • Decoding and BMOD tree extraction
      • New decoder is in operations. May need to recheck channel map
      • Post-production extractor is done
      • Still intend to do the extraction from JAPAN as part of first pass.

Hardware/DAQ tasklist

  1. EPICS run-start and fast logger (and EPICS decoder to slow tree)
  2. automatic production of run-dependent database
  3. e-logbook entries
    • All three are now active
  4. Green Monster rework: Robert
    • An "official" copy is installed under ~apar/devices/PyGreenMonster. Later we should import it into the DAQ repo.
  5. Timing: mostly understood, still small mysteries (LNE)
    • I think some CRLs still have module initialization at Prestart, so we need to pull that out.
  6. Synchronization-check system. w/help from Ed Jastrzembski
    • Scaler-based sync for injector is better, but still not 100%; see [1] and attachment
    • New digital system will be available some time after the run starts
  7. Pedestal studies, aka cross-talk
  8. alarms like end-of-run voice
    • Data quality alarm concept: a realtime engine will report problems via text output on a periodic basis (~few seconds), the alarm display will poll this and warn the shift crew.
    • "End-of-run" voice would be tied to coda transitions
  9. Clean up cabling, labels, fasteners - First need to examine all signals
    • CC: working on it.
  10. Document everything. Circuit diagrams, cable map, "how to".
    • CC: will make circuit diagrams.
  11. Remote power supply cycling capability:
    • Most things we need on them are now on them. The spectromater parity crates are not, due to power rating of the remote strips.

Prompt analysis toolchain

    • The engine is run twice, and then several scritps are run to produce plots
    • Plots got to a web directory
    • What tools are we missing for the WAC?

Present

Phone:

Excused

Retrieved from "https://prex.jlab.org/wiki/index.php?title=20190624-Analyzer-Mtg&oldid=6518"