Skip to content

Latest commit

 

History

History
93 lines (85 loc) · 6.64 KB

File metadata and controls

93 lines (85 loc) · 6.64 KB

areaDetector Collaboration Meeting (2025-05-08)

Attendance

  • Érico Nogueira Rolim
  • James Souter
  • Mark Rivers
  • Wang Xiaoqiang
  • Qun Zhang
  • Kevin Peterson
  • Gustavo Reis
  • Josh EC
  • Elaine Chandler
  • Mark Engbretson

Previous meeting action points

  • Small documentation and typo changes don't need PRs, but code changes can have them
  • Open issues/PRs specifying PV behavior more explicitly
    • Acquire -> people should use the busy callback
    • "Detector is ready for triggers" -> ARMED PV? Acquire_RBV?
  • Send list of issues/PRs to tech-talk to bring interested people into meeting
  • Find owners (contact points) for drivers and define obsolete drivers sent to tech-talk: https://epics.anl.gov/tech-talk/2025/msg00536.php
    • Diamond might take up ADAravis no updates on this
    • Even so, merging PRs doesn't have to depend on the owner; code review can come from anyone, and the author has presumably tested it
  • Releases are made when someone needs a new feature or driver change, or when changes have accumulated
    • Update all drivers to master
    • Tag ADCore and top-level areaDetector simultaneously
  • Inclusion of new drivers
    • Include documentation
    • Code quality
    • Build out of the box if possible
    • Generality (can other people use it?)
  • Help required: fix ADCore CI DONE!

Issues

Action points

  • See if PyDM autoconvert can be added to autoconvert recipe
  • Open issues/PRs specifying PV behavior more explicitly
    • Acquire -> people should use the busy callback
    • "Detector is ready for triggers" -> ARMED PV? Acquire_RBV?
  • Find owners (contact points) for drivers and define obsolete drivers sent to tech-talk: https://epics.anl.gov/tech-talk/2025/msg00536.php
    • Mark will respond to the email with further suggestions
    • Diamond might take up ADAravis