Skip to content
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

Log disulfide bridges #625

Merged
merged 6 commits into from
Oct 29, 2024
Merged

Log disulfide bridges #625

merged 6 commits into from
Oct 29, 2024

Conversation

csbrasnett
Copy link
Collaborator

Small useful feature to write where disulfide bridges have actually been found as per #620. Can't see any effect on time. message might need some work.

- doesn't seem to assert correctly atm but not clear why, the link gets found correctly
Copy link
Member

@pckroon pckroon left a 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, but I think you can already achieve this by adding a [ info ] section to the link:

;; Cystein bridge
[ link ]
resname "CYS"
[ constraints ]
SC1 >SC1 1 0.24 {"comment": "Disulfide bridge"}
[ features ]
disulfide
[ info ]
Disulfide bridge found between residues {SC1['chain']}-{SC1['resname']}{SC1['resid']} and {>SC1['chain']}-{>SC1['resname']}{>SC1['resid']}

Note that this is an educated guess and YMMV

@csbrasnett
Copy link
Collaborator Author

Nice, that worked with a small adjustment thanks!

Copy link
Member

@pckroon pckroon left a comment

Choose a reason for hiding this comment

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

Awesome. I love preempting requests this way.
Also, could you add it to the other force fields as well?

Copy link
Member

@pckroon pckroon left a comment

Choose a reason for hiding this comment

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

LGTM!

@pckroon pckroon merged commit 8a0a91c into marrink-lab:master Oct 29, 2024
9 of 10 checks passed
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.

2 participants