edf2csv 0.6.27 → 0.6.29
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/docs/CHANGELOG.md +32 -0
- package/package.json +1 -1
package/docs/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,38 @@
|
|
|
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.6.29
|
|
7
|
+
|
|
8
|
+
### Fixed: the warnings table listed two of `DUPLICATE_LABEL`'s three causes
|
|
9
|
+
|
|
10
|
+
The third is the one a reader is least able to work out for themselves: a channel that loses its
|
|
11
|
+
own column name to something else in the header — another channel's `_ch<index>` suffix landing
|
|
12
|
+
on it, or the `time_s` the writer puts in front of every signals.csv. `label-suffix-collision.edf`
|
|
13
|
+
in this repository raises it beside the ordinary shared-label warning, and the two read very
|
|
14
|
+
differently:
|
|
15
|
+
|
|
16
|
+
```
|
|
17
|
+
warning: 2 signals share the label "T8" (positions 0, 1).
|
|
18
|
+
warning: Signal 2 is labelled "T8_ch0", which is also the column name another channel's "_ch"
|
|
19
|
+
suffix produces, so its column is "T8_ch0_ch2".
|
|
20
|
+
```
|
|
21
|
+
|
|
22
|
+
The second is the one that renames a channel that did nothing wrong, and the table had no room
|
|
23
|
+
for it.
|
|
24
|
+
|
|
25
|
+
## 0.6.28
|
|
26
|
+
|
|
27
|
+
### Fixed: the warnings table gave `TIME_RESOLUTION` only its duplicate-timestamps half
|
|
28
|
+
|
|
29
|
+
Third row of the same table with the same shape as 0.6.26 and 0.6.27. The code has two branches
|
|
30
|
+
and they have opposite outcomes: samples too close together share a `time_s`, or the rate worked
|
|
31
|
+
out to `Infinity` — samples per record over a record duration too small to divide into — and no
|
|
32
|
+
rows are written for those channels at all. The section explains both, including why 0.5.84 was
|
|
33
|
+
needed. The summary line named the branch that still produces data.
|
|
34
|
+
|
|
35
|
+
Three rows of one table, each summarising a two-branch warning with one branch. The table is now
|
|
36
|
+
consistent with the sections under it.
|
|
37
|
+
|
|
6
38
|
## 0.6.27
|
|
7
39
|
|
|
8
40
|
### Fixed: the warnings table gave `UNUSABLE_PHYSICAL_RANGE` only its overflow half
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "edf2csv",
|
|
3
|
-
"version": "0.6.
|
|
3
|
+
"version": "0.6.29",
|
|
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",
|