Matt Thompson

I think we've finished this - please let me know if my memory is shoddy here or if there are future improvements that would make your work smoother

Yeah sorry this is all over the place; it'd be much easier if it was an OpenFE or OpenMM documentation issue and not a mixture of both The best suggestion...

Good catch, I'm confused by the different classes and method names. It might get passed through [here](https://github.com/openmm/openmmforcefields/blob/0.12.0/openmmforcefields/generators/system_generators.py#L336) when called [here](https://github.com/search?q=repo%3AOpenFreeEnergy%2Fopenfe+createSystem&type=code), not sure if it's [set later](https://github.com/search?q=repo%3AOpenFreeEnergy%2Fopenfe%20setnonbondedcutoff&type=code)?

Ah okay I missed those are passed to that constructor. I'm used to using `createSystem`

FTR * This is, I think, accurately captured in the [SMIRNOFF example](https://github.com/openmm/openmmforcefields?tab=readme-ov-file#using-the-open-force-field-initiative-smirnoff-small-molecule-force-fields) upstream * Because `openmmforcefields` does not itself implement `ForceField.createSystem` itself, users _must_ remember those settings if using that...

I'm like 80% sure that this is not actually an issue for OpenFE as scoped here, or something that would only benefit from testing/documentation improvements - please Outside of the...

@hannahbaumann Josh Mitchell (@Yoshanuikabundi) wrote `openff.interchange.components._packmol` but I'm the point person in case you run into issues, or have any questions about why something is the way it is in...

This looks done? https://github.com/conda-forge/gufe-feedstock/pull/34/files

This URL In the README appears to just point back to the repo; hovering over the link doesn't go where I'd expect (red box edited in):  The rST is...

@dependabot rebase