Skip to main content

A3D CLI

Accessing the Axial3D apis from the command line

Requirements

  • Python 3.7, 3.8, 3.9

Install

pip install a3d-cli

Usage

Create an order:

a3dcli create --config_file config.json --dicom_location ./path_to_dicoms/ --order-type 3DPrint --notes notes --surgery 'Surgery' --patient-gender M --patient-birth-year 2001 --catalogue-item 101 --required-date '10-08-2021'

Update an order

a3dcli upload --config_file config.json --dicom_location ./path_to_dicoms/ --order_id 1000

View help:

a3dcli --help
usage: a3dcli [-h] --config_file CONFIG_FILE --order-type [ORDER_TYPES [ORDER_TYPES ...]] --catalogue-item-id [CATALOGUE_ITEM_ID] --surgery [SURGERY] --required-date [REQUIRED_DATE]
              --patient-gender [{M,F,U}] --patient-birth-year [BIRTH_YEAR] --notes [NOTES] [--base_url BASE_URL] [--verify] [--username USERNAME] [--password PASSWORD] [--order_id ORDER_ID] [--dicom_location DICOM_LOCATION] {create,upload}

Axial3D CLI (0.2.0)

positional arguments:
  {create,upload}
                        Create Order, Upload by order id

optional arguments:
  -h, --help            show this help message and exit
  --config_file CONFIG_FILE
                        a3dcli config file
  --order-type [ORDER_TYPES [ORDER_TYPES ...]]
                        Order Types
  --catalogue-item-id [CATALOGUE_ITEM_ID]
                        Catalogue Item
  --surgery [SURGERY]   Surgery
  --required-date [REQUIRED_DATE]
                        Required Date
  --patient-gender [{M,F,U}]
                        Gender
  --patient-birth-year [BIRTH_YEAR]
                        Gender
  --notes [NOTES]       Notes
  --base_url BASE_URL   Base url of axial3D API
  --verify
  --username USERNAME   axial3D account username
  --password PASSWORD   axial3D account password
  --order_id ORDER_ID   ID of the order
  --dicom_location DICOM_LOCATION
                        Path to DICOM files

Dev requirements

Build

poetry build

Testing

Unit tests

poetry run pytest

Integration tests

poetry run pytest --integration --integration-user USERNAME --integration-password PASSWORD --integration-url https://example.com

Build

poetry build

> Building a3d-cli (0.1.0)
> - Building sdist
> - Built a3d-cli-0.1.0.tar.gz
> - Building wheel
> - Built a3d_cli-0.1.0-py3-none-any.whl

Metadata

Release files for a3d-cli 1.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for a3d-cli 1.0.0
File Size Uploaded Provenance
a3d-cli-1.0.0.tar.gz 8.9 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for a3d-cli 1.0.0
File Interpreter ABI Platform
a3d_cli-1.0.0-py3-none-any.whl Python 3 none any Details

Total release size: 18.7 kB

Release files / a3d-cli-1.0.0.tar.gz

Download URL a3d-cli-1.0.0.tar.gz
Size 8.9 kB
Tags Source
SHA-256 checksum
How to use checksums
0ab76a0345b6014e2a92b492f681c9009ca5545cf2a8aa495bbb91f8aad5cfe5
BLAKE2b-256 checksum
How to use checksums
4b111d6b27b3ea0c96a2545449a13fcf47ddad82fafb62b923a1e2aea398bd52
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via poetry/1.1.10 CPython/3.8.12 Linux/5.4.92-flatcar

Release files / a3d_cli-1.0.0-py3-none-any.whl

Download URL a3d_cli-1.0.0-py3-none-any.whl
Size 9.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
1b7d36d30f8b9ae04a676334f4b12de22708e9ee2d0fe16cb563f028cfc0f3e6
BLAKE2b-256 checksum
How to use checksums
c0a4d84b9400c8bdf87be6c6da92adaa93c7583e5d26265c4364f120610a09d1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via poetry/1.1.10 CPython/3.8.12 Linux/5.4.92-flatcar

Security for a3d-cli 1.0.0

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page