Uploading stellar data
Global asteroseismic and classical surface parameters
Upload a whitespace-separated ASCII file of stellar parameters for your stars. The first line must be a header starting with #, and the first column should contain a unique string ID for each star (“starid”) which should be utf-8 compliant, without spaces.
All succeeding column names must match the BASTA parameter list. For every measured quantity (at least those you want to fit against), provide an uncertainty column with the same name plus *_err (e.g. “Teff”, “Teff_err”).
If you want BASTA to estimate distance or fit for parallax, you need to include the sky coordinates and the star’s apparent brightness (in at least one photometric filter, see recognized filters). If you want to fit for parallax, its value and its uncertainty must be included too.
If you also want to fit against individual frequencies, you need to include \(\Delta \nu\) and \(\nu_\mathrm{max}\) with your stellar parameters (although not used directly in the fitting).
Use a single, consistent placeholder for missing values (e.g. -999.99). Download an example stellar data file.
Distance Estimation or parallax fitting
If you want BASTA to estimate distance or fit parallax you need to select whether to use the equatorial (RA, Dec) or galactic coordinate (l, b) system, as well as selecting which photometric filter(s) (at least one) to use for the apparent brightness. Finally, you need to select whether to estimate distance or fitting for parallax or none of them.
Individual frequencies
You can provide a separate ASCII file for each star if fitting individual mode frequencies or frequency ratios. The name of each file must exactly match the corresponding starid specified in the stellar data file, with extension *.fre; each header should again start with #.
At minimum, include the angular degree of each mode (labelled “l”, “ell” or “degree”), the mode frequency (“freq” or “frequency”) and their uncertainties.
Uncertainties should be a single column for symmetric (“err” or “error”), or two columns for asymmetric (“error_plus” and “error_minus”).
Optionally, you may also include the radial order (“order” or “n”) if available. Download an example frequency file. Otherwise BASTA estimates the radial order based on the radial modes, assuming they are continuous without any gaps in radial order!