edfcore 0.4.411 → 0.4.412

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
109
109
  readonly reserved: 224;
110
110
  };
111
111
  /** Published package version. Kept in sync with package.json by a test. */
112
- export declare const VERSION = "0.4.411";
112
+ export declare const VERSION = "0.4.412";
113
113
  //# sourceMappingURL=constants.d.ts.map
package/dist/constants.js CHANGED
@@ -79,5 +79,5 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
79
79
  reserved: 224,
80
80
  };
81
81
  /** Published package version. Kept in sync with package.json by a test. */
82
- export const VERSION = '0.4.411';
82
+ export const VERSION = '0.4.412';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,23 @@ alone does not tell you whether you were affected.
6
6
  edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
7
7
  defect; those are called out below.
8
8
 
9
+ ## 0.4.412
10
+
11
+ - **Added** tests for four header fields that are all finite and imply a gain that is not. An EDF
12
+ physical bound is eight bytes of ASCII, which is room for an exponent, so a physical range can
13
+ underflow against the digital range — `0` to `5E-324` over -1..1 puts `bitValue` at zero and
14
+ `offset` at infinity — or overflow it, where `-9.9E307` to `9.9E307` exceeds float64 before the
15
+ division happens.
16
+ - Nothing about such a file looks wrong. The header parses, every field is in range for its width,
17
+ and a reader who does not check `signal.scale` gets a column of `NaN` where microvolts should be
18
+ — which plots as an empty panel, or silently poisons a mean. The scale is refused exactly as the
19
+ obvious degeneracies are, and `decodeDigital` keeps working, which is the whole reason
20
+ `toPhysical` is a separate call.
21
+ - A signal declaring a negative `samplesPerRecord` is the other shape of "parses and cannot be
22
+ used", and it is fatal rather than diagnosed: every later signal's byte offset inside a record is
23
+ a running sum of that field, so a negative one does not make one signal wrong, it makes every
24
+ signal after it point at the wrong bytes.
25
+
9
26
  ## 0.4.411
10
27
 
11
28
  - **Added** tests for the envelope of the files and selections a viewer produces by accident.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.411",
3
+ "version": "0.4.412",
4
4
  "description": "Modern, typed, zero-dependency reader for EDF, EDF+, BDF and BDF+ biosignal files. Works in browsers and Node with true random access.",
5
5
  "keywords": [
6
6
  "edf",
package/src/constants.ts CHANGED
@@ -93,4 +93,4 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
93
93
  } as const;
94
94
 
95
95
  /** Published package version. Kept in sync with package.json by a test. */
96
- export const VERSION = '0.4.411';
96
+ export const VERSION = '0.4.412';