edf2csv 0.5.116 → 0.5.117
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 +38 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,44 @@
|
|
|
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.117
|
|
7
|
+
|
|
8
|
+
### Fixed: the recipes page loaded a file the example recording never writes
|
|
9
|
+
|
|
10
|
+
recipes runs `edf2csv sleep-study.edf --out ./sleep_csv`, shows an `ls` of the result, and then
|
|
11
|
+
reads it fourteen times over — pandas, R, data.table, MATLAB, DuckDB, the chunked reader, the
|
|
12
|
+
`merge_asof` recipe. Every one of them opened `sleep_csv/signals_256hz.csv`.
|
|
13
|
+
|
|
14
|
+
That recording has no 256 Hz channel. It has three at 100 Hz, one at 10 Hz and one at 1 Hz, and
|
|
15
|
+
converts into six files:
|
|
16
|
+
|
|
17
|
+
```text
|
|
18
|
+
annotations.csv
|
|
19
|
+
channels.csv
|
|
20
|
+
metadata.json
|
|
21
|
+
signals_100hz.csv
|
|
22
|
+
signals_10hz.csv
|
|
23
|
+
signals_1hz.csv
|
|
24
|
+
```
|
|
25
|
+
|
|
26
|
+
The `ls` block listed four, one of them a file the run does not write and three of them missing.
|
|
27
|
+
Every snippet on the page after it was a `FileNotFoundError` on its first line.
|
|
28
|
+
|
|
29
|
+
The channel names went with it: the snippets print an `ECG` column, which belongs to a different
|
|
30
|
+
recording — this one's third 100 Hz channel is `EOG horizontal`. The `--info` table a hundred
|
|
31
|
+
lines above them has listed the real channels and the real file names all along.
|
|
32
|
+
|
|
33
|
+
faq's answer to "why several signals files" laid the same recording out as `signals_256hz.csv`,
|
|
34
|
+
`signals_128hz.csv` and `signals_1hz.csv`, and its two loader snippets and its digital-code
|
|
35
|
+
recipe read the 256 Hz file.
|
|
36
|
+
|
|
37
|
+
Corrected against a conversion: file names, channel names, the sample values and times in the
|
|
38
|
+
outputs shown, the wall-clock example's timestamps, the `channels.csv` listing, and the count of
|
|
39
|
+
interpolated rows in the `merge_asof` note (2,880,000 at 100 Hz, not 7,372,800 at 256 Hz).
|
|
40
|
+
|
|
41
|
+
A test converts one second of the fixture the example recording is built from and holds every
|
|
42
|
+
path under that output directory, and the `ls` block itself, to what the run writes.
|
|
43
|
+
|
|
6
44
|
## 0.5.116
|
|
7
45
|
|
|
8
46
|
### Fixed: a recording it is not allowed to read came back as a raw Node error
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "edf2csv",
|
|
3
|
-
"version": "0.5.
|
|
3
|
+
"version": "0.5.117",
|
|
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",
|