edfcore 0.5.58 → 0.5.59
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 +20 -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.5.
|
|
112
|
+
export declare const VERSION = "0.5.59";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,26 @@ 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.5.59
|
|
10
|
+
|
|
11
|
+
- **Added** the round trip a streaming pipeline actually performs: stream a window in pieces, merge
|
|
12
|
+
the pieces, and get the window. `merge-split.test.ts` proves it for `readWindow`. `streamRecords`
|
|
13
|
+
is the other way to get a window in pieces and is different code — a `readRecords` per piece, a
|
|
14
|
+
seam check between them, and a `chunkRecords` knob that decides how many pieces there are. Its
|
|
15
|
+
docblock says the pieces must be "the same object in every respect" as a read chunk, and
|
|
16
|
+
`stream-equals-read.test.ts` checks that one piece at a time. Whether they reassemble was not
|
|
17
|
+
checked.
|
|
18
|
+
- If they do not join, the memory bound the call exists for is bought with an answer the caller
|
|
19
|
+
cannot reconstruct — which is the whole point of streaming a twelve-hour recording and then
|
|
20
|
+
running a filter over it.
|
|
21
|
+
- The stream is merged at four chunk sizes, from one piece per record to a single piece, and
|
|
22
|
+
compared against `readWindow` on the same window: the samples, the record range, the byte offset
|
|
23
|
+
and length, the exact start and duration in ticks, `precededByGap` and the diagnostics.
|
|
24
|
+
- On a discontinuous file the answer changes, correctly. The stream crosses the gap in pieces, so
|
|
25
|
+
merging all of them is refused with the message `chunks.ts` produces — and the advice that refusal
|
|
26
|
+
ends with is followed: grouped by run, each run reassembles into exactly the chunk `readWindow`
|
|
27
|
+
returns for it.
|
|
28
|
+
|
|
9
29
|
## 0.5.58
|
|
10
30
|
|
|
11
31
|
- **Added** the composition rule for `trimToWindow`: trimming to A and then to B is trimming once to
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED