LbProdRun
LbProdRun provides a stable interface that can be used by LHCbDIRAC for configuring and launching LHCb's various software applications.
In order to generate simulated data and reproduce legacy reprocessing it is necessary for LHCbDIRAC to be able to configure applications dating back to 2011.
Previously this was handled by the ProdConf data package however changes to the Run 3 software stack caused ProdConf is not longer generic enough.
Instead LbProdRun provides a CLI application (lb-prod-run) which is passed a single JSON file as it's argument.
This file contains all of the required information to run an LHCb application and hides the details of configuring the application away from LHCbDIRAC.
Usage
$ lb-prod-run prodspec_DaVinci_00145918_00000004_1.json
# Check the configuration is valid and print the command that would be ran
$ lb-prod-run prodspec_DaVinci_00145918_00000004_1.json --dry-run --verbose
Version 1 schema
The most minimal configuration file that can be passed to version 1 of the schema is:
{"spec_version": 1,
"application": {"name": "DaVinci", "version": "v45r8"},
"options": {"files": ["$APPCONFIGOPTS/my-options-file.py"]},
"output": {"prefix": "00145918_00000004_1", "types": ["d02hhll.strip.mdst"]}}
When parsing this is padded with the default values:
{"application": {"binary_tag": "best",
"data_pkgs": [],
"event_timeout": null,
"name": "DaVinci",
"number_of_processors": 1,
"version": "v45r8"},
"db_tags": {"conddb_tag": null, "dddb_tag": null, "dq_tag": null},
"input": {"files": null,
"first_event_number": null,
"n_of_events": -1,
"run_number": null,
"tck": null,
"xml_file_catalog": null,
"xml_summary_file": null},
"options": {"files": ["$APPCONFIGOPTS/my-options-file.py"],
"format": null,
"gaudi_extra_options": null,
"processing_pass": null},
"output": {"histogram_file": null,
"prefix": "00145918_00000004_1",
"types": ["d02hhll.strip.mdst"]}}
Metadata
Release files for LbProdRun 1.12.6
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 |
|---|---|---|---|---|
| lbprodrun-1.12.6.tar.gz | 855.4 kB | Without provenance | Details for lbprodrun-1.12.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lbprodrun-1.12.6-py3-none-any.whl | Python 3 | none | any | Details for lbprodrun-1.12.6-py3-none-any.whl |
Total release size: 879.2 kB
Release files / lbprodrun-1.12.6.tar.gz
| Download URL | lbprodrun-1.12.6.tar.gz |
|---|---|
| Size | 855.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c0c45bf78108f96cb2df8a1b11e72ea00ac48e75746acc5885a4018fd66b9284
|
|
BLAKE2b-256 checksum How to use checksums |
a237ca8f65b5ba916d9861400e58593d2a0cdc36c47d753d0bb48a54d67effc8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / lbprodrun-1.12.6-py3-none-any.whl
| Download URL | lbprodrun-1.12.6-py3-none-any.whl |
|---|---|
| Size | 23.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
327ebc16d53d611c82239329b726e10718e4b23e1d0e8e356fb0cadbe3932159
|
|
BLAKE2b-256 checksum How to use checksums |
c5f62a28f640cc88e76c1d26bf87eb7590ff6e15718989bc3f23d88d294b21ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for LbProdRun 1.12.6
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.