Phase 3 Questions & Answers

This page records specific questions of Phase 3 users and the corresponding answers given by the ESO/ASG support team assuming that the provided information appears to be helpful to a broader audience.

List of FAQs

Questions and Answers of General Interest

Compiled version of fitsverify from the Phase 3 web pages

Q: Is the compiled version of fitsverify available from the Phase 3 web pages running on Mac OS X?

A: the version of fitsverify is compiled for the Linux operating system. One may download the source code from:

and compile it on Mac OS X. We cannot assure though that everything would work, as it was not tested.

Java version and environment for validator_user.jar

Q: Which environment does validator.jar need to run? Which Java version?

A: the validator has been developed and tested under Scientific Linux 5.3 (based on Red Hat Enterprise 5). It requires Java version jdk1.6.0_18 or higher. The validator is expected to run under Linux; other platforms are not supported at the moment.

PROV keywords

Q: In the example header provided in the user documention the PROV refer to the archive file names, e.g. PROV1 = 'VCAM.2010-09-29T05:55:14.101.fits' while ours is PROV0001 = '[1]'. I understand that it makes more sense for you the first one, but can you confirm this point for me please? I.e. we have to change PROV0001 to PROV1 and also look up the name of the ARCFILE in our provenance file.

A: Regarding the PROV* keywords, it is correct that the ESO/EDP standard differs from the convention used at CASU. Specifically, the ESO/EDP data standard mandates that

  • the index i (i=1,..,N) of the indexed keyword PROVi is not zero-padded;
  • the values of PROVi are pointers to files rather than pointers to FITS extensions, i.e. no trailing extension number in square brackets;
  • the PROVi keywords reside in the primary HDU of FITS file.

Generally, the PROV pointers should point to files being archived at ESO. In the case of ESO public imaging surveys this can be either the original raw files using the ESO archive identifier like 'VCAM.2010-09-29T05:55:14.101.fits' or other product files being submitted to ESO for archival and publication.


VHS is expected to deliver tiles as primary survey products. If the PI/Co-I's choose not to submit the intermediate products, let's say pawprints, from which the tiles were created, then the PROVi keywords written in the tiles should point to the original raw files like 'VCAM.2010-09-29T05:55:14.101.fits'. The header example for the VISTA tile given in Sect. 3.2.1 of the ESO/EDP Standard (Issue 3) corresponds to this case.

Otherwise, if, based on an evaluation of the extra scientific merit to be expected, intermediate products (pawprints) are planned to be delivered as well, then the PROVi keywords written in the tiles should point to the pawprints and, in turn, the PROVi keys in the pawprints should point to the original raw files.

In the case of single-band source catalogues extracted per tile, called "source lists" in our terminology, the PROV1 key has to point to the originating tile unconditionally (cf. ESO/EDP Standard, Issue 3, Sect. 3.2.4, p.36).

For the definition of processing provenance in the context of Phase 3, including an extended set of examples, please refer to the ESO/EDP Standard, Issue 3, Sect. 2.4.

More on PROV keywords

Q: I note that the PROV keywords do not seem to be mandatory; if that is the case we do not need to provide them, right?

A: PROV keys were recommended for image data products (tile, pawprint etc.) submitted in 2011. The upgrade of the Phase 3 Infrastructure that took place in May 2012 entails the requirement saying that processing provenance is compulsory metadata for Phase 3 data products delivered thereafter.

Encoding PROV in catalogue data using prefixed notation

Q: How to encode processing provenance (PROV) of catalogue data being submitted at the same time as the original images?

A: A new option for the encoding of processing provenance that allows to point to original files within another release has been implemented as a temporary workaround (May 2014).

ORIGFILE can now be prefixed with the Phase 3 release ID, for example:

PROV1 = '104/vmc_er1_05h59-066d20_tile_j_deepimage_1403891.fits.fz'

PROV2 = '104/vmc_er1_05h59-066d20_tile_ks_deepimage_1403943.fits.fz’

The data provider can look up the release ID of the target release in the URL field when editing the release information with the Phase Release Manager, e.g.

N.B. later it is planned to implement support for the concurrent submission of image pixel and catalogue data within the same release, rendering the prefixed notation dispensable.

Missing keyword is not reported

Q: In checking the results of the Phase 3 validator (validation.jar file) I noted that the presence of the ELLIPTIC keyword is not checked for. I noticed this in one file which did not have this keyword defined and the validation did not show any error?

A: Regarding the ELLIPTIC keyword, we know that the validator does not catch the lack of this keyword (and other keywords) in all cases even though it is mandatory according to the EDP format standard. We are working on this issue, but, unfortunately, it is not trivial to fix it quickly.

The updated version of the Phase 3 validator (v1.1.1, May 2012) generally improves the checks on FITS keywords and their content to identify problems as early as possible in the validation process. The existence of the ELLIPTIC keyword is now verified for VISTA tiles and pawprints (but still not for single band source lists).

Displaying big files

Q: How can I display the 9Gb fits files of the stacked UltraVISTA images?

A: You must have a 64 bit OS to display the images. It will work right away in ds9 if your machine has at least 9GByte of RAM. If not, you can use imcopy in IRAF or the stand-alone utility fitscopy that comes with CFITSIO. Compiling fitscopy is usually as simple as:
make fitscopy
You can then copy out a subsection e.g. as
fitscopy 'filename.fits[6317:42736,7063:37182]' filename.trim.fits
This particular subsection would be about 4 Gbyte (and requires about 4 Gbyte RAM to make); you can of course try something smaller. The format of the subsection is x1:x2,y1:y2 (just like in IRAF).

Visualising 1D spectra in the binary table format

Q: How can I visualise the 1D spectra stored in binary table format as defined in the ESO science data products standard?

A: Please follow the instructions here.

CONTINUE convention not supported

Q: Can I use the CONTINUE FITS convention for values exceeding 68 characters?

A: No, the CONTINUE FITS convention for values exceeding 68 characters is not supported by ESO. Please remove offending keywords TRACE1 and ARC and the CONTINUE lines as well as the LONGSTRN related keywords.

OBSTECH values

Q: May you please clarify what the OBSTECH keyword values are?

A: We support the OBSTECH keywords listed in the table below, in addition to those listed in the SDP standard document

Origin of Keyword Value



WCS and CDELT requirements

Q: May you please clarify what the WCS requirements are?


  • CDELTn and PCij: the SDP standard does not allow their usage. Please use the CD matrix.
  • The WCS definition must be unique. Redundant and potentially conflicting keyword definitions will be rejected.

NCOMBINE now mandatory for all products

Q: Is NCOMBINE a mandatory keyword?

A: NCOMBINE in the primary header unit is mandatory for images and 1D spectra.

TEXPTIME now mandatory for images, spectra, and single band source lists.

Q: Is TEXPTIME a mandatory keyword?

A: TEXPTIME is mandatory for: images, 1D spectra, source lists.

Definition of mandatory keyword

Q: Can you please explain what a mandatory keyword means?

A: For keywords of type 'string' it means that both the keyword shall be present and its value shall not be blank (except for REFERENC if a refereed publication is not available at the time of the data release going public). For keywords of type 'float' or 'integer', it means that the FITS card shall not be incomplete and that a valid value shall be provided.

Programmatic access to archive and original filenames

Q: Is there a way to query the archive for the original filenames of the data?

A: Yes, please find more information about programmatic access at:

A typical query is listed below:

Clarify ancillary data content

Q: Which kind of data can be provided in an associated ancillary file?

A: An ancillary data product provided together with a data release should contain additional data that is not included in the science data product itself. The ancillary file should not replicate information present elsewhere. In particular keep in mind that Phase 3 generally mandates that the data documentation is to be provided in the release-description.pdf file. Referential information and other metadata must be defined in the header of the science file in terms of FITS keywords. ESO/ASG has the overall responsibility to assess if provided ancillary data qualify for ingestion into the ESO science archive facility.

EXPTIME cannot be negative

Q: Can EXPTIME assume negative values?

A: No, it is no more allowed to set EXPTIME to a negative value.

Positioning of ORIGFILE

Q: Can ORIGFILE be present in FITS extensions?

A: No, ORIGFILE must be present in the FITS primary header unit, and must not be present in FITS extensions to avoid potential inconsistencies.

Questions and Answers: Catalogues

Unique source identifier in VISTA survey catalogues

Sources in the band merged catalogues with duplication/deblending problems should still have a unique identifier.

Q: Please can you clarify if the column is to be called anything in particular and confirm it'll be OK for it to be a LONG INTEGER. Also will the validator.jar need to be updated?

A: There is no Phase 3 requirement for a particular column name. The names must comply with the restrictions specified in ESO SDP Standard, Issue 5, Sect. 5.1.3, keyword TTYPE*. The unified content descriptor (UCD);meta.main shall be set to identify the catalogue column that represents the source identifier. Long integer type is ok.

Here is an example:

TFORM1 = 'K '
TCOMM1 = 'Unique source identifier'
TUCD1  = ';meta.main'

Note: TNULL1 should not be defined here as the identifier is not nullable by definition. The validator does not need to be updated to accept these data.

About multi-band aperture-matched source lists and band merged catalogues.

Q: What are the differences between multi-band aperture-matched source lists and band-merged catalogue-like products.

A: Here are some useful information on multi-band aperture-matched source lists and band-merged catalogues.

Multi-band aperture-matched source lists (FITS tables) are produced from the single band source lists and are associated with the tiles observed in different bands for one pointing sky position. The astrometric and photometric calibrations for the ra/dec and magnitudes of the sources in these lists are based on night-calibrations. E.g. these are not global calibrations. The multi-band aperture matched source lists cannot be queried for content from the ESO archive; they can be downloaded as fits tables and will refer to the ra/dec sky position of tiles they were produced from.

Multi-band (or band merged) catalogue are released at the milestones for the survey releases. The first Phase 3 submission period for catalogue data resulting from VISTA public surveys occurs between 25 May and 30 June 2012. The calibration of the astrometry and photometry is global, on the whole region covered by the release. The catalogues will be querable for content, differently from the multi-band aperture-matched source lists , i.e. the individual sources in the catalogues will be accessed via the ESO query interface.

Sources in the catalogues may be detected based on the χ2 image or other criteria, driven by the scientific goal of the project. They will not come necessarily from matching single band source lists from the CASU data reduction pipeline.

Furthermore catalogues delivered at the survey releases may contain additional data, that do not come from the VISTA observations: for example photo-z or matched information with X-ray or other multi wavelength observations, weak lensing information etc.

Band-merged catalogues for the deep survey fields

Q: What are multi-band aperture-matched source lists and band merged catalogues for the deep survey fields?

A: It deals with the specific properties of deep surveys with respect to the wide area surveys. As illustrated before multi-band aperture matched source lists are different data products from band-merged catalogues.

Multi-band aperture matched source lists may refer to shallower data products than the deep stacked tiles that are obtained from the data collected over the whole period.

In case of the deep fields, the survey teams may decide to release 1 hr or xx hrs deep tiles with associated multi-band aperture-matched source lists, which will be very valuable data-products for multi-epoch observations, for example monitoring AGN variability or SN searches. In this case the information contained in the multi-band aperture matched source lists is not equivalent to the catalogue extracted from the deep stacks, as the variability information is lost in this final catalogue.

About the multi-band aperture-matched source lists: for deep surveys, the distinction between these source lists and the catalogues expected for the survey releases is more difficult to draw. While for wide surveys the scientific quality difference is clear, it is less so for deep surveys.

Example specific for a deep field

A deep field is observed in Z, J, and Ks in a period  with 28 tile-OBs in Z, 21 tile-OBs in J and 21 tile-OBs in Ks successfully executed. The related data products would be 28 tiles in Z, 21 tiles in J and 21 tiles in Ks + weight maps + single band source lists as data products for these observations.

One would then have 21 multi-band aperture matched source lists in Z, J, and Ks computed from the single-band source lists closest in time.

Light curves

Q: Are the data standards specified for light curves data products? When is the submission date for these products?

A: The ESO External Data Products Standard, Issue 3, Date 22.05.2012, now also covers multi-epoch photometric catalogues (Sect. 4.2.2) to support the Phase 3 delivery of light curves during the May/June 2012 submission period depending on survey progress.

Migrating catalogues from ASCII to FITS format

Q: How to convert an ascii file (table) to a fits file?

A: You can perform the following steps:

  1. Create a comma separated ascii table. For example if the table (cat1.txt) has n columns separated by white spaces:
    awk '{print $1,","$2,","$3,","$...,","$n-1,","$n}' cat1.txt > cat2.txt
  2. Convert the new table (cat2.txt) into a fits file using the stilts tool:
    stilts tcopy cat2.txt cat.fits ifmt=csv ofmt=fits-basic
    stilts <stilts-flags> tcopy ifmt=<in-format> ofmt=<out-format> [in=]<table> [out=]<out-table>
  3.  Add the missing header keywords according to the ESO External Data Products Standard.

The STIL Tool Set can be downloaded from:

For more information please check the following documentation:

TCOMMi and TUCDi keywords in catalogue data files

Q: Are TCOMMi and TUCDi keywords required in the FITS header of catalogue data files?

A: Yes, to successfully pass Phase 3 validation each catalogue data file must include the indexed keywords TCOMMi and TUCDi, one for each catalogue column. Note that Table 15 of the ESO Science Data Products Standard, Issue 5, is lacking these keywords although they are required - an inconsistency which will be corrected in a forthcoming version of the document.

Processing provenance per catalogue record (spectroscopic programs)

Q: Spectroscopic programmes like Gaia-ESO, PESSTO or zCOSMOS produce high-level results in the form of catalogues where each record contains the results of the analysis of one reduced spectrum (which is a Phase 3 product itself). How to encode the links between catalogue record and original spectra?

A: The catalogue must contain a column with a ORIGFILE or ARCFILE reference that identifies for each row the 1D spectrum from which the catalogued parameters are measured.

ORIGFILE refers to the filenames of the 1D spectra within the current release, ARCFILE refers to the ESO archive identifier of the form ADP.<timestamp>. ORIGFILE can be prefixed with the release ID in case spectra have been submitted in another Phase 3 release (see: prefixed notation).

The special keyword TXLNKi = ORIGFILE (or ARCFILE) must be defined in the catalog file.

If the processing provenance has been defined in this way, i.e. per catalogue record, then the PROVi keywords are not applicable and should not be included.


Header listing for HDU #1:



Header listing for HDU #2:





TFORM8 = '52A '

TCOMM8 = 'FITS file name of the original spectrum'

TUCD8  = 'meta.ref'

TXLNK8 = 'ORIGFILE' / Data link to the original spectrum


Questions and Answers: Imaging

Specification of a mask image

Q: May you please explain how to specify a mask image as an ancillary product?

A: The mask image describes the data quality of an image array by flagging bad pixels using integer numbers >0. For example: bright stars (=1), readout spikes (=2) etc. Mask value =0 indicates 'good' data. The detailed definition of mask values >1 shall be documented in the Phase 3 release description.
The mask image is a FITS file with the same dimension and number of extensions (if any) as the FITS file that contains the image data. The mask has integer data type, e.g. BITPIX = 8 or 16.
The indexed keyword ASSOCi is to be set to the following value:
In the case of OmegaCAM data,  i shall be greater than 1 given that  ASSOC1 is reserved for ANCILLARY.WEIGHTMAP.


Keywords refering to the tiling of the sky for OmegaCAM data

Q: How to fill in the values of the TL_RA, TL_DEC, and TL_OFFAN for VST data?

A: In what follows, the assumption is that the information provided by the VST survey teams in the OB does indeed refer to the nominal survey tile position.

  • The position of the tile in terms of TL_RA and TL_DEC is shown in the HIERARCH ESO TEL TARG ALPHA and HIERARCH ESO TEL TARG DELTA keywords. That is, for an OB pointing to a certain coordinate for the acquisition template, the HIERARCH ESO TEL TARG ALPHA/DELTA keywords do not change for each exposure even if these are acquired at relative offsets with respect to the above reference coordinates. The exact coordinates for each exposure are logged in the RA / DEC keywords. The RA/DEC keywords in the image headers contain the precise position on the sky of each individual exposure.
  • The unit and format of "HIERARCH ESO TEL TARG ALPHA" and "HIERARCH ESO TEL TARG DELTA" are HHMMSS.TTT and DDMMSS.TTT, respectively.
  • The tile orientation is recorded in HIERARCH ESO ADA POSANG. POSANG = 0 means the usual N/S orientation, with North and East being aligned with positive y and x. Within the fixed x-y coordinate system, the North axis rotates clockwise with increasing POSANG towards East, thus following the same sign convention as the position angle on the sky. Hence: TL_OFFAN = -POSANG.

Finally, note that by definition, the TL_* keywords are identical for all data belonging to the same tile.

About imaging data without accurate astrometric/photometric calibration

Q: How to submit image data without accurate astrometric/photometric calibration via Phase 3?

A: Imaging data need to be characterized in terms of their astrometric registration (WCS), photometric scale (PHOTZP) and dynamic range (ABMAGLIM, ABMAGSAT) in order to qualify as Science Data Product according to the ESO/SDP standard.

Taking into account that the accuracy of these calibrations varies depending on the scientific goals for which the data was obtained, the ESO/SDP standard does not specify a fixed level of accuracy for calibrations but allows to encode the quality using specific keywords, namely CRDERi, CSYERi, and PHOTZPER.

It means in practical terms that the image WCS may be defined based on the information given in the raw data if it is infeasible to register the image with respect to an astrometric reference catalogue. Similarly, the photometric scale and depth of the image data may be estimated based on the nominal instrumental characteristics (default instrumental zero points, exposure time calculator) if photometric standards have not been obtained as part of the observation. The larger uncertainty associated with the estimated photometric properties needs to be expressed by setting PHOTZPER to an appropriate value.

Specification of an uncalibrated image

Q: How to submit an image without photometric and astrometric calibration?

A: An image without photometric and astrometric calibration can be submitted as an associated file of a main SCIENCE product (e.g. an acquisition image associated to a SCIENCE.SPECTRUM). The uncalibrated image is identified in the header of the SCIENCE file with the ASSOCi keyword as follows: ASSOCi = 'ANCILLARY.IMAGE'.


NDITHER not mandatory any more for OmegaCAM products

Q: Could you please clarify the status of the NDITHER header keyword for OmegaCAM products?

A: NDITHER shall not be mandatory any more for OmegaCAM products.


EFFRON for median-combined SOFI images

Q: What is the correct EFFRON for median-combined SOFI images?

Example: There are 7 raw images, each resulting from averaging together 5 detector integrations (NDIT = 5). A science product is generated by reducing and median-combining those 7 raw images.

In this case:

EFFRON = 12 * sqrt(PI/2) / sqrt( 7 * 5)

where PI is 3.14159, and 12 is the detector readout noise of SOFI in electrons.

Questions and Answers: Spectroscopy

Total flux keyword definition

Q: When shall I set the TOT_FLUX keyword to true for spectroscopic observations?

A: The TOT_FLUX keyword shall be set to T (true) if measurements were taken with a slit wide enough to collect all flux from the source or when correction for slit loss was applied to the measurements.

Flux scale error keyword definition

Q: May you please clarify the definition of the FLUXERR keyword for spectroscopic observations?

A: The FLUXERR is a mandatory quantity that provides the uncertainty on the flux scale. It applies to spectroscopic data with FLUXCAL set to 'ABSOLUTE'. In this case, the FLUXERR value is expressed as a percentage with values between 0 and 100, unless its value cannot be determined, in which case the special value -2. shall be used.

If the spectroscopic data are of type FLUXCAL = 'UNCALIBRATED', the FLUXERR keyword shall be set to -1.

Statistical error in spectral coordinates

Q: May you please clarify the relation between the LAMRMS and the SPEC_ERR keywords for spectroscopic observations?

A: The keyword LAMRMS refer to a well defined measurement on the calibration data whereas the keyword SPEC_ERR refer to an estimate of the error in the science data that might come from LAMRMS or other information.

More precisely, LAMRMS is the root-mean-square of the residuals, defined as:

LAMRMS = sqrt( sum_i(R_i2)/N )

where R_i= residual of wavelength solution for i-th arc line, N = numbers of arc lines = LAMNLIN.

It is an estimator for the uncertainty in each residual under the assumption that all uncertainties are equal and that the model that was subtracted is the correct/appropriate model for the data (so that the errors are random and not systematic).

Identifying a best estimate for SPEC_ERR requires the PI's judgement. In most cases, including UVES and XSHOOTER, the formula SPEC_ERR = LAMRMS / sqrt(LAMNLIN) is a good approximation if the scatter is mainly due to random measurements errors and those errors are similar for all lines.

Note that the value of LAMRMS / sqrt(LAMNLIN) is a lower limit to SPEC_ERR.

Systematic error in spectral coordinates

Q: May you please clarify the definition of the SPEC_SYE keyword for spectroscopic observations?

A: The keyword SPEC_SYE aims at capturing the systematic error in spectral coordinate and is expressed in nanometers.  Possible sources of systematic error include any residual offset of the wavelength calibration and any error related to broadening of the lines due to the observation setup and the observation conditions.

If systematic uncertainties are known to represent an insignificant contribution to the overall error budget on the wavelength axis, or all the systematic errors have been accounted for in the submitted data product spectrum, then SPEC_SYE can be set to zero.

Position of the TFIELDS keyword in the spectroscopic extension header

Q: What is the correct position of the TFIELDS keyword in the binary table extension of a spectroscopic observation?

A: As per the FITS standard, the TFIELDS keyword that specifies the number of fields in each row of the binary table must be the 8th keyword in the FITS extension containing the binary table.

Please note that the current version of the Science Data Product standard (v5) will require an update to comply to the FITS standard.

Spectral resolving power or resolution?

Q: Should I provide the resolution or the resolving power for a 1D spectrum?

A: The SPEC_RES FITS keyword must represent the spectral resolving power (defined as Lambda / Delta_Lambda), and not the spectral resolution. SPEC_RES is therefore a dimensionless (floating point) number.

Please note that the definition of the SPEC_RES keyword in paragraph 2.12 of the Science Data Product standard, Issue 5, is to be amended. 

Specification of a 2D spectrum

Q: How to submit wavelength calibrated and distortion corrected 2D spectra?

A: A 2D spectrum denotes the 2D array with one axis oriented along the dispersion direction (calibrated in wavelength), the other axis being the spatial dimension, normally oriented along the slit. Wavelength calibrated and distortion corrected 2D spectra can be submitted as associated files of the SCIENCE.SPECTRUM products. They are identified in the headers of the SCIENCE.SPECTRUM files with the ASSOCi keyword as follows: ASSOCi = 'ANCILLARY.2DSPECTRUM'.

Variable length arrays

Q: Are variable length arrays supported in the FITS binary table of a 1D spectrum?

No, variable length arrays are not supported in the spectral case.

The 1D spectrum is serialised in a binary table as a single record, with as many cells as needed (e.g. one for the wavelength, one for the flux, etc.), each cell containing one array of data points, and with arrays across all cells of equal size. Despite being supported by FITS, the usage of variable length arrays is not allowed in Phase3, as such format is not well supported by the existing spectral tools.

Please make sure that:


Units of the spectral flux error array

Q: Can I express the errors on the flux of a 1d spectrum as a percentage (%)?

No, percentage is not allowed. The values of the error array associated to the flux of a 1d spectrum must be provided in the same units of the values in the flux array.

Computing EXPTIME and MJD-END of SOFI spectra

Q: How to compute the EXPTIME and MJD-END of a SOFI spectrum?


The EXPTIME value of a Phase 3 product must be set to the total integration time on target. In the case of a single SOFI observation, the correct value can be computed using the following formula:


where DIT and NDIT are to be found in the raw header, e.g.:

HIERARCH ESO DET DIT = 90.0000000 / Integration Time
HIERARCH ESO DET NDIT = 3 / # of Sub-Integrations

If instead the Phase 3 product is the result of a co-addition of multiple exposures, then obviously the EXPTIME will be the sum of the individual DIT * NDIT values.

The SOFI instrument manual states:

NOTA BENE: The counts in a raw data file always correspond to DIT seconds. However, a single raw data file represents a total integration time of NDITxDIT, because the counts in the file are the average of NDIT sub-integrations, each of DIT seconds!


The end time of a Phase 3 SOFI 1d spectrum product (MJD-END) must be computed using the following formula:

MJD-END = MJD-OBS of the last raw observation + NDIT * ( DIT + 1.8) / 86400

where the 1.8 seconds accounts for the necessary overheads, and 86400 scales back from seconds to days.

FILTER keyword in spectroscopic data

Q: May you please clarify the content of the FILTER keyword in 1D spectra products and in the ancillary 2D spectra?

The FILTER keyword must be dropped from the headers of the ESO 1d spectroscopic data products, or it can be renamed as follows:


Original data contains:

FILTER  = 'GBF     '            / Filter name

Please rename as follows:

OFILTER = 'GBF     '            / Filter name

The same applies to any ancillary 2d spectra.

BUNIT keyword in spectroscopic data

Q: Can I use BUNIT to specify the unit and a scaling factor for a 1d spectrum?

The BUNIT keyword must be dropped from the headers of the ESO 1d spectroscopic data products. To provide unit and a scaling factor please use the relevant TUNITn keyword(s).

EXT_OBJ keyword definition

Q: Q: May you please clarify the definition of the EXT_OBJ keyword for spectroscopic observations?

The EXT_OBJ keyword is mandatory for External Data Products, e.g. Spectroscopic Public Surveys.

The keyword EXT_OBJ is not applicable to XSHOOTER Internal Data Products, i.e. the keyword must not be listed in the header. It means the property is unknown.


EXT_OBJ  = F            / True if extended object

For pointlike UVES/Echelle data:

EXT_OBJ  = F            / True if extended object


Q: May you please clarify what the DISPELEM keyword values are?

A: In addition to the DISPELEM listed in a dedicated table in section 2.11 of the SDP standard v.5, please be aware of the following extra DISPELEM values:

Origin of Keyword Value
Possible Values

Encoding quality information

Q: May you please explain how to encode quality information in 1D spectra?

A: Relaxing the restrictions given in SDP standard v5, page 53, the data quality of each pixel is encoded in terms of the sum of powers of 2. Each 'bit' corresponds to a quality condition. Quality default to 0, i.e. good data.

Monotonicity of the wavelength array

Q: May you please clarify the properties of the wavelength array for 1D spectra?

A: The sequence of elements of the WAVE vector for 1D spectra must be in ascending order, i.e. strictly increasing. Same for the FREQ and ENER vectors.

Off source raw exposures

Q: May you please clarify whether off source raw exposures should be taken into account in the set up of the EXPTIME, NCOMBINE, MJD-OBS, MJD-END and PROVi keywords for 1D spectra?

A: Off source raw exposures should be excluded from the calculation of the EXPTIME, NCOMBINE, MJD-OBS, and MJD-END keywords values. The list of PROVi keywords should not contain any reference to off source raw exposures.

Definition of WAVELMIN and WAVELMAX

Q: May you please clarify the definition of the WAVELMIN and WAVELMAX keywords on page 20, section 2.11 of the SDP standard, v.5?

WAVELMIN = SPECTRUM.WAVE[1] / converted to nm

Clarification regarding CONTNORM

Q: Which value should take the keyword CONTNORM in the case I provide two flux arrays, one normalized and the other not?

A: If multiple flux arrays are provided, then
and the Spectral Data Model v2.0 applies (VOCLASS = 'SPECTRUM V2.0').
For example, if field 2 represents the continuum-normalised spectrum (field 3 its error)
and field 4 the non-normalised spectrum (field 5 its error), the TUTYPn are:

TUTYP1  = 'spec:Data.SpectralAxis.Value' / 'IVOA data model element for field 1'
TUTYP2  = 'spec:Data.FluxAxis.Value' / 'IVOA data model element for field 2'
TUTYP3  = 'spec:Data.FluxAxis.Accuracy.StatError' / 'IVOA data model element for
TUTYP4  = 'eso:Data.FluxAxis.Value' / 'ESO element for field 6'
TUTYP5  = 'eso:Data.FluxAxis.Accuracy.StatError' / 'ESO element for field 7'

Moreover the UCD must indicate which one is the continuum-normalised spectrum using the arith.ratio token
and indicate which one is the main one, by placing the meta.main token
at the end of the TUCD2 and TUCD3:

TUCD2 = 'phot.flux.density;em.wl;arith.ratio;meta.main'
TUTYP2 = 'spec:Data.FluxAxis.Value'

TUCD3 = 'stat.error;phot.flux.density;meta.main'
TUTYP3 = 'spec:Data.FluxAxis.Accuracy.StatError'

TUCD4 = 'phot.flux.density;em.wl'
TUTYP4 = 'eso:Data.FluxAxis.Value'

TUCD5 = 'stat.error;phot.flux.density'
TUTYP5 = 'eso:Data.FluxAxis.Accuracy.StatError'

List of Typos

List of typos in the SDP standard v.5

Typo: Page 47 of the SDP standard, v.5

Fix: The PRODCATG for the OmegaCAM pawprint should be set to SCIENCE.MEFIMAGE.

Typo: Page 33 of the SDP standard, v.5

Fix: The 'ancillary.weightmap' value should be uppercased on the fourth line of the page 33.

Typo: Section 4.1 of the SDP standard, v.5

Fix: In case the spectral data have been calibrated to absolute density, the flux scale should be given in physical units, e.g. in erg/s/cm2/A. 'A' should be 'Angstrom' instead.

Typo: Section 2.4.3 of the SDP standard, v.5

Fix: It should read 'exceeding 9999 records'.

Typo: Page 17 of the SDP standard, v.5

Fix: The format string should be TFORM1 = '35A'.