edfcore 0.5.54 → 0.5.56

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

package/docs/CHANGELOG.md

@@ -6,6 +6,46 @@ 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.56
+
+- **Added** the rule `precededByGap` carries, checked however the chunk was asked for. It is stated
+  in three places and was tested in one. `chunks.ts`: the field is `undefined` "in two different
+  situations: no gap, and nobody looked". `stream.ts`: a streamed chunk carries "the same
+  `precededByGap` a `readWindow` chunk would". `biosemi.ts` states the sharpest form — the gap
+  "precedes the RUN, not whichever sample the window happened to admit first, which could be a whole
+  record later", a rule narrowed in 0.3.67 after 0.3.92 wrote down a wider one.
+- Four entry points produce chunks, and the field is computed from the index rather than from the
+  read — so what it says must be the same whichever asked, for the same records.
+- One file with a twenty-second hole after record 4, and every way of naming the records around it:
+  `readRecords` by number, `readWindow` by time, `streamRecords` in pieces smaller than the run, and
+  `readEnvelope`. The gap appears on exactly one chunk in each — the one whose first record is
+  record 5 — and on none of the others, including the chunk starting at record 6, which is inside
+  the run and after it, and the chunk starting at record 4, which spans the hole by record number
+  and is not preceded by it. At four different `chunkRecords`, exactly one streamed chunk carries it
+  every time.
+- The other of the two situations is checked beside it: on a probed index the same read gives
+  `undefined`, which is "nobody looked" rather than "no gap" — and the samples are identical either
+  way, so only the field about structure differs.
+
+## 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

package/package.json

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