DevNotes_24Jul2026_Technical

New Topics to Discuss

• Sujaya's last technical meeting
  • Help to review his PRs
• James is returning
• Next Hackathon
  • Prior to Contributor Camp (September?)
  • Any dates we should avoid?
    • NOBUGS: Sept. 21-25
    • Delaware Neutron Day: Sept. 24-25
  • Jeff to send Doodle Poll avoiding 1st week of Sept. and Sept. 21-25
• Planning for Contributor Camp
  • Who is planning to attend? Register!
  • Discussion on presentations, projects, and collaborations
    • Questions only so far - What will be taught and what will be worked on?
    • Front-end presentations to orient people
    • Projects
      • GSC based on discussions
      • Refactoring Project
      • Sasmodels refactor/rework
      • Magnetic SANS(?)
      • MCR-ALS project

Version 6.2.0

• Release Candidate 1 is out
• Final release set for Thursday, July 30
• Outstanding Issues:
  • See the top-level issue
    • Truncated octahedron model problem #3993 - Generalized issue title and agree this should be fixed, but for a future bug fix release
  • PRs:
    • SasModels #730: Documentation for adaptive integration example file - Sujaya to include in final release
• Release manager for 6.2.x bug fix releases? Paul S. has volunteered (with help by Jeff K. and James)
• Any further issues/additions to the list?
  • PD: paracrystal models are slow with PD and PD never gets turned off when PD disabled. Paul B. (and Jeff K.?) to investigate and add issue
  • Fitting stop not working? When new fit started, old fit resurrected. Paul B. (and Jeff K.?) to investigate and add issue
  • Unable to add pure python + C model together. Unable to use magnetic data with pure python. Paul K. to investigate

Status updates of ongoing projects

• CodeScene (Paul S./Jeff)
  • CodeScene integration: Post-6.2.0 release - enable on sasmodels and sasview?
    • What gates may trip immediately in sasview? Jeff K. to investigate...
    • Current implementation ensures code isn't getting worse, so above may be moot
• MCR-ALS Project
  • Multivariate Curve Regression
  • Self-contained tool
  • pycosmics - separate curves contributing to a single fit
  • End of August timeline - present during biweekly call in mid-August

Outstanding PRs

• SasView
  • Ready to merge?
    • PDF Reports for Size Distribution: #3965 - to merge
    • Pytest from the base directory: #3974 - to merge
    • Multiline logging: #3975-
  • Needs reviewers
    • Shape2SAS reorg: #4054
    • Old cards in What's New: #4046 - likely have to wait
• SasModels
  • Ready to merge?
    • Torus elliptical shell model: #704 - to merge
    • Unused step warning: #737 - to merge
• SasData
  • Refactor Trend: #216
  • Database: #213 - Jeff K. to resolve merge issues, Paul S. to review, and Jeff K. to merge
• SasView.github.io
  • Update Acknowledgement Section on Website: #37

ADRs

• Finalized
  • https://github.com/orgs/SasView/discussions/4055: Linter
• To Finalize
  • https://github.com/orgs/SasView/discussions/3475: Release automation - Remove from ADRs and create issues for each step
    • Final write-up: https://github.com/orgs/SasView/discussions/3475#discussioncomment-16757778
    • Zenodo generation: build_tools/release_automation.py - Piotr to look into Zenodo DOI generation that he knows of in other repos
    • Pypi publishing: Work started in sasdata. Finalize and port to sasview and sasmodels - Piotr to work on https://github.com/SasView/sasdata/blob/master/.github/workflows/test.yml#L84
    • Upload binaries to releases: Already working for nightly build. Port in progress - Draft PR
  • Minor comments to address for linter ADR, nothing received for release automation.
  • Make final?
• Ongoing discussions:
  • https://github.com/orgs/SasView/discussions/3934: Defining the release process and release manager
    • Some of the process is outlined in https://github.com/SasView/sasview/wiki/DevNotes_DevGuide_ReleaseChecklistTemplate
    • Release notes for Dev releases? Cumulative from previous stable release or from last dev release? Final release should have cumulative.
    • Delete/pare-down/hide dev releases after stable release? As long as we keep the tags and the binaries, the release notes can be pared down. More work for release manager if pared down. Likely keep as is to not create more work for ourselves.
  • No Link: Contributing to SasView: Define the process, i.e. what the requestor needs to provide, level of support from the existing community, and what that gets the contributor
    • https://github.com/SasView/sasview/wiki/contribution_acknowledgments to an ADR - Paul B. to convert prior to the Nov. Contributor Camp

AOB?

• SASBDB Project:
  • One PR ready for review
  • AI agent context file included - keep in repo or not? What about other tools? Separate PR for this file? Need to discuss more on what is in the file. Add in separate directory as a base/starter/template? Wojtek to start a Github discussion on the topic.
• Sujaya - anything else he needs from anyone?