Closed john- closed 5 months ago
There is a bug I am trying to track down with this. The channel-log_reorg_squashed branch is not yet working.
The issue has been addressed.
Channel log appears to be working fine here. I looked back at old format reason and was intending that it track amplitude of the peak for the channel center spectrum bin in the log; this was the column hard coded 0 dB. The other column coded 0 dB was supposed to be the threshold squelch level at the time. Not having any need for that data right now it makes sense to leave those out and see how this logging works over awhile. I recommend merging this to master.
For future note the time field could probably be reduced, but in a database time field it is more optimized to just use a datetime than a smaller field so it makes sense to keep this extra for consistency. If one had a large file of channel logs and wanted to transfer it to a database format for instance the extra time field accuracy would be better to have than not.
Thanks for looking at this.
Yeah the time is pretty verbose. For that and the other items you mentioned they can be changed down the road.
Yes later on. The demod type used, and fixed frequency accuracy/digits would be good adds for later also.
This has been merged into master.
After some discussion I have done some work on channel log function. This is in a separate branch:
User impacting changes
The option
--log-type fixed-field
generally shows the same information as from before this change. Any gaps should be able to be addressed with this revised approach,Backend changes
New capability
See the README for details.