ASTAP Name does not match with VSX

Community
1

Hello everyone,

I am new here and still need some help.

I have collected observations of a star that ASTAP identifies as a variable star. In ASTAP, the object is listed as “ASAS J145842-0033.2”.

When I try to upload my data set, I receive an error message stating that this is not a valid name (AUID) in VSX.

I have spent some time researching the issue, but so far I have not been able to determine the correct AAVSO/VSX designation for this object.

Could someone help me identify the proper name under which this star is listed in the AAVSO database?

Thank you very much for your assistance.

Best regards, Alexander Pistorius

2

  1. Have you found the VSX tool on the main web page?

  2. Log in, it takes a separate PW.

  3. Search for “ASAS J145842-0033.2”

  4. Request an AUID.

HTH,

Ken

3

Thank you very much. That helped a lot.

1 Like
4

I wonder if the local VSX could be connected to SIMBAD, where the star is unambiguously identified as BD+00 3283. The AUID is not used anywhere outside the AAVSO, so why add another layer of acronyms?

\Brian

5

I have found the same issue with different stars using ASTAP. Look at the AAVSO report generated by ASTAP, and it occasionally will truncate the last part of the name after the initial space. I have to go and manually edit the report and add the part of the name after the initial space. I talked to Han about this, and I thought it was resolved in one of the last updates.

Anyway, the cut and paste of the name after the space is a work around.

Scott (MDSA)

6

I’m an absolute beginner and am currently reading up on and working with the topic of photometry. I find it incredibly fascinating—you pursue your favorite hobby and at the same time provide data for something meaningful. ASTAP itself is incredibly powerful and useful. I do the calibration process first in SIRIL and then switch to ASTAP for the final photometry. Sometimes, there’s a nice “bycatch” in a photo series that can also be used.

7

It wasn’t a name issue. It is just that lots of objects in the AID do not have AUIDs and AUIDs are required to submit data. We do not support observations of everything. If there is no issue (crowding, too small an amplitude, faintness), an AUID will be assigned automatically if you log in to VSX and click on the Request AUID button.