Differences

This shows you the differences between two versions of the page.

--- chara:trouble_shooting [2018/07/05 11:16]
jones [GUIs are frozen]
+++ chara:trouble_shooting [2018/07/05 11:19]
jones
@@ Line 201: / Line 201: @@
 DBADD is a command entered in a terminal window that allows you to add a star to the CHARA database or look up a name of a star, nova or AGN to see if it already has a CHARA number. Valid requests can look like dbadd Vega or dbadd HD 123456. Identifiers for a target can be a common name, an IRC, HR, HD, SAO, FK5, HIP, GJ, or 2MASS designation. If a star, AGN or nova is in the database, it will return a CHARA number.\\ \\ __Targets that are not in the CHARA database__\\ \\  If a star, nova or AGN is not in the CHARA database, dbadd will query the SIMBAD database to see if it can be found there. If it returns a result, the target's coordinates, magnitudes, and spectral type will be given. If this matches your object, then accept the result and a new CHARA number will be issued for the object.\\  You can also try to find another identifier for the star by using the \\ SIMBAD database: http://simbad.u-strasbg.fr/simbad/sim-fbasic\\ \\ SIMBAD will also show many other identifiers for your star and most likely will show one of the 8 database identifiers that Cosmic Debris recognizes. If you cannot find an identifier that Cosmic Debris or SIMBAD recognizes, you must enter the object manually with the instructions below. Examples of objects not identified are AGN's or novae. \\ \\ __Targets that are not in the CHARA database or in SIMBAD__\\ \\ Some objects like new novae or AGN's are not well studied and therefore are not in SIMBAD. Entering dbadd <star designation> for a star not in the SIMBAD database returns the message "Simbad is unable to find an object matching <star designation> Try using a different catalog designation, or use the "-m" switch to add the object manually." \\ \\ The command dbadd -m is used by entering the star name and coordinates in this format:\\ \\ Usage: dbadd -m <name> <RA> <Dec>\\ \\  <name>: Object ID (no spaces)\\ \\  <RA> : XXhXXmXX.X or XXhXX.X (no spaces)\\ \\  <Dec> : XXdXXmXX.X or XXdXX.X (no spaces)\\ \\ There are cases where an object is not in SIMBAD and doesn't return a result in dbadd, but is in fact in the CHARA database. Novae and AGN's are the likely objects that cause this result. At times, objects have multiple entries and several CHARA numbers since the names can be so unique. A system will be developed to find these entries without knowing or having a conventional database designation.\\ \\ __Binary stars__\\ \\  Some binary stars have a common HD number with an A or B after them. These can cause problems as Cosmic Debris does not accept non numerical entries when filling in star designation. These stars are likely in CHARA's database but need to be searched in dbadd or on SIMBAD to get the CHARA number or another designation.\\  When a recognized identifier is entered, the HD number with A or B will usually display. Confirm that the coordinates, magnitudes and spectral type match the star desired. If they do not match, you may have the wrong star or the database may have the wrong info and the baseline solution will be affected. Offsets based on incorrect coordinates or misidentifications can move the fringes many thousands of microns away from the calculated position. This can happen when observing a dim companion (B) using the brighter (A) companion's coordinates. Inform the observers that noting and using the CHARA number will save time next time the target is observed.\\ \\ __Editing the database__\\ \\ If you find a mistake in the database, please send an email to Nils to have it corrected. Identify what you believe to be the error and what is the correct information.\\ \\
 ==== Adding an anchor to the wiki page ====
- To add an anchor to the wikipage, type the following where you want the anchor inserted (without the spaces between the symbols):\\  [ [ #AnchorName ] ]\\ \\  Highlight the text you want to be a link to the anchor, click the link symbol above and select anchor. Select a page(such as Trouble Shooting) where the anchor is located and give the same name for the anchor.\\ \\ [[/Trouble%20Shooting#page.troubleshooting|Back to Main Menu]]\\ \\  Last updated 2017-04-12\\  grep bs /etc/rc.local\\ \\  6. Run it\\ \\  /usr/local/bin/esp_server /dev/ttyC1 bs &\\ \\ \\
+ To add an anchor to the wikipage, type the following where you want the anchor inserted (without the spaces between the symbols):\\  [ [ #AnchorName ] ]\\ \\  Highlight the text you want to be a link to the anchor, click the link symbol above and select anchor. Select a page(such as Trouble Shooting) where the anchor is located and give the same name for the anchor.\\ \\   Last updated 2017-04-12
-==== "Failed to request position of S1" ====
-\\  Cosmic Debris reports "Failed to request position of S1" when trying to set the beam order. This indicates that ople is no longer talking to the beam samplers. If the beam sampler server has been restarted recently, then the ople server will also need to be restarted to re-establish the connection.\\ \\  The beam sample server runs on ctrscrut. The ople server tries to open a connection to the beam sampler when it starts. If the beam sampler is not there, or dies,\\  you need to restart the ople server as there is no command to reopen that connection.\\ \\ [[/Trouble%20Shooting#page.troubleshooting|Back to Main Menu]]\\ \\
-===== __Remote Observing__ =====
-\\
-==== VPN connection is not working ====
- To re-establish the VPN connection, follow these steps:\\
-  * Open VPN status page from the firefox web broswer. To do this, click on the "AROC VPN reconnect" icon on the zoot desktop. Alternatively, you can open the firefox web browser and go to 192.168.3.1/vpn_sta.htm
-  * The browser will prompt you for the admin user name and password. If these entries are not already filled in, then look for this information on the papers near the console.
-  * If the browser does not open, then check if there are other instances of firefox already running. To do this, open a terminal window, type "ps auxw | grep firefox", and kill the other instances of firefox so that you can open a new window.
-  * When the VPN connection is working, it will report "Phase 1: M-ESTABLISHED / Phase 2: ESTABLISHED" under the state column.
-  * If either Phase 1 or Phase 2 states say IDLE for a given VPN, then you need to re-establish the connection. To do this, click on the "DROP" button for that VPN. Then click on the "CONNECT" button and wait for the Phase 1 and Phase 2 connections to be established.
-  * Make sure to close Firefox by using CTRL-Q to quit the program and not just close the window.
-\\ [[/Trouble%20Shooting#page.troubleshooting|Back to Main Menu]]\\ \\
-===== __General Problems__ =====
-\\
-==== GUIs are frozen ====
- Check to see if Sockman is working. Click the [LIST] button on sockman. If the list doesn't come up, Sockman may be hung up. Follow the Sockman restart procedure in the text file on the desktop if it won't respond.\\  Hit [REOPEN] on the gui to see if it reconnects with its server. if that does not fix it, the server may be dead. From the LIST on Sockman, select the server suspected of being frozen. Ping it and if it reports back as being dead, see [[/Trouble%20Shooting#chapter.general.frozenserver|Server is frozen]] section below.\\  Telescope guis often freeze. Hit reopen on the gui to bring it back to life. Hitting [MOVE] on the telescope gui before the star has stopped moving can cause the gui to freeze. Avoid doing this. Close the dead one and open a new one to fix the problem.\\ \\
-==== Server display is blank or filled with jibberish ====
-  * If the top of a server goes blank, try typing "sb" (start background) on the server command line.
-  * If the server screen fills with jibberish, try hitting CTRL-l in the server to clear it.
-\\
-==== Server is frozen ====
- Try quitting the server using CTRL-C and entering "Y". If that doesn't work, try the following:\\
-  * On Sockman, click [LIST] and select the appropriate server. It will give a PID number you can use to kill the server in a terminal. Open a terminal and follow the directions for Restarting Servers above.
-  * If a server window does not close, click the X in the upper right corner to close it, but only after getting the PID from Sockman.
-  * Click [REOPEN] on Cosmic Debris and relevant GUIs to re-initialize communication with the server after it is restarted.
-  * A folder is on the desktop that has the restart commands for CTRSCRUT servers and the Shutters server restart command running on OPLE. Use it to restart servers that will not reopen from the menu.
-\\
-==== PAVO Server - Error communicating with IFW ====
- The following error message sometimes appears when starting the PAVO server:\\  "Error communicating with IFW. Could not read from IFW. Is the filter wheel plugged in and on?"\\  Most of the time, restarting the PAVO server will clear this error message and allow PAVO to communicate with the filter wheel. If restarting the server doesn't help, then check that the cables going into the small, black IFW box on the PAVO table and into the back of the PAVO computer are plugged in securely.\\ \\
-==== Adding or Finding a Star in the CHARA Database ====
-DBADD is a command entered in a terminal window that allows you to add a star to the CHARA database or look up a name of a star, nova or AGN to see if it already has a CHARA number. Valid requests can look like dbadd Vega or dbadd HD 123456. Identifiers for a target can be a common name, an IRC, HR, HD, SAO, FK5, HIP, GJ, or 2MASS designation. If a star, AGN or nova is in the database, it will return a CHARA number.\\ \\ __Targets that are not in the CHARA database__\\ \\  If a star, nova or AGN is not in the CHARA database, dbadd will query the SIMBAD database to see if it can be found there. If it returns a result, the target's coordinates, magnitudes, and spectral type will be given. If this matches your object, then accept the result and a new CHARA number will be issued for the object.\\  You can also try to find another identifier for the star by using the \\ SIMBAD database: http://simbad.u-strasbg.fr/simbad/sim-fbasic\\ \\ SIMBAD will also show many other identifiers for your star and most likely will show one of the 8 database identifiers that Cosmic Debris recognizes. If you cannot find an identifier that Cosmic Debris or SIMBAD recognizes, you must enter the object manually with the instructions below. Examples of objects not identified are AGN's or novae. \\ \\ __Targets that are not in the CHARA database or in SIMBAD__\\ \\ Some objects like new novae or AGN's are not well studied and therefore are not in SIMBAD. Entering dbadd <star designation> for a star not in the SIMBAD database returns the message "Simbad is unable to find an object matching <star designation> Try using a different catalog designation, or use the "-m" switch to add the object manually." \\ \\ The command dbadd -m is used by entering the star name and coordinates in this format:\\ \\ Usage: dbadd -m <name> <RA> <Dec>\\ \\  <name>: Object ID (no spaces)\\ \\  <RA> : XXhXXmXX.X or XXhXX.X (no spaces)\\ \\  <Dec> : XXdXXmXX.X or XXdXX.X (no spaces)\\ \\ There are cases where an object is not in SIMBAD and doesn't return a result in dbadd, but is in fact in the CHARA database. Novae and AGN's are the likely objects that cause this result. At times, objects have multiple entries and several CHARA numbers since the names can be so unique. A system will be developed to find these entries without knowing or having a conventional database designation.\\ \\ __Binary stars__\\ \\  Some binary stars have a common HD number with an A or B after them. These can cause problems as Cosmic Debris does not accept non numerical entries when filling in star designation. These stars are likely in CHARA's database but need to be searched in dbadd or on SIMBAD to get the CHARA number or another designation.\\  When a recognized identifier is entered, the HD number with A or B will usually display. Confirm that the coordinates, magnitudes and spectral type match the star desired. If they do not match, you may have the wrong star or the database may have the wrong info and the baseline solution will be affected. Offsets based on incorrect coordinates or misidentifications can move the fringes many thousands of microns away from the calculated position. This can happen when observing a dim companion (B) using the brighter (A) companion's coordinates. Inform the observers that noting and using the CHARA number will save time next time the target is observed.\\ \\ __Editing the database__\\ \\ If you find a mistake in the database, please send an email to Nils to have it corrected. Identify what you believe to be the error and what is the correct information.\\ \\
-==== Adding an anchor to the wiki page ====
- To add an anchor to the wikipage, type the following where you want the anchor inserted (without the spaces between the symbols):\\  [ [ #AnchorName ] ]\\ \\  Highlight the text you want to be a link to the anchor, click the link symbol above and select anchor. Select a page(such as Trouble Shooting) where the anchor is located and give the same name for the anchor.\\ \\ [[/Trouble%20Shooting#page.troubleshooting|Back to Main Menu]]\\ \\  Last updated 2017-04-12

The CHARA Array Wiki

User Tools

Site Tools

Differences

Page Tools