edfcore 0.4.410 → 0.4.412

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

package/docs/CHANGELOG.md

@@ -6,6 +6,40 @@ 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.4.412
+
+- **Added** tests for four header fields that are all finite and imply a gain that is not. An EDF
+  physical bound is eight bytes of ASCII, which is room for an exponent, so a physical range can
+  underflow against the digital range — `0` to `5E-324` over -1..1 puts `bitValue` at zero and
+  `offset` at infinity — or overflow it, where `-9.9E307` to `9.9E307` exceeds float64 before the
+  division happens.
+- Nothing about such a file looks wrong. The header parses, every field is in range for its width,
+  and a reader who does not check `signal.scale` gets a column of `NaN` where microvolts should be
+  — which plots as an empty panel, or silently poisons a mean. The scale is refused exactly as the
+  obvious degeneracies are, and `decodeDigital` keeps working, which is the whole reason
+  `toPhysical` is a separate call.
+- A signal declaring a negative `samplesPerRecord` is the other shape of "parses and cannot be
+  used", and it is fatal rather than diagnosed: every later signal's byte offset inside a record is
+  a running sum of that field, so a negative one does not make one signal wrong, it makes every
+  signal after it point at the wrong bytes.
+
+## 0.4.411
+
+- **Added** tests for the envelope of the files and selections a viewer produces by accident.
+  `readEnvelope` exists to draw a recording at pixel width, so its caller is a UI: the signal
+  indices come from a multi-select, the bucket count from a canvas width, and the file from
+  whatever was dropped on the page.
+- **The same signal asked for twice** — a multi-select that appends on click, a "select all" over a
+  list that already had one checked — is now pinned as one series in order of first mention, and
+  costing what asking once costs. **A signal with no samples in a record** draws as an empty series
+  rather than failing the whole envelope, so a "plot everything" loop still gets a slot for every
+  channel it named. **A file whose records do not advance in time** buckets without dividing by the
+  duration: `readEnvelope` divides the samples evenly, because there are no timestamps to place
+  them along, and `readEnvelopeAtResolution` gets one bucket, because the span is zero.
+- A fourth case is a request rather than a file: a `secondsPerBucket` finer than one tick has no
+  whole-tick answer, and asking for one bucket per tick and letting the fold clamp to one bucket per
+  sample was a comment with nothing behind it.
+
 ## 0.4.410
 
 - **Added** a check that nothing on the site tells a crawler to stay away. `robots.txt.ts` opens

package/package.json

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