Jason McHuff

I do think it may be a good idea not to change the defaults. > did I mess that up? Line 1410 looks OK to me. It's a simple if...

> Would it make more sense to add a section in print_status() that prints the current decode rate for each system, and then make the timing of how often print_status()...

I was going to offer up to code it if there was consensus. My two thoughts are just: *if it's print_status() time, don't output the decoding rate if it's low...

Being able to control the status updates might be a nice to have. As I said, I'm just wanting a way to get the rates for the decode rate chart...

If you want to leave things as-is; I'd be willing to just customize things on my end and just submit the logDir config entry (unless you want to write that,...

Well, although it meant another day delay in getting things upgraded, I've decided to switch to logging the rates in a separate file. See https://github.com/robotastic/trunk-recorder/commit/0cd6c66c240abf2fd20017bea6e36991950d4695 While it means another file,...

No problem and thanks, as I've noticed some wonkyness with the site. As for logDir, see https://github.com/robotastic/trunk-recorder/pull/666/commits/bc23e8805c388c7c6eb557706a6d18151f098782 I can put it in another PR if we're unsure about this one....

This is now a plugin that logs the decoding rates to decode_rates.csv in the capture_dir. A header line is put in the file each time the program started. This only...

@robotastic this should be good to go, except for the rates being for only the proceeding 3 seconds. I know I could create a vector in the plugin to save...

Thinking about and looking at things, how about I (maybe in a separate issue, before this one gets addressed) create a `handle_message` plugin that passes the message and system and...