Skip to content

Conversation

@atravitz
Copy link
Contributor

this is likely where users will start, so we should make sure it's up to date and clear!

@atravitz atravitz requested a review from mikemhenry January 10, 2026 00:11
@github-actions
Copy link

Colab 👈 Launch a Colab session on branch update_cli_docs

Copy link
Member

@IAlibay IAlibay left a comment

Choose a reason for hiding this comment

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

Couple of things, otherwise it looks good to me.

```

Let's assume you want to exchange the kartograf atom mapper with the LOMAP atom mapper, the Minimal Spanning Tree
Network Planner with the Maximal Network Planner and the am1bcc charge method with [OpenFF NAGL](https://docs.openforcefield.org/projects/nagl/):
Copy link
Member

Choose a reason for hiding this comment

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

Jumping into 1/2/3 seems to be missing something here. Maybe in this sentence you should something like "to achieve this, you would do the following N steps:"

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I removed the numbering, I don't think it's actually helpful.

want to create a new job script for each simulation JSON file, and the core of
that job script will be to run the `openfe quickrun` command above.
When running a complete network of simulations, it is important to ensure that the file name for the result JSON and name of the working directory are different for each leg and each repeat, otherwise you'll overwrite results.
We recommend doing this programmatically, such as the example below, which uses the fact that the JSON files in `network_setup/transformations/` have unique names, and creates directories
Copy link
Member

Choose a reason for hiding this comment

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

I don't think it's a good idea to just have the slurm example be the one that shows this off. Partly this is because a lot of folks just don't have any clue about slurm. I would re-add the bash example that demonstrates how to do this and loop over all the files.

Copy link
Contributor Author

@atravitz atravitz Jan 16, 2026

Choose a reason for hiding this comment

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

Added it back! My only concern was adding a code block and saying "but don't do this!" - seems like a way to have users end up doing it anyway 😄 . I feel this is still quite verbose for a "Quickstart", so maybe as a follow-up we can decide if we should have a bare-minimum quickstart cookbook?

Genuinely not sure the best approach, I think the current state here is worth merging though, as it's an improvement.

@atravitz atravitz requested a review from IAlibay January 16, 2026 21:45
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.

3 participants