Differences

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

--- software [2025/05/10 18:09] – holtz
+++ software [2026/05/21 14:17] (current) – 24.4.246.2
@@ Line 18: / Line 18: @@
 An interactive client can be run from a Python environment. APOsong provides convenience routines to connect to Alpaca devices and provide user-friendly commands to control the telescope, dome, camera etc., but you can also use all regular Python functionality, providing for a powerful environment. Within the APOsong software, interactive image display is enabled using the pyvista display tool and built-in, e.g. for the expose() command, but of course any other Python packages can be used interactively.
-To access the command set:
+To start an ipython session and access the command set:
 <code>
-from aposong import *
+aposong
 </code>
@@ Line 36: / Line 36: @@
 ===== Robotic software =====
-Alternatively, a robotic client is implemented in the robotic.py module in this APOsong repository. This makes use of the command set provided by aposong.py, but adds in functionality for opening and closing the dome at appropriate times and under appropriate conditions, and selecting targets and exposure sequences from entries in the Postgres database.
+Alternatively, a robotic client is implemented in the robotic.py module in this APOsong repository. This makes use of the command set provided by aposong.py, but adds in functionality for opening and closing the dome at appropriate times and under appropriate conditions, and selecting targets and exposure sequences from entries in a Postgres database on song1m.
-For SONG operation, robotic operations will be conducted through Postgres database syncs from Aarhus, details TBD when this is implemented ...
+For SONG operation, robotic operations are conducted through Postgres database syncs from Aarhus to the song1m_db machine. Requested observations are loaded into the obs_request_4 table in db_song with information about the
+target and the observing sequence. As the request is started, completed, or aborted, the status is
+communicated back through the obs_reqeust_status_4 table in db_apo. Other tables in db_apo communicate
+the state of the APO system so that the conductor can choose appropriate targets.
 ===== song1m computer =====
@@ Line 45: / Line 48: @@
 <code>
 cd APOsong
-ipython
+aposong
-> from aposong import *
 </code>
 This should show you a list of commands (which you can see again with the commands() function), and a list of connected devices.
+Two other processes also need to be running on song1m:
+- status  : updates status window and database with various information
+- guider : process that handles guiding through socket connection to main aposong process
+These are normally run in different tabs in a terminal on a VNC desktop.
 ===== pwi1m computer =====
@@ Line 78: / Line 86: @@
 ASCOM remote is stated from a desktop icon. It may need to be restarted if power is cycled to any of the devices that it interfaces to. It takes a minute or two to start and should show connections to all of the devices listed above.
-The Alypca server is started from an Anaconda Python shell (start using Windows input). Once the terminal window comes up:
+A desktop icon has been set up to start the Alpyca server. This just starts an Anaconda Python shell and does a:
 <code>
 cd APOalpyca/device
@@ Line 86: / Line 94: @@
 The system should then be ready for remote usage.
+The three programs have been put into Startup folder so they should start by themselves if the computer is restarted (may take a minute or two).
 === Planewave software ===
@@ Line 142: / Line 151: @@
 Run ASCOM remote for QHY interface and Esatto focuser interface.
-Run Alpyca server for thermocouple interface from an Anaconda terminal shell:
+A desktop icon has been set up to start the Alpyca server for the thermocouple interface. This just starts an Anaconda Python shell and does a:
 <code>
 cd APOalpyca/device
@@ Line 149: / Line 158: @@
 Since the QHY power is controlled by the thermocouple interface, the ASCOM remote interface won't connect until this is run: it will prompt you to connect the ASCOM device within 10 seconds.
+The system should then be ready for remote usage.
+The two programs (ASCOM remote and Alpyca server) have been put into Startup folder so they should start by themselves if the computer is restarted (may take a minute or two).
 ===== dome1m =====
@@ Line 176: / Line 190: @@
 The Alpyca servers runs on port 5555 on dome1m. To start the Alpaca devices after a reboot:
 <code>
-cd APOalpyca/device
+/home/ocs/APOalpyca/bin/dome_app
-python dome_app.py
 </code>
+which will kill any existing servers and start a new server. Since we have issues with the server stopping
+working in the early afternoon, a cron job restarts the server each afternoon.
@@ Line 192: / Line 208: @@
   * git for Windows
-Modify timezone, location, display setting (for remote VNC), firewall as needed (for ASCOM Remote and TigerVNC), and power settings (don't let computer go to sleep).
+Modify timezone, location, display setting (for remote VNC), firewall as needed (for ASCOM Remote and TigerVNC), and power settings (don't let computer go to sleep). In device manager, turn off Power Managment for all USB devices; disable USB selective suspend settings in Control Panel.