edf2csv 0.5.118 → 0.5.119
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 +29 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,35 @@
|
|
|
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.119
|
|
7
|
+
|
|
8
|
+
### Fixed: a paragraph written into the middle of a quoted warning
|
|
9
|
+
|
|
10
|
+
The `CONTINUOUS_LIAR` entry in warnings-and-errors quotes what the run prints. What the page
|
|
11
|
+
showed was this:
|
|
12
|
+
|
|
13
|
+
```
|
|
14
|
+
warning: This file is marked continuous (EDF+C), but 2 of its 3 data records say they start
|
|
15
|
+
somewhere other than where continuity puts them.
|
|
16
|
+
|
|
17
|
+
A BDF+ file gets its own spelling — `BDF+C` and `BDF+D` — the same as the discontinuous entry
|
|
18
|
+
above. Until 0.5.105 this half of the code printed the EDF markers whatever the format, so a
|
|
19
|
+
BDF+ recording was told about a string it does not contain and pointed at a marker BDF+ does
|
|
20
|
+
not define.
|
|
21
|
+
Times are written as if the records were contiguous, which is what EDF+C means.
|
|
22
|
+
If the recording really has gaps, the file should have been marked EDF+D.
|
|
23
|
+
```
|
|
24
|
+
|
|
25
|
+
An English sentence, backticks and all, inside the code block, between the warning and its own
|
|
26
|
+
advice — so the two indented lines read as hanging off the paragraph rather than off the
|
|
27
|
+
warning, and the warning itself reads as ending mid-sentence. The paragraph is true and belongs
|
|
28
|
+
on the page; it is now below the block instead of inside it.
|
|
29
|
+
|
|
30
|
+
A hint is joined to its message by nothing but that indent. So an indented line in a quoted
|
|
31
|
+
diagnostic has to have a diagnostic directly above it, and a test now holds every such block on
|
|
32
|
+
every page to that. A blank line inside one is still fine — the mixed-rate example shows a
|
|
33
|
+
warning, a blank line and then the closing summary, which is exactly what that run prints.
|
|
34
|
+
|
|
6
35
|
## 0.5.118
|
|
7
36
|
|
|
8
37
|
### Fixed: one failed write, two error lines, and the second one wrong about it
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "edf2csv",
|
|
3
|
-
"version": "0.5.
|
|
3
|
+
"version": "0.5.119",
|
|
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",
|