xarray-datatree 0.0.14-1 source package in Ubuntu

Changelog

xarray-datatree (0.0.14-1) unstable; urgency=medium

  * New upstream release.
  * debian/rule:
    - Improve glob expression to remove unneeded *.*-inofo directories.
  * Update dates in d/copyright.
  * debian/patches:
    - Drop 0001-Fix-compatibility-with-xarray-2023.12.patch, applied upstream.

 -- Antonio Valentino <email address hidden>  Sat, 27 Jan 2024 11:45:18 +0000

Upload details

Uploaded by:
Debian GIS Project
Uploaded to:
Sid
Original maintainer:
Debian GIS Project
Architectures:
all
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Noble release universe misc

Builds

Noble: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
xarray-datatree_0.0.14-1.dsc 3.6 KiB b1aab1b2a1c7d0445d20919a2f08136cbe5a4f23e791f348d3fe38c32224b5ad
xarray-datatree_0.0.14.orig.tar.gz 83.1 KiB 0c4359e11827a9d30ee1c2b6a4b802d64a3ae53861dda50658e8a42963d9ad55
xarray-datatree_0.0.14-1.debian.tar.xz 3.3 KiB cb96fe15933feed28dc0205d4bd9fb2c9617190846fa56e9d9e49ecfa2ffad5b

Available diffs

No changes file available.

Binary packages built by this source

python3-xarray-datatree: Tree-like hierarchical data structure for xarray

 Datatree provides hierarchical data structure, more flexible than
 a single xarray.Dataset object.
 It is able to represent netCDF files / Zarr stores with multiple
 nested groups in a single in-memory object, but datatree.DataTree
 objects have many other uses, such as:
 .
  * organising many related datasets, e.g. results of the same
    experiment with different parameters, or simulations of the same
    system using different models,
  * analysing similar data at multiple resolutions simultaneously,
    such as when doing a convergence study,
  * comparing heterogenous but related data, such as experimental
    and theoretical data, I/O with nested data formats such as
    netCDF / Zarr groups.
 .
 The approach used is based on benbovy's DatasetNode example, the
 basic idea is that each tree node wraps a up to a single
 xarray.Dataset. The differences are that datatree:
 .
  * uses a node structure inspired by anytree for the tree,
  * implements path-like getting and setting,
  * has functions for mapping user-supplied functions over every
    node in the tree,
  * automatically dispatches some of xarray.Dataset's API over every
    node in the tree (such as .isel),
  * has a bunch of tests,
  * has a printable representation