Differences

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

--- chara:trouble_shooting [2018/09/25 16:10]
gail_stargazer
+++ chara:trouble_shooting [2018/09/25 18:57]
gail_stargazer
@@ Line 301: / Line 301: @@
 In the example above, the object "BD+41 3807" has been added to the database as CHARA number 320414.
- \\ __Targets that are not in the CHARA database or in SIMBAD__ \\  \\ Some objects like recently discovered novae 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.
+ \\ __Targets that are not in SIMBAD__ \\  \\ Some objects like recently discovered novae 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.

The CHARA Array Wiki

User Tools

Site Tools

Differences

Page Tools