Frequently Asked Questions
FORUM
- Where can I get help before submitting a new variable star to VSX?
General questions about submitting new variable stars and submissions can be asked on the AAVSO VSX Forum.
To start discussions in the VSX Forum you have to create an AAVSO website account.
Many people who know how to properly submit stars and combine data from different sources are members of the Forum as well as skilled data analysts who might help answer any questions or doubts that new VSX users may have.
They will also be able to correctly identify the type of a new variable star.
Announcements about new VSX features will also be announced on the Forum.
DISCOVERY CREDIT
- How to proceed when a variable star is found in VizieR but not in VSX?
The discoverers should be credited.
The primary name should be the one given in the discovery paper (with some exceptions,
e.g.: the Pan-STARRS1 RR Lyrae candidates in 2017AJ....153..204S have no star identifier).
If the star is not in VSX and is published with a wrong classification, you can add yourself as co-discoverer.
The new ATLAS catalog of variable stars 2018AJ....156..241H is a special case.
It contains almost 5 million candidates and is full of spurious entries.
Add the ATLAS (ATO) identifier when the star is published there but you can ignore the ATLAS team as discoverers when the star is classified
as dubious.
Add the ATLAS team as co-discoverers when the star has any other classification.
Add them as the only discoverers when the star is both classified as variable and also has the correct type.
In all cases (except for the dubious objects in the ATLAS catalogue), a reference to the discovery paper should be added.
A cross-identifier should always be provided (if available).
DATA-MINING
- May/should I use survey data in my submissions?
You can not only discover new variable stars by data-mining the publicly available survey data, you can also combine survey observations with
yours when you find new objects with your own data.
Using those observations spanning several months or years, you will be able to improve the elements for your star. And when you only have a
few observations, they may even allow you to classify it and solve it without the need of your own follow-up.
The easiest way to look for survey data is to use the external links in the VSX star page (for new objects, you can also do it after a positional search).
Because of security issues ASAS-SN epoch photometry is not available through the external links.
- Should the magnitudes from surveys be taken at face value?
NO. The different surveys have different resolution, this means that nearby stars will affect the photometry differently depending on
the survey, you have to check VizieR for the presence of companions in order to perform a correction if needed.
For the approximate distances in arcseconds where a companion will be included in the survey photometric aperture, see the Guidelines.
For bright stars contamination may reach longer distances.
A spreadsheet is available to correct for light contamination.
A remark should be added to indicate if a correction was applied (recommended) or not and to provide information about the identification,
magnitude and distance of the companions.
E.g.: "ASAS-3 magnitudes contaminated by GSC 00000-00000 (V= 14.5; sep. 17"). Range has been corrected."
REFERENCES
- Should I add a reference when I submit a discovery or a revision based on data-mining results?
Yes. Always add the survey reference when you use their data. Also the star identifier(s) in that survey should be added to the Other names field.
Some complete references of the most widely used surveys with their proper formats are:
| APASS | | Reference name: | Henden, A. A.; et al., 2018, AAVSO Photometric All Sky Survey (APASS) DR10 | | Reference bibcode: | 2018AAS...23222306H | | ASAS-3 | | Reference name: | Pojmanski, G., 2002, The All Sky Automated Survey | | Reference bibcode: | 2002AcA....52..397P | | ASAS-SN | | Reference name: | Kochanek, C. S.; et al., 2017, The All-Sky Automated Survey for Supernovae (ASAS-SN) Light Curve Server v1.0 | | Reference bibcode: | 2017PASP..129j4502K | | ATLAS online data | | Reference name: | Tonry, J. L.; et al., 2018, ATLAS: A High-cadence All-sky Survey System | | Reference bibcode: | 2018PASP..130f4505T | | ATLAS variables | | Reference name: | Heinze, A. N.; et al., 2018, A First Catalog of Variable Stars Measured by the Asteroid Terrestrial-impact Last Alert System (ATLAS) | | Reference bibcode: | 2018AJ....156..241H | | CRTS | | Reference name: | Drake, A. J.; et al., 2009, Catalina Real-time Transient Survey | | Reference bibcode: | 2009ApJ...696..870D | | Gaia DR3 photometry | | Reference name: | Gaia collaboration; et al., 2022, Gaia Data Release 3 (Gaia DR3) Part 1 Main source | | Reference bibcode: | 2022yCat.1355....0G | | Gaia DR3 variables | | Reference name: | Gaia collaboration; et al., 2022, Gaia Data Release 3 (Gaia DR3) Part 4 Variability | | Reference bibcode: | 2022yCat.1358....0G | | HIPPARCOS | | Reference name: | Perryman, M. A. C.; et al., 1997, The HIPPARCOS and TYCHO catalogues | | Reference bibcode: | 1997HIP...C......0E | | K2 | | Reference name: | Howell, S. B.; et al., 2014, The K2 Mission: Characterization and Early Results | | Reference bibcode: | 2014PASP..126..398H | | NSVS | | Reference name: | Wozniak, P. R.; et al., 2004, Northern Sky Variability Survey: Public Data Release | | Reference bibcode: | 2004AJ....127.2436W | | Pan-STARRS1 | | Reference name: | Chambers, K. C.; et al., 2016, The Pan-STARRS1 Surveys | | Reference bibcode: | 2016arXiv161205560C | | SuperWASP | | Reference name: | Butters, O. W.; et al., 2010, The first WASP public data release | | Reference bibcode: | 2010A&A...520L..10B | | TESS | | Reference name: | Ricker, G. R.; et al., 2014, Transiting Exoplanet Survey Satellite (TESS) | | Reference bibcode: | 2014SPIE.9143E..20R | | TESS QLP | | Reference name: | Huang, C. X.; et al., 2020, Photometry of 10 Million Stars from the First Two Years of TESS Full Frame Images: Part I | | Reference bibcode: | 2020RNAAS...4..204H | | ZTF | | Reference name: | Masci, F. J.; et al., 2019, The Zwicky Transient Facility: Data Processing, Products, and Archive | | Reference bibcode: | 2019PASP..131a8003M |
PHOTOMETRY AND PASSBANDS
- Where do I get magnitudes for my comparison stars?
Most of the new objects will not have sequences available through VSP so here are
some recommendations.
If the star is brighter than V= 10.5 (and fainter than 7th mag., for bright stars you should use the GCPD or HIPPARCOS) and South of +28º,
you'll have a V-mag. from ASAS-3
(and you'll be able to combine ASAS-3 data with yours the same way as you are doing with the data from other surveys, like NSVS data for
northern stars).
For stars fainter than V= 10.0 (it saturates at brighter magnitudes) you have APASS V magnitudes. They are available through VizieR.
If there are no APASS or ASAS-3 data, you can get a V magnitude from UCAC3 (UCAC4 has zero point issues) and CMC15 using 2MASS colors.
Note that UCAC3 is not a default VizieR catalog. Get both the f and a magnitudes (choose the faintest result you get) and enter
the UCAC4 position.
For fainter stars, IPHAS,
VPHAS and
SDSS can also be used to get good V magnitudes
(also Rc magnitudes). Remember that transformed values
are not as accurate as measures taken with the original passband filters but can be used when nothing else is available.
A transformation spreadsheet is available.
- What passband should I use for my report?
There are several options regarding passbands. It depends on your set-up.
Are you observing with filters (V?, Rc?, Ic?) or unfiltered (clear)?
If you use filters you have to choose comparison stars with magnitudes measured on the corresponding filter and give a range.
If you are going unfiltered, you can give a mean magnitude (e.g. V or Rc from APASS) from a catalogue as the maximum value and an amplitude
based on your observations with the passband "clear" and the "Minimum is an amplitude" box marked as the minimum value.
If you are using comparison stars to get your ranges, depending on the passband of those magnitudes, your ranges should be CR (R mags. used
for the comparison stars) or CV (V mags. used for the comparison stars). Most CCDs have an R-like response so CR is usually the one to be
chosen.
"clear" is not a passband per se so it should not be used in the maximum magnitude field.
- How should I determine the magnitude range of a variable?
Scatter should always be taken into account. Do not include outliers in the determination. Derive mean magnitudes both for the maximum
and minimum fields. In the case of strictly periodic variables without mean magnitude changes, get mean magnitudes from the phase plot.
In the case of objects with mean magnitude and amplitude changes between cycles (SR, M, RS, etc.), derive a mean magnitude for the brightest
and faintest recorded cycles.
REMARKS AND COMMENTS
- What should I include in the remarks field?
The remarks field is meant to include additional information on the star or the photometry.
- NO URLs or references of any kind should be written there. They belong to the Reference fields.
- NO information that could be included in the main table should be written here as a remark.
E.g.: "The correct position is..." --> If an improved position is found, it should replace the current one in the main table.
Use the revision form to modify parameters included in the main table.
- What is the revision comment meant for?
That field is used to list all the changes made in a revision with the corresponding sources used to make those changes.
E.g.: "Type, period, epoch and range from ASAS-3 data. UCAC4 position."
In the case of new stars, that field is meant to list additional sources used to modify some parameters in the submission that are not
included in the reference given or are not derived from the observer's own data analysis.
E.g.: "Mean magnitude from APASS. PPMXL position."
SUBMISSION
- May I leave some of the submission form fields blank?
- You have to provide as much information as possible.
- You always have to upload supporting documentation (e.g.: a phase plot for periodic variables and a JD light curve for irregular objects) or a reference if the star was formally published.
- You should always provide a magnitude range or a mean magnitude and an amplitude.
- You should always specify the passband of your observations.
- You always have to classify the variable (check the Variability types document for more information). If the classification is not confirmed, mark the uncertainty box.
- DO NOT mark the uncertainty box for empty fields. E.g.: if there is no period given, there is no uncertainty.
- DO NOT fill in fields that are not relevant to your submission. E.g.: if your object is not a nova, do not write a year in the "Outburst (nova) year" field.
- Is it acceptable to submit an object with only one night of data and without any classification?
Nowadays the number of variable stars have increased exponentially. If you find a new variable star, we recommend that you dedicate at least
the minimum time/effort required to classify it and determine its elements (for periodic variables).
There may be exceptions, like a single flare detected in a red dwarf (spectroscopic or multicolor archival data can be used to confirm its
classification) or a single eclipse in an EA-type that cannot be confirmed with follow-up or survey observations.
SUPPORTING DOCUMENTATION
- What should I provide as supporting documentation?
- A phase plot is required for periodic variables.
- A JD light curve should be uploaded for irregular variables.
- A finding chart should be provided for objects in crowded fields especially if they are not included in astrometric catalogues or do not
have reliable cross-identifications.
- What should the phase plot look like?
It is a good idea to display more than one variability cycle in phase plots so the light curve shape can be clearly seen.
- Display phase 0 to 2 in the case of pulsating variables so the maximum is displayed in the middle.
- Display phases -0.25 to 1.25 (or -0.5 to 1.5) in the case of eclipsing binaries so the secondary eclipse is displayed in the middle.
Phase 0 in the phase plot should be the epoch given in the table.
Remember that an epoch of maximum has to be given in the case of most pulsating variables (with the exception of RV Tauri stars and SR
variables displaying LSP (Long Secondary Periods)) and hot-spotted stars and an epoch of minimum has to be given in the case of eclipsing
binaries, ellipsoidal variables and dark-spotted stars.
STAR IDENTIFIERS
- Can I copy the star identifiers from VizieR and paste them to the Other names field?
Be careful with formats. SIMBAD lists identifiers with the proper formats but
it is not complete.
VizieR will include all data and identifiers for your object but sometimes catalogue acronyms will be in the column header and not in the
information field so you need to be careful.
The VSX New Star form and the VSX guidelines have examples of correct formats.
- Always add a J before the positional part of the J2000.0 coordinate-based identifiers (e.g. 2MASS J23171981+3102538, not 2MASS 23171981+3102538).
- GSC identifiers use leading zeroes but Tycho identifiers do not (e.g. GSC 01800-02202; TYC 1800-2202-1).
Check formats in the Dictionary of Nomenclature of Celestial Objects.
- What cross-identifiers should I write in the Other names field?
It depends on the star's brightness. Bright stars will have lots of names because they will be included in old classical catalogues like HR,
HD, SAO, BD, CD, CPD, PPM, HIP, TYC, GSC, etc.
Faint stars will only have identifiers from more recent and deeper surveys like 2MASS, UCAC4, GSC2.3, USNO-B1.0, IPHAS, SDSS, CMC15, etc.
It does not make sense to give GSC2.3 or CMC15 identifiers for a 5th magnitude star that already has all the bright star names because those
IDs won't ever be used to identify it.
AAVSO Unique Identifier (AUID)
- How can I request an AUID to submit my data?
A variable star should have an AAVSO Unique Identifier (AUID) before observations of that star can be submitted to the AAVSO.
Use the Request AUID link in the AAVSO UID field if you need to submit data for a star without an AUID.
An AUID will be assigned automatically if the star is a known confirmed variable with an acceptable range.
If we do not encourage observations of that object (e.g. constant stars, stars with extremely low amplitudes),
VSX moderators will contact you in order to get more details or assign the AUID eventually after checking the current data.
Using VSX to request an AUID is the fastest way to get an AUID assigned. E-mails to HQ may take several days to be acted upon.
- Should I request AUIDs for every variable in my field of view?
No. Please do not submit AUID requests for stars with extremely low amplitudes (e.g. Kepler microvariables). All those variables are in VSX
but we do not encourage observations from the ground for them because the required photometric precision cannot be reached.
- Can I use the AUID of a variable star to submit observations?
AUIDs are internal identifiers used only by AAVSO and may change for various reasons. So they should not be used to submit observations of variable stars.
Instead, use the primary name (preferred) or an alias present in VSX. To identify comparison stars however, you may use their AUID.
COMPARISON SEQUENCE
- Can I request a comparison star sequence from VSX?
Yes, you can. To the right of the Constellation field in the Detail Sheet of a variable star, you can click on the Sequence link.
In a separate window, you will get an overview of the existing comparison stars in the neighbourhood of the variable.
If you are logged in to VSX, there is a form at the bottom to request a comparison star sequence.
It will send an email as described here with most of the required details already filled in (except for the three fields in the form).
You will receive a copy of that email.
LOGIN PROBLEMS
- Do you have problems logging into VSX?
If you have problems logging in to VSX and a password reset did not work, try to log in again after deleting the
PHPSESSID cookie for aavso.org (e.g. by clearing the browser cache).
|
|
