feat: add support for non-orthogonal cells in amber/md format #870
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
The
amber/mdformat previously only supported orthogonal unit cells (90° angles), raising aRuntimeError("Unsupported cells")for any simulation with non-orthogonal cells. This limitation prevented users from processing AMBER trajectories with triclinic, monoclinic, or hexagonal crystal systems.Changes
cell_lengths_angles_to_cell()function that converts cell lengths and angles to 3×3 cell vector matrices using standard crystallographic conventionsread_amber_traj()by replacing the angle check with general cell conversionSupported Crystal Systems
The implementation now handles all crystal systems:
Example Usage
Testing
Added comprehensive test coverage including:
All existing amber/md tests continue to pass, ensuring no breaking changes.
Fixes #869.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.