edf2csv 0.6.26 → 0.6.28

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/docs/CHANGELOG.md +23 -0
  2. package/package.json +1 -1
package/docs/CHANGELOG.md CHANGED
@@ -3,6 +3,29 @@
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.28
7
+
8
+ ### Fixed: the warnings table gave `TIME_RESOLUTION` only its duplicate-timestamps half
9
+
10
+ Third row of the same table with the same shape as 0.6.26 and 0.6.27. The code has two branches
11
+ and they have opposite outcomes: samples too close together share a `time_s`, or the rate worked
12
+ out to `Infinity` — samples per record over a record duration too small to divide into — and no
13
+ rows are written for those channels at all. The section explains both, including why 0.5.84 was
14
+ needed. The summary line named the branch that still produces data.
15
+
16
+ Three rows of one table, each summarising a two-branch warning with one branch. The table is now
17
+ consistent with the sections under it.
18
+
19
+ ## 0.6.27
20
+
21
+ ### Fixed: the warnings table gave `UNUSABLE_PHYSICAL_RANGE` only its overflow half
22
+
23
+ The code picks the word from which way the span failed — `too ${underflowed ? 'small' : 'large'}
24
+ to represent` — and the section on the same page explains both at length, including the
25
+ underflow case 0.5.83 was released for. The one-line summary said "too wide to represent",
26
+ which is the half a reader scanning the table would take for the whole rule and the half that
27
+ does *not* apply to a magnetometer, the channel type the section names.
28
+
6
29
  ## 0.6.26
7
30
 
8
31
  ### Fixed: the warnings table still said a mixed-rate file means "several output files"
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edf2csv",
3
- "version": "0.6.26",
3
+ "version": "0.6.28",
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",