Blosc / Blosc/python-blosc2

ALWAYS_SPLIT seems necessary for ZFP

Open
#338 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
211
Forks
58
Avg merge
1d 17h
Merged PRs (30d)
6

Description

At least these tests:

```
FAILED tests/ndarray/test_lossy.py::test_lossy[shape1-float64-cparams1-None-False] - RuntimeError: Error while creating the NDArray
FAILED tests/ndarray/test_lossy.py::test_lossy[shape3-float32-cparams3-lossy.b2nd-False] - RuntimeError: Error while creating the NDArray
```

fail if "splitmode" is set to`AUTO_SPLIT`, which is the new default after [this discussion](https://github.com/Blosc/python-blosc2/discussions/337).

Perhaps this is due to the design of the test, but while we can investigate more, they are set explicitly in the test to `ALWAYS_SPLIT`.

Contributor guide

Open the contributing guide

Research direction

Start by running the two failing cases in tests/ndarray/test_lossy.py and inspect how splitmode is configured there. Compare AUTO_SPLIT with the explicit ALWAYS_SPLIT setup, then determine whether the failures come from the test design or the implementation. Done means the cause is established and the affected tests behave correctly with the intended split mode.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.