edf2csv 0.5.108 → 0.5.109

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 +29 -0
  2. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -3,6 +3,35 @@
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.109
7
+
8
+ ### Fixed: three pages still described an inverted channel by the rule that was corrected
9
+
10
+ What inverts a channel is a negative gain, and the gain is
11
+ `(physical_max - physical_min) / (digital_max - digital_min)` — so reversing exactly one of the
12
+ two bounds pairs inverts the polarity, and reversing both leaves it positive and ordinary. The
13
+ code was corrected to that rule and `reversed-bounds.edf` was written to hold it: three channels,
14
+ two warned about, one not.
15
+
16
+ One page was corrected with it. Three were not:
17
+
18
+ - **correctness** listed "`physicalMin` above `physicalMax`" as a header condition that raises
19
+ `INVERTED_PHYSICAL_RANGE`.
20
+ - **edf-format** said "`physicalMin > physicalMax` inverts the polarity of the channel".
21
+ - **output-files**, describing the `physical_min` and `physical_max` columns of `channels.csv`,
22
+ called such a channel "an inverted channel" outright — the page a reader lands on when they
23
+ are looking at those two columns and wondering.
24
+
25
+ The fixture's third channel is exactly that shape and draws nothing.
26
+
27
+ All three now state the rule by the sign of the gain and say what reversing both pairs does.
28
+ `reversed-bounds.edf` is also added to correctness's fixture table, which claimed the inversion
29
+ row had a fixture "listed below" and then didn't list it.
30
+
31
+ A test opens that fixture, confirms the channel is still there and still unwarned, and then
32
+ holds every page to it. It reads the backticked field and column names, so the warning's own
33
+ sentence — true of the channel it names — is not caught by it.
34
+
6
35
  ## 0.5.108
7
36
 
8
37
  ### Fixed: the annotations page said the example recording has one signal
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edf2csv",
3
- "version": "0.5.108",
3
+ "version": "0.5.109",
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",