edf2csv 0.5.125 → 0.5.127
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 +40 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,46 @@
|
|
|
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.127
|
|
7
|
+
|
|
8
|
+
### Fixed: the chunked-reader recipe printed a row count and a peak from nowhere
|
|
9
|
+
|
|
10
|
+
```python
|
|
11
|
+
print(rows, peak) # 7372800 122.161
|
|
12
|
+
```
|
|
13
|
+
|
|
14
|
+
The file it reads is `sleep_csv/signals_100hz.csv`, and neither number is that file's.
|
|
15
|
+
7,372,800 rows is eight hours at 256 Hz; eight hours at 100 Hz is 2,880,000, which the same
|
|
16
|
+
page states eighteen lines further down while explaining what `merge_asof` would do to it. And
|
|
17
|
+
122.161 is not the peak of anything — that column reaches 250, its declared physical maximum.
|
|
18
|
+
|
|
19
|
+
A recipe that prints a result is a claim about a file. This one is now converted and read down
|
|
20
|
+
by a test, the way the snippet reads it, and both numbers are checked against what comes out.
|
|
21
|
+
|
|
22
|
+
## 0.5.126
|
|
23
|
+
|
|
24
|
+
### Fixed: the metadata.json the page explains was a different recording's
|
|
25
|
+
|
|
26
|
+
output-files prints a whole `metadata.json` as its explanation of the format — the transcript
|
|
27
|
+
someone reads before writing code against those fields. Its `source.path` ends in
|
|
28
|
+
`sleep-study.edf`, which on this site is one specific recording: eight hours of five channels
|
|
29
|
+
at 100, 10 and 1 Hz with an annotation channel.
|
|
30
|
+
|
|
31
|
+
The sample described three channels at 256, 128 and 1 Hz. 39 MB against 18.7. 412 events
|
|
32
|
+
against 7. Three channel rows against 5. `signal_count` 4 against 6. Started in March 2026
|
|
33
|
+
rather than March 2002. One warning where that conversion raises two — and the field named
|
|
34
|
+
`notes` is the one a reader consults to find out what a warning looks like in the record.
|
|
35
|
+
|
|
36
|
+
The guard that existed declined to check any of it, on the stated grounds that "the sample
|
|
37
|
+
describes an 8-hour sleep study that is not in this repository". It has been in this repository
|
|
38
|
+
since 0.4.68, as `test/fixtures/sleep-study.mjs`, and is what every `--info` block on the site
|
|
39
|
+
is generated from. The values are now compared against a real conversion of it; the run's own
|
|
40
|
+
fields — the tool version, where the file sat, when it was converted — stay illustrative.
|
|
41
|
+
|
|
42
|
+
The same page ran `edf2csv sleep-study.edf` over a directory listing of `signals_256hz.csv`,
|
|
43
|
+
`signals_128hz.csv` and `signals_1hz.csv`. That is `recording.edf`, the three-rate example
|
|
44
|
+
sampling-rates uses, and it is now called that.
|
|
45
|
+
|
|
6
46
|
## 0.5.125
|
|
7
47
|
|
|
8
48
|
### Fixed: the FAQ's --json example was another recording's summary, warnings included
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "edf2csv",
|
|
3
|
-
"version": "0.5.
|
|
3
|
+
"version": "0.5.127",
|
|
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",
|