TL;DR
The operations table for every predicted complex: filter, reopen, select completed jobs, export CSV/PDB/contact artifacts, and compare epitope fingerprints.
Use it / Skip it
Interface creates the jobs; Interface Jobs is where a team manages them at scale.
Use when
You need to find an old job, export many completed jobs, delete failed clutter, or compare contact-residue fingerprints.
Don't use for
Do not use it to launch new predictions; launch from Interface or CAR Interface Assessment.
Inputs
- Search
- Job name or ID.
- Status filter
- all, done, running, queued, failed.
- Selection
- Only completed jobs can be selected for artifact export.
Outputs
- CSV exports
- Analysis metrics for selected or all completed jobs.
- ZIP export
- PDBs plus contacts and summary files for selected jobs.
- Comparison
- Contact-fingerprint comparison for selected completed jobs.
Walkthrough
1. Filter by name, ID, status, or backend to narrow the table
Filter by name, ID, status, or backend to narrow the table.
2. Open a row to return to the full Interface viewer
Open a row to return to the full Interface viewer.
3. Select completed jobs when you need artifacts
Select completed jobs when you need artifacts.
4. Export analysis CSV or ZIP for project packets
Export analysis CSV or ZIP for project packets.
5. Use compare actions for epitope/contact similarity review
Use compare actions for epitope/contact similarity review.
Under the hood
- Uses listInterfaceJobs and deleteInterfaceJob client helpers.
- Artifact endpoints are available only when a job is completed and analysis exists.
Worked example
Pitfalls
- Failed jobs can be deleted from the table, but that does not fix the underlying sequence/backend issue.
- Selected export skips incomplete jobs by design.
- Historical backend labels are normalized; do not infer old infrastructure from the display name alone.