edfcore 0.2.44 → 0.2.46

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.
package/CHANGELOG.md CHANGED
@@ -6,6 +6,33 @@ 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.2.45
10
+
11
+ - **Added** `scripts/golden/README.md`: how to regenerate every parity fixture, and — more usefully
12
+ — what each of the three harnesses actually claims and how strong that claim is. Bit-for-bit for
13
+ pyEDFlib physical values, exact-to-the-tick for pyEDFlib annotation onsets, 1e-12 relative for
14
+ MNE, with the reason the last one is weaker stated where someone would otherwise assume it was an
15
+ oversight. Also records the rule for adding a case: pick where the two candidate expressions
16
+ diverge or where a mistake would be least visible, and remember that a value comparison alone
17
+ cannot catch a mistake both libraries make.
18
+ - **Documented** the same table on the physical-values page, so a reader who never opens the
19
+ repository sees which claims are load-bearing and which are approximate.
20
+
21
+ ## 0.2.44
22
+
23
+ - **Added** annotation parity against pyEDFlib — the other axis, and the one edfcore has got wrong
24
+ most. The scaling harness checks arithmetic; this checks WHICH AXIS an onset is on. Six releases
25
+ were variants of "one function used the nominal grid while the rest used the record's true
26
+ onset", and every one was found by comparing edfcore against edfcore. The property test added in
27
+ 0.2.25 makes that internal agreement a hard invariant; this makes it an external one, which is a
28
+ different kind of evidence — a shared misreading of the format satisfies the first and fails
29
+ here. Onsets match to the tick, and edfcore reports no diagnostic at all on a file a reference
30
+ writer produced.
31
+ - The generator refuses to record fewer annotations than it wrote. `writeAnnotation` silently drops
32
+ an event that does not fit the region pyEDFlib sized, and the first run lost one — a golden file
33
+ recorded from that would have made the parity test compare an incomplete set and pass while doing
34
+ it.
35
+
9
36
  ## 0.2.43
10
37
 
11
38
  - **Added** parity against MNE — a second, independent reader. pyEDFlib and edfcore both descend
@@ -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.2.44";
112
+ export declare const VERSION = "0.2.46";
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.2.44';
82
+ export const VERSION = '0.2.46';
83
83
  //# sourceMappingURL=constants.js.map
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.2.44",
3
+ "version": "0.2.46",
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.2.44';
96
+ export const VERSION = '0.2.46';