AAVSO HOME > observing > submit > extended format
 
 
 
Observing
Observing Programs
Observing Aids
Submit Observations
  WebObs - Submit online
  PCObs - Format your obs
  Format specifications
Charts
 
Main sections of web
The AAVSO
Variable Stars
Observing
Access Data
Publications
Support
Education and Outreach
 
Pick a star

Create a light curve
Recent Observations
Find charts
VSX      
  Official AAVSO Extended Format

Version: 1.0
Release Date: January 15, 2008

This is one of two ASCII formats that the AAVSO accepts for variable star observations. Observations in this format may be submitted to the AAVSO by uploading them via the WebObs Batch Upload Tool for ccd observations, or by e-mailing them to observations @ aavso.org. The other format, which is intended for visual observers, is called the Official AAVSO Visual Format.

The extended format has two components: parameters and data. Each component is discussed in detail below.

The format is not case sensitive.

Parameters

The Parameters are specified at the top of the file and are used to describe the data that follows. Parameters must begin with a pound sign (#) at the start of the line. There are six specific parameters that we require to exist at the top of the file. Personal comments may also be added as long as they follow a pound sign (#). These comments will be ignored by the software and not loaded into the database. However, they will be retained when the complete file is stored in the AAVSO permanent archives.

The six parameters that we require are:

#TYPE=Extended
#OBSCODE=
#SOFTWARE=
#DELIM=
#DATE=
#OBSTYPE=

The six parameters explained:

  • TYPE: Should always say Extended for this format.
  • OBSCODE: The official AAVSO Observer Code for the observer which was previously assigned by the AAVSO. Request AAVSO Observer Initials here.
  • SOFTWARE: Name and version of software used to create the format. If it is private software, put some type of description here. For example: "#SOFTWARE=AIP4Win Version 2.2". This is limited to 30 characters.
  • DELIM: The delimiter used to separate fields in the report. Any ASCII character or UNICODE number that corresponds to ascii code 32-126 is acceptable as long as it is not used in any field. Suggested delimiters are: comma (,) semi-colon(;), exclamation point(!), and pipe(|). The only character that cannot be used is the pound (#) and the " " (space). If you want to use a tab, use the word "tab" instead of an actual tab character. Note: Excel users who want to use a comma will have to type "comma" here instead of a ",". Otherwise Excel will export the field incorrectly.
  • DATE: The format of the date used in the report. Convert all times from UT to one of the following formats:
    • JD: Julian Day (Ex: 2454101.7563)
    • HJD: Heliocentric Julian Day
    • EXCEL: the format created by Excel's NOW() function (Ex: 12/31/2007 12:59:59 a.m )
  • OBSTYPE: The type of observation in the data file. It can be CCD or PEP (for Photoelectric Photometry). If absent, it is assumed to be CCD.

The OBSCODE and DATE parameters may also be included elsewhere in the data. Our data processing software will read these parameters and will expect all following data to adhere to them. (For example, you can add "#OBSCODE=TST01" to the report and all subsequent observations will be attributed to observer TST01.)

Data

After the parameters comes the actual variable star observations. There should be one observation per line and the fields should be separated by the same character that is defined in the DELIM parameter field. If you do not have data for one of the optional fields, you must put "na" as a place holder. The list of fields are:

  • NAME: The star's identifier. It can be the AAVSO Designation, the AAVSO Name, or the AAVSO Unique Identifier
  • DATE: The date of the observation, in the format specified in the DATE parameter.
  • MAGNITUDE: The magnitude of the observation. Prepend with < if a fainter-than.
  • MAGERR: Photometric uncertainty associated with the variable star magnitude. If not available put "na".
  • FILTER: The filter used for the observation. This can be one of the following letters (in bold):
    • U: Johnson U
    • B: Johnson B
    • V: Johnson V
    • R: Cousins R
    • I: Cousins I
    • J: NIR 1.2 micron
    • H: NIR 1.6 micron
    • K: NIR 2.2 micron
    • TG: Green Filter
    • Z: Sloan Z
    • CV: Clear (unfiltered), V-band comp star magnitudes (this is more common than CR)
    • CR: Clear (unfiltered), R-band comp star magnitudes

  • TRANS: YES if transformed, NO if not.
  • MTYPE: Magnitude type. DIF if differential, ABS if absolute. Differential requires the use of CNAME.
  • CNAME: Comparison star name or label such as the chart label or the AUID for the comparison star used. If not present, use "na".
  • CMAG: Measured magnitude of the comparison star. If not present, use "na".
  • KNAME: Check star name or label such as the chart label or AUID for the check star. If not present, use "na".
  • KMAG: Measured magnitude of the check star. If not present, use "na".
  • AIRMASS: Airmass of observation. If not present, use "na".
  • GROUP: Grouping identifier (maximum 5 characters). It is used for grouping multiple observations together, usually an observation set that was taken through multiple filters. It makes it easier to retrieve all magnitudes from a given set in the database, say, if someone wanted to form color indices such as (B-V) with them. If you are just doing time series, or using the same filter for multiple stars, etc., just set GROUP to "na." For cases where you want to group observations, GROUP should be an integer, identical for all observations in a group, and unique for a given observer for a given star on a given Julian Date.

  • CHART: This should be the latest date you see anywhere on the chart, entered as YYMMDD. If you do not see a date, use the copyright year (Ex: "Copyright 2007" would be 070101). If no chart used, enter "na".
  • NOTES: Comments or notes about the observation. This field has a maximum length of 100 characters. If no comments, use "na".

Examples

1. A simple example: 

#TYPE=EXTENDED
#OBSCODE=TST01
#SOFTWARE=IRAF 12.4
#DELIM=,
#DATE=JD
SS CYG,2450702.1234,11.135,0.003,V,NO,ABS,105,na,na,na,na,na,070613,This is a test

2. A little more information: 

#TYPE=EXTENDED
#OBSCODE=TST01
#SOFTWARE=GCX 2.0
#DELIM=,
#DATE=JD
#OBSTYPE=CCD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
SS CYG,2450702.1234,11.235,0.003,B,NO,ABS,105,10.593,110,11.090,1.561,1,070613,na 
SS CYG,2450702.1254,11.135,0.003,V,NO,ABS,105,10.492,110,10.994,1.563,1,070613,na 
SS CYG,2450702.1274,11.035,0.003,R,NO,ABS,105,10.398,110,10.896,1.564,1,070613,na 
SS CYG,2450702.1294,10.935,0.003,I,NO,ABS,105,10.295,110,10.793,1.567,1,070613,na

Note the existence of the #NAME,DATE... line in the above format. Since it is prepended with a #, it will be ignored by our software. Feel free to do this if it makes writing and reading the format easier for you.

3. Ensemble photometry example:

Ensemble photometry is permitted under this format. You need to pick one star (the check star) in addition to the target to be measured by the technique. This star's calculated magnitude should be put in the KMAG field, so that if the true magnitude of the check star is found to be different at a later date, a simple zeropoint offset can be added to your ensemble value. If ensemble is used, CNAME should be set to ENSEMBLE and CMAG should be set to "na", as shown below. 

#TYPE=EXTENDED
#OBSCODE=TST01
#SOFTWARE=GCX 2.0
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
SS CYG,2450702.1234,11.235,0.003,B,NO,ABS,ENSEMBLE,na,105,10.593,1.561,1,070613,na 
SS CYG,2450702.1254,11.135,0.003,V,NO,ABS,ENSEMBLE,na,105,10.492,1.563,1,070613,na 
SS CYG,2450702.1274,11.035,0.003,R,NO,ABS,ENSEMBLE,na,105,10.398,1.564,1,070613,na 
SS CYG,2450702.1294,10.935,0.003,I,NO,ABS,ENSEMBLE,na,105,10.295,1.567,1,070613,na 
SS CYG,2450702.2234,11.244,0.003,B,NO,ABS,ENSEMBLE,na,105,10.590,1.661,2,070613,na 
SS CYG,2450702.2254,11.166,0.003,V,NO,ABS,ENSEMBLE,na,105,10.497,1.663,2,070613,na 
SS CYG,2450702.2274,11.030,0.003,R,NO,ABS,ENSEMBLE,na,105,10.402,1.664,2,070613,na 
SS CYG,2450702.2294,10.927,0.003,I,NO,ABS,ENSEMBLE,na,105,10.292,1.667,2,070613,na

This means your ensemble solution gave 11.235, 11.135, 11.035 and 10.935 for the B,V,Rc, and Ic (respectively) magnitudes of SS Cyg for the first group, and 11.244, 11.116, 11.030 and 10.927 for the second group. Your ensemble solution also gave 10.593, 10.492, 10.398, and 10.295 for the BVRcIc magnitudes of the check star for the first group.

4. Differential photometry example (not recommended):

Differential photometry is permitted under this format. CNAME should be the name of the comparison star (chart label, GSC number, etc.), CMAG should be its instrumental magnitude, KNAME should be the name of the check star and KMAG should be the instrumental magnitude of the check star. In this manner, HQ can calculate (K-C) to determine a time-series error, and HQ can also adjust the MAG field if at some later date the true standard magnitude of the comparison star becomes known. We highly recommend that you use "ABS" (absolute) instead of DIF (differential) as your data will not appear on the light curve generator, nor be properly validated otherwise. Here is an example of the differential format: 

#TYPE=EXTENDED
#OBSCODE=TST01
#SOFTWARE=GCX 2.0
#DELIM=,
#DATE=JD
#NAME,DATE,MAG,MERR,FILT,TRANS,MTYPE,CNAME,CMAG,KNAME,KMAG,AMASS,GROUP,CHART,NOTES
SS CYG,2450702.1234,1.065,0.003,B,NO,DIF,105,10.170,110,11.090,1.561,1,070613,na 
SS CYG,2450702.1254,1.114,0.003,V,NO,DIF,105,10.021,110,10.994,1.563,1,070613,na 
SS CYG,2450702.1274,1.001,0.003,R,NO,DIF,105,10.034,110,10.896,1.564,1,070613,na 
SS CYG,2450702.1294,.988,0.003,I,NO,DIF,105,9.947,110,10.793,1.567,1,070613,na

Please contact aavso@aavso.org if you have any questions.

To keep your observer information up-to-date in the AAVSO records, please make any necessary changes using our online Update Observer Information Form.

 
  search engine |  site map |  links |  contact us