You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have written a python script to decode the incoming radio data.
As I have hundreds of data rows, starting evaluating the /usr/bin/env python3 and starting the interpreter takes long, ...very long.
Describe the solution you'd like
Instead of feeding a single row via the first command line argument (which, as a minor side note, is prone to fail for gigantuous amounts of data per row), I suggest to provide the decoder with the data rows via stdin.
Note that I strongly suggest to first input all the data rows (one row per line, terminated by a single newline \n) and only start reading the decodeded data rows after all data has been written to stdin.
Doing so provides the decoder with the new (and optional) opportunity to process all data lines in context of each other, which even allows to tune parameters and reference previous or future data rows.
Describe alternatives you've considered
Writing the decoder as native binary.
Removing data rows by hand by selecting and deleting relevant input samples
Doing some other work while waiting for urh to finish
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
I have written a python script to decode the incoming radio data.
As I have hundreds of data rows, starting evaluating the
/usr/bin/env python3
and starting the interpreter takes long, ...very long.Describe the solution you'd like
Instead of feeding a single row via the first command line argument (which, as a minor side note, is prone to fail for gigantuous amounts of data per row), I suggest to provide the decoder with the data rows via stdin.
Note that I strongly suggest to first input all the data rows (one row per line, terminated by a single newline
\n
) and only start reading the decodeded data rows after all data has been written to stdin.Doing so provides the decoder with the new (and optional) opportunity to process all data lines in context of each other, which even allows to tune parameters and reference previous or future data rows.
Describe alternatives you've considered
The text was updated successfully, but these errors were encountered: