AtriumDB
AtriumDB is a comprehensive solution for the management and analysis of physiological waveform data. It includes a powerful SDK for data compression, storage and retrieval.
Installation
From PyPI (recommended)
$ pip install atriumdb
This will install the base version of AtriumDB, allowing the reading and writing to local datasets, supported by sqlite3 only. For more installation options including support to MariaDB datasets see the documentation. To install from source see GitHub readme here.
Quick Start
Creating a new dataset
To create a new dataset, you can use the create_dataset method. This method allows you to specify the type of metadata database to use and where the data will be stored.
from atriumdb import AtriumSDK
# Create a new local dataset using SQLite
sdk = AtriumSDK.create_dataset(dataset_location="./new_dataset", database_type="sqlite")
# OR create a new local dataset using MariaDB
connection_params = {
'host': "localhost",
'user': "user",
'password': "pass",
'database': "new_dataset",
'port': 3306
}
sdk = AtriumSDK.create_dataset(dataset_location="./new_dataset", database_type="mysql", connection_params=connection_params)
The sdk object is how you will interact with the dataset including retrieving data, saving data and any of the other methods defined in the documentation.
Connecting to an existing dataset
To connect to an already created dataset, you will need to specify a local path where the dataset is stored if it's a sqlite database. If it's a MariaDB dataset you will also have to specify the connection parameters.
# Import AtriumSDK python object
from atriumdb import AtriumSDK
# Define a directory path where the dataset is stored (always needed)
dataset_location = "./example_dataset"
# Create AtriumSDK python object (sqlite)
sdk = AtriumSDK(dataset_location=dataset_location)
# OR Connect to a dataset supported by mariadb
connection_params = {
'host': "localhost",
'user': "user",
'password': "pass",
'database': "new_dataset",
'port': 3306
}
sdk = AtriumSDK(dataset_location=dataset_location, metadata_connection_type="mysql", connection_params=connection_params)
Metadata
Release files for atriumdb 2.6.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 | |
|---|---|---|---|
| atriumdb-2.6.0.tar.gz | 1.1 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| atriumdb-2.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.3 MB
Release files / atriumdb-2.6.0.tar.gz
| Download URL | atriumdb-2.6.0.tar.gz |
|---|---|
| Size | 1.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3af1409ed054d1a468bf70e18e61089ccba9a1a0099f20cb0fb0bab2f0469fd5
|
|
BLAKE2b-256 checksum How to use checksums |
cbcf237b793553816ce733823c78db22853ee83fab6986da6205ca9a347c78bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Feb 13, 2026.
Transparency logRelease files / atriumdb-2.6.0-py3-none-any.whl
| Download URL | atriumdb-2.6.0-py3-none-any.whl |
|---|---|
| Size | 1.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
093940f36e10761c918e266e3299669d4fb5186a9d5df42f3781631ab4798359
|
|
BLAKE2b-256 checksum How to use checksums |
4a88a340854e7e3b5650315cb60916bf1cd9b499bceb0829f81e6436de7d85af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Feb 13, 2026.
Transparency log