Rhino Federated Computing SDK (Rhino SDK)
Programmatic interface for interacting with the Rhino Federated Computing Platform.
Example Usage
Please see the sample notebook files provided to you by the Rhino Team for additional use cases.
Create a session
import rhino_health
my_username = "rhino_user@rhinohealth.com" # Replace me
my_password = "ASecurePasswordYouSet321" # Replace me
session = rhino_health.login(username=my_username, password=my_password)
There will be three ways to interact with the API after you have a session
- Use defined endpoints under lib/endpoints for single actions
- Use our library functions for commonly performed advanced features
- Use our low level API Interface (advanced users)
Interact with the API via defined endpoints
We've included convenience functions for our most commonly used endpoints in the library with required input and output
data classes. These can be found in rhino_health/lib/endpoints.
my_projects = session.project.get_projects()
my_first_project = my_projects[0]
my_first_project.add_collaborator(collaborating_workgroup_uid)
my_dataset = session.dataset.get_dataset(my_dataset_uid)
dataset_project = my_dataset.project
my_dataset_info = my_dataset.dataset_info
Library Functions
Rhino also provides library functions which combine our basic building blocks to perform common actions.
Example:
from rhino_health.lib.metrics import RocAucWithCI
metric_configuration = RocAucWithCI(y_true_variable="label", y_pred_variable="pred", confidence_interval=95, timeout_seconds=600)
"""
data_filters=[{
"filter_column":"is_roc",
"filter_value":1
}]
"""
result = my_dataset.get_metric(metric_configuration)
print(f"{result.output}")
Interact using the low level API
Please contact us for support with interacting with our low level API.
Rate Limits
The Rhino SDK handles rate limits of the API for you if you use the same session between threads and will attempt to queue requests. Excess requests will be sent with exponential backoff. If you send requests to our server from multiple locations then you may run into exceptions.
Development Notes
You may need to use pip install -r requirements.txt --no-cache-dir on M1 Macs
1 maintainer
Metadata
1 maintainer
Release files for rhino-health 2.2.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| rhino_health-2.2.3.tar.gz | 108.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rhino_health-2.2.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 256.3 kB
Release files / rhino_health-2.2.3.tar.gz
| Download URL | rhino_health-2.2.3.tar.gz |
|---|---|
| Size | 108.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f3643ab1f60b6391c6cddb47437c5a9bcc89b0092ffd7b62d2f767a2eaac7fd3
|
|
BLAKE2b-256 checksum How to use checksums |
f2c091d37cacfdd8b1ff095258222fb731d77a6315c4da80c6e242a89891817e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logRelease files / rhino_health-2.2.3-py3-none-any.whl
| Download URL | rhino_health-2.2.3-py3-none-any.whl |
|---|---|
| Size | 148.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e0c047a2d6e8c8e58c61e3f4a4b7b0fed2a952264b0e4b67ae247f936a973963
|
|
BLAKE2b-256 checksum How to use checksums |
eda803b8891c1d8d01fc129f73e5122673e31b084bb61db2ae8edfd2ad9b090b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency log
