Differences

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

--- software [2026/05/17 23:21] – [Controlling the Dish] dsheen
+++ software [2026/08/22 15:48] (current) – [Satellite Tracking] dsheen
@@ Line 21: / Line 21: @@
 TODO: actually mirror it to the mirror now that we've invalidated the passwords that were in the git repo
+===== General Purpose Control UI =====
+For simple control applications not requiring feedback from the radio (pointing to a desired target in different coordinate systems, satellite tracking, tracking planetary bodies within the solar system, etc.) a general purpose [[bigdish_console|bigdish console]] program is available. This program requires that the dish client library is installed on the computer, and provides a browser-rendered control UI.
+====== RF Data Handling ======
+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.
+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 ======
@@ Line 27: / Line 42: @@
 The example pointing scripts for the BigDishControlServer software include a small Python program that bridges the WebSocket-based protocol to rotctl protocol, which is used by satellite-tracking software like Gpredict. Note that currently Gpredict/rotctl cannot supply tracking velocities, so the tracking accuracy will be a bit worse.
+Some ephemeris are available only in formats which are incompatible with gpredict. Programs to interpret a subset of these into the commands for the dish can be found here [[https://github.com/w1xm/BigDishTools/tree/main/simple_tracking_scripts|Bigdish tracking scripts and coordinate converters]] and can produce command files readable by [[https://github.com/w1xm/BigDishTools/blob/main/dish_client|WR66_run_pointing_file.py]]
+Satellite TLEs can aso be downloaded from Celestrak or imported from files to the [[bigdish_console|bigdish console]]. It will also accept pointing files of the same type as WR66_run_pointing_file.py.
 ===== Radio Astronomy =====