Skip to content

Update tutorial titles - #365

Open
hannahbaumann wants to merge 1 commit into
mainfrom
update-tutorial-titles
Open

hannahbaumann wants to merge 1 commit into
mainfrom
update-tutorial-titles

Conversation

@hannahbaumann

Copy link
Copy Markdown
Contributor

No description provided.

@review-notebook-app

Copy link
Copy Markdown

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

@github-actions

Copy link
Copy Markdown

Colab 👈 Launch a Colab session on branch update-tutorial-titles

@hannahbaumann hannahbaumann linked an issue Nov 17, 2026 that may be closed by this pull request
@hannahbaumann hannahbaumann self-assigned this Nov 17, 2026

@IAlibay IAlibay left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

looks a lot better! just a couple of small comments - approving early!

"<img src=\"images/OFE-color-horizontal.png\" width=\"300\"> \n",
"\n",
"# OpenFE Showcase: Relative Binding Free Energies in the TYK2 System"
"# OpenFE Showcase: RBFE for TYK2"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Do you think it's worth adding Hybrid Topology before the RBFE here? i.e. "Hybrid Topology RBFEs". Mostly thinking of this because you do that distinction for SepTop, and it might be good to do it both ways.

"metadata": {},
"source": [
"# Setting up a relative binding free energy network\n",
"# RBFE with the Python API\n",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Similarly, do you want to do "Hybrid Topology RBFEs..."?

@@ -1,4 +1,4 @@
# Binding Free Energies with the OpenFE CLI
# RBFE with the CLI

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

As per the API comment re: hybrid topology.

"metadata": {},
"source": [
"# Running a SepTop RBFE calculation\n",
"# RBFE with Separated Topologies\n",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I really like these shorter titles.

"metadata": {},
"source": [
"# Mixed Protocol Networks\n",
"# Mixed protocol networks\n",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This one I'm not sure re: semantics. Do we want capital P Protocol because it's the object or do we want lower cacse because it's referring to the ideal of a protocol?

Would defer to @atravitz here.

"metadata": {},
"source": [
"# RBFE calculations of a Protein-Membrane System\n",
"# RBFE for a membrane protein\n",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

As below, do we want to specify the method? i.e. hybrid topology

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.

Update tutorial titles

2 participants