![[ST-ECF]](/images/stecfwhite.gif)
HST Classic Search Form Help
| Archive Facility HOME | ESO HOME | ST-ECF HOME | INFO | FAQ |
|
|
HST Classic Search Form Help
|
Archive |
Archives to be queried. Description This interface allows queries to:
| ||||
Availability |
Description HST datasets are usually classified proprietary for about one year after observation and are not available for download. By unticking the checkbox, it is possible to see which data will become available in the future. The search will then also display datasets that can not be processed for technical reasons. | ||||
Target (SIMBAD name) |
The name of the target. This name will be resolved by an external service. Description The target name is sent to an external service, the SIMBAD name resolver at simbad.u-strasbg.fr/simbad, and its RA and Dec coordinates are retrieved. The search is executed in a box around this coordinate using the size of the box specified in the search box field. Unit dimensionless Examples M42 | ||||
Target description |
The description of the target as given in the HST database. Description The Target description in the HST database has been given the PI of the observation. Again, this can help in finding moving e.g. objects like planets or object types (e.g. AGN). Note however, that this classification is only a hint and is not complete. Wildcards are accepted in the search field. Unit dimensionless Examples Galaxy Seyfert ISM AGB star Emission Line | ||||
Search box |
Search box around point coordinates given via a target name or one of the coordinate fields. Description If a precise point is given, either by entering a target name or a coordinate a box search is executed around that point. If a range of coordinates (via .., < or >) is specified, the search box field is ignored. In Dec/Lat direction, the size of the search box is adapted to be approximately square at all declinations and latitudes. A special treatment is applied to the poles. Unit degrees minutes seconds [dd mm ss] Examples 00:10:00 | ||||
RA Dec |
Search position in Right Ascension and Declination. Description Position of the search. If a precise point is given, then a boxsearch with the size given in the Search Box field is executed. It is however also possible to exactly specify ranges or regions with the .., the < or the > operators. Unit either degrees or hours [deg or hours]. Values without colon are interpreted as decimal degrees. Examples 00:42:44.324 +41:16:08.53 10.684683 41.269036 10..20 >40 | ||||
Galactic coordinates |
Search position in galactic coordinates (longitude and latitude). Description Position of the search. If a precise point is given, then a boxsearch with the size given in the Search Box field is executed. It is however also possible to exactly specify ranges or regions with the .., the < or the > operators. Unit degrees. Examples 209.022900788 -19.4794454628 0..360 >60 | ||||
Ecliptic coordinates |
Search position in ecliptic coordinates (longitude and latitude). Description Position of the search. If a precise point is given, then a boxsearch with the size given in the Search Box field is executed. It is however also possible to exactly specify ranges or regions with the .., the < or the > operators. Unit degrees. Examples 82.8875673848 -28.7278978021 0..360 >60 | ||||
Spatial resolution |
The physical spatial resolution. Description Although a pixel will have a certain scale on the sky (see Pixel Scale), the actual physical resolution, i.e. the capability to separate two close-by point sources, depends on several factors amongs which is the diameter of the telescope. Several Hubble cameras, and particularly WFPC2, provide undersampled images. Unit arcsec Examples <0.07 | ||||
Moving objects |
Selecting only moving objects (e.g. planets or comets). Description Planets or other Solar System bodies are moving fast over the sky so that the telescope has to slew in order to keep them centered on the image. This flag allows one to search only for observations in which the telescope was slewing. Unit unitless Examples None | ||||
Target (Solar body name) |
The name of the target as given in the list of the Solar System body tracker SkyBoT. WARNING: Per default only associations and singlets are shown. It happens, however, that by chance a solar body object is on a member frame. In order to see those uncheck the Members checkbox in the upper right corner of the interface! Description ST-ECF provides a service that crossmatches data from the SkyBoT service at vo.imcce.fr/webservices/skybot with the data in the HST archive. This allows to discover frames that contain solar body objects (sometimes without the observation having being planned). Unit dimensionless Examples 1222 T-1 Jupiter Io | ||||
Dataset name |
The HST dataset name. Note that if you are looking for a dataset that is perhaps part of an association, uncheck the "Members hidden" checkbox at the top first. Description Dataset names start with a letter designing the instrument (I:WFC3, L:COS, J:ACS, U:WFPC2, O:STIS, N:NICMOS, Y:FOS, Z:HRS, W:WFPC, X:FOC). HLA products start with HST, HNG or HAG. Unit unitless Examples U2IR0104T for HST classic HST_10921_01_WFPC2_F502N_WF for one HLA associations HST_10921_01_WFPC2* | ||||
Type |
Description Filter to exclude non-science data. DARK, BIAS or CALIBRATION frames (e.g. lamp observations) and similar are not shown when the box is checked. | ||||
Instrument |
Select one or more instruments. Description Hold CTRL or SHIFT to select multiple entries. The dataset names corresponding to the different instruments start with special letters: (I:WFC3, L:COS, J:ACS, U:WFPC2, O:STIS, N:NICMOS, Y:FOS, Z:HRS, W:WFPC, X:FOC). Unit unitless Examples | ||||
Detector |
Detector that was used. Description Unit unitless Examples UVIS NIC2 | ||||
Data type |
Select specific types of data. Description Unit unitless Examples | ||||
Number of members |
Number of datasets that were combined together. Description HLA but also classical products can be created out of several datasets. These combined products are called associations and the component datasets are called members. This field allows to specify the type of the dataset. Number of members is 0 for member datasets, 1 for datasets that are not used to create (HST) associations (i.e. singlets) and > 1 for associations. Unit unitless Examples >5 | ||||
PI name |
Name of the principal investigator of the observation. Description The name is formatted as lastname firstname middle-initial. Unit unitless Examples Fosb* Fosbury R* | ||||
Proposal ID |
The ID of the proposal that the observation was part of. Description Unit unitless Examples 5345 | ||||
Proposal title |
The title of the proposal that observation was part of. Description The title was given by the PI upon proposal submission. Unit unitless Examples *dust* cloud interaction* | ||||
Observation date |
The start date of the observation. Description Starting date and time of this particular observation. In case of associations, this is the starting date of the first exposure. Unit unitless Examples Format: YYYY-MM-DD >2008-06-01 means all observations observed after June 01 2008 2008-01-01 12:00:00..2009-01-01 means all observations done between 2008 and 2009 | ||||
Exposure time |
Time the shutter is open. Description Unit second Examples 1000..2000 >5000 | ||||
Release date |
The date on which the data became (or will become) public. Description Data taken with the HST has typically a 1 year proprietary period. This date indicates when the data became public. For proprietary data it shows when the data will become public. Format: YYYY-MM-DD Unit unitless Examples >2008-01-01 means all observations public after Jan 01 2008 2008-01-01 12:00:00..2009-01-01 means all observations that became public between 2008 and 2009 | ||||
Wavelength or band |
The wavelength coverage of the image or spectrum or alternatively the specification of a standard band. Description The query will return any image or spectrum whose wavelength coverage intersects with the value or range given in this field. For filter combinations, we compute the central wavelength and the bandwidth values from the values of the individual filters. Alternatively one or more bands can be chosen from this list: Halpha, U, B, V, R, I, J, Jbroad, H, K, L, M, HeI, HeI-C, FeII, FeII-C, Paschen-Alpha, Paschen-Alpha-C, Millimeter, Infrared, Optical, Ultraviolet. Unit nm Examples <600 400..900 U U or V or B | ||||
Bandwidth |
The bandwidth of the throughput curve for this filter or combination of filters. Description The wavelength throughput curve can be characterized by its central wavelength and its bandwidth. For filter combinations, we compute these values from the values of the individual filters. Unit nm Examples <500 400..900 | ||||
Optical element type |
Select the type of the optical element that should be in the optical path. Description Unit unitless Examples | ||||
Filter/Grism/Prism |
The name of the filter, grating or prism used for the observation. Description If the name of the optical element (or parts of it) are known directly, they can be queried for here. Unit unitless Examples F160W F1*W G* | ||||
Spectral resolution |
The physical spectral resolution. Description Although a pixel will correspond to a certain wavelength range, the actual physical resolution, i.e. the capability to separate two close-by lines, depends on several factors and is in general different of the wavelength scale. Note that for symmetry, also images get assigned a Spectral Resolution which is equivalent to the full-width half maximum of the throughput curve. Unit nm Examples <200 | ||||
Resolving power |
The resolving power of the observation. Description The resolving power is defined as deltaLambda/Lambda where lambda is a typical wavelength in the throughput (e.g. the Central Wavelength) and deltaLambda is the Spectral Resolution at this wavelength. Unit unitless Examples >10000 100..300 |