Fix .PM3 traces that exceed single-byte range

Browse source

This was done programmatically using python.

The `lf_Keri.pm3` was in range `[-508 .. 491]` (1000 value range).
Each value was divided by four, cast to integer, and then adjusted by +1 (to center the values).
The data plot in the pm3 client now shows discernible changes in amplitude.
The resulting samples are all within range [-128,127].

This final fix allows ALL sample `.pm3` traces to be converted to one-byte-per-sample binary format.

...

This commit is contained in:

Henry Gabryjelski 2024-09-16 23:35:03 -07:00

parent 1a7267ca53

commit 1d4e5e8d90

1 changed files with 23944 additions and 23944 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

47888

traces/lf_Keri.pm3

View file

File diff suppressed because it is too large Load diff