semantic-benchmark
Reusable Python helpers for semantic benchmark descriptions, aggregate RO-Crate creation, and RoHub provenance workflows.
Install
pip install semantic-benchmark
Install optional features with extras:
pip install "semantic-benchmark[rocrate]"
pip install "semantic-benchmark[rohub]"
pip install "semantic-benchmark[all]"
To install the latest unreleased version directly from GitHub:
pip install "semantic-benchmark[all] @ git+https://github.com/Simulation-Benchmarks/semantic-benchmark.git"
Provided Modules
semantic_benchmark.semantics: dataclasses andBenchmarkLoaderfor JSON-LD benchmark descriptions.semantic_benchmark.rohub: RoHub configuration, upload, download, annotation, and query helpers.semantic_benchmark.rocrate: aggregate RO-Crate creation and validation helpers.
semantic_benchmark.semantics is available from the base installation.
semantic_benchmark.rocrate requires the rocrate extra.
semantic_benchmark.rohub requires the rohub extra.
The root semantic_benchmark package re-exports the semantic classes for backwards compatibility.
The legacy semantic_benchmark.semantic module also remains as a compatibility shim.
Loaded numerical variables and parameters expose both unit (the original
JSON-LD value) and unit_iri (the full IRI expanded through the document's
namespace bindings). Consumers should use unit_iri when creating links.
semantic_benchmark.rohub.download_benchmark_resources(...) downloads the
software source code and annotation collection resources from a RoHub research
object. The package also exposes the download-semantic-benchmark CLI.
semantic_benchmark.rocrate.create_main_ro(...) can validate the generated
aggregate crate by passing validation_profile. The package writes the RO-Crate
zip, unpacks it to a validation directory, and runs validate_rocrate(...).
Repository-specific projects can override the packaged RoHub defaults with:
import semantic_benchmark.rohub as rohub
rohub.configure_repository_settings(
rohub_config={...},
)
1 maintainer
Metadata
1 maintainer
Release files for semantic-benchmark 0.1.7
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 | |
|---|---|---|---|---|
| semantic_benchmark-0.1.7.tar.gz | 22.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| semantic_benchmark-0.1.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 46.0 kB
Release files / semantic_benchmark-0.1.7.tar.gz
| Download URL | semantic_benchmark-0.1.7.tar.gz |
|---|---|
| Size | 22.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0eb20b0dd94fc4618a5233b14d2e4aa3ad27362530a3a21c1101291062381423
|
|
BLAKE2b-256 checksum How to use checksums |
c0d41d4ed652a485817851100cd192b00cc91c2b1259aa801bc75606b7a0a17c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.4
|
Release files / semantic_benchmark-0.1.7-py3-none-any.whl
| Download URL | semantic_benchmark-0.1.7-py3-none-any.whl |
|---|---|
| Size | 23.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9a4e78f1a60845d173805df6e6b5d0702eac4572ae9904d6e304871cab727d63
|
|
BLAKE2b-256 checksum How to use checksums |
d55e331204dffc8ad585111574b41df7cba6f0e833a988e8a72e25c1269f82a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.4
|
Security for semantic-benchmark 0.1.7
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.
