Skip to content

Prep for v0.7.0: release notes and version bump - #362

Open
scal444 wants to merge 3 commits into
NVIDIA-BioNeMo:mainfrom
scal444:prep-v0.7.0
Open

scal444 wants to merge 3 commits into
NVIDIA-BioNeMo:mainfrom
scal444:prep-v0.7.0

Conversation

@scal444

@scal444 scal444 commented Oct 8, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

@greptile-apps

greptile-apps Bot commented Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerConfidence Score: 5/5

[Low impact] The PR appears safe to merge.

Summary

Prepares nvMolKit 0.7.0 by updating release notes, version values, installation examples, and release-tool fixtures.

  • The build, package, and runtime versions agree.
  • The documented API changes match the current code.
  • No actionable issue was found. Tests were not run.

Reviews (1) · Last reviewed commit: "Drop Butina note from 0.7.0 summary" · Reviewed by Greptile

@scal444
scal444 requested a review from evasnow1992 October 8, 2026 19:46
Comment thread docs/changelog.md

### Features
- Single-precision mode (`precision=PrecisionMode.SINGLE`) for MMFF and UFF force fields, BFGS and FIRE minimizers, and ETKDG distance geometry and ETK stages, available through the MMFF, UFF, `BatchedForcefield`, and `EmbedMolecules` APIs. On consumer GPUs, single precision is roughly an order of magnitude faster than double precision. Validation against RDKit is documented in the 3D minimizers guide ([#266](https://github.com/NVIDIA-BioNeMo/nvMolKit/issues/266))
- GPU-accelerated 3D descriptors through the new `nvmolkit.descriptors3d.Calc3DProperties`, which computes a user-selected set of properties in one fused pass over a batch of conformers: PMI, NPR, radius of gyration, shape factors, PBF, WHIM, RDF, MORSE, AUTOCORR3D, USR, USRCAT, and GETAWAY, matching RDKit's `rdMolDescriptors` ([#341](https://github.com/NVIDIA-BioNeMo/nvMolKit/issues/341))

@evasnow1992 evasnow1992 Oct 8, 2026 •

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Calc3DProperties defaults to PrecisionMode.SINGLE, unlike the minimizers and ETKDG, which default to FULL. Should we mention that single precision is used by default here, so users don't assume the descriptors are computed in double precision like the other APIs?

@evasnow1992 evasnow1992 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Thank you for bumping the version! So excited about this release!

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.

2 participants