DevNotes_30Jun2026

General updates (roundtable)

• Any technical meeting updates?
• Refactoring project updates?
• SASBDB integration project (Wojciech)
  • on hold till July
• Generic Scattering Calculator redesign working group
  • the webpage has been updated
  • A 3rd meeting will be scheduled to try to finalize a concept.
  • Would be nice to be in a position to start working on implementation at contributor camp
• Sasmodels working group (refactoring project and marketplace vs core etc) (Paul)
  • Wiki pages generated https://github.com/SasView/sasview/wiki/DevNotes_ModelsWG
  • Kickoff meeting delayed until...
  • Would be nice to be in a position to start working on implementation at contributor camp
• Contributor Camp XV - Prague -- UPDATES?
  • planning/info page
• Contributor Camp XVI - Paris
  • planning/info page
  • Need to submit the proposal by mid September
• Mailing lists.
  • Migrating to a new server in the next few weeks
  • AND, in the process, upgrading from MM2 to MM3
    • SHOULD be no change for mail recipients (except for few minutes glitch in receipts)
    • IF you manage your list account - you will need to create a new one using the email address you receive email on.
    • Archives will be more easily searchable (and indexable?)
    • mail should handle modern security much better.
• sAS2027
  • Should we schedule a community meeting (as in Traverse City - SAS2018)?
  • Should we think about training sessions of some kind?

6.2.0 Release - Sujaya

Discussion on status of testing. Any issues? Are we ready for the final release?

---

• Code freeze started on 15th May.

  • Release checklist
  • New versions for SasModels (1.0.13) and SasData (0.12.1)
    • Tag v0.12.0 inadvertently generated. Version associated with SasView v6.2.0 will be a point release.
  • The latest betas available for testing:
    • SasView B1
    • SasModels B1
    • SasData B1
  • Enter issues as sub-issues of #3955
    • Bumps DREAM plots issue to be fixed in bumps v1.0.5 (forthcoming)
    • Release dependency lists not used to generate release (pins in requirements.txt?)

• Timeline:

  • Mid June: end of alpha testing, Beta1 release
  • ~June 24-26: Final release candidate
  • End of June/early July: full release

• Rules:

  • only bug fixes and documentation relevant to new features
  • no new models

---

PRs

sasview: 33 open, 14 in draft

• Potentially for v6.2.0
  • #3967 Report backgrounds
  • #3975 Multiline log messages
• CI related
  • #3842 Add pixi configuration
  • #3932 Attach binaries to release page on tag
  • #3947 Cancel concurrent nightly builds
  • #3974 Allow pytest from base project directory
• New features
  • #3962 Size Distribution calculator clean up
  • #3963 Single kernel call for volume and intensity - approved but failing
  • #3965 Adds PDF report for Size Distribution
  • #3995 Undo/redo stack for perspectives
  • #3996 Fix invariant plot sliders
  • #3997 AUSAXS rigid body refinement

sasdata: 8 open, 3 in draft

• #207 Refactor averging.py and manipulations.py to use refactor Quantities
• #213 SasData Database
• #216 Trend Object Extended Work

sasmodels: 11 open, 6 in draft

• #722 Fractal S(Q) accuracy at small Q
• #730 Check adaptive example documentation - Possibly for sasmodels 1.1.0 final
• #737 Remove warnings from non-pd kernels
• Four models in the works - any updates?

ADRs sent out for review

• New code should be formatted using a linter -- sent out on June 12

Help desk staffing

https://github.com/SasView/sasview/wiki/DevNotes_HelpDesk

AOB