PDB Biological Assembly: Show the Right Protein Complex

For a figure of a functional protein complex, start by checking the PDB biological assembly rather than assuming the first downloaded structure contains the right number of subunits. Compare the entry’s asymmetric unit with its assembly description, choose the relevant assembly identifier and verify the displayed chain instances before styling. The asymmetric unit may contain part of a complex, one complete complex or several complexes. A beautiful render can therefore communicate the wrong molecular object even when every displayed atom came from an experimental structure.

This guide uses trout hemoglobin entry 1OUT to make that check concrete. Its deposited protein coordinates contain two chains, whereas biological assembly 1 is a four-subunit complex. You will learn a documented ChimeraX procedure and a short audit to attach to a figure or movie. The procedure was checked against current official documentation, but it was not executed locally in ChimeraX. The editorial images are conceptual illustrations, not coordinate-derived renders of 1OUT.

Use UCSF ChimeraX, an internet connection for fetching the structure and a writable folder for your session. The official release news lists version 1.12 as the current production release on October 7, 2026. Save any existing work and start a fresh session so the first structure receives model number #1. Keep the Log and Models tools available; their records are more useful than judging a complex by its silhouette.

Open the RCSB entry for 1OUT before opening the structure. It is trout hemoglobin I from Oncorhynchus mykiss, studied by X-ray diffraction. RCSB lists assembly 1 as author assigned with A2B2 stoichiometry: two copies of each of two protein types. This is a trout example, so do not caption its coordinates as human hemoglobin. The entry currently reports version 1.5, revised in August 2026; record the downloaded version or retrieval date with your project.

Write the planned figure claim first: “This view shows the deposited model’s assigned four-subunit assembly.” That narrow claim makes the expected result explicit without turning the picture into evidence for an association pathway or a physiological state you have not checked.

The asymmetric unit is the distinct part of a crystal structure from which crystallographic symmetry generates the repeating crystal. The biological assembly is the proposed or established functional grouping. These concepts answer different questions. The PDB-101 assembly guide illustrates 1OUT as a case where symmetry supplies the other half of the complex; it also shows examples where an asymmetric unit already contains a complete assembly or contains multiple assemblies.

Do not repair every small-looking structure by duplicating it. A monomer can be the relevant biological assembly, and two neighboring molecules in a crystal need not form a functional dimer. Inspect the assigned assembly and its supporting context before deciding that a larger object is more biologically useful.

For a teaching slide, use one compact complex as the main subject and describe crystal neighbors separately. A repeated packing view can explain how coordinates are organized, but should not visually imply that all nearby proteins are one active machine. The choice is about the claim your picture carries, not about making the scene fuller.

The open documentation describes identifier fetching; the sym documentation describes assemblies stored in mmCIF. In a fresh session, enter the commands below one at a time. Inspect the Log after sym #1 before continuing. The first command uses ChimeraX’s default mmCIF fetch, which carries the assembly information.

The assembly operation creates a new model and hides the original rather than closing it. Identify that new model in Models before further selections. The display commands provide a simple overview; they do not establish chain identity. The expected protein result for 1OUT assembly 1 is four subunits, representing two copies of each protein entity.

An alternative is open 1out from rcsb_bio maxAssemblies 1, which fetches the first available assembly directly. Use this as a separate route in a fresh session, not an additional step after generating the complex. On entries with alternatives, inspect the identifier you actually fetched; limiting the number of downloaded assemblies does not evaluate their biological relevance.

Stoichiometry means the number of each component in a complex. For this worked example, the audit target is A2B2. Two protein entities describe two distinct component types; four chain instances describe their copies in the selected assembly. The RCSB identifier guide distinguishes entities from instances and explains author-assigned versus archive-assigned chain identifiers.

Inspect the assembled model in Models and the available chain information. Match its protein components to the entry’s composition, keeping copied instances distinguishable even when they share a sequence. Do not count visible lobes as a substitute for chain records: occlusion can hide one subunit, and one chain can have several domains. Likewise, color bychain is an inspection aid, not a certificate that the composition is right.

Treat cofactors, solvent and non-protein components separately from the protein-subunit count. If you hide them for clarity, record that choice without calling them absent from the deposited structure. Once the count and identity are settled, choose a representation for the question. Our surface-versus-ribbon guide explains what each view emphasizes.

When a displayed complex does not match the entry, first inspect what is open and visible. Repeating a command can leave more than one generated model in the session. Close the redundant derivative after identifying it, or return to a fresh saved starting point. Do not delete chains from your only original file to make the count look right.

If sym #1 lists no assembly, confirm that #1 is the intended model and that the input retained assembly metadata. Fetch the entry again in a fresh session using the default mmCIF route. A stripped coordinate file may not contain the instructions you expected. Compare the downloaded file with the entry record before inventing your own arrangement.

For large assemblies, distinguish graphical copies from full atomic copies. ChimeraX uses graphical clones for efficient display of sufficiently large assemblies; analyses requiring atomic coordinates need full copies. That distinction matters when a scene looks complete but the analysis tools do not have the equivalent coordinate objects. Follow the current sym documentation for the intended operation.

Assembly coordinates support a spatial illustration of the chosen model. A camera orbit makes that spatial relationship easier to inspect, but it does not show proteins assembling in real time. Moving subunits together creates an association story that requires additional evidence about the process, even when the final arrangement matches the structural model.

For a paper or lab meeting, keep the audited coordinates fixed while changing the view. If you make an exploded explanation, describe the separation as a display operation and return to the unchanged reference arrangement. Do not attach kinetic units to presentation timing or use a smooth transition to imply a measured route.

This boundary is useful when briefing an animator. Supply the coordinate-based reference view, the assembly record and a sentence describing which movements are explanatory choices. A reviewer can then check the endpoint independently of the animation’s pacing. The broader PDB-to-animation guide provides context for building a story around a structure.

A short assembly explanation can use four shots without inventing a binding trajectory. Keep the scientific object unchanged through the sequence and reserve camera movement for revealing information. The shot plan below is an editorial example, with no measured durations or inferred molecular motion.

Use the actual entry identifier and a clear caption in a coordinate-based movie. If a separate animation uses simplified surfaces, introduce it as a conceptual teaching view. Keep two component types visually distinguishable and check that copies remain present through every transition. A useful learner task is to count the copies before reading the caption, then explain why two distinct types do not mean only two subunits.

For documented ChimeraX recording and export steps, use the existing movie tutorial. Prepare the assembly audit first so that recording captures the intended complex from the start.

Save a ChimeraX session with a descriptive .cxs filename using the save command. Retain the original coordinate file and your project note with it. A session records the visualization context; the note explains the biological choice to someone who does not use your software.

For this example, a concise note can read: “Trout hemoglobin I, PDB 1OUT, biological assembly 1, retrieved October 7, 2026. Protein composition A2B2. Assembly generated from the entry’s mmCIF instructions. Camera movement is for inspection; no association pathway is represented.” Add any hidden components, clipping or representation changes that matter to interpreting your actual figure.

Before handoff, review the final output rather than only the working viewport. Check that all expected subunits remain visible, the caption names the correct organism and assembly, and color has not become the sole identity cue. Ask a colleague to describe the grouping without your explanation. If their answer differs from the intended claim, revise the framing or caption before adding visual detail.