edfcore 0.4.315 → 0.4.317

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

package/docs/CHANGELOG.md

@@ -6,6 +6,28 @@ 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.317
+
+- **Added** an execution of the out-of-range section of `physical-values.md` — the four samples the
+  window returns unclamped, the count of two beside them, and the four values
+  `clampToDigitalRange` produces — all read out of the printed comments rather than restated.
+- Also checked is the sentence those two features turn on: both order the declared bounds before
+  using them. A file whose digital minimum and maximum are the wrong way round still reports two
+  samples out of range rather than every one of them, and still clamps to four distinct values
+  rather than folding the channel onto a single one, which is what the pair as written would do.
+
+## 0.4.316
+
+- **Added** an execution of the negative-gain section of `physical-values.md`: the scale it prints,
+  the three samples it converts, the envelope `physicalRangeOf` reports in size order rather than
+  field order, and the whole `INVERTED_PHYSICAL_RANGE` message it quotes for a one-signal file,
+  compared word for word against the one the package emits.
+- Only the page's hard wraps are undone for that comparison. A run of spaces inside a line is not
+  wrapping — it is the eight-byte physical minimum field quoted as the file holds it, padding
+  included — so collapsing every space would have compared against a message edfcore does not
+  emit. The byte offset in the quote is resolved through `signalFieldOffset`, which is the same
+  `256 + ns*104 + i*8` the address table on `edf-format.md` gives.
+
 ## 0.4.315
 
 - **Added** a measurement of the float32 cost `physical-values.md` cites as the reason `toPhysical`

package/package.json

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