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.0a2
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.0a2.tar.gz | 995.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xarray_behave-0.38.0a2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.0 MB
Release files / xarray_behave-0.38.0a2.tar.gz
| Download URL | xarray_behave-0.38.0a2.tar.gz |
|---|---|
| Size | 995.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6511fa73a6ff91959d21e60178bdf730d9e9f2e3c4de7e35f08908b07d34e639
|
|
BLAKE2b-256 checksum How to use checksums |
443f7099ccd31f0f489f4fc5e090e480c063c92e27e4f807ffc5ba6c96039ff0
|
| 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.0a2-py3-none-any.whl
| Download URL | xarray_behave-0.38.0a2-py3-none-any.whl |
|---|---|
| Size | 1.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
12292a1f80335ca7fe7967999e5b33ba0d4af96c8f52b930561ff1487a918c4d
|
|
BLAKE2b-256 checksum How to use checksums |
079b376dc228d6da3fec34cb1138358623ebf9fd38f4e5af444fe6600a11cf4d
|
| 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.0a2
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.