edfcore 0.4.355 → 0.4.357

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.355";
+export declare const VERSION = "0.4.357";
 //# 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.355';
+export const VERSION = '0.4.357';
 //# sourceMappingURL=constants.js.map

package/docs/CHANGELOG.md

@@ -6,6 +6,35 @@ 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.357
+
+- **Added** an execution of the two-signal `trimToWindow` example on `api-primitives.md`. It exists
+  to make one point — a 256 Hz channel and a 3 Hz channel asked for the same window start at
+  different instants and hold different counts — and that is why `startSeconds` lives on
+  `EdfChunkSignal` rather than only on the chunk. Both printed rows are now produced.
+- The rule underneath is also pinned: membership is decided against the tick edfcore PUBLISHES for
+  a sample, not against its exact rational start. The page's own worked figure is checked both
+  ways — 256 samples in a one-second record put sample 1 at 39,062.5 ticks, which is not a whole
+  tick, published as 39,063 — because selecting on the exact start excluded the very sample a
+  caller had aligned the window to, a defect this project shipped and fixed in 0.3.56.
+- Plus the three things trimming promises about its result: a subarray view rather than a copy so
+  it allocates nothing, a zero-length result rather than an error for a window that misses, and a
+  refusal when the header is not the one the chunk was read with.
+
+## 0.4.356
+
+- **Added** an execution of the `resolveTimeWindow` example on `api-primitives.md`: a one-second
+  window from t = 2.5 on a file with one-second records, straddling records 2 and 3. The function
+  exists so the price of a window is auditable before a byte is read, and a reader planning a
+  viewport from that example is doing arithmetic that has to hold — including that two records are
+  paid for to get one second.
+- The three ways to get nothing back are checked as well, since returning `[]` rather than throwing
+  is what lets a caller loop over ranges with no special case: a non-positive duration, a window
+  outside the recording, and one inside a gap on an index that knows where the gaps are. The last
+  is paired with the case either side of it, so the emptiness is about the gap rather than about
+  the file. And a probed index over a file with gaps throws rather than guessing at onsets nobody
+  has read.
+
 ## 0.4.355
 
 - **Fixed** a test of mine that could time out. The signature check added in 0.4.354 spawned `tsc`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.4.355",
+  "version": "0.4.357",
   "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.355';
+export const VERSION = '0.4.357';