edf2csv 0.6.48 → 0.6.49
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 +12 -0
- package/package.json +1 -1
package/docs/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,18 @@
|
|
|
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.49
|
|
7
|
+
|
|
8
|
+
### Fixed: recipes showed a 100 Hz row as `286.50000000`
|
|
9
|
+
|
|
10
|
+
Eight decimal places is what 256 Hz gets. The paragraph is about `signals_100hz.csv`, three code
|
|
11
|
+
blocks under a snippet that loads it, and 100 Hz gets three places — the file really writes
|
|
12
|
+
`286.500`, which converting the page's own example recording confirms.
|
|
13
|
+
|
|
14
|
+
The point being made is right and worth keeping: a window converted on its own keeps the whole
|
|
15
|
+
recording's clock rather than restarting at zero. It was the illustration that came from a
|
|
16
|
+
different file.
|
|
17
|
+
|
|
6
18
|
## 0.6.48
|
|
7
19
|
|
|
8
20
|
### Fixed: nothing said the JSON drops the hint every terminal warning carries
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "edf2csv",
|
|
3
|
-
"version": "0.6.
|
|
3
|
+
"version": "0.6.49",
|
|
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",
|