JSON schema and validation code for HEPData submissions
Project description
JSON schema and validation code (in Python 3) for HEPData submissions
Documentation: http://hepdata-validator.readthedocs.io
Installation
If you can, install LibYAML (a C library for parsing and emitting YAML) on your machine. This will allow for the use of CSafeLoader (instead of Python SafeLoader) for faster loading of YAML files. Not a big deal for small files, but performs markedly better on larger documents.
Install from PyPI using pip:
$ pip install --user hepdata-validator
$ hepdata-validate --help
Install from GitHub (for developers) in a virtual environment:
$ git clone https://github.com/HEPData/hepdata-validator
$ cd hepdata-validator
$ python3 -m venv ~/venv/hepdata-validator
$ source ~/venv/hepdata-validator/bin/activate
(hepdata-validator) $ pip install --upgrade -e .[tests]
(hepdata-validator) $ pytest testsuite
Usage
The hepdata-validator package allows you to validate (via the command line or Python):
A full directory of submission and data files
An archive file (.zip, .tar, .tar.gz, .tgz) containing all of the files (full details)
A single .yaml or .yaml.gz file (but not submission.yaml or a YAML data file)
A submission.yaml file or individual YAML data file (via Python only, not via the command line)
The same package is used for validating uploads made to hepdata.net, therefore first validating offline can be more efficient in checking your submission is valid before uploading.
Command line
Installing the hepdata-validator package adds the command hepdata-validate to your path, which allows you to validate a HEPData submission offline.
Examples
To validate a submission comprising of multiple files in the current directory:
$ hepdata-validate
To validate a submission comprising of multiple files in another directory:
$ hepdata-validate -d ../TestHEPSubmission
To validate an archive file (.zip, .tar, .tar.gz, .tgz) in the current directory:
$ hepdata-validate -a TestHEPSubmission.zip
To validate a single YAML file in the current directory:
$ hepdata-validate -f single_yaml_file.yaml
Usage options
$ hepdata-validate --help
Usage: hepdata-validate [OPTIONS]
Offline validation of submission.yaml and YAML data files. Can check either
a directory, an archive file, or the single YAML file format.
Options:
-d, --directory TEXT Directory to check (defaults to current working
directory)
-f, --file TEXT Single .yaml or .yaml.gz file (but not submission.yaml
or a YAML data file) to check - see https://hepdata-
submission.readthedocs.io/en/latest/single_yaml.html.
(Overrides directory)
-a, --archive TEXT Archive file (.zip, .tar, .tar.gz, .tgz) to check.
(Overrides directory and file)
--help Show this message and exit.
Python
Validating a full submission
To validate a full submission, instantiate a FullSubmissionValidator object:
from hepdata_validator.full_submission_validator import FullSubmissionValidator, SchemaType
full_submission_validator = FullSubmissionValidator()
# validate a directory
is_dir_valid = full_submission_validator.validate(directory='TestHEPSubmission')
# or uncomment to validate an archive file
# is_archive_valid = full_submission_validator.validate(archive='TestHEPSubmission.zip')
# or uncomment to validate a single file
# is_file_valid = full_submission_validator.validate(file='single_yaml_file.yaml')
# if there are any error messages, they are retrievable through this call
full_submission_validator.get_messages()
# the error messages can be printed for each file
full_submission_validator.print_errors('submission.yaml')
# the list of valid files can be retrieved via the valid_files property, which is a
# dict mapping SchemaType (e.g. SUBMISSION, DATA, SINGLE_YAML, REMOTE) to lists of
# valid files
full_submission_validator.valid_files[SchemaType.SUBMISSION]
full_submission_validator.valid_files[SchemaType.DATA]
# full_submission_validator.valid_files[SchemaType.SINGLE_YAML]
# if a remote schema is used, valid_files is a list of tuples (schema, file)
# full_submission_validator.valid_files[SchemaType.REMOTE]
# the list of valid files can be printed
full_submission_validator.print_valid_files()
Validating individual files
To validate submission files, instantiate a SubmissionFileValidator object:
from hepdata_validator.submission_file_validator import SubmissionFileValidator
submission_file_validator = SubmissionFileValidator()
submission_file_path = 'submission.yaml'
# the validate method takes a string representing the file path
is_valid_submission_file = submission_file_validator.validate(file_path=submission_file_path)
# if there are any error messages, they are retrievable through this call
submission_file_validator.get_messages()
# the error messages can be printed
submission_file_validator.print_errors(submission_file_path)
To validate data files, instantiate a DataFileValidator object:
from hepdata_validator.data_file_validator import DataFileValidator
data_file_validator = DataFileValidator()
# the validate method takes a string representing the file path
data_file_validator.validate(file_path='data.yaml')
# if there are any error messages, they are retrievable through this call
data_file_validator.get_messages()
# the error messages can be printed
data_file_validator.print_errors('data.yaml')
Optionally, if you have already loaded the YAML object, then you can pass it through as a data object. You must also pass through the file_path since this is used as a key for the error message lookup map.
from hepdata_validator.data_file_validator import DataFileValidator
import yaml
file_contents = yaml.safe_load(open('data.yaml', 'r'))
data_file_validator = DataFileValidator()
data_file_validator.validate(file_path='data.yaml', data=file_contents)
data_file_validator.get_messages('data.yaml')
data_file_validator.print_errors('data.yaml')
For the analogous case of the SubmissionFileValidator:
from hepdata_validator.submission_file_validator import SubmissionFileValidator
import yaml
submission_file_path = 'submission.yaml'
# convert a generator returned by yaml.safe_load_all into a list
docs = list(yaml.safe_load_all(open(submission_file_path, 'r')))
submission_file_validator = SubmissionFileValidator()
is_valid_submission_file = submission_file_validator.validate(file_path=submission_file_path, data=docs)
submission_file_validator.print_errors(submission_file_path)
Schema Versions
When considering native HEPData JSON schemas, there are multiple versions. In most cases you should use the latest version (the default). If you need to use a different version, you can pass a keyword argument schema_version when initialising the validator:
submission_file_validator = SubmissionFileValidator(schema_version='0.1.0')
data_file_validator = DataFileValidator(schema_version='0.1.0')
Remote Schemas
When using remotely defined schemas, versions depend on the organization providing those schemas, and it is their responsibility to offer a way of keeping track of different schema versions.
The JsonSchemaResolver object resolves $ref in the JSON schema. The HTTPSchemaDownloader object retrieves schemas from a remote location, and optionally saves them in the local file system, following the structure: schemas_remote/<org>/<project>/<version>/<schema_name>. An example may be:
from hepdata_validator.data_file_validator import DataFileValidator
data_validator = DataFileValidator()
# Split remote schema path and schema name
schema_path = 'https://scikit-hep.org/pyhf/schemas/1.0.0/'
schema_name = 'workspace.json'
# Create JsonSchemaResolver object to resolve $ref in JSON schema
from hepdata_validator.schema_resolver import JsonSchemaResolver
pyhf_resolver = JsonSchemaResolver(schema_path)
# Create HTTPSchemaDownloader object to validate against remote schema
from hepdata_validator.schema_downloader import HTTPSchemaDownloader
pyhf_downloader = HTTPSchemaDownloader(pyhf_resolver, schema_path)
# Retrieve and save the remote schema in the local path
pyhf_type = pyhf_downloader.get_schema_type(schema_name)
pyhf_spec = pyhf_downloader.get_schema_spec(schema_name)
pyhf_downloader.save_locally(schema_name, pyhf_spec)
# Load the custom schema as a custom type
import os
pyhf_path = os.path.join(pyhf_downloader.schemas_path, schema_name)
data_validator.load_custom_schema(pyhf_type, pyhf_path)
# Validate a specific schema instance
data_validator.validate(file_path='pyhf_workspace.json', file_type=pyhf_type)
The native HEPData JSON schema are provided as part of the hepdata-validator package and it is not necessary to download them. However, in principle, for testing purposes, note that the same mechanism above could be used with:
schema_path = 'https://hepdata.net/submission/schemas/1.1.0/'
schema_name = 'data_schema.json'
and passing a HEPData YAML data file as the file_path argument of the validate method.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
File details
Details for the file hepdata_validator-0.3.2.tar.gz
.
File metadata
- Download URL: hepdata_validator-0.3.2.tar.gz
- Upload date:
- Size: 25.0 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/3.6.0 importlib_metadata/4.8.2 pkginfo/1.8.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.9
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 0677b6042db87b0ea92724d51cda51538924b2d077e7fb1529992d0728cfdc6d |
|
MD5 | b45ec2feac82c1467d6de3cb28751c09 |
|
BLAKE2b-256 | 4a8beadccc4f6b143e7c59608a0b4f6224224e2185ed3bc80ec106ef8d86a758 |
File details
Details for the file hepdata_validator-0.3.2-py2.py3-none-any.whl
.
File metadata
- Download URL: hepdata_validator-0.3.2-py2.py3-none-any.whl
- Upload date:
- Size: 40.8 kB
- Tags: Python 2, Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/3.6.0 importlib_metadata/4.8.2 pkginfo/1.8.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.9
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | f0eb30ce3120029928a96d7b5239fd090d09ba76f67937aca57eb87c1a341ff1 |
|
MD5 | ac0cbf4271aa687c68988da35c6d648f |
|
BLAKE2b-256 | 60f2ca6ceb76b11e600944c57835632e308efa5fc2515fe068c63aee609f498d |