edfcore 0.5.57 → 0.5.59

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

package/docs/CHANGELOG.md

@@ -6,6 +6,48 @@ 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.5.59
+
+- **Added** the round trip a streaming pipeline actually performs: stream a window in pieces, merge
+  the pieces, and get the window. `merge-split.test.ts` proves it for `readWindow`. `streamRecords`
+  is the other way to get a window in pieces and is different code — a `readRecords` per piece, a
+  seam check between them, and a `chunkRecords` knob that decides how many pieces there are. Its
+  docblock says the pieces must be "the same object in every respect" as a read chunk, and
+  `stream-equals-read.test.ts` checks that one piece at a time. Whether they reassemble was not
+  checked.
+- If they do not join, the memory bound the call exists for is bought with an answer the caller
+  cannot reconstruct — which is the whole point of streaming a twelve-hour recording and then
+  running a filter over it.
+- The stream is merged at four chunk sizes, from one piece per record to a single piece, and
+  compared against `readWindow` on the same window: the samples, the record range, the byte offset
+  and length, the exact start and duration in ticks, `precededByGap` and the diagnostics.
+- On a discontinuous file the answer changes, correctly. The stream crosses the gap in pieces, so
+  merging all of them is refused with the message `chunks.ts` produces — and the advice that refusal
+  ends with is followed: grouped by run, each run reassembles into exactly the chunk `readWindow`
+  returns for it.
+
+## 0.5.58
+
+- **Added** the composition rule for `trimToWindow`: trimming to A and then to B is trimming once to
+  their overlap. The call returns a `subarray` view rather than a copy — "so trimming allocates
+  nothing and the two share storage" — which makes its result a chunk signal like any other, and a
+  caller who has one narrows it again as a matter of course: a viewer that has read a minute and is
+  now drawing ten seconds of it does exactly that.
+- `trim-window.test.ts` covers the rule for one trim, against the closed form the source derives.
+  Composing two was not covered, and it is where a narrowing that treated its input's
+  `firstSampleIndex` as zero would show — the second trim measured from the wrong origin, coming
+  back with the right number of samples from the wrong place. The fixture's samples are a ramp over
+  the whole recording, so a sample's value names its position and a wrong origin is a different
+  number rather than a different length.
+- The property runs over 300 arbitrary window pairs with a constant seed, including pairs that do
+  not nest and pairs that miss each other entirely.
+- **Found while writing it,** and now stated rather than asserted away: an empty trim has no
+  position to agree about. The docblock promises a window that misses the chunk "yields a
+  zero-length result rather than an error" and says nothing about where that result sits, so two
+  routes to an empty answer report different `firstSampleIndex` and `startSeconds` — each being
+  where its own arithmetic stopped. `sampleCount` is the field to branch on, and the property
+  compares positions only where there are samples in them.
+
 ## 0.5.57
 
 - **Added** the property that makes an envelope exhaustive: the buckets are a partition. `readEnvelope`

package/package.json

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