Difference between revisions of "AIOP May 20, 2024"

From epsciwiki
Jump to navigation Jump to search
(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...")
 
 
(One intermediate revision by one other user not shown)
Line 68: Line 68:
 
<!-- Attendees: David L., Thomas B., Torri J., Patrick M., Jiawei G., Naomi J., Malachi S., Armen K. -->
 
<!-- Attendees: David L., Thomas B., Torri J., Patrick M., Jiawei G., Naomi J., Malachi S., Armen K. -->
 
<ul>
 
<ul>
−
     <li>Reviewed previous minutes:
+
     <li>5-20-24</li>
 +
    <li>Attendees: David, Thomas, Torri, Hovanes, Jiawei, Armen, Cristiano, Patrick, Naomi</li>
 +
    <ul>
 +
        <li>Review of Minutes from last meeting</li>
 
         <ul>
 
         <ul>
−
             <li>Contention in nudge counts between patrick and jiawei’s algorithms</li>
+
             <li>Thorough review was had</li>
−
            <li>Slides from last time have been uploaded</li>
 
 
         </ul>
 
         </ul>
−
    </li>
+
        <li>Announcements:</li>
−
    <li>Project Progress
 
 
         <ul>
 
         <ul>
−
             <li>Patrick shared slides
+
             <li>There is a workshop at jlab on polarization. We should attend</li>
 +
        </ul>
 +
        <li>Project Progress</li>
 +
        <ul>
 +
            <li>data-mining/prep</li>
 +
            <ul>
 +
                <li>Jiawei: not much to report due to GlueX collab meeting</li>
 +
                <li>Patrick</li>
 
                 <ul>
 
                 <ul>
−
                     <li>Jiawei had 1123 nudge events vs 1241 for Patrick (~10% down from much greater)</li>
+
                     <li>Have identified more discrepancies</li>
−
                     <li>Looking over all spring 2020 (double check…may be 2018 fall)
+
                    <li>Need to remove Perp/para change based nudges</li>
 +
                    <li>Beam current on req from 30s to Jiawei’s 10s</li>
 +
                    <li>Showed a slide showing the difference in 1 vs 2 nudge counts</li>
 +
                    <li>David questioned the number of button clicks</li>
 +
                    <ul>
 +
                        <li>Looks like a nudge event may be many clicks waiting for system responses</li>
 +
                        <li>Hovanes agrees</li>
 +
                        <li>Naomi: how many &gt; = &gt;&gt;</li>
 +
                        <ul>
 +
                            <li>Hovanes: 10</li>
 +
                        </ul>
 +
                    </ul>
 +
                    <li>We think it should be 1 event not 2. Jiawei thinks he can combine them</li>
 +
                    <li>Do we have the rate of nudges?</li>
 +
                    <ul>
 +
                        <li>Patrick: no, not yet</li>
 +
                    </ul>
 +
                    <li>David: we need to have a nominal coherent edge to measure drift</li>
 +
                    <ul>
 +
                        <li>Naomi: will look (https://halldweb.jlab.org/hdops/wiki/index.php/Standard_Production_Running_Conditions)</li>
 +
                    </ul>
 +
                    <li>Hovanes: some PERP-&gt;PARA-&gt;PERP (vice versa) probably contain valid nudge events</li>
 +
                    <ul>
 +
                        <li>Patrick: being cut out…will go back and look</li>
 +
                    </ul>
 +
                    <li>~8% of nudges are when the beam is down. What do we do with them?</li>
 +
                     <ul>
 +
                        <li>Thomas thinks the case shown indicates the nudge condition was met and the button press happened when beam was away “unintentionally”</li>
 +
                        <li>Will try to reclaim with simple filters</li>
 +
                        <li>Beam conditions change from before to after nudge</li>
 
                         <ul>
 
                         <ul>
−
                             <li>Some discrepancies solved
+
                             <li>Naomi: small number get rid of them</li>
−
                                <ul>
 
−
                                    <li>Beam down times with nudge events</li>
 
−
                                    <li>@is_dirc_production and @status_approved tags not used before</li>
 
−
                                    <li>10 second window since goni changes</li>
 
−
                                </ul>
 
−
                            </li>
 
−
                            <li>Still 10% difference
 
−
                                <ul>
 
−
                                    <li>Going to look event by event</li>
 
−
                                </ul>
 
−
                            </li>
 
−
                            <li>David: Are the remaining events overlapping?
 
−
                                <ul>
 
−
                                    <li>Patrick: a couple hundred unique to each set. Maybe the timing (tagging) is slightly off</li>
 
−
                                </ul>
 
−
                            </li>
 
−
                            <li>Thomas: any other variables to tag events
 
−
                                <ul>
 
−
                                    <li>Patrick: yeah maybe duration, or end times. Etc.</li>
 
−
                                </ul>
 
−
                            </li>
 
−
                            <li>Slide 2 on Livingston c
 
−
                                <ul>
 
−
                                    <li>Tried to confirm c=k/gEo(...) using Hovanes script</li>
 
−
                                    <li>The script doesn’t seem to map pitch and yaw to delta c</li>
 
−
                                    <li>Hovanes needs to look at formula to agree. Looking at the formula x axis of slide 3. Patrick will provide this talk and the derivation for confirmation</li>
 
−
                                    <li>45/125 vs 0/90 may be problematic</li>
 
−
                                    <li>Naomi: pass the numbers from a small subset of events to hovanes?
 
−
                                        <ul>
 
−
                                            <li>Agreed to hand over the numbers</li>
 
−
                                        </ul>
 
−
                                    </li>
 
−
                                </ul>
 
−
                            </li>
 
 
                         </ul>
 
                         </ul>
−
                     </li>
+
                     </ul>
−
                </ul>
+
                     <li>New definition! Nudge sequence = multiple nudges. A nudge is a button press</li>
−
            </li>
+
                     <ul>
−
            <li>Jiawei showed slides [[20240506.pdf]]
+
                        <li>Hovanes: look at active collimator too</li>
−
                <ul>
+
                     </ul>
−
                     <li>Some nudges were alignment change oopse</li>
+
                    <li>Example of beam pos change with an event</li>
−
                    <li>Measured drift amounts (from start and from nominal)</li>
+
                    <li>More discussion as to the definition of the start/end of a nudge sequence</li>
−
                    <li>Spring 2020 looks best</li>
+
                    <li>Discussion of definitions of event start/end as it relates to the “training data”</li>
−
                    <li>Hovanes notes the number used as “nominal” really used as fit starting point.</li>
 
−
                     <li>Naomi: wasn’t fall 2018 had a flat top and needed a new spot?</li>
 
−
                    <li>Hovanes: bottom line: don’t use CBREM:REQ_EDGE</li>
 
−
                     <li>Naomi: may be able to get the required from Alex wiki</li>
 
−
                </ul>
 
−
            </li>
 
−
            <li>How is the beam spot determined</li>
 
−
                <ul>
 
−
                  <li> Naomi: look for most uniform thickness place</li>
 
−
                  <li>Looking at Richards calculator</li>
 
−
                  <li>There may be a way to change from goni pitch/yaw x y to diamond spot. Hovanes thinks both Richard and hall look at beam spot from the same side. Some radiators are missing from the dropdown</li>
 
−
                  <li>Hovanes: you need Zygo plot not beamspot</li>
 
−
                  <li>David: proposal mentions beamspot to do digi twin</li>
 
−
                  <li>Patrick: No reliable offsets right Hovanes?</li>
 
−
                  <li>Hovanes: no reliable offset</li>
 
−
                  <li>Hovanes sent a link: <a href="https://docs.google.com/spreadsheets/d/1v2lTIeHomF46NVSnvGhSi8oYJj6Tkd3zv341_EqYlrs/edit#gid=0">https://docs.google.com/spreadsheets/d/1v2lTIeHomF46NVSnvGhSi8oYJj6Tkd3zv341_EqYlrs/edit#gid=0</a></li>
 
−
                  <li>We looked at an example Zygo plot</li>
 
−
                </ul>
 
−
            <li>Patrick asked Hovanes about the use of the script.</li>
 
−
                <ul>
 
−
                <li>Hovanes: yes it is used. Buried in scripts and scripts</li>
 
−
                <li>What is the process</li>
 
−
                <li>Hovanes: shift worker looks and clicks a button and it shifts the goni. The button click runs the script to know how to adjust the goni</li>
 
 
                 </ul>
 
                 </ul>
−
            <li>PIER activities</li>
 
−
            <ul>
 
−
                <li>Meeting with Lisa biweekly</li>
 
−
                <li>~30 kids on chrome books</li>
 
−
                <li>Need to reserve F113</li>
 
−
                <li>Thomas working on draft agenda</li>
 
 
             </ul>
 
             </ul>
 
         </ul>
 
         </ul>
−
     </li>
+
     </ul>
 
</ul>
 
</ul>
  
  
 
==== Action Items ====
 
==== Action Items ====

Latest revision as of 13:02, 3 June 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:

  1. Previous Meeting
  2. Announcements
  3. Project Progress
  4. PIER Activities
  5. AOT


Minutes

  • 5-20-24
  • Attendees: David, Thomas, Torri, Hovanes, Jiawei, Armen, Cristiano, Patrick, Naomi
    • Review of Minutes from last meeting
      • Thorough review was had
    • Announcements:
      • There is a workshop at jlab on polarization. We should attend
    • Project Progress
      • data-mining/prep
        • Jiawei: not much to report due to GlueX collab meeting
        • Patrick
          • Have identified more discrepancies
          • Need to remove Perp/para change based nudges
          • Beam current on req from 30s to Jiawei’s 10s
          • Showed a slide showing the difference in 1 vs 2 nudge counts
          • David questioned the number of button clicks
            • Looks like a nudge event may be many clicks waiting for system responses
            • Hovanes agrees
            • Naomi: how many > = >>
              • Hovanes: 10
          • We think it should be 1 event not 2. Jiawei thinks he can combine them
          • Do we have the rate of nudges?
            • Patrick: no, not yet
          • David: we need to have a nominal coherent edge to measure drift
          • Hovanes: some PERP->PARA->PERP (vice versa) probably contain valid nudge events
            • Patrick: being cut out…will go back and look
          • ~8% of nudges are when the beam is down. What do we do with them?
            • Thomas thinks the case shown indicates the nudge condition was met and the button press happened when beam was away “unintentionally”
            • Will try to reclaim with simple filters
            • Beam conditions change from before to after nudge
              • Naomi: small number get rid of them
          • New definition! Nudge sequence = multiple nudges. A nudge is a button press
            • Hovanes: look at active collimator too
          • Example of beam pos change with an event
          • More discussion as to the definition of the start/end of a nudge sequence
          • Discussion of definitions of event start/end as it relates to the “training data”


Action Items

Retrieved from "https://wiki.jlab.org/epsciwiki/index.php?title=AIOP_May_20,_2024&oldid=5059"