The ATLAS-VAR data release is a catalog of variable stars discovered from ATLAS data. The first data release, presented here, consists of variable stars identified from 1.4 x 108 stars down to a limiting magnitude of r ~ 18 that obtained a minimum of 100 observations during the first two years of ATLAS operations. A total of 4.7 million variable star candidates are detected, using a Lomb-Scargle periodogram and several variability metrics described in Heinze et al. (2018).
The data products contain three catalog tables: object, observation, and detection.
The catalog of candidate variable stars has the following name:
The catalog of all ATLAS images for DR1 has the following name:
Data file types:
|_object.fits||The catalog of candidate stars|
|The catalog of all images used for DR1|
The "detection" table is only available through in the "HLSP_ATLAS_VAR" Context within MAST CasJobs. See Data Access below.
The primary way to interact with the ATLAS-VAR catalog tables is through MAST CasJobs. For convenience, we also provide the "object" and "observation" tables as binary FITS files below, but the "detection" table is only available through MAST CasJobs.
|~74 MB||Object Catalog|
|~8.5 GB||Image Catalog|
The catalog is also available through in the "HLSP_ATLAS_VAR" Context within MAST CasJobs. The "detection" table (all ATLAS photometric measurements of all the candidate variables) is only available via the MAST CasJobs SQL interface.
For more information about MAST CasJobs, click the "Expand All" or '+' link below.
Note that MAST CasJobs accounts are separate from STScI accounts. After logging in, you can navigate to the ATLAS_VAR tables by following MyDB (in the top menu bar) → HLSP_ATLAS_VAR (in the drop-down menu at the top-left). You can click on one of the tables and then hit the Sample button to get some example rows. The column names and data types are always available in the Table Schema underneath the Notes and Sample buttons.
You can execute SQL queries by visiting the Query tab in the top menu bar. Make sure you change the Context drop-down menu to HLSP_ATLAS_VAR. We have provided a few tutorials that demonstrate how to query the ATLAS-VAR variable star catalog.
NOTE: When entering these examples into CasJobs, do NOT include the numbers or pipe characters ("|"), those are only used to reference the line numbers here.
A web-based SQL interface to query and cross-match between catalogs. Export tables, saved queries, long query submissions.
Tutorial 1: Select 10 Targets Classified As "Pulse" With a Period Between 0.3 and 0.9 Days And Return The Cyan Filter Light Curves
WITH ctePLUS (ATO_ID, class, fp_period, objid) as (select top 10 ATO_ID, class, fp_period, objid from object where class='PULSE' and fp_period between 0.3 and 0.9) select o.ATO_ID, o.class, o.fp_period, d.filter, d.m, d.mjd from ctePLUS as o inner join detection as d on o.objid=d.objid where d.filter='c' order by o.ATO_ID, d.mjd
Line 1: randomly selects 10 targets from the "object" table that have class="PULSE" and a period between 0.3 and 0.9 days. The ATO_ID, class, fp_period, and objid columns are selected for these 10 targets and assigned to the "ctePLUS" variable.
Line 2: selects the ATO_ID, class, and fp_period values from the "ctePLUS" variable we created in Line 1, and selects the filter, m, and mjd columns from the "detection" table.
Line 3: assigns the "ctePLUS" variable to "o" and the "detection" table as "d" so that they can be used as short-hand elsewhere, for example, Lines 2, 4, and 5. It also performs a "join" between the "ctePLUS" variable and the "detection" table using the "objid" column from both. The "objid" column is a common key that allows SQL to combine the information in the "ctePLUS" and "detection" tables using this column as a common link between the two.
Line 4: applies a further constraint to only return the "cyan" ATLAS filter data.
Line 5: orders the output table by first the ATO_ID, then the MJD.
Tutorial 2: Do A Cone Search Centered On A Specified RA, Dec Coordinate And Return Light Curves For Both Cyan And Orange Filters
1| select o.objid, o.ra, o.dec, d.mjd, d.m, d.dm, d.filter 2| from fGetNearbyObjEq(295.85266, 19.82466, 300./3600.) as nb 3| inner join object as o on o.objid = nb.ObjID 4| inner join detection as d on o.objid = d.objid 5| order by o.objid, d.filter, d.mjd 6| into myDB.cone_search_results
Line 2: executes a cone search centered on a specified RA and Dec coordinates (in degrees). The search radius is the third argument and must be given in degrees (in our example, the search radius is set to 300 arcseconds). The result of this cone search is given a nickname of "nb" for shorthand use later.
Line 3: performs a "join" combining the columns we want from the "observation" table with the output columns of our cone search using the object ID columns from both as a common key.
Line 4: performs another "join", this time combining the columns we want from the "detection" table with the "observation" table, again using the object ID columns from both as a common key.
Line 5: orders the output to be sorted first by object ID, then by filter, then by timestamp.
Line 6: then stores the result in your output space (MyDB) in a table called "cone_search_results". You can then examine, download, or even use the output table in other queries. You can visit the MyDB tab in the top menu and choose "MyDB" to access any output tables you've made. Make sure the Context drop-down menu in the upper left of the "MyDB" tab page is set to "MyDB" to see your output tables.