![[PukiWiki]](http://www2.nao.ac.jp/~aste-www/aste_wiki/obs.jpg "[PukiWiki]")
[[FrontPage]] * FAQ / Known issues [#q6a35f41] :What's this page?| This page lists FAQ and known issues of ASTE operations. :Revision history| -- 2016-09-18 - Kamazaki,T. - created :Table of contents| #contents ---- ** FAQ [#d87d646f] *** COSMOS3 [#m7a8d2fb] - [[''How to restart COSMOS3''>UsefulShortcuts#tcc7461d]] - [[''How to start/stop COSMOS3''>UsefulShortcuts#tcc7461d]] - [[''How to restart Aspirin''>UsefulShortcuts#tcc7461d]] - [[''Enable Aspirin-blue''>UsefulShortcuts#tcc7461d]] - [[''Power control of digital backend''>UsefulShortcuts#k37aa6f7]] *** Observations [#gdff2d04] + ''Running observation does not start scans'' &br; 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. -- Both of main and sub reflectors are in the PROG mode on the antenna console. If not, let them set PROG. // + ''No (valid) pointing-result is displayed in QLOOK (Line) while reasonable spectra are plotted on it'' -- e.g.) always same offsets &br; &ref(5pon_coffsets.png,,50%); -- e.g.) always *****/***** + Here are points to be checked -- Make sure that signal baseline ranges (left line-free range | signal range | right line-free range; yellow lines in the plot) are reasonably set. Don't include line-free areas in the signal range setting. #ref(qlookl_baseline_set.png,,50%) -- Make sure that the number of ''*'' (on-position) is 6 (normally, ''1***1***'' or ''1*1*1*1*1*1*'') in a sequence pattern of a scan file for pointing measurements using the 5-point method. ** Known issues and their workarounds [#bfaacea1] // -------------------------------------------------- *** Antenna console [#db462458] // -------------------------------------------------- ---- #br + ''Time on the antenna console GUI stopped, COSMOS3 manager GUI frequently showed the "Now re-connecting ..." message and then, ANTENNA_G in the local controller activities GUI went to red after stopping running observation'' #br &ref(aste-137_acon.png,,25%); &ref(aste-137_mgui.png,,25%); &ref(aste-137_lact.png,,50%); -- COSMOS3 suddenly could not communicate with antenna controller. Its bugfix was done. However, it still occurs rarely and further bugfix is under consideration. -- ''Workaround'': Restart COSMOS3 at the ASTE site. -- (Added: 2017-08-01; Resolved: No; JIRA: ASTE-137) // // -------------------------------------------------- *** COSMOS3 Manager [#l67fbe00] // -------------------------------------------------- ---- #br + ''Observation suddenly stopped with the message "EMERGENCY STOP (Forced to stop) / Lost control priority." on the Manager GUI'' #br #ref(mgui-Lost_control_priority.png,,50%) -- 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) // #br + ''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'' #br #ref(mgui_ANTENNA_G_infsrv.png,,50%) -- The COSMOS3 manager could not connect with the ANTENNA LOC. Its possible cause is duplicate running of COSMOS3 relevant processes. -- ''Workaround'': Restart COSMOS3 at the ASTE site. If the restart script ''cos3_cntl'' lists remaining processes and asks about purging them, answer "y". -- %%''Workaround'': Try to stop COSMOS3 ''TWICE'' at the ASTE site. If some relevant processes are still listed by 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 or reboot aste-1c. Then, restart COSMOS3 at the ASTE site.%% -- %%If ASTE operation supporter is available, ask the supporter to reboot aste-1c.%% -- %%If not available, ask Computing people or support scientists.%% -- (Added: 2016-10-13; Updated: 2017-07-27; Resolved: No; JIRA: ASTE-161,ASTE-160) // #br + ''Observation or tuning fails with the messages "Fatal error INSTRUCTION XXX" and also "ERR local:FFX descriptor=7 cmn_socket_read error = Connection reset by peer / Command SET: local FFX: not connected"'' + ''Tuning never finishes, and FFX is in "NO RESPONSE" on the LOC activities GUI"'' #br &ref(mgui_FFX_descriptor_cmn_socket_read.png,,50%); &ref(locgui_FFX_NO_RESPONSE.png,,50%); &br; (Left) Fatal error INSTRUCTION XXX (Right) FFX in "NO RESPONSE" -- The COSMOS3 manager could not connect with the FFX (WHSF) LOC. It would be that old FFX processes remain on aste-1c and still occupy some communication ports of FFX. -- ''Workaround'': Stop COSMOS3 at the ASTE site, which also clear remaining FFX processes. If some relevant processes are still listed by the following command on aste-1c even after the stopping, ps -ef | grep ffx e.g.) # ps -ef | grep ffx root 22197 1 0 Oct11 ? 00:00:00 sh -c /home/asteffx/bin/if_bpf UW > /tmp/.ffx_exe.res root 22198 22197 0 Oct11 ? 00:00:00 /home/asteffx/bin/if_bpf UW ^^^^^ # kill 22198 # ps -ef | grep ffx root 7355 1 0 07:38 ? 00:00:00 sh -c /home/asteffx/bin/if_mtx S1USB S1LSB S2USB S2LSB > /tmp/.ffx_exe.res root 7356 7355 0 07:38 ? 00:00:00 /home/asteffx/bin/if_mtx S1USB S1LSB S2USB S2LSB ^^^^ # kill 7356 stop all of them using the KILL command by root or reboot aste-1c. Then, start COSMOS3 at the ASTE site. -- If ASTE operation supporter is available, ask the supporter to reboot aste-1c. -- If not available, ask Computing people or support scientists. -- (Added: 2016-10-14; Updated: 2017-09-15; Resolved: No; JIRA: Not created) #br // -------------------------------------------------- *** QLOOK (Line) [#s7360581] // -------------------------------------------------- ---- #br + ''Line Qlook does not show any spectra although the telescope is observing a target'' -- This looks to be communication failures between the ASTE and remote sites. -- ''Workaround'': First, restart COSMOS3 at the remote site. Second, also restart COSMOS3 at the ASTE site. -- (Added: 2016-09-30; Updated: 2016-11-26; Resolved: No; JIRA: ASTE-140) // #br + ''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'' #br #ref(whsf_spikes.png,,50%) -- 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 and never used for open-use program observations. -- ''Resolution'': Just "START TUNING" on the COSMOS3 manager GUI and then, restart your observation. -- (Added: 2016-10-05; Resolved: Yes; JIRA: None) // #br + ''Flat spectra on the Line Qlook and a warning message "Set dummy data because COR(1): SRQ #1: STOP" in the manager GUI'' + ''"Invalid scan data" on the Line Qlook and a warning message "Set dummy data because COR(1)..." in the manager GUI'' #br &ref(aste-163_qlookl1.png,,50%); &ref(aste-163_qlookl2.png,,50%); &ref(aste-163_mgui.png,,50%); -- COSMOS3 could not receive spectral data from the MAC due to unknown reasons. This is a issue specific to MAC. -- ''Workaround'': It is necessary to power-cycle the MAC. Stop COSMOS3 at the ASTE site and then, power-cycle the MAC using "mac_sw REBOOT". asteobs@aste-1c $ mac_sw REBOOT -- (Added: 2016-10-24; Resolved: No; JIRA: ASTE-163) #br // -------------------------------------------------- *** Others [#lb0c2be4] // -------------------------------------------------- ---- #br + ''The Local Controller Activity GUI is frozen and cannot be closed'' #br #ref(frozen_lact.png,,50%) -- 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) // #br + ''There are some error/warning messages like below from shm_pressure on a terminal'' ... 2016/11/12 20:55:09 ERROR shm_pressure : serial_read( 1 chars ) timeout 2016/11/12 20:55:09 ERROR shm_pressure : Read error (serial_read2) 2016/11/12 20:55:09 ERROR shm_pressure : Failed to read data 2016/11/12 20:55:09 WARNING shm_pressure : pressure read retry 2016/11/12 20:57:30 ERROR shm_pressure : serial_read( 1 chars ) timeout 2016/11/12 20:57:30 ERROR shm_pressure : Read error (serial_read2) 2016/11/12 20:57:30 ERROR shm_pressure : Failed to read data 2016/11/12 20:57:30 WARNING shm_pressure : pressure read retry ... -- shm_pressure acquires air pressure from the ASTE weather station. -- The error/warning messages suggest that shm_pressure fails to communicate with the weather station and retries it. Thus, they can be basically ignored. -- If the messages are reported frequently (every minute for 10 minutes or longer), something could be wrong with shm_pressure. -- ''Workaround'': Nothing to do. If the frequency is very high (e.g. every 30 seconds), restart COSMOS3 at the ASTE site. -- (Added: 2016-11-15; Resolved: Yes; JIRA: Not created) // #br + ''Aspirin time and/or weather time are different from current time by 30 seconds or larger'' + ''Aspirin status is NOT "( C22:on C6:OFF WIND:on )"'' Current time = 2017/07/17 02:15:27 Aspirin time = 1970/01/01 00:00:00 Weather time = 1970/01/01 00:00:00 Aspirin Offset : (Az, El) = ( 0.00, 0.00 ) Aspirin status : ** WIND ON ** ( C22:on C6:on WIND:on ) Refraction Corr. status : OK -- ''Workaround'': Restart COSMOS3 at the ASTE site. If the restart does not resolve the issue, contact with ASTE operator and/or ASTE support scientist. It could be necessary to reboot ASTE control computers (aste-1c and/or aste-v1c). -- (Added: 2017-07-17; Resolved: No; JIRA: Not created) -------------------------------------------------- ** CSV issues and their workarounds (specific to CSV activities) [#mea4296f] #br + ''No response from aste-c1c (= aste-cabin1c)'' -- aste-c1c may be down due to unknown reasons, when you try to use OPT. Recover aste-c1c using the following procedures. -- If you need help, contact with Computing. -- Loging to aste-c1c console via the terminal server "tslinux" > ssh asteobs@aste-1c > ssh asteobs@tslinux Serial Console Server Connection Menu for your Master Terminal Server 1 aste-1s 2 aste-1c 3 aste-2c 4 aste-3c 5 aste-v1c 6 aste-c1c 7 aste-r1c 8 ttyS8 Type 'q' to quit, a valid option[1-8], or anything else to refresh : 6 <--- select "6" for aste-c1c -- Pattern A: aste-c1c is down and its power-cycle is required, if nothing is displayed after the following messages Entering character/text Mode Escape character is ^] --- The way to power-cycle aste-c1c -- [asteobs@aste-1c ~]$ tap_lt1500.py lantap0 1 off POS=100,100,100,100 POF1 POS=000,100,100,100 (wait for about 10 seconds) [asteobs@aste-1c ~]$ tap_lt1500.py lantap0 1 on POS=000,100,100,100 PON1 POS=100,100,100,100 --- The following messages will start after the power-cycle -- screen not found. Can't open input device. Keyboard not present. Using ttya for input and output. FORCE,CPU-50(UltraSPARC-IIi 333MHz), No Keyboard OpenBoot 3.10.10, 256 MB memory installed, Serial #9220825. Ethernet address 0:80:42:10:43:4c, Host ID: 808cb2d9. ... aste-cabin1c console login: (It will take about 1-2 minutes after the power-cycle until the login prompt is displayed.) -- Pattern B: aste-c1c went down and restarted. But, it stopped on the way. Just type "boot". ok --- Type "boot" -- ok boot <--- Just type "boot" ... aste-cabin1c console login: -- Pattern C: aste-c1c is ready and nothing is required for it. Something could be wrong with your login method to aste-c1c. Recheck it. aste-cabin1c console login: -- Don't forget to logout from aste-c1c by "Ctrl-]" and also, tslinux by "q" #br + ''No receiver signal at TPD of WHSF, even after executing "swbox_ctl_be WHSF"'' -- It is necessary to run "swbox_ctl_pol 0 0" in the current IF configurations in addition to "swbox_ctl_be WHSF". So, follow the procedures below, when you need to switch receiver signals into WHSF by hand. [asteobs@aste-1c ~]$ swbox_ctl_pol 0 0 [asteobs@aste-1c ~]$ swbox_ctl_pol status: swbox_ctl_pol 0 0 400:P0-USB 402:P0-LSB [asteobs@aste-1c ~]$ swbox_ctl_be WHSF [asteobs@aste-1c ~]$ swbox_ctl_be status: swbox_ctl_be WHSF #br + ''観測を開始しても連続波QLOOKが更新されない'' -- 対処1 +++ 観測を停止する。 +++ 連続波QLOOKを立ち上げ直してSTARTボタンを押す。 +++ 観測を開始する。 -- 対処2(対処1で復帰しない場合) +++ 観測を停止し、連続波QLOOKを終了する。 +++ aste-1c上の連続波QLOOKサーバーを再起動する。 root@aste-1c: /cosmos3/aste/rc3.d/S98astqlcsv restart (rootパスワードが分からない場合は、COSMOS3の再起動をして下さい) asteobs@aste-1c: /cosmos3/naoj/sbin/cos3_cntl restart +++ aste-mt1上の連続波QLOOKサーバーを再起動する。 root@aste-mt1: /cosmos3/aste/rc3.d/S98astqlcsv restart (rootパスワードが分からない場合は、COSMOS3の再起動をして下さい) asteobs@aste-mt1: /cosmos3/naoj/sbin/cos3_cntl restart +++ 連続波QLOOKを立ち上げ直してSTARTボタンを押す。 +++ 観測を開始する。 #br + ''受信機制御計算機aste-recへのVNC接続、FEMC制御アプリの再起動、電源制御の方法'' -- VNC接続 +++ aste-ax1(SPdA)もしくはaste-mx1(MTK)上で端末を2つ開く +++ Terminal0において下記を実行する asteobs@aste-ax1: ssh aste-1c -L 15901:192.168.11.170:5901 +++ Terminal1において下記を実行する asteobs@aste-ax1: vncviewer localhost:15901 -- FEMC制御アプリ +++ (停止) LabView上のFEMC_TCP.viを停止(赤丸)ボタンを押して停止した後、LabViewのウィンドウを閉じる。 +++ (開始) デスクトップ上のFEMC_TCP.exeを実行した後、LabView上のFEMC_TCP.viを実行(矢印)ボタンを押して実行する。 -- 電源制御 --- 電源オフ asteobs@aste-1c: tap_lt1500.py lantap2 4 off --- 電源オン asteobs@aste-1c: tap_lt1500.py lantap2 4 on #br + ''How to restart DASBOX'' ++ Stop an observation if it is running --- It is unnecessary to stop COSMOS3. ++ Login to aste-1c with asteobs ++ Run ''dasbox_sw'' with the ''restart'' option asteobs@aste-1c: cosmos3/naoj/sbin/dasbox_sw restart DASBOX - restart /cosmos3/naoj/bin/tap_lt1500.py lantap2 1 off POS=100,100,000,100 POF1 POS=000,100,000,100 sleep 30 /cosmos3/naoj/bin/tap_lt1500.py lantap2 1 on POS=000,100,000,100 PON1 POS=100,100,000,100 sleep 180 /cosmos3/naoj/sbin/prebox Ch 0 Gain:5 (+- 0.312 V) ... Ch 10 Gain:1 (+- 5.000 V) Ch 11 Gain:1 (+- 5.000 V) Ch 12 Gain:1 (+- 5.000 V) Ch 13 Gain:0 (+- 10.000 V) ... Ch 15 Gain:0 (+- 10.000 V) Gain set PREBOX Cutoff set PREBOX asteobs@aste-1c: ++ Restart an observation // End of the page
