edfcore 0.4.406 → 0.4.408

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

package/docs/CHANGELOG.md

@@ -6,6 +6,39 @@ 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.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.
+  `concepts.md` calls a zero record duration legal and says what edfcore does about it — a
+  `ZERO_RECORD_DURATION` warning, `sampleRateHz` left `undefined`, "and keeps reading" — and
+  `api-errors.md` names the shape it comes from: an annotations-only EDF+ recording, whose records
+  carry events and no samples.
+- "Keeps reading" is the part with a window in it. Every record sits at one instant, so a window
+  either contains that instant or it does not and there is no interval arithmetic to do. That is
+  why the code has a separate branch for it, and why that branch is where a division by zero would
+  otherwise live. Both index shapes carry their own copy — a complete index answers from its
+  segments, a probed one from the nominal grid — and the two are now required to agree on every
+  window put to them.
+- The boundary rule is the same as everywhere else: a window opening exactly on the instant
+  contains it, one closing exactly on it does not.
+
 ## 0.4.406
 
 - **Added** tests for the index `validateRecording` is handed, and whether it is allowed to answer

package/package.json

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