edfcore 0.4.311 → 0.4.313

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.311";
+export declare const VERSION = "0.4.313";
 //# 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.311';
+export const VERSION = '0.4.313';
 //# 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.313
+
+- **Added** an execution of the conversion table on `physical-values.md`: four rows of exact
+  float64 literals showing where EDFlib's expression and the textbook one part company. The
+  literals are parsed from the page, edfcore's column is produced by `toPhysical` and the other by
+  the rejected form, and both are compared with `Object.is` — the comparison the golden-value
+  harness uses, and the only one that can see the digit the table exists to show.
+- The table is the argument for the package's one deliberate numerical choice, so its numbers
+  being right mattered more than most. They were, and nothing held them there. The scale the page
+  prints beside it and the claim that the two forms agree only at the endpoints are checked from
+  the same rows.
+
+## 0.4.312
+
+- **Added** a cross-check of the sample decoders printed on `edf-format.md` against edfcore's own.
+  The page's `decodeEdfSample` and `decodeBdfSample` are three lines each and derived straight
+  from the specification; `decode/digital.ts` de-interleaves whole records through a plan and a
+  typed-array fast path. Every one of the 65,536 EDF encodings now goes through both, along with
+  the BDF boundaries where sign extension from bit 23 is decided.
+- The results the page prints beside each call are parsed out of it rather than restated, so
+  `decodeBdfSample(0xff, 0xff, 0x7f)` has to keep printing what those bytes actually hold.
+
 ## 0.4.311
 
 - **Added** an execution of the worked address on `edf-format.md`. The page prints a hand-written

package/package.json

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