edfcore 0.4.316 → 0.4.318

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

package/docs/CHANGELOG.md

@@ -6,6 +6,27 @@ 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.318
+
+- **Strengthened** the check that the golden fixtures can tell the two scaling forms apart.
+  `physical-values.md` justifies pinning EDFlib's expression with one measurement — the textbook
+  form "fails it on 140 of 256 samples of the symmetric fixture", with an example pair of values —
+  and the existing assertion was that more than a quarter of the asymmetric file's samples differ.
+- That bound is the right shape for "the fixtures are not vacuous" and the wrong shape for a
+  sentence quoting an exact count and an exact pair of decimals. Both numbers and both values are
+  now read out of the page and reproduced from the committed pyEDFlib output, so the page's
+  evidence is measured rather than remembered. The looser bound stays; it says something different.
+
+## 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,

package/package.json

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