edfcore 0.2.43 → 0.2.45

package/CHANGELOG.md

@@ -6,6 +6,37 @@ 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.44
+
+- **Added** annotation parity against pyEDFlib — the other axis, and the one edfcore has got wrong
+  most. The scaling harness checks arithmetic; this checks WHICH AXIS an onset is on. Six releases
+  were variants of "one function used the nominal grid while the rest used the record's true
+  onset", and every one was found by comparing edfcore against edfcore. The property test added in
+  0.2.25 makes that internal agreement a hard invariant; this makes it an external one, which is a
+  different kind of evidence — a shared misreading of the format satisfies the first and fails
+  here. Onsets match to the tick, and edfcore reports no diagnostic at all on a file a reference
+  writer produced.
+- The generator refuses to record fewer annotations than it wrote. `writeAnnotation` silently drops
+  an event that does not fit the region pyEDFlib sized, and the first run lost one — a golden file
+  recorded from that would have made the parity test compare an incomplete set and pass while doing
+  it.
+
+## 0.2.43
+
+- **Added** parity against MNE — a second, independent reader. pyEDFlib and edfcore both descend
+  from EDFlib's arithmetic, so agreement between them shows edfcore copied it correctly rather than
+  that the answer is right; MNE is a different implementation.
+- The claim is deliberately WEAKER than the pyEDFlib one and says so. MNE returns SI units, so a
+  microvolt channel arrives divided by 1e6 and that division is lossy — the two cannot be
+  bit-identical, and asserting otherwise would be asserting something false. The bound is 1e-12
+  relative, about a hundred times the worst observed and ten orders of magnitude below the
+  quantisation step of any real recording. Bit-parity remains claimed for pyEDFlib alone.
+- The bound is RELATIVE rather than an ULP count, which was the first instinct and is the wrong
+  measure: near 1e-6 the same relative rounding spans far more representable floats than it does
+  near 100, so an ULP bound tight enough to be meaningful at one magnitude is meaningless at the
+  other. Channels MNE does not rescale — it leaves `degC` alone — are excluded rather than pushed
+  through a factor that would make the comparison an artefact of the test.
+
 ## 0.2.42
 
 - **Added** three cases to the pyEDFlib parity harness, chosen for where the two scaling

package/README.md

@@ -299,9 +299,15 @@ back with pyEDFlib, and records every sample as its exact IEEE-754 bit pattern;
 `tests/corpus/golden/` was produced by edfcore. Substituting the numerically better textbook
 expression fails it on 140 of 256 samples — which is why the EDFlib form is pinned.
 
-**Still open before 1.0.** The same harness against MNE, and validation across public corpora
-(sleep-edfx, CHB-MIT, the BioSemi and edfplus.info test files). Those claims are not made here
-until a test produces them.
+**MNE, as of 0.2.43.** edfcore agrees with MNE to within 1e-12 relative — a weaker claim than the
+one above, and deliberately so. MNE returns SI units, so a microvolt channel arrives divided by
+1e6, and that division is lossy; the residue is MNE's unit conversion rather than a disagreement
+about the sample. Bit-parity is claimed for pyEDFlib alone. Both readers also agree with the file's
+own declaration about POLARITY on a negative-gain channel, which a value comparison alone could not
+establish.
+
+**Still open before 1.0.** Validation across public corpora (sleep-edfx, CHB-MIT, the BioSemi and
+edfplus.info test files). That claim is not made here until a test produces it.
 
 **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.43";
+export declare const VERSION = "0.2.45";
 //# 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.43';
+export const VERSION = '0.2.45';
 //# sourceMappingURL=constants.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.2.43",
+  "version": "0.2.45",
   "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.43';
+export const VERSION = '0.2.45';