Bytes per element for a zarr dtype string, and whether it is an integer type.
Both spellings occur in practice: zarrita reports friendly names
('uint16', 'float32') while a raw .zarray carries numpy typestrings
('<u2', '|u1', '>f4'). Accepting only one form would make the budget
silently read 0 bytes for the other — the failure mode being a budget that
admits everything.
Returns null for anything unrecognised, which callers treat as a rejection
rather than a free pass.
Bytes per element for a zarr dtype string, and whether it is an integer type.
Both spellings occur in practice: zarrita reports friendly names (
'uint16','float32') while a raw.zarraycarries numpy typestrings ('<u2','|u1','>f4'). Accepting only one form would make the budget silently read0bytes for the other — the failure mode being a budget that admits everything.Returns
nullfor anything unrecognised, which callers treat as a rejection rather than a free pass.