edf2csv 0.5.128 → 0.5.130
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 +44 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,50 @@
|
|
|
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.5.130
|
|
7
|
+
|
|
8
|
+
### Fixed: the exit-2 list left out half of what exits 2
|
|
9
|
+
|
|
10
|
+
"**Exit 2** covers anything decided before touching data", says the reference, and then lists
|
|
11
|
+
what that is. The list named `--decimals` and neither `--jobs` nor `--layout`, which are checked
|
|
12
|
+
the same way, in the same function, a dozen lines apart — `--jobs 0` has been a usage error
|
|
13
|
+
since 0.4.2 and `--layout tall` since 0.5.0. It named one of the `--stdout` refusals, the one
|
|
14
|
+
about tables, and not `--json`, `--out`, `--checksum`, `--force`, a folder or a second
|
|
15
|
+
recording, every one of which the tool refuses before it opens the file. And the empty folder
|
|
16
|
+
appeared only as a parenthesis under exit 1, which is where it is not.
|
|
17
|
+
|
|
18
|
+
A list that claims to be complete and is half a list is worse than no list: a script written
|
|
19
|
+
from it treats an exit 2 it did not expect as a crash.
|
|
20
|
+
|
|
21
|
+
The missing conditions are named now, and a test derives them rather than trusting a copy. It
|
|
22
|
+
reads `--help` for every long option that takes a value, hands each one a value nothing could
|
|
23
|
+
mean, and requires the exit-2 section to name every flag that answers with exit 2 — so a flag
|
|
24
|
+
added tomorrow with a value it checks fails this until the reference mentions it. The `--stdout`
|
|
25
|
+
combinations are run the same way.
|
|
26
|
+
|
|
27
|
+
## 0.5.129
|
|
28
|
+
|
|
29
|
+
### Fixed: the commonest refusal on the site was quoted with its advice flush left
|
|
30
|
+
|
|
31
|
+
```
|
|
32
|
+
error: No channel named "ECQ". Did you mean "ECG"?
|
|
33
|
+
Run with --info to list the channels in this file.
|
|
34
|
+
```
|
|
35
|
+
|
|
36
|
+
The tool indents that second line by seven, under the first word of the message. Four hundred
|
|
37
|
+
lines below its own copy of this block, the reference explains why: "Every refusal takes that
|
|
38
|
+
shape — `error:` on the first line, the advice indented under it — so stderr can be grepped for
|
|
39
|
+
`^error:` and find all of them." Written flush left it reads as a second error, and a reader
|
|
40
|
+
building that grep out of these blocks would expect two lines back from a run that emits one.
|
|
41
|
+
|
|
42
|
+
The FAQ had it the same way, in the answer titled "I asked for a channel and it says there is
|
|
43
|
+
no channel with that name" — which is the page a reader arrives at holding the real message,
|
|
44
|
+
looking for the one on screen.
|
|
45
|
+
|
|
46
|
+
Both now match, and a test runs the refusal rather than matching its text: any block on the
|
|
47
|
+
site that opens `error: No channel named "…"` is compared against what that term really
|
|
48
|
+
produces.
|
|
49
|
+
|
|
6
50
|
## 0.5.128
|
|
7
51
|
|
|
8
52
|
### Fixed: the step formula the pages print is negative for a calibration real files carry
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "edf2csv",
|
|
3
|
-
"version": "0.5.
|
|
3
|
+
"version": "0.5.130",
|
|
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",
|