edfcore 0.4.341 → 0.4.343

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

package/docs/CHANGELOG.md

@@ -6,6 +6,41 @@ 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.343
+
+- **Added** `tests/property/scaling.test.ts`, which measures the bound 0.4.342 asserted. Random
+  declarations are built, written, parsed and converted at both endpoints, and the error is
+  compared against what the file itself declares — the fourth property file in the suite and the
+  first over the scaling expression.
+- Two wrong units on the way to the right one, both recorded in the file. ULP distance is the
+  mistake `mne-parity.test.ts` already documents: a declaration with bounds of 0.0002 and -4827
+  sits 5.4 million ULP from the smaller one while being physically indistinguishable from it.
+  Relative error fails at the other end — a bound of 0.001 beside one of 99,999 shows a relative
+  error of 1.3e-3 for an absolute error far below anything the file can express. Quantisation steps
+  are the only unit in which "you could not notice this" is a statement about the recording, and
+  they are what the rest of the page already uses. The measured worst is about 2e-5 of a step, and
+  0.4.342's note has been corrected from a relative figure to that one.
+- The property found a real constraint on its first run: a physical bound lives in an
+  eight-character field, so `1e-6` is written `0.000000` and comes back degenerate. Everything is
+  now measured against the parsed header rather than the numbers handed to the writer, which makes
+  this a property about declarations a file can actually hold.
+
+## 0.4.342
+
+- **Corrected** a claim on `physical-values.md` that read as general and holds only for the range
+  it introduces. "The two forms agree at the endpoints and disagree in the last place elsewhere"
+  is true of the tabulated -500..500 over -32768..32767, and false of most declarations: the
+  EDFlib expression derives an offset from `physicalMaximum / bitValue` and multiplies back, and
+  nothing in that round trip has to land on the declared bound. A signal declaring `1`..`1000`
+  over `0`..`4095` converts its digital minimum to `1.000000000000092`.
+- Not a defect in edfcore — EDFlib does the same and reproducing it bit for bit is the entire
+  point — but a reader who took the sentence generally would derive a plot axis from `toPhysical`
+  at the extremes and get a bound an ulp or two off. The sentence is now scoped to its range, and
+  a note gives the general case and points at `physicalRangeOf`, which reads the declared fields
+  and is exact.
+- Checked from both sides: the two quoted values are produced, the tabulated range still lands
+  exactly, and `physicalRangeOf` returns the declared bounds on all three.
+
 ## 0.4.341
 
 - **Added** an execution of the read pattern `large-files.md` measured. The page prints four byte

package/package.json

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