This page shows upcoming high-level (monthly) meetings for G4CMP updates. These meetings will occur monthly, starting from 7/25/2024, unless otherwise posted. They will be staggered on an "off week" from the biweekly technical meetings, since they're at the same day/time of the week.

Time: 9AM PT, 10AM MT, 11AM CT, 12PM ET (Calendar)

Zoom info: https://fnal.zoom.us/j/98903761047?pwd=sBNNne2mGQzJTRwVsNdNzVI22ZTQuP.1

 

Attendees: MK, RL, WP, SS, BL, BZ, NT, Wade Lamberson, SZ, PM, GC, TC, JL, ÉM, CL

Agenda:

 

Attendees: CSW, RL, SS, ÉM, PB, BL, NT, JL, JY, IH, MK, AP, TC,

Agenda:

  • Introductions/Announcements:
    • Mike worked on fixing a bug dealing with high voltage conditions where electrons would get stuck in a loop in mesh during IV process
      • Temporary fix: cut on number of steps the electron can do 
      • IV scattering improvement shown today also fix this problem
    • Mike: Nolan is getting phonon specular reflections nearly fully operational. Emile/Nolan/Mike will coordinate releases over the next few weeks
  • Talk on Charge Transport / IV Scattering (Émile Michaud)
  • Discussion
  • AOB


 

Attendees: Ryan, Mike, Gün Süer, Siamak, KC, Micah, Émile, Caitlyn, Nolan, Matthew, Tom, Jared, Eric M, Paul, GPC, Jesse, Birgit, Israel, Guillermo

Agenda:

  • Introductions: Gün Süer
  • Talk: "Investigations of Nuclear Interactions in Superconducting Quantum Devices" – Micah
  • Discussion points others find useful
  • Discussion of other interesting APS talks
    • SLAC/UW-Madison MEMS measurements + Selby's MEMS G4CMP modeling talk 
    • Doug P.'s talk on alpha measurements with SC qubits
    • NIST talk on electron beam hitting chiP
    • Others?
  • RISQ: any plans for this year? No, but want to do a RISQ-lite where we maybe have a long G4CMP consortium meeting + tutorial.
  • AOB

 

Attendees: RL, MK, CSW, SS, BZ, CS, BL, JL, NT, TC, ÉM, JY, GC, SZ, EM, IH, MJ, NK

Agenda:

  • Question:  Should we create true GitHub "releases" (tar-balls) of G4CMP main-branch tags?
    • May require some development work, especially to get the version number defined outside of git describe .
    • JY: A bit confusing because lots of tags that aren't releases – may solve through documentation or how to make easiest to get most recent one
      • MK: No section on downloading G4CMP in readme file – easy to write a paragraph clarifying  G4CMP-466 - Getting issue details... STATUS
      • Sounds like this is a vote for the tarballs, with good justification
    • SZ: There are three-digit "release tags" and "feature tags".
    • TC: Soft vote for having tarball package – easier for IT team to deal with
      • Want link for someone to click on w/o having to look at github
      • Stack management system? (A&M: EasyBuild – much prefer getting a tarball)
    • CS: appetite for pushing prebuilt package into conda-forge?
      • Mike no like.
      • CS says conda-forge lowers energy barrier for his IT

      • SZ: Conda is discouraged on Canadian clusters.

      • SZ: As a long-term development idea we has envisioned to adopt the SCDMS apptainer release model with computing resource support at SLAC.

    • Conclusions: worth looking into generating these G4CMP-467 - Getting issue details... STATUS
  • Introductions (brief): welcome Eric Mascot!
  • Discussion of APS March/April Talks
    • G4CMP Consortium Members' Talks/Sessions: MJ, GP, EM, BL, CSW, IH, RL, EY, TC, NK, [Zoey, Aviv, Jaden, Taylor: SLAC]
      • MJ: APR L-19/2
      • BL: Brenden APR L-19/3
      • Jaden@SLAC: charge readout for 526 material, long-term G4CMP relevant
      • To do for Ryan: find other G4CMP folks' talks and put here!
    • Other interesting talks/sessions (link to hastily-made notes document)
    • G4CMP-oriented conference goals?
      • Ryan: learn and compile set of applications for trackedFilmResponse, chat with folks on this
      • CSW: how do we articulate why G4CMP is useful? In what application space is it useful? Goal: help convince holdouts that this is a good tool (at least for particle detection and maybe more?)
    • Would like to organize a dinner to meet y'all in person! Thoughts on the night? Tuesday?
      • Tuesday saw thumbs up
      • MJ: Choose a place with drinks!
    • NK: Standard G4CMP Consortium plug slide for sharing with community – send around to Selby, Noah, Eric, others
  • TC: High-level question about G4CMP/Geant4
    • Context: wanting to toggle on/off G4CMP physics for sanity checks
    • Phonon stuff in pure Geant4 toolkit is obsolete
    • Open G4 ticket to remove all of the phonon stuff from G4
  • AOB

 

Attendees: 

Agenda:

 

Attendees: Siamak Sorooshyari, Eric Yelton, Jesse Lutz, Mike Kelsey, Anna Huynh (new!) Jared Yamaoka, John Batarkeh (new?) Brenden Longfellow, Paul Baity, Jake Inman, Émile Michaud, Nolan Tenpas (new!), Tom Carroll, Birgit Zatschler, Philip Mason, Warren Perry

Agenda:

  • Introductions
  • G4CMP applications, use cases (new folks, especially)
  • From Kelsey: Small updates and fixes on G4CMP develop branch over the break
    • Make debugging files thread-safe ( G4CMP-419 - Getting issue details... STATUS G4CMP-439 - Getting issue details... STATUS G4CMP-440 - Getting issue details... STATUS )
    • Improvements to Phonon_Caustics model ( G4CMP-434 - Getting issue details... STATUS G4CMP-438 - Getting issue details... STATUS G4CMP-437 - Getting issue details... STATUS )
      • Would like to rename directory to examples/caustics ( G4CMP-443 - Getting issue details... STATUS )
    • Fix to "Lindhard" (Robinson) NIEL model, from Tom Carroll ( G4CMP-436 - Getting issue details... STATUS )
  • "Propagation velocity measurements of substrate phonon bursts using MKIDs for superconducting circuits", https://doi.org/10.1063/5.0232368
    • From Jonathan DuBois: "The explanation for the time dynamics they observe doesn't make complete sense to me. In particular, the integrated phonon flux argument for why the see such a strong dependence of the effective propagation velocity on the SNS bias voltage seems to make some strong and not particularly well justified assumptions.  I'm also curious about what appears to be a (relatively) instantaneous effect observed in the data in figure 3 (see below) -- suggesting a photonic or galvanic connection between driving the SNS and the MKID response.
  • AOB

 

Attendees: Jared Yamaoka, Israel Hernandez, Eric Yelton, Ryan Linehan, Paul Baity, Stefan Zatschler, Chris Moore, Birgit Zatschler, Siamak Sorooshyari (new!), Birgit Zatschler, Philip Mason, Micah Johnson, Mike Kelsey, Tom Carroll, KC Fong

Agenda:

  • Introductions for new folks
  • Status update on quasiparticle tracking code (Ryan)
  • Issues with surface reflections and nested volumes (Ryan, Kelsey) – ran out of time, punted to next biweekly technical meeting
  • AOB

 

Attendees:

Agenda:

  • Discussion of how to press forward with writing down coding guidelines

  • Confluence and JIRA access.  Reminder: respond to the invitation e-mails!

  • AOB/Office hours
  • Feedback
    • NIEL models: mistake/inconsistency in what Linhard-Robinson model is returning the NIEL fraction, but if take Lewin-Smith NIEL partition as truth, the code is expecting ionization  fraction.
      • Quick fix is to return 1-(what Lindhard model is returning)
      • Tom can't put in request bc industry, but is encouraged to send Mike an email
      • Will double-check to make sure the bug is true, and will create Jira ticket
    • Mike: Questions for Jesse and Eric
      • Diffusion of charge carriers at zero volts
        • Discussion of doing this diffusion process more like G4Cerenkov – Warren might be a person to work on this, but depends on bandwidth/appropriateness
        • Little bit different from the way the trackedFilmResponse works – would want to bundle steps + phonon emission into multiple scattering process
        • For holes, only have NTL
        • For electrons, have intervalley scattering and NTL, many 10's of scatters across chip.
          • Goal is to reduce number of steps, compute average deflection from those phonons and then generate a bunch of random phonons
    • Probing to see if anyone is working on charge transport in new materials
      • Turns out that nobody's currently working on this
      • First step: similar literature search as for phonons, then charge transport will "just work"

 

Attendees: Matthew Natale, Eric Yelton, Stefan Zatschler, Gioele Casagranda, Jake Inman, KC Fong, Chris Moore, Émile Michaud, Birgit Zatschler, Ryan Linehan, Mike Kelsey, Jesse Lutz, Israel Hernandez, Jared Yamaoka

Agenda:

Notes:

  • No distinction between the level of accounts for Jira and Confluence – use a single G4CMP Confluence Users group attached to both Confluence and Jira access. Want to maintain distinction in web form, since SLAC license is for a fixed maximum number of Jira users (but no limit for Confluence). This becomes a problem if G4CMP becomes too big, but for now it's fine.
  • No way to identify on the google form whether you already have a SLAC account – may want to indicate somehow that you do (send separate email to Noah/Ryan to indicate that you have SLAC account). Hoping to add field to this to google form – stay tuned
  • Need github username as well for those who want to make changes on github – need a field for this

 

Attendees: RL, Eric Yelton, Gioele Casagranda, Chris Moore, Tom Carroll, Paul Baity, Nathan Nakamura, Emile Michaud, Jared Yamaoka, Jesse Lutz, Matthew Natale, Noah Kurinsky, Israel Hernandez, Caitlyn Stone-Whitehead, Michael Kelsey

Agenda:

 

Attendees (remembering from memory): AM, GPC, EY, GC, XL, JI, PB, DS, BZ, SZ, RL, NK, MK (plus some others I may have missed)

Agenda:

  • Presentation of Confluence Space

  • Discuss the vision for G4CMP co-development and community organization around this space (and solicit ideas from you all on how to improve it!)

    • Discussion of most useful cluster tools:
      • Jupyter frontend for analysis, access to SLAC cluster 
      • Goal is to make low barrier-of-entry for new folks – structure still under development
      • Stefan Zatschler: can help with software setup on S3DF
      • Don't want to require people to get S3DF accounts
        • In user form, can specify what account info they want
      • Computational requirements: 
        • Mike claims that we need 20 threads (CPUs) for a user to run a job
        • Jupyter sessions typically require 1-2 CPUs for simple
        • Hard question to answer because lots of CDMS computations done at Compute Canada
        •  Need to know what we want to start with, because we want to buy in (buying hardware) – have access to more than what we buy, though
          • Need typical number of users, number of CPUs per user
        • Would be nice to understand how many CPUs per machine
        • Benchmarking is open-ended story

        • S3DF is about "owning" the hardware. That guarentees you a pool of resources that cannot be preempted by other user groups.

    • Discussion of public/private:
      • Don't necessarily want barriers to use due to public nature of G4CMP
      • No account: can see most things already
        • Have internal pages – meeting slides/presentations that need approvals
        • Have an internal page for sensitive slides – can upload content there and then link there. Confluence should  handle that with authentication there
        • Then have public meeting page and those who are okay with making page public, just upload to this meeting page
        • Other internal things: hostname/address to get into S3DF, etc. 
    • Listservs:
      • Ryan will work offline to add a second one and make a page for people to sign up for this (as well as internal page for admin instructions)

  • Begin organization of G4CMP technical progress, and get volunteers to present work for upcoming G4CMP technical "working group" meetings.

    • Do people want to migrate, or are their local machines good enough?
    • Eric: working on QP diffusion, can share
    • Paul: can present ongoing work at BNL on chip optimization
    • Ryan: can present at some point
    • Student at A&M: fixing inability of phonons to be reflected at curved surfaces: Wade Lamberson
    • Another A&M student: Iman Ataee fix to electron transport
      • How does community care about roll-out?
    • Israel: working 
    • Gioele: "

      I definitely want to take part in these technical meetings, but rn I am currently "just" using G4CMP, not developing. I would anyway like to start developing"

    • Jesse: 

      I’m in the same position as Gioele.  Excited to contribute but well short of a presentation.  I’m happy to help create documentation.

  • Whitepaper: people should ping me on Slack and I'll follow up with that
  • AOB
  • No labels