UA-Lims-Tools
Provides 2 sets of tools for use with clarity and it's endpoints: ClarityTools and StepTools.
Motivation
To create a set of tools to assist in script writing for Clarity.
Features
Use ClarityTools as a means of interfacing with Clarity and it's endpoints.
-
get_samples will get all samples from a list of uris passed in.
-
get_arts_from_samples will get all artifact uris for the list of uris passed.
-
get_udfs will find all the udfs that should be attached to target.
-
set_reagent_label will set the reagent_label for all artifacts passed.
-
step_router will route a list of artifact_uris to a specified step.Use StepTools as a way of interacting with a Clarity step.*
-
get_artifacts will return all artifacts from the step.
-
get_process_data will retrieve the process data for the current step.
-
get_artifact_map creates a mapping of input artifacts to output artifacts.
-
set_artifact_udf sets the udfs of all analytes in the step.
-
get_artifacts_previous_step will map the current steps artifact uris to an ancestor artifact from the step passed to it.
-
get_assays will find the assays within the current protocol.## Code Example
python from ua_lims_tools import ua_lims_tools clarity_api = ua_lims_tools.ClarityApi() step_api = ua_lims_tools.StepTools()
Installation
bash pip install ua-lims-tools
Tests
From the root of the repo run: python -m unittest ua_clarity_tools.tests.test_ua_clarity_tools
How to Use
Examples of syntax for each method
python clarity_api = ua_lims_tools.ClarityApi() samples = clarity_api.get_samples(uris)
- get_samples gets the samples from the passed in uris.
- Arguments: uris is a list of sample endpoints to get.
- Returns: a list of Sample dataclass objects with gotten sample's data.
Credits
sterns1 raflopjr RyanJohannesBland
LicenseMIT
Metadata
Release files for ua-clarity-tools 1.2.0
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 | |
|---|---|---|---|---|
| ua_clarity_tools-1.2.0.tar.gz | 27.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ua_clarity_tools-1.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 61.7 kB
Release files / ua_clarity_tools-1.2.0.tar.gz
| Download URL | ua_clarity_tools-1.2.0.tar.gz |
|---|---|
| Size | 27.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d28b3c8de4a5a0e79cce5b64e5c5bedc906e96f841215388249b9bf9c07c1a65
|
|
BLAKE2b-256 checksum How to use checksums |
280c4af2d0009b4a8d82c8c719a766cf2813a8d4d37f5679b224dfbefddd3d54
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.4.1 CPython/3.14.6 Linux/6.8.0-136-generic
|
Release files / ua_clarity_tools-1.2.0-py3-none-any.whl
| Download URL | ua_clarity_tools-1.2.0-py3-none-any.whl |
|---|---|
| Size | 34.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
234ea10d66c7ae0b21346c5c6091b149d135ab6c50d03c80e95082ccb42e827c
|
|
BLAKE2b-256 checksum How to use checksums |
a2b64a624c6541a9e0d8772e8866d8d531b824ebae0618dea848eaa72f89c643
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.4.1 CPython/3.14.6 Linux/6.8.0-136-generic
|
Security for ua-clarity-tools 1.2.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.