Protein Data Bank (PDB) files often have a number of problems that must be fixed before they can be used in a molecular dynamics simulation. The details vary depending on how the file was generated. Here are some of the most common ones:
If the structure was generated by X-ray crystallography, most or all of the
hydrogen atoms will usually be missing.
There may also be missing heavy atoms in flexible regions that could not be clearly resolved from the electron density. This may include anything from a few atoms at the end of a sidechain to entire loops.
Many PDB files are also missing terminal atoms that should be present at the ends of chains.
The file may include nonstandard residues that were added for crystallography purposes, but are not present in the naturally occurring molecule you want to simulate.
The file may include more than what you want to simulate. For example, there may be salts, ligands, or other molecules that were added for experimental purposes. Or the crystallographic unit cell may contain multiple copies of a protein, but you only want to simulate a single copy.
There may be multiple locations listed for some atoms.
If you want to simulate the structure in explicit solvent, you will need to add a water box surrounding it.
PDBFixer can fix all of these problems for you in a fully automated way. You simply select a file, tell it which problems to fix, and it does everything else.
Metadata
Release files for pdbfixer 1.12.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pdbfixer-1.12.0.tar.gz | 665.9 kB | Without provenance | Details |
Release files / pdbfixer-1.12.0.tar.gz
| Download URL | pdbfixer-1.12.0.tar.gz |
|---|---|
| Size | 665.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
82e54074b33eb00270e9a439c8633fcf82cd3ab7a36561b01425a260c0fc4143
|
|
BLAKE2b-256 checksum How to use checksums |
dabd394c3185e4b9fbacf803651a374e99e597d3411d316784f8ea6d8fc17af5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.12
|
Security for pdbfixer 1.12.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.