Differences

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

--- bigdish_console [2026/08/22 18:39] – [Source Queries] dsheen
+++ bigdish_console [2026/08/22 19:19] (current) – [Tracking Offsets] dsheen
@@ Line 97: / Line 97: @@
    * OMM as ''.json'' or ''.csv''
    * CCSDS OEM as ''.oem'' or ''.asc'' (the format NASA used for Artemis II ephemeris)
-   * Starlink modified ITC format ''.txt'' (see: [[https://api.starlink.com/public-files/ephemerides/MANIFEST.txt]]) (TODO: need to test this one)
+   * Starlink modified ITC format ''.txt'' (see: [[https://api.starlink.com/public-files/ephemerides/MANIFEST.txt]], [[https://starlink.com/public-files/ephemerides/README.md]]) (TODO: need to test this one)
+==== Tracking Offsets ====
+The offsets tab in the sidebar allows setting an offset from a track in any of the three standard coordinate frames used by bigdish.
+Additionally, a fourth option is provided to offset by an angle defined in the frame of the target (parallel/perpendicular to track). This is defined as a right handed frame ordered as (pointing direction, travel direction, cross direction). Crucially, unlike the other frames, This frame gives a true angle of arc which is defined only by the commanded offsets independent of source position.
 ==== Source Queries ====
@@ Line 105: / Line 109: @@
 Note: this is very very slow. That is a problem with the database, not our queries.
 ==== Queued Antenna Commands ====
+Uploading pre-plannned antenna trajectories is also supported in the same format used by [[https://github.com/w1xm/BigDishTools/blob/main/dish_client/WR66_run_pointing_file.py|WR66_run_pointing_file.py]]. Files should be .csv with columns containing
+<code>
+UTC_Time in ISO format, coordinate system, first coordinate, second coordinate, azvel [optional], elvel [optional]
+</code>
+The commands in any such file are added to a non-blocking queue (e.g. other commands can still be issued to the antenna until the timestamp of the first command in the file.