edf2csv 0.4.74 → 0.4.76
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/CHANGELOG.md +37 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,43 @@
|
|
|
3
3
|
Notable changes to edf2csv. Versions follow [semantic versioning](https://semver.org); while the
|
|
4
4
|
major version is 0, a minor bump may contain breaking changes.
|
|
5
5
|
|
|
6
|
+
## 0.4.76
|
|
7
|
+
|
|
8
|
+
### Added: the API reference's examples are run, not just displayed
|
|
9
|
+
|
|
10
|
+
Every `js` block on the page is now extracted, pointed at a real recording, and executed.
|
|
11
|
+
Only paths and the package specifier are rewritten; the code is otherwise exactly what the
|
|
12
|
+
page shows, and each block runs against the first fixture that carries every channel it
|
|
13
|
+
names. A rename, a moved option, a return shape that changed — the kind of drift that leaves
|
|
14
|
+
a page looking perfectly fine — now fails a test instead.
|
|
15
|
+
|
|
16
|
+
The `parseTimeSpec` example is checked differently, because running it proves nothing: it
|
|
17
|
+
asserts its results in comments rather than printing them. Those four claimed values are
|
|
18
|
+
parsed out of the page and compared against what the function returns.
|
|
19
|
+
|
|
20
|
+
Both were confirmed capable of failing before being kept — one by renaming an import on the
|
|
21
|
+
page, the other by changing a claimed `0.25` to `0.5`.
|
|
22
|
+
|
|
23
|
+
## 0.4.75
|
|
24
|
+
|
|
25
|
+
### Fixed: the buffer-reuse warning described something the obvious test disproves
|
|
26
|
+
|
|
27
|
+
api.md calls the reused batch buffer "the one contract in the API that fails silently if you
|
|
28
|
+
get it wrong", and then described it as "kept[0], kept[1] and kept[2] are all identical, and
|
|
29
|
+
all hold the last batch read." Neither half survives being checked. `kept[0] === kept[1]` is
|
|
30
|
+
false — each iteration hands out its own `Uint8Array` — so a reader who tests the warning
|
|
31
|
+
the obvious way is told it does not apply and keeps the references. And they do not all hold
|
|
32
|
+
the last batch: the final batch is usually short, so an early view shows the last batch's
|
|
33
|
+
bytes for as far as they go and the *previous* batch's beyond that. A seam between two
|
|
34
|
+
batches, which produces plausible numbers rather than an error.
|
|
35
|
+
|
|
36
|
+
The section now says what is actually shared — distinct views, one buffer, all at offset
|
|
37
|
+
zero — and what a stale view holds afterwards. A test reads a fixture in batches with a
|
|
38
|
+
short tail and asserts all of it, so the description and the reader cannot drift apart.
|
|
39
|
+
|
|
40
|
+
Also corrects `decimalsForSignal`'s documented default, which 0.4.74 moved from 20 to 100
|
|
41
|
+
and this page still gave as 20.
|
|
42
|
+
|
|
6
43
|
## 0.4.74
|
|
7
44
|
|
|
8
45
|
### Fixed: the decimal ceiling was 20 on a false premise, and cost a magnetometer 69% of its codes
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "edf2csv",
|
|
3
|
-
"version": "0.4.
|
|
3
|
+
"version": "0.4.76",
|
|
4
4
|
"description": "Convert EDF, EDF+ and BDF biosignal recordings (European Data Format) to CSV from the command line. Local, streaming, and never resamples or alters units.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"edf",
|