Abstract
pacscopy is a simple plugin that copies data from open storage to create a new top level ChRIS Feed. It’s core utility is in demonstrating how to create a largely trivial FS plugin/app for the ChRIS system.
Synopsis
python pacscopy.py \
[-v <level>] [--verbosity <level>] \
[-d <dir>] [--dir <dir>] \
[--version] \
[--man] \
[--meta] \
<outputDir>
Run
This plugin can be run in two modes: natively as a python package or as a containerized docker image.
Using PyPI
To run from PyPI, simply do a
pip install pacscopy
and run with
pacscopy.py --man /tmp /tmp
to get inline help. To copy from one directory to another, simply do
pacscopy.py --dir /some/input/directory /destination/directory
Using docker run
To run using docker, be sure to assign an “input” directory to /incoming and an output directory to /outgoing. Make sure that the $(pwd)/out directory is world writable!
Now, prefix all calls with
docker run --rm -v $(pwd)/out:/outgoing \
fnndsc/pl-pacscopy pacscopy.py \
Thus, getting inline help is:
docker run --rm -v $(pwd)/in:/incoming -v $(pwd)/out:/outgoing \
fnndsc/pl-pacscopy pacscopy.py \
--man \
/outgoing
Examples
Copy a directory dataset/MPRAGE to the output directory. If called from ChRIS, the input directory spec refers to a location in openstorage, otherwise it is interpreted as a system directory spec.
mkdir out
docker run --rm -v $(pwd)/in:/incoming -v $(pwd)/out:/outgoing \
fnndsc/pl-pacscopy pacscopy.py \
--dir dataset/MPRAGE \
/outgoing
Metadata
Release files for pacscopy 1.0.4
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 | |
|---|---|---|---|---|
| pacscopy-1.0.4.tar.gz | 3.6 kB | Without provenance | Details |
Release files / pacscopy-1.0.4.tar.gz
| Download URL | pacscopy-1.0.4.tar.gz |
|---|---|
| Size | 3.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aca9d17553e083ed9d7686a66b0c4b005963dcec0ccafe6e5a443bd9f15b0484
|
|
BLAKE2b-256 checksum How to use checksums |
d8c9b1187c93d81f677a274a8f742065caaf16da92ee50e514723455243454b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.1 CPython/3.7.3
|
Security for pacscopy 1.0.4
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.