edfcore 0.4.500 → 0.4.502
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 +31 -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.502";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,37 @@ 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.502
|
|
10
|
+
|
|
11
|
+
- **Added** a property test for the round trip between `sampleStartTicksOf` and `sampleAt` — the
|
|
12
|
+
pair a viewer uses, a cursor position in and a sample index out.
|
|
13
|
+
- `api-helpers.md` states the rule as a four-way agreement: "`sampleAt`, `sampleStartTicksOf`, a
|
|
14
|
+
window bound and `readTriggers` all name the same sample." 0.3.32 settled it after `readTriggers`
|
|
15
|
+
disagreed with the other three, and 0.3.56 moved a window bound onto it after the same mismatch
|
|
16
|
+
turned up there. Both fixes were made against examples.
|
|
17
|
+
- `sample-grid-roundtrip.test.ts` covers the pure pair, which takes a SIGNAL and knows nothing
|
|
18
|
+
about gaps. These take the RECORDING, and that is the difference: after a hole a sample's instant
|
|
19
|
+
is not its index times the interval, so inverting it means finding the segment first. That half
|
|
20
|
+
was only ever checked at chosen points.
|
|
21
|
+
- Four geometries, two of them with a sample interval that is not a whole number of ticks, each run
|
|
22
|
+
contiguous and again across a ten-second hole — and once more in ticks rather than seconds, since
|
|
23
|
+
a trip through seconds can close on rounding luck.
|
|
24
|
+
|
|
25
|
+
## 0.4.501
|
|
26
|
+
|
|
27
|
+
- **Added** the four normalisations `api-sources.md` states for `cachedSource`'s two options:
|
|
28
|
+
`blockBytes` floored, never below 1, clamped down to `maxBytes`; `maxBytes` floored, never below
|
|
29
|
+
0. None was checked.
|
|
30
|
+
- Each exists because a caller computes these numbers rather than typing them — a block size
|
|
31
|
+
derived from `header.recordByteLength`, a budget read from an environment variable, a fraction of
|
|
32
|
+
`navigator.deviceMemory`. `hardening.test.ts` covers the NaN refusals, which are a different rule
|
|
33
|
+
with an error attached, and `cache.test.ts` passes whole numbers throughout.
|
|
34
|
+
- What the flooring costs is not obvious from the table, which is why the table is worth executing.
|
|
35
|
+
Rounding up fetches more than the caller budgeted for on every miss; a `blockBytes` of 0 that was
|
|
36
|
+
not floored to 1 divides by zero working out which block an offset falls in.
|
|
37
|
+
- Each rule is checked through what the WRAPPED source is asked for, because that is the only place
|
|
38
|
+
the block size is observable — the cache has no accessor for it, deliberately.
|
|
39
|
+
|
|
9
40
|
## 0.4.500
|
|
10
41
|
|
|
11
42
|
- **Added** the halves of `discontinuous.md` its existing test did not reach: what `openEdf` alone
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED