SPDF - Coordinated Data Analysis Web (CDAWeb)

+ SPDF HOME

+ MISSION DATA

+ MODELS at CCMC

+ SCIENCE ENABLED

+ AND MORE

+ CDAWeb Home

CDAWeb

+ FEEDBACK

CDAWeb Served Heliophysics Datasets Beginning with 'P'

PHOBOS2_HELIO1DAY_POSITION: Position in heliocentric coordinates from SPDF Helioweb - Natalia Papitashvili (NASA/GSFC/SPDF)

PIONEER10_COHO1HR_MERGED_MAG_PLASMA: Pioneer-10 merged hourly magnetic field, plasma and ephermis data - E.J. Smith (HVM) and A. Barnes (PLS) (NASA JPL/AMES)

PIONEER10_HELIO1DAY_POSITION: Position in heliocentric coordinates from SPDF Helioweb - Natalia Papitashvili (NASA/GSFC/SPDF)

PIONEER10_MAG_1MIN_MAGNETIC_FIELD: 1 min averaged magnetic field - Edward Smith (JPL NASA)

PIONEER11_COHO1HR_MERGED_MAG_PLASMA: Pioner-11 merged hourly magnetic field, plasma and ephermis data - E.J. Smith (HVM) and A. Barnes (PLS) (NASA JPL/AMES)

PIONEER11_HELIO1DAY_POSITION: Position in heliocentric coordinates from SPDF Helioweb - Natalia Papitashvili (NASA/GSFC/SPDF)

PIONEER6_R0_MAGPLASMA: Pioneer6 merged magnetic field and plasma hourly data from COHOWeb Service

PIONEER7_R0_MAGPLASMA: Pioneer7 merged magnetic field and plasma hourly data from COHOWeb Service

PIONEERVENUS_COHO1HR_MERGED_MAG_PLASMA: PioneerVenus merged magnetic field and plasma hourly data from COHOWeb Service - Dr. T. C. Russell (magnetic field), Dr. Aaron Barnes (plasma) (UCLA, NASA/Ames)

PIONEERVENUS_MERGED_SOLAR-WIND_10M: Pioneer Venus Orbiter 10-minute merged solar wind data - Dr. C. T. Russell (magnetic field), Dr. Aaron Barnes (plasma) (UCLA, NASA/Ames)

PLUTO_HELIO1DAY_POSITION: Position in heliocentric coordinates from SPDF Helioweb - Natalia Papitashvili (NASA/GSFC/SPDF)

PMC-TURBO_L1_BOLIDE_VBC: PMC-Turbo/BOLIDE Rayleigh lidar PMC data 20m 10s resolution - Bernd Kaifler, bernd.kaifler@dlr.de (DLR, IPA)

POLAR_HYDRA_MOMENTS-14SEC: Polar Fast Plasma Analyzer 13.8 second Resolution Moments - J. Scudder (U of Iowa)

PO_10MINATT_EFI: Polar Spacecraft Attitude in GSE Coordinates - Mozer (UC Berkeley)

PO_6SECEDSC_EFI: Polar Electric Field (x,y) in Despun Spacecraft Coordinates - Mozer (UC Berkeley)

PO_6SECPOTLDENS_EFI: Polar Spacecraft Potential and Inferred Plasma Density - Mozer (UC Berkeley)

PO_AT_DEF: Polar Definitive Attitude Data

PO_AT_PRE: Polar Predicted Attitude Data

PO_EJ_VIS: Polar Visible Imaging System, Earth Camera Images, processed - Louis A. Frank (The University of Iowa)

PO_H0_CAM: Ion Fluxes 1-200 keV/q @ 3-minute resolution, Polar CAMMICE - R. Friedel (Lanl)

PO_H0_HYD: Polar Fast Plasma Analyzer 13.8 second Resolution Parameters - J. Scudder (U of Iowa)

PO_H0_PWI: Polar Plasma Wave Instrument, MCA - D. Gurnett (U. Iowa)

PO_H0_TID: Polar TIDE H+,O+,He+ High Time Resolution Data (before 10/01/96) - Thomas E. Moore (Goddard Space Flight Center)

PO_H0_TIM: Polar Toroidal Imaging Mass-Angle Spectrograph, High Time Resolution data - W.K. Peterson (LASP/University of Colorado)

PO_H0_UVI: Polar Ultraviolet Imager, High Res. - G. Parks (U. Washington)

PO_H1_PWI: Polar Plasma Wave Instrument, Step Frequency Receivers A & B - D. Gurnett (U. Iowa)

PO_H1_TID: Polar TIDE Total Ion High Time Resolution Data (after 12/7/96) - Thomas E. Moore (Goddard Space Flight Center)

PO_H1_UVI: Polar Ultraviolet Imager, High Res. - G. Parks (U. Washington)

PO_H2_PWI: Polar Plasma Wave Instrument, Low Frequency Waveform Receiver, ~0.01 sec resolution fields - D. Gurnett (U. Iowa)

PO_H2_TIM: H+, O+, He+ and He++ upflowing fluxes, from Polar TIMAS - W.K. Peterson (LASP/University of Colorado)

PO_H3_PWI: Polar Plasma Wave Instrument, High Frequency Waveform Receiver, 16 kHz Time Domain Fields - D. Gurnett (U. Iowa)

PO_H4_PWI: Polar Plasma Wave Instrument, High Frequency Waveform Receiver, 2 kHz, Time Domain Fields - D. Gurnett (U. Iowa)

PO_H5_PWI: Polar Plasma Wave Instrument, High Frequency Waveform Receiver, 16 kHz, Time Domain Fields. - D. Gurnett (U. Iowa)

PO_H7_PWI: Polar Plasma Wave Instrument, High Frequency Waveform Receiver, 6-channel (~1.5 usec resolution) fields - D. Gurnett (U. Iowa)

PO_H8_PWI: Polar Plasma Wave Instrument, High Frequency Waveform Receiver - D. Gurnett (U. Iowa)

PO_H9_PWI: Polar Plasma Wave Instrument, High Frequency Waveform Receiver - D. Gurnett (U. Iowa)

PO_HYD_ENERGY_FLUX: Polar Fast Plasma Analyzer 13.8 second Resolution Moments - J. Scudder (U of Iowa)

PO_K0_CAM: CAMMICE Energetic particles & Ion composition, Key parameters - T. A. Fritz (Boston University)

PO_K0_CEP: CEPPAD Energetic particles & angular distribution, Key parameters - J. B.Blake (Aerospace Corp. )

PO_K0_EFI: Polar Electric Field Instrument, Key Parameters - F. Mozer (UC Berkeley)

PO_K0_GIFWALK: Links to Polar KP pre-generated survey and other plots - Polar-Wind-Geotail Ground System (NASA GSFC)

PO_K0_HYD: Polar Fast Plasma Analyzer, Key Parameters - J. Scudder (U of Iowa)

PO_K0_MFE: Polar Magnetic Field,Key Parameters - C.T. Russell (UCLA)

PO_K0_PIX: Polar Ionospheric X-ray Imaging Experiment Key Parameters - D. Chenette (Lockheed)

PO_K0_PWI: Polar Plasma Wave Instrument, Key Parameters - D. Gurnett (U. Iowa)

PO_K0_SPHA: Polar Spin Phase Key Parameters

PO_K0_UVI: Polar Ultraviolet Imager, Key Parameters - G. Parks (U. Washington)

PO_K0_VIS: Polar Visible Imaging System Key Parameters - Louis A. Frank (The University of Iowa)

PO_K1_TIM: Polar Toroidal Imaging Mass-Angle Spectrograph, Supplemental Key Parameters - W.K. Peterson (LASP/University of Colorado)

PO_K1_VIS: Polar Visible Imaging System Earth Camera Key Parameter - Louis A. Frank (The University of Iowa)

PO_LEVEL1_UVI: Polar UVI Level-1 Full Resolution Imager Data - G. Parks (U. Washington)

PO_OR_DEF: Polar Definitive Orbit Data

PO_OR_PRE: Polar Predicted Orbit Data

PO_PA_DEF: Polar Platform Attitude Definitive data

PO_VIS_EARTH-CAMERA-CALIBRATED: Polar Visible Imaging System (VIS) Earth Camera Images at ~4 minute cadence - Louis A. Frank (The University of Iowa)

PO_VIS_VISIBLE-IMAGER-CALIBRATED: Polar Visible Imaging System (VIS) Low Res. Camera - Louis A. Frank (The University of Iowa)

PSP_COHO1HR_MERGED_MAG_PLASMA: Merged hourly magnetic field, plasma, proton fluxes, and ephermis data of PSP - Natalia Papitashvili (NASA/GSFC)

PSP_FLD_L2_AEB: PSP FIELDS AEB - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_AC_BPF_DV12HG: PSP FIELDS Level 2 DFB AC Bandpass Filter dV12hg - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_AC_BPF_DV34HG: PSP FIELDS Level 2 DFB AC Bandpass Filter dV34hg - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_AC_BPF_SCMULFHG: PSP FIELDS Level 2 DFB AC Bandpass Filter SCMulfhg - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_AC_BPF_SCMUMFHG: PSP FIELDS Level 2 DFB AC Bandpass Filter SCMumfhg - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_AC_SPEC_DV12HG: psp fld l2 dfb ac spec dV12hg - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_AC_SPEC_DV34HG: psp fld l2 dfb ac spec dV34hg - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_AC_SPEC_SCMDLFHG: psp fld l2 dfb ac spec SCMdlfhg - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_AC_SPEC_SCMELFHG: psp fld l2 dfb ac spec SCMelfhg - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_AC_SPEC_SCMFLFHG: psp fld l2 dfb ac spec SCMflfhg - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_AC_SPEC_SCMMF: psp fld l2 dfb ac spec SCMmf - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_AC_SPEC_SCMULFLG: psp fld l2 dfb ac spec SCMulflg - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_AC_SPEC_SCMVLFHG: psp fld l2 dfb ac spec SCMvlfhg - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_AC_SPEC_V5HG: psp fld l2 dfb ac spec V5hg - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_AC_XSPEC_DV12HG_DV34HG: PSP FLD L2 DFB AC XSPEC DV12HG - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_AC_XSPEC_SCMDLFHG_SCMELFHG: PSP FLD L2 DFB AC XSPEC SCMDLFHG - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_AC_XSPEC_SCMDLFHG_SCMFLFHG: PSP FLD L2 DFB AC XSPEC SCMDLFHG - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_AC_XSPEC_SCMELFHG_SCMFLFHG: PSP FLD L2 DFB AC XSPEC SCMELFHG - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_DBM_DVAC: PSP FIELDS Level 2 DFB DBM Waveform Data - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_DBM_DVDC: PSP FIELDS Level 2 DFB DBM Waveform Data - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_DBM_SCM: PSP FIELDS Level 2 DFB DBM Waveform Data - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_DBM_VAC: PSP FIELDS Level 2 DFB DBM Waveform Data - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_DBM_VDC: PSP FIELDS Level 2 DFB DBM Waveform Data - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_DC_BPF_DV12HG: PSP FIELDS Level 2 DFB DC Bandpass Filter dV12hg - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_DC_BPF_DV34HG: PSP FIELDS Level 2 DFB DC Bandpass Filter dV34hg - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_DC_BPF_SCMULFHG: PSP FIELDS Level 2 DFB DC Bandpass Filter SCMulfhg - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_DC_BPF_SCMVLFHG: PSP FIELDS Level 2 DFB DC Bandpass Filter SCMvlfhg - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_DC_SPEC_DV12HG: psp fld l2 dfb dc spec dV12hg - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_DC_SPEC_SCMDLFHG: psp fld l2 dfb dc spec SCMdlfhg - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_DC_SPEC_SCMELFHG: psp fld l2 dfb dc spec SCMelfhg - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_DC_SPEC_SCMFLFHG: psp fld l2 dfb dc spec SCMflfhg - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_DC_SPEC_SCMULFHG: psp fld l2 dfb dc spec SCMulfhg - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_DC_SPEC_SCMVLFHG: psp fld l2 dfb dc spec SCMvlfhg - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_DC_SPEC_SCMWLFHG: psp fld l2 dfb dc spec SCMwlfhg - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_DC_XSPEC_SCMDLFHG_SCMELFHG: PSP FLD L2 DFB DC XSPEC SCMDLFHG - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_DC_XSPEC_SCMDLFHG_SCMFLFHG: PSP FLD L2 DFB DC XSPEC SCMDLFHG - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_DC_XSPEC_SCMELFHG_SCMFLFHG: PSP FLD L2 DFB DC XSPEC SCMELFHG - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_DC_XSPEC_SCMVLFHG_SCMWLFHG: PSP FLD L2 DFB DC XSPEC SCMVLFHG - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_WF_DVDC: PSP FIELDS Level 2 DFB Differential Voltage Waveform - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_WF_SCM: PSP FIELDS Level 2 DFB Search Coil Magnetometer Waveform - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_DFB_WF_VDC: PSP FIELDS Level 2 DFB Single Ended Antenna Voltage Waveform - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_F2_100BPS: PSP FIELDS F2-100bps Summary Telemetry - Stuart D. Bale (bale@berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_MAG_RTN: PSP FIELDS 4 samples per cycle cadence Fluxgate Magnetometer (MAG) data in RTN coordinates - Stuart D. Bale (bale@berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_MAG_RTN_1MIN: PSP FIELDS 1 minute cadence Fluxgate Magnetometer (MAG) data in RTN coordinates - Stuart D. Bale (bale@berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_MAG_SC: PSP FIELDS 4 samples per cycle cadence Fluxgate Magnetometer (MAG) data in SC coordinates - Stuart D. Bale (bale@berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_MAG_SC_1MIN: PSP FIELDS 1 minute cadence Fluxgate Magnetometer (MAG) data in SC coordinates - Stuart D. Bale (bale@berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_MAG_VSO: PSP FIELDS full cadence Fluxgate Magnetometer (MAG) data in VSO coordinates - Stuart D. Bale (bale@berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_RFS_BURST: PSP FIELDS RFS BURST Data - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_RFS_HFR: PSP FIELDS RFS HFR Data - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_RFS_LFR: PSP FIELDS RFS LFR Data - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L2_TDS_WF: PSP FIELDS TDS Wave-Form Burst Science Telemetry - Stuart D. Bale (bale@berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L3_DUST: PSP FIELDS Level 3 dust impact detection data - Stuart D. Bale (bale@berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L3_MERGED_SCAM_WF: PSP FIELDS Level 3 Merged Magnetic Field Waveform - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L3_RFS_HFR: PSP FIELDS RFS HFR Data - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L3_RFS_LFR: PSP FIELDS RFS LFR Data - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L3_RFS_LFR_QTN: PSP FIELDS Level 3 Electron Density Data from Radio Frequency Spectrometer (RFS) Low Frequency Receiver (LFR) Quasi-Thermal Noise (QTN) Spectroscopy - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_FLD_L3_SQTN_RFS_V1V2: Parker Solar Probe FIELDS Level 3 Simplified Quasi-Thermal Noise data, using the Radio Frequency Spectrometer spectra when connected to V1V2 dipole antenna - Stuart D. Bale (bale@ssl.berkeley.edu) (UC Berkeley Space Sciences Laboratory)

PSP_HELIO1DAY_POSITION: Position in heliocentric coordinates from SPDF Helioweb - Natalia Papitashvili (NASA/GSFC/SPDF)

PSP_ISOIS-EPIHI_L2-HET-RATES10: Parker Solar Probe ISOIS EPI-Hi Level 2 HET 10-second Rates - David McComas (Princeton University)

PSP_ISOIS-EPIHI_L2-HET-RATES300: Parker Solar Probe ISOIS EPI-Hi Level 2 HET 5-minute Rates - David McComas (Princeton University)

PSP_ISOIS-EPIHI_L2-HET-RATES3600: Parker Solar Probe ISOIS EPI-Hi Level 2 HET Hourly Rates - David McComas (Princeton University)

PSP_ISOIS-EPIHI_L2-HET-RATES60: Parker Solar Probe ISOIS EPI-Hi Level 2 HET 1-minute Rates - David McComas (Princeton University)

PSP_ISOIS-EPIHI_L2-LET1-RATES10: Parker Solar Probe ISOIS EPI-Hi Level 2 LET1 10-second Rates - David McComas (Princeton University)

PSP_ISOIS-EPIHI_L2-LET1-RATES300: Parker Solar Probe ISOIS EPI-Hi Level 2 LET1 5-minute Rates - David McComas (Princeton University)

PSP_ISOIS-EPIHI_L2-LET1-RATES3600: Parker Solar Probe ISOIS EPI-Hi Level 2 LET1 Hourly Rates - David McComas (Princeton University)

PSP_ISOIS-EPIHI_L2-LET1-RATES60: Parker Solar Probe ISOIS EPI-Hi Level 2 LET1 1-minute Rates - David McComas (Princeton University)

PSP_ISOIS-EPIHI_L2-LET2-RATES10: Parker Solar Probe ISOIS EPI-Hi Level 2 LET2 10-second Rates - David McComas (Princeton University)

PSP_ISOIS-EPIHI_L2-LET2-RATES300: Parker Solar Probe ISOIS EPI-Hi Level 2 LET2 5-minute Rates - David McComas (Princeton University)

PSP_ISOIS-EPIHI_L2-LET2-RATES3600: Parker Solar Probe ISOIS EPI-Hi Level 2 LET2 Hourly Rates - David McComas (Princeton University)

PSP_ISOIS-EPIHI_L2-LET2-RATES60: Parker Solar Probe ISOIS EPI-Hi Level 2 LET2 1-minute Rates - David McComas (Princeton University)

PSP_ISOIS-EPIHI_L2-SECOND-RATES: Parker Solar Probe ISOIS EPI-Hi Level 2 one-second Rates - David McComas (Princeton University)

PSP_ISOIS-EPILO_L2-IC: Parker Solar Probe ISOIS EPI-Lo Level 2 Ion Composition - David McComas (Princeton University)

PSP_ISOIS-EPILO_L2-PE: Parker Solar Probe ISOIS EPI-Lo Level 2 Particle Energy - David McComas (Princeton University)

PSP_ISOIS_L2-EPHEM: Parker Solar Probe ISOIS Level 2 ephem - David McComas (Princeton University)

PSP_ISOIS_L2-SUMMARY: Parker Solar Probe ISOIS level 2 summary - David McComas (Princeton University)

PSP_SWP_SPA_SF0_L2_16AX8DX32E: Electron Differential Energy Flux at each measured energy/deflector step and anode of the SPAN-Electron instrument - J. Kasper (Univ. of Michigan)

PSP_SWP_SPA_SF0_L3_PAD: Electron Pitch Angle Distribution for the SPAN-Electron instrument - J. Kasper (Univ. of Michigan)

PSP_SWP_SPA_SF1_L2_32E: Electron Differential Energy Flux at each measured energy step, and averaged over all deflection steps and anodes of the SPAN-Electron instrument - J. Kasper (Univ. of Michigan)

PSP_SWP_SPB_SF0_L2_16AX8DX32E: Electron Differential Energy Flux at each measured energy/deflector step and anode of the SPAN-Electron instrument - J. Kasper (Univ. of Michigan)

PSP_SWP_SPB_SF0_L3_PAD: Electron Pitch Angle Distribution for the SPAN-Electron instrument - J. Kasper (Univ. of Michigan)

PSP_SWP_SPB_SF1_L2_32E: Electron Differential Energy Flux at each measured energy step, and averaged over all deflection steps and anodes of the SPAN-Electron instrument - J. Kasper (Univ. of Michigan)

PSP_SWP_SPC_L2I: L2 charge flux distributions - Justin C. Kasper (University of Michigan)

PSP_SWP_SPC_L3I: Parker Solar Probe/SWEAP/SPC level 3 ion data - Justin C. Kasper (University of Michigan)

PSP_SWP_SPE_SF0_L3_PAD: Electron Pitch Angle Distribution for the SPAN-Electron instrument - J. Kasper (Univ. of Michigan)

PSP_SWP_SPI_SF00_L2_8DX32EX8A: Proton Differential Energy Flux at each measured energy/deflector step and anode of the SPAN-Ion instrument - J. Kasper (Univ. of Michigan)

PSP_SWP_SPI_SF00_L3_MOM: Partial moments of the Proton distribution function in the SPAN-Ion instrument, PSP spacecraft, and RTN coordinate systems. User should be aware that the full ion distribution is typically NOT in the FOV of the instrument. - J. Kasper (Univ. of Michigan)

PSP_SWP_SPI_SF00_L3_MOM_INST: Partial moments of the Proton distribution function in the instrument frame of reference. User should be aware that the full ion distribution is typically NOT in the FOV of the instrument. - J. Kasper (Univ. of Michigan)

PSP_SWP_SPI_SF01_L2_8DX32EX8A: Proton-contaminated Alpha Differential Energy Flux at each measured energy/deflector step and anode of the SPAN-Ion instrument - J. Kasper (Univ. of Michigan)

PSP_SWP_SPI_SF0A_L3_MOM: Partial moments of the Alpha distribution function in the SPAN-Ion instrument, PSP spacecraft, and RTN coordinate systems. User should be aware that the full ion distribution is typically NOT in the FOV of the instrument. - J. Kasper (Univ. of Michigan)

PSP_SWP_SPI_SF0A_L3_MOM_INST: Partial moments of the Alpha distribution function in the instrument frame of reference. User should be aware that the full ion distribution is typically NOT in the FOV of the instrument. - J. Kasper (Univ. of Michigan)

PHOBOS2_HELIO1DAY_POSITION (spase://NASA/NumericalData/Phobos2/HelioWeb/Ephemeris/P1D)

Description

No TEXT global attribute value.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PIONEER10_COHO1HR_MERGED_MAG_PLASMA doi:10.48322/dn2j-fn46

Description

Pioneer10 COHOweb connection
The main science objectives for the PIONEER interplanetary mission are as 
follows:
   search for the heliospheric boundary with interstellar space; 
   study the large-scale structure of the solar wind plasma and interplanetary
magnetic field within the heliosphere;
   investigate propagation of solar and galactic energetic particles in the
heliosphere;
   measure the radial gradient, spectra, and nuclear composition of the
anomalous cosmic rays from the solar wind termination shock;
   study acceleration of energetic particles by solar flare shocks and
corotating interaction regions within the heliosphere.
PI of magnetic field data: Dr. Edward J. Smith, NASA JPL.  PI of plasma data:
Dr. Aaron Barnes, Ames Research Center, NASA;  plasma data were provided by Dr.
P. Gazis, ARC. 
For the hourly resolution records, the PIONEER_10 directory contains hourly
averages of parameters for the interplanetary  magnetic field (1972-Mar-3 (63) -
1975-Nov-17 (321)), solar wind plasma (1972-Apr-18 (109) - 1995-Sep-07 (250)),
spacecraft trajectory coordinates (1972-Mar-3 (63) - 1995-Dec-31 (365)) and
Proton Fluxes (1972-Mar-15 - 1994-Nov-18)
Time Coverage of merged files: March 3, 1972 - December 31, 1995 
Pioneer-10 data have been reprocessed to ensure a uniformity of content and
coordinate systems relative to data from other deep-space missions:
   All spacecraft trajectory data were transformed to a Heliographic Inertial
(HGI) coordinate system.
   merging of trajectory coordinates, magnetic field data, and plasma data files
into a single annual file P10_YR.DAT, where YR is the year;
   Data gaps were filled with dummy numbers for the missing hours or entire days
to make all files of equal length.  The character Ə' is used to  fill all
fields for missing data according to their format, e.g. (9999.9) for a field
with the FORTRAN format F7.1. Note that format F7.1 below really means
(1X,F6.1),etc.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PIONEER10_HELIO1DAY_POSITION doi:10.48322/yzp2-cp45

Description

No TEXT global attribute value.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PIONEER10_MAG_1MIN_MAGNETIC_FIELD doi:10.48322/3np4-sz16

Description

This data set from the Pioneer 10 Helium Vector Magnetometer (HVM) consists of
one minute averages of vector components and scalar magnitudes of the
interplanetary magnetic field. The three components (Br, Bt, Bn) are given in
the RTN coordinate system and all magnetic fields are expressed in nanotelsa
units. The scalar magnitudes (B) are averages of higher resolution scalar
magnitudes. The time tag for each one-minute interval is the midpoint of the
averaging interval in SCET-UT (Spacecraft Event Time - UT). The averages were
originally calculated over one-minute intervals in Ground Received Time, and the
midpoints have been converted to SCET-UT. The file P10_LIGHTTIME contains daily
values for the one-way light-time delay. No records are written for data gaps.
Most files cover 28 or 35 days, but there are a number of shorter files,
particularly at year boundaries. Data for the Jupiter encounter, days 329-349 of
1973, are not included. The RTN system is fixed to the sun-spacecraft line and
aligned with the solar heliographic equator. The R axis is the radial direction
to the spacecraft, the T axis is the cross product of the solar rotation axis
and the R axis, and N is the cross product of R and T.  The file P10HVM_15M.SFD
provides a detailed description of the Pioneer spacecraft, the HVM experiment,
and the data. This ASCII document is written in Standard Formatted Data Unit
(SFDU) format as part of NSSDC data set 72-012A-01I for 15-minute averaged data
covering 1972-03-03 to 1975-11-17. 
Data Set Files: P10HVMMN_FMT.txt     - this document (ASCII) P10HVM_15M.SFD     
 - SFDU metadata extract from Pioneer 10 HVM 15-min. data set Myyddd.asc        
  - 1-minute data files from Pioneer 10 HVM starting at date yyddd
P10_LIGHTTIME.asc    - data file with one-way light-time delays (ASCII) 
Related Information and Data: Further details on the spacecraft, experiment,
data sets at NSSDC, and related WWW sites can be found on the Pioneer 10/11
flight project page under  http://nssdc.gsfc.nasa.gov/space/ Hour averages of 
the interplanetary solar wind data from, and hourly heliocentric coordinates of,
Pioneer 10/11 and other interplanetary spacecraft may be also be accessed and
plotted on-line through the COHOWeb service based at the same WWW site as above.
Pioneer data on NDADS (NASA"s Data Archive and Distribution Service) may be
located on the WWW via the SPyCAT service at the above URL or an e-mail message
to ARMS (Automated Retrieval Mail System) at archives@ndadsa.gsfc.nasa.gov with
"HOLDINGS" on the subject line.   
Acknowledgement: Use of these data in publications should be accompanied at
minimum by acknowledgements of the National Space Science Data Center and the
responsible Principal Investigator defined in the experiment documentation
provided here. Citation of NSSDC"s Coordinated Heliospheric Observations (COHO)
data base would also be appreciated, so that other potential users will be made
aware of this service.   
Data Set Coverage (yyyy-mm-dd): 1972-03-03 to 1975-11-17 
Data Set Contact: Joyce Wolf, NASA JPL

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PIONEER11_COHO1HR_MERGED_MAG_PLASMA doi:10.48322/vb0s-0w02

Description

Pioneer11 COHOweb connection
The main science objectives for the PIONEER interplanetary mission are as 
follows:
   search for the heliospheric boundary with interstellar space; 
   study the large-scale structure of the solar wind plasma and interplanetary
magnetic field within the heliosphere;
   investigate propagation of solar and galactic energetic particles in the
heliosphere;
   measure the radial gradient, spectra, and nuclear composition of the
anomalous cosmic rays from the solar wind termination shock;
   study acceleration of energetic particles by solar flare shocks and
corotating interaction regions within the heliosphere.
PI of magnetic field data: Dr. Edward J. Smith, NASA JPL.  PI of plasma data:
Dr. Aaron Barnes, Ames Research Center, NASA;  plasma data were provided by Dr.
P. Gazis, ARC. 
For the hourly resolution records, the PIONEER_11 directory contains hourly
averages of parameters for the interplanetary  magnetic field (1973-Apr-6 -
1992-Aug-1, solar wind plasma (1973-Apr-21  - 1992-May-30), Proton Fluxes
(1972-Mar-15 - 1994-Nov-18), and spacecraft trajectory coordinates (1973-Apr-6 
- 1992-Aug-1). 
Time Coverage of merged files: April 6, 1973 - August 1, 1992 
Pioneer-11 data have been reprocessed to ensure a uniformity of content and
coordinate systems relative to data from other deep-space missions:
   All spacecraft trajectory data were transformed to a Heliographic Inertial
(HGI) coordinate system.
   merging of trajectory coordinates, magnetic field data, and plasma data files
into a single annual file P11_YR.DAT, where YR is the year;
   Data gaps were filled with dummy numbers for the missing hours or entire days
to make all files of equal length.  The character Ə' is used to  fill all
fields for missing data according to their format, e.g. (9999.9) for a field
with the FORTRAN format F7.1. Note that format F7.1 below really means
(1X,F6.1),etc.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PIONEER11_HELIO1DAY_POSITION doi:10.48322/3dc9-j157

Description

No TEXT global attribute value.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PIONEER6_R0_MAGPLASMA

Description

Pioneer6 COHOweb connection

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PIONEER7_R0_MAGPLASMA

Description

Pioneer7 COHOweb connection

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PIONEERVENUS_COHO1HR_MERGED_MAG_PLASMA doi:10.48322/f172-0b94

Description

PIONEER VENUS ORBITER (PVO) was the first orbiter mission designed to conduct a
comprehensive and long term investigation of the planet Venus.  PVO measured the
detailed structure of the upper atmosphere and ionosphere of Venus and
investigated the interaction of the solar wind magnetic field and plasma with
the venusian ionosphere. Over the years 1978-1992 PVO provided nearly continuous
measurements of the solar wind from its highly eccentric orbit around Venus.
PI of magnetic field data: Dr. T. C. Russell, UCLA.
PI of plasma data: Dr. Aaron Barnes, Ames Research Center, NASA. plasma data
were provided by Dr. P. Gazis, Ames,NASA.
For the hourly resolution records, thePVO directory contains files with hourly
averages for selected parameters of the interplanetary magnetic field
(1978-12-05 - 1988-08-07) solar wind plasma (1978-12-05 - 1992-10-08) and the
spacecraft trajectory (1978-12-05 - 1992-12-31) in RTN, and in Venus-centered
(1978-12-05 - 1988-08-07) coordinates.  These were data taken from time
intervals when the spacecraft was outside the bow shock of the venusian
ionosphere and in the solar wind.
Time Coverage of merged files: 78-12-05 - 92-12-31.
PVO data have been reprocessed to ensure a uniformity of content and coordinate
systems relative to data from other deep-space missions:
- All spacecraft trajectory data were transformed to a Heliographic Inertial
(HGI) coordinate system.
- calculation of RTN components of interplanetary magnetic field from VSO
coordinates.
- merging of trajectory coordinates, magnetic field data, and plasma data files
into a single annual file PVO_YR.ascii, where YR is the year;
- Data gaps were filled with dummy numbers for the missing hours or entire days
to make all files of equal length.  The character \Ə\' is used to fill all
fields for missing data according to their format, e.g. \' 9999.9\' for a field
with the FORTRAN format F7.1. Note that format F7.1 below really means
(1X,F6.1),etc.
The Heliographic Inertial (HGI) coordinates are Sun-centered and inertially
fixed with respect to an X-axis  directed along the intersection line of the
ecliptic and solar equatorial planes.  The solar equator plane is inclined at
7.25 degrees from the ecliptic. This direction was towards ecliptic longitude of
74.36 degrees on 1 January 1900 at 1200 UT; because of precession of the
celestial equator, this longitude increases by 1.4 degrees/century. The Z axis
is directed perpendicular and northward from the solar equator, and the Y-axis
completes the right-handed set.  This system differs from the usual heliographic
coordinates  (e.g. Carrington longitudes) which are fixed in the frame of the
rotating Sun.
The RTN system is fixed at a spacecraft (or the planet). The R axis is directed
radially away from  the Sun, the T axis is the cross product of the solar
rotation axis and the R axis, and the N axis is the cross product of R and T. 
At zero Heliographic Latitude when the spacecraft is in the solar equatorial
plane the N and solar rotation axes are parallel.
Venus Solar Orbital (VSO) coordinates are defined with respect to the orbital
plane of Venus which is tilted about two degrees from the Ecliptic.  The VSO
system is Venus-centered with the X axis towards the Sun, the Z axis northward
and perpendicular to the orbital plane, and the Y axis completing the right hand
system.
Acknowledgement: Hour averages of the interplanetary solar wind data from, and
hourly heliocentric coordinates of, PVO and other interplanetary spacecraft may
be also be accessed and plotted on-line through the COHOWeb service
http://cohoweb.gsfc.nasa.gov/

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PIONEERVENUS_MERGED_SOLAR-WIND_10M doi:10.48322/ey7t-8763

Description

Pioneer Venus Orbiter (PVO) was the first orbiter mission designed to conduct a
comprehensive and long term investigation of the planet Venus.  PVO measured the
detailed structure of the upper atmosphere and ionosphere of Venus and
investigated the interaction of the solar wind with the Venusian ionosphere.
Over the years 1978-1992 PVO provided nearly continuous measurements of the
solar wind from its highly eccentric orbit around Venus.
PI of magnetic field data: Dr. C.T. Russell, UCLA.
PI of plasma data: Dr. Aaron Barnes, Ames Research Center, NASA.
The 10-min data include 10-minute averages for selected parameters of the
interplanetary magnetic field, solar wind plasma, and spacecraft trajectory. The
data were taken when the spacecraft was outside the bow shock of the Venusian
ionosphere and was in the solar wind.
Time coverage of merged data: 78-12-06 - 88-08-07.
PVO data were converted to CDF based on the  flatfiles from UCLA.
Venus Solar Orbital (VSO) coordinates are defined with respect to the orbital
plane of Venus which is tilted about two degrees from the Ecliptic.  The VSO
system is Venus-centered with the X axis towards the Sun, the Z axis northward
and perpendicular to the orbital plane, and the Y axis completing the right hand
system.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PLUTO_HELIO1DAY_POSITION (spase://NASA/NumericalData/Planet/Pluto/HelioWeb/Ephemeris/P1D)

Description

No TEXT global attribute value.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PMC-TURBO_L1_BOLIDE_VBC

Description

Instrument description in https://doi.org/10.5194/amt-13-5681-2020

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

POLAR_HYDRA_MOMENTS-14SEC doi:10.48322/gvf7-x480

Description

Reference: HYDRA is a 3-Dimensional Electron and Ion Hot Plasma Instrument
for the Polar Spacecraft of the GGS Mission, J. Scudder et al., 
Space Sci. Rev., 71,459-495, Feb. 1995. http://www-st.physics.uiowa.edu  
This data set contains survey electron and proton moments for density, 
bulk velocity (GSM), temperature: parallel, perpendicular, at 
13.8-second resolution as determined (0-20keV). 
Higher quality data products may be available from the P.I.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_10MINATT_EFI doi:10.48322/a4sb-1d04

Description

Important Warning: The data described below is meant for archival purposes.  It
should not be considered as highly accurate data.  For example, accurate data
requires a correction in the form of an offset to the Sunward component of the
electric field.  A constant offset of 1.2 mV/m has been used for all the data,
this being an approximate average value.  In fact, however, the offset varies
with time, and must be determined by analysis of the particular time of
interest.  Users of this data desiring more information should get in touch with
Dr. Forrest Mozer, at the Space Sciences Laboratory, University of California,
Berkeley.
The electric field data is at spin period time resolution. This means that there
is 1 data point about every 6 seconds. However, it should be noted that there
can be longer intervals between data points, due to missing data.  Data gaps are
not filled in.
The components of the electric field are given in a coordinate system designated
as Despun Spacecraft Coordinates , or DSC.  This is a coordinate system for a
rotating spacecraft that is in an orbit near the Earth.  DSC is defined by the
spacecraft's spin plane and spin axis. However, as the Despun part of the name
suggests, the coordinate axes do not participate of the spacecraft's rotation.
The X and Y axes are on the spacecraft's spin plane; the Z axis is along the
spacecraft's spin axis.  The positive X, Y, and Z axes form an orthogonal,
right-handed coordinate system.  The positive Z axis points in the same
direction as the spacecraft's angular momentum (or spin or attitude) vector. 
The positive X axis points in the direction on the spin plane that is closest to
the direction towards the Sun.  In other words, the positive X axis points in
the direction of the projection on the spin plane of the vector from the
spacecraft to the Sun.  The positive Y axis is determined by the requirement
that the DSC system (X, Y, Z) be an orthogonal right-handed system. It follows
that the positive Y axis points in the direction on the spin plane that is 90
degrees ahead of the positive X axis (in the sense of the spacecraft's
rotation). 
The electric field data included in these files consists of 2 electric field
components on the spin plane.  The original data used is V34L, which typically
has a time resolution of about 40 data points per second.  A least-squares spin
fit of V34L is performed, and the spin fit coefficients provide the spin plane
components of the spin period electric field. 
Time is a real double-precision quantity.  The units for the time are seconds. 
The time is time elapsed since the FAST Mission Epoch, which is May 24, 1968
(1968/05/24) at 00:00:00 UT.  Each time tag indicates the mid-point of the time
interval for the corresponding spin period.  Data gaps are not filled; each time
tag corresponds to an actual data point.  
X, Y, and Z are the 3 components of the attitude vector in the GSE coordinate
system (note that all 3 X, Y, and Z components are present, despite the X in the
file name).

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_6SECEDSC_EFI doi:10.48322/vkpj-6n73

Description

Important Warning: The data described below is meant for archival purposes.  It
should not be considered as highly accurate data.  For example, accurate data
requires a correction in the form of an offset to the Sunward component of the
electric field.  A constant offset of 1.2 mV/m has been used for all the data,
this being an approximate average value.  In fact, however, the offset varies
with time, and must be determined by analysis of the particular time of
interest.  Users of this data desiring more information should get in touch with
Dr. Forrest Mozer, at the Space Sciences Laboratory, University of California,
Berkeley.
The electric field data is at spin period time resolution. This means that there
is 1 data point about every 6 seconds. However, it should be noted that there
can be longer intervals between data points, due to missing data.  Data gaps are
not filled in.
The components of the electric field are given in a coordinate system designated
as Despun Spacecraft Coordinates , or DSC.  This is a coordinate system for a
rotating spacecraft that is in an orbit near the Earth.  DSC is defined by the
spacecraft's spin plane and spin axis. However, as the Despun part of the name
suggests, the coordinate axes do not participate of the spacecraft's rotation.
The X and Y axes are on the spacecraft's spin plane; the Z axis is along the
spacecraft's spin axis.  The positive X, Y, and Z axes form an orthogonal,
right-handed coordinate system.  The positive Z axis points in the same
direction as the spacecraft's angular momentum (or spin or attitude) vector. 
The positive X axis points in the direction on the spin plane that is closest to
the direction towards the Sun.  In other words, the positive X axis points in
the direction of the projection on the spin plane of the vector from the
spacecraft to the Sun.  The positive Y axis is determined by the requirement
that the DSC system (X, Y, Z) be an orthogonal right-handed system. It follows
that the positive Y axis points in the direction on the spin plane that is 90
degrees ahead of the positive X axis (in the sense of the spacecraft's
rotation). 
The electric field data included in these files consists of 2 electric field
components on the spin plane.  The original data used is V34L, which typically
has a time resolution of about 40 data points per second.  A least-squares spin
fit of V34L is performed, and the spin fit coefficients provide the spin plane
components of the spin period electric field. 
Time is a real double-precision quantity.  The units for the time are seconds. 
The time is time elapsed since the FAST Mission Epoch, which is May 24, 1968
(1968/05/24) at 00:00:00 UT.  Each time tag indicates the mid-point of the time
interval for the corresponding spin period.  Data gaps are not filled; each time
tag corresponds to an actual data point.  
E_X and E_Y are the X and Y components of the electric field in the DSC
coordinate system (note that both the X and the Y component are present, despite
the X in the file name).  E_X and E_Y are real single-precision quantities. The
units for the electric field components are mV/m.  There are no missing data
values; each data point value corresponds to an actual data point.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_6SECPOTLDENS_EFI doi:10.48322/ttha-dc31

Description

Important Warning: The data described below is meant for archival purposes.  It
should not be considered as highly accurate data.  For example, accurate data
requires a correction in the form of an offset to the Sunward component of the
electric field.  A constant offset of 1.2 mV/m has been used for all the data,
this being an approximate average value.  In fact, however, the offset varies
with time, and must be determined by analysis of the particular time of
interest.  Users of this data desiring more information should get in touch with
Dr. Forrest Mozer, at the Space Sciences Laboratory, University of California,
Berkeley.
The electric field data is at spin period time resolution. This means that there
is 1 data point about every 6 seconds. However, it should be noted that there
can be longer intervals between data points, due to missing data.  Data gaps are
not filled in.
The components of the electric field are given in a coordinate system designated
as Despun Spacecraft Coordinates , or DSC.  This is a coordinate system for a
rotating spacecraft that is in an orbit near the Earth.  DSC is defined by the
spacecraft's spin plane and spin axis. However, as the Despun part of the name
suggests, the coordinate axes do not participate of the spacecraft's rotation.
The X and Y axes are on the spacecraft's spin plane; the Z axis is along the
spacecraft's spin axis.  The positive X, Y, and Z axes form an orthogonal,
right-handed coordinate system.  The positive Z axis points in the same
direction as the spacecraft's angular momentum (or spin or attitude) vector. 
The positive X axis points in the direction on the spin plane that is closest to
the direction towards the Sun.  In other words, the positive X axis points in
the direction of the projection on the spin plane of the vector from the
spacecraft to the Sun.  The positive Y axis is determined by the requirement
that the DSC system (X, Y, Z) be an orthogonal right-handed system. It follows
that the positive Y axis points in the direction on the spin plane that is 90
degrees ahead of the positive X axis (in the sense of the spacecraft's
rotation). 
The electric field data included in these files consists of 2 electric field
components on the spin plane.  The original data used is V34L, which typically
has a time resolution of about 40 data points per second.  A least-squares spin
fit of V34L is performed, and the spin fit coefficients provide the spin plane
components of the spin period electric field. 
Time is a real double-precision quantity.  The units for the time are seconds. 
The time is time elapsed since the FAST Mission Epoch, which is May 24, 1968
(1968/05/24) at 00:00:00 UT.  Each time tag indicates the mid-point of the time
interval for the corresponding spin period.  Data gaps are not filled; each time
tag corresponds to an actual data point.  
The original data used is V1L, V2L, etc., which typically have a time resolution
of about 1 data point per 0.4 seconds. The spacecraft potentials come from spin
period averages of the voltages V1L, V2L, etc.  The spacecraft potential
S_C_Pot12 is defined as follows: S_C_Pot12 = (V1 + V2) / 2  The spacecraft
potential S_C_Pot34 is defined analogously.  V1, V2, etc. stand for V1L, V2L,
etc., respectively.  One additional spacecraft potential, S_C_Pot1234, is
defined as follows: S_C_Pot1234 = (S_C_Pot12 + S_C_Pot34) / 2
The plasma density n is obtained as a function of the spacecraft potential. The
function is a power function, provided by Dr. Jack Scudder (University of Iowa).
 It comes from a fit to the POLAR Hydra particle data.  The function was
determined using data for 2001/04/01. The validity of the function for dates far
from the date above has not been checked.  Values above 75 are regarded as
unphysical and re-assigned a NULL value. n will be in units of cm^(-3), i.e.,
number of charges per cubic centimeter.

Data Variable Descriptions

Spacecraft potential [S_C_Pot]

plasma density [n]

Values above 75 are regarded as unphysical and re-assigned a NULL value.

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_AT_DEF doi:10.48322/r4rq-sq24

Description

TBS

Modification History

6/13/91 - Original Implementation
9/18/91 - Modified for new attitude file format changes.  ICCR 881
2/11/92 - Used the variable name TIME and type CDF_INT4 and size 3 instead of 
EPOCH, CDF_EPOCH and 1 for the time tags.  CCR 490
6/1/92 - Added global attributes TITLE, PROJECT, DISCIPLINE, SOURCE_NAME, 
DATA_VERSION, and MODS; added variable attributes VALIDMIN, VALIDMAX, 
LABL_PTR_1, and MONOTON; added variables EPOCH and LABEL_TIME; 
changed variable name TIME to TIME_PB5.  CCR 1066
11/07/92 - use cdf variable Epoch and Time_PB5
6/8/93 - Added global attributes ADID_ref and Logical_file_id.  CCR 1092
7/5/94 - CCR ISTP 1852, updated CDHF skeleton to CDF standards - JT
9/20/94 - Added global attributes GCI_RA_ERR and GCI_DECL_ERR.  CCR 1932
11/7/94 - Merged CCR 1852 changes and corrected errors 
made in CCR 1852.  ICCR 1884
12/7/94 - Modified MODS and LABLAXIS to follow ISTP standards.  ICCR 1885

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_AT_PRE (spase://NASA/NumericalData/POLAR/Ephemeris/Attitude/PT10M)

Description

TBS

Modification History

6/13/91 - Original Implementation
9/18/91 - Modified for new attitude file format changes.  ICCR 881
2/11/92 - Used the variable name TIME and type CDF_INT4 and size 3 instead of 
EPOCH, CDF_EPOCH and 1 for the time tags.  CCR 490
6/1/92 - Added global attributes TITLE, PROJECT, DISCIPLINE, SOURCE_NAME, 
DATA_VERSION, and MODS; added variable attributes VALIDMIN, VALIDMAX, 
LABL_PTR_1, and MONOTON; added variables EPOCH and LABEL_TIME; 
changed variable name TIME to TIME_PB5.  CCR 1066
11/07/92 - use cdf variable Epoch and Time_PB5
6/8/93 - Added global attributes ADID_ref and Logical_file_id.  CCR 1092
7/5/94 - CCR ISTP 1852, updated CDHF skeleton to CDF standards - JT
9/20/94 - Added global attributes GCI_RA_ERR and GCI_DECL_ERR.  CCR 1932
11/7/94 - Merged CCR 1852 changes and corrected errors 
made in CCR 1852.  ICCR 1884
12/7/94 - Modified MODS and LABLAXIS to follow ISTP standards.  ICCR 1885

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_EJ_VIS

Description

Instrument functional description:
   The VIS is a set of three low-light-level cameras.  Two of these
   cameras share primary and some secondary optics and are designed to
   provide images of the nighttime auroral oval at visible wavelengths.
   A third camera is used to monitor the directions of the fields-of-view
   of the auroral cameras with respect to the sunlit Earth and return
   global images of the auroral oval at ultraviolet wavelengths.  The
   VIS instrumentation produces an auroral image of 256 x 256 pixels
   approximately every 24 seconds dependent on the integration time and
   filter selected.  The fields-of-view of the two nighttime auroral
   cameras are 5.6 x 6.3 degrees and 2.8 x 3.3 degrees for the low and
   medium resolution cameras, respectively.  One or more Earth camera
   images of 256 x 256 pixels are produced every five minutes, depending
   on the commanded mode.  The field-of-view of the Earth camera is
   approximately 20 x 20 degrees.
Reference:
   Frank, L. A., J. B. Sigwarth, J. D. Craven, J. P. Cravens, J. S. Dolan,
       M. R. Dvorsky, J. D. Harvey, P. K. Hardebeck, and D. Muller,
       'The Visible Imaging System (VIS) for the Polar Spacecraft',
       Space Science Review, vol. 71, pp. 297-328, 1995.
[Note to first-time users:  The first four variables are of primary
interest.  The displayable 256 x 256 image array is in variable 3.  The
correct orien- tation of a displayed image is explained in the
description of variable 3 below.]
Data set description:
   The VIS Earth camera data set comprises all Earth camera images for
the selected time period.  EJ-ER type files have images that have been
processed to remove the effects of penetrating radiation.  In addition,
the images have been flat-fielded and fixed pattern noise has been
removed.  Image pixels are median filtered with the images immediately
before and after in time.  The displayable image counts are in variable
3.  Some coordinate information is included for viewer orientation.
Coordinates are calculated for a grid of 18 x 18 points corresponding to
one pixel out of every 15 x 15 pixel block.  In addition, a rotation
matrix and a table of distortion-correcting look direction unit vectors
are provided for the purpose of calculating coordinates for every pixel.
See the description of variables 14 and 15 below.  To facilitate viewing
of the images, a mapping of pixel value to a recommended color table
based on the characteristics of the selected filter will be included with
each image.  See the description of variables 19, 20, and 21 below.  A
relative intensity scale is provided by the uncompressed count table of
variable 24.  Approximate intensity levels in kiloRayleighs are given in
the intensity table of variable 25.  Information on the availability of
more precisely calibrated intensities can be found on the VIS website at
URL .http://eiger.physics.uiowa.edu/~vis/software/. 
Variable descriptions:
   1,2. Center time
       The time assigned to an image is the center time of the integration
       period within a resolution of 50 milliseconds.
   3. Image counts
       Image pixel counts range from 0 to 255.  They are stored in a two-
       dimensional 256 x 256 byte array.  Images from the Earth camera
       (sensor 0) are conventionally displayed with row 1 at the top, row 256
       at the bottom, column 1 on the left, and column 256 on the right.  The
       conventional image display for the low resolution camera (sensor 1) is
       rotated 180 degrees so that the row 1-column 1 pixel is at the lower
       right corner and the row 256-column 256 pixel is at the upper left
       corner.  When displayed in this manner, the spacecraft spin axis is
       oriented to the right in the display, the X component is defined as
       the center of the image look direction, and the Y component is the
   4. Sensor number
       0 = Earth camera,
       1 = low resolution camera,
       2 = medium resolution camera.
   5. Half integration time
       This is half the length of the integration period for the image,
       measured in milliseconds.
   6. Filter
       Twelve filters are available for visible imaging; the filter number,
       1-12, is given here.  Ultra-violet imaging is done with one filter
       only, designated here as filter number 0.  In addition, the peak
       wavelength in Angstroms is given for the selected filter.
   7. Presumed altitude of emissions
       The presumed altitude of the emissions seen in the image varies
       with the characteristics of the filter used.
   8. Platform pitch angle
       This is the platform pointing angle of rotation around the spin
       axis, measured from nadir.
 9,10. Geographic coordinates
       Geographic north latitude and east longitude are provided for the
       pixels at these image array locations: every 15th row starting
       with row 1 and ending with row 256, and every 15th column starting
       with column 1 and ending with column 256, for a total of
       18 x 18 coordinate pairs.
11,12. Spacecraft position and velocity vectors, GCI
       The spacecraft position vector and velocity vector in GCI
       coordinates are for the image center time as given in variables
       1 and 2.
  13. Spacecraft spin axis unit vector, GCI
14,15. Image-to-GCI rotation matrix and look direction vector table
       The rotation matrix may be used with the look direction vector table to
       obtain pointing vectors in GCI coordinates for each pixel.  The
       resulting vectors may be used to calculate coordinates for the observed
       positions of the pixels.  Software for this purpose is available at URL
       .http://eiger.physics.uiowa.edu/~vis/software/.  The general method 
       used is described below.
       In the image coordinate system, the X axis is the center line-of-sight
       or look direction; the Y axis is the cross product of the spin axis an
       the X axis; and the Z axis is the cross product of the X axis and the
       Y axis.  When the display orientation conventions in the variable 3
       description are applied, the low resolution camera image is rotated so
       that both Earth camera and low resolution camera images are displayed
       with Y axis pointing up and Z axis pointing toward the right.
       To obtain the coordinates of the observed position of a pixel,
       calculate the intersection of the line-of-sight with the surface
       of an oblately spheroidal Earth at the altitude given as
       variable 7.  The equation of the spheroid is
           X**2/(A+ALT)**2 + Y**2/(A+ALT)**2 + Z**2/(B+ALT)**2 = 1
           where A is the Earth radius at the equator,
                 B is the Earth radius at the pole, and
                 ALT is the given altitude.
       The line-of-sight equations are
           (X-SCX)/DX = (Y-SCY)/DY = (Z-SCZ)/DZ
           where (SCX,SCY,SCZ) is the spacecraft position vector GCI, and
                   (DX,DY,DZ)  is the look direction unit vector GCI.
       Solve the line-of-sight equations for two variables in terms
       of the third; substitute into the spheroid equation; and use the
       quadratic formula to solve for the third variable.  Select
       the solution point closer to the spacecraft.
  16. Zenith angle of center line-of-sight at presumed altitude
       This is the angle between the geocentric vector through the
       observed point, assuming the altitude given as variable 7,
       and the reverse of the image center line-of-sight vector.
  17. Sun position unit vector, GCI
  18. Solar zenith angle at observed point of center line-of-sight
       This is the angle of the sun from zenith at the observed point
       of the center line-of-sight, assuming the altitude given as
       variable 7.
  19. RGB color table
       This is the recommended color table to be used with the
       limits given in variables 20 and 21.
20,21. Low and high color mapping limits
       The low and high color limits are recommended for remapping
       the color table entries, as follows:
           For pixel values less than the low limit, use the color
               at table position 1.
       assignments:
               and less than or equal to the high limit, use the color
               at table position (pix-low)/(high-low) x 255 + 1.
           For pixel values greater than the high limit, use the color
               at table position 256.
  22. Data quality flag
       The data quality word has bits set to 1 when the listed
       conditions are true.  Bit #31 is the most significant bit in the
       word, and it will not be used as a flag.  These are the bit
           bit 0 - image data frame sync error
           bit 1 - image data frame counters error
           bit 2 - image data fill frame flag.
  23. Post gap flag
       The post gap flag has these possible values:
           0 - no gap occurred immediately prior to this record,
           1 - the gap occurred because the instrument was not in
                 a mode that allowed for the production of images for the
                 selected sensor,
           2 - the gap occurred because level zero data were missing,
           3 - the gap occurred because level zero data were too
                 noisy to extract images.
  24. Expanded count table
       The image pixel counts are quasi-logarithmically compressed to the
       range 0-255.  This table gives the average of the uncompressed range
       for each compressed count value.  Table entries 1-256 correspond to
       compressed counts 0-255 respectively.
  25. Intensity table
       Approximate intensity levels in kiloRayleighs are given for each
       compressed count value.  Table entries 1-256 correspond to compressed
       counts 0-255 respectively.  Information on the availability of more
       precisely calibrated intensities can be found on the VIS website at
       URL .http://eiger.physics.uiowa.edu/~vis/software/. 
Supporting software:
   Supporting software is available on the VIS website at the URL
   .http://eiger.physics.uiowa.edu/~vis/software/.  Included is an IDL 
   program that displays the images with the recommended color bar and
   provides approximate intensities and coordinate data for each pixel.

Modification History

Initial development
Updated TEXT section bug
Updated some variables
Added an ADID number, same as K1

Data Variable Descriptions

Presumed emission altitude (also quickly shows times when images are available). [AltF]

Earth Camera UV Images (quasi-log cnts), small format display with click-expand (~1 min. res.) [Image_Counts]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> Larger format display with click-expand, no geographic registration. [Image_CountsF]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) With geographic map overlay [Mapped_ImageO]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> [DO NOT USE: UNDER-DEVELOPMENT] Test Display [Mapped_Image]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Azimuthal projection to geographic (fixed sun orientation) [Mapped_ImageP]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Azimuthal projection to magnetic LT and invariant lat [Mapped_ImageM]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

(USE SHORT TIME SPANS) Movie display of images, no geographic registration. [Movie_Image]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) With geographic grid overlay [Mapped_MovieO]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Azimuthal projection to geographic (fixed sun orientation) [Mapped_MovieP]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Azimuthal projection to magnetic LT and invariant lat [Mapped_MovieM]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

Earth Camera UV Images (kRay), small format display with click-expand (~1 min. res.) [IImage_Counts]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> Larger format display with click-expand, no geographic registration. [IImage_CountsF]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) With geographic grid overlay [Mapped_IImageO]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Azimuthal projection to geographic (fixed sun orientation) [Mapped_IImageP]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Azimuthal projection to magnetic LT and invariant lat [Mapped_IImageM]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

(USE SHORT TIME SPANS) Movie display of images, no geographic registration. [Movie_IImage]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) With geographic grid overlay [Mapped_IMovieO]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Azimuthal projection to geographic (fixed sun orientation) [Mapped_IMovieP]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Azimuthal projection to magnetic LT and invariant lat [Mapped_IMovieM]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

Sensor number: 0=Earth Camera,1=Low Resolution Camera,2=Medium Resolution Camera [Sensor]

Platform pointing angle from nadir [PPitch]

Platform angle of rotation around spin axis, measured from nadir in tenths of
degrees

GCI position vector of Polar spacecraft in kilometers. [SC_Pos_GCI]

GCI velocity vector of Polar spacecraft in km/sec. [SC_Vel_GCI]

GCI spin axis unit vector of Polar spacecraft. [SC_SpinV_GCI]

Image header bytes [Headers]

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_H0_CAM doi:10.48322/bdjc-7g81

Description

No TEXT global attribute value.

Modification History

CDF Master created 3/21/03

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_H0_HYD doi:10.48322/rpbf-wd36

Description

Reference: HYDRA is a 3-Dimensional Electron and Ion Hot Plasma Instrument
for the Polar Spacecraft of the GGS Mission, J. Scudder et al., 
Space Sci. Rev., 71,459-495, Feb. 1995. http://www-st.physics.uiowa.edu  
This data set contains the differential electron and proton 
omnidirectional fluxes per unit solid angle vs energy, 
at 13.8-second resolution.  Multiply the given value by 4 pi 
to obtain the total omnidirectional differential energy flux.
There are 29 energy channels from 12.5 ev to 18.3 keV.
HYDRA is composed of two boxes, each housing 6 detectors.
A separate stepping power supply is used for each box.
The values of these steps are designed to be interlaced.
Therefore, the energies designated in this file are 
interpolated between the values of the two power supplies.
Stepping modes may also vary the number and range of steps 
during the mission.  To accommodate these changes an 
interpolation is done from the steps for a particular mode 
to the common energy values listed in ENERGY_ELE and ENERGY_ION.

Modification History

Generated March 26, 2003.

Data Variable Descriptions

Electron Differential Energy Flux [ELECTRON_DIFFERENTIAL_ENERGY_FLUX]

Multiply the given value by 4 pi to obtain the total omnidirectional
differential energy flux.

Ion Differential Energy Flux [ION_DIFFERENTIAL_ENERGY_FLUX]

Multiply the given value by 4 pi to obtain the total omnidirectional
differential energy flux.

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_H0_PWI doi:10.48322/879x-0r04

Description

Reference:..Gurnett, D.A. et al, The Polar plasma wave instrument, Space Science
Reviews, Vol. 71, pp. 597-622, 1995.GURNETT@IOWAVE.physics.uiowa.edu
Note:..The electron cyclotron frequencies are derived from the following:  Fce =
0.028 kHz*B, where B is the magnitude of the ambient magnetic field measured in
nT.  All frequencies are converted to Hz.
There are 20 MCA E frequency bands, logarithmically spaced and 14 MCA B
frequency bands, logarithmically spaced.

Modification History

Created Dec 1997

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_H0_TID doi:10.48322/zkvp-5751

Description

TIDE data for dates 28-Mar-1996 to 30-Sep-1996 are mass resolved. 
TIDE data between 01-Oct-1996 and 07-Dec-1996 are not valid.

Modification History

Skeleton table version 1 created 08/10/98.
Skeleton table version 2 created 10/16/00.
Skeleton table version 3 created 07/12/06.

Data Variable Descriptions

H+ Ion density, only available before 01-Oct-1996. [hp_den]

Only available before 01-Oct-1996

H+ Ion Plasma Velocity, Field Aligned, available before 01-Oct-1996 [hp_vel]

Available before 01-Oct-1996 only,for energy, spin angle, and polar angle
calculation see moments_lim.

H+ Ion Temperature, Parallel and Perendicular to the Magnetic Field, available before 01-Oct-1996. [hp_temp]

Only available before 01-Oct-1996.  Direction of magnetic field obtained from
onboard values. See moments_lim for energy, spin angle, and polar angle
calculation limits.

H+ Energy Spectrogram. Only available before 01-Oct-1996. [hp_en]

Flux values summed or averaged over spin and polar angles.  See spect_lim for
sum/avg limits, see sum_avg to determine which one was used.

H+ Spin Angle Spectrogram. Only available before 01-Oct-1996. [hp_spin]

Flux values summed or averaged over energy and polar angle.  See spect_lim for
for sum/avg limits, see sum_avg to determine which one was used.

H+ Polar Angle Spectrogram. Only available before 01-Oct-1996. [hp_polar]

Flux values summed or averaged over energy and spin angle.  See spect_lim for
for sum/avg limits, see sum_avg to determine which one was used.

O+ Ion Density. Only available before 01-Oct-1996. [op_den]

Only available before 01-Oct-1996

O+ Ion Plasma Velocity, Field Aligned, available before 01-Oct-1996 [op_vel]

Available before 01-Oct-1996 only,for energy, spin angle, and polar angle
calculation limits see moments_lim.

O+ Ion Temperature, Parallel and Perendicular to the Magnetic Field, available before 01-Oct-1996. [op_temp]

Only available before 01-Oct-1996.  Direction of magnetic field obtained from
onboard values. See moments_lim for energy, spin angle, and polar angle
calculation limits.

O+ Energy Spectrogram. Only available before 01-Oct-1996. [op_en]

Flux values summed or averaged over spin and polar angles.  See spect_lim for
sum/avg limits, see sum_avg to determine which one was used.

O+ Spin Angle Spectrogram. Only available before 01-Oct-1996. [op_spin]

Flux values summed or averaged over energy and polar angle.  See spect_lim for
sum/avg limits, see sum_avg to determine which one was used.

O+ Polar Angle Spectrogram. Only available before 01-Oct-1996. [op_polar]

Flux values summed or averaged over energy and spin angle.  See spect_lim for
sum/avg limits, see sum_avg to determine which one was used.

He+ Ion Density. Only available before 01-Oct-1996. [hep_den]

Only available before 01-Oct-1996

He+ Ion Plasma Velocity, Field Aligned, available before 01-Oct-1996 [hep_vel]

Available before 01-Oct-1996 only,for energy, spin angle, and polar angle
calculation see moments_lim.

He+ Ion Temperature, Parallel and Perendicular to Magnetic Field, available before 01-Oct-1996. [hep_temp]

Only available before 01-Oct-1996.  Direction of magnetic field obtained from
onboard values. See moments_lim for energy, spin angle, and polar angle
calculation limits.

He+ Energy Spectrogram, only available before 01-Oct-1996. [hep_en]

Flux values summed or averaged over spin and polar angles.  See spect_lim for
sum/avg limits, see sum_avg to determine which one was used.

He+ Spin Angle Spectrogram. Only available before 01-Oct-1996. [hep_spin]

Flux values summed or averaged over energy and polar angle.  See spect_lim for
sum/avg limits, see sum_avg to determine which one was used.

He+ Polar Angle Spectrogram. Only available before 01-Oct-1996. [hep_polar]

Flux values summed or averaged over energy and spin angle.  See spect_lim for
sum/avg limits, see sum_avg to determine which one was used.

TIDE Instrument Status (0-off,1-on,2-standby,3-mirrors stepped) [tide_stat]

TIDE instrument status flag:  0 - TIDE not operational or data missing, 1 - TIDE
fully operational, 2 - TIDE MCP high voltages lowered for passage through
radiation belt, 3 - TIDE mirrors stepped down due to high counts, calibration
applied to correct counts.

PSI Instrument Status (0-off,1-on,2-standby) [psi_stat]

PSI instrument status flag:  0 - PSI not operation or data missing, 1 - PSI
fully operational, 2 - PSI on but keeper not ignited.

Spacecraft Potential (from EFI K0 or a constant value) [sc_pot]

value either constant or from EFI K0

Spacecraft Ram Spin Angle [ram_spin]

spin angle direction of the spacecraft

Spacecraft Ram Polar Angle [ram_polar]

polar angle direction of the spacecraft

Magnetic Field Azimuth [mag_az]

magnetic field elevation

Magnetic Field Elevation [mag_el]

magnetic field elevation

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_H0_TIM doi:10.48322/khhg-8859

Description

H+, O+, He+ and He++ number fluxes and statistical 
uncertainties processed by 
 the TIMAS science team.  Data acquired   
with various anglular and energy 
resolutions are combined here.  
Data Quality and other indicators are provided 
 to allow selection of high 
 resolution data (PA_status(ion)=0 and  
 Energy_status(ion)=0 )  and  
 High Quality data (Quality=0). 
 See the VAR_NOTES for the following  
 variables for more detailed information.  
Quality, PA_status, Energy_status 
Bcr, Fec, Even_odd,  
Energy_Range_ID and Spins. 
A PAPCO module exists that reads 
and displays these data and data 
From other POLAR instruments.  See
http://www.mpae.gwdg.de/mpae_projects/CCR/software/papco/papco.html and the
pointer to a description of the TIMAS PAPCO module on the TIMAS home page.
Reference:
E.G. Shelley et al., The Toroidal Imaging Mass-Angle Spectrograph (TIMAS) for
the Polar Mission, Sp. Sci. Rev, Vol 71, pp 497-530, 1995.
ftp://sierra.spasci.com/DATA/timas/TIMAS_description.html
Metadata provided by W.K. Peterson

Modification History

Version 0 December, 1997 
Version 1 July, 1998 
Version 2 December, 2000 Algorithm improved to more accurately subtract
backgrounds arising from spill over from H+ into He++ channel and other sources.
 Fill data are now inserted for limited energy and pitch angle ranges for Flux_H
Flux_O Flux_He_1 and Flux_He_2 variables. The meanging of values of the of
Quality variable have been slightly modified
Version 3 June, 2002 Algorithm for V_02 had an error that resulted in under
estimation of fluxes in high count regions----i.e. the cusp/cleft and radiation
belts.  V_03 corrects this error and has been expanded to included calculation
of fluxes obtained after December 8, 1998, when TIMAS had a damaging high
voltage breakdown that resulted in reduced sensitivity.

Data Variable Descriptions

H+ number flux for 28 energy and 3 selected angle bins - quality flag applied. [Flux_HQ]

CDAWeb VV - Negative values reflect low counting rates and background
subtraction.

H+ number flux for 6 selected energies and 12 angle bins - quality flag applied. [Flux_HVQ]

CDAWeb VV - Negative values reflect low counting rates and background
subtraction.

[DO NOT USE] H+ number flux for all energies and all angle bins - quality flag applied. [Flux_HVQ_all]

CDAWeb VV - Negative values reflect low counting rates and background
subtraction.

% Sigma for H+ number flux for 28 energies and 3 selected angle bins - quality flag applied [Sigma_HQ]

Value clipped at 255% of flux.

% Sigma for H+ number flux for 6 selected energies and 12 angle bins - quality flag applied. [Sigma_HVQ]

VV - Value clipped at 255% of flux.

O+ number flux for 28 energy and 3 selected angle bins - quality flag applied. [Flux_OQ]

VV - Negative values reflect low counting rates and background subtraction.

O+ number flux for 6 selected energies and 12 angle bins - quality flag applied. [Flux_OVQ]

VV - Negative values reflect low counting rates and background subtraction.

% Sigma for O+ number flux for 28 energies and 3 selected angle bins - quality flag applied. [Sigma_OQ]

Value clipped at 255% of flux.

% Sigma for O+ number flux for 6 selected energies and 12 angle bins - quality flag applied. [Sigma_OVQ]

VV - Value clipped at 255% of flux.

He+ number flux for 28 energies and 3 selected angle bins - quality flag applied. [Flux_He_1Q]

Negative values reflect low counting rates and background subtraction.

He+ number flux for 6 selected energies and 12 angle bins - quality flag applied. [Flux_He_1VQ]

VV - Negative values reflect low counting rates and background subtraction.

% Sigma for He+ number flux for 28 energies and 3 selected angle bins - quality flag applied. [Sigma_He_1Q]

Value clipped at 255% of flux.

% Sigma for He+ number flux for 6 selected energies and 12 angle bins - quality flag applied [Sigma_He_1VQ]

VV - Value clipped at 255% of flux.

He++ number flux for 28 energies and 3 selected angle bins - quality flag applied. [Flux_He_2Q]

Negative values reflect low counting rates and background subtraction.

He++ number flux for for 28 energy and 12 angle bins - quality flag applied. [Flux_He_2VQ]

VV-Negative values reflect low counting rates and background subtraction.

% Sigma for He++ number flux for 28 energy and 3 angle bins - quality flag applied. [Sigma_He_2Q]

Value clipped at 255% of flux.

% Sigma for He++ number flux for 6 selected energies and 12 angle bins - quality flag applied. [Sigma_He_2VQ]

VV - Value clipped at 255% of flux.

Energy Range Identification: 0: Full energy range; 1: Reduced energy range; 2: Low energy range [Energy_Range_ID]

TIMAS is operated in one of 3  energy ranges. Energy_Range_ID indicates which of
the 3 instrumental energy ranges is currently active. Each instrumental energy
range further divided into 3 Key Parameter (KP) energy channels (low - medium -
and high). The table below gives the full energy range and limits of the three
KP energy ranges. Energy_Range_ID=0: (Full instrumental energy range)Full range
(0.015 - 33.3 keV/e)low E channel (0.015 - 0.37 keV/e)mid E channel (0.37 - 3.3
keV/e)high E channel (3.3 - 33.3 keV/e)Energy_Range_ID=1: (Reduced instrumental
energy range)Full range (0.015 - 22.45 keV/e)low E channel (0.015 - 0.37
keV/e)mid E channel (0.37 - 3.3 keV/e)high E channel (3.3 - 22.45
keV/e)Energy_Range_ID=2: (Low instrumental energy range)Full range (0.015 - 2.18
keV/e)low E channel (0.015 - 0.11 keV/e)mid E channel (0.11 - 0.37 keV/e)high E
channel (0.37 - 2.18 keV/e)

Total counts per spin in the fast event counter [Fec]

The TIMAS detector has a non  linear response at high count  rates that is, to
some extent  corrected for in the software  that generated the data here.  The
correction, however introduces  some uncertainty.  The FEC count  rate is
carried as an indication of  the corrections applied to the  raw data.

Total Background counts per spin [Bcr]

Total background counts per  spin

Number of spins accumulated for the four ion species [Spins]

Number of spins of data accumulatedfor each of the 4 major ion species .

Energy Resolution Indicators (0=best, 99=invalid energies) [Energy_status]

TIMAS data are available from operational  modes with full (28 bins) or moderate
 (7 bins) energy resolution.  These data  were assembled from various data
products  with different energy resolution. Data are  given in this file with
full 28 energy  step resolution EVEN IF ONLY 7 energy  step resolution data are
available.    This flag documents the resolution of   the data included in the
average.   Values are:  0    All single spin 14 energy step data.  1    Mostly
14 energy step data. Some 7 energy step. All one or two spin.2    Mostly 7
energy step data. Some 14 energy step. All one or two spin. 3    All one or two
spin 7 energy step data.4    Mostly 14 energy step data. Some 7 energy step
multispins. 5    Mostly one or two spin 7 energy step data. Some multispins. 6  
 Mostly multispin 7 energy step data. 7    All multispin 7 energy step data. 99 
 Invalid energies.Some of these conditions (1,2,4,5,6) are very rare.

Pitch Angle Resolution Flags (0=best; >3=smeared PAs; 99=invalid PAs with omnidirec flux in 0-15 deg) [PA_status]

TIMAS data are available from operational  modes with various anglular
resolutions.  These data  were assembled from various data products  with
different angular  resolutions. Data  are  given in this file with full 12
angular   bin resolution EVEN IF 12 angular bin  resolution is not available in
the input  data. This flag documents the resolution of the data included in the
average.   Values are: 0    All 22 degree data. 1    Mostly 22 degree data. 2   
Mostly 45 degree data. 3    All 45 degree data. 4    Smeared 22 degree data. Not
spin locked.5    Smeared 45 degree data. Not spin locked.99   Invalid pitch
angles.

Quality flags for H+, O+, He+, He++ (values 0,1,2=good; 3=adequate; >3 bad/do not use) [Quality]

A quality flag in the range 0-99 with  the following values/meanings  0    OK. 
1    Some data missing.  2    Slight MCP saturation.  3    Moderate MCP
saturation.  4    Severe MCP saturation.  5    No magnetometer data available. 
6    Warning flags set. 99   No valid data.

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_H0_UVI

Description

References --------------------
1. M. R. Torr, et al., A far ultraviolet imager for the International
Solar-Terrestrial Physics mission, Space Sci. Rev., v71, pp329 - 383, 1995
Notes ------------------------ 
1. The UVI field of view is circular with an 8 degree full width.  The circular
image is stored in IMAGE_DATA as a rectangular array of 228 rows and 200
columns.
2.  Time information is contained in EPOCH, Time_PB5, IMG_MINUS_MSEC, and
IMG_PLUS_MSEC.  
3. Pointing information is given in GCI_LOOK_DIR, GEODETIC_LAT, and
GEODETIC_LONG.

Modification History

v1.0 Initial Prelaunch Release 10/16/95 
v1.0 Interim Prelaunch Release 
5/8/96 Added KPGS_VERSION
3/9/97 Changed min/max valuesfor IMAGE_DATA

Data Variable Descriptions

MPEG canned images [IMAGE_DATA]

The UVI field of view is circular with an 8 degree full width.  The circular
image is stored in IMAGE_DATA as a rectangular array of 228 rows and 200
columns.  Consequently, the corners of each image contain non-image data.  The
non-active corner pixel locations are identified by a corner fill value = -128. 
The image is oriented such that the direction of decreasing row number points
along the spacecraft spin axis.  The direction of decreasing column number
points to the outboard direction (relative to the spin axis).  The orientation
is the same for both detectors.

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_H1_PWI doi:10.48322/k1kt-d028

Description

Reference:..Gurnett, D.A. et al, The Polar plasma wave instrument, Space Science
Reviews, Vol. 71, pp. 597-622, 1995.GURNETT@IOWAVE.physics.uiowa.edu
There are 224 SFR frequency bands, logarithmically spaced.  When SFR_MODE is
Linear, the 448 linear frequency bands are mapped to 224 logarithmic bands.

Modification History

Created Oct 1999

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_H1_TID doi:10.48322/t5sd-r305

Description

TIDE data after 07-Dec-1996 are non-mass total ion contribution below 411 ev

Modification History

Skeleton table version 1 created 10/16/00.
Skeleton table version 2 created 07/12/06.

Data Variable Descriptions

Total Ion Density, available after 07-Dec-1996. [total_den]

Only avaliable after 07-Dec-1996

Total Ion Plasma Velocity, Field Aligned, available after 07-Dec-1996 [total_vel]

Available after 07-Dec-1996 only,for energy and spin angle calculation see
moments_lim.  Vx and Vy only.

Total Ion Temperature, Parallel and Perpendicular to the Magnetic Field. Available after 07-Dec-1996 [total_temp]

Avaliable after 07-Dec-1996.  Direction of magnetic field obtained from onboard
values.

Total Ion Energy Spectrogram. Available after 07-Dec-1996. [total_en]

Flux values summed or averaged over spin and polar angles.  See spect_lim for
sum/avg limits, see sum_avg to determine which one was used.

Total Ion Spin Angle Spectrogram. Available after 07-Dec-1996. [total_spin]

Flux values summed or averaged over energy and polar angle.  See spect_lim for
sum/avg limits, see sum_avg to determine which one was used.

TIDE Instrument Status (0-off,1-on,2-standby,3-mirrors stepped) [tide_stat]

TIDE instrument status flag:  0 - TIDE not operational or data missing, 1 - TIDE
fully operational, 2 - TIDE MCP high voltages lowered for passage through
radiation belt, 3 - TIDE mirrors stepped down due to high counts, calibration
applied to correct counts.

PSI Instrument Status (0-off,1-on,2-standby) [psi_stat]

PSI instrument status flag:  0 - PSI not operation or data missing, 1 - PSI
fully operational, 2 - PSI on but keeper not ignited.

Spacecraft Potential (from EFI K0 or a constant value) [sc_pot]

value either constant or from EFI K0

Spacecraft Ram Spin Angle [ram_spin]

spin angle direction of the spacecraft

Spacecraft Ram Polar Angle [ram_polar]

polar angle direction of the spacecraft

Magnetic Field Azimuth [mag_az]

magnetic field elevation

Magnetic Field Elevation [mag_el]

magnetic field elevation

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_H1_UVI

Description

References --------------------
1. M. R. Torr, et al., A far ultraviolet imager for the International
Solar-Terrestrial Physics mission, Space Sci. Rev., v71, pp329 - 383, 1995
Notes ------------------------ 
1. The UVI field of view is circular with an 8 degree full width.  The circular
image is stored in IMAGE_DATA as a rectangular array of 228 rows and 200
columns.
2.  Time information is contained in EPOCH, Time_PB5, IMG_MINUS_MSEC, and
IMG_PLUS_MSEC.  
3. Pointing information is given in GCI_LOOK_DIR, GEODETIC_LAT, and
GEODETIC_LONG.

Modification History

v1.0 Initial Prelaunch Release 10/16/95 
v1.0 Interim Prelaunch Release 
5/8/96 Added KPGS_VERSION
3/9/97 Changed min/max valuesfor IMAGE_DATA

Data Variable Descriptions

MPEG canned images [IMAGE_DATA]

The UVI field of view is circular with an 8 degree full width.  The circular
image is stored in IMAGE_DATA as a rectangular array of 228 rows and 200
columns.  Consequently, the corners of each image contain non-image data.  The
non-active corner pixel locations are identified by a corner fill value = -128. 
The image is oriented such that the direction of decreasing row number points
along the spacecraft spin axis.  The direction of decreasing column number
points to the outboard direction (relative to the spin axis).  The orientation
is the same for both detectors.

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_H2_PWI doi:10.48322/xbm6-4c53

Description

Reference:..Gurnett, D.A. et al, The Polar plasma wave instrument, Space Science
Reviews, Vol. 71, pp. 597-622, 1995.GURNETT@IOWAVE.physics.uiowa.edu
An FFT on 256 or 464 values, depending on the snapshot size, was used in
calibrating the data; i.e., perform FFT, calibrate in frequency domain, perform
inverse FFT to get calibrated time series.
Coordinate System Used:  local magnetic field-aligned, a spacecraft centered
coordinate system where Z is parallel to the local B-field determined from Polar
MFE, X points outward and lies in the plane defined by the Z-axis and the radial
vector from the earth to the spacecraft, and Y completes a right-handed system
and points eastward.  The X- and Z-axes are contained in the north-south plane.
The three orthogonal magnetic field components are given in units of nT/Sec
rather than nT because the response of the searchcoils across the passband is
not flat.  In order to obtain units of nT, the data would need to be digitally
filtered to the frequency of interest and then integrated over time. 
Integrating over the entire passband could possibly destroy the resolution of
the higher frequency components since the low frequency noise, if present, will
dominate.
Data are bandpass filtered.  The valid range of data in the frequency domain is
from 0.5 to 22.5 Hz.

Modification History

Created Oct 1999
True orientation of Polar PWI electric field antenna has been determined by the
PI group to be opposite to the nominal direction. On direction of the PI group,
signs of LFWR Ex, Ey and Ez have been reversed by SPDF/NSSDC staff from what was
originally submitted.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_H2_TIM doi:10.48322/5hsz-5423

Description

H+, O+, He+ and He++ upflowing fluxes and statistical .uncertainties processed
by . the TIMAS science team..These data were used as in  .preparing the
following papers .1: Peterson et al., JGR 2008 .2: Peterson et al., JGR 2006 .3:
Lennartson et al. JGR, 2004  .References:.O.W. Lennartsson et al., .Solar wind
control of Earth's H+ and O+ outflow .rates in the 15-eV to 33-keV energy
range,.J. Geophys. Res., Vol. 109, A12212 10.1029/2004JA010690, 2004..W.K.
Peterson et al., .Quiet time solar illumination effects on the fluxes and
.characteristic energies of ionospheric outflow, .J. Geophys. Res., 111, A11S05,
doi:10.1029/2005JA011596, 2006. .W.K. Peterson et al., .Solar-minimum quiet-time
ion energization and outflow in dynamic .boundary related coordinates,  .To
appear in J. Geophys. Res., 2008 .E.G. Shelley et al., The Toroidal Imaging
Mass-Angle Spectrograph (TIMAS) for the Polar Mission, Sp. Sci. Rev, Vol 71, pp
497-530, 1995...http://lasp.colorado.edu/timas/TIMAS_description.html. 
.uncertainties processed by . the TIMAS science team..These data were used as in
 .preparing the following papers .1: Peterson et al., JGR 2008 .2: Peterson et
al., JGR 2006 .3: Lennartson et al. JGR, 2004  .References:.O.W. Lennartsson et
al., .Solar wind control of Earth's H+ and O+ outflow .rates in the 15-eV to
33-keV energy range,.J. Geophys. Res., Vol. 109, A12212 10.1029/2004JA010690,
2004..W.K. Peterson et al., .Quiet time solar illumination effects on the fluxes
and .characteristic energies of ionospheric outflow, .J. Geophys. Res., 111,
A11S05, doi:10.1029/2005JA011596, 2006. .W.K. Peterson et al., .Solar-minimum
quiet-time ion energization and outflow in dynamic .boundary related
coordinates,  .To appear in J. Geophys. Res., 2008 .E.G. Shelley et al., The
Toroidal Imaging Mass-Angle Spectrograph (TIMAS) for the Polar Mission, Sp. Sci.
Rev, Vol 71, pp 497-530,
1995...http://lasp.colorado.edu/timas/TIMAS_description.html. .uncertainties 
processed by . the TIMAS science team..These data were used as in  .preparing
the following papers .1: Peterson et al., JGR 2008 .2: Peterson et al., JGR 2006
.3: Lennartson et al. JGR, 2004  .References:.O.W. Lennartsson et al., .Solar
wind control of Earth's H+ and O+ outflow .rates in the 15-eV to 33-keV energy
range,.J. Geophys. Res., Vol. 109, A12212 10.1029/2004JA010690, 2004..W.K.
Peterson et al., .Quiet time solar illumination effects on the fluxes and
.characteristic energies of ionospheric outflow, .J. Geophys. Res., 111, A11S05,
doi:10.1029/2005JA011596, 2006. .W.K. Peterson et al., .Solar-minimum quiet-time
ion energization and outflow in dynamic .boundary related coordinates,  .To
appear in J. Geophys. Res., 2008 .E.G. Shelley et al., The Toroidal Imaging
Mass-Angle Spectrograph (TIMAS) for the Polar Mission, Sp. Sci. Rev, Vol 71, pp
497-530, 1995...http://lasp.colorado.edu/timas/TIMAS_description.html. 
.uncertainties processed by . the TIMAS science team..These data were used as in
 .preparing the following papers .1: Peterson et al., JGR 2008 .2: Peterson et
al., JGR 2006 .3: Lennartson et al. JGR, 2004  .References:.O.W. Lennartsson et
al., .Solar wind control of Earth's H+ and O+ outflow .rates in the 15-eV to
33-keV energy range,.J. Geophys. Res., Vol. 109, A12212 10.1029/2004JA010690,
2004..W.K. Peterson et al., .Quiet time solar illumination effects on the fluxes
and .characteristic energies of ionospheric outflow, .J. Geophys. Res., 111,
A11S05, doi:10.1029/2005JA011596, 2006. .W.K. Peterson et al., .Solar-minimum
quiet-time ion energization and outflow in dynamic .boundary related
coordinates,  .To appear in J. Geophys. Res., 2008 .E.G. Shelley et al., The
Toroidal Imaging Mass-Angle Spectrograph (TIMAS) for the Polar Mission, Sp. Sci.
Rev, Vol 71, pp 497-530,
1995...http://lasp.colorado.edu/timas/TIMAS_description.html. .uncertainties 
processed by . the TIMAS science team..These data were used as in  .preparing
the following papers .1: Peterson et al., JGR 2008 .2: Peterson et al., JGR 2006
.3: Lennartson et al. JGR, 2004  .References:.O.W. Lennartsson et al., .Solar
wind control of Earth's H+ and O+ outflow .rates in the 15-eV to 33-keV energy
range,.J. Geophys. Res., Vol. 109, A12212 10.1029/2004JA010690, 2004..W.K.
Peterson et al., .Quiet time solar illumination effects on the fluxes and
.characteristic energies of ionospheric outflow, .J. Geophys. Res., 111, A11S05,
doi:10.1029/2005JA011596, 2006. .W.K. Peterson et al., .Solar-minimum quiet-time
ion energization and outflow in dynamic .boundary related coordinates,  .To
appear in J. Geophys. Res., 2008 .E.G. Shelley et al., The Toroidal Imaging
Mass-Angle Spectrograph (TIMAS) for the Polar Mission, Sp. Sci. Rev, Vol 71, pp
497-530, 1995...http://lasp.colorado.edu/timas/TIMAS_description.html.  
uncertainties processed by 
 the TIMAS science team.
These data were used as in  
preparing the following papers 
1: Peterson et al., JGR 2008 
2: Peterson et al., JGR 2006 
3: Lennartson et al. JGR, 2004  
References:
O.W. Lennartsson et al., 
Solar wind control of Earth's H+ and O+ outflow 
rates in the 15-eV to 33-keV energy range,
J. Geophys. Res., Vol. 109, A12212 10.1029/2004JA010690, 2004.
W.K. Peterson et al., 
Quiet time solar illumination effects on the fluxes and 
characteristic energies of ionospheric outflow, 
J. Geophys. Res., 111, A11S05, doi:10.1029/2005JA011596, 2006. 
W.K. Peterson et al., 
Solar-minimum quiet-time ion energization and outflow in dynamic 
boundary related coordinates,  
To appear in J. Geophys. Res., 2008 
E.G. Shelley et al., The Toroidal Imaging Mass-Angle Spectrograph (TIMAS) for
the Polar Mission, Sp. Sci. Rev, Vol 71, pp 497-530, 1995.
http://lasp.colorado.edu/timas/TIMAS_description.html
Metadata provided by W.K. Peterson

Modification History

Version 0 April, 2008 
Version 1 Hopefuly not

Data Variable Descriptions

H+ Fluence at this altitude [H_Fluence]

H+ Fluence at the altitude measured (R)...for statistical studies normailze to a
standard altitude!

--> O+ Fluence at this altitude [O_Fluence]

O+ Fluence at the altitude measured (R)...for statistical studies normailze to a
standard altitude!

--> He+ Fluence at this altitude [He1_Fluence]

He+ Fluence at the altitude measured (R)...for statistical studies normailze to
a standard altitude!

--> He++ Fluence at this altitude [He2_Fluence]

He++ Fluence at the altitude measured (R)...for statistical studies normailze to
a standard altitude!

% of H+ Fluence [H_sigma]

Fluence at the altitude measured (R)...for statistical studies normailze to a
standard altitude!

--> % of O+ Fluence [O_sigma]

Fluence at the altitude measured (R)...for statistical studies normailze to a
standard altitude!

--> % of He1 Fluence [He1_sigma]

Fluence at the altitude measured (R)...for statistical studies normailze to a
standard altitude!

--> % of He2 Fluence [He2_sigma]

Fluence at the altitude measured (R)...for statistical studies normailze to a
standard altitude!

H+ E-Flux at this altitude [H_Eflux]

E-Flux at the altitude measured (R)...for statistical studies normailze to a
standard altitude!

--> O+ E-Flux at this altitude [O_Eflux]

E-Flux at the altitude measured (R)...for statistical studies normailze to a
standard altitude!

--> He+ E-Flux at this altitude [He1_Eflux]

E-Flux at the altitude measured (R)...for statistical studies normailze to a
standard altitude!

--> He++ E-Flux at this altitude [He2_Eflux]

E-Flux at the altitude measured (R)...for statistical studies normailze to a
standard altitude!

% of H+ E-Flux. [H_efluxsigma]

E-Flux at the altitude measured (R)...for statistical studies normailze a
standard altitude!

--> % of O+ E-Flux. [O_efluxsigma]

E-Flux at the altitude measured (R)...for statistical studies normailze a
standard altitude!

--> % of He+ E-Flux. [He1_efluxsigma]

E-Flux at the altitude measured (R)...for statistical studies normailze a
standard altitude!

--> % of He++ E-Flux. [He2_efluxsigma]

E-Flux at the altitude measured (R)...for statistical studies normailze a
standard altitude!

Solar Zenith angle at the magnetic foot point [SZA]

Check the SZA_status flag

Solar Zenith angle at the Conjugate magnetic foot point [Conjugate_SZA]

Check the Conjugate_SZA_status flag

Quality of the SZA Values: 0=good 99=invalid [SZA_status]

Solar Zenith Angle

Quality of the Conjugate SZA Values: 0=good 99=invalid [Conjugate_SZA_status]

Conjugate Solar Zenith Angle

H+ Quality Flag (0 indicates OK, See Var_notes for other codes) [H_quality]

A quality flag in the range 0-99 with  the following values/meanings  0    OK. 
1    Some data missing.  2    more than 5% data missing  3   not  used.  4   
not used.  5    Warning flags set.   6 not used.     9 Invalid pitch angles 99  
No valid data.

--> O+ Quality Flag (0 indicates OK, See Var_notes for other codes) [O_quality]

A quality flag in the range 0-99 with  the following values/meanings  0    OK. 
1    Some data missing.  2    more than 5% data missing  3   not  used.  4   
not used.  5    Warning flags set.   6 not used.     9 Invalid pitch angles 99  
No valid data.

--> He+ Quality Flag (0 indicates OK, See Var_notes for other codes) [He1_quality]

A quality flag in the range 0-99 with  the following values/meanings  0    OK. 
1    Some data missing.  2    more than 5% data missing  3   not  used.  4   
not used.  5    Warning flags set.   6 not used.     9 Invalid pitch angles 99  
No valid data.

--> He++ Quality Flag (0 indicates OK, See Var_notes for other codes) [He2_quality]

A quality flag in the range 0-99 with  the following values/meanings  0    OK. 
1    Some data missing.  2    more than 5% data missing  3   not  used.  4   
not used.  5    Warning flags set.   6 not used.     9 Invalid pitch angles 99  
No valid data.

Geocentric Distance [R]

MacIlwain L Parameter [L]

Magnetic Local Time [MLT]

Local Time [LocT]

Magnetic Latitude [Mlat]

Invariant Latitude [ILA]

Magnetic Field in GSM Coordinates [MagField]

3 components are GSM-X, -Y, and -Z

Space Craft Potential from EFI (use with caution) [SC_Potential]

This Variable has not been extensively validated ...use with caution.

Time delayed Wind IFM Magnetic Field from WIND in GSM Coordinates [Imf_Gsm]

Time lagged solar wind pressure from WIND [SW_pressure]

Time lagged solar wind density from WIND [SW_density]

Time lagged Solar wind velocity from WIND in GSM Coordinates [SW_velocity]

Energy Range Identification: 0: Full energy range; 1: Reduced energy range; 2: Low energy range [Energy_range]

TIMAS is operated in one of 3  energy ranges. Energy_Range_ID indicates which of
the 3 instrumental energy ranges is currently active.

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_H3_PWI doi:10.48322/zvyr-jh19

Description

Reference:  Gurnett, D.A., et al., The Polar plasma wave instrument, Space
Science Reviews, Vol. 71, pp. 597-622, 1995. donald-gurnett@uiowa.edu
An FFT on 2048 values was used in calibrating the data; i.e., perform FFT,
calibrate in frequency domain, perform inverse FFT to get calibrated time
series.
Data are lowpass filtered so that the data are valid only up to 16 kHz.
Effective Bandwidth is 1.5*delta_f, where delta_f depends on the size of the FFT
used to convert to the frequency domain, and delta_t.

Modification History

Created Mar 2021
2021-03-23:  Version 3 replaces time tags with higher precision TT2000 and
applies waveform baseline corrections.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_H4_PWI doi:10.48322/32d0-db83

Description

Reference:  Gurnett, D.A. et al., The Polar plasma wave instrument, Space
Science Reviews, Vol. 71, pp. 597-622, 1995.  donald-gurnett@uiowa.edu  
An FFT on 2048 values was used in calibrating the data; i.e., perform FFT,
calibrate in frequency domain, perform inverse FFT to get calibrated time
series.
Data are lowpass filtered so that the data are valid only up to 2 kHz.
Effective Bandwidth is 1.5*delta_f, where delta_f depends on the size of the FFT
used to convert to the frequency domain, and delta_t.

Modification History

Created Mar 2021
2021-03-23:  Version 3 replaces time tags with higher precision TT2000 and
applies waveform baseline corrections and updated calibrations.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_H5_PWI doi:10.48322/kvvt-2c42

Description

Reference:..Gurnett, D.A. et al, The Polar plasma wave instrument, Space Science
Reviews, Vol. 71, pp. 597-622, 1995.GURNETT@IOWAVE.physics.uiowa.edu
An FFT on 2048 values was used in calibrating the data; i.e., perform FFT,
calibrate in frequency domain, perform inverse FFT to get calibrated time
series.
Data are lowpass filtered so that the data are valid only up to 16 kHz.
Effective Bandwidth is 1.5*delta_f, where delta_f depends on the size of the FFT
used to convert to the frequency domain, and delta_t.

Modification History

Created Oct 1999

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_H7_PWI doi:10.48322/7vp8-5w49

Description

Reference:..Gurnett, D.A. et al, The Polar plasma wave instrument, Space Science
Reviews, Vol. 71, pp. 597-622, 1995.GURNETT@IOWAVE.physics.uiowa.edu
An FFT on 1024 values was used in calibrating the data; i.e., perform FFT,
calibrate in frequency domain, perform inverse FFT to get calibrated time
series.
Coordinate System Used:  local magnetic field-aligned, a spacecraft centered
coordinate system where Z is parallel to the local B-field determined from Polar
MFE, X points outward and lies in the plane defined by the Z-axis and the radial
vector from the earth to the spacecraft, and Y completes a right-handed system
and points eastward.  The X- and Z-axes are contained in the north-south plane.
Effective Bandwidth is 1.5*delta_f, where delta_f depends on the size of the FFT
used to convert to the frequency domain, and delta_t.
This data comes is in snapshots of 31816 points per channel, every 9.2 seconds,
where the duration of each snapshot is 0.045 seconds.  Since Epoch time is in
milliseconds, the times for the data points will not be unique unless the
Delta_T in milliseconds is added to the Epoch time for the snapshot.
The data in this file will be in sets of 31744 (31*1024) points per channel
because the FFT size does not come out even within the number of points per
snapshot.  To obtain the time for each point in the snapshot, increment each
Epoch time after the first with Delta_T (in ms).

Modification History

Created Jan 2004

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_H8_PWI doi:10.48322/06zn-yc02

Description

Reference:..Gurnett, D.A. et al, The Polar plasma wave instrument, Space Science
Reviews, Vol. 71, pp. 597-622, 1995.GURNETT@IOWAVE.physics.uiowa.edu
An FFT on 1024 values was used in calibrating the data; i.e., perform FFT,
calibrate in frequency domain, perform inverse FFT to get calibrated time
series.
Effective Bandwidth is 1.5*delta_f, where delta_f depends on the size of the FFT
used to convert to the frequency domain, and delta_t.
Coordinate system used:  antenna coordinate system, where the u-axis is offset
by -45 degrees from the spacecraft x-axis, the v-axis is offset by -45 degrees
from the spacecraft y-axis, and the z-axis is identical to the spacecraft
z-axis.
This data comes in snapshots of 190902 points distributed among 2 to 6 channels
every 9.2 seconds, where the duration of the snapshot is 0.045 seconds.  Since
Epoch time is in milliseconds, the times for the data points will not be unique
unless the Delta_T (in milliseconds) is added to  the Epoch time for the
snapshot.

Modification History

Created Dec 2003

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_H9_PWI doi:10.48322/ybd2-7a47

Description

Reference:..Gurnett, D.A. et al, The Polar plasma wave instrument, Space Science
Reviews, Vol. 71, pp. 597-622, 1995.GURNETT@IOWAVE.physics.uiowa.edu
An FFT on 1992 values was used in calibrating the data; i.e., perform FFT,
calibrate in frequency domain, perform inverse FFT to get calibrated time
series.
Effective Bandwidth is 1.5*delta_f, where delta_f depends on the size of the FFT
used to convert to the frequency domain, and delta_t.
Coordinate system used:  antenna coordinate system, where the u-axis is offset
by -45 degrees from the spacecraft x-axis, the v-axis is offset by -45 degrees
from the spacecraft y-axis, and the z-axis is identical to the spacecraft
z-axis.
This data comes in snapshots of 1992 or 3984 points every 0.064 seconds. 
Duration of a snapshot is less when the instrument is in duty cycle modes. 
Since Epoch time is in milliseconds, the times for the data points will not be
unique unless the fmsec (fraction of milliseconds) is appended to the Epoch0
time for that point.
The frequency filters used for the wideband receiver have a range that limits
the calibration.  The following table specifies the range of frequencies for
which the calibration is certified.  Outside this range the amplitude values may
be in error and should not be used.  (Translation, Filter, Freq Range) (0 kHz,
90 kHz, 7.5 kHz-90.0 kHz) (125 kHz, 90 kHz, 131.9 kHz-214.8 kHz) (250 kHz, 90
kHz, 254.3 kHz-341.2 kHz) (500 kHz, 90 kHz, 504.79 kHz-591.1 kHz) (0 kHz, 10
kHz, 0.035 kHz-11.64 kHz) (0 kHz, 22 kHz, 0.065 kHz-21.59 kHz) (0 kHz, 1-3 kHz,
1.0 kHz-3.0 kHz) (0 kHz, 3-6 kHz, 3.0 kHz-6.0 kHz)

Modification History

Created Dec 2003

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_HYD_ENERGY_FLUX

Description

Reference: HYDRA is a 3-Dimensional Electron and Ion Hot Plasma Instrument for
the Polar Spacecraft of the GGS Mission, J. Scudder et al., Space Sci. Rev.,
71,459-495, Feb. 1995. http://www-st.physics.uiowa.edu This data set contains 
survey electron and proton moments for the energy flux (parallel), at
13.8-second resolution as determined (0-20keV). Higher quality data products may
be available from the P.I.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_K0_CAM doi:10.48322/88r3-b823

Description

This data set contains 96-second averaged counting rates for H+, He++, (O+, O++
together), (O>2+), all from the MICS part of the instrument, with a +/- 1 degree
field of view perpendicular to the spin axis, segmented into bins of size 1/32
of a spin.
T.A. Fritz et.al, CAMMICE:The POLAR CAMMICE instruments
It also contains 96-second averaged counting rates from two proton channels
(0.5-1.7 MeV and 1.7-5.8 MeV), two He channels (1.4-4.3 MeV and 4.3-9.6 MeV),
and six CNO channels (5-10, 6-11, 7-13, 17-92, 18-92, 21-92 MeV), from the HIT
part of the instrument, with a +/- 6 degree field of view perpendicular to the
spin axis, segmented into bins  
of 1/32 of a spin.
A. Fritz et.al, CAMMICE:The POLAR CAMMICE instruments

Modification History

This is the 1st version.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_K0_CEP doi:10.48322/gav4-4v68

Description

Data: 96 second averages
J. B. Blake et.al, Comprehensive Energetic Particle & Pitch Angle Distribution

Modification History

This is the 1st version.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_K0_EFI doi:10.48322/6n18-vn30

Description

Reference: DATA FORMAT CONTROL DOCUMENT (DFCD) BETWEEN THE 
INTERNATIONAL SOLAR-TERRESTRIAL PHYSICS (ISTP) PROGRAM 
INFORMATION PROCESSING DIVISION (IPD) GROUND DATA PROCESSING 
SYSTEM AND THE ISTP MISSION INVESTIGATORS SEPTEMBER 1993 Pages 3-57 through
3-60.
GGS Instrument papers (DRAFT)December 1992 pages B.2.1 thru B.2.14 inclusive.
The Polar Electric Field Instrument KPS will record data from two sets of
Langmuir probes.
The first set V12, are 130m apart, the second set V34, are 100m apart.

Modification History

Avoid B algorithm was added to the ground spinfits calculations in version 4.0.
Version 4.1: Update of Berkeley Modules.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_K0_GIFWALK

Description

Pre-generated PWG plots

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_K0_HYD doi:10.48322/8ksp-p425

Description

Reference: HYDRA is a 3-Dimensional Electron and Ion Hot  plasma Instrument for
the Polar Spacecraft of the GGS Mission, J. Scudder et al., Space Sci. Rev., 71,
459-495, Feb. 1995.
This data set contains the electron density and average energy, and the maximum
and minimum Debye energies, at 1-minute resolution.
J. Scudder, et.al, Space Sci. Rev., 71, 459-495, 1995,
http://www-st.physics.uiowa.edu
J. Scudder, et.al, Space Sci. Rev., 71, 459-495, 1995,
http://www-st.physics.uiowa.edu

Modification History

Created Feb. 10, 1997
3/23/97: Corrected attribute errors
Re-calibrated, 9/22/97

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_K0_MFE doi:10.48322/vsfk-ph35

Description

Data: 0.92 minute and6 second averages

Modification History

version 1.0 Jan 93 Test. Modified by JT on Nov. 30, 1995Modified by XL on Feb.
18, 1997

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_K0_PIX

Description

INSTRUMENT DESCRIPTION:              
The PIXIE instrument remotely images 
bremsstrahlung X-rays which are 
emitted from the earth's atmosphere. 
PIXIE measures the bremsstrahlung 
X-ray flux in two spatial dimensions 
and as a function of energy from 
2 keV to 60 keV in 64 energy 
channels.  The spatial 
resolution and sensitivity of the 
instrument are a function of orbital 
altitude.  Sensitivity is optimized 
by the use of a variable 
configuration of the instrument's 
adjustable aperture plate.    
Continuous imagery will be provided, 
since PIXIE is mounted on the 
despun platform.  Each X-ray photon 
is identified individually by the 
time and location at which it is 
detected within the focal plane.
INSTRUMENT REFERENCES:               
1.  Instrument Description Document 
for the Polar Ionospheric X-ray 
Imaging Experiment (PIXIE) on the 
ISTP/GGS POLAR Satellite (submitted 
to Project as a PIXIE deliverable). 
Document number LMSC F254274 
(Lockheed Space and Missiles Co.) 
2.  McKenzie, D. L., D. J. Gorney, 
and W. L. Imhof, Auroral X-ray 
Imaging from High- and Low-Earth 
Orbit, Proc. SPIE, 1745, 39, 1992. 
3.  McKenzie, D. L., D. J. Gorney, 
and W. L. Imhof, Auroral X-ray 
Imaging from High- and Low-Earth 
Orbit, Opt. Eng. (to be published in 
the February 1994 issue). 
4.  Imhof, W. L., et al., The Polar 
Ionospheric X-ray Imaging Experiment 
(PIXIE), Space Science Reviews (to 
be published as part of a special 
issue on the GGS instruments). 
KEY PARAMETERS DESCRIPTION:          
The Primary Key Parameter data 
consists of two 64x64 pixel X-ray 
image arrays and two Mean Intensity 
measures. The images and intensities 
are associated with two variable 
integrated energy channel ranges.  
The Secondary Key Parameter data 
contains information necessary to 
the appropriate interpretation of 
the images.  This information 
includes geographic and geomagnetic 
spatial registration references, 
integrated energy range definitions, 
data quality flags, and various 
mode/state indicators.  The spatial 
references include full pixel maps 
(providing the value of a particular 
coordinate, e.g., magnetic latitude, 
at each of the 4096 pixels) as well 
as simple pixel markers locating 
specific features (such as the 
geographic and geomagnetic poles).

Modification History

Unified image array has been split
into high & low energy image arrays.
VAR_NOTES attribute entries have
been included to supplement CATDESC
entries where appropriate.

Data Variable Descriptions

Low Energy X-ray Source Array, 64x64 image [XSA_LOW]

Intensity of photons detected in the energyrange specified by the first array
elementof variable ENERGY_RANGE and its associated delta values

--> Low Energy X-ray Source Array with geographic map overlay [XSA_LOW_O]

Intensity of photons detected in the energyrange specified by the first array
elementof variable ENERGY_RANGE and its associated delta values

[DO NOT USE: UNDER-DEVELOPMENT] --> Test Display [XSA_LOW_Test]

Intensity of photons detected in the energyrange specified by the first array
elementof variable ENERGY_RANGE and its associated delta values

--> Low Energy X-ray Source Array, azimuthal projection to geographic coordinates [XSA_LOW_P]

Intensity of photons detected in the energyrange specified by the first array
elementof variable ENERGY_RANGE and its associated delta values

--> Low Energy X-ray Source Array, azimuthal projection to magnetic local time and invariant latitude [XSA_LOW_M]

Intensity of photons detected in the energyrange specified by the first array
elementof variable ENERGY_RANGE and its associated delta values

Low Energy X-ray Source Array, 64x64 mpeg movie image [XSA_LOW_MV]

Intensity of photons detected in the energyrange specified by the first array
elementof variable ENERGY_RANGE and its associated delta values

--> Low Energy X-ray Source Array with geographic map overlay [XSA_LOW_O_MV]

Intensity of photons detected in the energyrange specified by the first array
elementof variable ENERGY_RANGE and its associated delta values

--> Low Energy X-ray Source Array, azimuthal projection to geographic coordinates [XSA_LOW_P_MV]

Intensity of photons detected in the energyrange specified by the first array
elementof variable ENERGY_RANGE and its associated delta values

--> Low Energy X-ray Source Array, azimuthal projection to magnetic local time and invariant latitude [XSA_LOW_M_MV]

Intensity of photons detected in the energyrange specified by the first array
elementof variable ENERGY_RANGE and its associated delta values

64x64 X-ray Source Array for high energy range [XSA_HIGH]

Represents photons detected in the energyrange specified by the second array
elementof variable ENERGY_RANGE and its associated delta values

--> High Energy X-ray Source Array with geographic map overlay [XSA_HIGH_O]

Represents photons detected in the energyrange specified by the second array
elementof variable ENERGY_RANGE and its associated delta values

[DO NOT USE: UNDER-DEVELOPMENT] --> Test Display [XSA_HIGH_Test]

Represents photons detected in the energyrange specified by the second array
elementof variable ENERGY_RANGE and its associated delta values

--> High Energy X-ray Source Array, azimuthal projection to geographic coordinates (fixed-sun orientation) [XSA_HIGH_P]

Represents photons detected in the energyrange specified by the second array
elementof variable ENERGY_RANGE and its associated delta values

--> High Energy X-ray Source Array, azimuthal projection to magnetic local time and invariant latitude [XSA_HIGH_M]

Represents photons detected in the energyrange specified by the second array
elementof variable ENERGY_RANGE and its associated delta values

64x64 X-ray Source Array for high energy range, mpeg movie image. [XSA_HIGH_MV]

Represents photons detected in the energyrange specified by the second array
elementof variable ENERGY_RANGE and its associated delta values

--> High Energy X-ray Source Array with geographic map overlay [XSA_HIGH_O_MV]

Represents photons detected in the energyrange specified by the second array
elementof variable ENERGY_RANGE and its associated delta values

--> High Energy X-ray Source Array, azimuthal projection to geographic coordinates (fixed-sun orientation) [XSA_HIGH_P_MV]

Represents photons detected in the energyrange specified by the second array
elementof variable ENERGY_RANGE and its associated delta values

--> High Energy X-ray Source Array, azimuthal projection to magnetic local time and invariant latitude [XSA_HIGH_M_MV]

Represents photons detected in the energyrange specified by the second array
elementof variable ENERGY_RANGE and its associated delta values

Mean photon intensity over entire image for low energy range [TXF_LOW]

Mean photon intensity over entire image for high energy range [TXF_HIGH]

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_K0_PWI doi:10.48322/0zmq-1b63

Description

Reference:..Gurnett, D.A. et al, The Polar plasma wave instrument, Space Science
Reviews, Vol. 71, pp. 597-622, 1995.GURNETT@IOWAVE.physics.uiowa.edu
Note:..The electron ion and cyclotron frequencies are derived from the
following:  Fce = 0.028 kHz*B, where B is the magnitude of the ambient magnetic
field measured in nT.  Fcp = Fce/1837 in kHz.  FcO+ = Fcp/16 in kHz.  All
frequencies in the key parameters are converted to Hz.
Since the SFR frequency steps vary with the mode, the measured SFR frequencies
will be mapped to a fixed array of 160 approximately logarithmically spaced
frequency values, 32 frequency values for each of the five SFR channels.  In the
log mode, the 64 frequency steps of the fourth and fifth frequency channels will
be mapped to 32 frequency steps each, using geometric averaging.  In the linear
mode, the 448 linearly spaced frequency steps of the five frequency channels
will be mapped to the fixed array of 160 logarithmically spaced frequency values
using a windowing technique.  The magnetic and electric field values
corresponding to each SFR frequency step will be similarly mapped to 160-point
fixed arrays corresponding to the mapped frequency array.

Modification History

Created Sept 1992, modified by JT 2/15/96

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_K0_SPHA doi:10.48322/f58f-3y50

Description

To be supplied

Modification History

6/4/93 - Original Implementation
6/8/94 - CCR ISTP 1852, updated CDHF skeleton to CDF standards - JT
11/10/94 - Correct errors made in ccr 1852.  ICCR 1884

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_K0_UVI doi:10.48322/1ac1-5c88

Description

References --------------------
1. M. R. Torr, et al., A far ultraviolet imager for the International
Solar-Terrestrial Physics mission, Space Sci. Rev., v71, pp329 - 383, 1995
Notes ------------------------ 
1. The UVI field of view is circular with an 8 degree full width.  The circular
image is stored in IMAGE_DATA as a rectangular array of 228 rows and 200
columns.
2.  Time information is contained in EPOCH, Time_PB5, IMG_MINUS_MSEC, and
IMG_PLUS_MSEC.  
3. Pointing information is given in GCI_LOOK_DIR, GEODETIC_LAT, and
GEODETIC_LONG.

Modification History

v1.0 Initial Prelaunch Release 10/16/95 
v1.0 Interim Prelaunch Release 
5/8/96 Added KPGS_VERSION
3/9/97 Changed min/max valuesfor IMAGE_DATA

Data Variable Descriptions

Quality indicator (also quickly shows times when images are available) [QUALITY_FLAG]

QUALITY_FLAG is a  bit-mapped flag in which each bit corresponds to a single
quality condition.  The most  significant bit (minus sign) is not used. 
Consequently up to 31 different quality conditions can be simultaneously
flagged.  The flags are ordered in severity with increasing bit position.  The
following _hexadecimal_ values have been defined  for QUALITY_FLAG: 0 = No
errors or quality conditions;  1 = an error occurred writing an SFDU comment; 2
=  image time was outside of selected processing window; 4 = some level zero
minor frames had fill values;  8 = some level zero minor frames had sync errors;
10 = the image single frame integration period could not be determined due to
bad telemetry (assumed to be 4 major frames);  20 = the despun platform was in
motion or had not settled down from a motion;   40 = the pointing calculations
have not been validated or may be unreliable;  80 = the time flags for this
image may be unreliable; 100 = there was an error decode star mode data; 200
=some major frames were missing but an image could be partially  reconstructed; 
400 = calibration data is missing or otherwise invalid;  800 = a background
image could not be found; 1000 = the  requested output image could not be found.

Far UV Images (kRay), small format display with click-expand (~10 min res) [IMAGE_DATA]

The UVI field of view is circular with an 8 degree full width.  The circular
image is stored in IMAGE_DATA as a rectangular array of 228 rows and 200
columns.  Consequently, the corners of each image contain non-image data.  The
non-active corner pixel locations are identified by a corner fill value = -128. 
The image is oriented such that the direction of decreasing row number points
along the spacecraft spin axis.  The direction of decreasing column number
points to the outboard direction (relative to the spin axis).  The orientation
is the same for both detectors.

--> (USE SHORT TIME SPANS) Large format display with click-expand, no geographic registration [IMAGE_DATA_LF]

The UVI field of view is circular with an 8 degree full width.  The circular
image is stored in IMAGE_DATA as a rectangular array of 228 rows and 200
columns.  Consequently, the corners of each image contain non-image data.  The
non-active corner pixel locations are identified by a corner fill value = -128. 
The image is oriented such that the direction of decreasing row number points
along the spacecraft spin axis.  The direction of decreasing column number
points to the outboard direction (relative to the spin axis).  The orientation
is the same for both detectors.

--> (USE SHORT TIME SPANS) With geographic map overlay [GEOD_IMAGE_O]

This is a virtual variable computed in read_myCDF

--> [DO NOT USE: UNDER-DEVELOPMENT] Test Display [GEOD_IMAGE]

This is a virtual variable computed in read_myCDF

--> (USE SHORT TIME SPANS) Azimuthal projection to geographic (with fixed sun orientation) [GEOD_IMAGE_PS]

This is a virtual variable computed in read_myCDF. Calling conv_map_image

--> (USE SHORT TIME SPANS) Azimuthal projection to magnetic LT and invariant lat, using eccentric dipole model [GEOD_IMAGE_M]

This is a virtual variable computed in read_myCDF. MLT map generated in
plot_map_images.pro

--> (USE SHORT TIME SPANS) Movie display of images, no geographic registration [IMAGE_MOVIE]

This is a virtual variable computed in read_myCDF

--> (USE SHORT TIME SPANS) Movie, with geographic map overlay [IMAGE_MOVIE_O]

This is a virtual variable computed in read_myCDF

--> (USE SHORT TIME SPANS) Movie, azimuthal projection to geographic (with fixed sun orientation) [IMAGE_MOVIE_PS]

This is a virtual variable computed in read_myCDF. Calling conv_map_image

--> (USE SHORT TIME SPAN) Movie, azimuthal projection to magnetic LT and invariant lat, using eccentric dipole model [IMAGE_MOVIE_M]

This is a virtual variable computed in read_myCDF. MLT map generated in
plot_map_images.pro

Spacecraft Position in GCI, 3 comp. [GCI_POSITION]

Copied from S/C orbit file.

Spacecraft Attitude in GCI, 3 comp. [ATTITUDE]

Calculated from S/C attitude file.

Sun Position in GCI, 3 comp. [GCI_SUN]

Vector pointing to sun.

Unit vector along field of view. [GCI_LOOK_DIR]

GCI_LOOK_DIR is a unit vector in GCI coordinates pointing from the spacecraft
along the center of the UVI line of sight.  An external utility can be used to
calculate latitude and longitude for any pixel of the UVI image.The pointing
utility can be found on the UVI WWW home page (URL: TBD)

Offset angle of despun platform from nadir. [DSP_ANGLE]

Positive in direction opposite of spacecraft rotation.

Filter selection. [FILTER]

1304=2, 1356=3, LBHS=4, LBHL=5, SOLR=6

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_K0_VIS

Description

 Instrument functional description:
    The VIS is a set of three low-light-level cameras.  Two of these
    cameras share primary and some secondary optics and are designed to
    provide images of the nighttime auroral oval at visible wavelengths.
    A third camera is used to monitor the directions of the fields-of-view
    of the auroral cameras with respect to the sunlit Earth and return
    global images of the auroral oval at ultraviolet wavelengths.  The
    VIS instrumentation produces an auroral image of 256 x 256 pixels
    approximately every 24 seconds dependent on the integration time and
    filter selected.  The fields-of-view of the two nighttime auroral
    cameras are 5.6 x 6.3 degrees and 2.8 x 3.3 degrees for the low and
    medium resolution cameras, respectively.  One or more Earth camera
    images of 256 x 256 pixels are produced every five minutes, depending
    on the commanded mode.  The field-of-view of the Earth camera is
    approximately 20 x 20 degrees.
 Reference:
    Frank, L. A., J. B. Sigwarth, J. D. Craven, J. P. Cravens, J. S. Dolan,
        M. R. Dvorsky, J. D. Harvey, P. K. Hardebeck, and D. Muller,
        'The Visible Imaging System (VIS) for the Polar Spacecraft',
        Space Science Review, vol. 71, pp. 297-328, 1995.
 [Note to first-time users:  The first four variables are of primary interest.
    The displayable 256 x 256 image array is in variable 3.  The correct orien-
    tation of a displayed image is explained in the description of variable 3
    below.]
 Data set description:
         The VIS key parameter data set is a survey of auroral activity
    provided by a series of single images showing a significant area of the
    auroral zone.  The displayable image counts are in variable 3.
         Some coordinate information is included for viewer orientation.
    Coordinates are calculated for a grid of 18 x 18 points corresponding
    to one pixel out of every 15 x 15 pixel block.  In addition, a rotation
    matrix and a table of distortion-correcting look direction unit vectors
    are provided for the purpose of calculating coordinates for every pixel.
    See the description of variables 17 and 18 below.
         To facilitate viewing of the images, a mapping of pixel value to a
    recommended color table based on the characteristics of the selected
    filter will be included with each image.  See the description of variables
    22, 23, and 24 below.
         A relative intensity scale is provided by the uncompressed count table
    of variable 27.  Approximate intensity levels in kiloRayleighs are given in
    the intensity table of variable 28.  Information on the availability of
    more precisely calibrated intensities can be found on the VIS website at
    URL .http://eiger.physics.uiowa.edu/~vis/software/. 
 Variable descriptions:
    1,2. Center time
        The time assigned to an image is the center time of the integration
        period within a resolution of 50 milliseconds.
    3. Image counts
        Image pixel counts range from 0 to 255.  They are stored in a two-
        dimensional 256 x 256 byte array.  Images from the Earth camera
        (sensor 0) are conventionally displayed with row 1 at the top, row 256
        at the bottom, column 1 on the left, and column 256 on the right.  The
        conventional image display for the low resolution camera (sensor 1) is
        rotated 180 degrees so that the row 1-column 1 pixel is at the lower
        right corner and the row 256-column 256 pixel is at the upper left
        corner.  When displayed in this manner, the spacecraft spin axis is
        oriented to the right in the display, the X component is defined as
        the center of the image look direction, and the Y component is the
        cross product of the spin axis and the look direction.
    4. Sensor number
        0 = Earth camera,
        1 = low resolution camera,
        2 = medium resolution camera.
    5. Half integration time
        This is half the length of the integration period for the image,
        measured in milliseconds.
    6. Filter
        Twelve filters are available for visible imaging; the filter number,
        1-12, is given here.  Ultra-violet imaging is done with one filter only,
        designated here as filter number 0.  In addition, the peak wavelength
        in Angstroms is given for the selected filter.
    7. Presumed altitude of emissions
        The presumed altitude of the emissions seen in the image varies
        with the characteristics of the filter used.
    8. Field stop position
        The field stop may partially occlude the field of view of the low
        or medium resolution cameras.  The position is given in 1.5 degree
        steps.
    9. Platform pitch angle
        This is the platform pointing angle of rotation around the spin
        axis, measured from nadir.
 10,11. Mirror elevation and azimuth angles
        For the low or medium resolution camera, the two-axis mirror
        position is given in steps measured from the instrument calibration
        switches.  The boresight of the instrument is located at step 68 in
        azimuth and step 118 in elevation.
 12,13. Geographic coordinates
        Geographic north latitude and east longitude are provided for the
        pixels at these image array locations: every 15th row starting
        with row 1 and ending with row 256, and every 15th column starting
        with column 1 and ending with column 256, for a total of
        18 x 18 coordinate pairs.
 14,15. Spacecraft position and velocity vectors, GCI
        The spacecraft position vector and velocity vector in GCI
        coordinates are for the image center time as given in variables
        1 and 2.
   16. Spacecraft spin axis unit vector, GCI
 17,18. Image-to-GCI rotation matrix and look direction vector table
        The rotation matrix may be used with the look direction vector table to
        obtain pointing vectors in GCI coordinates for each pixel.  The
        resulting vectors may be used to calculate coordinates for the observed
        positions of the pixels.  Software for this purpose is available at URL
         .http://eiger.physics.uiowa.edu/~vis/software/.  The general method 
         used is described below.
        In the image coordinate system, the X axis is the center line-of-sight
        or look direction; the Y axis is the cross product of the spin axis an
        the X axis; and the Z axis is the cross product of the X axis and the
        Y axis.  When the display orientation conventions in the variable 3
        description are applied, the low resolution camera image is rotated so
        that both Earth camera and low resolution camera images are displayed
        with Y axis pointing up and Z axis pointing toward the right.
        To obtain the coordinates of the observed position of a pixel,
        calculate the intersection of the line-of-sight with the surface
        of an oblately spheroidal Earth at the altitude given as
        variable 7.  The equation of the spheroid is
            X**2/(A+ALT)**2 + Y**2/(A+ALT)**2 + Z**2/(B+ALT)**2 = 1
            where A is the Earth radius at the equator,
                  B is the Earth radius at the pole, and
                  ALT is the given altitude.
        The line-of-sight equations are
            (X-SCX)/DX = (Y-SCY)/DY = (Z-SCZ)/DZ
            where (SCX,SCY,SCZ) is the spacecraft position vector GCI, and
                    (DX,DY,DZ)  is the look direction unit vector GCI.
        Solve the line-of-sight equations for two variables in terms
        of the third; substitute into the spheroid equation; and use the
        quadratic formula to solve for the third variable.  Select
        the solution point closer to the spacecraft.
   19. Zenith angle of center line-of-sight at presumed altitude
        This is the angle between the geocentric vector through the
        observed point, assuming the altitude given as variable 7,
        and the reverse of the image center line-of-sight vector.
   20. Sun position unit vector, GCI
   21. Solar zenith angle at observed point of center line-of-sight
        This is the angle of the sun from zenith at the observed point
        of the center line-of-sight, assuming the altitude given as
        variable 7.
   22. RGB color table
        This is the recommended color table to be used with the
        limits given in variables 23 and 24.
 23,24. Low and high color mapping limits
        The low and high color limits are recommended for remapping
        the color table entries, as follows:
            For pixel values less than the low limit, use the color
                at table position 1.
            For pixel values greater than or equal to the low limit
                and less than or equal to the high limit, use the color
                at table position (pix-low)/(high-low) x 255 + 1.
            For pixel values greater than the high limit, use the color
                at table position 256.
   25. Data quality flag
        The data quality word has bits set to 1 when the listed
        conditions are true.  Bit #31 is the most significant bit in the
        word, and it will not be used as a flag.  These are the bit
        assignments:
            bit 0 - image data frame sync error
            bit 1 - image data frame counters error
            bit 2 - image data fill frame flag.
   26. Post gap flag
        The post gap flag has these possible values:
            0 - no gap occurred immediately prior to this record,
            1 - the gap occurred because the instrument was not in
                  a mode that allowed for the production of images for the
                  selected sensor,
            2 - the gap occurred because level zero data were missing,
            3 - the gap occurred because level zero data were too
                  noisy to extract images.
   27. Expanded count table
        The image pixel counts are quasi-logarithmically compressed to the
        range 0-255.  This table gives the average of the uncompressed range
        for each compressed count value.  Table entries 1-256 correspond to
        compressed counts 0-255 respectively.
   28. Intensity table
        Approximate intensity levels in kiloRayleighs are given for each
        compressed count value.  Table entries 1-256 correspond to compressed
        counts 0-255 respectively.  Information on the availability of more
        precisely calibrated intensities can be found on the VIS website at
        URL .http://eiger.physics.uiowa.edu/~vis/software/. 
 Supporting software:
    Supporting software is available on the VIS website at the URL
    .http://eiger.physics.uiowa.edu/~vis/software/.  Included is an IDL program 
    that displays the images with the recommended color bar and provides
    approximate intensities and coordinate data for each pixel.

Modification History

Initial development

Data Variable Descriptions

Presumed emission altitude (also quickly shows time periods when images are available) [AltF]

Visible Image (quasi-log cnts), small format display with click-expand (~4 min. res.) [Image_Counts]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> Larger format display with click-expand, no geographic registration [Image_CountsF]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) With geographic map overlay [Mapped_ImageO]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> [DO NOT USE: UNDER-DEVELOPMENT] Test Display [Mapped_Image]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Azimuthal projection to geographic (fixed sun orientation) [Mapped_ImageP]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Azimuthal projection to magnetic LT and invariant lat [Mapped_ImageM]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie display of images, no geographic registration [Movie_Image]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie, with geographic grid overlay [Mapped_MovieO]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie, azimuthal projection to geographic (fixed sun orientation) [Mapped_MovieP]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie, azimuthal projection to magnetic LT and invariant lat [Mapped_MovieM]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

Visible Image (kRay), small format display with click-expand (~4 min. res.) [IImage_Counts]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> Larger format display with click-expand, no geographic registration [IImage_CountsF]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) With geographic grid overlay [Mapped_IImageO]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Azimuthal projection to geographic (fixed sun orientation) [Mapped_IImageP]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Azimuthal projection to magnetic LT and invariant lat [Mapped_IImageM]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie display of images, no geographic registration [Movie_IImage]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie, with geographic grid overlay [Mapped_IMovieO]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie, azimuthal projection to geographic (fixed sun orientation) [Mapped_IMovieP]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie, azimuthal projection to magnetic LT and invariant lat [Mapped_IMovieM]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

Sensor number: 0=Earth Camera,1=Low Resolution Camera,2=Medium Resolution Camera [Sensor]

Filter number and peak wavelength in Angstroms) [Filter]

Filters #1-12 are visible wavelengths; filter #0 is UV for Earth camera images

Platform pointing angle from nadir [PPitch]

Platform angle of rotation around spin axis, measured from nadir in tenths of
degrees

GCI position vector of Polar spacecraft in kilometers. [SC_Pos_GCI]

GCI velocity vector of Polar spacecraft in km/sec. [SC_Vel_GCI]

GCI spin axis unit vector of Polar spacecraft. [SC_SpinV_GCI]

Data quality flags [D_Qual]

MSB will not be used as a flag; see TEXT for other bit assignments

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_K1_TIM doi:10.48322/qzm5-9r79

Description

H+, O+, He+ and He++ number fluxes for survey  purposes only 
E.G. Shelley et al., The Toroidal Imaging Mass-Angle Spectrograph (TIMAS) for
the Polar Mission, Sp. Sci. Rev, Vol 71, pp 497-530, 1995.
ftp://sierra.spasci.com/DATA/timas/TIMAS_description.html
Metadata provided by W.K. Peterson

Modification History

Version 0 June, 2001

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_K1_VIS

Description

 Instrument functional description:
    The VIS is a set of three low-light-level cameras.  Two of these
    cameras share primary and some secondary optics and are designed to
    provide images of the nighttime auroral oval at visible wavelengths.
    A third camera is used to monitor the directions of the fields-of-view
    of the auroral cameras with respect to the sunlit Earth and return
    global images of the auroral oval at ultraviolet wavelengths.  The
    VIS instrumentation produces an auroral image of 256 x 256 pixels
    approximately every 24 seconds dependent on the integration time and
    filter selected.  The fields-of-view of the two nighttime auroral
    cameras are 5.6 x 6.3 degrees and 2.8 x 3.3 degrees for the low and
    medium resolution cameras, respectively.  One or more Earth camera
    images of 256 x 256 pixels are produced every five minutes, depending
    on the commanded mode.  The field-of-view of the Earth camera is
    approximately 20 x 20 degrees.
 Reference:
    Frank, L. A., J. B. Sigwarth, J. D. Craven, J. P. Cravens, J. S. Dolan,
        M. R. Dvorsky, J. D. Harvey, P. K. Hardebeck, and D. Muller,
        'The Visible Imaging System (VIS) for the Polar Spacecraft',
        Space Science Review, vol. 71, pp. 297-328, 1995.
 [Note to first-time users:  The first four variables are of primary interest.
    The displayable 256 x 256 image array is in variable 3.  The correct orien-
    tation of a displayed image is explained in the description of variable 3
    below.]
 Data set description:
         The VIS Earth camera key parameter data set is a survey of global
    auroral activity providedby a series of piled images produced by the median-
    filtering of up to five consecutive images.  The displayable image counts
    are in variable 3.
         Some coordinate information is included for viewer orientation.
    Coordinates are calculated for a grid of 18 x 18 points corresponding
    to one pixel out of every 15 x 15 pixel block.  In addition, a rotation
    matrix and a table of distortion-correcting look direction unit vectors
    are provided for the purpose of calculating coordinates for every pixel.
    See the description of variables 14 and 15 below.
         To facilitate viewing of the images, a mapping of pixel value to a
    recommended color table based on the characteristics of the selected
    filter will be included with each image.  See the description of variables
    19, 20, and 21 below.
         A relative intensity scale is provided by the uncompressed count table
    of variable 24.  Approximate intensity levels in kiloRayleighs are given in
    the intensity table of variable 25.  Information on the availability of
    more precisely calibrated intensities can be found on the VIS website at
    URL .http://eiger.physics.uiowa.edu/~vis/software/. 
 Variable descriptions:
    1,2. Center time
        The time assigned to an image is the center time of the integration
        period within a resolution of 50 milliseconds.
    3. Image counts
        Image pixel counts range from 0 to 255.  They are stored in a two-
        dimensional 256 x 256 byte array.  Images from the Earth camera
        (sensor 0) are conventionally displayed with row 1 at the top, row 256
        at the bottom, column 1 on the left, and column 256 on the right.  The
        conventional image display for the low resolution camera (sensor 1) is
        rotated 180 degrees so that the row 1-column 1 pixel is at the lower
        right corner and the row 256-column 256 pixel is at the upper left
        corner.  When displayed in this manner, the spacecraft spin axis is
        oriented to the right in the display, the X component is defined as
        the center of the image look direction, and the Y component is the
        cross product of the spin axis and the look direction.
    4. Sensor number
        0 = Earth camera,
        1 = low resolution camera,
        2 = medium resolution camera.
    5. Half integration time
        This is half the length of the integration period for the image,
        measured in milliseconds.
    6. Filter
        Twelve filters are available for visible imaging; the filter number,
        1-12, is given here.  Ultra-violet imaging is done with one filter only,
        designated here as filter number 0.  In addition, the peak wavelength
        in Angstroms is given for the selected filter.
    7. Presumed altitude of emissions
        The presumed altitude of the emissions seen in the image varies
        with the characteristics of the filter used.
    8. Platform pitch angle
        This is the platform pointing angle of rotation around the spin
        axis, measured from nadir.
  9,10. Geographic coordinates
        Geographic north latitude and east longitude are provided for the
        pixels at these image array locations: every 15th row starting
        with row 1 and ending with row 256, and every 15th column starting
        with column 1 and ending with column 256, for a total of
        18 x 18 coordinate pairs.
 11,12. Spacecraft position and velocity vectors, GCI
        The spacecraft position vector and velocity vector in GCI
        coordinates are for the image center time as given in variables
        1 and 2.
   13. Spacecraft spin axis unit vector, GCI
 14,15. Image-to-GCI rotation matrix and look direction vector table
        The rotation matrix may be used with the look direction vector table to
        obtain pointing vectors in GCI coordinates for each pixel.  The
        resulting vectors may be used to calculate coordinates for the observed
        positions of the pixels.  Software for this purpose is available at URL
         .http://eiger.physics.uiowa.edu/~vis/software/.  The general method 
         used is described below.
        In the image coordinate system, the X axis is the center line-of-sight
        or look direction; the Y axis is the cross product of the spin axis an
        the X axis; and the Z axis is the cross product of the X axis and the
        Y axis.  When the display orientation conventions in the variable 3
        description are applied, the low resolution camera image is rotated so
        that both Earth camera and low resolution camera images are displayed
        with Y axis pointing up and Z axis pointing toward the right.
        To obtain the coordinates of the observed position of a pixel,
        calculate the intersection of the line-of-sight with the surface
        of an oblately spheroidal Earth at the altitude given as
        variable 7.  The equation of the spheroid is
            X**2/(A+ALT)**2 + Y**2/(A+ALT)**2 + Z**2/(B+ALT)**2 = 1
            where A is the Earth radius at the equator,
                  B is the Earth radius at the pole, and
                  ALT is the given altitude.
        The line-of-sight equations are
            (X-SCX)/DX = (Y-SCY)/DY = (Z-SCZ)/DZ
            where (SCX,SCY,SCZ) is the spacecraft position vector GCI, and
                    (DX,DY,DZ)  is the look direction unit vector GCI.
        Solve the line-of-sight equations for two variables in terms
        of the third; substitute into the spheroid equation; and use the
        quadratic formula to solve for the third variable.  Select
        the solution point closer to the spacecraft.
   16. Zenith angle of center line-of-sight at presumed altitude
        This is the angle between the geocentric vector through the
        observed point, assuming the altitude given as variable 7,
        and the reverse of the image center line-of-sight vector.
   17. Sun position unit vector, GCI
   18. Solar zenith angle at observed point of center line-of-sight
        This is the angle of the sun from zenith at the observed point
        of the center line-of-sight, assuming the altitude given as
        variable 7.
   19. RGB color table
        This is the recommended color table to be used with the
        limits given in variables 20 and 21.
 20,21. Low and high color mapping limits
        The low and high color limits are recommended for remapping
        the color table entries, as follows:
            For pixel values less than the low limit, use the color
                at table position 1.
            For pixel values greater than or equal to the low limit
                and less than or equal to the high limit, use the color
                at table position (pix-low)/(high-low) x 255 + 1.
            For pixel values greater than the high limit, use the color
                at table position 256.
   22. Data quality flag
        The data quality word has bits set to 1 when the listed
        conditions are true.  Bit #31 is the most significant bit in the
        word, and it will not be used as a flag.  These are the bit
        assignments:
            bit 0 - image data frame sync error
            bit 1 - image data frame counters error
            bit 2 - image data fill frame flag.
   23. Post gap flag
        The post gap flag has these possible values:
            0 - no gap occurred immediately prior to this record,
            1 - the gap occurred because the instrument was not in
                  a mode that allowed for the production of images for the
                  selected sensor,
            2 - the gap occurred because level zero data were missing,
            3 - the gap occurred because level zero data were too
                  noisy to extract images.
   24. Expanded count table
        The image pixel counts are quasi-logarithmically compressed to the
        range 0-255.  This table gives the average of the uncompressed range
        for each compressed count value.  Table entries 1-256 correspond to
        compressed counts 0-255 respectively.
   25. Intensity table
        Approximate intensity levels in kiloRayleighs are given for each
        compressed count value.  Table entries 1-256 correspond to compressed
        counts 0-255 respectively.  Information on the availability of more
        precisely calibrated intensities can be found on the VIS website at
        URL .http://eiger.physics.uiowa.edu/~vis/software/. 
 Supporting software:
    Supporting software is available on the VIS website at the URL
    .http://eiger.physics.uiowa.edu/~vis/software/.  Included is an IDL program 
    that displays the images with the recommended color bar and provides
    approximate intensities and coordinate data for each pixel.

Modification History

Initial development

Data Variable Descriptions

Presumed altitude of emissions (also quickly shows times when images are available) [AltF]

Earth Camera UV Images (quasi-log cnts), small format display with click-expand (~4 min. res.) [Image_Counts]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> Larger format display with click-expand, no geographic registration [Image_CountsF]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) With geographic grid overlay [Mapped_ImageO]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> [DO NOT USE: UNDER-DEVELOPMENT] Test Display [Mapped_Image]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Azimuthal projection to geographic (fixed sun orientation) [Mapped_ImageP]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Azimuthal projection to magnetic LT and invariant lat [Mapped_ImageM]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie display of images, no geographic registration [Movie_Image]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie, with geographic grid overlay [Mapped_MovieO]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie, azimuthal projection to geographic (fixed sun orientation) [Mapped_MovieP]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie, azimuthal projection to magnetic LT and invariant lat [Mapped_MovieM]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

Earth Camera UV Images (kRay), small format display with click-expand (~4 min. res.) [IImage_Counts]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> Larger format display with click-expand, no geographic registration [IImage_CountsF]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) With geographic grid overlay [Mapped_IImageO]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Azimuthal projection to geographic (fixed sun orientation) [Mapped_IImageP]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Azimuthal projection to magnetic LT and invariant lat [Mapped_IImageM]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie display of images, no geographic registration [Movie_IImage]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie, with geographic grid overlay [Mapped_IMovieO]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie, azimuthal projection to geographic (fixed sun orientation) [Mapped_IMovieP]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie, azimuthal projection to magnetic LT and invariant lat [Mapped_IMovieM]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

Sensor number: 0=Earth Camera,1=Low Resolution Camera,2=Medium Resolution Camera [Sensor]

Platform pointing angle from nadir [PPitch]

Platform angle of rotation around spin axis, measured from nadir in tenths of
degrees

GCI position vector of Polar spacecraft in kilometers. [SC_Pos_GCI]

GCI velocity vector of Polar spacecraft in km/sec. [SC_Vel_GCI]

GCI spin axis unit vector of Polar spacecraft. [SC_SpinV_GCI]

Image header bytes [Headers]

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_LEVEL1_UVI doi:10.48322/kchw-gw93

Description

Primary UVI team data products
CDAWeb displayed images have time-tags shifted 51 seconds back from nominal
Epoch
This corrects that H2 Epochs are telemetry times, not centered collection time
51 seconds is an approximate, typical correction.  Exact values depend on modes
and transition status.

Modification History

Initial work at SPDF 3/20-x/xx/2001 by REM
This dataset was renamed  from po_h2_uvi and po_l1_uvi to po_level1_uvi on
5/6/2005 in CDAWeb

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_OR_DEF doi:10.48322/x2af-pn51

Description

TBS

Modification History

Originated Monday, May 13, 1991
Modified June 13, 1991 for version 2.1
Modified October 2,1991 for new global attributes, incr sizes
Modified 11/11/91 Add sun vector, replace space id with support id
Modified 1992 Feb 11 to use the variable name TIME and type CDF_INT4 instead of 
EPOCH and CDF_EPOCH for the time tags CCR 490
Modified 6/2/92 add project, discipline, source_name, data_version, title, and 
mods to global section; add validmin, validmax, labl_ptr_1 and monoton 
attributes to some variables; put epoch time back in, rename time to 
time_pb5; add label_time to variables
Modified 11/07/92 to use Epoch and Time_PB5 variable name
Modified 6/2/93 add ADID_ref and Logical_file_id
7/5/94 - CCR ISTP 1852 updated CDHF skeleton to CDF standards - JT
9/21/94 - Added 24 new global attributes to log the ephemeris 
comparison summary report from the definitive FDF orbit file.  CCR 1932
11/7/94 - Merged CCR 1852 changes and corrected errors 
made in CCR 1852.  ICCR 1884
12/7/94 - Modified MODS to follow ISTP standards.  ICCR 1885
01/05/95 - add heliocentric coordinate system.  CCR 1889
2/28/95 - added COMMENT1 and COMMENT2 for CCR 
11/03/95 - deleted crn_space for CCR 2154 - RM
09/20/96 - changed CRN to CRN_EARTH for CCR 2269

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_OR_PRE doi:10.48322/5tsm-w805

Description

TBS

Modification History

Originated Monday, May 13, 1991
Modified June 13, 1991 for version 2.1
Modified October 2,1991 for new global attributes, incr sizes
Modified 11/11/91 Add sun vector, replace space id with support id
Modified 1992 Feb 11 to use the variable name TIME and type CDF_INT4 instead of 
EPOCH and CDF_EPOCH for the time tags CCR 490
Modified 6/2/92 add project, discipline, source_name, data_version, title, and 
mods to global section; add validmin, validmax, labl_ptr_1 and monoton 
attributes to some variables; put epoch time back in, rename time to 
time_pb5; add label_time to variables
Modified 11/07/92 to use Epoch and Time_PB5 variable name
Modified 6/2/93 add ADID_ref and Logical_file_id
7/5/94 - CCR ISTP 1852 updated CDHF skeleton to CDF standards - JT
9/21/94 - Added 24 new global attributes to log the ephemeris 
comparison summary report from the definitive FDF orbit file.  CCR 1932
11/7/94 - Merged CCR 1852 changes and corrected errors 
made in CCR 1852.  ICCR 1884
12/7/94 - Modified MODS to follow ISTP standards.  ICCR 1885
01/05/95 - add heliocentric coordinate system.  CCR 1889
2/28/95 - added COMMENT1 and COMMENT2 for CCR 
11/03/95 - deleted crn_space for CCR 2154 - RM
09/20/96 - changed CRN to CRN_EARTH for CCR 2269

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_PA_DEF doi:10.48322/akgc-de65

Description

Based on the FDF DPA algorithm

Modification History

6/11/93 - Original Implementation
4/1/94 - Modified VALIDMIN and VALIDMAX for ORB_ROLL, 
ORB_YAW, GCI_ROLL, GCI_YAW, GSE_ROLL, GSE_YAW, GSM_ROLL, and GSM_YAW
6/7/94 - CCR ISTP 1852, updated CDHF skeleton to CDF standards - JT
11/9/94 - Correct errors made in ccr 1852.  ICCR 1884
04/04/96 - Added despun plat.offset and lock status

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_VIS_EARTH-CAMERA-CALIBRATED doi:10.48322/ma2e-tm75

Description

Instrument functional description:
The VIS is a set of three low-light-level cameras. Two of these cameras share
primary and some secondary optics and are designed to provide images of the
nighttime auroral oval at visible wavelengths. A third camera is used to monitor
the directions of the fields-of-view of the auroral cameras with respect to the
sunlit Earth and return global images of the auroral oval at ultraviolet
wavelengths. The VIS instrumentation produces an auroral image of 256 x 256
pixels approximately every 24 seconds dependent on the integration time and
filter selected.
The fields-of-view of the two nighttime auroral cameras are 5.6 x 6.3 degrees
and 2.8 x 3.3 degrees for the low and medium resolution cameras, respectively.
The medium resolution camera was never activated. One or more Earth camera
images of 256 x 256 pixels are produced every five minutes, depending on the
commanded mode. The field-of-view of the Earth camera is approximately 20 x 20
degrees.
Reference: 
Frank, L. A., J. B. Sigwarth, J. D. Craven, J. P. Cravens, J. S. Dolan, M. R.
Dvorsky, J. D. Harvey, P. K. Hardebeck, and D. Muller, 'The Visible Imaging
System (VIS) for the Polar Spacecraft', Space Science Review, vol. 71, pp.
297-328, 1995.
http://vis.physics.uiowa.edu/vis/vis_description/vis_description.htmlx
[Note to first-time users:  The first six variables are of primary interest. The
displayable 256 x 256 raw image data is in variable 3. The displayable 256 x 256
processed image datais in variable 4. The correct orientation of a displayed
image is explained in the description of variable 3 below.]
Data set description:
The VIS Earth camera data set comprises all Earth camera images for the selected
time period. The raw displayable image counts are in variable 3 while the
processed displayable image counts are in variable 4.
Full coordinate information is included for viewer orientation. 
In addition, a rotation matrix and a table of distortion-correcting look
direction unit vectors are provided for the purpose of calculating coordinates
for every pixel. See the description of variables 20 and 21 below.
To facilitate viewing of the images, a mapping of pixel value to a recommended
color table based on the characteristics of the selected filter will be included
with each image. See the description of variables 25, 26, and 27 below.
A relative intensity scale is provided by the uncompressed count table of
variable 30. Approximate intensity levels in kiloRayleighs are given in the
intensity table of variable 31.
For detailed information on intensities, see Sensitivities_and_Intensities.txt
https://cdaweb.gsfc.nasa.gov/Polar_VIS_docs/SENSITIVITIES_AND_INTENSITIES.TXT
Variable descriptions:
1,2. Center time
The time assigned to an image is the center time of the integration period
within a resolution of 50 milliseconds.
3. Raw (unprocessed) image counts
Image pixel counts range from 0 to 255. They are stored in a two-dimensional 256
x 256 byte array. Images from the Earth camera (sensor 0) are conventionally
displayed with row 1 at the top, row 256 at the bottom,column 1 on the left, and
column 256 on the right. The conventional image display for the low resolution
camera (sensor 1) is rotated 180 degrees so that the row 1-column 1 pixel is at
the lower right corner and the row 256-column 256 pixel is at the upper left
corner. When displayed in this manner, the spacecraft spin axis is oriented to
the right in the display, the X component is defined as the center of the image
look direction, and the Y component is the cross product of the spin axis and
the look direction.
4. Cleaned image counts
These are image pixel counts that have been calibrated using the following
routines.
For the earth camera:
Horizontal Smooth EC 4 if Modified Julian Date (MJD) > 3429 (correction required
after an event in 2005)
Horizontal Smooth EC 6 if MJD > 4307 (correction required after an event in
2007)
Subtract Cosmic Rays
Subtract Slopes (adjusts for biases across the CCD)
Remove Weave (corrects for interference from low resolution camera)
Flat Field (corrects for other characteristics of the CCD) [Note: depending on
viewing geometry, not all irregularities can be fixed completely;  in
particular, a wide diagonal stripe may still be visible]
Dayglow Subtract
Nightglow Minimum
For the low resolution camera:
Subtract Cosmic Rays
Subtract Slopes
Flat Field
Smooth Filter
The data structure is the same as the Raw image counts. See the description of
variable 3 for details.
5. Cleaned image data in kiloRayleighs.
Same data as in variable 4, only in kiloRayleighs.
6. Sensor number
0 = Earth camera
1 = low resolution camera
2 = medium resolution camera (never activated).
7. Half integration time
This is half the length of the integration period for the image, measured in
milliseconds.
8. Filter 
Twelve filters are available for visible imaging; the filter number, 1-12, is
given here. Ultra-violet imaging is done with one filter only, designated here
as filter number 0. In addition, the peak wavelength in Angstroms is given for
the selected filter.
For detailed information on filter characteristics, see
Sensitivities_and_Intensities.txt
https://cdaweb.gsfc.nasa.gov/Polar_VIS_docs/SENSITIVITIES_AND_INTENSITIES.TXT
9. Presumed altitude of emissions
The presumed altitude of the emissions seen in the image varies with the
characteristics of the filter used.
10. Platform pitch angle
This is the platform pointing angle of rotation around the spin axis, measured
from  nadir.
11,12. Geographic coordinates
Geographic north latitude and east longitude are provided for all pixels.
13,14. Right Ascension and Declination of each pixel These values are given in
degrees.
15. Altitude along tangent to line-of-sight for each pixel.
16. Flag to indicate if each pixel is pointed at the earth.
(0/False 1/True)
17,18. Spacecraft position and velocity vectors, GCI
The spacecraft position vector and velocity vector in GCI coordinates are for
the image center time as given in variables 1 and 2.
19. Spacecraft spin axis unit vector, GCI
20,21. Image-to-GCI rotation matrix and look direction vector table
The rotation matrix may be used with the look direction vector table to obtain
pointing vectors in GCI coordinates for each pixel. The resulting vectors may be
used to calculate coordinates for the observed positions of the pixels.
The general method used is described below in Coordinate_Calculation.txt
https://cdaweb.gsfc.nasa.gov/Polar_VIS_docs/Coordinate_Calculation.txt
22. Zenith angle of center line-of-sight at presumed altitude 
This is the angle between the geocentric vector through the observed point,
assuming the altitude given as variable 8, and the  reverse of the image center
line-of-sight vector.
23. Sun position unit vector, GCI
24. Solar zenith angle at observed point of center line-of-sight.
This is the angle of the sun from zenith at the observed point of the center
line-of-sight, assuming the altitude given as variable 8.
25. RGB color table
This is the recommended color table to be used with the limits given in
variables 26 and 27.
 26,27. Low and high color mapping limits
The low and high color limits are recommended for remapping the color table
entries, as follows:
For pixel values less than the low limit, use the color at table position 1.
For pixel values greater than or equal to the low limit and less than or equal
to the high limit, use the color at table position (pix-low)/(high-low) x 255 +
1.
For pixel values greater than the high limit, use the color at table position
256.
28. Data quality flag 
The data quality word has bits set to 1 when the listed conditions are true. Bit
#31 is the most significant bit in the word, and it will not be used as a flag.
These are the bit assignments:
bit 0 - image data frame sync error
bit 1 - image data frame counters error
bit 2 - image data fill frame flag.
29. Post gap flag
The post gap flag has these possible values: 
0 - no gap occurred immediately prior to this record.
1 - the gap occurred because the instrument wasnot in a mode that allowed for
the production of images for the selected sensor
2 - the gap occurred because level zero data were missing
3 - the gap occurred because level zero data were too noisy to extract images.
30. Expanded count table
The image pixel counts are quasi-logarithmically compressed to the range 0-255.
This table gives the average of the uncompressed range for each compressed count
value. Table entries 1-256 correspond to compressed counts 0-255 respectively.
31. Intensity table
Approximate intensity levels in kiloRayleighs are given for each compressed
count value. Table entries 1-256 correspond to compressed counts 0-255
respectively. Intensity calculation is described in
Sensitivities_and_Intensities.txt.
https://cdaweb.gsfc.nasa.gov/Polar_VIS_docs/SENSITIVITIES_AND_INTENSITIES.TXT
Supporting software:
Supporting software is available at
http://vis.physics.uiowa.edu/vis/software/
Included is an IDL program that displays the images with the recommended color
bar, provides approximate intensities and coordinate data for each pixel, and
and includes multiple options for image manipulation.

Modification History

Initial development

Data Variable Descriptions

Uncleaned 256 x 256 Ultra-Violet Image (quasi-logarithmically compressed counts) [Image_Counts_Raw]

Image_Counts_Raw contains the unprocessed displayable image.  The counts have
been quasi-logarithmically compressed by the instrument.  Approximate
uncompressed value for Image_Counts(i,j) isntens_Table
ExpandedCount(Image_Counts(i,j)+1).  Approximate intensity in kR is
Intens_Table(Image_Counts(i,j)+1).The appearance of the actual count value 255
is rare.  When displaying an image,it works best to use the fill value as an
overflow (i.e. brightest) value.

Cleaned and Filtered 256 x 256 Ultra-Violet Image (quasi-logarithmically compressed counts) [Image_Counts_Clean]

Image_Counts contains the cleaned displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) With geographic map overlay [Mapped_ImageO]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Azimuthal projection to geographic (fixed sun orientation) [Mapped_ImageP]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Azimuthal projection to magnetic LT and invariant lat [Mapped_ImageM]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

Movie display of cleaned UV images in QLC counts [Movie_Image]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie, with geographic grid overlay [Mapped_MovieO]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie, azimuthal projection to geographic (fixed sun orientation) [Mapped_MovieP]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie, azimuthal projection to magnetic LT and invariant lat [Mapped_MovieM]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

Cleaned and Filtered UV Images in kRay [IImage_Counts]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) With geographic map overlay [Mapped_ImageO_kRay]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Azimuthal projection to geographic (fixed sun orientation) [Mapped_ImageP_kRay]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Azimuthal projection to magnetic LT and invariant lat [Mapped_ImageM_kRay]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

Movie display of cleaned UV images in kRay [Movie_Image_kRay]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie, with geographic grid overlay [Mapped_MovieO_kRay]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie, azimuthal projection to geographic (fixed sun orientation) [Mapped_MovieP_kRay]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie, azimuthal projection to magnetic LT and invariant lat [Mapped_MovieM_kRay]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

Sensor number: 0=Earth Camera,1=Low Resolution Camera,2=Medium Resolution Camera [Sensor]

Platform pointing angle from nadir [PPitch]

Platform angle of rotation around spin axis, measured from nadir in tenths of
degrees

Geographic latitude grid [Geo_Lat]

Geographic N. latitude for pixels vals

Geographic longitude grid [Geo_Lon]

Geographic E. longitude for pixel vals

GCI position vector of Polar spacecraft in kilometers. [SC_Pos_GCI]

GCI velocity vector of Polar spacecraft in km/sec. [SC_Vel_GCI]

GCI spin axis unit vector of Polar spacecraft. [SC_SpinV_GCI]

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PO_VIS_VISIBLE-IMAGER-CALIBRATED doi:10.48322/1mkd-p917

Description

Instrument functional description:
The VIS is a set of three low-light-level cameras. Two of these cameras share
primary and some secondary optics and are designed to provide images of the
nighttime auroral oval at visible wavelengths. A third camera is used to monitor
the directions of the fields-of-view of the auroral cameras with respect to the
sunlit Earth and return global images of the auroral oval at ultraviolet
wavelengths. The VIS instrumentation produces an auroral image of 256 x 256
pixels approximately every 24 seconds dependent on the integration time and
filter selected.
The fields-of-view of the two nighttime auroral cameras are 5.6 x 6.3 degrees
and 2.8 x 3.3 degrees for the low and medium resolution cameras, respectively.
The medium resolution camera was never activated. One or more Earth camera
images of 256 x 256 pixels are produced every five minutes, depending on the
commanded mode. The field-of-view of the Earth camera is approximately 20 x 20
degrees.
Reference: 
Frank, L. A., J. B. Sigwarth, J. D. Craven, J. P. Cravens, J. S. Dolan, M. R.
Dvorsky, J. D. Harvey, P. K. Hardebeck, and D. Muller, 'The Visible Imaging
System (VIS) for the Polar Spacecraft', Space Science Review, vol. 71, pp.
297-328, 1995.
http://vis.physics.uiowa.edu/vis/vis_description/vis_description.htmlx
[Note to first-time users:  The first six variables are of primary interest. The
displayable 256 x 256 raw image data is in variable 3. The displayable 256 x 256
processed image datais in variable 4. The correct orientation of a displayed
image is explained in the description of variable 3 below.]
Data set description:
The VIS imaging data set comprises all Earth camera and Low Resolution camera
images for the selected time period. The raw displayable image counts are in
variable 3 while the processed displayable image counts are in variable 4.
Full coordinate information is included for viewer orientation. 
In addition, a rotation matrix and a table of distortion-correcting look
direction unit vectors are provided for the purpose of calculating coordinates
for every pixel. See the description of variables 20 and 21 below.
To facilitate viewing of the images, a mapping of pixel value to a recommended
color table based on the characteristics of the selected filter will be included
with each image. See the description of variables 25, 26, and 27 below.
A relative intensity scale is provided by the uncompressed count table of
variable 30. Approximate intensity levels in kiloRayleighs are given in the
intensity table of variable 31.
For detailed information on intensities, see Sensitivities_and_Intensities.txt
http://cdaweb.gsfc.nasa.gov/Polar_VIS_docs/SENSITIVITIES_AND_INTENSITIES.TXT
Variable descriptions:
1,2. Center time
The time assigned to an image is the center time of the integration period
within a resolution of 50 milliseconds.
3. Raw (unprocessed) image counts
Image pixel counts range from 0 to 255. They are stored in a two-dimensional 256
x 256 byte array. Images from the Earth camera (sensor 0) are conventionally
displayed with row 1 at the top, row 256 at the bottom,column 1 on the left, and
column 256 on the right.  The conventional image display for the low resolution
camera (sensor 1) is rotated 180 degrees so that the row 1-column 1 pixel is at
the lower right corner and the row 256-column 256 pixel is at the upper left
corner. When displayed in this manner, the spacecraft spin axis is oriented to
the right in the display, the X component is defined as the center of the image
look direction, and the Y component is the cross product of the spin axis and
the look direction.
4. Cleaned image counts
These are image pixel counts that have been calibrated using the following
routines.
For the earth camera:
Horizontal Smooth EC 4 if Modified Julian Date (MJD) > 3429 (correction required
after an event in 2005)
Horizontal Smooth EC 6 if MJD > 4307 (correction required after an event in
2007)
Subtract Cosmic Rays
Subtract Slopes (adjusts for biases across the CCD)
Remove Weave (corrects for interference from low resolution camera)
Flat Field (corrects for other characteristics of the CCD) [Note: depending on
viewing geometry, not all irregularities can be fixed completely;  in
particular, a wide diagonal stripe may still be visible]
Dayglow Subtract
Nightglow Minimum
For the low resolution camera:
Subtract Cosmic Rays
Subtract Slopes
Flat Field
Smooth Filter
The data structure is the same as the Raw image counts. See the description of
variable 3 for details.
5. Cleaned image data in kiloRayleighs.
Same data as in variable 4, only in kiloRayleighs.
6. Sensor number
0 = Earth camera
1 = low resolution camera
2 = medium resolution camera (never activated).
7. Half integration time
This is half the length of the integration period for the image, measured in
milliseconds.
8. Filter 
Twelve filters are available for visible imaging; the filter number, 1-12, is
given here. Ultra-violet imaging is done with one filter only, designated here
as filter number 0. In addition, the peak wavelength in Angstroms is given for
the selected filter.
For detailed information on filter characteristics, see
Sensitivities_and_Intensities.txt
http://cdaweb.gsfc.nasa.gov/Polar_VIS_docs/SENSITIVITIES_AND_INTENSITIES.TXT
9. Presumed altitude of emissions
The presumed altitude of the emissions seen in the image varies with the
characteristics of the filter used.
10. Field stop position
The field stop may partially occlude the field of view of the low or medium
resolution cameras.  The position is given in 1.5 degree steps.
11. Platform pitch angle
This is the platform pointing angle of rotation around the spin axis, measured
from  nadir.
12,13. Mirror elevation and azimuth angles
For the low or medium resolution camera, the two-axis mirror position is given
in steps measured from the instrument calibration switches.
The low resolution boresight is located at step 68 in azimuth and step 118 in
elevation.
14,15. Geographic coordinates
Geographic north latitude and east longitude are provided for all pixels.
16,17. Right Ascension and Declination of each pixel These values are given in
degrees.
18. Altitude along tangent to line-of-sight for each pixel.
19. Flag to indicate if each pixel is pointed at the earth.
(0/False 1/True)
20,21. Spacecraft position and velocity vectors, GCI
The spacecraft position vector and velocity vector in GCI coordinates are for
the image center time as given in variables 1 and 2.
22. Spacecraft spin axis unit vector, GCI
23,24. Image-to-GCI rotation matrix and look direction vector table
The rotation matrix may be used with the look direction vector table to obtain
pointing vectors in GCI coordinates for each pixel. The resulting vectors may be
used to calculate coordinates for the observed positions of the pixels.
The general method used is described below in Coordinate_Calculation.txt
http://cdaweb.gsfc.nasa.gov/Polar_VIS_docs/Coordinate_Calculation.txt
25. Zenith angle of center line-of-sight at presumed altitude 
This is the angle between the geocentric vector through the observed point,
assuming the altitude given as variable 8, and the  reverse of the image center
line-of-sight vector.
26. Sun position unit vector, GCI
27. Solar zenith angle at observed point of center line-of-sight.
This is the angle of the sun from zenith at the observed point of the center
line-of-sight, assuming the altitude given as variable 8.
28. RGB color table
This is the recommended color table to be used with the limits given in
variables 26 and 27.
29,30. Low and high color mapping limits
The low and high color limits are recommended for remapping the color table
entries, as follows:
For pixel values less than the low limit, use the color at table position 1.
For pixel values greater than or equal to the low limit and less than or equal
to the high limit, use the color at table position (pix-low)/(high-low) x 255 +
1.
For pixel values greater than the high limit, use the color at table position
256.
31. Data quality flag 
The data quality word has bits set to 1 when the listed conditions are true. Bit
#31 is the most significant bit in the word, and it will not be used as a flag.
These are the bit assignments:
bit 0 - image data frame sync error
bit 1 - image data frame counters error
bit 2 - image data fill frame flag.
32. Post gap flag
The post gap flag has these possible values: 
0 - no gap occurred immediately prior to this record.
1 - the gap occurred because the instrument wasnot in a mode that allowed for
the production of images for the selected sensor
2 - the gap occurred because level zero data were missing
3 - the gap occurred because level zero data were too noisy to extract images.
33. Expanded count table
The image pixel counts are quasi-logarithmically compressed to the range 0-255.
This table gives the average of the uncompressed range for each compressed count
value. Table entries 1-256 correspond to compressed counts 0-255 respectively.
34. Intensity table
Approximate intensity levels in kiloRayleighs are given for each compressed
count value. Table entries 1-256 correspond to compressed counts 0-255
respectively. Intensity calculation is described in
Sensitivities_and_Intensities.txt.
http://cdaweb.gsfc.nasa.gov/Polar_VIS_docs/SENSITIVITIES_AND_INTENSITIES.TXT
Supporting software:
Supporting software is available at
http://vis.physics.uiowa.edu/vis/software/
Included is an IDL program that displays the images with the recommended color
bar, provides approximate intensities and coordinate data for each pixel, and
and includes multiple options for image manipulation.

Modification History

Initial development

Data Variable Descriptions

256 x 256 Visible Image (quasi-logarithmically compressed counts) [Image_Counts_Raw]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Tables( Image_Counts(i,j)+1, Filter(1) ).  The
appearance of the actual count value 255 is rare.  When displaying an image,it
works best to use the fill value as an overflow (i.e. brightest) value.

256 x 256 Cleaned and Filtered Visible Image (quasi-logarithmically compressed counts) [Image_Counts_Clean]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Tables( Image_Counts(i,j)+1, Filter(1) ).  The
appearance of the actual count value 255 is rare.  When displaying an image,it
works best to use the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) With geographic map overlay [Mapped_ImageO]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Azimuthal projection to geographic (fixed sun orientation) [Mapped_ImageP]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Azimuthal projection to magnetic LT and invariant lat [Mapped_ImageM]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

Movie display of cleaned UV images in QLC counts [Movie_Image]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie, with geographic grid overlay [Mapped_MovieO]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie, azimuthal projection to geographic (fixed sun orientation) [Mapped_MovieP]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie, azimuthal projection to magnetic LT and invariant lat [Mapped_MovieM]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

UV Images in kRay [IImage_Counts]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) With geographic map overlay [Mapped_ImageO_kRay]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Azimuthal projection to geographic (fixed sun orientation) [Mapped_ImageP_kRay]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Azimuthal projection to magnetic LT and invariant lat [Mapped_ImageM_kRay]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

Movie display of cleaned UV images in kRay [Movie_Image_kRay]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie, with geographic grid overlay [Mapped_MovieO_kRay]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie, azimuthal projection to geographic (fixed sun orientation) [Mapped_MovieP_kRay]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

--> (USE SHORT TIME SPANS) Movie, azimuthal projection to magnetic LT and invariant lat [Mapped_MovieM_kRay]

Image_Counts contains the displayable image.  The counts have been
quasi-logarithmically compressed by the instrument.  Approximate uncompressed
value for Image_Counts(i,j) is ExpandedCount(Image_Counts(i,j)+1).  Approximate
intensity in kR is Intens_Table(Image_Counts(i,j)+1).The appearance of the
actual count value 255 is rare.  When displaying an image,it works best to use
the fill value as an overflow (i.e. brightest) value.

---> Filter number and peak wavelength in Angstroms) [Filter]

Filters #1-12 are visible wavelengths; filter #0 is UV for Earth camera images

---> Presumed altitude of emissions, km. [AltF]

---> Field-stop wheel position (1 step = 1.5 degrees) [Field_Stop]

A field stop may occultsome part of a visible image

---> Platform pointing angle from nadir [PPitch]

Platform angle of rotation around spin axis, measured from nadir in tenths of
degrees

---> Mirror pointing angle, elevation [Mirr_Elv]

Mirror pointing angle out of s/c X-Y plane in steps of ~.08660 degrees

---> Mirror pointing angle, azimuth [Mirr_Azm]

Mirror pointing angle of rotation around spin axis, w/r/t platform position, in
steps of ~.09375 degrees.

Geographic latitude grid [Geo_Lat]

Geographic N. latitude for pixels vals

Geographic longitude grid [Geo_Lon]

Geographic E. longitude for pixel vals

GCI position vector of Polar spacecraft in kilometers. [SC_Pos_GCI]

---> GCI velocity vector of Polar spacecraft in km/sec. [SC_Vel_GCI]

---> GCI spin axis unit vector of Polar spacecraft. [SC_SpinV_GCI]

Data quality flags [D_Qual]

MSB will not be used as a flag; see TEXT for other bit assignments

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_COHO1HR_MERGED_MAG_PLASMA doi:10.48322/19ed-kz70

Description

COHO hourly and daily PSP data were made using PSP high res data from from
CDAWeb at https://cdaweb.gsfc.nasa.gov/The name of the original  plasma data - 
'\PSP_SWP_SPC_L3I\', [ parameter names - Proton bulk velocity from 1-dimensional
Maxwellian fitting, in the [inertial] RTN frame (Only Good Quality); [Total]
proton density, from 1-dimensional Maxwellian fitting. (Only Good Quality);
Proton radial [most probable] thermal speed component from 1-dimensional
Maxwellian fitting. (Only Good Quality).] The name of  the original magnetic
field data: \'PSP_FLD_L2_MAG_RTN_1MIN\'.and heliocentric trajectory from
HELIOWeb at https://omniweb.gsfc.nasa.gov/coho/helios/heli.html 
This file includes the PSP FIELDS Fluxgate Magnetometer data.and densities,
vector velocities, and scalar (radial component) temperatures of the solar wind
protons measured by the Solar Probe Cup (SPC).
 About PSP data in COHOWEB PSP https://omniweb.gsfc.nasa.gov/coho and 
https://cdaweb.gsfc.nasa.gov/.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_AEB

Description

PSP FIELDS AEB.

Modification History

Version 1: Initial version

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_AC_BPF_DV12HG doi:10.48322/Y8GB-3N29

Description

PSP FIELDS Digital Fields Board (DFB), dV12hg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB AC bandpass data consist of peak and average values of the absolute value of
band-passed time series waveform data over a time interval equal to the
reporting cadence. The AC bandpass data have the peak response frequency of each
bin reported in the metadata. The frequency response curves for these bins are
given in [3]. 
The Level 2 data products contained in this data file have been calibrated for
(i) the ~6.3 dB loss associated with forming the bandpass signal [3], (ii) DFB
in-band gain, and (iii) the search coil preamplifier response (when applicable).
Calibrations for the DFB digital filters and analog filters have not been
implemented, as it was determined that these could not be applied accurately to
single numerical values representing a broadband signal response, and because
all bins except the highest frequency bin have a flat gain response equal to 1
due to these filters.  Calibrations for the FIELDS preamplifiers have not been
implemented, as the preamplifier response is flat and equal to 1 through the DFB
frequency range.  Corrections for plasma sheath impedance gain and antenna
effective length have not been applied to voltage sensor signals (these
corrections will be applied in Level 3 DFB data), therefore units for all
voltage sensor quantities are Volts.  Units for all magnetic field quantities
are nT.
The Level 2 data products contained in this data file are in sensor coordinates
(e.g. dV12, dV34 for voltage measurements, and u,v,w for the search coil
magnetometer). 
Time resolution of the DFB AC bandpass data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), the DFB AC bandpass
cadence is typically 1/8 of a NYsecond [2].  Timestamps correspond to the center
time of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1: Initial release version

Data Variable Descriptions

L2 AC Band-pass filter average power for channel dV12hg [psp_fld_l2_dfb_ac_bpf_dV12hg_avg]

Data is in the sensor reference frame. For description see Malaspina et al.,
(2016), JGR, 121, 5088-5096, doi:10.1002/2016JA022344

L2 AC Band-pass filter peak power for channel dV12hg [psp_fld_l2_dfb_ac_bpf_dV12hg_peak]

Data is in the sensor reference frame. For description see Malaspina et al.,
(2016), JGR, 121, 5088-5096, doi:10.1002/2016JA022344

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_AC_BPF_DV34HG doi:10.48322/6NN3-TS64

Description

PSP FIELDS Digital Fields Board (DFB), dV34hg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB AC bandpass data consist of peak and average values of the absolute value of
band-passed time series waveform data over a time interval equal to the
reporting cadence. The AC bandpass data have the peak response frequency of each
bin reported in the metadata. The frequency response curves for these bins are
given in [3]. 
The Level 2 data products contained in this data file have been calibrated for
(i) the ~6.3 dB loss associated with forming the bandpass signal [3], (ii) DFB
in-band gain, and (iii) the search coil preamplifier response (when applicable).
Calibrations for the DFB digital filters and analog filters have not been
implemented, as it was determined that these could not be applied accurately to
single numerical values representing a broadband signal response, and because
all bins except the highest frequency bin have a flat gain response equal to 1
due to these filters.  Calibrations for the FIELDS preamplifiers have not been
implemented, as the preamplifier response is flat and equal to 1 through the DFB
frequency range.  Corrections for plasma sheath impedance gain and antenna
effective length have not been applied to voltage sensor signals (these
corrections will be applied in Level 3 DFB data), therefore units for all
voltage sensor quantities are Volts.  Units for all magnetic field quantities
are nT.
The Level 2 data products contained in this data file are in sensor coordinates
(e.g. dV12, dV34 for voltage measurements, and u,v,w for the search coil
magnetometer). 
Time resolution of the DFB AC bandpass data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), the DFB AC bandpass
cadence is typically 1/8 of a NYsecond [2].  Timestamps correspond to the center
time of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1: Initial release version

Data Variable Descriptions

L2 AC Band-pass filter average power for channel dV34hg [psp_fld_l2_dfb_ac_bpf_dV34hg_avg]

Data is in the sensor reference frame. For description see Malaspina et al.,
(2016), JGR, 121, 5088-5096, doi:10.1002/2016JA022344

L2 AC Band-pass filter peak power for channel dV34hg [psp_fld_l2_dfb_ac_bpf_dV34hg_peak]

Data is in the sensor reference frame. For description see Malaspina et al.,
(2016), JGR, 121, 5088-5096, doi:10.1002/2016JA022344

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_AC_BPF_SCMULFHG doi:10.48322/6SVT-VR86

Description

PSP FIELDS Digital Fields Board (DFB), SCMulfhg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB AC bandpass data consist of peak and average values of the absolute value of
band-passed time series waveform data over a time interval equal to the
reporting cadence. The AC bandpass data have the peak response frequency of each
bin reported in the metadata. The frequency response curves for these bins are
given in [3]. 
The Level 2 data products contained in this data file have been calibrated for
(i) the ~6.3 dB loss associated with forming the bandpass signal [3], (ii) DFB
in-band gain, and (iii) the search coil preamplifier response (when applicable).
Calibrations for the DFB digital filters and analog filters have not been
implemented, as it was determined that these could not be applied accurately to
single numerical values representing a broadband signal response, and because
all bins except the highest frequency bin have a flat gain response equal to 1
due to these filters.  Calibrations for the FIELDS preamplifiers have not been
implemented, as the preamplifier response is flat and equal to 1 through the DFB
frequency range.  Corrections for plasma sheath impedance gain and antenna
effective length have not been applied to voltage sensor signals (these
corrections will be applied in Level 3 DFB data), therefore units for all
voltage sensor quantities are Volts.  Units for all magnetic field quantities
are nT.
The Level 2 data products contained in this data file are in sensor coordinates
(e.g. dV12, dV34 for voltage measurements, and u,v,w for the search coil
magnetometer). 
Time resolution of the DFB AC bandpass data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), the DFB AC bandpass
cadence is typically 1/8 of a NYsecond [2].  Timestamps correspond to the center
time of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1

Data Variable Descriptions

L2 AC Band-pass filter average power for channel SCMulfhg [psp_fld_l2_dfb_ac_bpf_SCMulfhg_avg]

Data is in the sensor reference frame. For description see Malaspina et al.,
(2016), JGR, 121, 5088-5096, doi:10.1002/2016JA022344

L2 AC Band-pass filter peak power for channel SCMulfhg [psp_fld_l2_dfb_ac_bpf_SCMulfhg_peak]

Data is in the sensor reference frame. For description see Malaspina et al.,
(2016), JGR, 121, 5088-5096, doi:10.1002/2016JA022344

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_AC_BPF_SCMUMFHG doi:10.48322/BE3K-1D62

Description

PSP FIELDS Digital Fields Board (DFB), SCMumfhg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB AC bandpass data consist of peak and average values of the absolute value of
band-passed time series waveform data over a time interval equal to the
reporting cadence. The AC bandpass data have the peak response frequency of each
bin reported in the metadata. The frequency response curves for these bins are
given in [3]. 
The Level 2 data products contained in this data file have been calibrated for
(i) the ~6.3 dB loss associated with forming the bandpass signal [3], (ii) DFB
in-band gain, and (iii) the search coil preamplifier response (when applicable).
Calibrations for the DFB digital filters and analog filters have not been
implemented, as it was determined that these could not be applied accurately to
single numerical values representing a broadband signal response, and because
all bins except the highest frequency bin have a flat gain response equal to 1
due to these filters.  Calibrations for the FIELDS preamplifiers have not been
implemented, as the preamplifier response is flat and equal to 1 through the DFB
frequency range.  Corrections for plasma sheath impedance gain and antenna
effective length have not been applied to voltage sensor signals (these
corrections will be applied in Level 3 DFB data), therefore units for all
voltage sensor quantities are Volts.  Units for all magnetic field quantities
are nT.
The Level 2 data products contained in this data file are in sensor coordinates
(e.g. dV12, dV34 for voltage measurements, and u,v,w for the search coil
magnetometer). 
Time resolution of the DFB AC bandpass data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), the DFB AC bandpass
cadence is typically 1/8 of a NYsecond [2].  Timestamps correspond to the center
time of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1: Initial release version

Data Variable Descriptions

L2 AC Band-pass filter average power for channel SCMumfhg [psp_fld_l2_dfb_ac_bpf_SCMumfhg_avg]

Data is in the sensor reference frame. For description see Malaspina et al.,
(2016), JGR, 121, 5088-5096, doi:10.1002/2016JA022344

L2 AC Band-pass filter peak power for channel SCMumfhg [psp_fld_l2_dfb_ac_bpf_SCMumfhg_peak]

Data is in the sensor reference frame. For description see Malaspina et al.,
(2016), JGR, 121, 5088-5096, doi:10.1002/2016JA022344

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_AC_SPEC_DV12HG doi:10.48322/rknp-e976

Description

PSP FIELDS Digital Fields Board (DFB), dV12hg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB AC spectra data consist of power spectral densities as a function of
frequency and time.  These spectra are averaged in both frequency and time as
described in [3]. The spectra have pseudo-logarithmically spaced frequency bins,
with the bin central frequencies reported in the metadata. The AC spectra are
duty-cycled such that spectral averaging takes place over the first 1/8 of any
given NYs (assuming a 1 NYs data cadence).  Less data are averaged by 2^N for
cadences faster than 1 NYs by 2^N.  For cadences slower than 1 NYs, the first
1/8 of each NYs of data included are averaged together to form the reported
data.  
The Level 2 data products contained in this data file have been calibrated for
(i) the Hanning window used in the spectral calculation, (ii) DFB in-band gain,
(iii) DFB analog filter gain response, (iv) DFB digital filter gain response,
(v) the search coil preamplifier response (when applicable), (vi) the bandwidth
of each spectral bin.  Note that compensation for the DFB digital filters will
introduce a non-physical positively sloped power trend at high frequencies when
the non-corrected signal is dominated by noise.  This effect should be examined
carefully when determining spectral slopes and features at the highest
frequencies.  Calibrations for the FIELDS preamplifiers have not been
implemented, as the preamplifier response is flat and equal to 1 through the DFB
frequency range.  Corrections for plasma sheath impedance gain and antenna
effective length have not been applied to voltage sensor data (these corrections
will be applied in Level 3 DFB data), therefore units for all voltage sensor
quantities are Volts^2/Hz.  Units for all magnetic field quantities are nT^2/Hz.
The Level 2 voltage data products contained in this data file are in sensor
coordinates (e.g. dV12, dV34 for voltage measurements). For solar orbits 1 and
2, the search coil magnetometer spectral data is rotated into a non-intuitive
coordinate system (d,e,f). For solar orbits 3 and beyond, magnetic field data
products are in u,v,w search coil magnetometer sensor coordinates.  
To rotate from d,e,f into u,v,w search coil sensor coordinates, use the
following matrix as (IDL notation) spectra_uvw_3vector = R ##
spectra_def_3vector.  
R =  [ [ 0.46834856  , -0.81336422    ,  0.34509170]
       [-0.66921924  , -0.071546954   ,  0.73961249]
       [-0.57688408  , -0.57733845    , -0.57782790]  ]
Time resolution of the DFB AC spectral data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), the DFB AC spectra
data is typically reported each 1 NYsecond [2].  Timestamps correspond to the
center time of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1: Initial release version

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_AC_SPEC_DV34HG doi:10.48322/52bj-8b73

Description

PSP FIELDS Digital Fields Board (DFB), dV34hg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB AC spectra data consist of power spectral densities as a function of
frequency and time.  These spectra are averaged in both frequency and time as
described in [3]. The spectra have pseudo-logarithmically spaced frequency bins,
with the bin central frequencies reported in the metadata. The AC spectra are
duty-cycled such that spectral averaging takes place over the first 1/8 of any
given NYs (assuming a 1 NYs data cadence).  Less data are averaged by 2^N for
cadences faster than 1 NYs by 2^N.  For cadences slower than 1 NYs, the first
1/8 of each NYs of data included are averaged together to form the reported
data.  
The Level 2 data products contained in this data file have been calibrated for
(i) the Hanning window used in the spectral calculation, (ii) DFB in-band gain,
(iii) DFB analog filter gain response, (iv) DFB digital filter gain response,
(v) the search coil preamplifier response (when applicable), (vi) the bandwidth
of each spectral bin.  Note that compensation for the DFB digital filters will
introduce a non-physical positively sloped power trend at high frequencies when
the non-corrected signal is dominated by noise.  This effect should be examined
carefully when determining spectral slopes and features at the highest
frequencies.  Calibrations for the FIELDS preamplifiers have not been
implemented, as the preamplifier response is flat and equal to 1 through the DFB
frequency range.  Corrections for plasma sheath impedance gain and antenna
effective length have not been applied to voltage sensor data (these corrections
will be applied in Level 3 DFB data), therefore units for all voltage sensor
quantities are Volts^2/Hz.  Units for all magnetic field quantities are nT^2/Hz.
The Level 2 voltage data products contained in this data file are in sensor
coordinates (e.g. dV12, dV34 for voltage measurements). For solar orbits 1 and
2, the search coil magnetometer spectral data is rotated into a non-intuitive
coordinate system (d,e,f). For solar orbits 3 and beyond, magnetic field data
products are in u,v,w search coil magnetometer sensor coordinates.  
To rotate from d,e,f into u,v,w search coil sensor coordinates, use the
following matrix as (IDL notation) spectra_uvw_3vector = R ##
spectra_def_3vector.  
R =  [ [ 0.46834856  , -0.81336422    ,  0.34509170]
       [-0.66921924  , -0.071546954   ,  0.73961249]
       [-0.57688408  , -0.57733845    , -0.57782790]  ]
Time resolution of the DFB AC spectral data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), the DFB AC spectra
data is typically reported each 1 NYsecond [2].  Timestamps correspond to the
center time of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1: Initial release version

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_AC_SPEC_SCMDLFHG doi:10.48322/ncfd-vr25

Description

PSP FIELDS Digital Fields Board (DFB), SCMdlfhg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB AC spectra data consist of power spectral densities as a function of
frequency and time.  These spectra are averaged in both frequency and time as
described in [3]. The spectra have pseudo-logarithmically spaced frequency bins,
with the bin central frequencies reported in the metadata. The AC spectra are
duty-cycled such that spectral averaging takes place over the first 1/8 of any
given NYs (assuming a 1 NYs data cadence).  Less data are averaged by 2^N for
cadences faster than 1 NYs by 2^N.  For cadences slower than 1 NYs, the first
1/8 of each NYs of data included are averaged together to form the reported
data.  
The Level 2 data products contained in this data file have been calibrated for
(i) the Hanning window used in the spectral calculation, (ii) DFB in-band gain,
(iii) DFB analog filter gain response, (iv) DFB digital filter gain response,
(v) the search coil preamplifier response (when applicable), (vi) the bandwidth
of each spectral bin.  Note that compensation for the DFB digital filters will
introduce a non-physical positively sloped power trend at high frequencies when
the non-corrected signal is dominated by noise.  This effect should be examined
carefully when determining spectral slopes and features at the highest
frequencies.  Calibrations for the FIELDS preamplifiers have not been
implemented, as the preamplifier response is flat and equal to 1 through the DFB
frequency range.  Corrections for plasma sheath impedance gain and antenna
effective length have not been applied to voltage sensor data (these corrections
will be applied in Level 3 DFB data), therefore units for all voltage sensor
quantities are Volts^2/Hz.  Units for all magnetic field quantities are nT^2/Hz.
The Level 2 voltage data products contained in this data file are in sensor
coordinates (e.g. dV12, dV34 for voltage measurements). For solar orbits 1 and
2, the search coil magnetometer spectral data is rotated into a non-intuitive
coordinate system (d,e,f). For solar orbits 3 and beyond, magnetic field data
products are in u,v,w search coil magnetometer sensor coordinates.  
To rotate from d,e,f into u,v,w search coil sensor coordinates, use the
following matrix as (IDL notation) spectra_uvw_3vector = R ##
spectra_def_3vector.  
R =  [ [ 0.46834856  , -0.81336422    ,  0.34509170]
       [-0.66921924  , -0.071546954   ,  0.73961249]
       [-0.57688408  , -0.57733845    , -0.57782790]  ]
Time resolution of the DFB AC spectral data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), the DFB AC spectra
data is typically reported each 1 NYsecond [2].  Timestamps correspond to the
center time of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_AC_SPEC_SCMELFHG doi:10.48322/qj28-mq33

Description

PSP FIELDS Digital Fields Board (DFB), SCMelfhg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB AC spectra data consist of power spectral densities as a function of
frequency and time.  These spectra are averaged in both frequency and time as
described in [3]. The spectra have pseudo-logarithmically spaced frequency bins,
with the bin central frequencies reported in the metadata. The AC spectra are
duty-cycled such that spectral averaging takes place over the first 1/8 of any
given NYs (assuming a 1 NYs data cadence).  Less data are averaged by 2^N for
cadences faster than 1 NYs by 2^N.  For cadences slower than 1 NYs, the first
1/8 of each NYs of data included are averaged together to form the reported
data.  
The Level 2 data products contained in this data file have been calibrated for
(i) the Hanning window used in the spectral calculation, (ii) DFB in-band gain,
(iii) DFB analog filter gain response, (iv) DFB digital filter gain response,
(v) the search coil preamplifier response (when applicable), (vi) the bandwidth
of each spectral bin.  Note that compensation for the DFB digital filters will
introduce a non-physical positively sloped power trend at high frequencies when
the non-corrected signal is dominated by noise.  This effect should be examined
carefully when determining spectral slopes and features at the highest
frequencies.  Calibrations for the FIELDS preamplifiers have not been
implemented, as the preamplifier response is flat and equal to 1 through the DFB
frequency range.  Corrections for plasma sheath impedance gain and antenna
effective length have not been applied to voltage sensor data (these corrections
will be applied in Level 3 DFB data), therefore units for all voltage sensor
quantities are Volts^2/Hz.  Units for all magnetic field quantities are nT^2/Hz.
The Level 2 voltage data products contained in this data file are in sensor
coordinates (e.g. dV12, dV34 for voltage measurements). For solar orbits 1 and
2, the search coil magnetometer spectral data is rotated into a non-intuitive
coordinate system (d,e,f). For solar orbits 3 and beyond, magnetic field data
products are in u,v,w search coil magnetometer sensor coordinates.  
To rotate from d,e,f into u,v,w search coil sensor coordinates, use the
following matrix as (IDL notation) spectra_uvw_3vector = R ##
spectra_def_3vector.  
R =  [ [ 0.46834856  , -0.81336422    ,  0.34509170]
       [-0.66921924  , -0.071546954   ,  0.73961249]
       [-0.57688408  , -0.57733845    , -0.57782790]  ]
Time resolution of the DFB AC spectral data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), the DFB AC spectra
data is typically reported each 1 NYsecond [2].  Timestamps correspond to the
center time of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_AC_SPEC_SCMFLFHG doi:10.48322/p0th-a636

Description

PSP FIELDS Digital Fields Board (DFB), SCMflfhg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB AC spectra data consist of power spectral densities as a function of
frequency and time.  These spectra are averaged in both frequency and time as
described in [3]. The spectra have pseudo-logarithmically spaced frequency bins,
with the bin central frequencies reported in the metadata. The AC spectra are
duty-cycled such that spectral averaging takes place over the first 1/8 of any
given NYs (assuming a 1 NYs data cadence).  Less data are averaged by 2^N for
cadences faster than 1 NYs by 2^N.  For cadences slower than 1 NYs, the first
1/8 of each NYs of data included are averaged together to form the reported
data.  
The Level 2 data products contained in this data file have been calibrated for
(i) the Hanning window used in the spectral calculation, (ii) DFB in-band gain,
(iii) DFB analog filter gain response, (iv) DFB digital filter gain response,
(v) the search coil preamplifier response (when applicable), (vi) the bandwidth
of each spectral bin.  Note that compensation for the DFB digital filters will
introduce a non-physical positively sloped power trend at high frequencies when
the non-corrected signal is dominated by noise.  This effect should be examined
carefully when determining spectral slopes and features at the highest
frequencies.  Calibrations for the FIELDS preamplifiers have not been
implemented, as the preamplifier response is flat and equal to 1 through the DFB
frequency range.  Corrections for plasma sheath impedance gain and antenna
effective length have not been applied to voltage sensor data (these corrections
will be applied in Level 3 DFB data), therefore units for all voltage sensor
quantities are Volts^2/Hz.  Units for all magnetic field quantities are nT^2/Hz.
The Level 2 voltage data products contained in this data file are in sensor
coordinates (e.g. dV12, dV34 for voltage measurements). For solar orbits 1 and
2, the search coil magnetometer spectral data is rotated into a non-intuitive
coordinate system (d,e,f). For solar orbits 3 and beyond, magnetic field data
products are in u,v,w search coil magnetometer sensor coordinates.  
To rotate from d,e,f into u,v,w search coil sensor coordinates, use the
following matrix as (IDL notation) spectra_uvw_3vector = R ##
spectra_def_3vector.  
R =  [ [ 0.46834856  , -0.81336422    ,  0.34509170]
       [-0.66921924  , -0.071546954   ,  0.73961249]
       [-0.57688408  , -0.57733845    , -0.57782790]  ]
Time resolution of the DFB AC spectral data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), the DFB AC spectra
data is typically reported each 1 NYsecond [2].  Timestamps correspond to the
center time of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_AC_SPEC_SCMMF doi:10.48322/16qy-w286

Description

PSP FIELDS Digital Fields Board (DFB), SCMmf data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB AC spectra data consist of power spectral densities as a function of
frequency and time.  These spectra are averaged in both frequency and time as
described in [3]. The spectra have pseudo-logarithmically spaced frequency bins,
with the bin central frequencies reported in the metadata. The AC spectra are
duty-cycled such that spectral averaging takes place over the first 1/8 of any
given NYs (assuming a 1 NYs data cadence).  Less data are averaged by 2^N for
cadences faster than 1 NYs by 2^N.  For cadences slower than 1 NYs, the first
1/8 of each NYs of data included are averaged together to form the reported
data.  
The Level 2 data products contained in this data file have been calibrated for
(i) the Hanning window used in the spectral calculation, (ii) DFB in-band gain,
(iii) DFB analog filter gain response, (iv) DFB digital filter gain response,
(v) the search coil preamplifier response (when applicable), (vi) the bandwidth
of each spectral bin.  Note that compensation for the DFB digital filters will
introduce a non-physical positively sloped power trend at high frequencies when
the non-corrected signal is dominated by noise.  This effect should be examined
carefully when determining spectral slopes and features at the highest
frequencies.  Calibrations for the FIELDS preamplifiers have not been
implemented, as the preamplifier response is flat and equal to 1 through the DFB
frequency range.  Corrections for plasma sheath impedance gain and antenna
effective length have not been applied to voltage sensor data (these corrections
will be applied in Level 3 DFB data), therefore units for all voltage sensor
quantities are Volts^2/Hz.  Units for all magnetic field quantities are nT^2/Hz.
The Level 2 voltage data products contained in this data file are in sensor
coordinates (e.g. dV12, dV34 for voltage measurements). For solar orbits 1 and
2, the search coil magnetometer spectral data is rotated into a non-intuitive
coordinate system (d,e,f). For solar orbits 3 and beyond, magnetic field data
products are in u,v,w search coil magnetometer sensor coordinates.  
To rotate from d,e,f into u,v,w search coil sensor coordinates, use the
following matrix as (IDL notation) spectra_uvw_3vector = R ##
spectra_def_3vector.  
R =  [ [ 0.46834856  , -0.81336422    ,  0.34509170]
       [-0.66921924  , -0.071546954   ,  0.73961249]
       [-0.57688408  , -0.57733845    , -0.57782790]  ]
Time resolution of the DFB AC spectral data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), the DFB AC spectra
data is typically reported each 1 NYsecond [2].  Timestamps correspond to the
center time of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_AC_SPEC_SCMULFLG doi:10.48322/2nwb-7q79

Description

PSP FIELDS Digital Fields Board (DFB), SCMulflg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB AC spectra data consist of power spectral densities as a function of
frequency and time.  These spectra are averaged in both frequency and time as
described in [3]. The spectra have pseudo-logarithmically spaced frequency bins,
with the bin central frequencies reported in the metadata. The AC spectra are
duty-cycled such that spectral averaging takes place over the first 1/8 of any
given NYs (assuming a 1 NYs data cadence).  Less data are averaged by 2^N for
cadences faster than 1 NYs by 2^N.  For cadences slower than 1 NYs, the first
1/8 of each NYs of data included are averaged together to form the reported
data.  
The Level 2 data products contained in this data file have been calibrated for
(i) the Hanning window used in the spectral calculation, (ii) DFB in-band gain,
(iii) DFB analog filter gain response, (iv) DFB digital filter gain response,
(v) the search coil preamplifier response (when applicable), (vi) the bandwidth
of each spectral bin.  Note that compensation for the DFB digital filters will
introduce a non-physical positively sloped power trend at high frequencies when
the non-corrected signal is dominated by noise.  This effect should be examined
carefully when determining spectral slopes and features at the highest
frequencies.  Calibrations for the FIELDS preamplifiers have not been
implemented, as the preamplifier response is flat and equal to 1 through the DFB
frequency range.  Corrections for plasma sheath impedance gain and antenna
effective length have not been applied to voltage sensor data (these corrections
will be applied in Level 3 DFB data), therefore units for all voltage sensor
quantities are Volts^2/Hz.  Units for all magnetic field quantities are nT^2/Hz.
The Level 2 voltage data products contained in this data file are in sensor
coordinates (e.g. dV12, dV34 for voltage measurements). For solar orbits 1 and
2, the search coil magnetometer spectral data is rotated into a non-intuitive
coordinate system (d,e,f). For solar orbits 3 and beyond, magnetic field data
products are in u,v,w search coil magnetometer sensor coordinates.  
To rotate from d,e,f into u,v,w search coil sensor coordinates, use the
following matrix as (IDL notation) spectra_uvw_3vector = R ##
spectra_def_3vector.  
R =  [ [ 0.46834856  , -0.81336422    ,  0.34509170]
       [-0.66921924  , -0.071546954   ,  0.73961249]
       [-0.57688408  , -0.57733845    , -0.57782790]  ]
Time resolution of the DFB AC spectral data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), the DFB AC spectra
data is typically reported each 1 NYsecond [2].  Timestamps correspond to the
center time of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1: Initial release version

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_AC_SPEC_SCMVLFHG doi:10.48322/83y8-hg94

Description

PSP FIELDS Digital Fields Board (DFB), SCMvlfhg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB AC spectra data consist of power spectral densities as a function of
frequency and time.  These spectra are averaged in both frequency and time as
described in [3]. The spectra have pseudo-logarithmically spaced frequency bins,
with the bin central frequencies reported in the metadata. The AC spectra are
duty-cycled such that spectral averaging takes place over the first 1/8 of any
given NYs (assuming a 1 NYs data cadence).  Less data are averaged by 2^N for
cadences faster than 1 NYs by 2^N.  For cadences slower than 1 NYs, the first
1/8 of each NYs of data included are averaged together to form the reported
data.  
The Level 2 data products contained in this data file have been calibrated for
(i) the Hanning window used in the spectral calculation, (ii) DFB in-band gain,
(iii) DFB analog filter gain response, (iv) DFB digital filter gain response,
(v) the search coil preamplifier response (when applicable), (vi) the bandwidth
of each spectral bin.  Note that compensation for the DFB digital filters will
introduce a non-physical positively sloped power trend at high frequencies when
the non-corrected signal is dominated by noise.  This effect should be examined
carefully when determining spectral slopes and features at the highest
frequencies.  Calibrations for the FIELDS preamplifiers have not been
implemented, as the preamplifier response is flat and equal to 1 through the DFB
frequency range.  Corrections for plasma sheath impedance gain and antenna
effective length have not been applied to voltage sensor data (these corrections
will be applied in Level 3 DFB data), therefore units for all voltage sensor
quantities are Volts^2/Hz.  Units for all magnetic field quantities are nT^2/Hz.
The Level 2 voltage data products contained in this data file are in sensor
coordinates (e.g. dV12, dV34 for voltage measurements). For solar orbits 1 and
2, the search coil magnetometer spectral data is rotated into a non-intuitive
coordinate system (d,e,f). For solar orbits 3 and beyond, magnetic field data
products are in u,v,w search coil magnetometer sensor coordinates.  
To rotate from d,e,f into u,v,w search coil sensor coordinates, use the
following matrix as (IDL notation) spectra_uvw_3vector = R ##
spectra_def_3vector.  
R =  [ [ 0.46834856  , -0.81336422    ,  0.34509170]
       [-0.66921924  , -0.071546954   ,  0.73961249]
       [-0.57688408  , -0.57733845    , -0.57782790]  ]
Time resolution of the DFB AC spectral data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), the DFB AC spectra
data is typically reported each 1 NYsecond [2].  Timestamps correspond to the
center time of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1: Initial release version

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_AC_SPEC_V5HG doi:10.48322/g6gw-8t30

Description

PSP FIELDS Digital Fields Board (DFB), V5hg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB AC spectra data consist of power spectral densities as a function of
frequency and time.  These spectra are averaged in both frequency and time as
described in [3]. The spectra have pseudo-logarithmically spaced frequency bins,
with the bin central frequencies reported in the metadata. The AC spectra are
duty-cycled such that spectral averaging takes place over the first 1/8 of any
given NYs (assuming a 1 NYs data cadence).  Less data are averaged by 2^N for
cadences faster than 1 NYs by 2^N.  For cadences slower than 1 NYs, the first
1/8 of each NYs of data included are averaged together to form the reported
data.  
The Level 2 data products contained in this data file have been calibrated for
(i) the Hanning window used in the spectral calculation, (ii) DFB in-band gain,
(iii) DFB analog filter gain response, (iv) DFB digital filter gain response,
(v) the search coil preamplifier response (when applicable), (vi) the bandwidth
of each spectral bin.  Note that compensation for the DFB digital filters will
introduce a non-physical positively sloped power trend at high frequencies when
the non-corrected signal is dominated by noise.  This effect should be examined
carefully when determining spectral slopes and features at the highest
frequencies.  Calibrations for the FIELDS preamplifiers have not been
implemented, as the preamplifier response is flat and equal to 1 through the DFB
frequency range.  Corrections for plasma sheath impedance gain and antenna
effective length have not been applied to voltage sensor data (these corrections
will be applied in Level 3 DFB data), therefore units for all voltage sensor
quantities are Volts^2/Hz.  Units for all magnetic field quantities are nT^2/Hz.
The Level 2 voltage data products contained in this data file are in sensor
coordinates (e.g. dV12, dV34 for voltage measurements). For solar orbits 1 and
2, the search coil magnetometer spectral data is rotated into a non-intuitive
coordinate system (d,e,f). For solar orbits 3 and beyond, magnetic field data
products are in u,v,w search coil magnetometer sensor coordinates.  
To rotate from d,e,f into u,v,w search coil sensor coordinates, use the
following matrix as (IDL notation) spectra_uvw_3vector = R ##
spectra_def_3vector.  
R =  [ [ 0.46834856  , -0.81336422    ,  0.34509170]
       [-0.66921924  , -0.071546954   ,  0.73961249]
       [-0.57688408  , -0.57733845    , -0.57782790]  ]
Time resolution of the DFB AC spectral data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), the DFB AC spectra
data is typically reported each 1 NYsecond [2].  Timestamps correspond to the
center time of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1: Initial release version

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_AC_XSPEC_DV12HG_DV34HG doi:10.48322/2a1q-xm10

Description

PSP FIELDS Digital Fields Board (DFB), dV12hg x dV34hg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB AC cross spectra data consist of, for a pair of input channels, (i) power
spectral densities (auto spectra, e.g. FT1 x FT1*), (ii) real and imaginary
parts of the spectral cross term (FT1 x FT2*), (iii) coherence, and (iv) phase,
all as a function of frequency and time.  Coherence and phase are defined in
[3].  These cross spectra are averaged in both frequency and time as described
in [3]. The cross spectra have either 56 or 96 bins (selectable) with the bin
central frequencies reported in the metadata. The AC cross spectra are
duty-cycled such that spectral averaging takes place over the first 1/8 of any
given NYs (assuming a 1 NYs data cadence).  Less data are averaged by 2^N for
cadences faster than 1 NYs by 2^N.  For cadences slower than 1 NYs, the first
1/8 of each NYs of data included are averaged together to form the reported
data.
The Level 2 data products contained in this data file have been calibrated for
(i) the Hanning window used in the spectral calculation, (ii) DFB in-band gain,
(iii) DFB analog filter gain response, (iv) DFB digital filter gain response,
(v) the search coil preamplifier response (when applicable), (vi) the bandwidth
of each spectral bin.  Note that compensation for the DFB digital filters will
introduce a non-physical positively sloped power trend at high frequencies when
the non-corrected signal is dominated by noise.  This effect should be examined
carefully when determining spectral slopes and features.  Calibrations for the
FIELDS preamplifiers have not been implemented, as the preamplifier response is
flat and equal to 1 through the DFB frequency range.  Corrections for plasma
sheath impedance gain and antenna effective length have not been applied to
voltage sensor data (these corrections will be applied in Level 3 DFB data),
therefore units for all voltage sensor quantities are Volts^2/Hz.  Units for all
magnetic field quantities are nT^2/Hz. Coherence is unitless.  Units for phase
are degrees. 
The Level 2 voltage data products contained in this data file are in sensor
coordinates (e.g. dV12, dV34 for voltage measurements). For solar orbits 1 and
2, the search coil magnetometer cross spectral data is rotated into a
non-intuitive coordinate system (d,e,f). For solar orbits 3 and beyond, magnetic
field data products are in the u,v,w search coil magnetometer sensor
coordinates.  
To rotate from d,e,f into u,v,w search coil sensor coordinates, use the
following matrix as (IDL notation) spectra_uvw_vector = R ## spectra_def_vector.
 
R =  [ [ 0.46834856  , -0.81336422    ,  0.34509170]
       [-0.66921924  , -0.071546954   ,  0.73961249]
       [-0.57688408  , -0.57733845    , -0.57782790]  ]
For some orbits, sufficient spectral information exists in the auto- and
cross-spectra to determine wave ellipticity, planarity, and wave normal angles. 
One method for accomplishing this is presented in [4]. 
Time resolution of the DFB AC cross spectral data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), cadence for the DFB AC
cross spectra is typically 1 NYsecond [2].  Timestamps correspond to the center
time of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344 
4. Santolik, O., Parrot, M., Lefeuvre, F. (2003) Radio Science, 38, 1010.
https://doi.org/10.1029/2000RS002523

Modification History

Version 1: Initial release version
Version 2: Corrected sign of imaginary part of cross spectra

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_AC_XSPEC_SCMDLFHG_SCMELFHG doi:10.48322/kt78-6c57

Description

PSP FIELDS Digital Fields Board (DFB), SCMdlfhg x SCMelfhg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB AC cross spectra data consist of, for a pair of input channels, (i) power
spectral densities (auto spectra, e.g. FT1 x FT1*), (ii) real and imaginary
parts of the spectral cross term (FT1 x FT2*), (iii) coherence, and (iv) phase,
all as a function of frequency and time.  Coherence and phase are defined in
[3].  These cross spectra are averaged in both frequency and time as described
in [3]. The cross spectra have either 56 or 96 bins (selectable) with the bin
central frequencies reported in the metadata. The AC cross spectra are
duty-cycled such that spectral averaging takes place over the first 1/8 of any
given NYs (assuming a 1 NYs data cadence).  Less data are averaged by 2^N for
cadences faster than 1 NYs by 2^N.  For cadences slower than 1 NYs, the first
1/8 of each NYs of data included are averaged together to form the reported
data.
The Level 2 data products contained in this data file have been calibrated for
(i) the Hanning window used in the spectral calculation, (ii) DFB in-band gain,
(iii) DFB analog filter gain response, (iv) DFB digital filter gain response,
(v) the search coil preamplifier response (when applicable), (vi) the bandwidth
of each spectral bin.  Note that compensation for the DFB digital filters will
introduce a non-physical positively sloped power trend at high frequencies when
the non-corrected signal is dominated by noise.  This effect should be examined
carefully when determining spectral slopes and features.  Calibrations for the
FIELDS preamplifiers have not been implemented, as the preamplifier response is
flat and equal to 1 through the DFB frequency range.  Corrections for plasma
sheath impedance gain and antenna effective length have not been applied to
voltage sensor data (these corrections will be applied in Level 3 DFB data),
therefore units for all voltage sensor quantities are Volts^2/Hz.  Units for all
magnetic field quantities are nT^2/Hz. Coherence is unitless.  Units for phase
are degrees. 
The Level 2 voltage data products contained in this data file are in sensor
coordinates (e.g. dV12, dV34 for voltage measurements). For solar orbits 1 and
2, the search coil magnetometer cross spectral data is rotated into a
non-intuitive coordinate system (d,e,f). For solar orbits 3 and beyond, magnetic
field data products are in the u,v,w search coil magnetometer sensor
coordinates.  
To rotate from d,e,f into u,v,w search coil sensor coordinates, use the
following matrix as (IDL notation) spectra_uvw_vector = R ## spectra_def_vector.
 
R =  [ [ 0.46834856  , -0.81336422    ,  0.34509170]
       [-0.66921924  , -0.071546954   ,  0.73961249]
       [-0.57688408  , -0.57733845    , -0.57782790]  ]
For some orbits, sufficient spectral information exists in the auto- and
cross-spectra to determine wave ellipticity, planarity, and wave normal angles. 
One method for accomplishing this is presented in [4]. 
Time resolution of the DFB AC cross spectral data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), cadence for the DFB AC
cross spectra is typically 1 NYsecond [2].  Timestamps correspond to the center
time of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344 
4. Santolik, O., Parrot, M., Lefeuvre, F. (2003) Radio Science, 38, 1010.
https://doi.org/10.1029/2000RS002523

Modification History

Version 1: Initial release version
Version 2: Corrected sign of imaginary part of cross spectra

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_AC_XSPEC_SCMDLFHG_SCMFLFHG doi:10.48322/scxb-g511

Description

PSP FIELDS Digital Fields Board (DFB), SCMdlfhg x SCMflfhg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB AC cross spectra data consist of, for a pair of input channels, (i) power
spectral densities (auto spectra, e.g. FT1 x FT1*), (ii) real and imaginary
parts of the spectral cross term (FT1 x FT2*), (iii) coherence, and (iv) phase,
all as a function of frequency and time.  Coherence and phase are defined in
[3].  These cross spectra are averaged in both frequency and time as described
in [3]. The cross spectra have either 56 or 96 bins (selectable) with the bin
central frequencies reported in the metadata. The AC cross spectra are
duty-cycled such that spectral averaging takes place over the first 1/8 of any
given NYs (assuming a 1 NYs data cadence).  Less data are averaged by 2^N for
cadences faster than 1 NYs by 2^N.  For cadences slower than 1 NYs, the first
1/8 of each NYs of data included are averaged together to form the reported
data.
The Level 2 data products contained in this data file have been calibrated for
(i) the Hanning window used in the spectral calculation, (ii) DFB in-band gain,
(iii) DFB analog filter gain response, (iv) DFB digital filter gain response,
(v) the search coil preamplifier response (when applicable), (vi) the bandwidth
of each spectral bin.  Note that compensation for the DFB digital filters will
introduce a non-physical positively sloped power trend at high frequencies when
the non-corrected signal is dominated by noise.  This effect should be examined
carefully when determining spectral slopes and features.  Calibrations for the
FIELDS preamplifiers have not been implemented, as the preamplifier response is
flat and equal to 1 through the DFB frequency range.  Corrections for plasma
sheath impedance gain and antenna effective length have not been applied to
voltage sensor data (these corrections will be applied in Level 3 DFB data),
therefore units for all voltage sensor quantities are Volts^2/Hz.  Units for all
magnetic field quantities are nT^2/Hz. Coherence is unitless.  Units for phase
are degrees. 
The Level 2 voltage data products contained in this data file are in sensor
coordinates (e.g. dV12, dV34 for voltage measurements). For solar orbits 1 and
2, the search coil magnetometer cross spectral data is rotated into a
non-intuitive coordinate system (d,e,f). For solar orbits 3 and beyond, magnetic
field data products are in the u,v,w search coil magnetometer sensor
coordinates.  
To rotate from d,e,f into u,v,w search coil sensor coordinates, use the
following matrix as (IDL notation) spectra_uvw_vector = R ## spectra_def_vector.
 
R =  [ [ 0.46834856  , -0.81336422    ,  0.34509170]
       [-0.66921924  , -0.071546954   ,  0.73961249]
       [-0.57688408  , -0.57733845    , -0.57782790]  ]
For some orbits, sufficient spectral information exists in the auto- and
cross-spectra to determine wave ellipticity, planarity, and wave normal angles. 
One method for accomplishing this is presented in [4]. 
Time resolution of the DFB AC cross spectral data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), cadence for the DFB AC
cross spectra is typically 1 NYsecond [2].  Timestamps correspond to the center
time of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344 
4. Santolik, O., Parrot, M., Lefeuvre, F. (2003) Radio Science, 38, 1010.
https://doi.org/10.1029/2000RS002523

Modification History

Version 1: Initial release version
Version 2: Corrected sign of imaginary part of cross spectra

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_AC_XSPEC_SCMELFHG_SCMFLFHG doi:10.48322/srne-rk07

Description

PSP FIELDS Digital Fields Board (DFB), SCMelfhg x SCMflfhg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB AC cross spectra data consist of, for a pair of input channels, (i) power
spectral densities (auto spectra, e.g. FT1 x FT1*), (ii) real and imaginary
parts of the spectral cross term (FT1 x FT2*), (iii) coherence, and (iv) phase,
all as a function of frequency and time.  Coherence and phase are defined in
[3].  These cross spectra are averaged in both frequency and time as described
in [3]. The cross spectra have either 56 or 96 bins (selectable) with the bin
central frequencies reported in the metadata. The AC cross spectra are
duty-cycled such that spectral averaging takes place over the first 1/8 of any
given NYs (assuming a 1 NYs data cadence).  Less data are averaged by 2^N for
cadences faster than 1 NYs by 2^N.  For cadences slower than 1 NYs, the first
1/8 of each NYs of data included are averaged together to form the reported
data.
The Level 2 data products contained in this data file have been calibrated for
(i) the Hanning window used in the spectral calculation, (ii) DFB in-band gain,
(iii) DFB analog filter gain response, (iv) DFB digital filter gain response,
(v) the search coil preamplifier response (when applicable), (vi) the bandwidth
of each spectral bin.  Note that compensation for the DFB digital filters will
introduce a non-physical positively sloped power trend at high frequencies when
the non-corrected signal is dominated by noise.  This effect should be examined
carefully when determining spectral slopes and features.  Calibrations for the
FIELDS preamplifiers have not been implemented, as the preamplifier response is
flat and equal to 1 through the DFB frequency range.  Corrections for plasma
sheath impedance gain and antenna effective length have not been applied to
voltage sensor data (these corrections will be applied in Level 3 DFB data),
therefore units for all voltage sensor quantities are Volts^2/Hz.  Units for all
magnetic field quantities are nT^2/Hz. Coherence is unitless.  Units for phase
are degrees. 
The Level 2 voltage data products contained in this data file are in sensor
coordinates (e.g. dV12, dV34 for voltage measurements). For solar orbits 1 and
2, the search coil magnetometer cross spectral data is rotated into a
non-intuitive coordinate system (d,e,f). For solar orbits 3 and beyond, magnetic
field data products are in the u,v,w search coil magnetometer sensor
coordinates.  
To rotate from d,e,f into u,v,w search coil sensor coordinates, use the
following matrix as (IDL notation) spectra_uvw_vector = R ## spectra_def_vector.
 
R =  [ [ 0.46834856  , -0.81336422    ,  0.34509170]
       [-0.66921924  , -0.071546954   ,  0.73961249]
       [-0.57688408  , -0.57733845    , -0.57782790]  ]
For some orbits, sufficient spectral information exists in the auto- and
cross-spectra to determine wave ellipticity, planarity, and wave normal angles. 
One method for accomplishing this is presented in [4]. 
Time resolution of the DFB AC cross spectral data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), cadence for the DFB AC
cross spectra is typically 1 NYsecond [2].  Timestamps correspond to the center
time of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344 
4. Santolik, O., Parrot, M., Lefeuvre, F. (2003) Radio Science, 38, 1010.
https://doi.org/10.1029/2000RS002523

Modification History

Version 1: Initial release version
Version 2: Corrected sign of imaginary part of cross spectra

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_DBM_DVAC doi:10.48322/6rwq-2e67

Description

PSP FIELDS Digital Fields Board (DFB), Differential Voltage data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB burst waveform data consist of short bursts of time-series data from various
FIELDS sensors. These data have been filtered by both analog and digital filters
[3]. These data are pre-sorted by on-board competitive selection algorithms
described in [3] before storage by FIELDS. A sub-set of this stored burst data
is telemetered to Earth for scientist-selected regions of interest.  
The Level 2 data products contained in this data file have been calibrated for
(i) DFB in-band gain, (ii) DFB analog filter gain/phase response, (iii) DFB
digital filter phase response, and (iv) the search coil preamplifier gain/phase
response (when applicable). 
Calibrations for the FIELDS voltage sensor preamplifiers have not been
implemented, as the preamplifier response is flat and equal to 1 through the DFB
frequency range.  Corrections for plasma sheath impedance gain and antenna
effective length have not been applied to the voltage sensor data (these
corrections will be applied in Level 3 DFB data), therefore units for all
voltage sensor quantities are Volts.  Units for all magnetic field quantities
are nT.
The Level 2 data products contained in this data file are in sensor coordinates
(e.g. dV12, dV34 for voltage measurements, and u,v,w for the search coil
magnetometer). 
Time resolution for the DFB burst waveform data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), cadence for the DFB
burst waveform data is typically 150,000 samples/second.  This rate is the
sample rate of the ADC, and data taken at this rate do not pass through a
digital filter.
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1: Initial release version
Version 2: Correct units in waveform time metadata

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_DBM_DVDC

Description

PSP FIELDS Digital Fields Board (DFB), Differential Voltage data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB burst waveform data consist of short bursts of time-series data from various
FIELDS sensors. These data have been filtered by both analog and digital filters
[3]. These data are pre-sorted by on-board competitive selection algorithms
described in [3] before storage by FIELDS. A sub-set of this stored burst data
is telemetered to Earth for scientist-selected regions of interest.  
The Level 2 data products contained in this data file have been calibrated for
(i) DFB in-band gain, (ii) DFB analog filter gain/phase response, (iii) DFB
digital filter phase response, and (iv) the search coil preamplifier gain/phase
response (when applicable). 
Calibrations for the FIELDS voltage sensor preamplifiers have not been
implemented, as the preamplifier response is flat and equal to 1 through the DFB
frequency range.  Corrections for plasma sheath impedance gain and antenna
effective length have not been applied to the voltage sensor data (these
corrections will be applied in Level 3 DFB data), therefore units for all
voltage sensor quantities are Volts.  Units for all magnetic field quantities
are nT.
The Level 2 data products contained in this data file are in sensor coordinates
(e.g. dV12, dV34 for voltage measurements, and u,v,w for the search coil
magnetometer). 
Time resolution for the DFB burst waveform data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), cadence for the DFB
burst waveform data is typically 150,000 samples/second.  This rate is the
sample rate of the ADC, and data taken at this rate do not pass through a
digital filter.
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1: Initial release version
Version 2: Correct units in waveform time metadata

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_DBM_SCM doi:10.48322/y1e1-8f41

Description

PSP FIELDS Digital Fields Board (DFB), Search Coil data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB burst waveform data consist of short bursts of time-series data from various
FIELDS sensors. These data have been filtered by both analog and digital filters
[3]. These data are pre-sorted by on-board competitive selection algorithms
described in [3] before storage by FIELDS. A sub-set of this stored burst data
is telemetered to Earth for scientist-selected regions of interest.  
The Level 2 data products contained in this data file have been calibrated for
(i) DFB in-band gain, (ii) DFB analog filter gain/phase response, (iii) DFB
digital filter phase response, and (iv) the search coil preamplifier gain/phase
response (when applicable). 
Calibrations for the FIELDS voltage sensor preamplifiers have not been
implemented, as the preamplifier response is flat and equal to 1 through the DFB
frequency range.  Corrections for plasma sheath impedance gain and antenna
effective length have not been applied to the voltage sensor data (these
corrections will be applied in Level 3 DFB data), therefore units for all
voltage sensor quantities are Volts.  Units for all magnetic field quantities
are nT.
The Level 2 data products contained in this data file are in sensor coordinates
(e.g. dV12, dV34 for voltage measurements, and u,v,w for the search coil
magnetometer). 
Time resolution for the DFB burst waveform data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), cadence for the DFB
burst waveform data is typically 150,000 samples/second.  This rate is the
sample rate of the ADC, and data taken at this rate do not pass through a
digital filter.
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1: Initial release version
Version 2: Correct units in waveform time metadata
Version 3: Update SCM convolution kernel to correct sign error, also combine
high and low gain waveforms in a single file
Version 4: Update some SCM waveforms which were processed using an incorrect
kernel when updated from v02 to v03

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_DBM_VAC

Description

PSP FIELDS Digital Fields Board (DFB), Single Ended Voltage data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB burst waveform data consist of short bursts of time-series data from various
FIELDS sensors. These data have been filtered by both analog and digital filters
[3]. These data are pre-sorted by on-board competitive selection algorithms
described in [3] before storage by FIELDS. A sub-set of this stored burst data
is telemetered to Earth for scientist-selected regions of interest.  
The Level 2 data products contained in this data file have been calibrated for
(i) DFB in-band gain, (ii) DFB analog filter gain/phase response, (iii) DFB
digital filter phase response, and (iv) the search coil preamplifier gain/phase
response (when applicable). 
Calibrations for the FIELDS voltage sensor preamplifiers have not been
implemented, as the preamplifier response is flat and equal to 1 through the DFB
frequency range.  Corrections for plasma sheath impedance gain and antenna
effective length have not been applied to the voltage sensor data (these
corrections will be applied in Level 3 DFB data), therefore units for all
voltage sensor quantities are Volts.  Units for all magnetic field quantities
are nT.
The Level 2 data products contained in this data file are in sensor coordinates
(e.g. dV12, dV34 for voltage measurements, and u,v,w for the search coil
magnetometer). 
Time resolution for the DFB burst waveform data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), cadence for the DFB
burst waveform data is typically 150,000 samples/second.  This rate is the
sample rate of the ADC, and data taken at this rate do not pass through a
digital filter.
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1: Initial release version
Version 2: Correct units in waveform time metadata

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_DBM_VDC

Description

PSP FIELDS Digital Fields Board (DFB), Single Ended Voltage data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB burst waveform data consist of short bursts of time-series data from various
FIELDS sensors. These data have been filtered by both analog and digital filters
[3]. These data are pre-sorted by on-board competitive selection algorithms
described in [3] before storage by FIELDS. A sub-set of this stored burst data
is telemetered to Earth for scientist-selected regions of interest.  
The Level 2 data products contained in this data file have been calibrated for
(i) DFB in-band gain, (ii) DFB analog filter gain/phase response, (iii) DFB
digital filter phase response, and (iv) the search coil preamplifier gain/phase
response (when applicable). 
Calibrations for the FIELDS voltage sensor preamplifiers have not been
implemented, as the preamplifier response is flat and equal to 1 through the DFB
frequency range.  Corrections for plasma sheath impedance gain and antenna
effective length have not been applied to the voltage sensor data (these
corrections will be applied in Level 3 DFB data), therefore units for all
voltage sensor quantities are Volts.  Units for all magnetic field quantities
are nT.
The Level 2 data products contained in this data file are in sensor coordinates
(e.g. dV12, dV34 for voltage measurements, and u,v,w for the search coil
magnetometer). 
Time resolution for the DFB burst waveform data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), cadence for the DFB
burst waveform data is typically 150,000 samples/second.  This rate is the
sample rate of the ADC, and data taken at this rate do not pass through a
digital filter.
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1: Initial release version
Version 2: Correct units in waveform time metadata

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_DC_BPF_DV12HG doi:10.48322/j99p-vf52

Description

PSP FIELDS Digital Fields Board (DFB), dV12hg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB DC bandpass data consist of peak and average values of the absolute value of
band-passed time series waveform data over a time interval equal to the
reporting cadence. The DC bandpass data have the peak response frequency of each
bin reported in the metadata. The frequency response curves for these bins are
given in [3]. 
The Level 2 data products contained in this data file have been calibrated for
(i) the ~6.3 dB loss associated with forming the bandpass signal [3], (ii) DFB
in-band gain, (iii) DFB digital filter time delays, which become significant in
the lowest frequency DC bandpass bins, and (iv) the search coil preamplifier
response (when applicable). Calibrations for the DFB digital filter and analog
filter gains have not been implemented, as it was determined that these could
not be applied accurately to single numerical values representing a broadband
signal response, and because all bins except the highest frequency bin have a
flat gain response equal to 1 due to these filters.  Calibrations for the FIELDS
preamplifiers have not been implemented, as the preamplifier response is flat
and equal to 1 through the DFB frequency range.  Corrections for plasma sheath
impedance gain and antenna effective length have not been applied voltage sensor
signals (these corrections will be applied in Level 3 DFB data), therefore units
for all voltage sensor quantities are Volts.  Units for all magnetic field
quantities are nT.
The Level 2 data products contained in this data file are in sensor coordinates
(e.g. dV12, dV34 for voltage measurements, and u,v,w for the search coil
magnetometer). 
Time resolution of the DFB DC bandpass data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), DFB AC bandpass
cadence is typically 1 NYsecond [2].  Timestamps correspond to the center time
of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1: Initial release version

Data Variable Descriptions

L2 DC Band-pass filter average power for channel dV12hg [psp_fld_l2_dfb_dc_bpf_dV12hg_avg]

Data is in the sensor reference frame. For description see Malaspina et al.,
(2016), JGR, 121, 5088-5096, doi:10.1002/2016JA022344

L2 DC Band-pass filter peak power for channel dV12hg [psp_fld_l2_dfb_dc_bpf_dV12hg_peak]

Data is in the sensor reference frame. For description see Malaspina et al.,
(2016), JGR, 121, 5088-5096, doi:10.1002/2016JA022344

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_DC_BPF_DV34HG doi:10.48322/p859-3938

Description

PSP FIELDS Digital Fields Board (DFB), dV34hg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB DC bandpass data consist of peak and average values of the absolute value of
band-passed time series waveform data over a time interval equal to the
reporting cadence. The DC bandpass data have the peak response frequency of each
bin reported in the metadata. The frequency response curves for these bins are
given in [3]. 
The Level 2 data products contained in this data file have been calibrated for
(i) the ~6.3 dB loss associated with forming the bandpass signal [3], (ii) DFB
in-band gain, (iii) DFB digital filter time delays, which become significant in
the lowest frequency DC bandpass bins, and (iv) the search coil preamplifier
response (when applicable). Calibrations for the DFB digital filter and analog
filter gains have not been implemented, as it was determined that these could
not be applied accurately to single numerical values representing a broadband
signal response, and because all bins except the highest frequency bin have a
flat gain response equal to 1 due to these filters.  Calibrations for the FIELDS
preamplifiers have not been implemented, as the preamplifier response is flat
and equal to 1 through the DFB frequency range.  Corrections for plasma sheath
impedance gain and antenna effective length have not been applied voltage sensor
signals (these corrections will be applied in Level 3 DFB data), therefore units
for all voltage sensor quantities are Volts.  Units for all magnetic field
quantities are nT.
The Level 2 data products contained in this data file are in sensor coordinates
(e.g. dV12, dV34 for voltage measurements, and u,v,w for the search coil
magnetometer). 
Time resolution of the DFB DC bandpass data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), DFB AC bandpass
cadence is typically 1 NYsecond [2].  Timestamps correspond to the center time
of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1: Initial release version

Data Variable Descriptions

L2 DC Band-pass filter average power for channel dV34hg [psp_fld_l2_dfb_dc_bpf_dV34hg_avg]

Data is in the sensor reference frame. For description see Malaspina et al.,
(2016), JGR, 121, 5088-5096, doi:10.1002/2016JA022344

L2 DC Band-pass filter peak power for channel dV34hg [psp_fld_l2_dfb_dc_bpf_dV34hg_peak]

Data is in the sensor reference frame. For description see Malaspina et al.,
(2016), JGR, 121, 5088-5096, doi:10.1002/2016JA022344

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_DC_BPF_SCMULFHG doi:10.48322/q09x-dw27

Description

PSP FIELDS Digital Fields Board (DFB), SCMulfhg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB DC bandpass data consist of peak and average values of the absolute value of
band-passed time series waveform data over a time interval equal to the
reporting cadence. The DC bandpass data have the peak response frequency of each
bin reported in the metadata. The frequency response curves for these bins are
given in [3]. 
The Level 2 data products contained in this data file have been calibrated for
(i) the ~6.3 dB loss associated with forming the bandpass signal [3], (ii) DFB
in-band gain, (iii) DFB digital filter time delays, which become significant in
the lowest frequency DC bandpass bins, and (iv) the search coil preamplifier
response (when applicable). Calibrations for the DFB digital filter and analog
filter gains have not been implemented, as it was determined that these could
not be applied accurately to single numerical values representing a broadband
signal response, and because all bins except the highest frequency bin have a
flat gain response equal to 1 due to these filters.  Calibrations for the FIELDS
preamplifiers have not been implemented, as the preamplifier response is flat
and equal to 1 through the DFB frequency range.  Corrections for plasma sheath
impedance gain and antenna effective length have not been applied voltage sensor
signals (these corrections will be applied in Level 3 DFB data), therefore units
for all voltage sensor quantities are Volts.  Units for all magnetic field
quantities are nT.
The Level 2 data products contained in this data file are in sensor coordinates
(e.g. dV12, dV34 for voltage measurements, and u,v,w for the search coil
magnetometer). 
Time resolution of the DFB DC bandpass data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), DFB AC bandpass
cadence is typically 1 NYsecond [2].  Timestamps correspond to the center time
of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1

Data Variable Descriptions

L2 DC Band-pass filter average power for channel SCMulfhg [psp_fld_l2_dfb_dc_bpf_SCMulfhg_avg]

Data is in the sensor reference frame. For description see Malaspina et al.,
(2016), JGR, 121, 5088-5096, doi:10.1002/2016JA022344

L2 DC Band-pass filter peak power for channel SCMulfhg [psp_fld_l2_dfb_dc_bpf_SCMulfhg_peak]

Data is in the sensor reference frame. For description see Malaspina et al.,
(2016), JGR, 121, 5088-5096, doi:10.1002/2016JA022344

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_DC_BPF_SCMVLFHG doi:10.48322/k7kr-he12

Description

PSP FIELDS Digital Fields Board (DFB), SCMvlfhg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB DC bandpass data consist of peak and average values of the absolute value of
band-passed time series waveform data over a time interval equal to the
reporting cadence. The DC bandpass data have the peak response frequency of each
bin reported in the metadata. The frequency response curves for these bins are
given in [3]. 
The Level 2 data products contained in this data file have been calibrated for
(i) the ~6.3 dB loss associated with forming the bandpass signal [3], (ii) DFB
in-band gain, (iii) DFB digital filter time delays, which become significant in
the lowest frequency DC bandpass bins, and (iv) the search coil preamplifier
response (when applicable). Calibrations for the DFB digital filter and analog
filter gains have not been implemented, as it was determined that these could
not be applied accurately to single numerical values representing a broadband
signal response, and because all bins except the highest frequency bin have a
flat gain response equal to 1 due to these filters.  Calibrations for the FIELDS
preamplifiers have not been implemented, as the preamplifier response is flat
and equal to 1 through the DFB frequency range.  Corrections for plasma sheath
impedance gain and antenna effective length have not been applied voltage sensor
signals (these corrections will be applied in Level 3 DFB data), therefore units
for all voltage sensor quantities are Volts.  Units for all magnetic field
quantities are nT.
The Level 2 data products contained in this data file are in sensor coordinates
(e.g. dV12, dV34 for voltage measurements, and u,v,w for the search coil
magnetometer). 
Time resolution of the DFB DC bandpass data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), DFB AC bandpass
cadence is typically 1 NYsecond [2].  Timestamps correspond to the center time
of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1: Initial release version

Data Variable Descriptions

L2 DC Band-pass filter average power for channel SCMvlfhg [psp_fld_l2_dfb_dc_bpf_SCMvlfhg_avg]

Data is in the sensor reference frame. For description see Malaspina et al.,
(2016), JGR, 121, 5088-5096, doi:10.1002/2016JA022344

L2 DC Band-pass filter peak power for channel SCMvlfhg [psp_fld_l2_dfb_dc_bpf_SCMvlfhg_peak]

Data is in the sensor reference frame. For description see Malaspina et al.,
(2016), JGR, 121, 5088-5096, doi:10.1002/2016JA022344

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_DC_SPEC_DV12HG doi:10.48322/zqz0-3j38

Description

PSP FIELDS Digital Fields Board (DFB), dV12hg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB DC spectra data consist of power spectral densities as a function of
frequency and time.  These spectra are averaged in both frequency and time as
described in [3]. The spectra have pseudo-logarithmically spaced frequency bins,
with the bin central frequencies reported in the metadata. 
The Level 2 data products contained in this data file have been calibrated for
(i) the Hanning window used in the spectral calculation, (ii) DFB in-band gain,
(iii) DFB analog filter gain response, (iv) DFB digital filter gain response,
(v) the search coil preamplifier response (when applicable), (vi) the bandwidth
of each spectral bin.  Note that compensation for the DFB digital filters will
introduce a non-physical positively sloped power trend at high frequencies when
the non-corrected signal is dominated by noise.  This effect should be examined
carefully when determining spectral slopes and features.  Calibrations for the
FIELDS preamplifiers have not been implemented, as the preamplifier response is
flat and equal to 1 through the DFB frequency range.  Corrections for plasma
sheath impedance gain and antenna effective length have not been applied to
voltage sensor data (these corrections will be applied in Level 3 DFB data),
therefore units for all voltage sensor quantities are Volts^2/Hz.  Units for all
magnetic field quantities are nT^2/Hz.
The Level 2 voltage data products contained in this data file are in sensor
coordinates (e.g. dV12, dV34 for voltage measurements). For solar orbits 1 and
2, the search coil magnetometer spectral data is rotated into a non-intuitive
coordinate system (d,e,f). For solar orbits 3 and beyond, magnetic field data
products are in the u,v,w search coil magnetometer sensor coordinates.  
To rotate from d,e,f into u,v,w search coil sensor coordinates, use the
following matrix as (IDL notation) spectra_uvw_vector = R ## spectra_def_vector.
 
R =  [ [ 0.46834856  , -0.81336422    ,  0.34509170]
       [-0.66921924  , -0.071546954   ,  0.73961249]
       [-0.57688408  , -0.57733845    , -0.57782790]  ]
Time resolution of the DFB DC spectral data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), cadence for the DFB DC
spectra is typically 30 NYseconds [2].  Timestamps correspond to the center time
of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1: Initial release version

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_DC_SPEC_SCMDLFHG doi:10.48322/nf08-v237

Description

PSP FIELDS Digital Fields Board (DFB), SCMdlfhg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB DC spectra data consist of power spectral densities as a function of
frequency and time.  These spectra are averaged in both frequency and time as
described in [3]. The spectra have pseudo-logarithmically spaced frequency bins,
with the bin central frequencies reported in the metadata. 
The Level 2 data products contained in this data file have been calibrated for
(i) the Hanning window used in the spectral calculation, (ii) DFB in-band gain,
(iii) DFB analog filter gain response, (iv) DFB digital filter gain response,
(v) the search coil preamplifier response (when applicable), (vi) the bandwidth
of each spectral bin.  Note that compensation for the DFB digital filters will
introduce a non-physical positively sloped power trend at high frequencies when
the non-corrected signal is dominated by noise.  This effect should be examined
carefully when determining spectral slopes and features.  Calibrations for the
FIELDS preamplifiers have not been implemented, as the preamplifier response is
flat and equal to 1 through the DFB frequency range.  Corrections for plasma
sheath impedance gain and antenna effective length have not been applied to
voltage sensor data (these corrections will be applied in Level 3 DFB data),
therefore units for all voltage sensor quantities are Volts^2/Hz.  Units for all
magnetic field quantities are nT^2/Hz.
The Level 2 voltage data products contained in this data file are in sensor
coordinates (e.g. dV12, dV34 for voltage measurements). For solar orbits 1 and
2, the search coil magnetometer spectral data is rotated into a non-intuitive
coordinate system (d,e,f). For solar orbits 3 and beyond, magnetic field data
products are in the u,v,w search coil magnetometer sensor coordinates.  
To rotate from d,e,f into u,v,w search coil sensor coordinates, use the
following matrix as (IDL notation) spectra_uvw_vector = R ## spectra_def_vector.
 
R =  [ [ 0.46834856  , -0.81336422    ,  0.34509170]
       [-0.66921924  , -0.071546954   ,  0.73961249]
       [-0.57688408  , -0.57733845    , -0.57782790]  ]
Time resolution of the DFB DC spectral data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), cadence for the DFB DC
spectra is typically 30 NYseconds [2].  Timestamps correspond to the center time
of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_DC_SPEC_SCMELFHG doi:10.48322/s9kz-nb55

Description

PSP FIELDS Digital Fields Board (DFB), SCMelfhg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB DC spectra data consist of power spectral densities as a function of
frequency and time.  These spectra are averaged in both frequency and time as
described in [3]. The spectra have pseudo-logarithmically spaced frequency bins,
with the bin central frequencies reported in the metadata. 
The Level 2 data products contained in this data file have been calibrated for
(i) the Hanning window used in the spectral calculation, (ii) DFB in-band gain,
(iii) DFB analog filter gain response, (iv) DFB digital filter gain response,
(v) the search coil preamplifier response (when applicable), (vi) the bandwidth
of each spectral bin.  Note that compensation for the DFB digital filters will
introduce a non-physical positively sloped power trend at high frequencies when
the non-corrected signal is dominated by noise.  This effect should be examined
carefully when determining spectral slopes and features.  Calibrations for the
FIELDS preamplifiers have not been implemented, as the preamplifier response is
flat and equal to 1 through the DFB frequency range.  Corrections for plasma
sheath impedance gain and antenna effective length have not been applied to
voltage sensor data (these corrections will be applied in Level 3 DFB data),
therefore units for all voltage sensor quantities are Volts^2/Hz.  Units for all
magnetic field quantities are nT^2/Hz.
The Level 2 voltage data products contained in this data file are in sensor
coordinates (e.g. dV12, dV34 for voltage measurements). For solar orbits 1 and
2, the search coil magnetometer spectral data is rotated into a non-intuitive
coordinate system (d,e,f). For solar orbits 3 and beyond, magnetic field data
products are in the u,v,w search coil magnetometer sensor coordinates.  
To rotate from d,e,f into u,v,w search coil sensor coordinates, use the
following matrix as (IDL notation) spectra_uvw_vector = R ## spectra_def_vector.
 
R =  [ [ 0.46834856  , -0.81336422    ,  0.34509170]
       [-0.66921924  , -0.071546954   ,  0.73961249]
       [-0.57688408  , -0.57733845    , -0.57782790]  ]
Time resolution of the DFB DC spectral data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), cadence for the DFB DC
spectra is typically 30 NYseconds [2].  Timestamps correspond to the center time
of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_DC_SPEC_SCMFLFHG doi:10.48322/gn7g-y542

Description

PSP FIELDS Digital Fields Board (DFB), SCMflfhg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB DC spectra data consist of power spectral densities as a function of
frequency and time.  These spectra are averaged in both frequency and time as
described in [3]. The spectra have pseudo-logarithmically spaced frequency bins,
with the bin central frequencies reported in the metadata. 
The Level 2 data products contained in this data file have been calibrated for
(i) the Hanning window used in the spectral calculation, (ii) DFB in-band gain,
(iii) DFB analog filter gain response, (iv) DFB digital filter gain response,
(v) the search coil preamplifier response (when applicable), (vi) the bandwidth
of each spectral bin.  Note that compensation for the DFB digital filters will
introduce a non-physical positively sloped power trend at high frequencies when
the non-corrected signal is dominated by noise.  This effect should be examined
carefully when determining spectral slopes and features.  Calibrations for the
FIELDS preamplifiers have not been implemented, as the preamplifier response is
flat and equal to 1 through the DFB frequency range.  Corrections for plasma
sheath impedance gain and antenna effective length have not been applied to
voltage sensor data (these corrections will be applied in Level 3 DFB data),
therefore units for all voltage sensor quantities are Volts^2/Hz.  Units for all
magnetic field quantities are nT^2/Hz.
The Level 2 voltage data products contained in this data file are in sensor
coordinates (e.g. dV12, dV34 for voltage measurements). For solar orbits 1 and
2, the search coil magnetometer spectral data is rotated into a non-intuitive
coordinate system (d,e,f). For solar orbits 3 and beyond, magnetic field data
products are in the u,v,w search coil magnetometer sensor coordinates.  
To rotate from d,e,f into u,v,w search coil sensor coordinates, use the
following matrix as (IDL notation) spectra_uvw_vector = R ## spectra_def_vector.
 
R =  [ [ 0.46834856  , -0.81336422    ,  0.34509170]
       [-0.66921924  , -0.071546954   ,  0.73961249]
       [-0.57688408  , -0.57733845    , -0.57782790]  ]
Time resolution of the DFB DC spectral data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), cadence for the DFB DC
spectra is typically 30 NYseconds [2].  Timestamps correspond to the center time
of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_DC_SPEC_SCMULFHG doi:10.48322/0cwt-mw28

Description

PSP FIELDS Digital Fields Board (DFB), SCMulfhg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB DC spectra data consist of power spectral densities as a function of
frequency and time.  These spectra are averaged in both frequency and time as
described in [3]. The spectra have pseudo-logarithmically spaced frequency bins,
with the bin central frequencies reported in the metadata. 
The Level 2 data products contained in this data file have been calibrated for
(i) the Hanning window used in the spectral calculation, (ii) DFB in-band gain,
(iii) DFB analog filter gain response, (iv) DFB digital filter gain response,
(v) the search coil preamplifier response (when applicable), (vi) the bandwidth
of each spectral bin.  Note that compensation for the DFB digital filters will
introduce a non-physical positively sloped power trend at high frequencies when
the non-corrected signal is dominated by noise.  This effect should be examined
carefully when determining spectral slopes and features.  Calibrations for the
FIELDS preamplifiers have not been implemented, as the preamplifier response is
flat and equal to 1 through the DFB frequency range.  Corrections for plasma
sheath impedance gain and antenna effective length have not been applied to
voltage sensor data (these corrections will be applied in Level 3 DFB data),
therefore units for all voltage sensor quantities are Volts^2/Hz.  Units for all
magnetic field quantities are nT^2/Hz.
The Level 2 voltage data products contained in this data file are in sensor
coordinates (e.g. dV12, dV34 for voltage measurements). For solar orbits 1 and
2, the search coil magnetometer spectral data is rotated into a non-intuitive
coordinate system (d,e,f). For solar orbits 3 and beyond, magnetic field data
products are in the u,v,w search coil magnetometer sensor coordinates.  
To rotate from d,e,f into u,v,w search coil sensor coordinates, use the
following matrix as (IDL notation) spectra_uvw_vector = R ## spectra_def_vector.
 
R =  [ [ 0.46834856  , -0.81336422    ,  0.34509170]
       [-0.66921924  , -0.071546954   ,  0.73961249]
       [-0.57688408  , -0.57733845    , -0.57782790]  ]
Time resolution of the DFB DC spectral data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), cadence for the DFB DC
spectra is typically 30 NYseconds [2].  Timestamps correspond to the center time
of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1: Initial release version

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_DC_SPEC_SCMVLFHG doi:10.48322/hvzj-4k68

Description

PSP FIELDS Digital Fields Board (DFB), SCMvlfhg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB DC spectra data consist of power spectral densities as a function of
frequency and time.  These spectra are averaged in both frequency and time as
described in [3]. The spectra have pseudo-logarithmically spaced frequency bins,
with the bin central frequencies reported in the metadata. 
The Level 2 data products contained in this data file have been calibrated for
(i) the Hanning window used in the spectral calculation, (ii) DFB in-band gain,
(iii) DFB analog filter gain response, (iv) DFB digital filter gain response,
(v) the search coil preamplifier response (when applicable), (vi) the bandwidth
of each spectral bin.  Note that compensation for the DFB digital filters will
introduce a non-physical positively sloped power trend at high frequencies when
the non-corrected signal is dominated by noise.  This effect should be examined
carefully when determining spectral slopes and features.  Calibrations for the
FIELDS preamplifiers have not been implemented, as the preamplifier response is
flat and equal to 1 through the DFB frequency range.  Corrections for plasma
sheath impedance gain and antenna effective length have not been applied to
voltage sensor data (these corrections will be applied in Level 3 DFB data),
therefore units for all voltage sensor quantities are Volts^2/Hz.  Units for all
magnetic field quantities are nT^2/Hz.
The Level 2 voltage data products contained in this data file are in sensor
coordinates (e.g. dV12, dV34 for voltage measurements). For solar orbits 1 and
2, the search coil magnetometer spectral data is rotated into a non-intuitive
coordinate system (d,e,f). For solar orbits 3 and beyond, magnetic field data
products are in the u,v,w search coil magnetometer sensor coordinates.  
To rotate from d,e,f into u,v,w search coil sensor coordinates, use the
following matrix as (IDL notation) spectra_uvw_vector = R ## spectra_def_vector.
 
R =  [ [ 0.46834856  , -0.81336422    ,  0.34509170]
       [-0.66921924  , -0.071546954   ,  0.73961249]
       [-0.57688408  , -0.57733845    , -0.57782790]  ]
Time resolution of the DFB DC spectral data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), cadence for the DFB DC
spectra is typically 30 NYseconds [2].  Timestamps correspond to the center time
of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1: Initial release version

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_DC_SPEC_SCMWLFHG doi:10.48322/pakh-kk30

Description

PSP FIELDS Digital Fields Board (DFB), SCMwlfhg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB DC spectra data consist of power spectral densities as a function of
frequency and time.  These spectra are averaged in both frequency and time as
described in [3]. The spectra have pseudo-logarithmically spaced frequency bins,
with the bin central frequencies reported in the metadata. 
The Level 2 data products contained in this data file have been calibrated for
(i) the Hanning window used in the spectral calculation, (ii) DFB in-band gain,
(iii) DFB analog filter gain response, (iv) DFB digital filter gain response,
(v) the search coil preamplifier response (when applicable), (vi) the bandwidth
of each spectral bin.  Note that compensation for the DFB digital filters will
introduce a non-physical positively sloped power trend at high frequencies when
the non-corrected signal is dominated by noise.  This effect should be examined
carefully when determining spectral slopes and features.  Calibrations for the
FIELDS preamplifiers have not been implemented, as the preamplifier response is
flat and equal to 1 through the DFB frequency range.  Corrections for plasma
sheath impedance gain and antenna effective length have not been applied to
voltage sensor data (these corrections will be applied in Level 3 DFB data),
therefore units for all voltage sensor quantities are Volts^2/Hz.  Units for all
magnetic field quantities are nT^2/Hz.
The Level 2 voltage data products contained in this data file are in sensor
coordinates (e.g. dV12, dV34 for voltage measurements). For solar orbits 1 and
2, the search coil magnetometer spectral data is rotated into a non-intuitive
coordinate system (d,e,f). For solar orbits 3 and beyond, magnetic field data
products are in the u,v,w search coil magnetometer sensor coordinates.  
To rotate from d,e,f into u,v,w search coil sensor coordinates, use the
following matrix as (IDL notation) spectra_uvw_vector = R ## spectra_def_vector.
 
R =  [ [ 0.46834856  , -0.81336422    ,  0.34509170]
       [-0.66921924  , -0.071546954   ,  0.73961249]
       [-0.57688408  , -0.57733845    , -0.57782790]  ]
Time resolution of the DFB DC spectral data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), cadence for the DFB DC
spectra is typically 30 NYseconds [2].  Timestamps correspond to the center time
of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1: Initial release version

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_DC_XSPEC_SCMDLFHG_SCMELFHG doi:10.48322/krzj-sw31

Description

PSP FIELDS Digital Fields Board (DFB), SCMdlfhg x SCMelfhg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB DC cross spectra data consist of, for a pair of input channels, (i) power
spectral densities (auto spectra, e.g. FT1 x FT1*), (ii) real and imaginary
parts of the spectral cross term (FT1 x FT2*), (iii) coherence, and (iv) phase,
all as a function of frequency and time.  Coherence and phase are defined in
[3].  These cross spectra are averaged in both frequency and time as described
in [3]. The cross spectra have either 56 or 96 bins (selectable) with the bin
central frequencies reported in the metadata.    
The Level 2 data products contained in this data file have been calibrated for
(i) the Hanning window used in the spectral calculation, (ii) DFB in-band gain,
(iii) DFB analog filter gain response, (iv) DFB digital filter gain response,
(v) the search coil preamplifier response (when applicable), (vi) the bandwidth
of each spectral bin.  Note that compensation for the DFB digital filters will
introduce a non-physical positively sloped power trend at high frequencies when
the non-corrected signal is dominated by noise.  This effect should be examined
carefully when determining spectral slopes and features.  Calibrations for the
FIELDS preamplifiers have not been implemented, as the preamplifier response is
flat and equal to 1 through the DFB frequency range.  Corrections for plasma
sheath impedance gain and antenna effective length have not been applied to
voltage sensor data (these corrections will be applied in Level 3 DFB data),
therefore units for all voltage sensor quantities are Volts^2/Hz.  Units for all
magnetic field quantities are nT^2/Hz. Coherence is unitless.  Units for phase
are degrees. 
The Level 2 voltage data products contained in this data file are in sensor
coordinates (e.g. dV12, dV34 for voltage measurements). For solar orbits 1 and
2, the search coil magnetometer cross spectral data is rotated into a
non-intuitive coordinate system (d,e,f). For solar orbits 3 and beyond, magnetic
field data products are in the u,v,w search coil magnetometer sensor
coordinates.  
To rotate from d,e,f into u,v,w search coil sensor coordinates, use the
following matrix as (IDL notation) spectra_uvw_vector = R ## spectra_def_vector.
 
R =  [ [ 0.46834856  , -0.81336422    ,  0.34509170]
       [-0.66921924  , -0.071546954   ,  0.73961249]
       [-0.57688408  , -0.57733845    , -0.57782790]  ]
For some orbits, sufficient spectral information exists in the search coil auto-
and cross-spectra to determine wave ellipticity, planarity, and wave normal
angles.  One method for accomplishing this is presented in [4]. 
Time resolution of the DFB DC cross spectral data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), cadence for the DFB DC
cross spectra is typically 30 NYseconds [2].  Timestamps correspond to the
center time of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344 
4. Santolik, O., Parrot, M., Lefeuvre, F. (2003) Radio Science, 38, 1010.
https://doi.org/10.1029/2000RS002523

Modification History

Version 1: Initial release version
Version 2: Corrected sign of imaginary part of cross spectra

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_DC_XSPEC_SCMDLFHG_SCMFLFHG doi:10.48322/j3dc-kr21

Description

PSP FIELDS Digital Fields Board (DFB), SCMdlfhg x SCMflfhg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB DC cross spectra data consist of, for a pair of input channels, (i) power
spectral densities (auto spectra, e.g. FT1 x FT1*), (ii) real and imaginary
parts of the spectral cross term (FT1 x FT2*), (iii) coherence, and (iv) phase,
all as a function of frequency and time.  Coherence and phase are defined in
[3].  These cross spectra are averaged in both frequency and time as described
in [3]. The cross spectra have either 56 or 96 bins (selectable) with the bin
central frequencies reported in the metadata.    
The Level 2 data products contained in this data file have been calibrated for
(i) the Hanning window used in the spectral calculation, (ii) DFB in-band gain,
(iii) DFB analog filter gain response, (iv) DFB digital filter gain response,
(v) the search coil preamplifier response (when applicable), (vi) the bandwidth
of each spectral bin.  Note that compensation for the DFB digital filters will
introduce a non-physical positively sloped power trend at high frequencies when
the non-corrected signal is dominated by noise.  This effect should be examined
carefully when determining spectral slopes and features.  Calibrations for the
FIELDS preamplifiers have not been implemented, as the preamplifier response is
flat and equal to 1 through the DFB frequency range.  Corrections for plasma
sheath impedance gain and antenna effective length have not been applied to
voltage sensor data (these corrections will be applied in Level 3 DFB data),
therefore units for all voltage sensor quantities are Volts^2/Hz.  Units for all
magnetic field quantities are nT^2/Hz. Coherence is unitless.  Units for phase
are degrees. 
The Level 2 voltage data products contained in this data file are in sensor
coordinates (e.g. dV12, dV34 for voltage measurements). For solar orbits 1 and
2, the search coil magnetometer cross spectral data is rotated into a
non-intuitive coordinate system (d,e,f). For solar orbits 3 and beyond, magnetic
field data products are in the u,v,w search coil magnetometer sensor
coordinates.  
To rotate from d,e,f into u,v,w search coil sensor coordinates, use the
following matrix as (IDL notation) spectra_uvw_vector = R ## spectra_def_vector.
 
R =  [ [ 0.46834856  , -0.81336422    ,  0.34509170]
       [-0.66921924  , -0.071546954   ,  0.73961249]
       [-0.57688408  , -0.57733845    , -0.57782790]  ]
For some orbits, sufficient spectral information exists in the search coil auto-
and cross-spectra to determine wave ellipticity, planarity, and wave normal
angles.  One method for accomplishing this is presented in [4]. 
Time resolution of the DFB DC cross spectral data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), cadence for the DFB DC
cross spectra is typically 30 NYseconds [2].  Timestamps correspond to the
center time of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344 
4. Santolik, O., Parrot, M., Lefeuvre, F. (2003) Radio Science, 38, 1010.
https://doi.org/10.1029/2000RS002523

Modification History

Version 1: Initial release version
Version 2: Corrected sign of imaginary part of cross spectra

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_DC_XSPEC_SCMELFHG_SCMFLFHG doi:10.48322/x8yt-7b32

Description

PSP FIELDS Digital Fields Board (DFB), SCMelfhg x SCMflfhg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB DC cross spectra data consist of, for a pair of input channels, (i) power
spectral densities (auto spectra, e.g. FT1 x FT1*), (ii) real and imaginary
parts of the spectral cross term (FT1 x FT2*), (iii) coherence, and (iv) phase,
all as a function of frequency and time.  Coherence and phase are defined in
[3].  These cross spectra are averaged in both frequency and time as described
in [3]. The cross spectra have either 56 or 96 bins (selectable) with the bin
central frequencies reported in the metadata.    
The Level 2 data products contained in this data file have been calibrated for
(i) the Hanning window used in the spectral calculation, (ii) DFB in-band gain,
(iii) DFB analog filter gain response, (iv) DFB digital filter gain response,
(v) the search coil preamplifier response (when applicable), (vi) the bandwidth
of each spectral bin.  Note that compensation for the DFB digital filters will
introduce a non-physical positively sloped power trend at high frequencies when
the non-corrected signal is dominated by noise.  This effect should be examined
carefully when determining spectral slopes and features.  Calibrations for the
FIELDS preamplifiers have not been implemented, as the preamplifier response is
flat and equal to 1 through the DFB frequency range.  Corrections for plasma
sheath impedance gain and antenna effective length have not been applied to
voltage sensor data (these corrections will be applied in Level 3 DFB data),
therefore units for all voltage sensor quantities are Volts^2/Hz.  Units for all
magnetic field quantities are nT^2/Hz. Coherence is unitless.  Units for phase
are degrees. 
The Level 2 voltage data products contained in this data file are in sensor
coordinates (e.g. dV12, dV34 for voltage measurements). For solar orbits 1 and
2, the search coil magnetometer cross spectral data is rotated into a
non-intuitive coordinate system (d,e,f). For solar orbits 3 and beyond, magnetic
field data products are in the u,v,w search coil magnetometer sensor
coordinates.  
To rotate from d,e,f into u,v,w search coil sensor coordinates, use the
following matrix as (IDL notation) spectra_uvw_vector = R ## spectra_def_vector.
 
R =  [ [ 0.46834856  , -0.81336422    ,  0.34509170]
       [-0.66921924  , -0.071546954   ,  0.73961249]
       [-0.57688408  , -0.57733845    , -0.57782790]  ]
For some orbits, sufficient spectral information exists in the search coil auto-
and cross-spectra to determine wave ellipticity, planarity, and wave normal
angles.  One method for accomplishing this is presented in [4]. 
Time resolution of the DFB DC cross spectral data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), cadence for the DFB DC
cross spectra is typically 30 NYseconds [2].  Timestamps correspond to the
center time of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344 
4. Santolik, O., Parrot, M., Lefeuvre, F. (2003) Radio Science, 38, 1010.
https://doi.org/10.1029/2000RS002523

Modification History

Version 1: Initial release version
Version 2: Corrected sign of imaginary part of cross spectra

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_DC_XSPEC_SCMVLFHG_SCMWLFHG doi:10.48322/4sc7-7454

Description

PSP FIELDS Digital Fields Board (DFB), SCMvlfhg x SCMwlfhg data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB DC cross spectra data consist of, for a pair of input channels, (i) power
spectral densities (auto spectra, e.g. FT1 x FT1*), (ii) real and imaginary
parts of the spectral cross term (FT1 x FT2*), (iii) coherence, and (iv) phase,
all as a function of frequency and time.  Coherence and phase are defined in
[3].  These cross spectra are averaged in both frequency and time as described
in [3]. The cross spectra have either 56 or 96 bins (selectable) with the bin
central frequencies reported in the metadata.    
The Level 2 data products contained in this data file have been calibrated for
(i) the Hanning window used in the spectral calculation, (ii) DFB in-band gain,
(iii) DFB analog filter gain response, (iv) DFB digital filter gain response,
(v) the search coil preamplifier response (when applicable), (vi) the bandwidth
of each spectral bin.  Note that compensation for the DFB digital filters will
introduce a non-physical positively sloped power trend at high frequencies when
the non-corrected signal is dominated by noise.  This effect should be examined
carefully when determining spectral slopes and features.  Calibrations for the
FIELDS preamplifiers have not been implemented, as the preamplifier response is
flat and equal to 1 through the DFB frequency range.  Corrections for plasma
sheath impedance gain and antenna effective length have not been applied to
voltage sensor data (these corrections will be applied in Level 3 DFB data),
therefore units for all voltage sensor quantities are Volts^2/Hz.  Units for all
magnetic field quantities are nT^2/Hz. Coherence is unitless.  Units for phase
are degrees. 
The Level 2 voltage data products contained in this data file are in sensor
coordinates (e.g. dV12, dV34 for voltage measurements). For solar orbits 1 and
2, the search coil magnetometer cross spectral data is rotated into a
non-intuitive coordinate system (d,e,f). For solar orbits 3 and beyond, magnetic
field data products are in the u,v,w search coil magnetometer sensor
coordinates.  
To rotate from d,e,f into u,v,w search coil sensor coordinates, use the
following matrix as (IDL notation) spectra_uvw_vector = R ## spectra_def_vector.
 
R =  [ [ 0.46834856  , -0.81336422    ,  0.34509170]
       [-0.66921924  , -0.071546954   ,  0.73961249]
       [-0.57688408  , -0.57733845    , -0.57782790]  ]
For some orbits, sufficient spectral information exists in the search coil auto-
and cross-spectra to determine wave ellipticity, planarity, and wave normal
angles.  One method for accomplishing this is presented in [4]. 
Time resolution of the DFB DC cross spectral data can vary by multiples of 2^N. 
During encounter (when PSP is within 0.25 AU of the Sun), cadence for the DFB DC
cross spectra is typically 30 NYseconds [2].  Timestamps correspond to the
center time of each window. 
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344 
4. Santolik, O., Parrot, M., Lefeuvre, F. (2003) Radio Science, 38, 1010.
https://doi.org/10.1029/2000RS002523

Modification History

Version 1: Initial release version
Version 2: Corrected sign of imaginary part of cross spectra

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_WF_DVDC doi:10.48322/fdh3-5n37

Description

PSP FIELDS Digital Fields Board (DFB), Differential Voltage data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB continuous waveform data consist of time-series data from various FIELDS
sensors. These data have been filtered by both analog and digital filters [3]. 
The Level 2 data products contained in this data file have been calibrated for
(i) DFB in-band gain, (ii) DFB analog filter gain/phase response, (iii) DFB
digital filter phase response, and (iv) the search coil preamplifier gain/phase
response (when applicable). Calibrations for the FIELDS digital filter gain
response have not been implemented, but the required convolution kernel is
provided in this file.  It was decided not to apply the FIELDS digital filter
gain response to the L2 data because this can introduce non-physical power at
high frequencies when the non-corrected signal is dominated by noise. This
effect should be examined carefully when determining spectral slopes and
features at the highest frequencies. Calibrations for the FIELDS voltage sensor
preamplifiers have not been implemented, as the preamplifier response is flat
and equal to 1 through the DFB frequency range.  Corrections for plasma sheath
impedance gain and antenna effective length have not been applied to the voltage
sensor data (these corrections will be applied in Level 3 DFB data), therefore
units for all voltage sensor quantities are Volts.  Units for all magnetic field
quantities are nT.
The Level 2 data products contained in this data file are in spacecraft
coordinates (e.g. x,y,z) and in sensor coordinates (e.g. dV12, dV34 for voltage
measurements, and u,v,w for the search coil magnetometer). 
Time resolution for the DFB continuous waveform data can vary by multiples of
2^N.  During encounter (when PSP is within 0.25 AU of the Sun), cadence for the
DFB continuous waveform data is typically 256 samples/NYsecond [2].  
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1: Initial release version
Version 2: Time stamp corrections to waveform data
Version 3: Corrected rotation into spacecraft coordinates from sensor
coordinates

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_WF_SCM doi:10.48322/h34r-jn18

Description

PSP FIELDS Digital Fields Board (DFB), Search Coil Magnetometer data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB continuous waveform data consist of time-series data from various FIELDS
sensors. These data have been filtered by both analog and digital filters [3]. 
The Level 2 data products contained in this data file have been calibrated for
(i) DFB in-band gain, (ii) DFB analog filter gain/phase response, (iii) DFB
digital filter phase response, and (iv) the search coil preamplifier gain/phase
response (when applicable). Calibrations for the FIELDS digital filter gain
response have not been implemented, but the required convolution kernel is
provided in this file.  It was decided not to apply the FIELDS digital filter
gain response to the L2 data because this can introduce non-physical power at
high frequencies when the non-corrected signal is dominated by noise. This
effect should be examined carefully when determining spectral slopes and
features at the highest frequencies. Calibrations for the FIELDS voltage sensor
preamplifiers have not been implemented, as the preamplifier response is flat
and equal to 1 through the DFB frequency range.  Corrections for plasma sheath
impedance gain and antenna effective length have not been applied to the voltage
sensor data (these corrections will be applied in Level 3 DFB data), therefore
units for all voltage sensor quantities are Volts.  Units for all magnetic field
quantities are nT.
The Level 2 data products contained in this data file are in spacecraft
coordinates (e.g. x,y,z) and in sensor coordinates (e.g. dV12, dV34 for voltage
measurements, and u,v,w for the search coil magnetometer). 
Time resolution for the DFB continuous waveform data can vary by multiples of
2^N.  During encounter (when PSP is within 0.25 AU of the Sun), cadence for the
DFB continuous waveform data is typically 256 samples/NYsecond [2].  
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1: Initial release version
Version 2: Corrected SCM convolution kernel, and time stamp corrections to
waveform data

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_DFB_WF_VDC doi:10.48322/qhgy-hm62

Description

PSP FIELDS Digital Fields Board (DFB), Single Ended Voltage data. 
The DFB is the low frequency (< 75 kHz) component of the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. For a description of the DFB, see [3].
DFB continuous waveform data consist of time-series data from various FIELDS
sensors. These data have been filtered by both analog and digital filters [3]. 
The Level 2 data products contained in this data file have been calibrated for
(i) DFB in-band gain, (ii) DFB analog filter gain/phase response, (iii) DFB
digital filter phase response, and (iv) the search coil preamplifier gain/phase
response (when applicable). Calibrations for the FIELDS digital filter gain
response have not been implemented, but the required convolution kernel is
provided in this file.  It was decided not to apply the FIELDS digital filter
gain response to the L2 data because this can introduce non-physical power at
high frequencies when the non-corrected signal is dominated by noise. This
effect should be examined carefully when determining spectral slopes and
features at the highest frequencies. Calibrations for the FIELDS voltage sensor
preamplifiers have not been implemented, as the preamplifier response is flat
and equal to 1 through the DFB frequency range.  Corrections for plasma sheath
impedance gain and antenna effective length have not been applied to the voltage
sensor data (these corrections will be applied in Level 3 DFB data), therefore
units for all voltage sensor quantities are Volts.  Units for all magnetic field
quantities are nT.
The Level 2 data products contained in this data file are in spacecraft
coordinates (e.g. x,y,z) and in sensor coordinates (e.g. dV12, dV34 for voltage
measurements, and u,v,w for the search coil magnetometer). 
Time resolution for the DFB continuous waveform data can vary by multiples of
2^N.  During encounter (when PSP is within 0.25 AU of the Sun), cadence for the
DFB continuous waveform data is typically 256 samples/NYsecond [2].  
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344

Modification History

Version 1: Initial release version
Version 2: Time stamp corrections to waveform data

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_F2_100BPS doi:10.48322/8khn-cs70

Description

PSP FIELDS F2-100bps Summary Telemetry Data

Modification History

2019-08-01 - Revision 1
2019-09-27 - Revision 2 - add VDC values; add sensor data existence flags in
each record; remove CDF-level sensor count values; remove SCM given in mV (use
nT); move Bx, By and Bz into single array;add RTN version of MAG axes.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_MAG_RTN doi:10.48322/0yy0-ba92

Description

PSP FIELDS Fluxgate Magnetometer data. Time resolution varies with instrument
mode, ranging from 2.3-292.9 samples/sec, corresponding to 2-256 samples per
0.874 seconds (0.874 = 2^25 / 38.4 MHz, see reference [2]).
The Magnetometer has 4 ranges - +/-1024, +/-4096, +/-16,384, +/-65,536 nT,
selected by the ranging algorithm, based on the ambient magnetic field.
Precision is +/- 15 bits, based on the 16-bit ADC.
References:
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s11214-015-0211-6
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s11214-016-0244-5

Modification History

Version 1: Original release version.
Version 2: Timing correction for coordinate transformations, corrections for
non-orthogonality of sensor axes, and phase shift compensating for downsampling
filter.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_MAG_RTN_1MIN doi:10.48322/c0zj-xf76

Description

PSP FIELDS Fluxgate Magnetometer data. Time resolution varies with instrument
mode, ranging from 2.3-292.9 samples/sec, corresponding to 2-256 samples per
0.874 seconds (0.874 = 2^25 / 38.4 MHz, see reference [2]).
The Magnetometer has 4 ranges - +/-1024, +/-4096, +/-16,384, +/-65,536 nT,
selected by the ranging algorithm, based on the ambient magnetic field.
Precision is +/- 15 bits, based on the 16-bit ADC.
References:
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s11214-015-0211-6
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s11214-016-0244-5

Modification History

Version 1: Original release version.
Version 2: Timing correction for coordinate transformations, corrections for
non-orthogonality of sensor axes, and phase shift compensating for downsampling
filter.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_MAG_SC doi:10.48322/8fc4-fq16

Description

PSP FIELDS Fluxgate Magnetometer data. Time resolution varies with instrument
mode, ranging from 2.3-292.9 samples/sec, corresponding to 2-256 samples per
0.874 seconds (0.874 = 2^25 / 38.4 MHz, see reference [2]).
The Magnetometer has 4 ranges - +/-1024, +/-4096, +/-16,384, +/-65,536 nT,
selected by the ranging algorithm, based on the ambient magnetic field.
Precision is +/- 15 bits, based on the 16-bit ADC.
References:
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s11214-015-0211-6
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s11214-016-0244-5

Modification History

Version 1: Original release version.
Version 2: Timing correction for coordinate transformations, corrections for
non-orthogonality of sensor axes, and phase shift compensating for downsampling
filter.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_MAG_SC_1MIN doi:10.48322/7hrp-ya88

Description

PSP FIELDS Fluxgate Magnetometer data. Time resolution varies with instrument
mode, ranging from 2.3-292.9 samples/sec, corresponding to 2-256 samples per
0.874 seconds (0.874 = 2^25 / 38.4 MHz, see reference [2]).
The Magnetometer has 4 ranges - +/-1024, +/-4096, +/-16,384, +/-65,536 nT,
selected by the ranging algorithm, based on the ambient magnetic field.
Precision is +/- 15 bits, based on the 16-bit ADC.
References:
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s11214-015-0211-6
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s11214-016-0244-5

Modification History

Version 1: Original release version.
Version 2: Timing correction for coordinate transformations, corrections for
non-orthogonality of sensor axes, and phase shift compensating for downsampling
filter.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_MAG_VSO

Description

PSP FIELDS Fluxgate Magnetometer data. Time resolution varies with instrument
mode, ranging from 2.3-292.9 samples/sec, corresponding to 2-256 samples per
0.874 seconds (0.874 = 2^25 / 38.4 MHz, see reference [2]).
The Magnetometer has 4 ranges - +/-1024, +/-4096, +/-16,384, +/-65,536 nT,
selected by the ranging algorithm, based on the ambient magnetic field.
Precision is +/- 15 bits, based on the 16-bit ADC.
References:
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s11214-015-0211-6
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s11214-016-0244-5

Modification History

Version 1: Original release version.
Version 2: Timing correction for coordinate transformations, corrections for
non-orthogonality of sensor axes, and phase shift compensating for downsampling
filter.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_RFS_BURST

Description

PSP FIELDS Radio Frequency Spectrometer (RFS), BURST data.
The RFS is the high frequency component  of the FIELDS experiment on the  Parker
Solar Probe spacecraft [1].  For a full description of the FIELDS  experiment,
see [2].  For a description  of the RFS, see [3].
The RFS produces auto and cross spectral data products in two frequency ranges,
the LFR (Low Frequency Reciever) range and the HFR (High Frequency Receiver)
range.  Telemetered spectral data products for both HFR and LFR contain 64
frequency bins, with the LFR typically covering a frequency range from 10.5 kHz
to 1.7 MHz, and the HFR covering from 1.3 MHz to 19.2 MHz, with approximately
logarithmically spaced bins. LFR HiRes spectra contain 32 finely spaced
frequency bins near the plasma frequency. The exact frequency bins are
selectable and are included as metadata variables in this file.
The Level 2 data products contained in this data file have been calibrated for
the preamp and RFS analog section response, and the polyphase filter bank (PFB)
and the FFT spectral processing as described in [3].  Corrections for base
capacitance and antenna effective length have not been applied (these
corrections will be applied in Level 3 RFS data.) Therefore, units for all
spectral quantities are given in V^2/Hz.
Time resolution of the RFS varies with instrument mode.  During encounter (when
PSP is within 0.25 AU of the Sun), cadence for RFS HFR and LFR spectra is
typically about 7 seconds.  During cruise mode, which is the default mode for
operations outside of 0.25 AU, cadence for HFR and LFR spectra is about 56
seconds.
References:
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s11214-015-0211-6
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s11214-016-0244-5
3. Pulupa, M., Bale, S. D., Bonnell, J.W. et al. (2017) JGR Space Physics, 122,
2836-2854. https://doi.org/10.1002/2016JA023345

Modification History

Revision 1
Revision 2: Corrected 'Instrument_type' metadata

Data Variable Descriptions

BURST auto, Ch0: V1V2 [psp_fld_l2_rfs_burst_auto_ch0_V1V2]

Gain flag for BURST auto, Ch0: V1V2 [psp_fld_l2_rfs_burst_auto_ch0_V1V2_gain]

0: Low gain, 1: High gain.

N summed spectra for BURST auto, Ch0: V1V2 [psp_fld_l2_rfs_burst_auto_ch0_V1V2_nsum]

Overrange flag for BURST auto, Ch0: V1V2 [psp_fld_l2_rfs_burst_auto_ch0_V1V2_hl]

Overrange flag indicates an overrange condition in at least one input waveform
collected during the LFR or HFR accumulation interval (see Ref. [3]).0: No
overranges, 1: Overrange in Low Gain but not High Gain, 2: Overrange in High
Gain but not Low Gain, 3: Overrange in Low Gain and High Gain.

BURST auto, Ch1: V3V4 [psp_fld_l2_rfs_burst_auto_ch1_V3V4]

Gain flag for BURST auto, Ch1: V3V4 [psp_fld_l2_rfs_burst_auto_ch1_V3V4_gain]

0: Low gain, 1: High gain.

N summed spectra for BURST auto, Ch1: V3V4 [psp_fld_l2_rfs_burst_auto_ch1_V3V4_nsum]

Overrange flag for BURST auto, Ch1: V3V4 [psp_fld_l2_rfs_burst_auto_ch1_V3V4_hl]

Overrange flag indicates an overrange condition in at least one input waveform
collected during the LFR or HFR accumulation interval (see Ref. [3]).0: No
overranges, 1: Overrange in Low Gain but not High Gain, 2: Overrange in High
Gain but not Low Gain, 3: Overrange in Low Gain and High Gain.

BURST Cross Spectra Imag Part, Ch0: V1V2 Ch1: V3V4 [psp_fld_l2_rfs_burst_cross_im_V1V2_V3V4]

Gain flag for BURST Cross Spectra Imag Part, Ch0: V1V2 Ch1: V3V4 [psp_fld_l2_rfs_burst_cross_im_V1V2_V3V4_gain]

0: Low gain, 1: High gain.

N summed spectra for BURST Cross Spectra Imag Part, Ch0: V1V2 Ch1: V3V4 [psp_fld_l2_rfs_burst_cross_im_V1V2_V3V4_nsum]

Overrange flag for BURST Cross Spectra Imag Part, Ch0: V1V2 Ch1: V3V4 [psp_fld_l2_rfs_burst_cross_im_V1V2_V3V4_hl]

Overrange flag indicates an overrange condition in at least one input waveform
collected during the LFR or HFR accumulation interval (see Ref. [3]).0: No
overranges, 1: Overrange in Low Gain but not High Gain, 2: Overrange in High
Gain but not Low Gain, 3: Overrange in Low Gain and High Gain.

BURST Cross Spectra Real Part, Ch0: V1V2 Ch1: V3V4 [psp_fld_l2_rfs_burst_cross_re_V1V2_V3V4]

Gain flag for BURST Cross Spectra Real Part, Ch0: V1V2 Ch1: V3V4 [psp_fld_l2_rfs_burst_cross_re_V1V2_V3V4_gain]

0: Low gain, 1: High gain.

N summed spectra for BURST Cross Spectra Real Part, Ch0: V1V2 Ch1: V3V4 [psp_fld_l2_rfs_burst_cross_re_V1V2_V3V4_nsum]

Overrange flag for BURST Cross Spectra Real Part, Ch0: V1V2 Ch1: V3V4 [psp_fld_l2_rfs_burst_cross_re_V1V2_V3V4_hl]

Overrange flag indicates an overrange condition in at least one input waveform
collected during the LFR or HFR accumulation interval (see Ref. [3]).0: No
overranges, 1: Overrange in Low Gain but not High Gain, 2: Overrange in High
Gain but not Low Gain, 3: Overrange in Low Gain and High Gain.

Averages enable flag for all BURST spectra [psp_fld_l2_rfs_burst_averages]

Average mode enable flag for all BURST spectra. A value of 1 indicates that
average mode is enabled, and a value of 0 indicates that average mode is
disabled.

Peak enable flag for all BURST spectra [psp_fld_l2_rfs_burst_peaks]

Peak mode enable flag for all BURST spectra. A value of 1 indicates that peak
mode is enabled, and a value of 0 indicates that peak mode is disabled.

Channel 0 source for all BURST spectra [psp_fld_l2_rfs_burst_ch0]

Source for BURST Channel 0 data. 0: V1V2, 1: V1V3, 2: V2V4, 3: SCM, 4: V1, 5:
V3, 6: GND, 7: GND.

Channel 1 source for all BURST spectra [psp_fld_l2_rfs_burst_ch1]

Source for BURST Channel 1 data. 0: V3V4, 1: V3V2, 2: V1V4, 3: SCM, 4: V2, 5:
V4, 6: GND, 7: GND.

N summed spectra for all BURST spectra [psp_fld_l2_rfs_burst_nsum]

Number of summed individual spectra for BURST auto and cross reduced spectra.

Gain flag for all BURST spectra [psp_fld_l2_rfs_burst_gain]

Gain flag for BURST auto and cross reduced spectra. 0: Low gain, 1: High gain.

Overrange flag for all BURST spectra [psp_fld_l2_rfs_burst_hl]

Overrange flag for BURST auto and cross reduced spectra.  Flag indicates an
overrange condition in at least one input waveform collected during the LFR or
HFR accumulation interval (see Ref. [3]).0: No overranges, 1: Overrange in Low
Gain but not High Gain, 2: Overrange in High Gain but not Low Gain, 3: Overrange
in Low Gain and High Gain.

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_RFS_HFR doi:10.48322/gf9t-4082
Proper citations should include the "Accessed on date" in the form .

Description

PSP FIELDS Radio Frequency Spectrometer (RFS), HFR data.
The RFS is the high frequency component  of the FIELDS experiment on the  Parker
Solar Probe spacecraft [1].  For a full description of the FIELDS  experiment,
see [2].  For a description  of the RFS, see [3].
The RFS produces auto and cross spectral data products in two frequency ranges,
the LFR (Low Frequency Reciever) range and the HFR (High Frequency Receiver)
range.  Telemetered spectral data products for both HFR and LFR contain 64
frequency bins, with the LFR typically covering a frequency range from 10.5 kHz
to 1.7 MHz, and the HFR covering from 1.3 MHz to 19.2 MHz, with approximately
logarithmically spaced bins. LFR HiRes spectra contain 32 finely spaced
frequency bins near the plasma frequency. The exact frequency bins are
selectable and are included as metadata variables in this file.
The Level 2 data products contained in this data file have been calibrated for
the preamp and RFS analog section response, and the polyphase filter bank (PFB)
and the FFT spectral processing as described in [3].  Corrections for base
capacitance and antenna effective length have not been applied (these
corrections will be applied in Level 3 RFS data.) Therefore, units for all
spectral quantities are given in V^2/Hz.
Time resolution of the RFS varies with instrument mode.  During encounter (when
PSP is within 0.25 AU of the Sun), cadence for RFS HFR and LFR spectra is
typically about 7 seconds.  During cruise mode, which is the default mode for
operations outside of 0.25 AU, cadence for HFR and LFR spectra is about 56
seconds.
References:
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s11214-015-0211-6
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s11214-016-0244-5
3. Pulupa, M., Bale, S. D., Bonnell, J.W. et al. (2017) JGR Space Physics, 122,
2836-2854. https://doi.org/10.1002/2016JA023345

Modification History

Revision 1
Revision 2: Corrected 'Instrument_type' metadata
Revision 3: Corrected error where onboard compression could generate telemetered
spectral data with an incorrect value of zero

Data Variable Descriptions

HFR Auto Spectra, Ch0: V1V2 [psp_fld_l2_rfs_hfr_auto_averages_ch0_V1V2]

Gain flag for HFR Auto Spectra, Ch0: V1V2 [psp_fld_l2_rfs_hfr_auto_averages_ch0_V1V2_gain]

0: Low gain, 1: High gain.

N summed spectra for HFR Auto Spectra, Ch0: V1V2 [psp_fld_l2_rfs_hfr_auto_averages_ch0_V1V2_nsum]

Overrange flag for HFR Auto Spectra, Ch0: V1V2 [psp_fld_l2_rfs_hfr_auto_averages_ch0_V1V2_hl]

Overrange flag indicates an overrange condition in at least one input waveform
collected during the LFR or HFR accumulation interval (see Ref. [3]).0: No
overranges, 1: Overrange in Low Gain but not High Gain, 2: Overrange in High
Gain but not Low Gain, 3: Overrange in Low Gain and High Gain.

HFR Auto Spectra, Ch1: V3V4 [psp_fld_l2_rfs_hfr_auto_averages_ch1_V3V4]

Gain flag for HFR Auto Spectra, Ch1: V3V4 [psp_fld_l2_rfs_hfr_auto_averages_ch1_V3V4_gain]

0: Low gain, 1: High gain.

N summed spectra for HFR Auto Spectra, Ch1: V3V4 [psp_fld_l2_rfs_hfr_auto_averages_ch1_V3V4_nsum]

Overrange flag for HFR Auto Spectra, Ch1: V3V4 [psp_fld_l2_rfs_hfr_auto_averages_ch1_V3V4_hl]

Overrange flag indicates an overrange condition in at least one input waveform
collected during the LFR or HFR accumulation interval (see Ref. [3]).0: No
overranges, 1: Overrange in Low Gain but not High Gain, 2: Overrange in High
Gain but not Low Gain, 3: Overrange in Low Gain and High Gain.

HFR Peak Spectra, Ch0: V1V2 [psp_fld_l2_rfs_hfr_auto_peaks_ch0_V1V2]

Gain flag for HFR Peak Spectra, Ch0: V1V2 [psp_fld_l2_rfs_hfr_auto_peaks_ch0_V1V2_gain]

0: Low gain, 1: High gain.

N summed spectra for HFR Peak Spectra, Ch0: V1V2 [psp_fld_l2_rfs_hfr_auto_peaks_ch0_V1V2_nsum]

Overrange flag for HFR Peak Spectra, Ch0: V1V2 [psp_fld_l2_rfs_hfr_auto_peaks_ch0_V1V2_hl]

Overrange flag indicates an overrange condition in at least one input waveform
collected during the LFR or HFR accumulation interval (see Ref. [3]).0: No
overranges, 1: Overrange in Low Gain but not High Gain, 2: Overrange in High
Gain but not Low Gain, 3: Overrange in Low Gain and High Gain.

HFR Peak Spectra, Ch1: V3V4 [psp_fld_l2_rfs_hfr_auto_peaks_ch1_V3V4]

Gain flag for HFR Peak Spectra, Ch1: V3V4 [psp_fld_l2_rfs_hfr_auto_peaks_ch1_V3V4_gain]

0: Low gain, 1: High gain.

N summed spectra for HFR Peak Spectra, Ch1: V3V4 [psp_fld_l2_rfs_hfr_auto_peaks_ch1_V3V4_nsum]

Overrange flag for HFR Peak Spectra, Ch1: V3V4 [psp_fld_l2_rfs_hfr_auto_peaks_ch1_V3V4_hl]

Overrange flag indicates an overrange condition in at least one input waveform
collected during the LFR or HFR accumulation interval (see Ref. [3]).0: No
overranges, 1: Overrange in Low Gain but not High Gain, 2: Overrange in High
Gain but not Low Gain, 3: Overrange in Low Gain and High Gain.

HFR Cross Spectra Imag Part, Ch0: V1V2 Ch1: V3V4 [psp_fld_l2_rfs_hfr_cross_im_V1V2_V3V4]

Gain flag for HFR Cross Spectra Imag Part, Ch0: V1V2 Ch1: V3V4 [psp_fld_l2_rfs_hfr_cross_im_V1V2_V3V4_gain]

0: Low gain, 1: High gain.

N summed spectra for HFR Cross Spectra Imag Part, Ch0: V1V2 Ch1: V3V4 [psp_fld_l2_rfs_hfr_cross_im_V1V2_V3V4_nsum]

Overrange flag for HFR Cross Spectra Imag Part, Ch0: V1V2 Ch1: V3V4 [psp_fld_l2_rfs_hfr_cross_im_V1V2_V3V4_hl]

Overrange flag indicates an overrange condition in at least one input waveform
collected during the LFR or HFR accumulation interval (see Ref. [3]).0: No
overranges, 1: Overrange in Low Gain but not High Gain, 2: Overrange in High
Gain but not Low Gain, 3: Overrange in Low Gain and High Gain.

HFR Cross Spectra Real Part, Ch0: V1V2 Ch1: V3V4 [psp_fld_l2_rfs_hfr_cross_re_V1V2_V3V4]

Gain flag for HFR Cross Spectra Real Part, Ch0: V1V2 Ch1: V3V4 [psp_fld_l2_rfs_hfr_cross_re_V1V2_V3V4_gain]

0: Low gain, 1: High gain.

N summed spectra for HFR Cross Spectra Real Part, Ch0: V1V2 Ch1: V3V4 [psp_fld_l2_rfs_hfr_cross_re_V1V2_V3V4_nsum]

Overrange flag for HFR Cross Spectra Real Part, Ch0: V1V2 Ch1: V3V4 [psp_fld_l2_rfs_hfr_cross_re_V1V2_V3V4_hl]

Overrange flag indicates an overrange condition in at least one input waveform
collected during the LFR or HFR accumulation interval (see Ref. [3]).0: No
overranges, 1: Overrange in Low Gain but not High Gain, 2: Overrange in High
Gain but not Low Gain, 3: Overrange in Low Gain and High Gain.

HFR Cross Coherence, Ch0: V1V2 Ch1: V3V4 [psp_fld_l2_rfs_hfr_coher_V1V2_V3V4]

Gain flag for HFR Cross Coherence, Ch0: V1V2 Ch1: V3V4 [psp_fld_l2_rfs_hfr_coher_V1V2_V3V4_gain]

0: Low gain, 1: High gain.

N summed spectra for HFR Cross Coherence, Ch0: V1V2 Ch1: V3V4 [psp_fld_l2_rfs_hfr_coher_V1V2_V3V4_nsum]

Overrange flag for HFR Cross Coherence, Ch0: V1V2 Ch1: V3V4 [psp_fld_l2_rfs_hfr_coher_V1V2_V3V4_hl]

Overrange flag indicates an overrange condition in at least one input waveform
collected during the LFR or HFR accumulation interval (see Ref. [3]).0: No
overranges, 1: Overrange in Low Gain but not High Gain, 2: Overrange in High
Gain but not Low Gain, 3: Overrange in Low Gain and High Gain.

HFR Cross Phase, Ch0: V1V2 Ch1: V3V4 [psp_fld_l2_rfs_hfr_phase_V1V2_V3V4]

Gain flag for HFR Cross Phase, Ch0: V1V2 Ch1: V3V4 [psp_fld_l2_rfs_hfr_phase_V1V2_V3V4_gain]

0: Low gain, 1: High gain.

N summed spectra for HFR Cross Phase, Ch0: V1V2 Ch1: V3V4 [psp_fld_l2_rfs_hfr_phase_V1V2_V3V4_nsum]

Overrange flag for HFR Cross Phase, Ch0: V1V2 Ch1: V3V4 [psp_fld_l2_rfs_hfr_phase_V1V2_V3V4_hl]

Overrange flag indicates an overrange condition in at least one input waveform
collected during the LFR or HFR accumulation interval (see Ref. [3]).0: No
overranges, 1: Overrange in Low Gain but not High Gain, 2: Overrange in High
Gain but not Low Gain, 3: Overrange in Low Gain and High Gain.

Averages enable flag for all HFR spectra [psp_fld_l2_rfs_hfr_averages]

Average mode enable flag for all HFR spectra. A value of 1 indicates that
average mode is enabled, and a value of 0 indicates that average mode is
disabled.

Peak enable flag for all HFR spectra [psp_fld_l2_rfs_hfr_peaks]

Peak mode enable flag for all HFR spectra. A value of 1 indicates that peak mode
is enabled, and a value of 0 indicates that peak mode is disabled.

Channel 0 source for all HFR spectra [psp_fld_l2_rfs_hfr_ch0]

Source for HFR Channel 0 data. 0: V1V2, 1: V1V3, 2: V2V4, 3: SCM, 4: V1, 5: V3,
6: GND, 7: GND.

Channel 1 source for all HFR spectra [psp_fld_l2_rfs_hfr_ch1]

Source for HFR Channel 1 data. 0: V3V4, 1: V3V2, 2: V1V4, 3: SCM, 4: V2, 5: V4,
6: GND, 7: GND.

N summed spectra for all HFR spectra [psp_fld_l2_rfs_hfr_nsum]

Number of summed individual spectra for HFR auto and cross reduced spectra.

Gain flag for all HFR spectra [psp_fld_l2_rfs_hfr_gain]

Gain flag for HFR auto and cross reduced spectra. 0: Low gain, 1: High gain.

Overrange flag for all HFR spectra [psp_fld_l2_rfs_hfr_hl]

Overrange flag for HFR auto and cross reduced spectra.  Flag indicates an
overrange condition in at least one input waveform collected during the LFR or
HFR accumulation interval (see Ref. [3]).0: No overranges, 1: Overrange in Low
Gain but not High Gain, 2: Overrange in High Gain but not Low Gain, 3: Overrange
in Low Gain and High Gain.

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_RFS_LFR doi:10.48322/re4h-tk40
Proper citations should include the "Accessed on date" in the form .

Description

PSP FIELDS Radio Frequency Spectrometer (RFS), LFR data.
The RFS is the high frequency component  of the FIELDS experiment on the  Parker
Solar Probe spacecraft [1].  For a full description of the FIELDS  experiment,
see [2].  For a description  of the RFS, see [3].
The RFS produces auto and cross spectral data products in two frequency ranges,
the LFR (Low Frequency Reciever) range and the HFR (High Frequency Receiver)
range.  Telemetered spectral data products for both HFR and LFR contain 64
frequency bins, with the LFR typically covering a frequency range from 10.5 kHz
to 1.7 MHz, and the HFR covering from 1.3 MHz to 19.2 MHz, with approximately
logarithmically spaced bins. LFR HiRes spectra contain 32 finely spaced
frequency bins near the plasma frequency. The exact frequency bins are
selectable and are included as metadata variables in this file.
The Level 2 data products contained in this data file have been calibrated for
the preamp and RFS analog section response, and the polyphase filter bank (PFB)
and the FFT spectral processing as described in [3].  Corrections for base
capacitance and antenna effective length have not been applied (these
corrections will be applied in Level 3 RFS data.) Therefore, units for all
spectral quantities are given in V^2/Hz.
Time resolution of the RFS varies with instrument mode.  During encounter (when
PSP is within 0.25 AU of the Sun), cadence for RFS HFR and LFR spectra is
typically about 7 seconds.  During cruise mode, which is the default mode for
operations outside of 0.25 AU, cadence for HFR and LFR spectra is about 56
seconds.
References:
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s11214-015-0211-6
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s11214-016-0244-5
3. Pulupa, M., Bale, S. D., Bonnell, J.W. et al. (2017) JGR Space Physics, 122,
2836-2854. https://doi.org/10.1002/2016JA023345

Modification History

Revision 1
Revision 2: Corrected 'Instrument_type' metadata
Revision 3: Corrected error where onboard compression could generate telemetered
spectral data with an incorrect value of zero

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L2_TDS_WF

Description

PSP FIELDS TDS_WF Science Telemetry Data

Modification History

2020-07-29 - Revision 0

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L3_DUST

Description

Database of dust impact detections on Parker Solar Probe via impact plasma
clouds detected by the FIELDS instrument, TDS receiver. Each file contains data
relevant to (i) individual dust impacts (events), (ii) impact rates (rates), and
(ii) ancillary information important for interpreting the dust impact data
(spacecraft pointing, position).
References:
[1] Bale, S.D. et al. "The FIELDS Instrument Suite for Solar Probe Plus.
Measuring the Coronal Plasma and Magnetic Field, Plasma Waves and Turbulence,
and Radio Signatures of Solar Transients" Space Science Reviews, Volume 204,
Issue 1-4, pp. 49-82, December 2016, https://doi.org/10.1007/s11214-016-0244-5 
[2] Malaspina, D.M. et al. "A dust detection database for the inner heliosphere
using the Parker Solar Probe spacecraft", The Astrophysical Journal Supplement
Series, Volume 266, Number 2, May 2023, https://doi.org/10.3847/1538-4365/acca75

Modification History

Version 1: Original release version.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L3_MERGED_SCAM_WF

Description

PSP FIELDS Merged Search Coil Magnetometer and Fluxgate Magnetometer (SCaM),
SCaM data. 
Merged SCaM data is composed of SCM and MAG data from the FIELDS experiment on
the Parker Solar Probe spacecraft [1]. For a full description of the FIELDS
experiment, see [2]. The SCM is sampled by the Digital Fields Board (DFB),
discussed in ref. [3]. For an overview of FIELDS/MAG calibration see ref. [4].
SCaM data consists of continuous time-series data from the SCM and MAG sensors.
Merged SCaM data is a Level 3 (l3) product derived from the direct sum of
weighted and time corrected l1 MAG and SCM data [4]. The weighting coefficients
are designed to optimize the SCaM signal to the integrated instrumental noise
floor.
The Level 3 SCaM product uses SCM data which has been calibrated for (i) DFB
in-band gain, (ii) DFB analog filter gain/phase response, (iii) DFB digital
filter gain/phase response, and (iv) the SCM preamplifier gain/phase response.
The SCM data is empirically gain-matched to the MAG, with correction factors
included in the metadata [4]. Information on SCM sample rate is provided at a 1
min cadence.
The Level 3 SCaM product uses orthogonalized MAG data with spacecraft zero
offsets removed. Spacecraft zero offset data, along with the native MAG range
and sample-rate meta-data is provided at a 1 minute cadence. 
The Level 3 SCaM data product in this file may be in spacecraft coordinates
(e.g. X,Y,Z), RTN coordinates (R,T,N), or SCM sensor coordinates (U,V,W). For
large parts of the PSP mission, anomalous performance of the SCM sensor-X axis
(in the U direction) precludes merging in SC or RTN coordinates. In these cases
data is only provided for the SCM sensor coordinate system (V,W).
References: 
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s1121401502116 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s1121401602445 
3. Malaspina, D.M., Ergun, R.E., Bolton, M. et al. (2016) JGR Space Physics,
121, 5088-5096. https://doi.org/10.1002/2016JA022344 
4. Bowen, T.A., Bale, S.D., Bonnell, J.W., Dudok DeWit, T. et al. (2020) JGR
Space Physics, https://doi.org/10.1029/2020JA027813

Modification History

V1: Initial version
V2: Added sensor coordinate data (two-axis after Encounter 1)

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L3_RFS_HFR doi:tbd
Proper citations should include the "Accessed on date" in the form .

Description

PSP FIELDS Radio Frequency Spectrometer (RFS), HFR data.
The RFS is the high frequency component of the FIELDS experiment on the Parker
Solar Probe spacecraft [1]. For a full description of the FIELDS experiment, see
[2]. For a description of the RFS, see [3].
The RFS produces auto and cross spectral data products in two frequency ranges,
the LFR (Low Frequency Receiver) range and the HFR (High Frequency Receiver)
range. Telemetered spectral data products for both HFR and LFR contain 64
frequency bins, with the LFR typically covering a frequency range from 10.5 kHz
to 1.7 MHz, and the HFR covering from 1.3 MHz to 19.2 MHz, with approximately
logarithmically spaced bins. LFR HiRes spectra contain 32 finely spaced
frequency bins near the plasma frequency. The exact frequency bins are
selectable and are included as metadata variables in this file.
The Level 3 data products contained in this data file have been calibrated for
the preamp and RFS analog section response, the polyphase filter bank (PFB), and
the FFT spectral processing as described in [3]. Instrumental background noise
from the preamp and RFS analog section has been removed from the L3 data. Level
3 flux variables are converted from power spectral density using base
capacitance and antenna effective length values from [4]. This conversion
assumes that the PSP/FIELDS antenna response can be characterized as an ideal
short dipole, and the antenna impedance is capacitive. At higher frequencies
(above ~7 MHz), the antenna no longer responds as an ideal dipole, and at very
high densities, the resistive component of the antenna impedance can result in
an impedance that is not purely capacitive. The effects of non-ideal dipole
antenna response and non-capacitive impedance are not included in the current
version of Level 3 processing.
Units for spectral quantities are V^2/Hz and W/m^2/Hz (flux). Flux is computed
for cross dipole measurements (V1V2 and V3V4) and for
psp_fld_l3_rfs_hfr_PSD_FLUX.
The psp_fld_l3_rfs_hfr_PSD_FLUX, psp_fld_l3_rfs_hfr_PSD_SFU, and
psp_fld_l3_rfs_hfr_STOKES_V variables incorporate both RFS channels to generate
an estimate of power spectral density and circular polarization for radio
emission with a source near the Sun. Corrections for spacecraft attitude and
antenna non-orthogonality have been applied [5]. The PSD_SFU variable contains
the flux from PSD_FLUX, converted to sfu and normalized to a distance of 1 au.
These quantities are directly comparable to the equivalently named quantities in
the STEREO and Solar Orbiter Level 3 CDF files.
Time resolution of the RFS varies with instrument mode. During encounter (when
PSP is within 0.25 AU of the Sun), cadence for RFS HFR and LFR spectra is
typically about 7 seconds.  During cruise mode, which is the default mode for
operations outside of 0.25 AU, cadence for HFR and LFR spectra is about 56
seconds.
References:
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s11214-015-0211-6
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s11214-016-0244-5
3. Pulupa, M., Bale, S. D., Bonnell, J.W. et al. (2017) JGR Space Physics, 122,
2836-2854. https://doi.org/10.1002/2016JA023345 
4. Page, B., Bassett, N., Lecacheux, A. et al. (2022) Astronomy & Astrophysics,
668, A127. https://doi.org/10.1051/0004-6361/202244621 
5. Lecacheux, A. (2011) in Planetary, Solar and Heliospheric Radio Emissions
(PRE VII), 13-36. https://doi.org/10.1553/PRE7s13

Modification History

Revision 1
Revision 2: Corrected 'Instrument_type' metadata
Revision 3: Corrected error where onboard compression could generate telemetered
spectral data with an incorrect value of zero

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L3_RFS_LFR doi:tbd
Proper citations should include the "Accessed on date" in the form .

Description

PSP FIELDS Radio Frequency Spectrometer (RFS), LFR data.
The RFS is the high frequency component of the FIELDS experiment on the Parker
Solar Probe spacecraft [1]. For a full description of the FIELDS experiment, see
[2]. For a description of the RFS, see [3].
The RFS produces auto and cross spectral data products in two frequency ranges,
the LFR (Low Frequency Receiver) range and the HFR (High Frequency Receiver)
range. Telemetered spectral data products for both HFR and LFR contain 64
frequency bins, with the LFR typically covering a frequency range from 10.5 kHz
to 1.7 MHz, and the HFR covering from 1.3 MHz to 19.2 MHz, with approximately
logarithmically spaced bins. LFR HiRes spectra contain 32 finely spaced
frequency bins near the plasma frequency. The exact frequency bins are
selectable and are included as metadata variables in this file.
The Level 3 data products contained in this data file have been calibrated for
the preamp and RFS analog section response, the polyphase filter bank (PFB), and
the FFT spectral processing as described in [3]. Instrumental background noise
from the preamp and RFS analog section has been removed from the L3 data. Level
3 flux variables are converted from power spectral density using base
capacitance and antenna effective length values from [4]. This conversion
assumes that the PSP/FIELDS antenna response can be characterized as an ideal
short dipole, and the antenna impedance is capacitive. At higher frequencies
(above ~7 MHz), the antenna no longer responds as an ideal dipole, and at very
high densities, the resistive component of the antenna impedance can result in
an impedance that is not purely capacitive. The effects of non-ideal dipole
antenna response and non-capacitive impedance are not included in the current
version of Level 3 processing.
Units for spectral quantities are V^2/Hz and W/m^2/Hz (flux). Flux is computed
for cross dipole measurements (V1V2 and V3V4) and for
psp_fld_l3_rfs_lfr_PSD_FLUX.
The psp_fld_l3_rfs_lfr_PSD_FLUX, psp_fld_l3_rfs_lfr_PSD_SFU, and
psp_fld_l3_rfs_lfr_STOKES_V variables incorporate both RFS channels to generate
an estimate of power spectral density and circular polarization for radio
emission with a source near the Sun. Corrections for spacecraft attitude and
antenna non-orthogonality have been applied [5]. The PSD_SFU variable contains
the flux from PSD_FLUX, converted to sfu and normalized to a distance of 1 au.
These quantities are directly comparable to the equivalently named quantities in
the STEREO and Solar Orbiter Level 3 CDF files.
Time resolution of the RFS varies with instrument mode. During encounter (when
PSP is within 0.25 AU of the Sun), cadence for RFS HFR and LFR spectra is
typically about 7 seconds.  During cruise mode, which is the default mode for
operations outside of 0.25 AU, cadence for HFR and LFR spectra is about 56
seconds.
References:
1. Fox, N.J., Velli, M.C., Bale, S.D. et al. Space Sci Rev (2016) 204: 7.
https://doi.org/10.1007/s11214-015-0211-6
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s11214-016-0244-5
3. Pulupa, M., Bale, S. D., Bonnell, J.W. et al. (2017) JGR Space Physics, 122,
2836-2854. https://doi.org/10.1002/2016JA023345 
4. Page, B., Bassett, N., Lecacheux, A. et al. (2022) Astronomy & Astrophysics,
668, A127. https://doi.org/10.1051/0004-6361/202244621 
5. Lecacheux, A. (2011) in Planetary, Solar and Heliospheric Radio Emissions
(PRE VII), 13-36. https://doi.org/10.1553/PRE7s13

Modification History

Revision 1
Revision 2: Corrected 'Instrument_type' metadata
Revision 3: Corrected error where onboard compression could generate telemetered
spectral data with an incorrect value of zero

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L3_RFS_LFR_QTN

Description

Quasi-thermal noise (QTN) spectroscopy is an efficient tool for measuring in
situ macroscopic plasma properties in space, using a passive wave receiver at
the ports of an electric antenna [1]. The Radio Frequency Spectrometer (RFS) is
a dual channel digital spectrometer, designed for both remote sensing of radio
waves and in situ measurement of electrostatic fluctuations using signals from
the V1-V4 electric field antennas [2]. Usually, the two RFS channels record
differences between V1-V2 and V3-V4 antennas (dipole mode). It allows us to
retrieve plasma properties independently by two sets of antennas. The plasma
line is automatically identified in a frequency range determined by the density
model based on spacecraft distance from the Sun. The frequency range is manually
adjusted for intervals when the plasma line occurs at lower or higher
frequencies than predicted. We assume that the plasma line is well identified if
detected at the same frequency by the V1-V2 and V3-V4 dipoles simultaneously. We
assume that the plasma frequency is equal to the geometric mean of the plasma
line and the preceding  frequency channel. In other words, the plasma frequency
corresponds to the steepest positive slope below the plasma line. The provided
error bars are calculated from the frequency resolution of the RFS instrument.
[1] Meyer-Vernet, N., Issautier, K., & Moncuquet, M. (2017). Quasi-thermal noise
spectroscopy: The art and the practice. Journal of Geophysical Research: Space
Physics, 122, 7925-7945. https://doi.org/10.1002/2017ja024449 
[2] Bale, S. D., Goetz, K., Harvey, P. R., Turin, P., Bonnell, J. W., Dudok de
Wit, T., et al. (2016). The FIELDS instrument suite for Solar probe plus.
Measuring the coronal plasma and magnetic field, plasma waves and turbulence,
and radio signatures of Solar transients. Space Science Reviews, 204(1-4),
49-82. https://doi.org/10.1007/s11214-016-0244-5

Modification History

2021-10-07: CDF skeleton created (VK)

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_FLD_L3_SQTN_RFS_V1V2 doi:tbd
Proper citations should include the "Accessed on date" in the form .

Description

Parker Solar Probe/FIELDS Simplified Quasi-Thermal Noise data (SQTN).
The SQTN spectroscopy is a method which allows to deduce the electron density
and the core temperature of the plasma surrounding a s/c, by using the power
spectra acquired from an electric dipole antenna (see [1] for the PSP case, and
references therein).
There are two dipoles on the PSP/FIELDS experiment [2] exploitable for the SQTN,
named V1V2 and V3V4, which are both connected to the FIELDS Radio Frequency
Spectrometer (RFS), see [3].
The density is deduced from the plasma frequency (fp) detection algorithm,
applied to RFS available spectra, with elimination of questionable detection (or
false positive) using QTN theory (see [1]). No fp detection results in filling
the data by -1e31 (for all variables provided here). In particular, since we are
using 2x2m dipoles on PSP, the fp detection is impossible when the local Debye
length is larger than about 5m. On a daily basis, the typical rate of validated
detection of fp is more than 90% of the available spectra when PSP is within
0.25 AU of the Sun, but this rate may drop to only 20% at larger distances (0.5
AU being the upper limit used to product this CDF file, which corresponds at
most to +/- 15 days around the exact date of the PSP perihelion).
When the fp detection is validated, fp errors bars are defined taking into
account the RFS_LFR spectral resolution (64 pseudo-logarithmically spaced
frequencies in the range of 10 kHz-1.7 MHz), then refined by using QTN theory,
and this finally provides the error bars for the density
(electron_density_delta). The electron density is then deduced as the most
probable value within the error bars, using again QTN theory.
Note the electron density provided here is fully independant of antennas
calibrations and floating potential, but not the electron core temperature which
is deduced from the QTN level below fp (see [1]), so the core temperature will
be certainly more subject to future improvments of this CDF file (see version
and mods, v00 corresponding to the method exactly as published for the two first
encounters/perihelions by PSP in [1]).
All variables provided here were not subject to post-processing noise filtering
nor any interpolation/smoothing of data.
The time resolution of the RFS varies with instrument mode, so does these
electron data derived from RFS data.  During encounter (when PSP is within 0.25
AU of the Sun), cadence for RFS HFR and LFR spectra is typically about 7 seconds
(and about 3.5 seconds during +/- 3 days around the perihelion date from
encounter 06). During cruise mode, which is the default mode for operations
outside of 0.25 AU, cadence for HFR and LFR spectra is about 56 seconds.
References:
1. Moncuquet, M., Meyer-Vernet, N., Issautier, K. et al. (2020), Astrophysical
Journal Supplement Series, 246:44. https://doi.org/10.3847/1538-4365/ab5a84 
2. Bale, S.D., Goetz, K., Harvey, P.R. et al. Space Sci Rev (2016) 204: 49.
https://doi.org/10.1007/s11214-016-0244-5
3. Pulupa, M., Bale, S. D., Bonnell, J.W. et al. (2017) JGR Space Physics, 122,
2836-2854. https://doi.org/10.1002/2016JA023345

Modification History

Version 2.0 corresponds mainly to improvment of the electron core temperature Tc
determination with better calibration of the thermal plateau on a half-daily
basis, using the more-or-less periodic sequences of ~2 minutes where no bias
currents were set on the V1V2 dipole. Only version 2.0 is available from
Encounter 6 and next

Data Variable Descriptions

Electron number density [electron_density]

The electron density is deduced from the automatic detection of the plasma
frequency in RFS spectra with SQTN spectroscopy (see TEXT_global_attributes)

Electron core temperature [electron_core_temperature]

The electron core temperature is deduced from the QTN level below fp in RFS
spectra with SQTN spectroscopy (see TEXT_global_attributes)

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_HELIO1DAY_POSITION doi:10.48322/41s1-hx58

Description

No TEXT global attribute value.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_ISOIS-EPIHI_L2-HET-RATES10 doi:10.48322/6b2f-mx69

Description

EPI-Hi 10 second rates cdf. Time tags indicate midpoint of integration.
Instrument paper: Integrated Science Investigation of the Sun (ISIS): Design of
the Energetic Particle Investigation. McComas, D. J. et al (2016). Space Sci.
Rev., doi:10.1007/s11214-014-0059-1

Modification History

Release 17 (data 5.0.0, code 5.0.0): Add Quality_Flag variable for each epoch
indicating any potential concerns with the data. See the ISOIS Data Glossary for
details.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_ISOIS-EPIHI_L2-HET-RATES300 doi:10.48322/jwkm-bn55

Description

EPI-Hi HET 300 second rates cdf. Time tags indicate midpoint of integration.
Instrument paper: Integrated Science Investigation of the Sun (ISIS): Design of
the Energetic Particle Investigation. McComas, D. J. et al (2016). Space Sci.
Rev., doi:10.1007/s11214-014-0059-1

Modification History

Release 17 (data 5.0.0, code 5.0.0): Add Quality_Flag variable for each epoch
indicating any potential concerns with the data. See the ISOIS Data Glossary for
details.

Data Variable Descriptions

NetoSi sectored count rate side B [B_NetoSi_SECT_Rate]

Pitch angle HETB R17 SECT [HET_B_R17_SECT_PA]

Heliocentric distance [HCI_R]

At timestamp. After Fraenz and Harper, PSS, 2002.

FeGroup sectored count rate side A [A_FeGroup_SECT_Rate]

Nominal Parker Spiral angle HETB [HET_B_SA]

Angle between particle direction and nominal outward Parker Spiral, based on
400km/s solar wind and corotation breakdown at 10Rs.

CNO sectored count rate side B [B_CNO_SECT_Rate]

Pitch angle HETA R17 SECT [HET_A_R17_SECT_PA]

RTN flow direction HETA [HET_A_RTN]

Unit vector, after Fraenz and Harper, PSS, 2002.

RTN flow direction HETA R17 SECT [HET_A_R17_SECT_RTN]

Unit vector, after Fraenz and Harper, PSS, 2002.

HCI flow direction HETB [HET_B_HCI]

Unit vector, after Fraenz and Harper, PSS, 2002.

NetoSi sectored count rate side A [A_NetoSi_SECT_Rate]

HCI longitude [HCI_Lon]

At timestamp. After Fraenz and Harper, PSS, 2002.

Nominal Parker Spiral angle HETB R17 SECT [HET_B_R17_SECT_SA]

Angle between particle direction and nominal outward Parker Spiral, based on
400km/s solar wind and corotation breakdown at 10Rs.

Nominal Parker Spiral angle HETA R17 SECT [HET_A_R17_SECT_SA]

Angle between particle direction and nominal outward Parker Spiral, based on
400km/s solar wind and corotation breakdown at 10Rs.

HGC latitude [HGC_Lat]

At timestamp. After Fraenz and Harper, PSS, 2002.

HCI flow direction HETA [HET_A_HCI]

Unit vector, after Fraenz and Harper, PSS, 2002.

Heliocentric distance [HGC_R]

At timestamp. After Fraenz and Harper, PSS, 2002.

HGC longitude [HGC_Lon]

At timestamp. After Fraenz and Harper, PSS, 2002.

RTN flow direction HETB R17 SECT [HET_B_R17_SECT_RTN]

Unit vector, after Fraenz and Harper, PSS, 2002.

HCI latitude [HCI_Lat]

At timestamp. After Fraenz and Harper, PSS, 2002.

CNO sectored count rate side A [A_CNO_SECT_Rate]

FeGroup sectored count rate side B [B_FeGroup_SECT_Rate]

HCI flow direction HETB R17 SECT [HET_B_R17_SECT_HCI]

Unit vector, after Fraenz and Harper, PSS, 2002.

RTN flow direction HETB [HET_B_RTN]

Unit vector, after Fraenz and Harper, PSS, 2002.

Pitch angle HETB [HET_B_PA]

HCI flow direction HETA R17 SECT [HET_A_R17_SECT_HCI]

Unit vector, after Fraenz and Harper, PSS, 2002.

Nominal Parker Spiral angle HETA [HET_A_SA]

Angle between particle direction and nominal outward Parker Spiral, based on
400km/s solar wind and corotation breakdown at 10Rs.

Pitch angle HETA [HET_A_PA]

Data-quality flag [Quality_Flag]

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_ISOIS-EPIHI_L2-HET-RATES3600 doi:10.48322/ahkk-d044

Description

EPI-Hi HET 3600 second rates cdf. Time tags indicate midpoint of integration.
Instrument paper: Integrated Science Investigation of the Sun (ISIS): Design of
the Energetic Particle Investigation. McComas, D. J. et al (2016). Space Sci.
Rev., doi:10.1007/s11214-014-0059-1

Modification History

Release 17 (data 5.0.0, code 5.0.0): Add Quality_Flag variable for each epoch
indicating any potential concerns with the data. See the ISOIS Data Glossary for
details.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_ISOIS-EPIHI_L2-HET-RATES60 doi:10.48322/7gr7-1791

Description

EPI-Hi HET 60 second rates cdf. Time tags indicate midpoint of integration.
Instrument paper: Integrated Science Investigation of the Sun (ISIS): Design of
the Energetic Particle Investigation. McComas, D. J. et al (2016). Space Sci.
Rev., doi:10.1007/s11214-014-0059-1

Modification History

Release 17 (data 5.0.0, code 5.0.0): Add Quality_Flag variable for each epoch
indicating any potential concerns with the data. See the ISOIS Data Glossary for
details.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_ISOIS-EPIHI_L2-LET1-RATES10 doi:10.48322/nez9-cx16

Description

EPI-Hi 10 second rates cdf. Time tags indicate midpoint of integration.
Instrument paper: Integrated Science Investigation of the Sun (ISIS): Design of
the Energetic Particle Investigation. McComas, D. J. et al (2016). Space Sci.
Rev., doi:10.1007/s11214-014-0059-1

Modification History

Release 17 (data 5.0.0, code 5.0.0): Add Quality_Flag variable for each epoch
indicating any potential concerns with the data. See the ISOIS Data Glossary for
details.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_ISOIS-EPIHI_L2-LET1-RATES300 doi:10.48322/53vk-b987

Description

EPI-Hi LET1 300 second rates cdf. Time tags indicate midpoint of integration.
Instrument paper: Integrated Science Investigation of the Sun (ISIS): Design of
the Energetic Particle Investigation. McComas, D. J. et al (2016). Space Sci.
Rev., doi:10.1007/s11214-014-0059-1

Modification History

Release 17 (data 5.0.0, code 5.0.0): Add Quality_Flag variable for each epoch
indicating any potential concerns with the data. See the ISOIS Data Glossary for
details.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_ISOIS-EPIHI_L2-LET1-RATES3600 doi:10.48322/xkhj-qx02

Description

EPI-Hi 3600 seconds rates cdf. Time tags indicate midpoint of integration.
Instrument paper: Integrated Science Investigation of the Sun (ISIS): Design of
the Energetic Particle Investigation. McComas, D. J. et al (2016). Space Sci.
Rev., doi:10.1007/s11214-014-0059-1

Modification History

Release 17 (data 5.0.0, code 5.0.0): Add Quality_Flag variable for each epoch
indicating any potential concerns with the data. See the ISOIS Data Glossary for
details.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_ISOIS-EPIHI_L2-LET1-RATES60 doi:10.48322/97te-0132

Description

EPI-Hi LET1 60 second rates cdf. Time tags indicate midpoint of integration.
Instrument paper: Integrated Science Investigation of the Sun (ISIS): Design of
the Energetic Particle Investigation. McComas, D. J. et al (2016). Space Sci.
Rev., doi:10.1007/s11214-014-0059-1

Modification History

Release 17 (data 5.0.0, code 5.0.0): Add Quality_Flag variable for each epoch
indicating any potential concerns with the data. See the ISOIS Data Glossary for
details.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_ISOIS-EPIHI_L2-LET2-RATES10 doi:10.48322/7853-6s02

Description

EPI-Hi 10 second rates cdf. Time tags indicate midpoint of integration.
Instrument paper: Integrated Science Investigation of the Sun (ISIS): Design of
the Energetic Particle Investigation. McComas, D. J. et al (2016). Space Sci.
Rev., doi:10.1007/s11214-014-0059-1

Modification History

Release 17 (data 5.0.0, code 5.0.0): Add Quality_Flag variable for each epoch
indicating any potential concerns with the data. See the ISOIS Data Glossary for
details.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_ISOIS-EPIHI_L2-LET2-RATES300 doi:10.48322/k5z7-rv23

Description

EPI-Hi LET2 300 second rates cdf. Time tags indicate midpoint of integration.
Instrument paper: Integrated Science Investigation of the Sun (ISIS): Design of
the Energetic Particle Investigation. McComas, D. J. et al (2016). Space Sci.
Rev., doi:10.1007/s11214-014-0059-1

Modification History

Release 17 (data 5.0.0, code 5.0.0): Add Quality_Flag variable for each epoch
indicating any potential concerns with the data. See the ISOIS Data Glossary for
details.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_ISOIS-EPIHI_L2-LET2-RATES3600 doi:10.48322/2xj3-hj37

Description

EPI-Hi LET2 3600 second rates cdf. Time tags indicate midpoint of integration.
Instrument paper: Integrated Science Investigation of the Sun (ISIS): Design of
the Energetic Particle Investigation. McComas, D. J. et al (2016). Space Sci.
Rev., doi:10.1007/s11214-014-0059-1

Modification History

Release 17 (data 5.0.0, code 5.0.0): Add Quality_Flag variable for each epoch
indicating any potential concerns with the data. See the ISOIS Data Glossary for
details.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_ISOIS-EPIHI_L2-LET2-RATES60 doi:10.48322/54ew-zj36

Description

EPI-Hi LET2 60 second rates cdf. Time tags indicate midpoint of integration.
Instrument paper: Integrated Science Investigation of the Sun (ISIS): Design of
the Energetic Particle Investigation. McComas, D. J. et al (2016). Space Sci.
Rev., doi:10.1007/s11214-014-0059-1

Modification History

Release 17 (data 5.0.0, code 5.0.0): Add Quality_Flag variable for each epoch
indicating any potential concerns with the data. See the ISOIS Data Glossary for
details.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_ISOIS-EPIHI_L2-SECOND-RATES doi:10.48322/8ng6-5z57

Description

EPI-Hi second rates cdf. Time tags indicate time of collection.
Instrument paper: Integrated Science Investigation of the Sun (ISIS): Design of
the Energetic Particle Investigation. McComas, D. J. et al (2016). Space Sci.
Rev., doi:10.1007/s11214-014-0059-1

Modification History

Release 17 (data 5.0.0, code 5.0.0): Add Quality_Flag variable for each epoch
indicating any potential concerns with the data. See the ISOIS Data Glossary for
details.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_ISOIS-EPILO_L2-IC doi:10.48322/vrve-qw24

Description

EPI-Lo, Ion Composition mode.
Instrument paper: Integrated Science Investigation of the Sun (ISIS): Design of
the Energetic Particle Investigation. McComas, D. J. et al (2016). Space Sci.
Rev., doi:10.1007/s11214-014-0059-1

Modification History

Release 17 (data 5.0.0, code 5.0.0): Add Quality_Flag variable for each epoch
indicating any potential concerns with the data. See the ISOIS Data Glossary for
details.
Release 20 (data 6.0.0, code 6.0.0): Add testing periods quality flag.

Data Variable Descriptions

Data-quality flag for channel C (Ions1) [Quality_Flag_ChanC]

Data-quality flag for channel D (Ions2) [Quality_Flag_ChanD]

Data-quality flag for channel P (HiResProtons) [Quality_Flag_ChanP]

Data-quality flag for channel R (HiTimeResProtons) [Quality_Flag_ChanR]

Data-quality flag for channel T (IonTOF) [Quality_Flag_ChanT]

[Spectrogram, averaged over 80 Look Directions for these variables] H count rate channel P (HiResProtons) [H_CountRate_ChanP_avg]

Ion Composition mode. Corrected for deadtime.

---> H flux channel P (HiResProtons) [H_Flux_ChanP_avg (PRIMARY_VAR,SUMMARY)]

Ion Composition mode.

---> H count rate channel R (HiTimeResProtons) [H_CountRate_ChanR_avg]

Ion Composition mode. Corrected for deadtime.

---> H flux channel R (HiTimeResProtons) [H_Flux_ChanR_avg (PRIMARY_VAR,SUMMARY)]

Ion Composition mode.

---> H count rate channel T (IonTOF) [H_CountRate_ChanT_avg]

Ion Composition mode. Corrected for deadtime. May contain significant photon
counts, particularly directions L31, L34, L35. See Hill, M.E. et al., 2020,
ApJS, doi:10.3847/1538-4365/ab643d .

---> H flux channel T (IonTOF) [H_Flux_ChanT_avg (PRIMARY_VAR,SUMMARY)]

Ion Composition mode. May contain significant photon counts, particularly
directions L31, L34, L35. See Hill, M.E. et al., 2020, ApJS,
doi:10.3847/1538-4365/ab643d .

---> He3 count rate channel C (Ions1) [He3_CountRate_ChanC_avg]

Ion Composition mode. Corrected for deadtime.

---> He4 count rate channel C (Ions1) [He4_CountRate_ChanC_avg]

Ion Composition mode. Corrected for deadtime.

---> He4 flux channel C (Ions1) [He4_Flux_ChanC_avg (PRIMARY_VAR,SUMMARY)]

Ion Composition mode.

---> Fe count rate channel C (Ions1) [Fe_CountRate_ChanC_avg]

Ion Composition mode. Corrected for deadtime.

---> Mg count rate channel D (Ions2) [Mg_CountRate_ChanD_avg]

Ion Composition mode. Corrected for deadtime.

---> C count rate channel D (Ions2) [C_CountRate_ChanD_avg]

Ion Composition mode. Corrected for deadtime.

---> O count rate channel C (Ions1) [O_CountRate_ChanC_avg]

Ion Composition mode. Corrected for deadtime.

---> Si count rate channel D (Ions2) [Si_CountRate_ChanD_avg]

Ion Composition mode. Corrected for deadtime.

---> N count rate channel D (Ions2) [N_CountRate_ChanD_avg]

Ion Composition mode. Corrected for deadtime.

---> Ne count rate channel D (Ions2) [Ne_CountRate_ChanD_avg]

Ion Composition mode. Corrected for deadtime.

[All options, except plots, available for these variables] H counts channel P (HiResProtons) [H_Counts_ChanP]

Ion Composition mode. Raw counts per integration.

---> H count rate channel P (HiResProtons) [H_CountRate_ChanP]

Ion Composition mode. Corrected for deadtime.

---> H flux channel P (HiResProtons) [H_Flux_ChanP (PRIMARY_VAR,SUMMARY)]

Ion Composition mode.

---> H counts channel R (HiTimeResProtons) [H_Counts_ChanR]

Ion Composition mode. Raw counts per integration.

---> H count rate channel R (HiTimeResProtons) [H_CountRate_ChanR]

Ion Composition mode. Corrected for deadtime.

---> H flux channel R (HiTimeResProtons) [H_Flux_ChanR (PRIMARY_VAR,SUMMARY)]

Ion Composition mode.

---> H counts channel T (IonTOF) [H_Counts_ChanT]

Ion Composition mode. Raw counts per integration. May contain significant photon
counts, particularly directions L31, L34, L35. See Hill, M.E. et al., 2020,
ApJS, doi:10.3847/1538-4365/ab643d .

---> H count rate channel T (IonTOF) [H_CountRate_ChanT]

Ion Composition mode. Corrected for deadtime. May contain significant photon
counts, particularly directions L31, L34, L35. See Hill, M.E. et al., 2020,
ApJS, doi:10.3847/1538-4365/ab643d .

---> H flux channel T (IonTOF) [H_Flux_ChanT (PRIMARY_VAR,SUMMARY)]

Ion Composition mode. May contain significant photon counts, particularly
directions L31, L34, L35. See Hill, M.E. et al., 2020, ApJS,
doi:10.3847/1538-4365/ab643d .

---> He3 counts channel C (Ions1) [He3_Counts_ChanC]

Ion Composition mode. Raw counts per integration.

---> He3 count rate channel C (Ions1) [He3_CountRate_ChanC]

Ion Composition mode. Corrected for deadtime.

---> He4 counts channel C (Ions1) [He4_Counts_ChanC]

Ion Composition mode. Raw counts per integration.

---> He4 count rate channel C (Ions1) [He4_CountRate_ChanC]

Ion Composition mode. Corrected for deadtime.

---> He4 flux channel C (Ions1) [He4_Flux_ChanC (PRIMARY_VAR,SUMMARY)]

Ion Composition mode.

---> Fe counts channel C (Ions1) [Fe_Counts_ChanC]

Ion Composition mode. Raw counts per integration.

---> Fe count rate channel C (Ions1) [Fe_CountRate_ChanC]

Ion Composition mode. Corrected for deadtime.

---> Mg counts channel D (Ions2) [Mg_Counts_ChanD]

Ion Composition mode. Raw counts per integration.

---> Mg count rate channel D (Ions2) [Mg_CountRate_ChanD]

Ion Composition mode. Corrected for deadtime.

---> C counts channel D (Ions2) [C_Counts_ChanD]

Ion Composition mode. Raw counts per integration.

---> C count rate channel D (Ions2) [C_CountRate_ChanD]

Ion Composition mode. Corrected for deadtime.

---> O counts channel C (Ions1) [O_Counts_ChanC]

Ion Composition mode. Raw counts per integration.

---> O count rate channel C (Ions1) [O_CountRate_ChanC]

Ion Composition mode. Corrected for deadtime.

---> Si counts channel D (Ions2) [Si_Counts_ChanD]

Ion Composition mode. Raw counts per integration.

---> Si count rate channel D (Ions2) [Si_CountRate_ChanD]

Ion Composition mode. Corrected for deadtime.

---> N counts channel D (Ions2) [N_Counts_ChanD]

Ion Composition mode. Raw counts per integration.

---> N count rate channel D (Ions2) [N_CountRate_ChanD]

Ion Composition mode. Corrected for deadtime.

---> Ne counts channel D (Ions2) [Ne_Counts_ChanD]

Ion Composition mode. Raw counts per integration.

---> Ne count rate channel D (Ions2) [Ne_CountRate_ChanD]

Ion Composition mode. Corrected for deadtime.

HCI flow direction ChanC - no plot [HCI_ChanC]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanC timebase.

---> Look direction 00 - stack plot [HCI_ChanC_L00]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanC timebase.

---> Look direction 11 [HCI_ChanC_L11]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanC timebase.

---> Look direction 22 [HCI_ChanC_L22]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanC timebase.

---> Look direction 33 [HCI_ChanC_L33]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanC timebase.

---> Look direction 44 [HCI_ChanC_L44]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanC timebase.

---> Look direction 55 [HCI_ChanC_L55]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanC timebase.

---> Look direction 66 [HCI_ChanC_L66]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanC timebase.

---> Look direction 77 [HCI_ChanC_L77]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanC timebase.

HCI Heliocentric distance ChanC [HCI_R_ChanC]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanC timebase.

HCI latitude ChanC [HCI_Lat_ChanC]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanC timebase.

HCI longitude ChanC [HCI_Lon_ChanC]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanC timebase.

HCI flow direction ChanD - no plot [HCI_ChanD]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanD timebase.

---> Look direction 00 - stack plot [HCI_ChanD_L00]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanD timebase.

---> Look direction 11 [HCI_ChanD_L11]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanD timebase.

---> Look direction 22 [HCI_ChanD_L22]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanD timebase.

---> Look direction 33 [HCI_ChanD_L33]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanD timebase.

---> Look direction 44 [HCI_ChanD_L44]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanD timebase.

---> Look direction 55 [HCI_ChanD_L55]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanD timebase.

---> Look direction 66 [HCI_ChanD_L66]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanD timebase.

---> Look direction 77 [HCI_ChanD_L77]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanD timebase.

HCI Heliocentric distance ChanD [HCI_R_ChanD]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanD timebase.

HCI latitude ChanD [HCI_Lat_ChanD]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanD timebase.

HCI longitude ChanD [HCI_Lon_ChanD]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanD timebase.

HCI flow direction ChanP - no plot [HCI_ChanP]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanP timebase.

---> Look direction 00 - stack plot [HCI_ChanP_L00]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanP timebase.

---> Look direction 11 [HCI_ChanP_L11]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanP timebase.

---> Look direction 22 [HCI_ChanP_L22]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanP timebase.

---> Look direction 33 [HCI_ChanP_L33]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanP timebase.

---> Look direction 44 [HCI_ChanP_L44]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanP timebase.

---> Look direction 55 [HCI_ChanP_L55]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanP timebase.

---> Look direction 66 [HCI_ChanP_L66]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanP timebase.

---> Look direction 77 [HCI_ChanP_L77]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanP timebase.

HCI Heliocentric distance ChanP [HCI_R_ChanP]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanP timebase.

HCI latitude ChanP [HCI_Lat_ChanP]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanP timebase.

HCI longitude ChanP [HCI_Lon_ChanP]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanP timebase.

HCI flow direction ChanR - no plot [HCI_ChanR]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanR timebase.

---> Look direction 00 - stack plot [HCI_ChanR_L00]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanR timebase.

---> Look direction 11 [HCI_ChanR_L11]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanR timebase.

---> Look direction 22 [HCI_ChanR_L22]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanR timebase.

---> Look direction 33 [HCI_ChanR_L33]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanR timebase.

---> Look direction 44 [HCI_ChanR_L44]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanR timebase.

---> Look direction 55 [HCI_ChanR_L55]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanR timebase.

---> Look direction 66 [HCI_ChanR_L66]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanR timebase.

---> Look direction 77 [HCI_ChanR_L77]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanR timebase.

HCI Heliocentric distance ChanR [HCI_R_ChanR]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanR timebase.

HCI latitude ChanR [HCI_Lat_ChanR]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanR timebase.

HCI longitude ChanR [HCI_Lon_ChanR]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanR timebase.

HCI flow direction ChanT - no plot [HCI_ChanT]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanT timebase.

---> Look direction 00 - stack plot [HCI_ChanT_L00]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanT timebase.

---> Look direction 11 [HCI_ChanT_L11]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanT timebase.

---> Look direction 22 [HCI_ChanT_L22]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanT timebase.

---> Look direction 33 [HCI_ChanT_L33]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanT timebase.

---> Look direction 44 [HCI_ChanT_L44]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanT timebase.

---> Look direction 55 [HCI_ChanT_L55]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanT timebase.

---> Look direction 66 [HCI_ChanT_L66]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanT timebase.

---> Look direction 77 [HCI_ChanT_L77]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanT timebase.

HCI Heliocentric distance ChanT [HCI_R_ChanT]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanT timebase.

HCI latitude ChanT [HCI_Lat_ChanT]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanT timebase.

HCI longitude ChanT [HCI_Lon_ChanT]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanT timebase.

HGC Heliocentric distance ChanC [HGC_R_ChanC]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanC timebase.

HGC latitude ChanC [HGC_Lat_ChanC]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanC timebase.

HGC longitude ChanC [HGC_Lon_ChanC]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanC timebase.

HGC Heliocentric distance ChanD [HGC_R_ChanD]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanD timebase.

HGC latitude ChanD [HGC_Lat_ChanD]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanD timebase.

HGC longitude ChanD [HGC_Lon_ChanD]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanD timebase.

HGC Heliocentric distance ChanP [HGC_R_ChanP]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanP timebase.

HGC latitude ChanP [HGC_Lat_ChanP]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanP timebase.

HGC longitude ChanP [HGC_Lon_ChanP]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanP timebase.

HGC Heliocentric distance ChanR [HGC_R_ChanR]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanR timebase.

HGC latitude ChanR [HGC_Lat_ChanR]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanR timebase.

HGC longitude ChanR [HGC_Lon_ChanR]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanR timebase.

HGC Heliocentric distance ChanT [HGC_R_ChanT]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanT timebase.

HGC latitude ChanT [HGC_Lat_ChanT]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanT timebase.

HGC longitude ChanT [HGC_Lon_ChanT]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanT timebase.

Pitch angle ChanC [PA_ChanC]

Pitch angle ChanD [PA_ChanD]

Pitch angle ChanP [PA_ChanP]

Pitch angle ChanR [PA_ChanR]

Pitch angle ChanT [PA_ChanT]

RTN flow direction ChanC - no plot [RTN_ChanC]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanC timebase.

---> Look direction 00 - stack plot [RTN_ChanC_L00]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanC timebase.

---> Look direction 11 [RTN_ChanC_L11]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanC timebase.

---> Look direction 22 [RTN_ChanC_L22]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanC timebase.

---> Look direction 33 [RTN_ChanC_L33]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanC timebase.

---> Look direction 44 [RTN_ChanC_L44]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanC timebase.

---> Look direction 55 [RTN_ChanC_L55]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanC timebase.

---> Look direction 66 [RTN_ChanC_L66]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanC timebase.

---> Look direction 77 [RTN_ChanC_L77]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanC timebase.

RTN flow direction ChanD - no plot [RTN_ChanD]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanD timebase.

---> Look direction 00 - stack plot [RTN_ChanD_L00]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanD timebase.

---> Look direction 11 [RTN_ChanD_L11]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanD timebase.

---> Look direction 22 [RTN_ChanD_L22]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanD timebase.

---> Look direction 33 [RTN_ChanD_L33]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanD timebase.

---> Look direction 44 [RTN_ChanD_L44]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanD timebase.

---> Look direction 55 [RTN_ChanD_L55]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanD timebase.

---> Look direction 66 [RTN_ChanD_L66]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanD timebase.

---> Look direction 77 [RTN_ChanD_L77]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanD timebase.

RTN flow direction ChanP - no plot [RTN_ChanP]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanP timebase.

---> Look direction 00 - stack plot [RTN_ChanP_L00]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanP timebase.

---> Look direction 11 [RTN_ChanP_L11]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanP timebase.

---> Look direction 22 [RTN_ChanP_L22]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanP timebase.

---> Look direction 33 [RTN_ChanP_L33]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanP timebase.

---> Look direction 44 [RTN_ChanP_L44]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanP timebase.

---> Look direction 55 [RTN_ChanP_L55]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanP timebase.

---> Look direction 66 [RTN_ChanP_L66]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanP timebase.

---> Look direction 77 [RTN_ChanP_L77]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanP timebase.

RTN flow direction ChanR - no plot [RTN_ChanR]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanR timebase.

---> Look direction 00 - stack plot [RTN_ChanR_L00]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanR timebase.

---> Look direction 11 [RTN_ChanR_L11]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanR timebase.

---> Look direction 22 [RTN_ChanR_L22]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanR timebase.

---> Look direction 33 [RTN_ChanR_L33]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanR timebase.

---> Look direction 44 [RTN_ChanR_L44]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanR timebase.

---> Look direction 55 [RTN_ChanR_L55]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanR timebase.

---> Look direction 66 [RTN_ChanR_L66]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanR timebase.

---> Look direction 77 [RTN_ChanR_L77]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanR timebase.

RTN flow direction ChanT - no plot [RTN_ChanT]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanT timebase.

---> Look direction 00 - stack plot [RTN_ChanT_L00]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanT timebase.

---> Look direction 11 [RTN_ChanT_L11]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanT timebase.

---> Look direction 22 [RTN_ChanT_L22]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanT timebase.

---> Look direction 33 [RTN_ChanT_L33]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanT timebase.

---> Look direction 44 [RTN_ChanT_L44]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanT timebase.

---> Look direction 55 [RTN_ChanT_L55]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanT timebase.

---> Look direction 66 [RTN_ChanT_L66]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanT timebase.

---> Look direction 77 [RTN_ChanT_L77]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanT timebase.

Nominal Parker Spiral angle ChanC [SA_ChanC]

Angle between particle direction and nominal outward Parker Spiral, based on
400km/s solar wind and corotation breakdown at 10Rs.

Nominal Parker Spiral angle ChanD [SA_ChanD]

Angle between particle direction and nominal outward Parker Spiral, based on
400km/s solar wind and corotation breakdown at 10Rs.

Nominal Parker Spiral angle ChanP [SA_ChanP]

Angle between particle direction and nominal outward Parker Spiral, based on
400km/s solar wind and corotation breakdown at 10Rs.

Nominal Parker Spiral angle ChanR [SA_ChanR]

Angle between particle direction and nominal outward Parker Spiral, based on
400km/s solar wind and corotation breakdown at 10Rs.

Nominal Parker Spiral angle ChanT [SA_ChanT]

Angle between particle direction and nominal outward Parker Spiral, based on
400km/s solar wind and corotation breakdown at 10Rs.

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_ISOIS-EPILO_L2-PE doi:10.48322/rz8e-5y91

Description

EPI-Lo, Particle Energy mode.
Instrument paper: Integrated Science Investigation of the Sun (ISIS): Design of
the Energetic Particle Investigation. McComas, D. J. et al (2016). Space Sci.
Rev., doi:10.1007/s11214-014-0059-1

Modification History

Release 17 (data 5.0.0, code 5.0.0): Add Quality_Flag variable for each epoch
indicating any potential concerns with the data. See the ISOIS Data Glossary for
details.
Release 20 (data 6.0.0, code 6.0.0): Add testing periods quality flag.

Data Variable Descriptions

HCI flow direction ChanE [HCI_ChanE]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanE timebase.

HCI flow direction ChanF [HCI_ChanF]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanF timebase.

HCI flow direction ChanG [HCI_ChanG]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanG timebase.

HGC latitude ChanF [HGC_Lat_ChanF]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanF timebase.

HCI longitude ChanF [HCI_Lon_ChanF]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanF timebase.

HCI longitude ChanG [HCI_Lon_ChanG]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanG timebase.

HCI longitude ChanE [HCI_Lon_ChanE]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanE timebase.

Electron counts channel E (HiResElectrons) [Electron_Counts_ChanE]

Particle Energy mode. Raw counts per integration.

Electron counts channel G (HiLookResElectrons) [Electron_Counts_ChanG]

Particle Energy mode. Raw counts per integration.

Electron counts channel F (HiTimeResElectrons) [Electron_Counts_ChanF]

Particle Energy mode. Raw counts per integration.

HGC Heliocentric distance ChanG [HGC_R_ChanG]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanG timebase.

HGC Heliocentric distance ChanF [HGC_R_ChanF]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanF timebase.

HGC Heliocentric distance ChanE [HGC_R_ChanE]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanE timebase.

HGC longitude ChanE [HGC_Lon_ChanE]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanE timebase.

HGC longitude ChanF [HGC_Lon_ChanF]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanF timebase.

HGC longitude ChanG [HGC_Lon_ChanG]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanG timebase.

HGC latitude ChanE [HGC_Lat_ChanE]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanE timebase.

H count rate channel F (HiTimeResElectrons) [H_CountRate_ChanF]

Particle Energy mode. Corrected for deadtime.

H count rate channel G (HiLookResElectrons) [H_CountRate_ChanG]

Particle Energy mode. Corrected for deadtime.

H count rate channel E (HiResElectrons) [H_CountRate_ChanE]

Particle Energy mode. Corrected for deadtime.

H counts channel E (HiResElectrons) [H_Counts_ChanE]

Particle Energy mode. Raw counts per integration.

H counts channel F (HiTimeResElectrons) [H_Counts_ChanF]

Particle Energy mode. Raw counts per integration.

H counts channel G (HiLookResElectrons) [H_Counts_ChanG]

Particle Energy mode. Raw counts per integration.

HGC latitude ChanG [HGC_Lat_ChanG]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanG timebase.

Electron count rate channel E (HiResElectrons) [Electron_CountRate_ChanE]

Particle Energy mode. Corrected for deadtime.

Electron count rate channel G (HiLookResElectrons) [Electron_CountRate_ChanG]

Particle Energy mode. Corrected for deadtime.

Electron count rate channel F (HiTimeResElectrons) [Electron_CountRate_ChanF]

Particle Energy mode. Corrected for deadtime.

HCI Heliocentric distance ChanE [HCI_R_ChanE]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanE timebase.

HCI Heliocentric distance ChanG [HCI_R_ChanG]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanG timebase.

HCI Heliocentric distance ChanF [HCI_R_ChanF]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanF timebase.

HCI latitude ChanF [HCI_Lat_ChanF]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanF timebase.

HCI latitude ChanG [HCI_Lat_ChanG]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanG timebase.

HCI latitude ChanE [HCI_Lat_ChanE]

At timestamp. After Fraenz and Harper, PSS, 2002. ChanE timebase.

Nominal Parker Spiral angle ChanE [SA_ChanE]

Angle between particle direction and nominal outward Parker Spiral, based on
400km/s solar wind and corotation breakdown at 10Rs.

Nominal Parker Spiral angle ChanG [SA_ChanG]

Angle between particle direction and nominal outward Parker Spiral, based on
400km/s solar wind and corotation breakdown at 10Rs.

Nominal Parker Spiral angle ChanF [SA_ChanF]

Angle between particle direction and nominal outward Parker Spiral, based on
400km/s solar wind and corotation breakdown at 10Rs.

Pitch angle ChanE [PA_ChanE]

Pitch angle ChanF [PA_ChanF]

Pitch angle ChanG [PA_ChanG]

RTN flow direction ChanE [RTN_ChanE]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanE timebase.

RTN flow direction ChanF [RTN_ChanF]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanF timebase.

RTN flow direction ChanG [RTN_ChanG]

Unit vector, after Fraenz and Harper, PSS, 2002. ChanG timebase.

Data-quality flag for channel E (HiResElectrons) [Quality_Flag_ChanE]

Data-quality flag for channel F (HiTimeResElectrons) [Quality_Flag_ChanF]

Data-quality flag for channel G (HiLookResElectrons) [Quality_Flag_ChanG]

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_ISOIS_L2-EPHEM doi:10.48322/y0fb-3v04

Description

Instrument paper: Integrated Science Investigation of the Sun (ISIS): Design of
the Energetic Particle Investigation. McComas, D. J. et al (2016). Space Sci.
Rev., doi:10.1007/s11214-014-0059-1

Data Variable Descriptions

HGC latitude [HGC_Lat]

At timestamp. After Fraenz and Harper, PSS, 2002.

Lo look angle with nominal parker spiral [Spiral_Lo]

Angle between +Z Lo frame (look directions x9) and nominal parker spiral
assuming constant 400 km/s solar wind speed and a corotation boundry of 20 solar
radii

Spacecraft is ram pointing [Ram_Pointing]

1 if roll angle is small, and either sun angle or clock angle are small
(pointing into ram).

HCI longitude [HCI_Lon]

At timestamp. After Fraenz and Harper, PSS, 2002.

HETA look angle with nominal parker spiral [Spiral_HETA]

Angle between +Z HETA frame and nominal parker spiral assuming constant 400 km/s
solar wind speed and a corotation boundary of 20 solar radii

HGC longitude [HGC_Lon]

At timestamp. After Fraenz and Harper, PSS, 2002.

Heliocentric distance [HCI_R]

At timestamp. After Fraenz and Harper, PSS, 2002.

angle of off-pointing from ecliptic north when not in encounter [Clock_Angle]

Angle (around +R axis) between SC +Z projected into the TN plane and +N axis.
Nominally zero (roughly ecliptic north). Ascends CCW (right-handed) despite the
name, so positive values are toward -T (opposite ram) and negative towards +T
(into ram). Undefined (fill) if Sun Angle is small.

Angle between nominal ram and actual ram, 0 in encounter [Roll_Angle]

Angle between s/c +X and RTN +T. Positive if s/c +X is towards +N (roughly
ecliptic north); right-handed in RTN.

Heliocentric distance [HGC_R]

At timestamp. After Fraenz and Harper, PSS, 2002.

Spacecraft is umbra pointing [Umbra_Pointing]

1 (nominal for encounter) if Sun angle = 0 else 0

LET1A look angle with nominal parker spiral [Spiral_LET1A]

Angle between +Z LET1A frame and nominal parker spiral assuming constant 400
km/s solar wind speed and a corotation boundary of 20 solar radii

LET2C look angle with nominal parker spiral [Spiral_LET2C]

Angle between +Z LET2C frame and nominal parker spiral assuming constant 400
km/s solar wind speed and a corotation boundary of 20 solar radii

HCI latitude [HCI_Lat]

At timestamp. After Fraenz and Harper, PSS, 2002.

Angle between TPS and Sun, 0 in encounter [Sun_Angle]

Angle between s/c +Z and RTN -R. Always positive.

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_ISOIS_L2-SUMMARY doi:10.48322/mede-7j02

Description

EPI-Hi HET 3600 second rates cdf. Time tags indicate midpoint of integration.
Instrument paper: Integrated Science Investigation of the Sun (ISIS): Design of
the Energetic Particle Investigation. McComas, D. J. et al (2016). Space Sci.
Rev., doi:10.1007/s11214-014-0059-1
EPI-Hi 3600 seconds rates cdf. Time tags indicate midpoint of integration.
EPI-Lo, Ion Composition mode.
EPI-Lo, Particle Energy mode.

Modification History

Release 12 (data 3.0.0, code 3.0.0): Remove H_CountRate_ChanT and related
variables, as these time-of-flight only rates contain substantial background.
Replaced with H_CountRate_ChanP, containing protons with a triple-coincidence
(TOFxE) requirement. Contains all look directions but a similar energy range to
the previous ChanT variable.

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_SWP_SPA_SF0_L2_16AX8DX32E doi:10.48322/7j5c-zg65

Description

http://sprg.ssl.berkeley.edu/data/psp/pub/sci/sweap/description/

Modification History

Revision 0

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_SWP_SPA_SF0_L3_PAD doi:10.48322/envk-8520

Description

http://sprg.ssl.berkeley.edu/data/psp/pub/sci/sweap/description/

Modification History

Revision 0

Data Variable Descriptions

Quality Flag [QUALITY_FLAG]

The quality flag is a two-byte unsigned integer (UINT2) with its least
significant bit (Bit 1) indicating: Counter Overflow, Bit 2: Snapshot ON, Bit 3:
Alternate Energy Table, Bit 4: Spoiler Test, Bit 5: Attenuator Engaged, Bit 6:
Highest Archive Rate, Bit 7: No Targeted Sweep, Bit 8: SPAN-Ion New Mass Table
(not applicable to electrons), Bit 9: Over-deflection, Bit 10: Archive Snapshot
ON Bits 11-16: Reserved.

Differential Energy Flux vs Energy at Each Pitch Angle (spectrograms) [EFLUX_VS_PA_E_byE_atP]

Differential Energy Flux vs Pitch Angle at Each Energy Level (spectrograms) [EFLUX_VS_PA_E_atE_byP]

Differential Energy Flux vs Energy [EFLUX_VS_ENERGY]

Differential Energy Flux vs Phi [EFLUX_VS_PHI]

Magnetic Field in Spacecraft Coordinates [MAGF_SC]

In spacecraft frame

Magnetic Field in Instrument Coordinates [MAGF_INST]

In instrument frame

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_SWP_SPA_SF1_L2_32E doi:10.48322/9pz0-sj43

Description

http://sprg.ssl.berkeley.edu/data/psp/pub/sci/sweap/description/

Modification History

Revision 0

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_SWP_SPB_SF0_L2_16AX8DX32E doi:10.48322/f1vx-0f86

Description

http://sprg.ssl.berkeley.edu/data/psp/pub/sci/sweap/description/

Modification History

Revision 0

Data Variable Descriptions

Quality Flag [QUALITY_FLAG]

The quality flag is a two-byte unsigned integer (CDF_UINT2) with its least
significant bit (Bit 0) indicating: Counter Overflow, Bit 1: Survey Snapshot ON
(not applicable to archive products), Bit 2: Alternate Energy Table, Bit 3:
Spoiler Test, Bit 4: Attenuator Engaged, Bit 5: Highest Archive Rate, Bit 6: No
Targeted Sweep, Bit 7: SPAN-Ion New Mass Table (not applicable to electrons),
Bit 8: Over-deflection, Bit 9: Archive Snapshot ON, Bits 10-15: Reserved.

Differential Energy Flux vs Energy/angle bin [EFLUX]

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_SWP_SPB_SF0_L3_PAD doi:10.48322/ccen-5a96

Description

http://sprg.ssl.berkeley.edu/data/psp/pub/sci/sweap/description/

Modification History

Revision 0

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_SWP_SPB_SF1_L2_32E doi:10.48322/db2p-rk78

Description

http://sprg.ssl.berkeley.edu/data/psp/pub/sci/sweap/description/

Modification History

Revision 0

Data Variable Descriptions

Quality Flag [QUALITY_FLAG]

The quality flag is a two-byte unsigned integer (CDF_UINT2) with its least
significant bit (Bit 0) indicating: Counter Overflow, Bit 1: Survey Snapshot ON
(not applicable to archive products), Bit 2: Alternate Energy Table, Bit 3:
Spoiler Test, Bit 4: Attenuator Engaged, Bit 5: Highest Archive Rate, Bit 6: No
Targeted Sweep, Bit 7: SPAN-Ion New Mass Table (not applicable to electrons),
Bit 8: Over-deflection, Bit 9: Archive Snapshot ON, Bits 10-15: Reserved.

Differential Energy Flux vs Energy/angle bin [EFLUX]

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_SWP_SPC_L2I doi:10.48322/wpk2-yq48

Description

Solar Probe Cup (SPC) charge flux distributions comprise electrical current as a
function of time and energy-per-charge, with appropriate instrument response
elements considered and calibrations applied. This is a two SWEAP SPC experiment
level 2 (L2) standard data product.

Modification History

01/12/2018- CDF skeleton created (MLS)
2019-10-01: corrections to axis label fields, expanded var_notes, various
revised metatdata
2019-11-04: contracted calibration file variables to global attribute
2020-09-11: data version increment to signify correspondence with L3i version 2
release. No actual L2 processing changes

Data Variable Descriptions

Current measured by sensor A, in picoAmperes [a_current]

This current represents the differential charge flux upon the sensor, as a
function of the time and modulator voltage pair.

Current measured by sensor B, in picoAmperes [b_current]

This current represents the differential charge flux upon the sensor, as a
function of the time and modulator voltage pair.

Current measured by sensor C, in picoAmperes [c_current]

This current represents the differential charge flux upon the sensor, as a
function of the time and modulator voltage pair.

Current measured by sensor D, in picoAmperes [d_current]

This current represents the differential charge flux upon the sensor, as a
function of the time and modulator voltage pair.

rough estimate angle of the mean flow into the cup, in radians, in SPC coordinates [flow_angle]

This flow component is across the sensor with respect to the sensor coordinate
system.  This flow angle is estimated using the linear cold-plasma approximation
and considering a three-point neighborhood in time at the peak flux measurement.
It does not account for spreading of the beam in the instrument, which may be
significant.  This angle is used to estimate the diff_charge_flux_density
variable (refer to documentation)

differential charge flux density, in pA*cm**-2 [diff_charge_flux_density]

This is the charge flux density of the solar wind measured over the energy range
defined by the modulator voltage pair. The [calibrated] effective area of the
cup has been taken into account.  This quantity is the equivalent of the total
charge crossing a ZSC-oriented unit area per unit time) due to charge carriers
having energy-per-charge between mv_lo and mv_hi.  This quantity is estimated
using a linear, cold-plasma approximation for the mean flow angle of the solar
wind into the sensor. See remarks.

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_SWP_SPC_L3I doi:10.48322/49we-tr31

Description

This file includes the densities, vector velocities, and scalar (radial
component) temperatures of the solar wind protons measured by the Solar Probe
Cup (SPC). These are determined both by a direct computation of the velocity
moments of the reduced distribution function and by attempting to fit the
primary peak in the ion I(V) curve with a Maxwellian model.
When such fitting is successful, the data set also includes Maxwellian model
fits to the alpha-particle (He++) and tertiary (usually proton beam or shoulder)
populations.

Modification History

2018-12-04: CDF skeleton created (MLS)
2019-01-20: expanded data quality flags, variable notes
2019-01-28: modified to include RTN reference frame
2019-07-23: minor modifications for spdf compliance
2019-08-20: minor modifications for spdf compliance
2019-10-01: corrections to axis label fields, expanded var_notes
2019-11-04: contracted calibration file variables to global attribute
2019-10-31: inclusion of standalone general_flag variable
2020-09-11: corrections to heliographic inertial coordinate system variables

Data Variable Descriptions

Array of SPC data quality indicators. [DQF]

The indication of the 32 elements of the data quality array is given by the
metadata variable 'DQF_flagnames'. All flags are encoded as follows: ---------
---------------    = 0,   good/nominal/condition not present/etc     > 1, 
bad/problematic/condition present/etc     = -1,  status not determined ("don't
know")    < -1,  status does not matter ("don't care")  -1 ("don't know") is the
default value for all flags.  The 0th flag array element is the [standardized]
global quality flag, signifying whether the data are suitable for use without
caveate. It is repeated in the "general_flag" variable.

Global quality flag, signifying whether the data for this epoch are suitable for use without caveate. [general_flag]

All flags are encoded as follows: --------------------------    = 0,  
good/nominal/condition not present/etc     > 1,  bad/problematic/condition
present/etc     = -1,  status not determined ("don't know")    < -1,  status
does not matter ("don't care")  -1 ("don't know") is the default value for all
flags.  The user is advised to consider the quoted measurement uncertainties,
particularly when the general quality flag is zero.

Proton bulk velocity from the 1st moment of the reduced distribution function, in the spacecraft frame (Only Good Quality) [vp_moment_SC_gd]

This moment is a model-independant estimate of the proton bulk speed, but it is
subject to confusion with alpha particles when present. Error bars represent
estimated upper and lower limits.

---> upper uncertainty [vp_moment_SC_deltahigh_gd]

This moment is a model-independant estimate of the proton most-probable thermal
speed, but it is subject to confusion with alpha particles when present. Error
bars represent estimated upper and lower limits.

---> lower uncertainty [vp_moment_SC_deltalow_gd]

This moment is a model-independant estimate of the proton most-probable thermal
speed, but it is subject to confusion with alpha particles when present. Error
bars represent estimated upper and lower limits.

Proton bulk velocity from the 1st moment of the reduced distribution function in [inertial] RTN coordinate system (Only Good Quality) [vp_moment_RTN_gd]

This moment is a model-independant estimate of the proton bulk speed, but it is
subject to confusion with alpha particles when present. Error bars represent
estimated upper and lower limits.

---> upper uncertainty [vp_moment_RTN_deltahigh_gd]

This moment is a model-independant estimate of the proton most-probable thermal
speed, but it is subject to confusion with alpha particles when present. Error
bars represent estimated upper and lower limits.

---> lower uncertainty [vp_moment_RTN_deltalow_gd]

This moment is a model-independant estimate of the proton most-probable thermal
speed, but it is subject to confusion with alpha particles when present. Error
bars represent estimated upper and lower limits.

Proton density estimate from the 0th moment of the reduced distribution function (Only Good Quality) [np_moment_gd]

This moment is a model-independant estimate of the proton density, but it is
subject to confusion with alpha particles when present. Error bars represent
estimated upper and lower limits.

---> upper uncertainty [np_moment_deltahigh_gd]

This moment is a model-independant estimate of the proton density, but it is
subject to confusion with alpha particles when present. Error bars represent
estimated upper and lower limits.

---> lower uncertainty [np_moment_deltalow_gd]

This moment is a model-independant estimate of the proton density, but it is
subject to confusion with alpha particles when present. Error bars represent
estimated upper and lower limits.

Proton radial [most probable] thermal speed estimate from the 2nd velocity moment of the reduced distribution function (Only Good Quality) [wp_moment_gd]

This moment is a model-independant estimate of the proton most-probable thermal
speed, but it is subject to confusion with alpha particles when present. Error
bars represent estimated upper and lower limits.

---> upper uncertainty [wp_moment_deltahigh_gd]

This moment is a model-independant estimate of the proton most-probable thermal
speed, but it is subject to confusion with alpha particles when present. Error
bars represent estimated upper and lower limits.

---> lower uncertainty [wp_moment_deltalow_gd]

This moment is a model-independant estimate of the proton most-probable thermal
speed, but it is subject to confusion with alpha particles when present. Error
bars represent estimated upper and lower limits.

Primary proton population velocity, from 1-dimensional Maxwellian fitting, in the spacecraft frame (Only Good Quality) [vp1_fit_SC_gd]

The strongest signal peak, which generally corresponds to the bulk proton
population in the solar wind, is fit to a convected Maxwellian model.

---> 1-sigma error [vp1_fit_SC_uncertainty_gd]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  The flow angles relative to the SPC are
obtained by comparing fluxes upon the four sensor quadrants. This uncertainty
incorporates uncertainties in the absolute responses of the respective sensors.

Primary proton population velocity, from 1-dimensional Maxwellian fitting, in the [inertial] RTN frame (Only Good Quality) [vp1_fit_RTN_gd]

The strongest signal peak, which generally corresponds to the bulk proton
population in the solar wind, is fit to a convected Maxwellian model.

---> 1-sigma error [vp1_fit_RTN_uncertainty_gd]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  The flow angles relative to the SPC are
obtained by comparing fluxes upon the four sensor quadrants. This uncertainty
incorporates uncertainties in the absolute responses of the respective sensors.

Primary proton population density, from 1-dimensional Maxwellian fitting. (Only Good Quality) [np1_fit_gd]

The strongest signal peak, which generally corresponds to the bulk proton
population in the solar wind, is fit to a convected Maxwellian model.

---> 1-sigma error [np1_fit_uncertainty_gd]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  This variable reflects *precision*
uncertainty from fitting, summed in quadrature with the *accuracy* uncertainy
associated with the absolute responses of the SPC sensors.

Primary proton population radial [most probable] thermal speed, from 1-dimensional Maxwellian fitting. (Only Good Quality) [wp1_fit_gd]

The strongest signal peak, which generally corresponds to the bulk proton
population in the solar wind, is fit to a convected Maxwellian model.  This
measurement most accurately represents the thermal width of the reduced
phase-space-distribution function along the SPC-normal direction. This roughly
corresponds to the radial component of the temperature tensor.  This is a most
probable thermal speed, i.e. the model distribution goes like exp(-v^2/w^2).

---> 1-sigma error [wp1_fit_uncertainty_gd]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  This variable reflects *precision*
uncertainty from fitting, summed in quadrature with the *accuracy* uncertainy
associated with the absolute responses of the SPC sensors.

Proton bulk velocity, from 1-dimensional Maxwellian fitting, in the spacecraft frame (Only Good Quality) [vp_fit_SC_gd]

the bulk proton population in the solar wind is fit to a group of convected
Maxwellian models.

---> 1-sigma error [vp_fit_SC_uncertainty_gd]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  The flow angles relative to the SPC are
obtained by comparing fluxes upon the four sensor quadrants. This uncertainty
incorporates uncertainties in the absolute responses of the respective sensors.

Proton bulk velocity, from 1-dimensional Maxwellian fitting, in the [inertial] RTN frame (Only Good Quality) [vp_fit_RTN_gd]

the bulk proton population in the solar wind is fit to a group of convected
Maxwellian models.

---> 1-sigma error [vp_fit_RTN_uncertainty_gd]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  The flow angles relative to the SPC are
obtained by comparing fluxes upon the four sensor quadrants. This uncertainty
incorporates uncertainties in the absolute responses of the respective sensors.

[Total] proton density, from 1-dimensional Maxwellian fitting. (Only Good Quality) [np_fit_gd]

the bulk proton population in the solar wind is fit to a group of convected
Maxwellian models.

---> 1-sigma error [np_fit_uncertainty_gd]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  This variable reflects *precision*
uncertainty from fitting, summed in quadrature with the *accuracy* uncertainy
associated with the absolute responses of the SPC sensors.

Proton radial [most probable] thermal speed component, from 1-dimensional Maxwellian fitting. (Only Good Quality) [wp_fit_gd]

the bulk proton population in the solar wind is fit to a group of convected
Maxwellian models.

---> 1-sigma error [wp_fit_uncertainty_gd]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  This variable reflects *precision*
uncertainty from fitting, summed in quadrature with the *accuracy* uncertainy
associated with the absolute responses of the SPC sensors.

Alpha particle velocity vector, from 1-dimensional Maxwellian fitting, in the spacecraft frame (Only Good Quality) [va_fit_SC_gd]

The alpha particle (He++) peak in the solar wind, when clearly distinguishable,
is fit to a convected Maxwellian model.

---> 1-sigma error [va_fit_SC_uncertainty_gd]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  The flow angles relative to the SPC are
obtained by comparing fluxes upon the four sensor quadrants. This uncertainty
incorporates uncertainties in the absolute responses of the respective sensors.

Alpha particle velocity vector, from 1-dimensional Maxwellian fitting, in the [inertial] RTN frame (Only Good Quality) [va_fit_RTN_gd]

The alpha particle (He++) peak in the solar wind, when clearly distinguishable,
is fit to a convected Maxwellian model.

---> 1-sigma error [va_fit_RTN_uncertainty_gd]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  The flow angles relative to the SPC are
obtained by comparing fluxes upon the four sensor quadrants. This uncertainty
incorporates uncertainties in the absolute responses of the respective sensors.

Alpha particle density, from 1-dimensional Maxwellian fitting. (Only Good Quality) [na_fit_gd]

The alpha particle (He++) peak in the solar wind, when clearly distinguishable,
is fit to a convected Maxwellian model.

---> 1-sigma error [na_fit_uncertainty_gd]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  This variable reflects *precision*
uncertainty from fitting, summed in quadrature with the *accuracy* uncertainy
associated with the absolute responses of the SPC sensors.

Alpha particle radial [most probable] thermal speed, from 1-dimensional Maxwellian fitting. (Only Good Quality) [wa_fit_gd]

The alpha particle (He++) peak in the solar wind, when clearly distinguishable,
is fit to a convected Maxwellian model.  This measurement most accurately
represents the thermal width of the reduced phase-space-distribution function
along the SPC-normal direction. This roughly corresponds to the radial component
of the temperature tensor.  This is a most probable thermal speed, i.e. the
model distribution goes like exp(-v^2/w^2).

---> 1-sigma error [wa_fit_uncertainty_gd]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  This variable reflects *precision*
uncertainty from fitting, summed in quadrature with the *accuracy* uncertainy
associated with the absolute responses of the SPC sensors.

Population 3 velocity vector, from 1-dimensional Maxwellian fitting, in the spacecraft frame (Only Good Quality) [v3_fit_SC_gd]

The population 3 peak in the solar wind, when clearly distinguishable, is fit to
a convected Maxwellian model.   Population 3 most typically characterizes a
proton shoulder or beam (mtoq=1)

---> 1-sigma error [v3_fit_SC_uncertainty_gd]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  The flow angles relative to the SPC are
obtained by comparing fluxes upon the four sensor quadrants. This uncertainty
incorporates uncertainties in the absolute responses of the respective sensors.

Population 3 velocity vector, from 1-dimensional Maxwellian fitting, in the [inertial] RTN frame (Only Good Quality) [v3_fit_RTN_gd]

The population 3 peak in the solar wind, when clearly distinguishable, is fit to
a convected Maxwellian model.   Population 3 most typically characterizes a
proton shoulder or beam (mtoq=1)

---> 1-sigma error [v3_fit_RTN_uncertainty_gd]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  The flow angles relative to the SPC are
obtained by comparing fluxes upon the four sensor quadrants. This uncertainty
incorporates uncertainties in the absolute responses of the respective sensors.

Population 3 particle density, from 1-dimensional Maxwellian fitting. (Only Good Quality) [n3_fit_gd]

The population 3 particle peak in the solar wind, when clearly distinguishable,
is fit to a convected Maxwellian model.  Population 3 most typically
characterizes a proton shoulder or beam (mtoq=1)

---> 1-sigma error [n3_fit_uncertainty_gd]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  This variable reflects *precision*
uncertainty from fitting, summed in quadrature with the *accuracy* uncertainy
associated with the absolute responses of the SPC sensors.

Population 3 particle radial [most probable] thermal speed, from 1-dimensional Maxwellian fitting. (Only Good Quality) [w3_fit_gd]

The population 3 peak in the solar wind, when clearly distinguishable, is fit to
a convected Maxwellian model.  Population 3 most typically characterizes a
proton shoulder or beam (mtoq=1)  This measurement most accurately represents
the thermal width of the reduced phase-space-distribution function along the
SPC-normal direction. This roughly corresponds to the radial component of the
temperature tensor.  This is a most probable thermal speed, i.e. the model
distribution goes like exp(-v^2/w^2).

---> 1-sigma error [w3_fit_uncertainty_gd]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  This variable reflects *precision*
uncertainty from fitting, summed in quadrature with the *accuracy* uncertainy
associated with the absolute responses of the SPC sensors.

PSP Spacecraft position in the Heliocentric Inertial system, in km [sc_pos_HCI]

Also called Ecliptic J2000. Z is the solar north rotational axis, and X is the
solar ascending node on the J2000 ecliptic.

PSP Spacecraft velocity in the Heliocentric Inertial system, in km/s [sc_vel_HCI]

Also called Ecliptic J2000. Z is the solar north rotational axis, and X is the
solar ascending node on the J2000 ecliptic.

Carrington Latitude [carr_latitude]

spacecraft position degrees Latitude from solar equator

Carrington Longitude [carr_longitude]

spacecraft position degrees longitude from solar prime meridian

Proton bulk velocity from the 1st moment of the reduced distribution function, in the spacecraft frame (All Qualities) [vp_moment_SC]

This moment is a model-independant estimate of the proton bulk speed, but it is
subject to confusion with alpha particles when present. Error bars represent
estimated upper and lower limits.

---> upper uncertainty [vp_moment_SC_deltahigh]

This moment is a model-independant estimate of the proton most-probable thermal
speed, but it is subject to confusion with alpha particles when present. Error
bars represent estimated upper and lower limits.

---> lower uncertainty [vp_moment_SC_deltalow]

This moment is a model-independant estimate of the proton most-probable thermal
speed, but it is subject to confusion with alpha particles when present. Error
bars represent estimated upper and lower limits.

Proton bulk velocity from the 1st moment of the reduced distribution function in [inertial] RTN coordinate system (All Qualities) [vp_moment_RTN]

This moment is a model-independant estimate of the proton bulk speed, but it is
subject to confusion with alpha particles when present. Error bars represent
estimated upper and lower limits.

---> upper uncertainty [vp_moment_RTN_deltahigh]

This moment is a model-independant estimate of the proton most-probable thermal
speed, but it is subject to confusion with alpha particles when present. Error
bars represent estimated upper and lower limits.

---> lower uncertainty [vp_moment_RTN_deltalow]

This moment is a model-independant estimate of the proton most-probable thermal
speed, but it is subject to confusion with alpha particles when present. Error
bars represent estimated upper and lower limits.

Proton density estimate from the 0th moment of the reduced distribution function (All Qualities) [np_moment]

This moment is a model-independant estimate of the proton density, but it is
subject to confusion with alpha particles when present. Error bars represent
estimated upper and lower limits.

---> upper uncertainty [np_moment_deltahigh]

This moment is a model-independant estimate of the proton density, but it is
subject to confusion with alpha particles when present. Error bars represent
estimated upper and lower limits.

---> lower uncertainty [np_moment_deltalow]

This moment is a model-independant estimate of the proton density, but it is
subject to confusion with alpha particles when present. Error bars represent
estimated upper and lower limits.

Proton radial [most probable] thermal speed estimate from the 2nd velocity moment of the reduced distribution function (All Qualities) [wp_moment]

This moment is a model-independant estimate of the proton most-probable thermal
speed, but it is subject to confusion with alpha particles when present. Error
bars represent estimated upper and lower limits.

---> upper uncertainty [wp_moment_deltahigh]

This moment is a model-independant estimate of the proton most-probable thermal
speed, but it is subject to confusion with alpha particles when present. Error
bars represent estimated upper and lower limits.

---> lower uncertainty [wp_moment_deltalow]

This moment is a model-independant estimate of the proton most-probable thermal
speed, but it is subject to confusion with alpha particles when present. Error
bars represent estimated upper and lower limits.

Primary proton population velocity, from 1-dimensional Maxwellian fitting, in the spacecraft frame (All Qualities) [vp1_fit_SC]

The strongest signal peak, which generally corresponds to the bulk proton
population in the solar wind, is fit to a convected Maxwellian model.

---> 1-sigma error [vp1_fit_SC_uncertainty]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  The flow angles relative to the SPC are
obtained by comparing fluxes upon the four sensor quadrants. This uncertainty
incorporates uncertainties in the absolute responses of the respective sensors.

Primary proton population velocity, from 1-dimensional Maxwellian fitting, in the [inertial] RTN frame (All Qualities) [vp1_fit_RTN]

The strongest signal peak, which generally corresponds to the bulk proton
population in the solar wind, is fit to a convected Maxwellian model.

---> 1-sigma error [vp1_fit_RTN_uncertainty]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  The flow angles relative to the SPC are
obtained by comparing fluxes upon the four sensor quadrants. This uncertainty
incorporates uncertainties in the absolute responses of the respective sensors.

Primary proton population density, from 1-dimensional Maxwellian fitting. (All Qualities) [np1_fit]

The strongest signal peak, which generally corresponds to the bulk proton
population in the solar wind, is fit to a convected Maxwellian model.

---> 1-sigma error [np1_fit_uncertainty]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  This variable reflects *precision*
uncertainty from fitting, summed in quadrature with the *accuracy* uncertainy
associated with the absolute responses of the SPC sensors.

Primary proton population radial [most probable] thermal speed, from 1-dimensional Maxwellian fitting. (All Qualities) [wp1_fit]

The strongest signal peak, which generally corresponds to the bulk proton
population in the solar wind, is fit to a convected Maxwellian model.  This
measurement most accurately represents the thermal width of the reduced
phase-space-distribution function along the SPC-normal direction. This roughly
corresponds to the radial component of the temperature tensor.  This is a most
probable thermal speed, i.e. the model distribution goes like exp(-v^2/w^2).

---> 1-sigma error [wp1_fit_uncertainty]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  This variable reflects *precision*
uncertainty from fitting, summed in quadrature with the *accuracy* uncertainy
associated with the absolute responses of the SPC sensors.

Proton bulk velocity, from 1-dimensional Maxwellian fitting, in the spacecraft frame (All Qualities) [vp_fit_SC]

the bulk proton population in the solar wind is fit to a group of convected
Maxwellian models.

---> 1-sigma error [vp_fit_SC_uncertainty]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  The flow angles relative to the SPC are
obtained by comparing fluxes upon the four sensor quadrants. This uncertainty
incorporates uncertainties in the absolute responses of the respective sensors.

Proton bulk velocity, from 1-dimensional Maxwellian fitting, in the [inertial] RTN frame (All Qualities) [vp_fit_RTN]

the bulk proton population in the solar wind is fit to a group of convected
Maxwellian models.

---> 1-sigma error [vp_fit_RTN_uncertainty]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  The flow angles relative to the SPC are
obtained by comparing fluxes upon the four sensor quadrants. This uncertainty
incorporates uncertainties in the absolute responses of the respective sensors.

[Total] proton density, from 1-dimensional Maxwellian fitting. (All Qualities) [np_fit]

the bulk proton population in the solar wind is fit to a group of convected
Maxwellian models.

---> 1-sigma error [np_fit_uncertainty]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  This variable reflects *precision*
uncertainty from fitting, summed in quadrature with the *accuracy* uncertainy
associated with the absolute responses of the SPC sensors.

Proton radial [most probable] thermal speed component, from 1-dimensional Maxwellian fitting. (All Qualities) [wp_fit]

the bulk proton population in the solar wind is fit to a group of convected
Maxwellian models.

---> 1-sigma error [wp_fit_uncertainty]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  This variable reflects *precision*
uncertainty from fitting, summed in quadrature with the *accuracy* uncertainy
associated with the absolute responses of the SPC sensors.

Alpha particle velocity vector, from 1-dimensional Maxwellian fitting, in the spacecraft frame (All Qualities) [va_fit_SC]

The alpha particle (He++) peak in the solar wind, when clearly distinguishable,
is fit to a convected Maxwellian model.

---> 1-sigma error [va_fit_SC_uncertainty]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  The flow angles relative to the SPC are
obtained by comparing fluxes upon the four sensor quadrants. This uncertainty
incorporates uncertainties in the absolute responses of the respective sensors.

Alpha particle velocity vector, from 1-dimensional Maxwellian fitting, in the [inertial] RTN frame (All Qualities) [va_fit_RTN]

The alpha particle (He++) peak in the solar wind, when clearly distinguishable,
is fit to a convected Maxwellian model.

---> 1-sigma error [va_fit_RTN_uncertainty]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  The flow angles relative to the SPC are
obtained by comparing fluxes upon the four sensor quadrants. This uncertainty
incorporates uncertainties in the absolute responses of the respective sensors.

Alpha particle density, from 1-dimensional Maxwellian fitting. (All Qualities) [na_fit]

The alpha particle (He++) peak in the solar wind, when clearly distinguishable,
is fit to a convected Maxwellian model.

---> 1-sigma error [na_fit_uncertainty]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  This variable reflects *precision*
uncertainty from fitting, summed in quadrature with the *accuracy* uncertainy
associated with the absolute responses of the SPC sensors.

Alpha particle radial [most probable] thermal speed, from 1-dimensional Maxwellian fitting. (All Qualities) [wa_fit]

The alpha particle (He++) peak in the solar wind, when clearly distinguishable,
is fit to a convected Maxwellian model.  This measurement most accurately
represents the thermal width of the reduced phase-space-distribution function
along the SPC-normal direction. This roughly corresponds to the radial component
of the temperature tensor.  This is a most probable thermal speed, i.e. the
model distribution goes like exp(-v^2/w^2).

---> 1-sigma error [wa_fit_uncertainty]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  This variable reflects *precision*
uncertainty from fitting, summed in quadrature with the *accuracy* uncertainy
associated with the absolute responses of the SPC sensors.

Population 3 velocity vector, from 1-dimensional Maxwellian fitting, in the spacecraft frame (All Qualities) [v3_fit_SC]

The population 3 peak in the solar wind, when clearly distinguishable, is fit to
a convected Maxwellian model.   Population 3 most typically characterizes a
proton shoulder or beam (mtoq=1)

---> 1-sigma error [v3_fit_SC_uncertainty]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  The flow angles relative to the SPC are
obtained by comparing fluxes upon the four sensor quadrants. This uncertainty
incorporates uncertainties in the absolute responses of the respective sensors.

Population 3 velocity vector, from 1-dimensional Maxwellian fitting, in the [inertial] RTN frame (All Qualities) [v3_fit_RTN]

The population 3 peak in the solar wind, when clearly distinguishable, is fit to
a convected Maxwellian model.   Population 3 most typically characterizes a
proton shoulder or beam (mtoq=1)

---> 1-sigma error [v3_fit_RTN_uncertainty]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  The flow angles relative to the SPC are
obtained by comparing fluxes upon the four sensor quadrants. This uncertainty
incorporates uncertainties in the absolute responses of the respective sensors.

Population 3 particle density, from 1-dimensional Maxwellian fitting. (All Qualities) [n3_fit]

The population 3 particle peak in the solar wind, when clearly distinguishable,
is fit to a convected Maxwellian model.  Population 3 most typically
characterizes a proton shoulder or beam (mtoq=1)

---> 1-sigma error [n3_fit_uncertainty]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  This variable reflects *precision*
uncertainty from fitting, summed in quadrature with the *accuracy* uncertainy
associated with the absolute responses of the SPC sensors.

Population 3 particle radial [most probable] thermal speed, from 1-dimensional Maxwellian fitting. (All Qualities) [w3_fit]

The population 3 peak in the solar wind, when clearly distinguishable, is fit to
a convected Maxwellian model.  Population 3 most typically characterizes a
proton shoulder or beam (mtoq=1)  This measurement most accurately represents
the thermal width of the reduced phase-space-distribution function along the
SPC-normal direction. This roughly corresponds to the radial component of the
temperature tensor.  This is a most probable thermal speed, i.e. the model
distribution goes like exp(-v^2/w^2).

---> 1-sigma error [w3_fit_uncertainty]

This uncertainty may be invalid when the Maxwellian is a poor model for the
data. Refer to the data quality flags.  This variable reflects *precision*
uncertainty from fitting, summed in quadrature with the *accuracy* uncertainy
associated with the absolute responses of the SPC sensors.

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_SWP_SPE_SF0_L3_PAD doi:10.48322/8ync-7p95

Description

http://sprg.ssl.berkeley.edu/data/psp/pub/sci/sweap/description/

Modification History

Revision 0

Data Variable Descriptions

Quality Flag [QUALITY_FLAG]

The quality flag is a two-byte unsigned integer (UINT2) with its least
significant bit (Bit 1) indicating: Counter Overflow, Bit 2: Snapshot ON, Bit 3:
Alternate Energy Table, Bit 4: Spoiler Test, Bit 5: Attenuator Engaged, Bit 6:
Highest Archive Rate, Bit 7: No Targeted Sweep, Bit 8: SPAN-Ion New Mass Table
(not applicable to electrons), Bit 9: Over-deflection, Bit 10: Archive Snapshot
ON Bits 11-16: Reserved.

Differential Energy Flux vs Energy at Each Pitch Angle (spectrograms) [EFLUX_VS_PA_E_byE_atP]

Differential Energy Flux vs Pitch Angle at Each Energy Level (spectrograms) [EFLUX_VS_PA_E_atE_byP]

Differential Energy Flux vs Energy [EFLUX_VS_ENERGY]

Magnetic Field in Spacecraft Coordinates [MAGF_SC]

In spacecraft frame

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_SWP_SPI_SF00_L2_8DX32EX8A doi:10.48322/ftnv-7755

Description

http://sprg.ssl.berkeley.edu/data/psp/pub/sci/sweap/description/

Modification History

Revision 0

Data Variable Descriptions

Quality Flag [QUALITY_FLAG]

The quality flag is a two-byte unsigned integer (CDF_UINT2) with its least
significant bit (Bit 0) indicating: Counter Overflow, Bit 1: Survey Snapshot ON
(not applicable to archive products), Bit 2: Alternate Energy Table, Bit 3:
Spoiler Test, Bit 4: Attenuator Engaged, Bit 5: Highest Archive Rate, Bit 6: No
Targeted Sweep, Bit 7: SPAN-Ion New Mass Table (not applicable to electrons),
Bit 8: Over-deflection, Bit 9: Archive Snapshot ON, Bits 10-15: Reserved.

Differential Energy Flux vs Energy/angle bin [EFLUX]

Energy [NO PLOT] [ENERGY]

Elevation Angle in instrument coordinates [NO PLOT] [THETA]

Azimuth Angle in instrument coordinates [NO PLOT] [PHI]

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_SWP_SPI_SF00_L3_MOM

Description

http://sprg.ssl.berkeley.edu/data/psp/pub/sci/sweap/description/

Modification History

Revision 0

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_SWP_SPI_SF00_L3_MOM_INST doi:10.48322/ypyh-s325

Description

http://sprg.ssl.berkeley.edu/data/psp/pub/sci/sweap/description/

Modification History

Revision 0

Data Variable Descriptions

Quality Flag [QUALITY_FLAG]

The quality flag is a two-byte unsigned integer (CDF_UINT2) with its least
significant bit (Bit 0) indicating: Counter Overflow, Bit 1: Survey Snapshot ON
(not applicable to archive products), Bit 2: Alternate Energy Table, Bit 3:
Spoiler Test, Bit 4: Attenuator Engaged, Bit 5: Highest Archive Rate, Bit 6: No
Targeted Sweep, Bit 7: SPAN-Ion New Mass Table (not applicable to electrons),
Bit 8: Over-deflection, Bit 9: Archive Snapshot ON, Bits 10-15: Reserved.

Partial Moment Density [DENS]

Partial Moment Velocity in Instrument Coordinates [VEL]

In instrument frame

Partial Moment Temperature Tensor in instrument frame [T_TENSOR]

In instrument frame

Average of Trace of Partial Moment Temperature Tensor [TEMP]

Magnetic Field in Spacecraft Coordinates [MAGF_SC]

In spacecraft frame

Magnetic Field in Instrument Coordinates [MAGF_INST]

In instrument frame

Differential Energy Flux vs Energy [EFLUX_VS_ENERGY]

Differential Energy Flux vs Theta [EFLUX_VS_THETA]

Differential Energy Flux vs Phi [EFLUX_VS_PHI]

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_SWP_SPI_SF01_L2_8DX32EX8A (spase://NASA/NumericalData/ParkerSolarProbe/SWEAP/SPAN-I/Level2/AlphaDifferentialEnergyFlux/VariableCadence)

Description

http://sprg.ssl.berkeley.edu/data/psp/pub/sci/sweap/description/

Modification History

Revision 0

Data Variable Descriptions

Quality Flag [QUALITY_FLAG]

The quality flag is a two-byte unsigned integer (CDF_UINT2) with its least
significant bit (Bit 0) indicating: Counter Overflow, Bit 1: Survey Snapshot ON
(not applicable to archive products), Bit 2: Alternate Energy Table, Bit 3:
Spoiler Test, Bit 4: Attenuator Engaged, Bit 5: Highest Archive Rate, Bit 6: No
Targeted Sweep, Bit 7: SPAN-Ion New Mass Table (not applicable to electrons),
Bit 8: Over-deflection, Bit 9: Archive Snapshot ON, Bit 10: Bad Energy Table,
Bit 11: MCP Test, Bit 12: Survey Available, Bit 13:  ُArchive Available, Bits
14-15: Reserved.

Differential Energy Flux vs Energy/Angle Bin [EFLUX]

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_SWP_SPI_SF0A_L3_MOM

Description

http://sprg.ssl.berkeley.edu/data/psp/pub/sci/sweap/description/

Modification History

Revision 0

Data Variable Descriptions

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

PSP_SWP_SPI_SF0A_L3_MOM_INST doi:10.48322/ke19-2789

Description

http://sprg.ssl.berkeley.edu/data/psp/pub/sci/sweap/description/

Modification History

Revision 0

Data Variable Descriptions

Quality Flag [QUALITY_FLAG]

The quality flag is a two-byte unsigned integer (CDF_UINT2) with its least
significant bit (Bit 0) indicating: Counter Overflow, Bit 1: Survey Snapshot ON
(not applicable to archive products), Bit 2: Alternate Energy Table, Bit 3:
Spoiler Test, Bit 4: Attenuator Engaged, Bit 5: Highest Archive Rate, Bit 6: No
Targeted Sweep, Bit 7: SPAN-Ion New Mass Table (not applicable to electrons),
Bit 8: Over-deflection, Bit 9: Archive Snapshot ON, Bits 10-15: Reserved.

Partial Moment Density [DENS]

Partial Moment Velocity in Instrument Coordinates [VEL]

In instrument frame

Partial Moment Temperature Tensor in instrument frame [T_TENSOR]

In instrument frame

Average of Trace of Partial Moment Temperature Tensor [TEMP]

Magnetic Field in Spacecraft Coordinates [MAGF_SC]

In spacecraft frame

Magnetic Field in Instrument Coordinates [MAGF_INST]

In instrument frame

Differential Energy Flux vs Energy [EFLUX_VS_ENERGY]

Differential Energy Flux vs Theta [EFLUX_VS_THETA]

Differential Energy Flux vs Phi [EFLUX_VS_PHI]

Dataset in CDAWeb
Data Access Code Examples written in

and IDL®.
Back to top

NASA Official: Robert M. Candey
(301)286-6707, Robert.M.Candey@nasa.gov
Curator: Tami Kovalick
Last Modified:

Contact SPDF: NASA-SPDF-Support@nasa.onmicrosoft.com
+ Privacy Policy and Important Notices
+ Accessibility