Data Set Information
DATA_SET_NAME MARS EXPRESS MARS PFS EDR THIRD EXTENSION MISSION DATA V1.0
DATA_SET_ID MEX-M-PFS-2-EDR-EXT3-V1.0
NSSDC_DATA_SET_ID
DATA_SET_TERSE_DESCRIPTION
DATA_SET_DESCRIPTION Data Set Overview :The Mars Express (MEX) Planetary Fourier Spectrometer (PFS) DataArchive is a collection of raw data collected during the MEX Missionto Mars. For more information on the investigations proposed see thePFS documentations in the DOCUMENT/ folder.This data set was collected during the MEX Mission phases:- First Extension Mission PhaseMission Phase Definition:It should be noted that the Mars Express (MEX) Planetary FourierSpectrometer (PFS) group uses mission phases which deviate from theones defined in the MISSION.CAT files given by ESA in order to keep the keywords and abbreviations consistent for Mars Express, Venus Express and Rosetta.Those mission phase abbreviations are also used in the data description field of the dataset_id.MaRS mission name | abbreviation | time span:Near Earth Verification | NEV | 2003-06-02 - 2003-07-31----------------------------------------------------------------Interplanetary Cruise | IC | 2003-08-01 - 2003-12-25----------------------------------------------------------------Nominal Mission | Nominal | 2003-12-26 - 2005-11-30----------------------------------------------------------------First Extension Mission | EXT1 | 2006-01-01 - 2007-09-30----------------------------------------------------------------Second Extension Mission| EXT2 | 2007-10-01 - 2009-12-31---------------------------------------------------------------- Data files ---------- Data files are: The tracking files from Deep Space Network (DSN) and from the Intermediate Frequency Modulation System (IFMS) used by the ESA ground station New Norcia. Level 1b data are archived. The Geometry files All Level binary data files will have the file name extension eee : .DAT Data levels ---------- It should be noted that these data levels which are also used in the file names and data directories are PSA data levels whereas in the PDS label files CODMAC levels are used. PSA data level | CODMAC level ----------------------------- 1a | 1 1b | 2 2 | 3 Data Set Identifier ------------------- The 'DATA_SET_ID' is a unique alphanumeric identifier for the data sets. The PFS data set ID is generated using the follow syntax:---- ---V Acronym | Description--------------------------------------------------------------------- | MEX this is fixed, and is the mission ID for | Mars Express.--------------------------------------------------------------------- | M this is fixed, and refers to the target of Mars--------------------------------------------------------------------- | PFS this is fixed and identifies the instrument | as PFS (Planetary Fourier Spectrometer)---------------------------------------------------------------------| 2 this number indicates the level of processing | the data has undergone on the CODMAC scale--------------------------------------------------------------------- | EDR this represents the type of data in the data | set. For the standard PFS deliveries, this will | always be set to 'EDR' meaning 'Experimental Data | Record'--------------------------------------------------------------------- | this is a descriptive secion of the ID and will | typically refer to the mission phase ID or an | orbital range for the nominal mission. Values are: | | NOMINAL nominal mission phase. | EXT1 first extended mission phase. | EXT2 second extended mission phase. | EXT3 third extended mission phase.--------------------------------------------------------------------- | <1.0> this is the version of the data set, | starting at 1.0 and increasing incrementally if | changes are made to the products or the dataset | itself.---------------------------------------------------------------------When all of this is put together, it provides a data set ID of theformMEX-M-PFS-2-EDR-NOMINAL-V1.0orMEX-M-PFS-2-EDR- EXT1-V1.0 VOLUME ------The VOLUME_SET_ID follows a strict formation rule defined in [1],section 19.5.1, with theCountry > IT for ItalyGovernment Branch > CNRDiscipline within government branch > IFSImission and instrument ID > MEXPFSand a 4-digit sequence number > 1001For the number, the first digit represents the VOLUME_SET and thelast number the VOLUME within the VOLUME_SET. Descriptive files ----------------- Descriptive files contain information in order to support the processing and analysis of data files. The following file types are defined as descriptive files with extension eee : .LBL PDS label files .TXT Information (text) filesData Directory Naming Convention and Structure:Inside the DATA directory, the data products are organized intoseveral subdirectories. The structure of the directories will dependupon the phase of the mission in the dataset.IC and NEV:During the Near Earth Verification (NEV) and Interplanetary Cruise(IC) phases of the mission, PFS only took measurements of theinternal calibration source (Internal Black Body and Lamp) and ofdeep space. The limited number of observations are simply divided bysensor into the following directory structure:DATA | |-NEV | |- LWC [Long Wave detector] | |- SWC [Short Wave detector]Nominal and Extended Mission:For the nominal and extended mission phases at Mars, data will besplit into groups of 10 orbits, whith the following syntax: The base directory will be MARS as all products from these phases will be from the planet. Beneath this, data will be separated into observations from the long-wave (LWC) and short-wave (SWC) sensors. Finally, data will be divided into blocks of 10 orbits using the following taxonomy:ORBXAcronym | Description--------------------------------------------------------------------- ORB | This is fixed and means ORBIT--------------------------------------------------------------------- | This will be the first 3 digits of all orbits contained | in this directory--------------------------------------------------------------------- X | This is fixed and means that inside this directory are data | from orbits YYY0 to YYY9.---------------------------------------------------------------------For example, the directory ORB000X will contain all products fromorbit 0001 to 0009.The DATA subdirectory structure for the nominal mission data willtherefore follow the scheme:DATA | |-NEV | | | |-LWC | |-SWC | |- IC | |-LWC | |-SWC | |-MARS | | | |-LWC | | |-ORB001X | | |-ORB002X | | | |-SWC | | |-ORB001X | | |-ORB002XFile naming Convention:The data products are identified principally by orbit numer anddetector type, following the scheme:PFS____. Orbit number.For the Near Earth Verification and Interplanetary Cruise Phase the field is substituted with the name of the Phase andSub-phase as : : .For the files in the CALIB/ directory the field is substitutewith the field, Responsivity or Deep Spaceobservation, and the field, Forward or Reversependulum motion, as: : _--------------------------------------------------------------------- | IC for Interplanetary Cruise Phase | NEV for Near Earth Verification Phase--------------------------------------------------------------------- | C Check Out Sub-phase | D Dry Earth Sub-phase | E Earth Moon Sub-phase (Observation to Earth and Moon) | 1 PS001 Sub-phase (First Switch ON) | 2 PS002 Sub-phase (Calibration) | 3 PS003 Sub-phase (DTM, Pericenter Pass Simulation , | Calibration) | 4 PS004 Sub-phase (FOV, Calibration) | 5 PS005 Sub-phase (Calibration, heating of SW detector) | S Star Calibration Sub-phase | M Mars Crossing Sub-phase | | all the sub-phases reffer to specific PFS test | operation performed during the NEV phases.--------------------------------------------------------------------- | Defines if the instrument is in calibration mode or | in measurement mode: | | CAL Calibration | MEAS Measurement | | For the HK file field is referred to the | corrisponding RAW file field.--------------------------------------------------------------------- | indicates the type of data provided: RAW-HK-RAD | | RAW contains interferogram | HK contains the HK information about PFS during the | acquisition | RAD contains radiance spectra (calibrated data only)--------------------------------------------------------------------- | defines the type of the detector used for the | interferogram acquisition: Short wavelength (SW) or Long | wavelength (LW).--------------------------------------------------------------------- | the extension depends on the type of file (LBL for a | label file, DAT for the data product associated with | the label)---------------------------------------------------------------------For Mars:PFS_0010_ MEAS_HK_SW.LBLPFS_0010_ MEAS_HK_SW.DATwould be a PFS product from Mars orbit 0010. It would be a rawcalibration data product from the short wavelength sensor with itsassociated label.For the Near Earth Verification and Interplanetary Cruise Phase:PFS_NEV1_MEAS_HK_SW.DATPFS_NEV1_MEAS_HK_SW.LBLwould be a PFS product from the PS001 Sub-phase of the Near EarthVerification phase. It would be a raw calibration product from theshort wavelength sensor with its associated label.PFS_IC_CAL_HK_SW.DATPFS_IC_CAL_HK_SW.LBLwould a PFS product from the Check Out sub-phase of theInterplanetary Cruise. It would be a raw calibration product from thelong wavelength sensor with its associated label.Ancillary Data - EXTRAS:The EXTRAS directory contains items that may be useful to a user, butare non-essential for the use of the data in the PFS data sets andare not essential for the PSA or compliance to the PDS Standards.The contents of the EXTRAS directory do not need to conform to PDSstandards, and all files within this directory are produced andpresented by the PFS team. In the PFS EXTRAS directory is a filethat describes any special features of a given orbit. For example,any specific scientific objectives targeted, special events thatoccurred or tests that were completed for a given orbit are listed inthis file. The file is presented in ASCII format.Software:PFS software (IDL version)febrary 2007When downloading a ZIP file, the user should put it in a workingdirectory dedicated to PFS software,then unzip it. This will createa two subdirectory :/SOFTWARE/||- /CALIB/||- /DATA/||- /GEOMETRY/The essential functions to open and read the data are in the FUNCTIONSsubdirectory of each directory. The examples programs given in bothDATA and GEOMETRY are intended only as reader of the PFS data.The CALIB subdirectory contains both the programs to read calibratedPFS spectra stored in the /CALIB_SAMPLE/ directory at root level andthe code to produce that outputs starting from the RAW data and thecalibration tables stored in the /CALIB / directory at root level.Essentially the software in the /SOFTWARE/CALIB/CALIBRATOR/ use thesame functions stored in the /SOFTWARE/CALIB/DATA/ to read raw data,then read the right calibration tables and apply the calibrationoperation to obtain the calibrated spectra (further details should befound in the calibration documents PFS_LWC_CALIB.PDF andPFS_SWC_CALIB.PDF as well in the PFS_CAL_LAB_1.PDF ,PFS_CAL_LAB_2.PDF and PFS_CAL_NEAREARTH.PDF, in the /DOCUMENT/directory).To run example code do the following steps:- open a .PRJ file (for DATA or for GEOMETRY)- change the PATH variable to your PFS Data directory- Project > Compile > All Files- Project > RunOnly for the software stored in the /CALIBRATOR/ subdirectory, thelast step must be substituted with :- Run > Run 'program_name'The LWC_CAL.pro, SWC_CAL_LASER-OFF.pro and SWC_CAL_LASER-ON.pro willgive to the user the calibrated spectra calculated directly from theraw data and from the calibration tables.---------Function and Resulting Variables--------read_pfs_data(FILE,NUM,RECORDS):return a structured variable array whith the data. Array lenght isNUM.Each array element is defined as : OBT_OBSERVATION_TIME : DOUBLE PRECISION FLOAT SCET_OBSERVATION_TIME : UNSIGNED LONG INTEGER INTERFEROGRAM : INTEGER ARRAY WHITH LENGHT : RECORDSINPUT: FILE : path of the data file to open NUM : total number of the field (: observation) stored in the file RECORDS : length of a single interferogram--------read_pfs_hk(FILE,NUM): return a structured variable array whith the housekeeping data. Array lenght is NUM. Each array element is defined as : OBT_OBSERVATION_TIME : DOUBLE PRECISION FLOAT SCET_OBSERVATION_TIME : UNSIGNED LONG INTEGER TypeOfMes : UNSIGNED LONG INTEGER SD_Version : UNSIGNED LONG INTEGER ZOPD_SW_FWD : UNSIGNED LONG INTEGER ZOPD_SW_REV : UNSIGNED LONG INTEGER ZOPD_LW_FWD : UNSIGNED LONG INTEGER ZOPD_LW_REV : UNSIGNED LONG INTEGER SCANPOS : UNSIGNED LONG INTEGER SW_ZeroX_Cutoff_Status : DOUBLE PRECISION FLOAT LW_ZeroX_Cutoff_Status : DOUBLE PRECISION FLOAT SPEEDCLOCK_Status : DOUBLE PRECISION FLOAT ADCCLOCK_Status : DOUBLE PRECISION FLOAT SW_Detector_Cutoff_Status : DOUBLE PRECISION FLOAT LW_Detector_Cutoff_Status : DOUBLE PRECISION FLOAT SWGAIN_Status : UNSIGNED LONG INTEGER LWGAIN_Status : UNSIGNED LONG INTEGER First_ADC_1_Status : UNSIGNED LONG INTEGER Second_ADC_1_Status : UNSIGNED LONG INTEGER First_ADC_2_Status : UNSIGNED LONG INTEGER Second_ADC_2_Status : UNSIGNED LONG INTEGER Select_Motor_Coil_Status : UNSIGNED LONG INTEGER DPDIR_Status : UNSIGNED LONG INTEGER SW_ZOPD_Position : UNSIGNED LONG INTEGER LW_ZOPD_Position : UNSIGNED LONG INTEGER Right_Collisions : UNSIGNED LONG INTEGER Left_Collisions : UNSIGNED LONG INTEGER SWLASERPWR_10V : DOUBLE PRECISION FLOAT LWLASERPWR_10V : DOUBLE PRECISION FLOAT SWPHOTODIODEPWR_10V : DOUBLE PRECISION FLOAT LWPHOTODIODEPWR_10V : DOUBLE PRECISION FLOAT T1_10V : DOUBLE PRECISION FLOAT T2_10V : DOUBLE PRECISION FLOAT T3_10V : DOUBLE PRECISION FLOAT T4_10V : DOUBLE PRECISION FLOAT T5_10V : DOUBLE PRECISION FLOAT T6_10V : DOUBLE PRECISION FLOAT T7_10V : DOUBLE PRECISION FLOAT T8_10V : DOUBLE PRECISION FLOAT LDTEMPSW_10V : DOUBLE PRECISION FLOAT LDTEMPLW_10V : DOUBLE PRECISION FLOAT SWTEMP_10V : DOUBLE PRECISION FLOAT LWTEMP_10V : DOUBLE PRECISION FLOAT TEMPA1_10V : DOUBLE PRECISION FLOAT TEMPA2_10V : DOUBLE PRECISION FLOAT SWTRW_10V : DOUBLE PRECISION FLOAT LWTRW_10V : DOUBLE PRECISION FLOAT CLVOLTAGE_10V : DOUBLE PRECISION FLOATINPUT: FILE : path of the data file to open NUM : total number of the field (: observation) stored in the file--------read_pfs_label(FILE,NAME):return value stored in a PDS label file in the NAME fieldINPUT: FILE : path of the label file to open NAME : name if the fiel to search for (i.e. ROWS or FIELDS)--------reader_geometry(FILE,NUM):return a structured variable array whith all the geometricalinformation.Array lenght is NUM.Each array element is defined as : SCET : DOUBLE PRECISION FLOAT LONGITUDE : DOUBLE PRECISION FLOAT LATITUDE : DOUBLE PRECISION FLOAT SPACECRAFT_ALTITUDE : DOUBLE PRECISION FLOAT Local_Time : SINGLE PRECISION FLOAT Solar_Longitude : DOUBLE PRECISION FLOAT INCIDENC_EANGLE : SINGLE PRECISION FLOAT EMISSION_ANGLE : SINGLE PRECISION FLOAT PHASE_ANGLE : SINGLE PRECISION FLOAT MOLA_ALTIMETRY : SINGLE PRECISION FLOAT LW_TANGENT_ALTITUDE : SINGLE PRECISION FLOAT LW_TARGET_DISTANCE : SINGLE PRECISION FLOAT SOLAR_DISTANCE : SINGLE PRECISION FLOAT SUBSOLAR_LONGITUDE : DOUBLE PRECISION FLOAT SUBSOLAR_LATITUDE : DOUBLE PRECISION FLOAT PLANETARY_PHASE_ANGLE : SINGLE PRECISION FLOAT SUB_SPACECRAFT_LONGITUDE : DOUBLE PRECISION FLOAT SUB_SPACECRAFT_LATITUDE : DOUBLE PRECISION FLOAT JULIAN_DATE : DOUBLE PRECISION FLOAT AIR_MASS : SINGLE PRECISION FLOATINPUT: FILE : path of the geometry file to open NUM : total number of the field (: observation) stored in the fileDefiniton of field in Geometry File:------------------------------------------------------------------Label | Description | Range | Units------------------------------------------------------------------SCET | Value of the Spacecraft clock | |LONG_LW | Mars Longitude for the LWC | -180/+180 | degLAT_LW | Mars Latitude for the LWC | - 90/+ 90 | degLONG_SW | Mars Longitude for the SWC | -180/+180 | degLAT_SW | Mars Latitude for the SWC | - 90/+ 90 | deg | The Longitudes are expressed | | following the Eastward convention | |SC_ALT | Spacecraft altitude | | kmLT | Local Time at the SWC target | |hoursLS | Solar Longitude | 0/+360 | degINC_SW | Incidence angle for the SWC | 0/+180 | degEM_SW | Emission angle for the SWC | 0/+180 | degPH_SW | Phase angle for the SWC | 0/+180 | degALTM | Mola Altimetry | | mTG_ALT | Limb altitude for the SWC | | km | This parameter is not null only | | | for limb observations | |TG_DIST | Distance from the spacecraft to | | km | the target point (SWC) | |S_DIST | Solar distance | | auSS_LONG | Longitude of the sub-solar point | -180/+180 | degSS_LAT | Latitude of the sub-solar point | - 90/+ 90 | degPL_PH | Planetary phase angle | 0/+180 | degSSC_LONG | Longitude of the sub-spacecraft | -180/+180 | degSSC_LAT | Latitude of the sub-spacecraft | - 90/+ 90 | degJD | Julian Date | |Airmass | Secant of the emission angle | |--------------------------------------------------------------------------read_pfs_data_calib(FILE,NUM,RECORDS):return a structured variable array whith the data. Array lenght is NUM. Each array element is defined as : OBT_OBSERVATION_TIME : DOUBLE PRECISION FLOAT SCET_OBSERVATION_TIME : DOUBLE PRECISION FLOAT WAVENUMBER : DOUBLE PRECISION ARRAY WHITH LENGHT : RECORDS RADIANCE : DOUBLE PRECISION ARRAY WHITH LENGHT : RECORDSINPUT: FILE : path of the data file toopen NUM : total number of the field (: observation) stored in the file RECORDS : length of a single spectra, the same for the WAVENUMBER and RADIANCE fields.--------Documents:Documents directory contains all of the Flight user manual documents,which have been divided into 9 chapters, describing in detail all ofthe features of the experiment. In addition, the ICD (this document)is provided also in ASCII format, and papers describing thecalibration procedures for PFS are provided. A complete list and a short description:---------------------------------------------------------------------Name | Description---------------------------------------------------------------------DOCINFO.TXT | DOCUMENTS directory content list---------------------------------------------------------------------CALIBR_REPORTS_LONG_TERM.TXT| Calibration Reports, warnings on | Calibration and long term calibration | notes.---------------------------------------------------------------------CALIBR_REPORTS_LONG_TERM.LBL| Label file for the Calibration Reports---------------------------------------------------------------------CALIB_SAMPLES_NOTE.TXT | Reports on how to obtain the files in | CALIB_SAMPLES/ from the RAWdata.---------------------------------------------------------------------CALIB_SAMPLES_NOTE.LBL | Label file for the Calibration notes.---------------------------------------------------------------------MEX-PFS-PSA-ICD-24.ASC | Interface Control Document in ASCII---------------------------------------------------------------------MEX-PFS-PSA-ICD-24.LBL | Label file for Interface Control Document---------------------------------------------------------------------MEX-PFS-PSA-ICD-24.PDF | Interface Control Document in Portable | Document Format---------------------------------------------------------------------MEX-PFS-PSA-ICD_FIG_1.PNG | ICD figure 1 - Pfs optical scheme---------------------------------------------------------------------MEX-PFS-PSA-ICD_FIG_2.PNG | ICD figure 2 - Data acquisition and | processing scheme---------------------------------------------------------------------MEX-PFS-PSA-ICD_FIG_3.PNG | ICD figure 3 - High level directory | structure---------------------------------------------------------------------MEX-PFS-PSA-ICD_FIG_4.PNG | ICD figure 4 -DATA directory structure---------------------------------------------------------------------MEX_ORIENTATION_DESC.LBL | Label file for Mars express spacecraft | orientation---------------------------------------------------------------------MEX_ORIENTATION_DESC.TXT | Mars express spacecraft orientation---------------------------------------------------------------------PFS_CAL_LAB_1.LBL | Label fi le for Internal Note on Pfs | Calibration - Volume I---------------------------------------------------------------------PFS_CAL_LAB_1.PDF | Internal Note on Pfs Calibration - I---------------------------------------------------------------------PFS_CAL_LAB_2.LBL | Label file for Internal Note on Pfs | Calibration - Volume I---------------------------------------------------------------------PFS_CAL_LAB_2.PDF | Internal Note on Pfs Calibration - I---------------------------------------------------------------------PFS_CAL_NEAREARTH.LBL | Label file for Internal Note on Pfs | Calibration in Space---------------------------------------------------------------------PFS_CAL_NEAREARTH.PDF | Internal Note on Pfs Calibration in Space---------------------------------------------------------------------PFS_LWC_CALIB.LBL | Label file for LWC channel Calibration---------------------------------------------------------------------PFS_LWC_CALIB.PDF | LWC channel Calibration---------------------------------------------------------------------PFS_MEX_FUM.LBL | Label file for FUMs Index---------------------------------------------------------------------PFS_MEX_FUM.PDF | FUMs Index---------------------------------------------------------------------PFS_MEX_FUM1.LBL | Label file for FUM 1 - Instrument | description---------------------------------------------------------------------PFS_MEX_FUM1.PDF | FUM 1 - Instrument description---------------------------------------------------------------------PFS_MEX_FUM2.LBL | Label file for FUM 2 - Instrument | performance budgets---------------------------------------------------------------------PFS_MEX_FUM2.PDF | FUM 2 - Instrument performance budgets---------------------------------------------------------------------PFS_MEX_FUM3.LBL | Label file for FUM 3 - Instrument | software and memory map---------------------------------------------------------------------PFS_MEX_FUM3.PDF | FUM 3 - Instrument software and memory | map---------------------------------------------------------------------PFS_MEX_FUM4.LBL | Label file for FUM 4 - Housekeeping | information---------------------------------------------------------------------PFS_MEX_FUM4.PDF | FUM 4 - Housekeeping information---------------------------------------------------------------------PFS_MEX_FUM5.LBL | Label file for FUM 5 - Operating, | non-operating conditions and interfaces---------------------------------------------------------------------PFS_MEX_FUM5.PDF | FUM 5 - Operating, non-operating conditions | and interfaces---------------------------------------------------------------------PFS_MEX_FUM7.LBL | Label file for FUM 7 - Instrument operation | manual---------------------------------------------------------------------PFS_MEX_FUM7.PDF | FUM 7 - Instrument operation manual---------------------------------------------------------------------PFS_MEX_FUM8.LBL | Label file for FUM 8 - Science operations---------------------------------------------------------------------PFS_MEX_FUM8.PDF | FUM 8 - Science operations---------------------------------------------------------------------PFS_MEX_FUM9.LBL | Label file for FUM 9 - Tm_tc interface | data base---------------------------------------------------------------------PFS_MEX_FUM9.PDF | FUM 9 - Tm_tc interface data base---------------------------------------------------------------------PFS_ON_MARS_EXPRESS.LBL | Label file for Instruments description---------------------------------------------------------------------PFS_ON_MARS_EXPRESS.PDF | Instruments description---------------------------------------------------------------------PFS_SWC_CALIB.LBL | Label file for SWC channel Calibration---------------------------------------------------------------------PFS_SWC_CALIB.PDF | SWC channel Calibration---------------------------------------------------------------------
DATA_SET_RELEASE_DATE 2010-12-07T00:00:00.000Z
START_TIME 2010-01-01T10:16:25.159Z
STOP_TIME 2010-06-30T01:18:33.389Z
MISSION_NAME MARS EXPRESS
MISSION_START_DATE 1997-10-31T12:00:00.000Z
MISSION_STOP_DATE N/A (ongoing)
TARGET_NAME PHOBOS
RESPONSIVITY
INTERNAL SOURCE
MARS
DEEP SPACE
TARGET_TYPE SATELLITE
CALIBRATION
PLANET
INSTRUMENT_HOST_ID MEX
INSTRUMENT_NAME PLANETARY FOURIER SPECTROMETER
INSTRUMENT_ID PFS
INSTRUMENT_TYPE INFRARED INTERFEROMETER
NODE_NAME Geosciences
ARCHIVE_STATUS IN PEER REVIEW
CONFIDENCE_LEVEL_NOTE :Review::These data have been reviewed by the instrument team and are of thehighest quality that can be generated at this time. Science resultsbased on these data have been published in several journals (JGR,PSS,EGU, etc.).Data Coverage/Quality::There are several known problems throughout the dataset(microvibrations, contamination, etc.) that are still under study. Thequality of data is therefore not fixed, as these problems will bedetected and corrected over time. For details of the known problems todate, please refer to the following documentation: GIURANNAETAL2005aand GIURANNAETAL2005b.
CITATION_DESCRIPTION V. Formisano, F. Angrilli, G. Arnold,S. Atreya, G. Bianchini, D. Biondi,A.,Blanco, M. I. Blecka,A. Coradini, L. Colangeli, A. Ekonomov, F. Esposito, S.,Fonti,M.Giuranna, D. Grassi, V. Gnedykh, A. Grigoriev, G.Hansen, H. Hirsh,I. Khatuntsev, A. Kiselev, N. Ignatiev,, A. Jurewicz, E. Lellouch,J. LopezMoreno, A. Marten, A. Mattana, A. Maturilli, E. Mencarelli,M. Michalska, V.Moroz, B.Moshkin, F. Nespoli, Y. Nikolsky, R. Orfei,P. Orleanski, V.Orofino,E. Palomba, D. Patsaev, G. Piccioni, M. Rataj,R. Rodrigo, J.Rodriguez, M.Rossi, B.Saggin, D. Titov, L. ZasovaMEX-PFS-PSA-ICD-24.PDF, NASA Planetary Data System, 2005.
ABSTRACT_TEXT The Mars Express PFS data set contains raw (CODMAC Level 2) measurements from the Planetary Fourier Spectrometer collected during the first extension Mars orbit phases.
PRODUCER_FULL_NAME PFS SCIENCE TEAM
SEARCH/ACCESS DATA
  • Geosciences Web Service
    		•