ewoksid22
Data processing workflows for ID22
Getting started
Example of using the command line scripts directly (needs access to /data/id22/inhouse/):
./examples/rebinsum.sh
Example of defining and executing an HDF5 to SPEC conversion workflow (needs access to /data/id22/inhouse/):
ewoks execute examples/convert.json
Example of defining and executing a ROI collection rebin+sum workflow (needs access to /data/id22/inhouse/):
ewoks execute examples/rebinsum.json
Installation
pip install multianalyzer@git+https://github.com/kif/multianalyzer.git@main
pip install ewoksid22
The following command line scripts are installed:
id22sumepy: python wrapper forid22sumeandid22sumalleid22sume: fortran programid22sumalle: fortran programzingit: awk program
Documentation
Metadata
Release files for ewoksid22 0.1.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 |
|---|---|---|---|---|
| ewoksid22-0.1.1.tar.gz | 2.1 MB | Without provenance | Details for ewoksid22-0.1.1.tar.gz |
Release files / ewoksid22-0.1.1.tar.gz
| Download URL | ewoksid22-0.1.1.tar.gz |
|---|---|
| Size | 2.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eb529b29149b0dbcda7a47929102530a8d417275963d2aed7d742542f267f6ca
|
|
BLAKE2b-256 checksum How to use checksums |
4ca8e71eda4e6ca8705531a5b7d6d7acc880e0b6a408edf57f9aa147d1163c7c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Security for ewoksid22 0.1.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.