Problems related to the ISPI GUI
GUI hangs because connection with TCS is lost
The most common problem when observing with ISPI, is that the ISPI GUI will loose connection with the TCS. As a result the ISPI GUI might hang. If this happens, close the GUI, stop the ArcVIEW main application and then restart the GUI. Detailed instructions can be found under Simple Restart on the Re-starting ISPI page.
If simply restarting the GUI does not bring back up the connection with the TCS, ask the night assistent to re-start the TCS router. See also the pages on Telescope & TCS related problems.
The GUI might also hang as a result of an overload on ctioa9, the ISPI computer. Avoid opening too many terminal windows on the VNCs running on ctioa9. It is recommended to limit the number of windows to the minimum, e.g. one to run IRAF and one to edit script. Use either of these windows to check the temperature.
An apparent problem, where the GUI hangs when using too many co-adds, is most likely related to an overload on ctioa9. We have not been able to reproduce this problem. Hence, we advice to limit the number of processes run on ctioa9, rather than limiting the number of coadds.
Along the same line of thought: when transferring data to another computer, it is recommended to start the transfer at the other end, rather than running the command, e.g. scp, on ctioa9.
Other problems with ISPI GUI & ctioa9
NOTE: Site under construction
February 21, 2007