edfcore 0.2.53 → 0.2.55
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 +22 -0
- package/dist/constants.d.ts +1 -1
- package/dist/constants.js +1 -1
- package/package.json +1 -1
- package/src/constants.ts +1 -1
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.55
|
|
10
|
+
|
|
11
|
+
- **Added** CLI coverage against the real corpus. Every existing CLI fixture is a few hundred bytes
|
|
12
|
+
written by this project, which checks the decisions — exit codes, flags, output shape — and
|
|
13
|
+
cannot check what a command does when pointed at 48 MB of clinical recording, or at a scoring
|
|
14
|
+
file with 154 events and a record duration of zero.
|
|
15
|
+
- The load-bearing one: **`edfcore validate` exits 0 on a real recording from a real sleep lab.**
|
|
16
|
+
That is what makes the command usable as a CI gate at all; a validator that fails real files is
|
|
17
|
+
worse than no validator, because it teaches people to ignore it.
|
|
18
|
+
- Also pins that the sleep-edfx PSG is plain **EDF, not EDF+** — it carries an `Event marker` data
|
|
19
|
+
channel rather than an annotations channel, which is how that dataset splits signals from
|
|
20
|
+
scoring. I had assumed EDF+ writing the test and the file said otherwise.
|
|
21
|
+
|
|
22
|
+
## 0.2.54
|
|
23
|
+
|
|
24
|
+
- **Added** the random-access claim, measured over HTTP on the real 48 MB recording. A `fetch`
|
|
25
|
+
double serves byte ranges out of the file and counts what it hands over; reading a 30-second
|
|
26
|
+
window twelve hours in costs **under 64 KB**, and opening the file costs under a five-hundredth
|
|
27
|
+
of it. This is the property the whole package is built around, checked over the transport that
|
|
28
|
+
makes it matter — a reader that has to download the file first cannot do it at all, and until now
|
|
29
|
+
it was only demonstrated on fixtures small enough that the distinction did not exist.
|
|
30
|
+
|
|
9
31
|
## 0.2.53
|
|
10
32
|
|
|
11
33
|
- **Added** a check that `validateRecording`'s sample scan sees what pyEDFlib sees. The observed
|
package/dist/constants.d.ts
CHANGED
|
@@ -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.
|
|
112
|
+
export declare const VERSION = "0.2.55";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/package.json
CHANGED
package/src/constants.ts
CHANGED