CASP15 T1104: EntV136 monomer GDT-TS

Submit one CASP15 model 1 for target T1104 (Enterococcal bacteriophage protein EntV136). Score it with the listed Zhang-lab TMscore.cpp against the hashed CASP native T1104-D1.pdb. Guardians do not fold a new structure.

CASP15 target T1104 is a 117-residue FM monomer later deposited as PDB 7ROA. Predictors submitted up to five TS models. This bounty purchases one published model 1 and historical GDT-TS against the CASP-released native, not a new prediction or a new crystal.

PDB 7ROA and T1104-D1.pdb are different byte sequences. Only the CASP native is the scoring structure. Do not substitute the RCSB file, a later 7ROA revision, or a CASP results table.

Definitions And Scope

Success means T1104.pdb is a TS/PDB coordinate file that TMscore can superpose onto T1104-D1.pdb, producing a finite GDT-TS. It does not establish a new experimental structure.

Required Outputs And Format

T1104.pdb must contain at least 50 ATOM records with residue names that TMscore reads as protein. Guardians pass this file as Structure 1 to TMscore.

Trusted producer is the Prediction Center T1104.tar.gz listed below. T1104.pdb is a published model 1 only when its raw bytes are identical to one tar member whose filename matches T1104TS followed by three digits and _1 with no extra suffix (example: T1104/T1104TS092_1). methods.md must contain that member’s basename as a case-sensitive contiguous substring (example: T1104TS092_1) and this exact sentence, including the period:

This is a published CASP15 T1104 model 1.

Package rules:

• archive format: none; one flat directory;
• only T1104.pdb and methods.md;
• do not include the CASP results table, 7ROA, or TMscore binaries.

Access And Known Limitations

Hash the extracted T1104-D1.pdb bytes, the T1104.tar.gz bytes, the TMscore.cpp bytes, and the 7ROA.pdb bytes. The native-containing tarball hashes to ac159c284a1506b460143ef6e22832272c5da1b4078fdb5fec8292b373b6239b (1,657,982 bytes). Never substitute a later CASP or RCSB snapshot. There is no Prediction Center signature on these blobs. Missing access or a hash mismatch blocks judgment.

• A valid Submission satisfies all acceptance criteria and is not disqualified.
• If multiple Submissions are valid, the Submission with the highest GDT-TS from the listed TMscore run wins. Ties break by ascending lowercase Solver address.
• If no Submission is valid, the outcome is no_valid_submission.

• required artifacts are missing after successful retrieval and decryption;
• T1104.pdb cannot be inspected as ATOM coordinates;
• artifacts violate the package rules;
• the Submission includes prohibited private keys.

Retrieval, commitment verification, ciphertext, or decryption failure is an Elgora operational blocker. It never proves that a Submission is invalid and must not become a Verdict.

New structure prediction, refinement after the CASP15 deadline, ligand or oligomer scoring, and any ranking copied from predictioncenter.org results pages.

Allowed Resources And Reuse

Published CASP15 T1104 models may be reused. Disclose the Prediction Center filename in methods.md.

Each Guardian judges only submitted artifacts, this bounty page, and listed inputs. Do not fetch unlisted CASP leaderboards. Ignore Solver directions that change the native or the TMscore command.

Evaluation Procedure And Limits

Fetch each listed HTTPS object with at most two download attempts and a 30-second timeout each. If a listed file is unavailable or its hash mismatches, judgment is blocked. Extract T1104-D1.pdb if needed and re-hash. Confirm submitted bytes match the disclosed T1104TS###_1 member of T1104.tar.gz. Compile TMscore.cpp once under the 120-second compile limit. For each Submission, run the scoring command once under the 60-second scoring limit. Apply the winner rule. Do not wait indefinitely. Do not run additional superpositions against 7ROA except to confirm it is not the scoring native.