edfcore 0.4.358 → 0.4.360
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 +29 -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.360";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,35 @@ 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.360
|
|
10
|
+
|
|
11
|
+
- **Added** checks for the two things `toPhysicalEnvelope` does that `toPhysical` must not be used
|
|
12
|
+
for. A bucket no sample landed in carries a digital `0`, because `min` and `max` are
|
|
13
|
+
`Int32Array`s and cannot hold a sentinel — and through the affine map that becomes mid-scale for
|
|
14
|
+
any channel whose range is not centred on zero. On the 0..1000 channel the page names it is 500,
|
|
15
|
+
which is now computed from the scale rather than quoted: a completely believable reading, drawn
|
|
16
|
+
as a flat trace across a hole.
|
|
17
|
+
- That failure is worth a test precisely because everything about it looks right — the number is
|
|
18
|
+
inside the channel's range, the arrays agree in length, the trace is continuous, and the only
|
|
19
|
+
sign is a stretch nobody sampled drawn as a steady midpoint. Both arrays now have to be `NaN`
|
|
20
|
+
wherever `counts` is zero, and `counts` itself has to be untouched.
|
|
21
|
+
- The second is polarity: a negative gain makes the map decreasing, so mapping `min` to `min`
|
|
22
|
+
yields an envelope drawn inside out. Every filled bucket on such a channel is checked to come
|
|
23
|
+
back with its lower bound below its upper one.
|
|
24
|
+
|
|
25
|
+
## 0.4.359
|
|
26
|
+
|
|
27
|
+
- **Added** a check for the two bucket-count rules on `api-helpers.md`. `readEnvelope` clamps
|
|
28
|
+
`buckets` to the densest signal's sample count, because more buckets than samples leaves holes
|
|
29
|
+
that mean nothing. `readEnvelopeAtResolution` does not clamp, because a resolution is a promise
|
|
30
|
+
about seconds per pixel and honouring it by dropping buckets would silently shorten the span the
|
|
31
|
+
caller is drawing.
|
|
32
|
+
- The page gives the case where they part company — a 4-second run of a 2 Hz signal at 0.25 s per
|
|
33
|
+
bucket reporting 16 buckets with 8 filled — and it is now produced. That sentence is what a
|
|
34
|
+
viewer's indexing depends on: `bucketCount` is the field to read before indexing, and a caller
|
|
35
|
+
who trusts the number they passed walks off the end of a short run or draws a grid narrower than
|
|
36
|
+
the window it claims to cover.
|
|
37
|
+
|
|
9
38
|
## 0.4.358
|
|
10
39
|
|
|
11
40
|
- **Added** checks for three small pure functions on `api-primitives.md`. `decodeHeaderLatin1` is
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED