Fix .PM3 traces that exceed single-byte range

Browse source

This was done programmatically using python.
Files with a range that fell outside of [-128,127], but which would fit into that range, were offset by the noted amount to ensure the file woul now fit within range [-128,127].  This allows the trace files to be converted to one-byte-per-sample binary format, for example.

offset | filename
-----|-----
`-14` | `lf_Q5_mod-manchester.pm3`
`-14` | `lf_Q5_mod-nrz.pm3`
`-10` | `lf_Q5_mod-fsk1.pm3`
`-15` | `lf_Q5_mod-biphase.pm3`
`-9` | `lf_Q5_mod-fsk2.pm3`

...

This commit is contained in:

Henry Gabryjelski 2024-09-16 23:05:15 -07:00

parent f1d638c295

commit 1a7267ca53

5 changed files with 118434 additions and 118434 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

47792

traces/lf_Q5_mod-fsk1.pm3

View file

File diff suppressed because it is too large Load diff