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
We can add support to monitor multiple frequencies using the same 2 physical RX radios.
This can be done with a round-robin algorithm that iterates through "n" number of frequencies and provide sampled IQ data.
Will these samples be correlated with each other to enhance the accuracy of detected objects vs. noise? or each pair of ref/surv channels would provide their sets of data independently?
Integration with 3lips is a key consideration; hence, outputs (from blah2) need to be compatible.
How much latency sweeping through different frequencies will introduce?
Can we maintain 0.5 CPI across all frequencies? this is relevant to the frequencies-values chosen.. does this need to be explained in the documentation?
For the sake of clarity (to users), is it better to change the format of the config.yml to have an array of different "capture" fields. Or change the way config.yml files are provided so you can point to ./config/*.yml and blah2 will extract all provided files there as sources to utilise?
The text was updated successfully, but these errors were encountered:
We can add support to monitor multiple frequencies using the same 2 physical RX radios.
The text was updated successfully, but these errors were encountered: