Add RFdiffusion-to-LigandMPNN workflow and direct app-backed nodes#27
Merged
Conversation
…llucinated positions
…uce orchestrator abstraction layer
…prevent duplicates Previous code would save inline bytes into two files, and save base64 bytes in the ledger sqlite3 table.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
rfd_ligandmpnnworkflow to fan out RFdiffusion trajectories/designs and run LigandMPNN design nodes in parallel for each generated scaffold.VolumePathstorage.--dry-runDAG printing, compact DAG labels, workflow CLI coverage, and updated app/workflow agent docs and skills.Details
.trb/PDB outputs so fixed contig residues are not passed as designable positions.