edfcore 0.6.43 → 0.6.45

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

package/docs/CHANGELOG.md

@@ -6,6 +6,41 @@ 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.6.45
+
+- **Fixed** a claim in `large-files.md`: that building a complete index "is the only price in the
+  library proportional to the file". It is the only one a *reading* call can spring on you — every
+  other cost on that page follows the window you asked for — and that is the sentence the page now
+  makes. It is not the only one in the library.
+- `validateRecording` has two of its own, and `validation.md` describes both on the same site.
+  `scanSamples` reads every sample of every record: `edfcore validate` on the 48 MB polysomnogram
+  in the test corpus reports `scanned 2650 records, read 48,336,000 bytes`, and the validation page
+  says that on a 13 GiB BDF it is every record. On a discontinuous file the sweep also makes the
+  same traversal `buildRecordIndex` makes, for the same onsets, unless it is handed a complete
+  index — which is what the `index` option is for, and why the same page puts it as "conformance
+  costs one traversal rather than two", a sentence that presupposes there being two.
+- What the wrong one cost: a reader taking "the only price" at face value budgets a conformance
+  sweep as free. The two pages disagreed, and the cheaper claim was the one on the page about cost.
+- The paragraph now also says what neither price does unasked. Without `scanSamples`, validating a
+  continuous file reports `recordsScanned: 0` and `bytesRead: 0`, and a test measures all four
+  cells rather than quoting either page.
+
+## 0.6.44
+
+- **Fixed** a claim in `edf-format.md`: that onsets "parsed digit by digit are exact, and
+  `parseFloat` is the only thing that makes them inexact". The first half is what `tal/ticks.ts`
+  exists for. The second half is broken by the grammar printed nine lines above it — `Onset =
+  ("+" / "-") 1*DIGIT [ "." 1*DIGIT ]` puts no bound on the fraction, and a writer emitting full
+  double precision produces `+1234.5678901234`.
+- edfcore counts in 100 ns, so the eighth fractional digit onward is dropped: `+0.12345678` is
+  `1234567` ticks and `+1.00000009` is one second exactly, with `ok: true` either way, because a
+  resolution is not a parse failure. That is the right design — it is the unit `onsetTicks` and
+  every window in the library are counted in — and the wrong sentence. A reader told `parseFloat`
+  is the only lossy step concludes the digits survive, and `EdfAnnotation.onsetRaw`, the field that
+  actually keeps them, has no reason to exist.
+- No behaviour changed. The page now names both places precision goes, and points at `onsetRaw` and
+  `durationRaw` for the digits as written.
+
 ## 0.6.43
 
 - **Fixed** a claim in `cli.md`, in `cli-run.ts` and in the test that repeated it: that the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.6.43",
+  "version": "0.6.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.6.43';
+export const VERSION = '0.6.45';