EUVE Search Help

The search pages basically contain 3 parts. The top of the page lists the input search fields. Entering values (as described below) for one or more of these fields will define the selection criteria for the database search. The middle of the form contains buttons to initiate various actions including:

perform the search using the specified search criteria and output format,
clear the search form and reset values to the original defaults,
reset entries to the set of (default) values used the previous time the search page was drawn, and
display this help page.

The bottom portion of the page deals with formatting the table of found entries that appears after the search is completed. The format options include specifying which columns appear in the output list, the order of the entries, the maximum number of returned entries, the epoch of the output coordinates, and the option to display the actual SQL command used to retrieve the database entries. First time users may want to run the search using the default output options.

After selecting search criteria, output options, and clicking the search button, a second page will appear listing the returned database entries. From this table, one may click on the data file entries to download the selected FITS file.

Note Currently all the data requested through this interface will be retrieved from HEASARC at Goddard Space Flight Center.

Local File Name

The name of a local file containing a table or list of parameters such as coordinates, targets names, or data IDs to be uploaded to the server and used to query the database. The file must be a plain ASCII text file (e.g., not DOC or RTF files) with either one entry per line (e.g., a target name, a Data ID, or a set of coordinates), or a table separated with one of the allowed delimiters, with targets, Data IDs, or RA and Dec values in the designated columns. Note in either case, only one entry per line is extracted. If, for example, a comma-separated list of target names is downloaded in one line, only the value in the designated column will be used.

For security reasons, there are many restrictions on file uploads. If you have trouble please contact the help desk.

The search script will perform a separate cone search for each extracted target name or set of coordinates contained in the uploaded list, with a separate table of results for each. Target names will be resolved to coordinates. If a resolver error occurs with target names, the search will abort and the compiled results displayed. (Note unresolved target names are not considered an error.) Coordinates may be given using sexigesimal notation or decimal degrees. When Data IDs or Kepler IDs are specified, the results are displayed in a single table. If the output is requested in CSV or Excel spreadsheet format, a blank line will be used to distinguish the results of one cone search from another. VOTable format incorporates separate RESOURCE tags for each cone search.

Use the other form entries to specify field delimiters, RA, DEC, or Target column numbers (when the file contains a table of values), and file contents (target names or coordinates). The browse button allows users to seach local directories to locate files.

Warning: Since uploading long lists can take a while to run, uploaded files are limited to 10,000 entries.

File Contents

Specifies the contents of the local file to be uploaded. The current choices are: coordinates, target names, and Data IDs (or for Kepler missions, Kepler IDs).

If "target name", or "coordinates" are specified, each entry is treated as a separate query. The results are displayed as each query is run. If however "Data IDs" or "Kepler IDs" is specified, (up to 10,000 are allowed), it is processed as a single query (e.g., select * where data_id in (ID1,ID2,...).

Recently, Simbad has started adding Kepler IDs to its list of resolvable target names. This means that for Kepler (and perhaps eventually K2), an uploaded list of IDs can be treated as either "Target Names", which generate a set of cone searches, or "Kepler IDs", which creates a single search result based on found IDs. The advantage to the latter search is that all the search results are listed in one table, and can be submitted for retrieval in one click.

To avoid displaying column names after each target name or coordinate query, consider using the comma-separated values output format. Also keep in mind that not all target names are resolvable. For example, SIMBAD currently does not reolve most 2MASS IDs.

RA/Target/Data ID Column Number

The column number containing either the Data ID, Right Ascension (decimal degrees or sexagesimal), or target name (depending on how file_contents is set). The default is to assume the first column is to be used.

Dec Column Number

For forms allowing coordinates as input, the column number containing the Declnation (decimal degrees or sexagesimal). The default is to assume the second column contains the DEC value. If the file contents is set to Target Name or any Data ID, this parameter is ignored.

Column Delimiter

The character used to delimit table entries in the uploaded file. Allowed values include tabs( ), commas(,), vertical bar (|), or semi-colons(;). The default is to assume tabs are the delimiters. If the file contains only a single column, use tabs as the delimiter.

Target Name

The name of the astronomical object you want to search for. Examples of valid names include gam Gem, NGC 1068, JUPITER, and hd 45677. For Kepler, a sky-region limited mission, examples might be 14 Cyg, HR 7483, HD 181649, or NGC 6819. Multiple target names can be entered if separated by commas, although table sorting is turned off in these cases.

Kepler input catalog numbers are also accepted in forms such as: kic1026032, kplr1026032, kepler1026032, or kplr001026032. Kepler planet names can also be resolved when entered in a form such as kepler-7, kepler-32b, etc.

K2 IDs from either EPIC or the Custom Aperture File (CAF) starting with (case-insensitive) epic, k2, or ktwo can also be resolved. Some, but not all, K2-discovered exoplanet names can be resolved to the host stars coordinates (e.g., K2-16, K2-97 b).

The Target Name is used in combination with the Resolver Field. If set to "Resolve" (the default), a cone search is initiated using the resolved coordinates for the input target name and the specified search radius.

For most mission searches, you also have a "don't resolve" option. Choose "Don't resolve" to perform string searches on the entered object name rather than it's coordinates. (Note Kepler and K2 catalogs do not include a generic object name field, so this option is not available for Kepler users.)

When you search on the object name in the database (i.e. without using the name resolver), case will be ignored. The object name will not be wildcarded at the front and back automatically (that's so if you innocently enter IO, you don't match things like ORION). You can however wildcard the object name using * (for example, *IO*). You can also enter a comma-separated list; for example, *JUP*,*SAT* would match object names containing either JUP or SAT.

Note that most missions store some target names in a format that is not compatible with the NED or SIMBAD name resolvers. For example, most 2MASS IDs are currently not resolveable by SIMBAD.

Resolver

This field describes how target names are to be handled. If you want to resolve a target name into its coordinates, use the default value "Resolve". For most missions, you can also elect to search the database by the target name itself by choossing the "Don't Resolve" option.

The two main name resolver services are SIMBAD and NED. NED is the NASA Extragalactic Database at Caltech in Pasadena, California, and SIMBAD is the Set of Identifications, Measurements, and Bibliography for Astronomical Data at the Centre de Données astronomiques in Strasbourg, France (SIMBAD at CDS). A mirror site at the Center for Astrophysics in Boston is also now available. NED is an extragalactic database, and generally won't resolve object names within the Milky Way galaxy.

Because we occasionally have problems with network connections and web servers, we now store previously resolved target names and coordinates in a local database and search this database before trying to access NED or SIMBAD.

If any error occurs, the search form will be redrawn with an error message at the top. Otherwise, the returned coordinates will be used to search the database, along with whatever other query qualifications were specified.

We recommend that you use object name resolution to find observations of specific stationary targets. This is the most reliable way to look up observations, because the observer could have given any object name at all (for example, NGC1976 instead of M42, or PARALLEL-FIELD).

The name resolvers can resolve only fixed objects; they cannot compute the positions of moving objects (planets, comets, etc.). To find moving objects, try selecting the appropriate category option available on most MAST search forms, or as mentioned above, enter an object name that could match what you're looking for, and select "Don't Resolve" for the name resolver. Note wild cards are allowed, so for Jupiter you might enter "*JUP*".

Right Ascension, Declination

The Right Ascension and Declination values. If single values are entered, a cone search is performed using the specified search radius (default = 3 arcminutes for most missions, 0.02 arcmin. for Kepler). Values may be entered in decimal degrees or using sexagesimal notation. Although decimal hours is NOT an allowed input format, Right Ascension search results may optionally be displayed as decimal hours (see the "Output Coords" form element).

Note the examples listed below (and elsewhere) are only intended to show the format of the form entries. There is no guarantee that entering these specific values will return any search results.

You may also enter ranges of right ascension or declination, using the ".." operator. For example, you can enter 21h 51m .. 21h 52m for the right ascension, and 28 51 .. 29 51 for the declination. Comparators can also be used, i.e. ">", ">=", "<", "<=". For example, "> 85" as a declination value will return all observations with declination larger than 85 degrees. (Note when ranges of coordinates are specified the search radius will be ignored. Also, searches on ranges can be quite time consuming.)

Coordinate values may be specified using a number of formats. Examples of valid formats include:

    Decimal Degrees
       	185.63325 29.8959861111111
 
    Hours, minutes and Seconds
        12 22 31.98      29 53 45.55
        12h22m31.98s     29d53m45.55s
        12:22:31.98     +29:53:45.55
        12h22'31.98"     29d53'45.55"
        12h 22m 31.98s   29d 53m 45.55s
        12h 22' 31.98"   29d 53' 45.55"
        12h 22' 31.98"  -29d 53' 45.55"
        12h22'31".98    -29d53'45".55
        12h22m31s.98    -29o53m45s.55
        12h 22' 31".98  -29d 53' 45".55
     
    Hours/Degrees and Minutes (no seconds)
        12 22     29 53
        12h22m   +29d53m
        12h22m    29d53m
        12:22m    29:53m
        12h22'    29d53'
        12h 22m   29d 53m
        12h 22'   29d 53'
        12h 22'  -29d 53'

    The RA may be given in decimal degrees by indicating
    a D or d after the degrees:
        12d 22m   29d 53m

Spacing is not important, as long as the value is unambiguous. You can delimit the hours/degrees, minutes, and (optional) seconds with letters, colons, spaces, or any character that's not a digit or a decimal point. Like target names, multiple coordinates can be entered if separated by commas.

Radius

The radius of the search box around the RA and Dec, in floating-point arcminutes (e.g., 5.0). You should be careful about giving too restrictive a search radius since (for some missions) the coordinates of the object were given by the Guest Observer, and may not reflect the precise pointing of the instrument at the time of the observation.

The search routine computes the angular separation between each result dataset and the search center so this really is a circular radius. (Results are generally sorted on the angular separation by default.)

Equinox

The equinox of the RA and Dec you have entered, either B1900, B1950 or J2000. If B1900 or B1950 are selected, the input coordinates are precessed to year 2000, but NOT converted to FK5 or ICRS. This will add an error which (from year 1900) can range from a few arcseconds up to roughly 25" at the poles.

Note the precession is only applied to the input coordinates. The coordinates displayed in the search results will depend on the mission database and the selected output columns. (Note: all MAST missions include J2000 coordinates as default output columns.)

If you enter a target name and use either the SIMBAD or NED name resolver, the equinox will be set to J2000.

Object Category

This is a broad category for the target. Values include:

wd - white dwarfs
late - late-type stars
early - early-type stars
cv - cataclysmic variables
ex - extragalactic objects
ss - solar system objects
pulsar - pulsars
pn - planetary nebulae
noid - unidentified
lmxb - low-mass X-ray binaries
snr - supernova remnants
grb - gamma-ray bursters
other - none of the above

Observation Start Time

The date of the observation. More specifically, the date and time, in GMT, on which the exposure was started.

When specifying this date, you need to include a date and an optional time. If time is omitted then then midnight (00:00:00) is assumed. This means that a specification like "July 1 1994" will look for observations done on July 1 1994 00:00:00, not for observations done for the entire day July 1 1994. To search for observations for an entire day use the range option described below.

Note also that when entering a date with the month in numerical format, the American ordering is used; i.e., the first number is the month.

The date can have any of the following formats (the month name can be spelled out or abbreviated to three letters; case is not significant):

      Jul 15 1994
      Jul 1994 15
      15 Jul 1994
      1994 Jul 15
      1994 15 Jul
      7/15/1994  <--- Note order of month/day of month/year for numeric formats
      7-15-1994
      7.15.1994

If the day is omitted, the first day of the month is assumed. This means that a specification like "July 1994" will look for observations done on July 1 1994 00:00:00, not for observations done during July 1994. Note also that when entering a date with the month in numerical format, the American ordering is used; i.e., the first number is the month.

If a time is omitted, then midnight (00:00:00) is assumed. Otherwise, you can specify a time in any of these formats:

      14:30
      14:30:20
      14:30:20:999
      14:30:20.9
      4am
      4 PM
      04:30:20 AM

To search for observations before a given date, use <, and for observations after a given date, use >. For example,

      > Jul 15 1994
      < Jul 15 1994

You can use the .. operator to search on a range of dates:

     Jul 1 1994 .. Aug 1 1995

This operator is inclusive on the first date and exclusive on the second.

Finally, you can search on a list of dates or date ranges. For example,

     Jul 1 1994 .. Jul 3 1994,
     Dec 1 1995 .. Dec 6 1995

will search for observations done within either one of these date ranges.

Exposure Length

This is the median exposure for a given observation. There are four EUVE detectors which normally collect data simultaneously during an observation. Each detector will have a different exposure time. In this field, we have listed the median of the exposures of the individual detectors, in units of kiloseconds and rounded off to the nearest kilosecond. Note that sometimes one detector can be way off from the others and skew this number, or an observation can be very short producing an exposure time of zero. For the true exposure times you need to look in the headers of the images.fit extensions. The units can optionally be specified in seconds, although kiloseconds is the default used by the project.

Day/Night

Entries will contain either the word "night" or "day" indicating which part of the observation is being cataloged. Some observations will have both parts, others will only have a night part. Sometimes the night and day parts appear on different volumes. By default, both day and night observations will be returned. To not retrieve one or the other, click on the entry not desired.

Data ID

The unique identifier for an EUVE observation. EUVE data ids contain the target name, observation date and a character indicating if the target was taken in the night (N) or day (D) part of the orbit. Examples of data ids are: am_her__9808040924N and comet_hale-bopp__9411201903N.

Observer

The name of the PI of the proposal which has been associated with this observation in the CEA database. This is not always a very meaningful field, because many times multiple proposals (and PIs) were given simultaneous data rights to the target in the same observing cycle. In that case, only one of the PIs is listed here. The observer is listed as "EUVE" for targets which were scheduled as calibration targets. However, for most calibration targets, there was also a PI to whom the data was proprietary; unfortunately, our archive does not contain these PI names for calibration targets.

Old Filename

Old EUVE Archive ID number (gonum): this is the old ID number the target was assigned in the now obsolete EUVE spectral browser and archive. Notice that there is not a one-to-one correspondence between the old archive and the new one, so some targets have more than one ID number associated with them and other IDs are used by multiple targets. The old ID might be of use for historical purposes or for users who know the old ID of a target they want. EUVE has stopped assigning ID numbers to publically released targets as of the Feb. 1, 1998 release.

Note wildcards can be used in the filename specification.

Public Date

This is the date on which an observation becomes public. If this field is blank, the target is already public. If there is a date present, the target is still proprietary to its Guest Observer and should not be made public until the indicated date. EUVE releases data on monthly intervals. Targets observed in Cycles 1-4 of the EUVE Guest Observer program have one year proprietary periods. In Cycle 5 (which began in 1997) and later, the period is six months. The period begins when the data is delivered, not when it was observed, and we sometimes make exceptions if there was a problem with the data delivery, etc., so the public dates cannot be inferred from the data itself. Also, some EUVE observations are done in parts over an extended period of time; the proprietary period is determined from the delivery date of the last part.

User Specified Field n

You may use these form elements to search on any column(s) in the mission table. First, select the field you wish to search from the pulldown menu under the "User-specified field n" heading. Then, type in the qualification in the corresponding "Field Descriptions" box. Clicking on the "Field Descriptions" link, will display information on the allowed fields including the allowed range of values.

As an example, a Kepler user might select "E(B-V)" from the pulldown menu and enter "< 0.5" in the "Field Descriptions" box.

NOTE only fields which are not already included on the search form should be selected. Specifying search criteria for a field that is listed in BOTH the form and in the User Specified field, may cause either the query to fail or return unexpected results.

Output Columns

This form element allows you to determine which columns are displayed and in what order. The initial list contains those designated as defaults, but it may be possible to add more. (Its possible a project decided all columns should be displayed by default.)

To remove a column, highlight the column to be removed then click the "remove" button to the right of the output columns list. To remove all columns, click the "remove all" button. This is useful when only a few output columns are desired. If a search is submitted with all columns removed, it will display the original set of default columns.

To add a column, select the desired column from the pull down menu beneath the list of chosen output columns, then click the "add" button. The column will be added to the bottom of the output column list. To add all the available columns, click the "add all" button.

You can change the order of columns by highlighting a column and then clicking the up or down buttons to the right of the list of chosen output columns. Each click moves the column by one position. Note the "Mark" column, which allows data sets to be retrieved, will always appear at the top of the list. If desired though it can be removed.

The output columns form element has its own "reset" button to restore the list of output columns to the original defaults. This is different than the "Reset" button at the top of the form which is used to reset the other form elements. Clicking the "clear form" button will restore the original defaults in all sections of the form.

One warning, the amount of memory required and possibly the execution time for a search is proportional to the amount of information returned. For large requests, users may want to reduce the number of output columns to the minimum required. Also consider non-html output formats and the "Skip formatting" option.

Suppress Null Result Message

By default, when using "file upload mode", the message "No Records Found Matching Query" (or for non-html output, "no rows found") is displayed for each entry with no search results. Also, for non-html output, a line is now added for each entry in the uploaded file stating the entry number and target name or coordinates used for that particular database query. Clicking this button will prevent either of these messages from appearing in the output which may be useful for reducing output from large search results and/or for parsing the CSV-style output.

Add Entry Number

If checked when using "file upload mode" to search on coordinates or targets and when specifying a csv-like output format, a number will be prepended to each row of search results indicating the position of the input target in the uploaded list of targets. For example, if 10 entries were found for the 5th target listed in the uploaded file, each of those 10 rows would have a 5 in the first column. This can be useful for correlating search results to input targets when multiple targets are searched. Note Data ID search results which all appear in one output table will NOT have entry numbers since they are all returned in one database query.

Verb

Verb is an integer parameter used by the VO community for specifying the amount of output returned for a given search request. It is only available when retrieving data as a web service but works with every MAST service. Setting verb=3 in a search request is equivalent to specifying "add all" from a search form; it will return all the available columns in the output not just the standard default fields. Currently setting verb to any other value has no effect.

Sort output by:

Choose how you want the output rows sorted. You can select up to three fields to sort on. The rows will be sorted in the order of the first sort field; if two rows have the same sort field, they will be sorted in order of the second sort field, and so on. Default sort fields may be listed, but any field from the pulldown list can be used. Specifying multiple sort fields may increase execution time. If you prefer no sorting, you can specify "null" for all 3 fields. This may speed up the query, but results will be displayed in the order in which they were originally stored in the database table.

For each field, you can select that the rows be sorted in reverse order on that field by selecting the reverse checkbox. For example, you can sort the rows with the most recent observations first by selecting Observation Date for the first sort field and selecting the reverse checkbox next to it.

One word of caution: the selected sort field can change the search results when the query finds more rows than are displayed ( i.e, when the number of found rows exceeds the value of "maximum records"). For example, for a search on a particular coordinate that finds 5,000 entries, if the search is sorted on exposure time and 1,001 rows are to be displayed (the default), then the 1,001 shortest exposures from the 5,000 found entries will be displayed which may not include the entries closest to the desired position. (It is a good idea to always sort on "ang_sep" for target or coordinate searches).

Finally, note that when displaying the search results in HTML, further sorting is possible based on any of the displayed columns simply by clicking the column header. Even columns using sexigesimal notation can now be correctly sorted. Clicking a header a 2nd time will reverse the order. Reloading the page will return results to the original order. (This sorting is performed using javascript, so javascript needs to be enabled.)

Display Coordinates

Specifies the format for displaying the primary equatorial (i.e., RA and Dec) coordinates. The options include:

Sexagesimal - The default format with Right Ascension specified as hh mm ss.sss and Declination as +/-dd mm ss.ss ( e.g., RA = 12 46 11.091, Dec = -00 30 12.08). Note an extra digit was added as of June, 2012.
Degrees - Decimal degrees for both RA and Dec with 7 significant figures to the right of the decimal point (e.g., RA=191.5461912, Dec=-0.5033333). Note 2 extra digits were added as of June, 2012. or
Hours - Decimal hours for RA and decimal degrees for Dec in same format as for decimal degrees (e.g., RA=12.7697512, Dec=-0.5033333). Note decimal hours = decimal degrees/15.0. (Note 2 extra digits were added as of June, 2012.)

Any other coordinate fields contained in the searched mission catalog will be displayed in their original format.

Maximum Records

This value specifies the maximum number of rows returned in a single query. For the standard mission search forms, the current default is 5,001, but values from 1 to 50,001 are allowed. For the file upload forms in which multiple targets, data ID's, or coordinates can be specified, the default is set to 20 rows per file entry, with allowed values ranging from 1 to 5,000.

Note when displayed as HTML, the latest search scripts will display 500 records per page. Links to the additional pages are shown on the results page. This paging feature however does require javascript to be turned on.

Users should be cautioned about retrieving a large number of records (i.e., > 10,000 - 15,000) in HTML format. This can cause memory problems for the browser (particulrly Safari) and prevent javascript commands from functioning. It may also cause the browser to freeze and require restarting. Using the output format options which download results in a file can reduce the problem.

Another option for large requests is to use "Casjobs". Casjobs requires requesting a user name and password, and submitting queries in SQL, but it allows users to submit large search results and save them online. For Kepler, the link ito Casjobs is http://mastweb.stsci.edu/kplrcasjobs/. For other missions, check the Search_Retrieve page in the left gutter.

When queries are submitted as a web service, the default number of rows returned is 2,000, but any value is allowed when max_records is specified as a query parameter. A practical limit might be 25,000. (See the MAST Web services page for more information.)

Records per page

This parameter controls the number of records displayed per web page. By default, 500 rows or records are displayed per HTML page. Therefore if 2000 records are returned, links to 4 pages will be displayed at the top and bottom of the results table. The paging feature however uses javascript, so if javascript is turned off, paging won't work and only the rows shown on the first page can be displayed. This is one reason why increasing the default value may be helpful. Note this value is ignored when output formats other than HTML are selected.

Make Rows Distinct

Selecting this checkbox will restrict the display to only rows in which every output column value for a given row is unique. This option is primarily useful when only a small number of columns are displayed (i.e., using the "remove" button to remove default output columns) and when the selected columns have duplicate values. Including columns which already have unique values (e.g. Kepler ID or Data ID) will make the "Distinct" option ineffective.

As an example, a IUE or FUSE user might want to create a list of unique target names for a specific object class/category. He or she would specify the desired object class, select only "object Class" and "target name" for the output columns, click the "Make Rows Distinct" button, then click "Search".

Note that for some missions, columns such as RA, Dec and Magnitude were frequently defined by the observer and often have different values for the same target. If columns such as these are chosen as output columns, there will often be more than one row listed per object name.

Remove Null Columns

After the search results are retrieved from the database, selecting this option will remove columns with all null values. Zeroes are maintained. In some cases selecting this option can reduce the execution times, but it can also take longer depending on the number of null columns and the number of columns selected.

Removing null columns is primarily useful for sparsely-populated tables when a large number of columns are requested. Note for the HSC summary form this option is selected by default.

Skip Formatting

After the results are retrieved from the database, some reformatting is done. This includes converting decimal degrees to sexagesimal format, restricting the number of significant numbers displayed for certain data types, changing date formats, etc. Since this processing may be applied to every row and column, and as catalogs keep getting larger, this step can significantly slow down large requests (e.g., queries returning more than a few thousand rows). Checking this box will skip these steps and thereby reduce execution times.

Output Format

You may choose any of the following formats for displaying/storing search results. If you are using a browser (e.g., Firefox, etc) to submit a query from a MAST web form, the formats labelled "File: ..." offer a way to download results directly to your local computer. The names shown below are the actual values specified in a GET request or as an API request. The description in parentheses is how the option will appear on the MAST classic search forms.

HTML_Table (HTML_Table) default - results returned as a standard HTML table including various links for retrieving data, displaying previews, literature references, plotting spectra, etc.
Excel_Spreadsheet (Excel_Spreadsheet) - results are downloaded as an Excel spreadsheet file. (Note: assumes users computer/browser provides support for Excel-format files). The default file name when downloaded is "mission"_search.xls where "mission" is the mission name (e.g., fuse_search.xls).
VOTable (VOTable) - an XML format adopted by the Virtual Observatory (VO) project and displayed in the user's browser. Note coordinates in VOTable format are always in decimal degrees rather than sexagesimal format. For searches returning results from more than one mission and/or target, multiple "resource" tags are created. Searches with a radius of 0 will return a VOTable file listing the output fields for that particular mission/catalog. (For more information on the XML file format, see VOTable documentation.)
CSV (Comma-separated values) - a simple ASCII array containing column headings followed by rows of comma-separated values. In file upload mode, a blank line is inserted between the search results to separate multiple target queries.
SSV (Space-separated values) - a simple ASCII array containing column headings followed by rows of space-separated values. In file upload mode, a blank line is inserted between the search results to separate multiple target queries. Note users may want to select coordinates in decimal rather than sexagesimal format to maintain the correspondence between column headings and entries although some column headings may contain blanks as well. (Semi-colons, pipes, or commas are probably safer delimiters.)
IRAF (IRAF Space-separated w/INDEFs) - Like the space-separated format above except empty fields are replaced with the string "INDEF". This format is useful for IRAF-compatibility.
COSV (Semicolon separated values) - a simple ASCII array containing column headings followed by rows of semi-colon separated values. In file upload mode, a blank line is inserted between the search results to separate multiple target queries.
TSV (Tab-separated values) - a simple ASCII array containing tabs for delimiters. May be useful for ingesting into Excel spreadsheets.
PSV (Pipe-separated values) - a simple ASCII array containing column headings followed by rows of pipe or vertical bar separated values. (Note: not offered in file upload mode.)
JSON (Json format) - Javascript Object Notation (json) is a simple machine and human-readable, name/value ASCII format supported by many programming languages. (Note: not offered in file upload mode.)
CSV_file (File: comma-separated values) - a simple ASCII text file containing column headings followed by rows of comma-separated values. In file upload mode, a blank line is inserted between the search results to separate multiple target queries. Rather than being displayed in the browser, the results are directly downloaded to the users computer using the file name "mission"_search.txt where "mission" is the mission name (e.g., hst_search.txt). Depending on the browser settings, the user may be prompted for a file location before the file is downloaded.
SSV_file (File: Space-separated values) - a simple ASCII text file containing column headings followed by rows of space-separated values. In file upload mode, a blank line is inserted between the search results to separate multiple target queries. Rather than being displayed in the browser, the results are directly downloaded to the users computer using the file name "mission"_search.txt where "mission" is the mission name (e.g., hst_search.txt). Depending on the browser settings, the user may be prompted for a file location before the file is downloaded.
IRAF_file (File: IRAF Space-separated w/INDEFs) - Like the space-separated format above except empty fields are replaced with the string "INDEF". This file format is useful for IRAF-compatibility.
SSV_file (File: Semicolon-separated values) - a simple ASCII text file containing column headings followed by rows of semicolon-separated values. In file upload mode, a blank line is inserted between the search results to separate multiple target queries. Rather than being displayed in the browser, the results are directly downloaded to the users computer using the file name "mission"_search.txt where "mission" is the mission name (e.g., hst_search.txt). Depending on the browser settings, the user may be prompted for a file location before the file is downloaded.
TSV_file (File: Tab-separated values) - a simple ASCII file containing tabs for delimiters. May be useful for ingesting into Excel spreadsheets.
PSV_file (File: Pipe-separated values) - a simple ASCII text file containing column headings followed by rows of pipe-separated values. (Note: not offered in file upload mode.) Rather than being displayed in the browser, the results are directly downloaded to the users computer using the file name "mission"_search.txt where "mission" is the mission name (e.g., hst_search.txt). Depending on the browser settings, the user may be prompted for a file location before the file is downloaded.
JSON_file (File: Json format) - Javascript Object Notation (json) is a simple machine and human-readable, name/value ASCII format supported by many programming languages. Rather than being displayed in the browser, the results are directly downloaded to the users computer using the file name "mission"_search.txt where "mission" is the mission name (e.g., hst_search.txt). Depending on the browser settings, the user may be prompted for a file location before the file is downloaded.
WGET_file (File: WGET Commands) - This option is only available for certain missions. If selected, a shell script file is output which the user can execute from his own computer to download all the selected files with one command. The shell script file uses the "WGET" program which is available for most operating systems. Note for Kepler, two WGET options are available: "File: WGET LC commands" will create a script for downloading available light curves, "File: WGET TPF commands" (also available for K2) will create a script for downloading target pixel files. For Swift, the WGET option will create a script for downloading the Sky coordinate images.
CURL_file (File: CURL Commands) - Like the WGET command, this option is only available for certain missions. If selected, a shell script file is output which the user can execute from his own computer to download all the selected files with one command. The shell script file uses the "CURL" program which is available for most operating systems. Note for Kepler, two CURL options are available: "File: CURL LC commands" will create a script for downloading available light curves, "File: CURL TPF commands" (also available for K2) will create a script for downloading target pixel files. For Swift, the CURL option will create a script for downloading the Sky coordinate images.

Note: If no entries are found for an entry a "no entries found" message is written in the selected format and the program continues. In all cases, error conditions will cause the database search to abort.