In this section you can find some resources and information for external users who are using the publicly available data on the ESA Planetary Science Archive.


ESA Planetary Science Archive

SO and UVIS calibrated data is now publicly available via the ESA Planetary Science Archive.


Access the ESA Planetary Science Archive


Below you can find a sample SO file and a short guide explaining how to use the data. Firstly, we suggest that you read both Neefs et al. 2015 and Liuzzi et al. 2019 to understand how the AOTF and diffraction grating work to select the desired spectral region (diffraction order). For those unaccustomed to the PDS4 standard, we suggest you take a look at the NASA PDS Atmospheres Node.


A NOMAD calibrated data product consists of 4 files, conforming to the NASA PDS4 format. An example of an SO channel product is given here:

Update 22nd June 2020: Following peer review, the products have been modified.

Note that this is an example of a version 1.0 product. Small changes may be made between the product here and those in the PSA archive. Also note that UVIS observes at the same time as the SO and LNO channels, but operates differently and therefore contains some different fields.


The solar occultation filename has a defined format: nmd_cal_sc_<channel>_<start_time>-<end_time>-<altitude_type>-<observation_type>-<diffraction_order> for the data product/label and nmd_cal_sc_browse_<start_time>-<end_time>-<altitude_type>-<observation_type>-<diffraction_order>-<channel> for the browse product/label. More information on the <altitude_type> and <observation_type> letters can be found here.

By looking at the filename we can see that the product above contains data taken by the SO channel, measuring diffraction order 134 during an egress occultation, starting at 20:21:11 UTC on 21st April 2018 (the first solar occultation of the science phase). The <altitude_type> letter "a" tells us that this diffraction order was measured for the complete solar occultation (i.e. from above the atmosphere to the surface).


The browse product shows a quick summary of the data, displaying the transmittances of all recorded spectra throughout the entire occultation. Notable features include a small H2O absorption band around 3026cm-1. Most bad pixels have been successfully corrected; however some datasets still include the occasional bad pixel. The SO channel consists of 320 pixels in the spectral dimension, ranging here from 3011 to 3035cm-1 for diffraction order 134 and this specific instrument temperature. To run a simple test of your PDS reader, follow the instructions below to plot the transmittances in the data product and check that the figure matches the browse product:

  • Wavenumber data, to be plotted on the x axis, can be found in the xml group field Pixel wavenumbers (for SO) or Pixel wavelengths (for UVIS)
  • Transmittances, to be ploted on the y axis, can be found in the xml group field Pixel transmittances (for occultation data) or Pixel radiances (for UVIS nadir data).
  • The tangent altitude corresponding to the centre of the field of view is found in the fields TangentAltStart0 and TangentAltEnd0, where Start and End correspond to the acqusition start and end times respectively, and the 0 refers to the field of view point (where 0 = centre, and 1-4 define the corners of the SO channel). 


Experiment-To-Archive Interface Document (EAICD)

The EAICD describes the steps taken to process and calibrate the data, and a detailed description of all the fields available in the data.


Click here to access the NOMAD EAICD



Analysing the data

To run retrievals on the data, it is essential that the efffects of the AOTF and diffraction grating are accounted for within the retrieval code. Work is ongoing within the team to finalise the AOTF and grating blaze functions; at present a model is presented in Liuzzi et al. 2019 for those interested in further analysis. As calibration progresses, this page will be updated with more information.


Known issues

This page contains a list of known issues that have been found in the data. If you find anything unusual, please check these pages first to see if the reason is already known.