User Tools

Site Tools


software

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
software [2026/05/17 23:58] dsheensoftware [2026/05/18 00:06] (current) – [RF Data Handling] dsheen
Line 24: Line 24:
 ====== RF Data Handling ====== ====== RF Data Handling ======
  
-For storage of RF data, we typically use [[https://github.com/MITHaystack/digital_rf|digital_rf]] which provides a number of useful tools for rf data recording (such as thor.py) and for viewing said data (drf_sti.py). Generally, this is installed along with other useful sdr drivers, gnuradio libraries, and the like with [[https://github.com/radioconda/radioconda-installer|radioconda]].+The main radio for the dish is currently an Ettus X300 with twin UBX-160 daughtercards.  
 + 
 +For realtime processing of rf data, your best bet is usually to start with a gnuradio-companion flowgraph. gqrx can also be used for simply viewing the recieved spectrum and tuning the sdr. these can be installed along with other useful sdr drivers, gnuradio libraries, and the like with [[https://github.com/radioconda/radioconda-installer|radioconda]]. 
 + 
 +For storage of RF data for later analysis, we typically use [[https://github.com/MITHaystack/digital_rf|digital_rf]] which provides a number of useful tools for rf data recording (such as thor.py) and for viewing said data (drf_sti.py). It is also included in radioconda. 
  
 **Note:** You should generally avoid storing RF sample data to the same hard disk partition as a computer OS. The file sizes become large very quickly and accidentally filling the drive (and thereby rendering the computer unuseable) is a real possibility. Most machines with access to the [[networking|RF Data Network]] have dedicated /data partitions for this purpose that map to a separate raid array that is substantially larger than the partition for user and operating system files.  **Note:** You should generally avoid storing RF sample data to the same hard disk partition as a computer OS. The file sizes become large very quickly and accidentally filling the drive (and thereby rendering the computer unuseable) is a real possibility. Most machines with access to the [[networking|RF Data Network]] have dedicated /data partitions for this purpose that map to a separate raid array that is substantially larger than the partition for user and operating system files. 
  
-if you don't need to save data but want to retain it for a few seconds for some reason, the "drf ringbuffer" tool can provide a good option for managing digital_rf files in-memory. laforge.mit.edu and scotty.mit.edu have memory mapped file folders at /tmp/ramdisk for this purpose.+if you don't need to save data but want to retain it for a few seconds for some reason, the "drf ringbuffer" tool can provide a good option for managing digital_rf files in-memory. laforge.mit.edu and scotty.mit.edu have memory mapped file folders at /tmp/ramdisk for this purpose. This can also help to protect against dropped samples due to disk IO rate variations by using drf mirror to copy rf data from the ringbuffer to disk.
  
 ====== Application-Specific Software ====== ====== Application-Specific Software ======
software.1779062330.txt.gz · Last modified: 2026/05/17 23:58 by dsheen

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki