edfcore 0.4.309 → 0.4.311

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

package/docs/CHANGELOG.md

@@ -6,6 +6,30 @@ 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.311
+
+- **Added** an execution of the worked address on `edf-format.md`. The page prints a hand-written
+  `byteOfSample` and one result — byte 1832 for sample 20 of a 16-samples-per-record channel,
+  "record 1, sample 4" — as the fastest way to understand the layout. The index and the address
+  are parsed out of the page, the arithmetic is run against a file built to the snippet's
+  description, and the two bytes at that address are decoded and compared with the sample edfcore
+  returns for the same index.
+- The page says "edfcore does that arithmetic for you", and that sentence is the one worth
+  holding: the value of the printed byte is that it is the byte the library reads, so the check
+  is against a real read rather than against the formula restated.
+
+## 0.4.310
+
+- **Added** the second half of 0.4.309: the per-signal address table on `edf-format.md`, ten rows
+  of `256 + ns*K + i*W`. Each row's `K` and `W` are checked against `SIGNAL_FIELD_BLOCK_OFFSETS`
+  and `SIGNAL_FIELD_WIDTHS`, each address is resolved for several signal counts and compared with
+  `signalFieldOffset`, and the two claims the page makes about the table's own shape — that every
+  `K` is the sum of the widths before it, and that the widths total 256 — are computed from it.
+- This is the table the page calls "the layout detail that produces the most wrong parsers", and
+  the reason is in the check: at `ns = 1` the field-major and struct-per-signal layouts are
+  identical, so a one-signal fixture cannot tell them apart. The addresses are resolved at 1, 2 and
+  30 for that reason.
+
 ## 0.4.309
 
 - **Added** a check over the fixed header table on `edf-format.md`: ten rows giving the offset and

package/package.json

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