edf2csv 0.5.97 → 0.5.99

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.
Files changed (2) hide show
  1. package/CHANGELOG.md +38 -0
  2. 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.99
7
+
8
+ ### Fixed: "Anything the tool noticed is printed after the table" — followed by one of the two
9
+
10
+ `edf2csv sleep-study.edf --info` prints two warnings: the mixed sampling rates, and that at
11
+ least one output file will exceed what Excel and Numbers can open. getting-started introduced
12
+ the block with that sentence and showed the first.
13
+
14
+ The omission is an odd one to leave: the row limit is a section of this project's own FAQ, and
15
+ a reader is sent there later having been shown a run of the same recording that apparently did
16
+ not raise it.
17
+
18
+ Both are there now, with a link to the answer. The test runs the command the page is describing
19
+ and requires every `warning:` line it prints to appear on the page — which is the only way a
20
+ block quoting output stays honest as the tool gains things to say.
21
+
22
+ ## 0.5.98
23
+
24
+ ### Fixed: "what --info can and can't tell you" was wrong in both directions
25
+
26
+ cli-reference points readers at that section for the answer, which makes being wrong there
27
+ worse than being silent. It was wrong twice.
28
+
29
+ It said `--info` "also raises `ANNOTATION_DECODE_FAILED`", unqualified. It raises it for what
30
+ it read, and on a continuous file that is sixteen records — so `two-annotation-channels.edf`
31
+ warns about three unreadable events when converted and says nothing at all under `--info`. Its
32
+ byte-identical discontinuous twin warns either way, because there the whole channel is read.
33
+
34
+ And its list of what `--info` cannot raise — `NO_ANNOTATIONS`, `STALE_OUTPUT`, the EDF+C
35
+ contradiction — left out the `NO_SAMPLES` that reports a signal file *not written*.
36
+ `annotations-only.edf` raises it on conversion and not under `--info`. The per-channel
37
+ `NO_SAMPLES`, about a channel carrying no samples, comes from the header and is raised, so the
38
+ code alone does not settle it and the page now says which form it means.
39
+
40
+ Held to it by a sweep rather than by review: every fixture is described and converted, and any
41
+ code the conversion raises that `--info` does not has to be one the page names. That is how the
42
+ two missing ones were found, and it is what would find the next.
43
+
6
44
  ## 0.5.97
7
45
 
8
46
  ### Fixed: three pages said `--info` reads only the header, on files where it reads records
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edf2csv",
3
- "version": "0.5.97",
3
+ "version": "0.5.99",
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",