edfcore 0.2.52 → 0.2.54

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,28 @@ 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.54
10
+
11
+ - **Added** the random-access claim, measured over HTTP on the real 48 MB recording. A `fetch`
12
+ double serves byte ranges out of the file and counts what it hands over; reading a 30-second
13
+ window twelve hours in costs **under 64 KB**, and opening the file costs under a five-hundredth
14
+ of it. This is the property the whole package is built around, checked over the transport that
15
+ makes it matter — a reader that has to download the file first cannot do it at all, and until now
16
+ it was only demonstrated on fixtures small enough that the distinction did not exist.
17
+
18
+ ## 0.2.53
19
+
20
+ - **Added** a check that `validateRecording`'s sample scan sees what pyEDFlib sees. The observed
21
+ digital minimum and maximum are the only numbers in a validation report derived from every sample
22
+ rather than from the header, so they are the ones worth checking against another reader — and a
23
+ sampled window cannot check them, because the extremes of a 22-hour recording are very unlikely
24
+ to fall inside the 256 samples the goldens record. The whole-signal extremes now come from
25
+ pyEDFlib, across all five corpus files.
26
+ - Also pins `outOfDigitalRangeCount` against those extremes. It is a claim about the DECLARATION
27
+ rather than about the samples — a non-zero count means the header's digital range is wrong, and
28
+ edfcore never clamps — so recomputing whether any sample could be outside the declared bounds
29
+ from pyEDFlib's own observations is the independent form of that check.
30
+
9
31
  ## 0.2.52
10
32
 
11
33
  - **Added** streaming equivalence on the 22-hour recording. The documented claim is that a streamed
@@ -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.52";
112
+ export declare const VERSION = "0.2.54";
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.52';
82
+ export const VERSION = '0.2.54';
83
83
  //# sourceMappingURL=constants.js.map
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.2.52",
3
+ "version": "0.2.54",
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.52';
96
+ export const VERSION = '0.2.54';