This release is a pre-release and may not be stable for production use.
xarray-behave
Install a working conda installation (see here).
conda env create -n xb -y -f https://raw.githubusercontent.com/janclemenslab/xarray-behave/refs/heads/master/env/xb.yml
See demo.ipynb for usage examples.
GUI configuration
The GUI saves reusable state to ~/.das.yaml when it closes cleanly. This
includes the window and panel layout, display and annotation options, audio and
threshold settings, event-type presets, and the last reusable load-dialog
choices. Source-specific values such as file paths, HDF5 dataset names, inferred
sample rates, and pixel calibration are deliberately not saved.
Configuration is applied in this order, with later values taking precedence:
- Built-in defaults.
~/.das.yaml..das.yamlin a directory source, or beside a file or.zarrsource.- A file supplied with
--config. - Explicit command-line options and edits made in the load dialog.
For example:
python -m xarray_behave.gui.app recording.wav --config lab-profile.yaml
Use File > Save Configuration As... to create a local or shared profile. Configuration files are versioned YAML mappings. A minimal profile is:
version: 1
window:
panels:
sidebar: true
timeline: true
event_table: true
viewer:
spectrogram:
colormap: magma
compression: 3
audio:
waveform_all: true
playback_all: false
event_types:
- name: pulse
fixed_duration: true
duration_seconds: 0.01
duration_editable: false
color_hex: "#ffd166"
visible: true
editable: true
Metadata
Release files for xarray-behave 0.38.0a3
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 | |
|---|---|---|---|---|
| xarray_behave-0.38.0a3.tar.gz | 996.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xarray_behave-0.38.0a3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.0 MB
Release files / xarray_behave-0.38.0a3.tar.gz
| Download URL | xarray_behave-0.38.0a3.tar.gz |
|---|---|
| Size | 996.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8dc1afabee9538d975b55a2df83160fc5969f8802c77a981a1bc64cc3c39eafd
|
|
BLAKE2b-256 checksum How to use checksums |
39d5a0304ecfed715253b43fca581a2b7ed8ec7ee250ca6070eb325f3b0bdda0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.3 {"installer":{"name":"uv","version":"0.11.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / xarray_behave-0.38.0a3-py3-none-any.whl
| Download URL | xarray_behave-0.38.0a3-py3-none-any.whl |
|---|---|
| Size | 1.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8d73e2ba587e978484bbe8b21c57fb2e7783088bb5ad3e5081ea409775bd8666
|
|
BLAKE2b-256 checksum How to use checksums |
6afe85c99e3824ff51addff4a08a19b0a6a9f7f5f166dea50921264559edba6d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.3 {"installer":{"name":"uv","version":"0.11.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for xarray-behave 0.38.0a3
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.