You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After a structure prediction completes, the pipeline should run DSSP (Dictionary of Protein Secondary Structure) to assign secondary structure elements (helices, sheets, coils) to the predicted model. This annotation would be available in the output alongside the structure file, enabling downstream analysis and richer reports.
Current state
DSSP is used internally by protein_compare during report generation (SecondaryStructureAnalyzer via BioPython's DSSP wrapper), but only for the HTML report
The secondary structure assignment is not persisted as a standalone output artifact
The BV-BRC pipeline does not run DSSP as an explicit step — it is buried inside report generation
Proposed change
Add DSSP as a discrete post-prediction work step in the pipeline, after structure prediction and before report generation:
Description
After a structure prediction completes, the pipeline should run DSSP (Dictionary of Protein Secondary Structure) to assign secondary structure elements (helices, sheets, coils) to the predicted model. This annotation would be available in the output alongside the structure file, enabling downstream analysis and richer reports.
Current state
protein_compareduring report generation (SecondaryStructureAnalyzervia BioPython'sDSSPwrapper), but only for the HTML reportProposed change
Add DSSP as a discrete post-prediction work step in the pipeline, after structure prediction and before report generation:
This would:
mkdsspon the predicted model (model_1.pdb or model_1.cif)predictions/model_1.dssp)Benefits
Implementation notes
mkdsspis already installed in the production SIF (required by protein_compare)App-PredictStructure.plas a step between prediction and report, or integrated into the Python normalizerPriority
Low — enhancement, not blocking current functionality.