Restart the MAGIQ keyword server and MAGIQ server in that order:
GPIB camera. See here.
- log into k1-magiq-server
- run magiqAdmin start MagiqKwd
- from MAGIQ pulldown menu select Resart
PXL camera. See here.
PXL camera. See here.
PXL camera. See here.
GPIB camera. See here
Start or stop MAGIQ server via DCS GUI MAGIQ tear-off menu.
Start or stop MAGIQ server via DCS GUI MAGIQ tear-off menu. See above.
Note:When stopping and starting the MAGIQ server, it is recommended to verify that the processes are actually stopped and restarted by checking MAGIQ status. See below.
When MAGIQ server starts, it checks if the needed camera servers are running and starts them if necessary. No extra manual steps are necessary.
When MAGIQ server stops, it does not stop the camera servers.
To recover from an error or to trouble shoot problems, start or stop MAGIQ camera and mech servers via DCS GUI MAGIQ tear-off menu. See below.
Example for NIRSPEC:
Only one set of camera servers can be running at the same time for one camera. To ensure that the start-up script first forces any running camera servers to quit before starting a new one. This is why the menu to start the camera server is labeled with "Restart".
The menu item "Power cycle" is available for those cases when a simple restart does not restore the camera functionality and a full power cycle is required. A power cycle always includes:
There are two ways to check MAGIQ status:
- terminating any running camera and mech servers,
- powering off the camera electronics and the Galil controller,
- then powering on the Galil controller and the camera electronics and
- then restarting the camera and mech servers.
In some cases, a manual restart of the MAGIQ server and MAGIQ OA GUI is necessary after a power cycle of the camera electronics and Galil controller.
- Via DCSGUI MAGIQ tear-off menu button "Check MAGIQ status"
- From a xterm on k1-magiq-server or k2-magiqserver as k1obs or k2obs:
- magiq status
- The example above shows two GUIs: MAGIQ OA GUI and Observer GUI. MAGIQ server is running. NIRSPEC camera and mech servers are running on k2-magiq-camserver1. And MAGIQ keyword server is running. Note that there are two cam_rpc_svc processes for each camera server.
MAGIQ status web page
Another way to check the status is through the MAGIQ status web page:
MAGIQ status is also displayed on the weather page:
The DCSGUI MAGIQ tear-off menu provides the buttons to power cycle the NIRSPEC MAGIQ camera electronics and Galil controller.
See magiq script section for more details.
SCAM is available via the legacy camera server.
To use SCAM the NIRSPEC keyword scamguide must be set to 1. This is usually done via the NIRSPEC eavesdrop GUI.
The DCSGUI MAGIQ tear-off menu has an option to start the SCAM legacy camera server. See above.
Note: The commands and scripts description in this section and in the next section are intended to be invoked via GUIs and for trouble shooting purposes. In normal operation, there is not need to use these scripts directly.
The magiq script provides the means to manage MAGIQ processes and it is available on k1-magiq-server or k2-magiq-server. The general syntax is:
magiq command Subsystem [parameters]
There can be only one MagiqServer running.
- status (see 2.4.1)
magiq start MagiqServer
magiq restart MagiqServer
Starts the MagiqServer. The script always kills any running MAGIQ server before starting a new one. Thus start is same as restart.
magiq stop MagiqServer
Multiple MagiqGui can run simultaneously.
Stops the MagiqServer.
magiq start MagiqGui
Starts a new MAGIQ OA GUI using the current DISPLAY environment variable.
magiq stop MagiqGui
Stops ALL running MAGIQ OA GUIs.
magiq restart MagiqGui
Multiple OvserverUI can run simultaneously.
Stops ALL running MAGIQ OA GUIs and start ONE MAGIQ OA GUI.
magiq start ObserverUI
Starts a new MAGIQ Observer GUI using the current DISPLAY environment variable.
magiq stop ObserverUI
Stops ALL running MAGIQ Observer GUIs.
magiq restart ObserverUI
Multiple IqmUI can run simultaneously.
Stops ALL running MAGIQ Observer GUIs and start ONE MAGIQ Observer GUI.
magiq start IqmUI
Starts a new MAGIQ IQM GUI using the current DISPLAY environment variable.
magiq stop IqmUI
Stops ALL running MAGIQ IQM GUIs.
magiq restart IqmUI
Multiple CameraDiagnostic can run simultaneously.
Stops ALL running MAGIQ IQM GUIs and start ONE MAGIQ IQM GUI.
magiq start CameraDiagnostic
Starts a new MAGIQ CameraDiagnostic GUI using the current DISPLAY environment variable.
magiq stop CameraDiagnostic
Stops ALL running MAGIQ CameraDiagnostic GUIs.
magiq restart CameraDiagnostic
The cache generator caches catalog and image archive look-up results on local disk to speed up subsequent look-ups. Multiple cache generators can be running simultaneously. The cache directory is:
The MAGIQ keyword agent broadcasts MAGIQ keywords to an UNIX-IOC and listens for MAGIQ keyword changes and forwards them to the MAGIQ server. There can be only one MAGIQ keyword agent running.
Stops ALL running MAGIQ CameraDiagnostic GUIs and start ONE MAGIQ CameraDiagnostic GUI.
magiq start MagiqKwd
Starts the MAGIQ Keyword Agent.
magiq stop MagiqKwd
Stops the MAGIQ Keyword Agent.
magiq restart MagiqKwd
The MAGIQ audio alarm script magiqAudio is a shell script that monitors the MagiqServer.log file and issues an audio alarm by playing an .au file. There can be only one audio alarm script running.
Stops the MAGIQ Keyword Agent and restarts a new one.
magiq start Audio
Starts the MAGIQ audio alarm script.
magiq stop Audio
Stops the MAGIQ audio alarm script.
magiq restart Audio
The MAGIQ script invokes another script called magiqCamera, which runs k1-magiq-camserver1 or k2-magiq-camserver2 dependent on the telescope. The magiqCamera script starts and stops the actual camera server and also controls the power of the camera electronics and Galil controller.
Stops the MAGIQ audio alarm script and restarts a new one.
magiq start CameraServer camera_host camera_name
Starts the MAGIQ camera server for the camera camera_name on host camera_host, including the needed motion/mech servers.
magiq start CameraServer k2-magiq-camserver1 nirspecm
magiq start CameraServer k1-magiq-camserver1 lrisSlit
magiq start CameraServer k1-magiq-camserver1 lrisOffset
magiq stop CameraServer camera_host camera_name
Stops the MAGIQ camera server for the camera camera_name on host camera_host, including the needed motion/mech servers.
magiq restart CameraServer camera_host camera_name
Stops the MAGIQ camera server for the camera camera_name on host camera_host
and restarts a new one. This includes the needed motion/mech servers.
magiq poweroff CameraServer camera_host camera_name
Turns off power to camera_name on camera_host. This affects camera electronics only.
magiq poweroff CameraServer k1-magiq-camserver1 lrisSlit
magiq poweroff CameraServer k1-magiq-camserver1 lrisOffset
magiq poweroff CameraServer k2-magiq-camserver1 nirspecm
magiq poweron CameraServer camera_host camera_name
Turns on power to camera_name on camera_host. This affects camera electronics only.
magiq powercycle CameraServer camera_host camera_name
Turns off power to camera_name on camera_host and turns power back on. This affects camera electronics only.
magiq poweroff MechServer camera_host camera_name
Stops camera/mech server(s) and turns off power to Galil controller.
magiq poweroff MechServer k2-magiq-camserver1 nirspecm
Stops the camera server, the motion control server and the mechanism server and then turns off power to the Galil controller.
magiq poweron MechServer camera_host camera_name
MAGIQ CAMERA SCRIPT
The MAGIQ camera script, magiqCamera, is available on k1-magiq-camserver1 and k2-magiq-camserver1. It is invoked by the MAGIQ script. It can be invoked manually also. This script sets up the environment variables and calls other instrument dependent scripts.
The syntax is:
magiqCamera command camera-name
command is one of:
camera-name is one of:
magiqCamera start lrisSlit
magiqCamera start lrisOffset
magiqCamera start nirspecm
The script checks if the camera/mech servers are already running, if not then it starts camera server and mech/motion control servers and initializes mechanisms.
magiqCamera stop lrisSlit
magiqCamera stop lrisOffset
magiqCamera stop nirspecm
Stops the camera/mech/motion servers and delete the corresponding entries from the RPC info table.
magiqCamera restart lrisSlit
The configuration file for the camera server is located at:
magiqCamera restart lrisOffset
magiqCamera restart nirspecm
Stops the camera/mech/motion servers and restarts them, and initializes the mechanisms.
Shows all running camera/mech/motion server processes.
on the camera server host.
This configuration is a XML file containing information of all MAGIQ cameras (for one telescope) including:
The mech/motor servers require the following configuration files located at:
- identification (name)
- offsets (biases)
- temperature set point
- unit number
- channel number
- RPC program number
MAGIQ server configuration files are located on the MAGIQ server host at:
$KROOT/rel/default/data on the camera server host:
Configuration information includes:
- type of motor
- output channel
- encoder resolution
- name and position of filters in encoder counts
- list of keywords
The directory configData contains XML files describing instruments and their guider cameras.
The file Telescopes.xml contains the list of telescopes. In the case of Keck 1 or Keck 2, there is only one telescope in the list. This is to avoid confusion and redundant copies of configuration files.
The file KECK1.xml or KECK2.xml contains the list of instruments that are available for the given telescope. The configuration files for the instruments are located in the directory KECK1 and KECK2 respectively.
An instrument configuration includes an XML file and a directory of the same name. The XML file lists the guider cameras and subsystems. The information on subsystems are included for completeness and not used at this time. The instrument directory contains an XML file describing pointing origins. This description is only used for off-sky operations (observing planning or testing). When on-sky the pointing origin information is given via keywords that supersede the static information from the XML file.
The directory Cameras contains configuration for guider cameras available for the given telescope. The list of these cameras is given in the file cameras.xml. Each camera has its own XML configuration file, which includes REF x/y and default pointing origin name, plate scale and other information.
The file magiqConfig.xml.k2server includes the following information:
- Telescope name
- Update rates for various event loops
- Star catalog cache directory
- Fits header description file
- Directory containing configData
- Logging level
- Simulation modes
- Centroiding algorithms
- Flexure compensation parameter file location
- Keyword services
To add a new instrument:
- Choose a name for the new instrument, for example INSTR123.
- Create XML file INSTR123.xml containing list of guider cameras.
- Create directory INSTR123 containing the PointingOrigins.xml file.
- Add INSTR123 in KECK1.xml or KECK2.xml
To add a new guider camera:
- Choose a new for the new camera, for example CAM123.
- Create a XML configuration file CAM123.xml including reference pixel location, and the default pointing origin, plate scale, tv angle and flip.
- Add CAM123 in Cameras/cameras.xml.