dask-contrib/dask-histogram

Issues

• Unserializable histogram generated if computed without fill call

  #153 opened 2 months ago by yimuchen
  5

• Cannot `import dask_histogram` which causes failures downstream (`hist.dask` etc) with the newest `dask 2024.9.0`

  #149 opened 3 months ago by ikrommyd
  9

• Return empty histogram on `compute()` if there are no staged fills

  #115 opened a year ago by douglasdavis
  1

• histgram filling not reproducible except in "processes" scheduler?

  #100 opened a year ago by lgray
  28

• copied hist will retain the original name after computing it

  #76 opened 2 years ago by ikrommyd
  6

• dask_histogram creates MaterializedLayers which are slow to optimize over multiple partitions

  #72 opened 2 years ago by lgray
  1

• Feature request: support float weights for histograms

  #68 opened 2 years ago by alexander-held
  2

• Support dask-awkward inputs with weights

  #52 opened 2 years ago by douglasdavis
  3

• feature request: Filling really large histograms that are distributed across a cluster.

  #35 opened 2 years ago by lgray
  2

• bug: dask histograms are not recognized as `compute`-able

  #36 opened 2 years ago by lgray
  0

• Mean storage for histograms

  #8 opened 3 years ago by mpoehlmann
  2

• Computing histogram with dask distributed cluster

  #6 opened 3 years ago by mpoehlmann
  2

• Merge results with a tree reduction.

  #3 opened 3 years ago by douglasdavis
  1

• Document return types for histogram, histogram2d, and histogramdd

  #1 opened 4 years ago by douglasdavis
  0