edfcore 0.5.5 → 0.5.7

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

package/docs/CHANGELOG.md

@@ -6,6 +6,47 @@ 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.7
+
+- **Added** the one worked `readWindow` result on `api-reading.md`, built and run. The page shows a
+  65-second window over a discontinuous file coming back as two chunks — `{ start: 498, count: 2 }`
+  at 498 s and `{ start: 500, count: 3 }` at 560 s with a gap before it — and it is the only place
+  the page shows what "one chunk per contiguous run" produces. Every figure in it was prose.
+- The counts are the part worth running. 2 and 3 are not the same number and neither is 5, so a
+  reader can see from them that the window did not return every record between its ends. Both fall
+  out of the half-open rule: record 499 ends exactly at 500 s and is in, record 503 starts exactly
+  at 563 s and is out — the rule that decides whether consecutive epochs partition or overlap. The
+  run asserts the excluded record starts exactly at the window's end.
+- `startSeconds: 560` is the other half: sixty seconds of the window lie inside the gap, so the
+  second chunk starts 62 seconds after the first while being only 2 records later. A consumer that
+  assumed `startSeconds` advanced with the record number would place three records a minute early.
+- The window and both chunks are parsed out of the page, anchored to the printed line rather than
+  to the first `startSeconds` on it — an unanchored pattern picked up an earlier example's window
+  and built one nothing on the page describes, which passed its own parse and tested a different
+  file.
+
+## 0.5.6
+
+- **Fixed** two lines of the `EdfSignal` block on `api-types.md` describing a different file from
+  the other five. The page prints one running example — six one-second records, one 100-sample
+  signal — and its test builds that file and checks `index`, `kind`, `samplesPerRecord`,
+  `sampleRateHz` and `sampleCount`. It stopped there, and the two lines it stopped before are the
+  two that would have failed: `signal.scale` prints a bitValue of `0.1221001221001221` and
+  `signal.raw.digitalMinimum` prints `'-2048   '`, while the fixture took the writer's defaults and
+  produced `0.015259021896696421` and `'-32768  '`.
+- The page is the specification and the fixture is the reconstruction, so the fixture moved: the
+  printed values imply 500 µV over 4,095 digital steps and nothing else, and the conventions
+  paragraph at the top of the page introduces the "exposed twice" rule with the same `-2048` as its
+  example. Declaring `-250`..`250` over `-2048`..`2047` makes every line of the block true of one
+  file, and makes the sentence at the top true of it too.
+- `bitValue` is re-derived through the pinned expression from the declared fields rather than
+  compared against the printed float. It is the number a reader checks their own port against, and
+  copying the page's sixteen digits into the test would make the two agree without either being
+  right.
+- The whole block is now under test, including the raw field with its padding intact — compared
+  against the page without collapsing whitespace, since collapsing turns `'-2048   '` into
+  `'-2048 '` and quietly passes the check the sentence exists to make.
+
 ## 0.5.5
 
 - **Added** the table under "Files with several sample rates" on `reading-signals.md`, and the

package/package.json

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