nvidia-collaboration
OHSU CEDAR Cyclic IF and H&E images
Getting started
Setup python environment
source venv/bin/activate
python3 -m pip install -r requirements.txt
python3 -m pip install -r requirements-dev.txt
python3 -m pip install -e .
Run meta import with --plugin_path
The input directory:
tests/fixtures-new/
├── HandE
├── RegisteredImages
│ ├── 17633-6-Scene-001
│ ├── 18538-6-Scene-001
│ ├── 19142-6-Scene-001
│ ├── 24952-6-Scene-001
│ ├── 30411-6-Scene-001
│ ├── 31022-6-Scene-001
│ ├── 31480-6-Scene-001
│ ├── 33548-6-Scene-001
│ ├── 38592-6-Scene-001
│ ├── 48411-6-Scene-001
│ ├── 54774-4-Scene-001
│ ├── 57494-6-Scene-001
│ └── 57658-6-Scene-001
└── annotations
will produce:
gen3_util meta import dir tests/fixtures/ tmp/output --project_id aced-nvidia --plugin_path gen3_util_plugin_nvidia --remove_path_prefix tests/fixtures/
summary:
ResearchStudy:
count: 1
ResearchSubject:
count: 13
Patient:
count: 13
Specimen:
count: 13
DocumentReference:
count: 738
size: 74437
msg: OK
expected results
Output files:
tmp/output
├── DocumentReference.ndjson
├── Patient.ndjson
├── ResearchStudy.ndjson
├── ResearchSubject.ndjson
└── Specimen.ndjson
Identifiers:
$ cat tmp/output/*.ndjson | jq -rc '. as $r | .identifier[]? | [$r.resourceType, .value]'
["Patient","P1"]
["Specimen","T1"]
Run the tests
pytest tests/
Distribution
- PyPi
# update pypi
# pypi credentials - see https://twine.readthedocs.io/en/stable/#environment-variables
export TWINE_USERNAME= # the username to use for authentication to the repository.
export TWINE_PASSWORD= # the password to use for authentication to the repository.
# this could be maintained as so: export $(cat .env | xargs)
rm -r dist/
python3 setup.py sdist bdist_wheel
twine upload dist/*
Metadata
Release files for gen3-util-plugin-nvidia 0.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 | Actions |
|---|---|---|---|---|
| gen3_util_plugin_nvidia-0.0.4.tar.gz | 5.1 kB | Without provenance | Details for gen3_util_plugin_nvidia-0.0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gen3_util_plugin_nvidia-0.0.4-py3-none-any.whl | Python 3 | none | any | Details for gen3_util_plugin_nvidia-0.0.4-py3-none-any.whl |
Total release size: 10.1 kB
Release files / gen3_util_plugin_nvidia-0.0.4.tar.gz
| Download URL | gen3_util_plugin_nvidia-0.0.4.tar.gz |
|---|---|
| Size | 5.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
43528ae570ad276727777b26ab852b4d36136215dec3346b700a64a83624205e
|
|
BLAKE2b-256 checksum How to use checksums |
fd75ab4245a137a45ffa1a54e109469b62c03d00745462afefc52434b1adf863
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.12
|
Release files / gen3_util_plugin_nvidia-0.0.4-py3-none-any.whl
| Download URL | gen3_util_plugin_nvidia-0.0.4-py3-none-any.whl |
|---|---|
| Size | 5.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c255214cbbf8ac0f8b921c98a6933f6e5c11f456bee0a708fdea20b65e85fc47
|
|
BLAKE2b-256 checksum How to use checksums |
65aa7d7ea166ce410691e7f4d41e77b51bb0bfd7268e9292840e04135273e5b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.12
|
Security for gen3-util-plugin-nvidia 0.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.