edfcore 0.5.21 → 0.5.23

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.5.21";
+export declare const VERSION = "0.5.23";
 //# 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.5.21';
+export const VERSION = '0.5.23';
 //# sourceMappingURL=constants.js.map

package/docs/CHANGELOG.md

@@ -6,6 +6,53 @@ 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.5.23
+
+- **Added** the conformance report `validation.md` prints, printed. That page ends with a whole
+  program and the output it produces on one file: a header line, a summary line, two diagnostic
+  blocks, and two per-signal stat lines. `validate-page.test.ts` covers the code table higher up and
+  `validation-report.test.ts` the `report.ok` rule; the transcript — the thing a reader compares
+  their own terminal against — was prose.
+- The stat lines are the reason it is worth running. They are not printed by edfcore at all: the
+  page composes them from `report.signalStats`, `getSignal` and arithmetic of its own, and the
+  paragraph under them is an argument built on the result. "The first channel uses half a percent of
+  the range its header declares, which is legal and lossy." "81,806 of its 153,600 samples fall
+  outside the range the header declares, so that declaration is wrong." A change to
+  `observedDigitalMin`, `outOfDigitalRangeCount` or `sampleCount` would leave the page arguing from
+  figures the library no longer produces.
+- The snippet is now run rather than restated: the stat lines are built by the same expression the
+  page shows and compared against the page's own text character for character, along with the
+  summary line's `no errors, 4 diagnostics, 600 records and 650400 bytes read`.
+- The fixture is built to the page's description and its geometry falls out of the transcript —
+  600 one-second records at 650,400 bytes is 1,084 a record, which is two 256-sample channels and a
+  30-sample annotation region, and 153,600 samples is 600 x 256. The one number that cannot be
+  derived is how many fall outside; that is read off the page and built into the sample generator,
+  which is what makes the count an assertion about the counter rather than about the waveform.
+- The last sentence of the paragraph is checked too. "Any consumer that clamps to it returns
+  different numbers for this file than edfcore does" — a read returns the bytes as written, at
+  -150..150 outside the declared -100..100, and `clampToDigitalRange` returns something else.
+
+## 0.5.22
+
+- **Added** the scrolling table on `large-files.md`, measured. `large-files-cost.test.ts` runs the
+  two tables above it — what opening costs, and what one ten-second window costs. This is the third,
+  and the one that carries an argument rather than a figure: thirty consecutive ten-second windows
+  over an 8-channel EDF+C cost 30 reads and 1,246,800 bytes from a bare source, and 1 read of
+  1,048,576 bytes through `cachedSource`.
+- The sentence under it is why the table is there. "Removing `cachedSource` changes the number of
+  reads and nothing else" is a debugging instruction — if a bug appears with the cache in place,
+  delete the wrapper; if it survives, the cache was not involved — and it is only as good as the
+  "nothing else". The two runs are now compared sample for sample, all 153,600 of them, with the
+  count of non-zero values asserted too: a fixture decoding to zeros throughout would make an exact
+  match mean nothing.
+- The page also says which block the single read is — "the second 1 MiB block. The first was already
+  resident because the header read at open pulled it in, so the reads that come with opening a file
+  are not wasted." That is checked as an offset, because it is what a reader plans an HTTP range
+  budget around, and because a cache issuing one read of the right size at the wrong place would
+  satisfy every other assertion here.
+- The neighbouring claim goes with it: thirty ten-second windows cost thirty reads, and one
+  300-second window over the same records costs one, for the same 1,246,800 bytes.
+
 ## 0.5.21
 
 - **Added** the census `reading-signals.md` takes of the derived sample rate. `samplesPerRecord` is

package/package.json

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