View on GitHub

DIALS // knowledgebase

community resources, howtos, meeting minutes

ND Investigate getting psana tests running on the DIALS xfel-regression testing
ND: Move dials.diamond.ac.uk to a redirect to dials.github.io
ND: Action: Replace dials-support link with slack link/new mailing list address

Work done.
Numpy 2 support in cctbx/dxtbx#751 dials/dials#2942
Python 3.13 support in cctbx/dxtbx#826 dials/dials#2946
Previously discussed: To test, let’s add to matrix to run both and python 3.13 in branch. DP will do this.
- Discussion about https://github.com/cctbx/cctbx_project/issues/1084 and numpy 2 support
- Notes on flumpy, idea about abstracting to separate library.

3pm Thursdays was what we talked about
ND talk to JBE about running
Make informal promise for office hours, and a slack channel that people can make known that they have a request to chat/for help about a particular topic
JBE booked room, not sent out invites/ zoom yet - try to get done in next week.
- Consider sending reminder to slack day before advertising
Graeme suggested “themes” for the office hours

Aaron wants to have a dials tag attached to all export, then we can make sure that is always carried through to refined structure. Aaron will handle Phenix, DW will try for CCP4.
- CCP4 GUI, data is lost when packaging mmcif
- Ongoing investigations, optimism that can be fixed
DGW made some progress, agreement to add history recording into experiments file. Will pick up again after Easter, but WIP.
Discussion between Aaron/DGW about contents of history/approach across cctbx/dials
Address when david back
08/05/25 update - DGW - PR nearly ready that records history item in experiments file. Top level field outside of experiment list. But will require a number of dials changes as often we make new lists/copies, so will need to copy across history. dxtbx PR first, then follow up with dials once in.At point of export, look through existing history items and extract integrate, scale lines and filter those out.
Follow up with Aaron again next time.
PRs and Blockers:
- ~~https://github.com/dials/dials/issues/2931 - version numbering off~~
- Aaron had build issue, a joint look has identified issues, DGW can continue

https://github.com/dials/dials/pull/2732
Do we need to keep .conda_envs/*.txt present (with e.g. a notice saying not to edit directly?)
General agreement