History of FAQKI(No. 12) - ASTE Observation Wiki

[ Front page ] [ New | Page list | Search | Recent changes | Help ]

FAQ / Known issues†

What's this page?: This page lists FAQ and known issues in ASTE operations.

Revision history

2016-09-18 - Kamazaki,T. - created

Table of contents

FAQ / Known issues
- FAQ
  - COSMOS3
- Known issues and their workarounds

FAQ†

COSMOS3†

How to restart COSMOS3
How to restart Aspirin
Enable Aspirin-blue
Running observation does not start scans
Here are points to be checked
- Antenna PROG values are updated every second on the antenna console. If not, make sure that your observation actually starts.
- Main and sub reflectors are in the PROG mode on the antenna console. If not, let them set PROG.

Known issues and their workarounds†

COSMOS3 Manager†

Observation suddenly stopped with the message "EMERGENCY STOP (Forced to stop) / Lost control priority." on the Manager GUI
- COSMOS3 communication between the ASTE and remote sites was cut due to some (unknown) reasons.
- Workaround: Just take the priority again by pushing the "THIS NODE" button on the Manager GUI, and you will be able to restart your observations.
- (Added: 2016-09-28, Resolved: No, JIRA: Not created)

New observation does not start with the messages "EMERGENCY STOP (Forced to stop) / Cannot connect with COSMOS3 Manager." and also "WARNING Cannot connect with ANTENNA_G infsrv (-1)" on the Manager GUI
- The COSMOS3 manager could not connect with the ANTENNA LOC. Its possible cause is duplicate running of COSMOS3 relevant processes.
- Workaround: Try to stop COSMOS3 TWICE at the ASTE site. If some relevant processes are still listed with the following command on aste-1c even after the stopping,
```
ps -ef | grep -E '(astd|astkyr|astact|astqlcsv|cntsv|hlgsv|pcv|ant|ref|rxt|ffx)' | grep -v antstat
```
  stop all of them using the KILL command. Then, start COSMOS3 at the ASTE site.
- If you cannot be root, ask Computing people or support scientists.
- (Added: 2016-10-13, Resolved: No, JIRA: ASTE-160)

QLOOK (Line)†

Line Qlook does not show spectra although an observation is running.
- This looks to be communication failures between the ASTE and remote sites.
- Workaround: First, restart COSMOS3 at the ASTE site. Second, also restart COSMOS3 at the remote site.
- (Added: 2016-09-30, Resolved: No, JIRA: Not created)

Line Qlook shows extremely strong spikes (e.g. >1000 K) at some of X[1-4] in 2GHz mode and X[1-2] in 4GHz mode
- Synchronization loss could happen between digital data and reference clocks.
- Such a pattern could be also seen at X5 and X6 in 2GHz mode and X3 in 4GHz mode. They can be ignored, because they are cross-polarization data.
- Resolution: Just "START TUNING" on the COSMOS3 manager GUI and then, restart your observation.
- (Added: 2016-10-05, Resolved: Yes, JIRA: None)

QLOOK (Cont)†

Others†

The Local Controller Activity GUI is frozen and cannot be closed.
- The LOC GUI sometimes freezes. Its cause is unknown yet.
- Workaround: Kill it using xkill (type 'xkill' on a terminal and click the GUI) and then, restart it from the COSMOS3 launcher.
- (Added: 2016-09-28, Resolved: No, JIRA: Not created)