[FEA] Improve cuSignal Integration with SoapySDR
SoapSDR is a vendor agnostic software defined radio library used for direct control of the radio. Since Soapy's use is widespread in the SDR community, cuSignal should have better integration and documentation centered on online-signal processing. We've addressed this a bit with our sdr notebooks, but could use a bit of a refresh.
To-do:
- [x] Update install documentation to walk a user through installing SoapySDR and applicable modules for their specific radio (e.g. LimeSDR, rtlsdr)
- [ ] Update Jupyter notebooks, particularly the wideband FM demod one (https://github.com/rapidsai/cusignal/blob/branch-0.16/notebooks/sdr/sdr_wfm_demod.ipynb) to reflect improved cuSignal + SoapySDR integration
- [ ] Consider adding SoapySDR to the manual conda build environments (for source installs).
This issue has been marked rotten due to no recent activity in the past 90d. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.
This issue has been marked stale due to no recent activity in the past 30d. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be marked rotten if there is no activity in the next 60d.
This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.
This issue has been labeled inactive-90d due to no recent activity in the past 90 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.