H5T_NATIVE_B8 dataset shows up empty

Open
  • Is something wrong?
#206 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reproducing the issue in HDF Compass with a dataset written as H5T_NATIVE_B8, then compare its display with H5T_NATIVE_UINT8 and verify the values using h5dump. Done means the bitfield dataset is displayed with its stored values while the existing readback behavior remains intact.

Written by the indexing model from the issue text.

Description

Writing a normal 1-byte bool into a dataset of type H5T_NATIVE_B8 shows up empty in HDF Compass, even though the data is there and can be read back, or viewed with h5dump. See the top window on the attached screenshot.
Cheers!

hdfcompass_bool_crop

15 min later: I just realized that the "B" in H5T_NATIVE_B8 stands for bitfield and not bool. In fact H5T_NATIVE_UINT8 does show up and fixes my immediate problem. In any case, the file using H5T_NATIVE_B8 seems well formed and the dataset not showing up could be a bug.

Dominant language
Python
Stars
132
Forks
27
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from HDFGroup/hdf-compass

All issues in HDFGroup/hdf-compass

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.