edf2csv 0.5.107 → 0.5.109

package/CHANGELOG.md

@@ -3,6 +3,57 @@
 Notable changes to edf2csv. Versions follow [semantic versioning](https://semver.org); while the
 major version is 0, a minor bump may contain breaking changes.
 
+## 0.5.109
+
+### Fixed: three pages still described an inverted channel by the rule that was corrected
+
+What inverts a channel is a negative gain, and the gain is
+`(physical_max - physical_min) / (digital_max - digital_min)` — so reversing exactly one of the
+two bounds pairs inverts the polarity, and reversing both leaves it positive and ordinary. The
+code was corrected to that rule and `reversed-bounds.edf` was written to hold it: three channels,
+two warned about, one not.
+
+One page was corrected with it. Three were not:
+
+- **correctness** listed "`physicalMin` above `physicalMax`" as a header condition that raises
+  `INVERTED_PHYSICAL_RANGE`.
+- **edf-format** said "`physicalMin > physicalMax` inverts the polarity of the channel".
+- **output-files**, describing the `physical_min` and `physical_max` columns of `channels.csv`,
+  called such a channel "an inverted channel" outright — the page a reader lands on when they
+  are looking at those two columns and wondering.
+
+The fixture's third channel is exactly that shape and draws nothing.
+
+All three now state the rule by the sign of the gain and say what reversing both pairs does.
+`reversed-bounds.edf` is also added to correctness's fixture table, which claimed the inversion
+row had a fixture "listed below" and then didn't list it.
+
+A test opens that fixture, confirms the channel is still there and still unwarned, and then
+holds every page to it. It reads the backticked field and column names, so the warning's own
+sentence — true of the channel it names — is not caught by it.
+
+## 0.5.108
+
+### Fixed: the annotations page said the example recording has one signal
+
+`edf2csv sleep-study.edf --info`, on the EDF+ annotations page, answered
+
+```
+Channels   1 signal + 1 annotation channel
+```
+
+Three other pages run that exact command on that exact recording and print `5 signals`, which
+is what it has: two EEG derivations, an EOG, a respiration trace and a rectal temperature, all
+of them listed in the channel table further down two of those pages.
+
+The line had been written to make the section's point — that the annotation channel is counted
+apart from the signals — and the real number makes it just as well.
+
+A test now runs `--info` on the fixture the site's example recording is built from and compares
+every header line the docs show against the line that comes out, on every page, skipping only
+`File` (the path as typed, which differs by page on purpose). It reads the fields a block chose
+to show, so an excerpt of two lines is checked as strictly as a full block.
+
 ## 0.5.107
 
 ### Fixed: recipes.md said the signal CSVs are already sorted, and one kind of file is not

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edf2csv",
-  "version": "0.5.107",
+  "version": "0.5.109",
   "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.",
   "keywords": [
     "edf",