edfcore 0.5.40 → 0.5.42

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

package/docs/CHANGELOG.md

@@ -6,6 +6,53 @@ 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.5.42
+
+- **Added** the transformation that changes what the samples MEAN without changing the samples.
+  Rewriting `physicalMinimum`/`physicalMaximum` in the header leaves every stored integer identical
+  — `decodeDigital` never looks at the range and `toPhysical` never looks at the bytes — and moves
+  everything derived from it onto the new scale. Nothing tested the two against each other:
+  `physical-values.md` is checked against printed numbers and `out-of-range.test.ts` against the
+  digital path, and the relationship between them was prose.
+- The interesting half is the part that does **not** hold. Multiplying the declared range by ten
+  multiplies `bitValue` by exactly ten and leaves `offset` untouched — both exact in float64 — and
+  yet a quarter of the converted values are not exactly ten times their counterpart.
+  `bitValue * (offset + digital)` is a float64 multiply, and scaling an operand is not the same
+  operation as scaling the result.
+- That is worth pinning because it is a mistake a caller makes on purpose. Given microvolts and
+  wanting millivolts, the obvious move is to divide the values, and the obvious check is that
+  dividing the declared range agrees. It does not, in the last place, for a quarter of the range —
+  and the last place is what `physical-values.md` spends a page refusing to be casual about.
+- So four things are asserted together: the digital path is bit-identical under the transformation
+  and so are the structural numbers and the observed digital range; the scale moves by exactly the
+  factor the declaration moved by; every converted value is on its own declared scale exactly; and
+  the rescaling identity fails, by at most one unit in the last place and for neither none nor all
+  of the values. Distributing the multiply in `toPhysical` — an algebraically equivalent
+  rearrangement — fails three of them.
+
+## 0.5.41
+
+- **Added** a metamorphic test: reordering the signals in a header changes where the bytes are and
+  nothing else. EDF interleaves — every data record holds each signal's samples end to end in header
+  order, and a signal's block begins at the sum of the widths declared before it — so a channel's
+  position decides the offset every read of it is computed from, and decides nothing about what that
+  channel contains.
+- That makes signal order a transformation with unusual reach: it changes every offset in the
+  de-interleaving arithmetic and must change no value anywhere. A fixture with one signal, or with
+  several of equal width, cannot tell the difference. The arithmetic only has room to be wrong when
+  the widths differ — which is exactly the file the format exists for, EEG at 256 Hz beside a
+  temperature channel at 1 Hz.
+- The suite tested reading against expected values, per fixture; nothing tested it against itself
+  under a transformation. A `recordByteOffset` computed from the wrong running total, an off-by-one
+  in the signal loop, or a decode that assumed uniform width would survive every fixture in the
+  suite and fail here.
+- Both directions are asserted, because half of it would be worthless. The offsets really do move —
+  three orders give three different offset sets, and `EEG Fpz-Cz` moves from byte 0 to byte 18 while
+  `Temp rectal` moves from 80 to 0 — and every per-label result stays identical: samples, physical
+  values, envelope buckets, sample counts, the range the sweep observes, and what `getSignal` and
+  `findSignals` return.
+- The last block is the property over arbitrary widths and arbitrary rotations, with a constant seed.
+
 ## 0.5.40
 
 - **Added** the resolution of every index and byte offset edfcore publishes. The API is full of

package/package.json

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