edf2csv 0.5.23 → 0.5.24
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 +25 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,31 @@
|
|
|
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.24
|
|
7
|
+
|
|
8
|
+
### Fixed: the correctness page described a method it says two hundred lines later was abandoned
|
|
9
|
+
|
|
10
|
+
"The comparison runs at `--decimals 20`, the most `--decimals` accepts, so what is being
|
|
11
|
+
compared is two computations of a value rather than one of them against its printed form."
|
|
12
|
+
|
|
13
|
+
It does not. Since 0.4.32 both sides dump their doubles and the 64 bits are compared; nothing
|
|
14
|
+
goes through a CSV, and `compare.py` mentions `--decimals` once, in the past tense, to say it
|
|
15
|
+
used to. The same page explains that change further down. Reading a printed cell back cannot
|
|
16
|
+
be exact at any precision — a cell is a rounded rendering, so parsing it gives the nearest
|
|
17
|
+
double to those digits rather than the double that was computed, which is exactly why the
|
|
18
|
+
method was replaced.
|
|
19
|
+
|
|
20
|
+
Two more on the same page:
|
|
21
|
+
|
|
22
|
+
- It gave the derived precision cap as 20. It has been 100 since 0.4.74, and the sentence was
|
|
23
|
+
making an argument about a magnetometer needing more places than a volt channel — the
|
|
24
|
+
argument the ceiling was raised for.
|
|
25
|
+
- It said `--decimals 20` prints `0.195360195360195` "from both forms". It prints
|
|
26
|
+
`0.19536019536019536003`, and the specification's literal ordering prints
|
|
27
|
+
`0.19536019536019466614` — they first differ at the fifteenth decimal. Which is the
|
|
28
|
+
difference that section exists to describe, so the sentence was undercutting its own point
|
|
29
|
+
with a number neither form produces.
|
|
30
|
+
|
|
6
31
|
## 0.5.23
|
|
7
32
|
|
|
8
33
|
### Fixed: the `time_s` precision rule was documented as it worked before 0.4.55
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "edf2csv",
|
|
3
|
-
"version": "0.5.
|
|
3
|
+
"version": "0.5.24",
|
|
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",
|