-
Notifications
You must be signed in to change notification settings - Fork 29
Fix #624: Refine ExtraFieldWarning handling in validation #1443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
Changes from all commits
84df54f
6f1ce0b
48519de
55f674d
4d11721
2e9565c
dc89001
501df27
883b733
27aa910
d8a690f
e0b6174
8fbfcf7
bc684d6
b4e7100
b1b9cd0
41ed817
5126c65
acfb1ab
47699ef
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,13 @@ | ||
| # HDMF Changelog | ||
|
|
||
| ## Unreleased | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please undo this change as well. These were released in HDMF 6.0.0. It seems like these came from resolving conflicts from a git merge incorrectly. |
||
|
|
||
| ### Breaking changes | ||
| - `HDF5IO` `expandable` argument is now a list of data type names instead of a boolean. The default is `("VectorData", "ElementIdentifiers")`, so only `DynamicTable` columns and id are expandable out of the box — previously every dataset with a matching spec shape was expanded. Datasets of types outside this list that previously were expandable by default will now default to fixed-shape on-disk layout; add the relevant type to `expandable` to restore prior behavior. Replace `expandable=True` with an explicit list (e.g. `["VectorData", "ElementIdentifiers", "MyType"]`) and `expandable=False` with `[]`; passing `True`/`False` now raises a `TypeError`. @bendichter @rly [#1439](https://github.com/hdmf-dev/hdmf/pull/1439) | ||
|
|
||
| ### Enhancements | ||
| - Set sensible default chunk sizes (~4 MB, in the recommended 2-16 MB range for cloud-hosted files) when `chunks=True`, replacing h5py's much smaller defaults. Added public `HDF5IO.compute_default_chunk_shape()` so users can inspect or override the chunk shape that would be used. @bendichter [#1440](https://github.com/hdmf-dev/hdmf/pull/1440) | ||
|
|
||
| ## HDMF 6.0.1 (May 5, 2026) | ||
|
|
||
| ### Fixed | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -1501,6 +1501,9 @@ def compute_default_chunk_shape(data_shape, dtype, target_chunk_bytes=4 * 1024 * | |
| The shape of the dataset. | ||
| dtype : numpy.dtype or type | ||
| The data type, used to determine bytes per element. | ||
| target_chunk_bytes : int, optional | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why were these changes made in this file? |
||
| Target chunk size in bytes. Default is 4 MB. | ||
| neurodata_type : str, optional | ||
| target_chunk_bytes : int | ||
| Target chunk size in bytes. Default is 4 MB. | ||
| neurodata_type : str | ||
|
|
@@ -1509,6 +1512,7 @@ def compute_default_chunk_shape(data_shape, dtype, target_chunk_bytes=4 * 1024 * | |
|
|
||
| Returns | ||
| ------- | ||
| tuple or True | ||
| tuple or bool | ||
| The computed chunk shape, or ``True`` to fall back to h5py auto-chunking when a shape | ||
| cannot be computed (unsupported dtype or zero-length trailing dimension). | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please undo this change as well