edfcore 0.4.450 → 0.4.451

package/dist/constants.d.ts

@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
     readonly reserved: 224;
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export declare const VERSION = "0.4.450";
+export declare const VERSION = "0.4.451";
 //# sourceMappingURL=constants.d.ts.map

package/dist/constants.js

@@ -79,5 +79,5 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
     reserved: 224,
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.4.450';
+export const VERSION = '0.4.451';
 //# sourceMappingURL=constants.js.map

package/docs/CHANGELOG.md

@@ -6,6 +6,23 @@ alone does not tell you whether you were affected.
 edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
 defect; those are called out below.
 
+## 0.4.451
+
+- **Added** a property test for `bucketCount` over arbitrary windows. `api-helpers.md` calls it
+  "the field to read before indexing, and it is not always the `buckets` you asked for" — a caller
+  who sizes a canvas to 800 pixels, asks for 800 buckets and loops to 800 reads past the end of
+  `counts` on any run shorter than 800 samples, which is every run near the end of a recording and
+  every run between two gaps.
+- The two calls answer differently and both answers are deliberate. `readEnvelope` clamps to the
+  densest signal's sample count, because a grid with more buckets than samples has columns that
+  mean nothing. `readEnvelopeAtResolution` does not, because its contract is the bucket WIDTH:
+  shortening the count would shorten the grid rather than coarsen it, and a time axis asked for
+  30 s per bucket has to keep getting it.
+- Both rules are exactly the kind that hold for the case someone checked — a run long enough for
+  the clamp never to bite, a resolution dividing the span exactly — so they are now checked over
+  generated geometries, along with the invariant a caller actually indexes on: every signal's
+  `counts`, `min` and `max` are `bucketCount` long, whatever the count turns out to be.
+
 ## 0.4.450
 
 - **Added** a property test that `printable` never changes the width of what it is given. Every

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.4.450",
+  "version": "0.4.451",
   "description": "Modern, typed, zero-dependency reader for EDF, EDF+, BDF and BDF+ biosignal files. Works in browsers and Node with true random access.",
   "keywords": [
     "edf",

package/src/constants.ts

@@ -93,4 +93,4 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
 } as const;
 
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.4.450';
+export const VERSION = '0.4.451';