Help Page for Advanced Data Products Query Form

Specify the name of the astronomical object you want to search for and select the appropriate name resolver from the pull-down menu. Target identifiers will be resolved into coordinates by SIMBAD (default), or NED.
NED is an extragalactic database, hence galactic targets should be resolved by SIMBAD.

If you would like to match the target name against the value stored in the ESO database (that is, without using any SIMBAD/NED name resolver), choose the option 'Do not resolve' from the pull-down menu. Your input will be wildcarded and the search will be case insensitive: car might return eta car, Cartwheel,... To change this default behaviour, use the following operators:

• =car* will match carina,... but not eta car nor Carina.
• ~car* will match carina, Carina, Cartwheel,... but not eta car.
• ==carina will match exactly.

Solar System bodies cannot be resolved. Thus, if you would like to search for moving targets, enter a target name (e.g. neptune) and do not select any name resolver but instead choose the option 'Do not resolve' from the pull-down menu.

Suppose you have a list of targets and you would like to query the ESO Archive for each target in that list. Instead of having to re-type the target name or coordinates and run a new search for each target in the list, you may query the ESO Archive using an input file of targets. Click on the 'Browse' button to locate and upload the file from your local directories. The file must contain no more than one target per line. The target can be

• either a Name
• or a set of RA and DEC coordinates being Tab-separated

A few notes regarding the syntax of the input file:

• Lines starting with a single hash '#' are not recognized as targets, but they will be displayed on the query result screen as comments.
• Comments may contain HTML tags.
• You may add your own input notes or comments as an additional column in the query results. Simply add a hash '#' after the target, followed by your input comments. Here are some examples:
  
  • HD 93308 # Variable Star
  • 10 45 03.591 \tab -59 41 04.26 # eta car
  The strings Variable Star and eta car will then get added to the query results in the first column, named Note. It is useful for further processing of the query results, especially with formatted results like TSV or VOTable.
• Blank lines are ignored, as well as lines starting with a double hash '##'.

In addition, choose the appropriate name resolver from the pull-down menu. A database search will be performed for each target in the uploaded list. If one of the target names cannot be resolved, it is skipped and the search proceeds with the next target in the list.
Do not forget to set the size of the Search Box.

If you search by coordinates or target name to be resolved by SIMBAD/NED, enter here the size of the search box around the target.
Alternatively, if you search by range in RA and DEC (see below), the Search Box field must be empty.

Alternatively to the target name, you can specify here the Right Ascension. Recognised format is either sexagesimal or decimal.
For sexagesimal notation, both blanks and colons are accepted as separators between hours/degrees, minutes and seconds.
Use the pull-down menu to indicate wether input values for RA are given in hours or degrees. You may also search by range in RA (e.g. 15:00 .. 15:30). If so, be sure to empty the Search Box field.

Alternatively to the target name, you can specify here the Declination. Recognised format is either sexagesimal or decimal degrees.
For sexagesimal notation, both blanks and colons are accepted as separators between degrees, arcminutes and arcseconds.
You may also search by range in DEC (e.g. -51 00 .. -50 00). If so, be sure to empty the Search Box field.

Specify here the constraint on the redshift value. It will be matched against both the value specified by the PI and the value derived from the cross-identification of spectral advanced data products targets with astronomical objects in the SIMBAD and NED databases.

The value of the redshift, as specified by the PI.

At present our database holds redshift quality flags for the following datasets: GOODS/FORS2, GOODS/VIMOS and zCOSMOS. Please refer to the corresponding data release pages to get a full description of the meaning of the quality flag values.

Specify here the constraint on the radial velocity value. Your input will be matched against the value derived from the cross-identification of spectral advanced data products targets with astronomical objects in the SIMBAD and NED databases.

The cross-identification of spectral advanced data products targets with astronomical objects in the SIMBAD and NED databases enables the ESO Science Archive user to search by additional target properties, namely object name, object class, redshift, and radial velocity, which do not come from the information submitted by the PI of the programme but which were retrieved from the respective databases a posteriori.

Even though the procedure for cross-identification has been designed for maximum reliability and results were checked carefully there is a small chance for mis-identifications. We encourage the user to report back such cases to archive@eso.org.

Primary_Name is the first identifier suggested by SIMBAD/NED, and Primary_Class is the object type associated with the Primary_Name. For a list of possible class designators, please refer to SIMBAD standard designations and NED codes.

The extension of the search by target name and target class against all identifiers/classes suggested by SIMBAD/NED for a given object and not just the primary ones is planned for a future release.

At present our database holds cross-identifications for 74% of the QC UVES spectra (to be routinely expanded). The same feature will soon be implemented for HARPS targets as well.

At present our database holds SNRs for UVES QC spectra. Those SNRs are extracted from the QC reports.

Enter here words from the project title. For more information about releases of advanced data products, please have a look at the summary table. Note that data from the Monitor project cannot be retrieved through this unified interface yet; please use instead the specific data retrieval interface available from the Monitor data release page. For UVES and HARPS reprocessed data, the project title corresponds to the proposal/programme title. You may specify multiple words with the help of the OR or AND operators.

Enter here the name of the Principal Investigator.
You may specify multiple names with the help of the OR operator, e.g. Smith OR Dupont.

Read the documentation on the ESO programme identification code.

Modified Julian Date

The Modified Julian Date converted to DD MMM YYYY hh:mm:ss.

Enter the date of the first night in DD MM YYYY format and select a time [UT] from the pull-down menu. If you do not specify any end date, the search engine will look for all datasets having a Modified Julian Date greater than or equal to your input.

Enter the date of the last night in DD MM YYYY format and select a time [UT] from the pull-down menu. If you do not specify any start date, the search engine will look for all datasets having a Modified Julian Date less than your input.

For more information on ESO instrumentation, please check http://www.eso.org/instruments/

This is the technique used for the observation.

Filter name (for images) or dispersion element (for spectra).

The width of the slit in arcseconds.

The rotation angle of the slit in degrees. N=0 and E=90.

Exposure time in seconds.

Input form:
Specify a reference wavelength in nanometers to constrain your search to those spectra that do contain this particular wavelength in their wavelength range.

Query results page:
The wavelength range (lower and upper limits: Min_Wavel_[nm] and Max_Wavel_[nm]) of each spectrum is given in the query results page, provided you marked the Ref. Wavel. checkbox on the search screen. In addition, the central wavelength (Central_Wavel_[nm]) is also provided.

The VOTable format is a Virtual Observatory XML standard for tabular data. More about the VOTable description is available at http://www.ivoa.net/Documents/latest/VOT.html.
The VOTable format allows you to easily load into any VO-enabled application the results of your search among ESO's collection of advanced data products.
You can also easily convert the VOTable results of your query into any kind of file format (e.g. ascii, CSV) using e.g. the tcopy command-line tool of the STIL Tool Set (STILTS).