Skip to content

Add SepTop BACE dataset#116

Open
hannahbaumann wants to merge 15 commits into
plan_septopfrom
add_bace_septop
Open

Add SepTop BACE dataset#116
hannahbaumann wants to merge 15 commits into
plan_septopfrom
add_bace_septop

Conversation

@hannahbaumann
Copy link
Copy Markdown
Contributor

No description provided.

@hannahbaumann hannahbaumann changed the base branch from main to plan_septop March 18, 2026 15:14
@hannahbaumann hannahbaumann requested a review from jthorton April 15, 2026 12:29
Comment on lines +94 to +95
for edge in network.edges:
edge.annotations.update(network_provenance)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Unfortunately, annotations is a copy of the data so this doesn't get saved into the network, you can make a new set of edges using new_edge = edge.with_annotations(network_provenance) though.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Thanks, fixed this!

Copy link
Copy Markdown
Contributor

@jthorton jthorton left a comment

Choose a reason for hiding this comment

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

Just one change needed for the lomap planning script to make sure the generation details are saved and then we just need to generate the network again and its good to go. Thanks for adding this one @hannahbaumann !

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.

Is it intentional that all systems have the tag "ross"? I'm assuming not. I would propose we update the CI so that if the first list is empty then none of the systems get that tag (opposite of current behavior where all of them do), and then add system names to the second list as exceptions to add the tag to those systems.

Copy link
Copy Markdown
Collaborator

@jaclark5 jaclark5 left a comment

Choose a reason for hiding this comment

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

Other than a proper reference to exp.csv I think this is good to go!

# tag each entry with the source, currently we link to the aggregated reference data but this should be changed if we refine it in future.
baumann_et_al_doi = "https://doi.org/10.1021/acs.jctc.3c00282"
# load the ref data from the industry benchmark results stored on github
ref_dg_data = pd.read_csv("/Users/hannahbaumann/test_septop/bace/exp.csv")
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.

Instead of hard coding the path on your computer, maybe this should be (a) an input argument or (b) hardcode a wget from your GitHub repo

("cofactor", ["cofactors.sdf"], []),
("bfe", ["experimental_binding_data.json"], []),
("sfe", ["experimental_solvation_free_energy_data.json"], ["mnsol_neutral"]),
("ross", [], []),
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.

I double checked this, and this is correct. It acknowledges that the tag exists but doesn't have any rules on how it should be used. Thus, it can catch typos like accidentally manually writing the tag as roos for example

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