edf2csv 0.5.127 → 0.5.129
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 +45 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,51 @@
|
|
|
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.129
|
|
7
|
+
|
|
8
|
+
### Fixed: the commonest refusal on the site was quoted with its advice flush left
|
|
9
|
+
|
|
10
|
+
```
|
|
11
|
+
error: No channel named "ECQ". Did you mean "ECG"?
|
|
12
|
+
Run with --info to list the channels in this file.
|
|
13
|
+
```
|
|
14
|
+
|
|
15
|
+
The tool indents that second line by seven, under the first word of the message. Four hundred
|
|
16
|
+
lines below its own copy of this block, the reference explains why: "Every refusal takes that
|
|
17
|
+
shape — `error:` on the first line, the advice indented under it — so stderr can be grepped for
|
|
18
|
+
`^error:` and find all of them." Written flush left it reads as a second error, and a reader
|
|
19
|
+
building that grep out of these blocks would expect two lines back from a run that emits one.
|
|
20
|
+
|
|
21
|
+
The FAQ had it the same way, in the answer titled "I asked for a channel and it says there is
|
|
22
|
+
no channel with that name" — which is the page a reader arrives at holding the real message,
|
|
23
|
+
looking for the one on screen.
|
|
24
|
+
|
|
25
|
+
Both now match, and a test runs the refusal rather than matching its text: any block on the
|
|
26
|
+
site that opens `error: No channel named "…"` is compared against what that term really
|
|
27
|
+
produces.
|
|
28
|
+
|
|
29
|
+
## 0.5.128
|
|
30
|
+
|
|
31
|
+
### Fixed: the step formula the pages print is negative for a calibration real files carry
|
|
32
|
+
|
|
33
|
+
Three pages state the smallest physical step a channel can express, because it is what decides
|
|
34
|
+
how many decimals its values get. Two printed it with the magnitude on one difference only:
|
|
35
|
+
|
|
36
|
+
```
|
|
37
|
+
step = |physical_max - physical_min| / (digital_max - digital_min)
|
|
38
|
+
```
|
|
39
|
+
|
|
40
|
+
`reversed-bounds.edf` has a channel whose digital pair is written the wrong way round — legal,
|
|
41
|
+
warned about with `INVERTED_PHYSICAL_RANGE`, and converted as the header says. For that channel
|
|
42
|
+
the printed formula is -0.1, and the next thing the page tells you to do with it is take
|
|
43
|
+
`ceil(-log10(step))`, which of a negative number is not a number at all. The code takes the
|
|
44
|
+
magnitude of the whole quotient and gives that channel 3 decimals, the same as the upright
|
|
45
|
+
channel beside it — the only answer that keeps its distinct codes distinguishable.
|
|
46
|
+
|
|
47
|
+
Both differences are magnitudes now, on all three pages, with a sentence saying why. Held by a
|
|
48
|
+
test that evaluates the formula the page prints against the function the conversion uses, on
|
|
49
|
+
each of that fixture's three shapes: physical pair reversed, digital pair reversed, and both.
|
|
50
|
+
|
|
6
51
|
## 0.5.127
|
|
7
52
|
|
|
8
53
|
### Fixed: the chunked-reader recipe printed a row count and a peak from nowhere
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "edf2csv",
|
|
3
|
-
"version": "0.5.
|
|
3
|
+
"version": "0.5.129",
|
|
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",
|