edfcore 0.2.57 → 0.2.60

package/CHANGELOG.md

@@ -6,6 +6,44 @@ alone does not tell you whether you were affected.
 edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
 defect; those are called out below.
 
+## 0.2.59
+
+- **Added** `calib.rec` from edfplus.info — the last corpus the README named. It was written by
+  **Bob Kemp, who wrote the EDF specification**, expressly to check that a reader gets amplitude
+  and POLARITY right, which makes it the closest thing this format has to a conformance test.
+- It is the only fixture in the suite whose expected values come from neither edfcore nor another
+  library, but from the file's own design. Its declared range is ±100 µV over ±4096 digital units,
+  so the gain is 25/1024 — a small integer over a power of two, exactly representable in float64 —
+  and the offset is exactly zero. Digital `-2048` is therefore exactly `-50 µV`, checkable from the
+  header by hand, and every level in the file is asserted with no tolerance.
+- The polarity assertions are the point. A reader that swapped the physical bounds returns the
+  right magnitudes with the wrong sign — plausible microvolts that invert the clinical reading of
+  the trace — so the extremes are asserted as signed values tied to the digital codes that produced
+  them, not as an amplitude.
+- I first wrote the gain up as "a power of two". It is not; log2 of it is -5.356. The corrected
+  claim and a test pinning the distinction are both in the file, so nobody simplifies it back.
+- The coverage guard added in 0.2.50 earned its place on the way: it failed this release because
+  the new corpus file had no parity golden yet. That is exactly the drift it exists to catch, and
+  it caught it before the release rather than after.
+
+## 0.2.58
+
+- **Added** CHB-MIT to the corpus, closing a gap the README has named since 0.1. It is chosen to be
+  UNLIKE sleep-edfx rather than to add volume: 23 channels at a uniform 256 Hz in one-second
+  records, recorded in 2010 at another institution on other equipment, against 7 channels at mixed
+  rates in 30-second records from 1989. Every real file in this suite came from one dataset until
+  now. Same bit-for-bit parity with pyEDFlib across all 23 channels.
+- It also supplies something no fixture in this project had: **a montage that names one derivation
+  twice.** `T8-P8` appears at index 14 and index 22, and the two carry identical samples — verified
+  against pyEDFlib over the whole hour rather than assumed; I had written the test expecting them
+  to differ. `EdfAmbiguousChannelError` had until now only ever been raised against a fixture
+  written to raise it.
+- That identity makes the refusal matter more, not less. If `getSignal` picked one arbitrarily, no
+  comparison of the returned numbers could reveal which it picked, so a caller would never learn
+  the question had two answers. The error is the only signal there is.
+- Downloaded on demand under the Open Data Commons Attribution License v1.0, hash-verified, never
+  redistributed — the same terms as every other corpus entry.
+
 ## 0.2.57
 
 - **Documented** what the corpus work of 0.2.49-0.2.55 actually established. The README's

package/README.md

@@ -334,8 +334,24 @@ state you are in, because a skipped test and a passing one look identical in a s
 npm run corpus:fetch
 ```
 
-**Still open before 1.0.** CHB-MIT, and the edfplus.info conformance files. Those are not claimed
-here until a test produces them.
+**CHB-MIT, as of 0.2.58.** A second real clinical recording, deliberately unlike the first: 23
+channels at a uniform 256 Hz in one-second records, recorded in 2010 at another institution, where
+sleep-edfx is 7 channels at mixed rates in 30-second records from 1989. Same bit-for-bit parity. It
+also supplies something no synthetic fixture here had — a montage that names one derivation twice,
+which is what `EdfAmbiguousChannelError` exists for and had until now only ever been raised against
+a fixture written to raise it.
+
+**The format author's own calibration file, as of 0.2.59.** `calib.rec` was written by Bob Kemp —
+who wrote the EDF specification — expressly to check that a reader gets amplitude *and polarity*
+right. It is the only fixture here whose expected values come from neither edfcore nor another
+library but from the file's own design: its gain is 25/1024, exactly representable in binary, so
+digital `-2048` is exactly `-50 µV` and a human can check it from the header by hand. edfcore
+returns the exact levels, and the negative extreme comes from the negative code — which is the
+whole point, since a reader that swapped the bounds would return plausible microvolts of the wrong
+sign and invert the clinical reading of the trace.
+
+**Still open before 1.0.** Nothing named. The remaining work is API, not verification — see the
+0.3 note in [CHANGELOG.md](https://github.com/tayal-sarthak/edfcore/blob/main/CHANGELOG.md).
 
 **Shipped since 0.1.6.** Min/max envelope decimation (`readEnvelope`,
 `readEnvelopeAtResolution`). BioSemi Status-byte helpers (`readTriggers`). Streaming iteration

package/dist/constants.d.ts

@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
     readonly reserved: 224;
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export declare const VERSION = "0.2.57";
+export declare const VERSION = "0.2.60";
 //# sourceMappingURL=constants.d.ts.map

package/dist/constants.js

@@ -79,5 +79,5 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
     reserved: 224,
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.2.57';
+export const VERSION = '0.2.60';
 //# sourceMappingURL=constants.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.2.57",
+  "version": "0.2.60",
   "description": "Modern, typed, zero-dependency reader for EDF, EDF+, BDF and BDF+ biosignal files. Works in browsers and Node with true random access.",
   "keywords": [
     "edf",

package/src/constants.ts

@@ -93,4 +93,4 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
 } as const;
 
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.2.57';
+export const VERSION = '0.2.60';