edfcore 0.4.321 → 0.4.323

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.321";
+export declare const VERSION = "0.4.323";
 //# 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.321';
+export const VERSION = '0.4.323';
 //# 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.323
+
+- **Added** an execution of the four-line record arithmetic on `edf-format.md` — the sample width
+  per family, the record length as the summed sample counts, each signal's offset within a record
+  as the sum of the counts before it, and the file offset of record `r`. The four lines are checked
+  to still be on the page, then run against four shapes: both families, a five-signal file, a
+  one-signal file, and the mixed-rate case the page describes, EEG at 256 samples per record beside
+  a channel at 1.
+- `concepts-arithmetic.test.ts` covers one specific file from the concepts page. These are the
+  general equations that file is an instance of, including the closing one: the last record has to
+  end exactly at the end of the file, with no padding and no trailer.
+
+## 0.4.322
+
+- **Fixed** a wrong claim on `edf-format.md`. It named `|0`, `<<` and `>>>` together as operators
+  that "wrap it negative without warning" past 2^31. `>>>` is the unsigned shift and never returns
+  a negative number: it truncates to 32 bits and keeps handing back a plausible offset until 2^32,
+  then a wrong one. Grouping it with the other two described the safer failure and hid the more
+  dangerous one — a negative offset is caught by the first bounds check it meets, and a positive
+  wrong one is not.
+- Found while writing 0.4.321, whose demonstration would not assert what the sentence said. The
+  corrected wording is now pinned by that test, and both behaviours are shown at the sizes where
+  they actually occur.
+
 ## 0.4.321
 
 - **Added** a guard for the offset rule `edf-format.md` states: offsets stay in plain floats, which

package/package.json

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