Software Overview
User Interfaces
PFCam is controlled by a number of programs running in concert. The
observer interacts with the instrument via three user interfaces.
Each is described in detail under
PFCam User Interfaces. Their
functions are outlined in the following table:
Two additional programs are of interest to the observer:
the soundserver and
guidercopy. Though not
strictly instrument control, and not essential to the operation of
PFCam, the soundserver and guidercopy are useful observing aids.
Each is described in another section of this manual.
Component Distribution
From the user's perspective, all the PFCam software runs on on the
host
gouda.ucolick.org,
but in fact, most of the programs are distributed across the two hosts
shanepc and
pfcampc. The soundserver (responsible
for the bells, beeps, and squawks signaling exposure events) is run on
gouda for hardware reasons. The following table shows the
distribution of all PFCam's software components.
| Summary of PFCam software distribution |
|---|
| program
| host
| UI
| function |
|---|
| pfcamdispatch |
shanepc |
no |
Governs communication between rest of software |
| adctrack |
shanepc |
no |
Computes position of ADCs |
| dashboard |
shanepc |
yes |
GUI control of PFCam motors |
| mosdispatch |
shanepc |
no |
Governs communication with Top End motors |
| mosui |
shanepc |
yes |
UI for Top End motors |
| pfcamstart |
pfcampc |
yes |
PFCam data taker |
| pgEvent2Music |
pfcampc |
no |
Monitor program for exposure events |
| eventsounds |
gouda |
yes |
Generate sounds for exposure events |