edfcore 0.4.356 → 0.4.357
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.
- package/dist/constants.d.ts +1 -1
- package/dist/constants.js +1 -1
- package/docs/CHANGELOG.md +15 -0
- package/package.json +1 -1
- package/src/constants.ts +1 -1
package/dist/constants.d.ts
CHANGED
|
@@ -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.
|
|
112
|
+
export declare const VERSION = "0.4.357";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,21 @@ 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.357
|
|
10
|
+
|
|
11
|
+
- **Added** an execution of the two-signal `trimToWindow` example on `api-primitives.md`. It exists
|
|
12
|
+
to make one point — a 256 Hz channel and a 3 Hz channel asked for the same window start at
|
|
13
|
+
different instants and hold different counts — and that is why `startSeconds` lives on
|
|
14
|
+
`EdfChunkSignal` rather than only on the chunk. Both printed rows are now produced.
|
|
15
|
+
- The rule underneath is also pinned: membership is decided against the tick edfcore PUBLISHES for
|
|
16
|
+
a sample, not against its exact rational start. The page's own worked figure is checked both
|
|
17
|
+
ways — 256 samples in a one-second record put sample 1 at 39,062.5 ticks, which is not a whole
|
|
18
|
+
tick, published as 39,063 — because selecting on the exact start excluded the very sample a
|
|
19
|
+
caller had aligned the window to, a defect this project shipped and fixed in 0.3.56.
|
|
20
|
+
- Plus the three things trimming promises about its result: a subarray view rather than a copy so
|
|
21
|
+
it allocates nothing, a zero-length result rather than an error for a window that misses, and a
|
|
22
|
+
refusal when the header is not the one the chunk was read with.
|
|
23
|
+
|
|
9
24
|
## 0.4.356
|
|
10
25
|
|
|
11
26
|
- **Added** an execution of the `resolveTimeWindow` example on `api-primitives.md`: a one-second
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED