Home Help Tools Create Account Login   Not Logged in



Greetings and Introduction

1. Provenance and Purposes of CasJobs

CasJobs was originally developed by JHU/SDSS team, a copy of which was given to MAST. Until recently it has been used for downloading target results for GALEX objects, and you will see reference to the GALEX table as well as Kepler in some pages. MAST has posted the latest version (v3.5.16). This greeting and the Guide pages have been written for use with Kepler data. Acknowledgments of the use of CasJobs in publications should note that its authorship by the JHU/SDSS team. The url for the original site is http://casjobs.sdss.org/CasJobs.

The purpose of CasJobs is to permit large queries, phrased in SQL, to be run in batch queue, such that they don't interfere with execution of small queries run in real time. A Quick run button on the open "Query" page is provided to test submission syntax. Note that no email notification is provided when a job is completed.

Please note that CasJobs will enable you to obtain metadata (field descriptions, including Kepler IDs) if you've entered coordinate values in an object upload file. If you are searching on large numbers of targets (above several thousand) this is the page for you. However, if you are interested in downloads of all these objects, this will be only a first step. CasJobs alone cannot server this function.

CasJobs also permits data to be shared by group collaborators. This is useful for for teams working on proprietary data that require a chain of queries to the mission database.

2. Running CasJobs

Register/login first. This is easy and intuitive. Notice that registration enables you to get into MAST's GALEX implementation of CasJobs too. Therefore, it you've already worked with GALEX data using CasJobs, you shouldn't register again. After registering, it is necessary for you to click on the "MyDB" tab at the top of the page. This will create your own CasJobs-stored database, which you will probably be using. After a period of several minutes' inactivity you will be logged out, so you will have to log back in and to navigate back to the page you had worked on earlier. (Any unsaved or unsubmitted work that you have done will not be saved.)

Read this and the Help/Guide page for orientation.

We encourage you to consult our sample queries after logging in by clicking on "Tools" (top banner), which takes you to the main SQL query box page Next, mouse over "Samples," read the descriptions, and select the query you want to work on. If none of these suits your purposes, feel free to contact us and perhaps the next sample will be yours.

Send any questions, comments, or help requests to archive@stsci.edu.

3. Query syntax:

Query syntax is in SQL. Knowing SQL helps, but if you don't know SQL, you can Google "SQL tutorials," or come to MAST for recommendations on beginners text or specific queries. . This implementation of CasJobs is designed for you to "fake it." Our strategy to initiate you into its use is to provide "use case" samples. If you have new cases to provide us with, contact us at archive@stsci.edu, and we'll add them, or show you how to customize a posted example.

4. Browser incompatibilities

CasJobs is a web-based tool, and all its elements work for Internet Explorer and Firefox. There have been some issues with previous versions of CasJobs for Safari, Mozilla, and Opera. At this writing it is not clear that their use still causes problems.

5. News items

[add date of opening of the Kepler CasJobs site.]

6. Needed columns and sample queries:

You will need to consult this list of Kepler table columns for target searches, data retrievals, and GO investigator identification tables (TBD: e.g. from http://archive.stsci.edu/search_fields.php?mission=list).

The following is an list of descriptions of the samples. You will find the same list of sample queries under the Sample tab. Written in SQL in an open query box. This format allows you to customize the query to your needs. (Hint: we suggest that your initial run be made with the quick button so that it will show right away that your query can be successfully run. For example, you can start the query with a "top 100" phrase, meaning that only the first 100 entries will be reported back.) Commented lines are provided to show what the query does or to provide other options.

ASCII list of sample use cases goes here.