Skip to main content

SciDuck

A thin DuckDB layer for managing versioned scientific data.

Each variable is stored in its own table. Variables are associated with a hierarchical dataset schema (e.g. subject -> session -> trial) and can be saved at any level of that hierarchy. Multiple versions of each variable are supported natively.

All data -- including arrays -- is stored in queryable DuckDB types (LIST, nested LIST, JSON) so the database can be inspected with DBeaver or any DuckDB-compatible viewer.

Usage

from sciduckdb import SciDuck

duck = SciDuck("data.duckdb", dataset_schema=["subject", "session"])
duck.save("MyVar", data, subject="S01", session=1)
loaded = duck.load("MyVar", subject="S01", session=1)

Features

  • Three save modes: DataFrame with schema columns (Mode A), single entry via kwargs (Mode B), or dict mapping tuples to values (Mode C)
  • Automatic type inference: Maps Python/numpy types to DuckDB types
  • Round-trip restoration: Metadata tracks original types for lossless load
  • Version management: Automatic version numbering, duplicate hash detection
  • Variable groups: Organize variables into named groups
  • Schema validation: Validates dataset schema consistency across sessions

Note: all schema key values are coerced to strings before storage.

Datetimes

A datetime value (datetime.datetime, pd.Timestamp, np.datetime64, NaT) is stored as two columns: <col> TIMESTAMP_NS holding the UTC instant (or a naive value's wall clock), and <col>__tz VARCHAR holding that value's zone ("Europe/Berlin", "UTC", "+02:00"; NULL = naive). Zones are per value, so one column may hold several zones and naive values. Loads give back each value in its own zone. The __tz column exists from the column's first save and is never listed in the variable's data columns. In raw SQL, filter on <col>__tz IS NULL to tell naive rows apart. Owner: sciduckdb.datetimes; design: docs/claude/datetime-roundtrip.md.

Metadata

Release files for sciduckdb 0.1.59

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

Source distribution (sdist)

Source distribution for sciduckdb 0.1.59
File Size Uploaded Provenance Actions
sciduckdb-0.1.59.tar.gz 31.6 kB With provenance Details for sciduckdb-0.1.59.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for sciduckdb 0.1.59
File Interpreter ABI Platform Actions
sciduckdb-0.1.59-py3-none-any.whl Python 3 none any Details for sciduckdb-0.1.59-py3-none-any.whl

Total release size: 63.8 kB

Release files / sciduckdb-0.1.59.tar.gz

Download URL sciduckdb-0.1.59.tar.gz
Size 31.6 kB
Tags Source
SHA-256 checksum
How to use checksums
6517cb9579aff14e7b37ce5a1a8b7840fe369dc22e2145c7feae7c94e4499bc2
BLAKE2b-256 checksum
How to use checksums
2d47e51d52a880382857bd066d54a0cbe0d2f86f0b64fca8f065675b7e38f031
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 27, 2026.

Transparency log

Release files / sciduckdb-0.1.59-py3-none-any.whl

Download URL sciduckdb-0.1.59-py3-none-any.whl
Size 32.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6848f900302239789313158fad9af7531fe1c595dbc8a21f7db65853f0027122
BLAKE2b-256 checksum
How to use checksums
839b334a286704cb4e8436b493f0a4cfc5acfe8777b6906362320f380715d556
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 27, 2026.

Transparency log

Security for sciduckdb 0.1.59

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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for sciduckdb-0.1.59.tar.gz

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 27, 2026.

Transparency log

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.

Release history Release notifications | RSS feed

This release

0.1.59 This release

2 release files Full provenance

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