discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] usrp_spectrum_sense.py


From: GNUBeginner
Subject: Re: [Discuss-gnuradio] usrp_spectrum_sense.py
Date: Mon, 5 Jun 2017 12:39:15 -0700 (MST)

Hello Marcus,

Here is the requirements. I was planning to modify osmocom_spectrum_sense.py
code for these requirements and would appreciate your guidance/support. I am
very new to python and think that there needs to be minor modification such
as adding another class for decimation.

• Tuning Range: It will scan the band from 100 MHz to 6 GHz.  This tuning
range can be configurable. 
• Patches: The scanner will stop at interim frequencies to analyze a 20 MHz
"patch."  This patch width can also be configurable.
• No gaps: The full 5.9 GHz band will be covered presumably with no gaps in
coverage.
• Dynamic Range: It will optimize the effective dynamic range of the
receiver by dynamically controlling the three gains.  This will not be a
manual process but should be implemented as a MIMO feedback loop.  The
fastest loop be the loop farthest from the antenna.  The slowest will be the
loop closest to the antenna.  To keep it simple, each loop could be
implemented as a single pole recursive filter.  
• Metrics:  The scanner will collect samples and then analyze the patch and
compute metrics on emissions within the patch.  Metrics will include the
center frequency or power centroid and the band edges of emissions.
• Thresholding: The threshold used to detect emission will be dynamically
adjusted similarly to the gain controller.  The radio app will likely base
the threshold as some dB level above the noise floor.
• False alarms:  We don't want the radio app to report noise floor
detections, so detection false alarms will be minimized using the threshold
algorithm and perhaps a minimum emitter bandwidth constraint.  It would be
nice to show mathematically that this threshold achieves some false alarm
probability such as 1e-5.  The threshold should be configurable and that the
default is such that the app has a 1e-5 false alarm rate.
• Logging of metrics:  The metrics will be stored to a console and to a
file.  To elaborate this, the metrics will need at a minimum the following
information in order to be useful: time, centroid/center frequency, band
edges of the emitter, band power of the emitter (note that this is an
integrated metric across the emitter bandwidth, not the peak power of the
centroid.)

Thanks,




--
View this message in context: 
http://gnuradio.4.n7.nabble.com/usrp-spectrum-sense-py-tp63994p64141.html
Sent from the GnuRadio mailing list archive at Nabble.com.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]