edfcore 0.3.84 → 0.3.85
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/CHANGELOG.md +19 -0
- package/dist/constants.d.ts +1 -1
- package/dist/constants.js +1 -1
- package/package.json +1 -1
- package/src/constants.ts +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,25 @@ alone does not tell you whether you were affected.
|
|
|
6
6
|
edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
|
|
7
7
|
defect; those are called out below.
|
|
8
8
|
|
|
9
|
+
## 0.3.85
|
|
10
|
+
|
|
11
|
+
- **Fixed** four pages denying a comparison the test suite performs on every run.
|
|
12
|
+
- `api-primitives.md` — the page a caller reads to decide whether to trust the pinned scaling
|
|
13
|
+
expression — said the float64 parity with pyEDFlib "isn't yet demonstrated by a golden-value
|
|
14
|
+
harness, so treat it as intent rather than a measured guarantee". `api-validate.md` and
|
|
15
|
+
`validation.md` said edfcore's output "has not been compared element by element" against
|
|
16
|
+
pyEDFlib or MNE. `comparison.md` said validation against the public corpora "has not happened
|
|
17
|
+
yet".
|
|
18
|
+
- `tests/corpus/golden-values.test.ts` writes its fixtures with pyEDFlib's own writer, reads them
|
|
19
|
+
back with pyEDFlib, and compares every physical sample against the IEEE-754 bits it produced
|
|
20
|
+
using `Object.is` — a one-ULP difference fails. `mne-parity.test.ts` does the same for MNE. The
|
|
21
|
+
goldens are committed, so both run on a fresh clone. The harness has existed since 0.2.34-0.2.48.
|
|
22
|
+
- The pages now say what is measured and what is not, and `comparison.md` says plainly that the
|
|
23
|
+
corpus tests SKIP without `npm run corpus:fetch` — so a fresh clone proves the golden comparison
|
|
24
|
+
and not the corpus one. Understating a guarantee is still a false statement about the package.
|
|
25
|
+
- Same class as 0.3.64, which removed this wording from three other pages and missed these four. The
|
|
26
|
+
guard now sweeps every page for both retired phrasings.
|
|
27
|
+
|
|
9
28
|
## 0.3.84
|
|
10
29
|
|
|
11
30
|
- **Fixed** four statements that the `node:` import lives in exactly one file. `src/cli.ts` imports
|
package/dist/constants.d.ts
CHANGED
|
@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
|
|
|
109
109
|
readonly reserved: 224;
|
|
110
110
|
};
|
|
111
111
|
/** Published package version. Kept in sync with package.json by a test. */
|
|
112
|
-
export declare const VERSION = "0.3.
|
|
112
|
+
export declare const VERSION = "0.3.85";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/package.json
CHANGED
package/src/constants.ts
CHANGED