Expression Atlas metadata validator
This is a Python module to parse a set of MAGE-TAB files and check for compatibility with the Expression Atlas and Single Cell Expression Atlas analysis pipelines. The main validation script automatically detects the experiment type from the MAGE-TAB and runs the respective tests. Currently general checks (for bulk and single-cell experiment) as well as Single Cell Expression Atlas specific checks are supported. The controlled vocabulary for the checks are stored in the metadata-validation-config repository.
Requirements
Python 3.6, requests (tested with version 2.20.1), and GitPython (tested with version 3.1.7)
Install
Install with pip:
pip install atlas-metadata-validator
Set environment variables to fetch the validation configuration for controlled vocabulary terms:
export VALIDATION_CONFIG_REPO='https://github.com/ebi-gene-expression-group/metadata-validation-config'
export VALIDATION_CONFIG_FILE='atlas_validation_config.json'
(if not specified the above values are used as default)
Set local path where to store the validation config files, default is working dir when calling the script
export VALIDATION_CONFIG_LOCAL_PATH='/path/to/your/local/copy/'
Single-cell MAGE-TAB validator
A MAGE-TAB pre-validation module for running checks that guarantee the experiment can be processed for Single Cell Expression Atlas. The checks are mainly covering the pre-validation by https://github.com/ebi-gene-expression-group/scxa-control-workflow/blob/master/bin/sdrfToNfConf.R in order to guarantee correct processing. It reads metadata directly from the MAGE-TAB and generates a log file in the directory of the IDF file.
The checks can be invoked using the atlas_validation script with an IDF file path as input:
atlas_validation.py path/to/test.idf.txt
Options
- The SDRF file is expected in the same directory as the IDF file. If this is not the case, the location of the SDRF and other data files can be specified with
-d PATH_TO_DATAoption. - The script guesses the experiment type (sequencing, microarray or single-cell) from the MAGE-TAB. If this was unsuccessful the experiment type can be set by specifying the respective argument
-seq,-maor-sc. - The URI checks may take long time. Hence there is an option to skip these checks with
-x. - Verbose logging can be activated with
-v. - Special validation rules for HCA-imported experiments can be invoked with
-hcaoption. The validator will otherwise guess if the experiment is an HCA import based on the HCAD accession code in the ExpressionAtlasAccession field.
Metadata
Release files for atlas-metadata-validator 1.6.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 |
|---|---|---|---|---|
| atlas-metadata-validator-1.6.1.tar.gz | 11.8 kB | Without provenance | Details for atlas-metadata-validator-1.6.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| atlas_metadata_validator-1.6.1-py3-none-any.whl | Python 3 | none | any | Details for atlas_metadata_validator-1.6.1-py3-none-any.whl |
Total release size: 31.2 kB
Release files / atlas-metadata-validator-1.6.1.tar.gz
| Download URL | atlas-metadata-validator-1.6.1.tar.gz |
|---|---|
| Size | 11.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fdda1a7d7896a8fe1848cc0dfa30d8f1c1d2f2358cd6e5332bef635bf3fa29de
|
|
BLAKE2b-256 checksum How to use checksums |
b0e38d4a2722974027820963bc3f48b5ea111029142f1357616a10a8654f6b27
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/39.1.0 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/3.6.6
|
Release files / atlas_metadata_validator-1.6.1-py3-none-any.whl
| Download URL | atlas_metadata_validator-1.6.1-py3-none-any.whl |
|---|---|
| Size | 19.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9a8413e0e3cad3cb27b1b304bfc0342d06b7cb1329d0d669790456a3c9256411
|
|
BLAKE2b-256 checksum How to use checksums |
95c49eaa821f37bbb80af005b3466b713d44ebedefc3d6eb1b8b767a7132f3c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/39.1.0 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/3.6.6
|
Security for atlas-metadata-validator 1.6.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.