edfcore 0.2.57 → 0.2.58
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 +18 -0
- package/README.md +9 -2
- 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,24 @@ 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.58
|
|
10
|
+
|
|
11
|
+
- **Added** CHB-MIT to the corpus, closing a gap the README has named since 0.1. It is chosen to be
|
|
12
|
+
UNLIKE sleep-edfx rather than to add volume: 23 channels at a uniform 256 Hz in one-second
|
|
13
|
+
records, recorded in 2010 at another institution on other equipment, against 7 channels at mixed
|
|
14
|
+
rates in 30-second records from 1989. Every real file in this suite came from one dataset until
|
|
15
|
+
now. Same bit-for-bit parity with pyEDFlib across all 23 channels.
|
|
16
|
+
- It also supplies something no fixture in this project had: **a montage that names one derivation
|
|
17
|
+
twice.** `T8-P8` appears at index 14 and index 22, and the two carry identical samples — verified
|
|
18
|
+
against pyEDFlib over the whole hour rather than assumed; I had written the test expecting them
|
|
19
|
+
to differ. `EdfAmbiguousChannelError` had until now only ever been raised against a fixture
|
|
20
|
+
written to raise it.
|
|
21
|
+
- That identity makes the refusal matter more, not less. If `getSignal` picked one arbitrarily, no
|
|
22
|
+
comparison of the returned numbers could reveal which it picked, so a caller would never learn
|
|
23
|
+
the question had two answers. The error is the only signal there is.
|
|
24
|
+
- Downloaded on demand under the Open Data Commons Attribution License v1.0, hash-verified, never
|
|
25
|
+
redistributed — the same terms as every other corpus entry.
|
|
26
|
+
|
|
9
27
|
## 0.2.57
|
|
10
28
|
|
|
11
29
|
- **Documented** what the corpus work of 0.2.49-0.2.55 actually established. The README's
|
package/README.md
CHANGED
|
@@ -334,8 +334,15 @@ state you are in, because a skipped test and a passing one look identical in a s
|
|
|
334
334
|
npm run corpus:fetch
|
|
335
335
|
```
|
|
336
336
|
|
|
337
|
-
**
|
|
338
|
-
|
|
337
|
+
**CHB-MIT, as of 0.2.58.** A second real clinical recording, deliberately unlike the first: 23
|
|
338
|
+
channels at a uniform 256 Hz in one-second records, recorded in 2010 at another institution, where
|
|
339
|
+
sleep-edfx is 7 channels at mixed rates in 30-second records from 1989. Same bit-for-bit parity. It
|
|
340
|
+
also supplies something no synthetic fixture here had — a montage that names one derivation twice,
|
|
341
|
+
which is what `EdfAmbiguousChannelError` exists for and had until now only ever been raised against
|
|
342
|
+
a fixture written to raise it.
|
|
343
|
+
|
|
344
|
+
**Still open before 1.0.** The edfplus.info conformance files. Not claimed here until a test
|
|
345
|
+
produces them.
|
|
339
346
|
|
|
340
347
|
**Shipped since 0.1.6.** Min/max envelope decimation (`readEnvelope`,
|
|
341
348
|
`readEnvelopeAtResolution`). BioSemi Status-byte helpers (`readTriggers`). Streaming iteration
|
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.58";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/package.json
CHANGED
package/src/constants.ts
CHANGED