edfcore 0.5.53 → 0.5.55

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

package/docs/CHANGELOG.md

@@ -6,6 +6,44 @@ 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.55
+
+- **Added** the window that begins before the recording does. "A window that starts before record 0
+  is how a pre-stimulus epoch is spelled" is the sentence `tal/ticks.ts` uses to justify `floorDiv`
+  and `ceilDiv` existing at all, and `annotations.md` builds a section on negative onsets around the
+  same idea. 0.5.15 tested the two divisions; what a caller actually writes —
+  `readWindow(recording, { startSeconds: -2, durationSeconds: 4 })` — was tested for its bounds and
+  not for the negative side of them.
+- There are three outcomes and only one is an error, and it is not the one a reader expects. A
+  window straddling t = 0 is read, clamped to the samples that exist. A window entirely before the
+  recording comes back as `[]` — the same empty array a window past the end gives, which
+  `api-reading.md` says in as many words. Nothing throws for either: a negative bound is a
+  legitimate question with a possibly empty answer, and only a non-finite one is a mistake.
+- The trimmed result is where it matters, and it is asserted sample for sample.
+  `trimToWindow(header, series, -2, 4)` starts at 0 rather than at -2 and holds exactly the samples
+  in `[0, 2)` — the arithmetic that needs a floor rather than a truncation, on operands that are
+  negative for the whole first half of the window. A bound that is not a whole second is checked
+  with it, and `sampleAt` is checked either side of the boundary.
+
+## 0.5.54
+
+- **Added** the claim the `index` option on `validateRecording` is only worth having if it holds: a
+  sweep that was handed an index says what a sweep that read one says. `api-validate.md` prices the
+  option — a supplied complete index is the difference between a scan of every record and no
+  traversal at all — and `inspect-validate.test.ts` checks that it does skip the traversal and that
+  a probed index is not accepted as a substitute. Nothing checked that the report is the same.
+- It is a real risk rather than a formality. The two paths reach `segmentCount` and `gaps` through
+  different code — one from `buildSegmentation` over onsets it just read, the other from the
+  `segments` and `gaps` already on the supplied index — and everything the report says about
+  structure is derived from those two. A supplied index that produced a different segment count
+  would be a faster answer to a different question.
+- Both now run over every shape in the matrix and are compared whole, with `scanSamples` on so the
+  sample statistics are in it: `ok`, every diagnostic and every entry of `signalStats`. The matrix
+  is asserted to reach both verdicts and to produce real statistics, so the comparison is of
+  something.
+- `bytesRead` is the one number that legitimately differs, and it is asserted to be lower — on the
+  files where there is anything to skip, which is the reason the option exists.
+
 ## 0.5.53
 
 - **Added** the CLI's half of determinism. `diagnostics.md` says of the formatter underneath it that

package/package.json

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