edfcore 0.4.318 → 0.4.319

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
109
109
  readonly reserved: 224;
110
110
  };
111
111
  /** Published package version. Kept in sync with package.json by a test. */
112
- export declare const VERSION = "0.4.318";
112
+ export declare const VERSION = "0.4.319";
113
113
  //# sourceMappingURL=constants.d.ts.map
package/dist/constants.js CHANGED
@@ -79,5 +79,5 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
79
79
  reserved: 224,
80
80
  };
81
81
  /** Published package version. Kept in sync with package.json by a test. */
82
- export const VERSION = '0.4.318';
82
+ export const VERSION = '0.4.319';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,19 @@ alone does not tell you whether you were affected.
6
6
  edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
7
7
  defect; those are called out below.
8
8
 
9
+ ## 0.4.319
10
+
11
+ - **Added** a check that the three cross-implementation harnesses claim on the page exactly what
12
+ they assert in code. `physical-values.md` tabulates them precisely because they are not equally
13
+ strong — pyEDFlib values bit for bit, pyEDFlib onsets exact to the tick, MNE only to 1e-12
14
+ relative and explicitly not bit-exact — and that is a claim about the tests, so no test could
15
+ previously be wrong about it in a way that showed.
16
+ - The MNE bound is now read out of `mne-parity.test.ts` rather than restated: loosening that one
17
+ constant for a flaky run would otherwise leave the page publishing a parity claim a thousand
18
+ times stronger than the one being made, with the whole suite still green. The two exact rows are
19
+ checked for the ABSENCE of a tolerance, with comments stripped first — `golden-values.test.ts`
20
+ explains at length why it does not use one, and the explanation must not vouch for itself.
21
+
9
22
  ## 0.4.318
10
23
 
11
24
  - **Strengthened** the check that the golden fixtures can tell the two scaling forms apart.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.318",
3
+ "version": "0.4.319",
4
4
  "description": "Modern, typed, zero-dependency reader for EDF, EDF+, BDF and BDF+ biosignal files. Works in browsers and Node with true random access.",
5
5
  "keywords": [
6
6
  "edf",
package/src/constants.ts CHANGED
@@ -93,4 +93,4 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
93
93
  } as const;
94
94
 
95
95
  /** Published package version. Kept in sync with package.json by a test. */
96
- export const VERSION = '0.4.318';
96
+ export const VERSION = '0.4.319';