edfcore 0.5.2 → 0.5.4

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

package/docs/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.5.4
+
+- **Added** the rest of the block `discontinuous.md` prints for `index.segments` and `index.gaps`.
+  The page prints three objects in full — fifteen fields between them — and the tests checked four:
+  the two record ranges and the two `startSeconds`. Each segment's own `index`, its `startTicks`,
+  its `endSeconds`, and the gap's `beforeSegmentIndex`/`afterSegmentIndex` were printed and never
+  run.
+- Those are the fields most worth running. `startTicks` is the exact value the whole time model
+  rests on and the only one a reader cannot check by eye against the diagram above it;
+  `endSeconds` is derived from two other printed numbers, so a page printing all three can
+  contradict itself while every individual number matches something; and the gap's two segment
+  indices are what make it a gap between a specific pair rather than a free-floating interval.
+- The fields are enumerated from the page rather than listed in the test — the block is parsed into
+  objects and each `name: value` compared against the object the scan produced — so a field added to
+  the block is checked by having been printed. Adding `1n` to a segment's `startTicks` fails it.
+- The derived fields are also checked against each other rather than only against the page:
+  `endSeconds` is `startSeconds + durationSeconds` on every segment and gap, and the gap runs from
+  where the earlier segment ends to where the later one starts, in ticks.
+
+## 0.5.3
+
+- **Added** the claim `api-reading.md` makes in one clause: "that makes `startSeconds` trustworthy
+  on an EDF+D file even when the index is only probed". A chunk decodes its start from the
+  timekeeping TALs in its own bytes, so an index that has read two records cannot make it wrong.
+- It is worth checking because the cheap answer is available and wrong. Every record has a nominal
+  position, `start + r * recordDuration`, that a reader can compute without touching the file — and
+  on a contiguous file it is right. On an EDF+D file it is short by every gap before it, which is
+  the number nobody notices: the samples are fine, the record numbers are fine, and only the clock
+  has moved.
+- The fixture puts a seven-second hole after record 3 and reads a chunk on each side of it through
+  an index that has never looked. The far chunk is asserted not to report the nominal position, to
+  report the true one in ticks, and to report the same value the scanned index does — which is what
+  "trustworthy" has to mean. The near chunk reports a position where the two answers coincide,
+  which is why testing only that half would conclude the nominal grid was fine.
+- `precededByGap` is asserted `undefined` on the same chunk, deliberately. It is the field a probed
+  index genuinely cannot fill, and the one `mergeChunks` stopped keying its refusal on in 0.2.19 —
+  before that, two chunks a minute apart on an EDF+D file joined in silence.
+
 ## 0.5.2
 
 - **Added** the map of how far `strict` reaches on a read, which has three cells rather than the

package/package.json

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