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 118427 additions and 118427 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

traces/lf_Q5_mod-biphase.pm3

+23423 -23423

File diff suppressed because it is too large Load Diff

traces/lf_Q5_mod-fsk1.pm3

+23896 -23896

File diff suppressed because it is too large Load Diff

traces/lf_Q5_mod-fsk2.pm3

+23811 -23811

File diff suppressed because it is too large Load Diff

traces/lf_Q5_mod-manchester.pm3

+23722 -23722

File diff suppressed because it is too large Load Diff

traces/lf_Q5_mod-nrz.pm3

+23575 -23575

File diff suppressed because it is too large Load Diff