edfcore 0.6.74 → 0.6.75

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.6.74";
112
+ export declare const VERSION = "0.6.75";
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.6.74';
82
+ export const VERSION = '0.6.75';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,20 @@ 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.6.75
10
+
11
+ - **Fixed** the inspector deciding whether a file needs a complete index by comparing
12
+ `spanSeconds` with `coveredSeconds`. `EdfTimeline` says which fields carry that verdict:
13
+ "`spanTicks === coveredTicks` is the two-probe contiguity verdict, and the ticks are what it
14
+ must be asked of", because the seconds are float64 conversions and two tick counts can round to
15
+ one float once the span is large enough that an ulp exceeds a tick.
16
+ - Asked of the floats, such a file answers "contiguous", `buildRecordIndex` is skipped, and the
17
+ page draws a discontinuous recording on the nominal grid — the silently wrong timeline the
18
+ library exists to refuse, on the page that is its central claim made checkable. The same
19
+ comparison was fixed inside `resolveTimeWindow` in 0.3.4 and the type's docblock records it.
20
+ - The test demonstrates the collision rather than arguing it, and shows the two staying apart at
21
+ an ordinary scale, which is why this could sit there.
22
+
9
23
  ## 0.6.74
10
24
 
11
25
  - **Fixed** `sample-locate.ts` describing a repeated record onset as something "edfcore reports
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.6.74",
3
+ "version": "0.6.75",
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.6.74';
96
+ export const VERSION = '0.6.75';