dls_marco_score_ispby
dls_marco_score_ispby ia a script which runs the marco scoring tool for images passed to it in a list and writes the scores into ispyb database using ispby API.
There are two requirements for it tow work:
the connection to the database has to be established
the images for which the scoring is calculate need to be added to the database table called ispyb.BLSampleImage.
See comments in ticket VMXI-488 for more details.
Once the local database connection is established and the images added to the database the script can be used as follows:
import dls_marco_score_ispyb.score as ms
crystal_images = [‘imgae1’, ‘image2’]
ms.run(crystal_images)
Features
Run function takes up to 3 parameters. The first one is the list of image names (absolute path) and is an obligatory parameter. The second is the path to the ispyb config file (ispyb_config_path), this is a optional parameter with the default path to the local host (DEFAULT_ISPYB_CONFIG=dls_marco_score_ispby/config.conf) The third parameter is the path to the marco model, this is also an optional parameter, the default value is the path to the model packaged up with the module (DEFAULT_MODEL_DIR=dls_marco_score_ispby/savedmodel).
Installation
In order to install dls_marco_score_ispyb it do:
pip install dls_marco_score_ispyb
Note one of the modules used by dls_marco_score_ispyb - tensorflow - is a bit picky in terms of the version of pip used to install it. Make sure you have the latest version of pip installed.
Contribute
The source code of dls_marco_score_ispyb is on gitlab - Source Code: https://gitlab.diamond.ac.uk/controls/python3/dls_marco_score_ispyb
Support
If you are having issues, please contact Urszula Neuman at urszula.neuman@diamond.ac.uk
1 maintainer
Metadata
1 maintainer
Release files for dls-marco-score-ispyb 1.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 |
|---|---|---|---|---|
| dls_marco_score_ispyb-1.0.1.tar.gz | 43.1 MB | Without provenance | Details for dls_marco_score_ispyb-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dls_marco_score_ispyb-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for dls_marco_score_ispyb-1.0.1-py3-none-any.whl |
Total release size: 86.1 MB
Release files / dls_marco_score_ispyb-1.0.1.tar.gz
| Download URL | dls_marco_score_ispyb-1.0.1.tar.gz |
|---|---|
| Size | 43.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e990036e64f8696e2249cb7d2579b4d3a2010f9aefc1d4721336b016e2881571
|
|
BLAKE2b-256 checksum How to use checksums |
ec1b54d2361346bd469c37f8f418ff1082b7615f1473758926ef083d7ff5500b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/45.1.0 requests-toolbelt/0.9.1 tqdm/4.42.0 CPython/3.7.2
|
Release files / dls_marco_score_ispyb-1.0.1-py3-none-any.whl
| Download URL | dls_marco_score_ispyb-1.0.1-py3-none-any.whl |
|---|---|
| Size | 43.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4484e1ed251793d0fb1ef229630151d11baf1a90eaa72fd6dc1cc9e09097a5e8
|
|
BLAKE2b-256 checksum How to use checksums |
efdec9eb5953c9aac099793bb916518eced298c322d526cd8f5f0d2da7cad149
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/45.1.0 requests-toolbelt/0.9.1 tqdm/4.42.0 CPython/3.7.2
|
Security for dls-marco-score-ispyb 1.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.
