BILN → pyPept → generated conformer

Five proteins, five explicit pyPept output receipts.

FoldSense uses pyPept for the BILN-to-chemical-graph/generated-3D representation lane. Each judge protein must have its own generated PDB and standalone 3D view before the pyPept gate is PASS. These outputs are generated conformers—not experimental structures and not molecular-dynamics trajectories.

One bounded chemistry transformation per protein window.

BILN→pinned pyPept→RDKit graph / depiction→generated PDB→FoldSense 2D/3D renderers

The generation manifest retains pyPept version, upstream commit, input BILN, return code, exact PDB/PNG/HTML hashes, byte counts and failed entries. Failure is not replaced with an experimental PDB.

Open the exact artifact used by the pyPept viewer.

Loading /structures/manifest.json…

Generated representation and experimental context stay separate.

The main Molecular Reader can switch between a pyPept-generated fragment and a cited experimental PDB context. The UI labels the active source explicitly; no generated conformer is promoted to experimental evidence.