edfcore 0.4.340 → 0.4.342

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

package/docs/CHANGELOG.md

@@ -6,6 +6,35 @@ 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.342
+
+- **Corrected** a claim on `physical-values.md` that read as general and holds only for the range
+  it introduces. "The two forms agree at the endpoints and disagree in the last place elsewhere"
+  is true of the tabulated -500..500 over -32768..32767, and false of most declarations: the
+  EDFlib expression derives an offset from `physicalMaximum / bitValue` and multiplies back, and
+  nothing in that round trip has to land on the declared bound. A signal declaring `1`..`1000`
+  over `0`..`4095` converts its digital minimum to `1.000000000000092`.
+- Not a defect in edfcore — EDFlib does the same and reproducing it bit for bit is the entire
+  point — but a reader who took the sentence generally would derive a plot axis from `toPhysical`
+  at the extremes and get a bound an ulp or two off. The sentence is now scoped to its range, and
+  a note gives the general case and points at `physicalRangeOf`, which reads the declared fields
+  and is exact.
+- Checked from both sides: the two quoted values are produced, the tabulated range still lands
+  exactly, and `physicalRangeOf` returns the declared bounds on all three.
+
+## 0.4.341
+
+- **Added** an execution of the read pattern `large-files.md` measured. The page prints four byte
+  ranges and a total for opening a 29,925,760-byte EDF+C, and the file is now rebuilt from the
+  sentence describing it — eight channels at 256 Hz, 7,200 one-second records — and opened through
+  a recording source, so all four offsets and lengths have to match, in order.
+- Rebuilding it is itself a check on having read the description right: the annotation channel is
+  not in the parenthesis and is implied by the record size, since eight channels at 256 samples is
+  4,096 bytes and the page says 4,156. The assembled file comes out at exactly the byte count in
+  the sentence. The read block is matched inside its own fence, because the page prints the same
+  shape again for the eight-hour window further down and a page-wide match reports six reads for a
+  call that issues four.
+
 ## 0.4.340
 
 - **Added** a check for the table `large-files.md` opens with: a read count and a byte count for

package/package.json

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