Skip to content

Post for release 2.11.0 - #526

Open
orbeckst wants to merge 2 commits into
masterfrom
post-release-mda-211
Open

orbeckst wants to merge 2 commits into
masterfrom
post-release-mda-211

Conversation

@orbeckst

Copy link
Copy Markdown
Member

fixes #525

Draft post based on CHANGELOG and release information.

Generated with cursor's default model and manually checked and edited.

@orbeckst
orbeckst force-pushed the post-release-mda-211 branch from 5ec8c2a to edd856b Compare October 24, 2026 21:45
- generated draft based on CHANGELOG and release info on GitHub
- manually checked and edited

Assisted-by: Auto cursor
@orbeckst
orbeckst force-pushed the post-release-mda-211 branch from edd856b to 66b583e Compare October 24, 2026 21:47
@orbeckst

Copy link
Copy Markdown
Member Author

@IAlibay feel free to use/edit for the release post.

@orbeckst

orbeckst commented Oct 24, 2026 •

Copy link
Copy Markdown
Member Author

(It builds fine with my local jekyll installation)


MDAnalysis thanks [NumFOCUS][] for its continued support as our fiscal sponsor,
the [Chan Zuckerberg Initiative][] for supporting MDAnalysis under an EOSS5 award,
and the [National Science Foundation][NSF] for support under CSSI award

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did not include RMSF because we only just hired but if you think we should add them right away then I am not opposed!

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@micaela-matta @jennaswa what do you think?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wouldn't include, none of the work here was done with that funding.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have left it as is — please chime in if you want it changed.

@IAlibay IAlibay left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couple of brief comments from an initial read through. Thanks for writing this!

Comment thread _posts/2026-10-21-release-2.11.0.md Outdated

We are happy to release version 2.11.0 of MDAnalysis!

This is a minor release of the MDAnalysis library, which means that it

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This reads LLM generated, so my comment is more direct. As far as I can remember, this isn't a thing we usually say, personally I wouldn't want to have this statement / guarantee.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's directly from the previous release posts – https://www.mdanalysis.org/2025/10/26/release-2.10.0/ , https://www.mdanalysis.org/2025/03/11/release-2.9.0/, https://www.mdanalysis.org/2024/11/22/release-2.8.0/ — we've been writing it like this previously, so I actually have defen the LLM: it did exactly what I'd have done, namely template the new post on the old ones.

I can rewrite a little bit for variety ;-)

Comment thread _posts/2026-10-21-release-2.11.0.md Outdated
Supported Python versions: **3.11, 3.12, 3.13, 3.14**.

Supported Operating Systems:
- **Linux** (on [x86-64][])

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And ARM64.

We also release conda installs for ppc64le.

Comment thread _posts/2026-10-21-release-2.11.0.md Outdated
* GROMACS TPR reader improvements:
* Support for TPR files written by GROMACS 2026 ([PR #5219][])
* Linear angle potentials are read into the topology ([Issue #5361][], [PR #5372][])
* Box vectors are available as `Universe.dimensions` ([Issue #5375][], [PR #5466][])

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Box vectors are available as `Universe.dimensions` ([Issue #5375][], [PR #5466][])
* Box vectors are now read from file and available as `Universe.dimensions` ([Issue #5375][], [PR #5466][])

Comment thread _posts/2026-10-21-release-2.11.0.md Outdated
the upstream PyDSSP 0.9.1 fix ([Issue #4913][], [PR #5065][])
* Faster distance calculations, with a selectable distance `backend`
(for example `"distopia"`), and hydrogen-bond detection that respects
periodic boundary conditions ([PR #5182][])

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this more of a fix than an enhancement?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, I split it up

Comment thread _posts/2026-10-21-release-2.11.0.md Outdated

#### Fixes:

* Positions and velocities read from TPR files are converted to MDAnalysis

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would maybe group the TPR fixes, like we do for enhancements.

([PR #5374][])
* Fixed reading of older TPR files written before GROMACS 5.1 (TPX version
< 103) ([Issue #5145][], [PR #5146][])
* Fixed periodic-boundary handling for triclinic boxes in `apply_PBC()`

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe would be good to have this as the first item, given that it's the most concerning bug.

Comment thread _posts/2026-10-21-release-2.11.0.md Outdated
example a rhombic dodecahedron); `pkdtree` in boxes with both `b_x`
and `c_y` non-zero (for example a truncated octahedron).
* NumPy boolean arrays passed to `AnalysisBase.run(frames=...)` are treated
as frame masks. Previously they were interpreted as integer frame indices

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Where True was parsed as frame 1 and False frame 0" - I think this might be worth saying more explicitly so that folks who are newer to python understand the issue.

- addressed @IAlibay's comments
- added an initial highlight sentence for mmCIF/PDBx support
- reorganized fixes so that all analysis-related ones are together
- clarified AtomicDistances changes and linked to docs

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

add post for 2.11.0 release

2 participants