Difference between revisions of "AIEC Weekly Meeting June 8, 2023"

From epsciwiki
Jump to navigation Jump to search
(Created page with "=== Agenda: === # Previous Meeting #: # Announcements: #: # Activities: #: #* <b> roboCDC: </b> #** Hall-D is down for ~1yr. #** Model tr...")
 
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
 +
The current weekly meeting time is Thursdays at 3:00pm
 +
 +
=== Connection Info: ===
 +
<div class="toccolours mw-collapsible mw-collapsed">
 +
You can connect using [https://jlab-org.zoomgov.com/j/1601987443?pwd=bUVPV3puTHJPU0Fub2Q2Z1dsV0JjQT09&from=addon ZOOM Video conferencing (ID: 1601987443)]. <font size="-3">(Click "Expand" to the right for details -->):</font>
 +
 +
<div class="mw-collapsible-content">
 +
 +
One tap mobile: US: +16692545252,,1601987443# or +16468287666,,1601987443#
 +
 +
Meeting URL: https://jlab-org.zoomgov.com/j/1601987443?pwd=bUVPV3puTHJPU0Fub2Q2Z1dsV0JjQT09&from=addon<br>
 +
Meeting ID: 160 198 7443<br>
 +
Passcode: 607906<br>
 +
 +
Join by Telephone<br>
 +
For higher quality, dial a number based on your current location.<br>
 +
Dial: <br>
 +
US: +1 669 254 5252 or +1 646 828 7666 or +1 669 216 1590 or +1 551 285 1373 or 833 568 8864 (Toll Free)<br>
 +
Meeting ID: 160 198 7443<br>
 +
International numbers<br>
 +
Join from an H.323/SIP room system<br>
 +
H.323: 161.199.138.10 (US West)<br>
 +
161.199.136.10 (US East)<br>
 +
Meeting ID: 160 198 7443<br>
 +
Passcode: 607906<br>
 +
 +
SIP: 1601987443@sip.zoomgov.com<br>
 +
Passcode: 607906<br>
 +
 +
</div>
 +
</div>
 
=== Agenda: ===
 
=== Agenda: ===
−
# [[AIEC Weekly Meeting Jun. 1, 2023| Previous Meeting]]
+
# [[AIEC Weekly Meeting June 1, 2023| Previous Meeting]]
 
#:
 
#:
 
# Announcements:
 
# Announcements:
Line 7: Line 38:
 
#:
 
#:
 
#* <b> roboCDC: </b>
 
#* <b> roboCDC: </b>
−
#** Hall-D is down for ~1yr.
+
#*# Performance of runs with RoboCDC turned on
−
#** Model training script runs :)
+
#*# Status of CDC gain calibrations
−
#** Test procedure for Hot Checkout just before next run?
+
#*# Time-to-drift calibrations
 +
#*# What statements can be made for final report on calibration time?
 +
#*# Test procedure for Hot Checkout just before next run?
 
#:
 
#:
 
#* <b> FCAL: </b>
 
#* <b> FCAL: </b>
−
#** FCAL correlation work: [https://halldweb.jlab.org/DocDB/0060/006089/001/fcal_correlations-2.html Torri's notebook]
+
#*# Correlations with Vmon, Temperature, etc ...
 +
#*# [[AIEC FCAL Simulation Q-Learning]]  
 
#*:
 
#*:
 +
#* <b> FDC: </b>
 +
#*# State of gain calibrations where we left off
 +
#*# Plots indicating improved PID with FDC
 +
#:
 
# Talks/Presentations
 
# Talks/Presentations
−
#* [https://indico.jlab.org/event/459/contributions/11374/ CHEP talk] ''Thomas''
+
#* [https://indico.jlab.org/event/459/contributions/11374/ CHEP talk] Proceedings
 
#:
 
#:
  
  
−
<hr>
 
−
This plot shows one block (row=30, column=27) for two runs (110805 and 111500). All plots show the pedestal subtracted FADC pulse_peak values with no calibration constants applied.
 
−
 
−
* The two plots on the left are from the ``FCAL-LED`` skim
 
−
* The two plots on the right are from the ``compton-neutral`` skim (see description below)
 
−
* The two plots on the top are the original, raw data with no scaling factor applied
 
−
* The two plots on the bottom have a relative scaling factor of 1.2 applied to the run 111500 values
 
−
 
−
The scaling factor of 1.2 is done by eye to make the LED plots in the lower left roughly lined up. The plots on the right use light generated in the FCAL block. The fact that the spectra in the top right look well aligned by eye, but are not well-aligned in the lower right plot suggest that the scaling factor of 1.2 is due to the LED light source rather than the PMT response.
 
  
−
The two plots on the right were made by looking at reconstructed FCAL clusters where bock 30,27 was the center. The goal here was to have a distribution with some structure that allowed one to test if there was any relative scaling of the x-axis.
 
−
 
−
 
−
[[File:2023.05.31.project_block.png|400px]]
 
 
<hr>
 
<hr>
 
=== Minutes ===
 
=== Minutes ===
−
* We shared with Igal what we have learned regarding the lack of correlation between LED peak position and existing calibration constants (gains) from the CCDB.
+
''TBD''
−
** David's anecdotal plot (see above) was discussed.
 
−
* We discussed what previous evidence Igal had seen for a correlation. He noted that the results were inconsistent across blocks.
 
−
** We reviewed some of Igal's plots from the [[AIEC Weekly Meeting Feb. 22, 2023|Feb. 22, 2023 AIEC meeting]].
 
−
*** We noted that the strongest evidence appeared to be from the [https://wiki.jlab.org/epsciwiki/images/a/a4/Plot_primex-phase1_led_1344.pdf block 1344 in ring 1 plot]. However, we concluded that this was most likely due to radiation damage.
 
−
*** We looked for evidence in the [https://wiki.jlab.org/epsciwiki/images/5/59/Plot_primex-phase1_led_707.pdf block 707 in ring 9 plot], but were not convinced that a correlation was clearly evident.
 
−
*:
 
−
* We reviewed some of Torri's plots where the ratio of individual blocks to the sum of all blocks was plotted against the pi0 derived calibration constants.
 
−
** Igal noted that the quadrants have different pulsers so we should use the overlap of a ring with the quadrant for the average rather than the whole FCAL.
 
−
** We may also want to plot individual colors so the x-axis stretches out more to show potential correlations.
 
−
*:
 
−
* Igal suggested one cause of the LED amplitude shifts could be due to temperature changes related to frequent accesses to the FCAL dark box during the first PrimEx run (run numbers 60XXX). He said they did not observe so many fluctuations in the section PrimEx run which had fewer dark box accesses.
 
−
* Igal suggested looking at the CompCal might be easier since it had a more carefully designed LED system that was much more stable.
 
−
** n.b. the CompCal has since been disassembled and will never be in use again.
 
−
*:
 
−
* David suggested spending 1 more week to seek out a LED-gain correlation in the FCAL and then pivoting to the CompCal.
 
−
 
 
 
==== Action Items ====
 
==== Action Items ====
−
# Investigate temperature for a possible correlation with the LED peak position drifts
+
''TBD''
−
# Reproduce ratio plots vs. CCDB values:
 
−
#* use only reliable blocks from same quadrant for sum
 
−
#* Plot only small and large blue so x-axis covers smaller range
 
−
# Decide how to proceed for remainder of project (FCAL, CompCal, other?)
 

Latest revision as of 18:40, 8 June 2023

The current weekly meeting time is Thursdays at 3:00pm

Connection Info:

You can connect using ZOOM Video conferencing (ID: 1601987443). (Click "Expand" to the right for details -->):

One tap mobile: US: +16692545252,,1601987443# or +16468287666,,1601987443#

Meeting URL: https://jlab-org.zoomgov.com/j/1601987443?pwd=bUVPV3puTHJPU0Fub2Q2Z1dsV0JjQT09&from=addon
Meeting ID: 160 198 7443
Passcode: 607906

Join by Telephone
For higher quality, dial a number based on your current location.
Dial:
US: +1 669 254 5252 or +1 646 828 7666 or +1 669 216 1590 or +1 551 285 1373 or 833 568 8864 (Toll Free)
Meeting ID: 160 198 7443
International numbers
Join from an H.323/SIP room system
H.323: 161.199.138.10 (US West)
161.199.136.10 (US East)
Meeting ID: 160 198 7443
Passcode: 607906

SIP: 1601987443@sip.zoomgov.com
Passcode: 607906

Agenda:

  1. Previous Meeting
  2. Announcements:
  3. Activities:
    • roboCDC:
      1. Performance of runs with RoboCDC turned on
      2. Status of CDC gain calibrations
      3. Time-to-drift calibrations
      4. What statements can be made for final report on calibration time?
      5. Test procedure for Hot Checkout just before next run?
    • FCAL:
      1. Correlations with Vmon, Temperature, etc ...
      2. AIEC FCAL Simulation Q-Learning
    • FDC:
      1. State of gain calibrations where we left off
      2. Plots indicating improved PID with FDC
  4. Talks/Presentations


Minutes

TBD

Action Items

TBD

Retrieved from "https://wiki.jlab.org/epsciwiki/index.php?title=AIEC_Weekly_Meeting_June_8,_2023&oldid=3500"