Repository navigation
Update cookbook titles for docs display #351
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
1f4cd32
7a19ea8
d25149f
174fe74
42db0ad
e0aa03d
628f240
0166207
2041138
9b2c2fa
3f9ff11
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -4,7 +4,7 @@ | |
| "cell_type": "markdown", | ||
| "metadata": {}, | ||
| "source": [ | ||
| "# BespokeFit: Using bespoke force field parameters with OpenFE protocols\n", | ||
| "# Use bespoke parameters with BespokeFit\n", | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I notice you're changing the text away from present participle - is this intentional?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, this was intentional, mostly to shorten titles, and also because if now it's How-to ... it works better I thought. But if others think the other version is better, I can also switch to that.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ah I see, so it's "How to X"? That makes a lot of sense, thanks! |
||
| "\n", | ||
| "This tutorial gives a step-by-step guide on the use of OpenFF-BespokeFit generated force field parameters with OpenFE protocols. Here we will focus on relative\n", | ||
| "binding free energy (RBFE) calculations, but this strategy can be used with any OpenMM-based OpenFE protocol. \n", | ||
|
|
@@ -130,9 +130,10 @@ | |
| "cell_type": "markdown", | ||
| "metadata": {}, | ||
| "source": [ | ||
| "# Recap\n", | ||
| "## Recap\n", | ||
| "\n", | ||
| "To recap the workflow can be reduced to the following steps:\n", | ||
| "\n", | ||
| "So to recap the workflow can be reduced to the following steps:\n\n", | ||
| "- Plan the RBFE network\n", | ||
| "- Create a single SMIRNOFF style force field with all of the bespoke parameters for the network using the BespokeFit `combine` CLI\n", | ||
| "- Store the force field as a string in the OpenFE protocol under the `settings.forcefield_settings.small_molecule_forcefield` field\n", | ||
|
|
@@ -144,7 +145,7 @@ | |
| ], | ||
| "metadata": { | ||
| "kernelspec": { | ||
| "display_name": "asapdiscovery", | ||
| "display_name": "Python 3 (ipykernel)", | ||
| "language": "python", | ||
| "name": "python3" | ||
| }, | ||
|
|
@@ -158,9 +159,9 @@ | |
| "name": "python", | ||
| "nbconvert_exporter": "python", | ||
| "pygments_lexer": "ipython3", | ||
| "version": "3.11.6" | ||
| "version": "3.13.14" | ||
| } | ||
| }, | ||
| "nbformat": 4, | ||
| "nbformat_minor": 2 | ||
| "nbformat_minor": 4 | ||
| } | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -5,7 +5,7 @@ | |
| "id": "035c0099-6892-4ed2-b0d6-80b1c247c1e7", | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should it be -> Plan a Reply via ReviewNB
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Done! |
||
| "metadata": {}, | ||
| "source": [ | ||
| "# Planning a Ligand Network" | ||
| "# Plan a `LigandNetwork`" | ||
| ] | ||
| }, | ||
| { | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -10,7 +10,7 @@ | |
| "tags": [] | ||
| }, | ||
| "source": [ | ||
| "# Visualizing Ligand Networks" | ||
| "# Visualize a `LigandNetwork`" | ||
| ] | ||
| }, | ||
| { | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we could hit part of OpenFreeEnergy/openfe#2283 with this change as well and drop bespokefit from the title? I can then update the introduction in another PR to say BespokeFit is just one example of the input files we can use.
What about "Using custom force field parameters" as a more general title?
Reply via ReviewNB
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the idea of changing the title and the explanation to make it more broad, but I would suggest we can maybe change the title together with the text in a follow up PR?