edfcore 0.4.407 → 0.4.409

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

package/docs/CHANGELOG.md

@@ -6,6 +6,41 @@ 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.409
+
+- **Added** tests for the start offset a chunk has to derive when it does not begin at record 0.
+  A caller following the `decodeAnnotations` example on `api-primitives.md` hands over a record
+  range that usually excludes record 0, so record 0's sub-second offset — what every published
+  onset is rebased on — has to be derived by subtracting the nominal distance back to it.
+- That subtraction is valid only while the records in between are contiguous, which is what a
+  discontinuous file is not. A derived value outside [0, 1) is therefore evidence about the file:
+  on one marked EDF+C it means the file is either discontinuous while claiming continuity or its
+  onsets drift, and the diagnostic says so instead of rebasing on a number known to be wrong. On an
+  EDF+D file the same value implies nothing, so nothing is reported — otherwise `strict` would
+  reject every conformant discontinuous recording.
+- A supplied `originTicks` or `startOffsetTicks` outranks the derivation even when it lies outside
+  [0, 1), because it came from the timeline rather than from arithmetic across a gap. That is what
+  keeps the diagnostic count a property of the file: before 0.3.15 the three internal callers
+  re-derived it per chunk, and one file produced 1, 2, 4, 7, 16 or 31 of them purely as a function
+  of `maxMaterializeBytes`.
+
+## 0.4.408
+
+- **Added** tests for the refusals in the sample helpers. `sampleAt`, `sampleStartTicksOf` and
+  `gridSampleIndexAt` all map between a time and a sample index, all three sit behind a guard
+  rejecting the signals and files where no such mapping exists, and none of those guards had ever
+  been executed.
+- None of the inputs is exotic. An annotations channel is in `header.signals`, so
+  `signals.map((s, i) => sampleAt(recording, i, t))` reaches it on the first EDF+ file. A signal
+  declaring zero samples per record opens with a warning, beside live channels. A file whose
+  records do not advance in time opens with a warning too, and `api-errors.md` names a scoring file
+  as the reason it is legal.
+- The three messages differ because the ways out differ — an annotations channel to
+  `onsetTicksFromFirstRecord`, a zero-sample signal to the diagnostic explaining it, a zero-duration
+  file to `readRecords` — so the pairing is checked rather than the error type. `sample-grid.ts` and
+  `sample-locate.ts` carry the same three refusals and are checked side by side, because 0.3.78 was
+  the two disagreeing about which onset field to recommend.
+
 ## 0.4.407
 
 - **Added** tests for a window over a recording whose records do not advance in time.

package/package.json

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