tomogram_shift_alignment
Outline
Different tomogram generation and/or reconstruction techniques often generate tomograms with slightly different coordinates. This makes comparing the attainable resolution of the structure from these tomograms difficult. This program compares the shifts between two of the same tomogram which were constructed by different methods, and adjusts the particle coordinates of a star file to fit the new tomogram.
This is designed for RELION v4.0 star files. The generated star file should be imported into RELION 4.0 using Import Coordinates.
Installation and Usage
Requirements
- Python (3.0 or later)
Installation is carried out via:
pip install tomogram_shift_alignment
Invoke from the command line via typing:
tomogram_shift_alignment [original_tomograms] [new_tomograms] [particles_star] [tomogram_binning] [Optional: tomogram_trimming]
e.g.
tomogram_shift_alignment './tomograms' './new_tomograms' './run_data.star' 8 60
Where original_tomograms is the path to directory containing original tomograms where particles were picked. New tomograms is the path to directory containing new tomograms where the coordinates don't match. particles_star is a star file containing refinemed particle positions and angles. Tomogram binning is the binning level of the tomograms. An optional input is tomogram_trimming which is the number (in percent) to trim the tomograms by from the outer edges. This is to avoid comparison of the tomograms in empty space. Default is 40%. Use a higher value if your sample is perfectly centred in the tomogram and vice versa.
Metadata
Release files for tomogram-shift-alignment 0.0.1
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 | Actions |
|---|---|---|---|---|
| tomogram_shift_alignment-0.0.1.tar.gz | 6.3 kB | Without provenance | Details for tomogram_shift_alignment-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tomogram_shift_alignment-0.0.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for tomogram_shift_alignment-0.0.1-py2.py3-none-any.whl |
Total release size: 13.8 kB
Release files / tomogram_shift_alignment-0.0.1.tar.gz
| Download URL | tomogram_shift_alignment-0.0.1.tar.gz |
|---|---|
| Size | 6.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4780a6a8c1d3cf9d5f575923cdd0294bc397e397775854c499fedabcce4af6ce
|
|
BLAKE2b-256 checksum How to use checksums |
ec5437ea251f88f73f647da1d038d5961054739247725ae5a520b04e59668596
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/34.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.62.3 importlib-metadata/4.11.3 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.9.10
|
Release files / tomogram_shift_alignment-0.0.1-py2.py3-none-any.whl
| Download URL | tomogram_shift_alignment-0.0.1-py2.py3-none-any.whl |
|---|---|
| Size | 7.5 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
266d161749ff6f7a456410ea70b445123b70882ace9320273688d98ac7ce1d55
|
|
BLAKE2b-256 checksum How to use checksums |
dabbbe53d70b2bfd556e407deeb05fbb6d06db741b057bf9cf9e1c72cbc75b99
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/34.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.62.3 importlib-metadata/4.11.3 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.9.10
|
Security for tomogram-shift-alignment 0.0.1
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.