Difference between revisions of "AIOP Nov. 18, 2024"
(Created page with "The current weekly meeting time is every other Monday at 13:00 US/Eastern === Connection Info: === <div class="toccolours mw-collapsible mw-collapsed"> You can connect using...") |
|||
Line 72: | Line 72: | ||
<!--Attendees: Naomi J., Patrick M., David L., Jiawei G., Torri J., Armen K.--> | <!--Attendees: Naomi J., Patrick M., David L., Jiawei G., Torri J., Armen K.--> | ||
+ | <!DOCTYPE html> | ||
+ | <html lang="en"> | ||
+ | <head> | ||
+ | <meta charset="UTF-8"> | ||
+ | <meta name="viewport" content="width=device-width, initial-scale=1.0"> | ||
+ | <title>AIOP Meeting Notes - 11/18/24</title> | ||
+ | </head> | ||
+ | <body> | ||
+ | <h1>AIOP Meeting Notes - 11/18/24</h1> | ||
+ | <p><strong>Attendees:</strong> David, Thomas, Torri, Naomi, Armen, Jiawei, Patrick</p> | ||
+ | <p><strong>Note:</strong> With the holidays approaching, some work may need to be conducted through alternative means.</p> | ||
+ | <h2>Progress Updates</h2> | ||
+ | |||
+ | <h3>Thomas</h3> | ||
+ | <ul> | ||
+ | <li>Will run queries to retrieve data on nudges again.</li> | ||
+ | <li>Plans to search for relevant anecdotes in the logbook.</li> | ||
+ | </ul> | ||
+ | |||
+ | <h3>Patrick</h3> | ||
+ | <ul> | ||
+ | <li>Shared slides on his investigation into backlash: | ||
+ | <ul> | ||
+ | <li>Used <strong>S2020</strong> and removed outliers.</li> | ||
+ | <li>Ensured the beam was operational.</li> | ||
+ | <li>Observed fixed roll and three groupings of yaw: | ||
+ | <ul> | ||
+ | <li><strong>Coherent edge spread</strong> (a few hundred MeV).</li> | ||
+ | <li>Question: Where is this spread originating?</li> | ||
+ | </ul> | ||
+ | </li> | ||
+ | <li>Hypothesized that variation could be <strong>fit-driven</strong>: | ||
+ | <ul> | ||
+ | <li>Scalar values archived: | ||
+ | <ul> | ||
+ | <li>Requires refitting (current fits show errors).</li> | ||
+ | <li>Utilized <strong>Minuit fit</strong>.</li> | ||
+ | <li>Possible hue mismatch with run number (or another factor).</li> | ||
+ | <li>Need to calculate the error on the coherent edge.</li> | ||
+ | </ul> | ||
+ | </li> | ||
+ | <li>Highlighted the <strong>difference between set point and position</strong>.</li> | ||
+ | </ul> | ||
+ | </li> | ||
+ | </ul> | ||
+ | </li> | ||
+ | </ul> | ||
+ | |||
+ | <h3>Naomi</h3> | ||
+ | <ul> | ||
+ | <li>Researched coherent peak movement instances: | ||
+ | <ul> | ||
+ | <li>Recalled the <strong>March 30, 2018 event</strong>, where the coherent edge appeared problematic: | ||
+ | <ul> | ||
+ | <li>A new diamond spot was located with a very narrow width.</li> | ||
+ | <li>After the accelerator resumed operation, the width increased significantly.</li> | ||
+ | <li>Hovannes relocated the beam to a new position for stability.</li> | ||
+ | </ul> | ||
+ | </li> | ||
+ | <li>Plans to examine CPP logs for periods with significant beam movement.</li> | ||
+ | </ul> | ||
+ | </li> | ||
+ | </ul> | ||
+ | |||
+ | <h3>Jiawei</h3> | ||
+ | <ul> | ||
+ | <li>Presented <strong>before-and-after plots</strong> of coherent peak changes using archived data: | ||
+ | <ul> | ||
+ | <li>Data source: <strong>HD:CBREM:ENH_REF</strong>.</li> | ||
+ | <li>While the reference plot appears static, it successfully illustrates the difference in coherence.</li> | ||
+ | <li>Mentioned that a <strong>“live plot” is harder</strong> to implement but feasible.</li> | ||
+ | </ul> | ||
+ | </li> | ||
+ | </ul> | ||
+ | |||
+ | <h2>Action Items</h2> | ||
+ | <ul> | ||
+ | <li><strong>Thomas:</strong> Follow up on nudge data and search for relevant logbook entries.</li> | ||
+ | <li><strong>Naomi:</strong> Continue analysis in CPP logs for beam movement.</li> | ||
+ | <li><strong>Patrick:</strong> Refine Minuit fit and further explore causes of variation in coherent edge spread.</li> | ||
+ | <li><strong>Jiawei:</strong> Investigate feasibility of implementing a live plot for coherent edge monitoring.</li> | ||
+ | </ul> | ||
+ | </body> | ||
+ | </html> | ||
=== Action Items=== | === Action Items=== |
Revision as of 19:10, 18 November 2024
The current weekly meeting time is every other Monday at 13:00 US/Eastern
Connection Info:
You can connect using ZOOM Video conferencing (ID: 161 588 8669). (Click "Expand" to the right for details -->):
One tap mobile: US: +16692545252,,1602484178# or +16468287666,,1602484178#
Meeting URL: https://jlab-org.zoomgov.com/j/1615888669?pwd=MnhGVUhpeEd3NVpnTGxoZHJManNBdz09&from=addon
Meeting ID: 161 588 8669
Passcode: 561441
Join by Telephone
For higher quality, dial a number based on your current location.
Dial: +1 669 254 5252 US (San Jose)
+1 646 828 7666 US (New York)
+1 646 964 1167 US (US Spanish Line)
+1 551 285 1373 US (New Jersey)
+1 669 216 1590 US (San Jose)
+1 415 449 4000 US (US Spanish Line)
833 568 8864 US Toll-free
Meeting ID: 161 588 8669
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: 161 588 8669
Passcode: 561441
SIP: 1615888669@sip.zoomgov.com
Passcode: 561441
One tap mobile: US: +16692545252,,1601987443# or +16468287666,,1601987443#
Meeting URL: https://jlab-org.zoomgov.com/j/1615888669?pwd=MnhGVUhpeEd3NVpnTGxoZHJManNBdz09&from=addon
Meeting ID: 161 588 8669
Passcode: 561441
AIOP - Polarized Photon Source
Agenda:
- Previous Meeting
- Announcements
- Conferences/Workshops
- Project Progress
- Coherent peak drift evidence
- GitHub AIOP Project (AIOP-Photon issues)
- Milestones: PDF(GitHub AIOP Project AIOP-Photon issues FTE Profiles)
- PIER Activities
Middle School Data Science Hackathon Workshop (Oct. 16) Flappy Bird RL Learning- COMPLETED!HUGS mini-Workshop- COMPLETED!
- AOT
Minutes
<!DOCTYPE html> <html lang="en"> <head>
<meta charset="UTF-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <title>AIOP Meeting Notes - 11/18/24</title>
</head> <body>
AIOP Meeting Notes - 11/18/24
Attendees: David, Thomas, Torri, Naomi, Armen, Jiawei, Patrick
Note: With the holidays approaching, some work may need to be conducted through alternative means.
Progress Updates
Thomas
- Will run queries to retrieve data on nudges again.
- Plans to search for relevant anecdotes in the logbook.
Patrick
- Shared slides on his investigation into backlash:
- Used S2020 and removed outliers.
- Ensured the beam was operational.
- Observed fixed roll and three groupings of yaw:
- Coherent edge spread (a few hundred MeV).
- Question: Where is this spread originating?
- Hypothesized that variation could be fit-driven:
- Scalar values archived:
- Requires refitting (current fits show errors).
- Utilized Minuit fit.
- Possible hue mismatch with run number (or another factor).
- Need to calculate the error on the coherent edge.
- Highlighted the difference between set point and position.
- Scalar values archived:
Naomi
- Researched coherent peak movement instances:
- Recalled the March 30, 2018 event, where the coherent edge appeared problematic:
- A new diamond spot was located with a very narrow width.
- After the accelerator resumed operation, the width increased significantly.
- Hovannes relocated the beam to a new position for stability.
- Plans to examine CPP logs for periods with significant beam movement.
- Recalled the March 30, 2018 event, where the coherent edge appeared problematic:
Jiawei
- Presented before-and-after plots of coherent peak changes using archived data:
- Data source: HD:CBREM:ENH_REF.
- While the reference plot appears static, it successfully illustrates the difference in coherence.
- Mentioned that a “live plot” is harder to implement but feasible.
Action Items
- Thomas: Follow up on nudge data and search for relevant logbook entries.
- Naomi: Continue analysis in CPP logs for beam movement.
- Patrick: Refine Minuit fit and further explore causes of variation in coherent edge spread.
- Jiawei: Investigate feasibility of implementing a live plot for coherent edge monitoring.
</body> </html>