Peter Lindstrom

I used homebrew to install HDF5. ``` otool -L `where h5repack` /opt/homebrew/bin/h5repack: /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1336.61.1) /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.12) /opt/homebrew/opt/libaec/lib/libsz.2.dylib (compatibility version 2.0.0,...

> we (or maybe it was just me...I don't think @lindstro cared too much) were worried that the stream header could dominate HDF5 chunk overheads. I don't want to derail...

> > uses the default sw4 master branch . > > Hmmm...I worry you may need to work from a _released_ version of spack. I don't honestly know how stable...

Maybe I'm being confused by HDF5 lingo, but *requiring* 8-bit writes while *allowing* non-8-bit writes seems contradictory. I would advocate for encoding which word size was used in the `cd_vals`...

This seems like a reasonable approach, in particular since big-endian machines are quickly falling out of favor. But let me ask this first: is there any situation where H5Z-ZFP might...

> Can ZFP losses compound under those conditions? I mean, can the result drift...I don't think so but I thought I should ask. Yes, losses can certainly compound. With some...

The point I was making about persistent errors is exactly the one you make. In other words, compressing half a block padded with fill values will introduce some irrevocable loss....

This issue of "generation loss" is one I've pondered for a long time and hypothesized about but never had much time to investigate further. We've conjectured that starting from some...

@markcmiller86 What are your thoughts on this proposal of mine: > I would propose that we add a 2-bit code, _n_, to `cd_values` that indicates that the word size is...

@markcmiller86 Thanks for the summary. I think it's safe to assume that the buffer is word aligned if it was produced by `malloc` and not deliberately advanced to break alignment....