Hi all,

We are seeking community feedback on a new RFC proposing a unified, 
string-based filter configuration interface for HDF5.

The current H5Pset_filter interface requires filter parameters to be passed as 
raw unsigned int arrays (cd_values). This works well for integer parameters but 
is cumbersome for filters that accept floating-point values (rates, 
tolerances), and produces opaque sequences that are difficult to use from the 
command line or high-level language bindings.

This RFC proposes a new function, H5Pappend_filter, that accepts filter 
parameters either as a raw cd_values array or as a human-readable key=value 
string (e.g., "mode=rate, rate=3.5"). The design:

* Adds H5Pappend_filter and the H5Z_params_t tagged union to the public API
* Introduces H5Z_class3_t with optional string-configuration callbacks for 
plugin authors
* Preserves full backward compatibility --- existing APIs, plugins, and call 
sites are unchanged
* Covers Fortran and Java bindings, h5repack/h5dump integration, and a 
normative cd_values packing convention for floating-point parameters

We are particularly interested in feedback on:

[RFC_HDFG_2026_001-1.pdf|attachment](upload://edkwASb6mKw3dLJJRZL6qCJeMis.pdf) 
(334.9 KB)

1. The H5Z_params_t tagged union and the H5Pappend_filter function signature, 
including feedback on the key-value parser.
2. The H5Z_class3_t plugin callback contract, especially the two-pass 
set_config protocol
3. The normative cd_values packing convention for double/float parameters
4. The Fortran and Java binding designs
5. Any use cases or edge cases not addressed by the current design

Please reply to this thread or preferably on the related issue at your earliest 
convenience:

https://github.com/HDFGroup/hdf5/issues/6153

Thank you,
Scot Breitenfeld





---
[Visit 
Topic](https://forum.hdfgroup.org/t/rfc-hdfg-2026-001-string-based-filter-configuration-api-request-for-community-feedback/13776/1)
 or reply to this email to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, [click 
here](https://forum.hdfgroup.org/email/unsubscribe/5673fe46463f2f03eb170b58de40ce646dd94e679ac96d9b5943becc266ca9cc).

Reply via email to