Use better cd_values[] in LZ4 example#186
Conversation
The old value does not seem appropriate for the LZ4 filter as it is too small.
|
Because this change comes from a branch in a fork, the reqular plugin workflow fails to run, the daily-build workflow needs to run from the fork and use the ignore option. |
@byrnHDF https://github.com/HDFGroup/hdf5_plugins/actions/runs/15354926926 |
|
Right so you need to update the testfiles references to match the output of the tests |
|
It seems more than just that. The example fails on this line: Line 156 in 5c28b5b with the error: |
|
Yes, that does indicate a coding error. |
|
Changing the case will also need to be applied to the examples in HDF5 repo. |
|
Are you okay with this capitalization change @byrnHDF ? I wanted to ask you but you responded faster. |
|
Was there a reason - because it will have consequences in other projects.
Also is it consistent with the other filters - or will those need changed as well.
Allen
…________________________________________
From: Aleksandar Jelenak ***@***.***>
Sent: Wednesday, June 4, 2025 11:57 AM
To: HDFGroup/hdf5_plugins
Cc: Allen Byrne; Mention
Subject: Re: [HDFGroup/hdf5_plugins] Use better cd_values[] in LZ4 example (PR #186)
[https://avatars.githubusercontent.com/u/7267124?s=20&v=4]ajelenak left a comment (HDFGroup/hdf5_plugins#186)<#186 (comment)>
Are you okay with this capitalization change @byrnHDF<https://github.com/byrnHDF> ? I wanted to ask you but you responded faster.
—
Reply to this email directly, view it on GitHub<#186 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AL77KBWKHCIVKWHZQBE6FAL3B4QPBAVCNFSM6AAAAAB6G5OHRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNBQG42TIMJTGY>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Projects out there, or in-house, like HDF5? The reason was the name of the filter is LZ4, not lz4. It is not a required change. Now that I better understand how many places need to be changed, I will switch back. |
|
Yes, usually my choice too, if it involves a lot more work for little gain.
…________________________________________
From: Aleksandar Jelenak ***@***.***>
Sent: Wednesday, June 4, 2025 1:28 PM
To: HDFGroup/hdf5_plugins
Cc: Allen Byrne; Mention
Subject: Re: [HDFGroup/hdf5_plugins] Use better cd_values[] in LZ4 example (PR #186)
[https://avatars.githubusercontent.com/u/7267124?s=20&v=4]ajelenak left a comment (HDFGroup/hdf5_plugins#186)<#186 (comment)>
Was there a reason - because it will have consequences in other projects.
Projects out there, or in-house, like HDF5?
The reason was the name of the filter is LZ4, not lz4. It is not a required change. Now that I better understand how many places need to be changed, I will switch back.
—
Reply to this email directly, view it on GitHub<#186 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AL77KBTPCHGXX23IF7VIEFL3B43D3AVCNFSM6AAAAAB6G5OHRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNBQHE4TQMJYGQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
57dcd98 to
f0dc290
Compare
|
Ok, I removed those changes. Back to the important stuff... I switched to an older version of the LZ4 plugin in this branch, and it worked for a more sensible block size in the LZ4 example. Also all LZ4-related tests are updated accordingly. We now need to decide how to proceed. It would be nice to understand why introduction of the |
|
The LZ4 plugin seems to work now using the new |
LZ4/src/H5Zlz4.c
Outdated
| goto error; | ||
| } | ||
| #else | ||
| #if LZ4_VERSION_NUMBER > 10800 |
There was a problem hiding this comment.
LZ4_decompress_safe existed before LZ4_VERSION_NUMBER existed lz4/lz4@64547df
So I think the version checks can be safely removed.
There was a problem hiding this comment.
Yes, it would simplify the code. I am not familiar with the LZ4 evolution, is there any chance that older versions of this function were slower than the current implementation?
There was a problem hiding this comment.
Yes, but even for older versions of LZ4, the better error handling is worth it.
|
I am eager to test LZ4 compression in NetCDF Operators (NCO) and NetCDF itself. What steps remain before this PR can be merged? |
|
All LZ4 tests pass. Fixed #185. |
The old value does not seem appropriate for the LZ4 filter as it is too small. Such small values will create much larger compressed chunks than the original chunk size.