
The Mercury Surface, Space Environment, Geochemistry and Ranging (MESSENGER) mission is designed to study the characteristics and environment of Mercury from orbit. Specifically, the scientific objectives of the mission are to characterize the chemical composition of Mercury's surface, the geologic history, the nature of the magnetic field, the size and state of the core, the volatile inventory at the poles, and the nature of Mercurys exosphere and magnetosphere over a nominal orbital mission of one Earth year MESSENGER launched on 3 August 2004 at 6:15:56 UT (2:15:56 a.m. EDT) on a Delta 7925H (a Delta II Heavy launch vehicle with nine strapon solidrocket boosters). The spacecraft was injected into solar orbit 57 minutes later. The solar panels were then deployed and the spacecraft began sending data on its status. One year after launch, on 2 August 2005, MESSENGER flew by Earth at an altitude of 2347 km. On 12 December 2005 at 11:30 UT, MESSENGER fired its large thruster for 524 seconds, changing the spacecraft velocity by 316 m/s and putting it on course for its 24 October 2006 Venus flyby at an altitude of 2990 km. The second Venus flyby took place on 5 June 2007 at 23:08 UT (7:08 p.m. EDT) at an altitude of approximately 337 km. The first of three Mercury flybys, all at roughly 200 km altitude, occurred on 14 January 2008 at 19:04:39 UT, and the second on 6 October 2008 at 08:40:22 UT. The third will be on 29 September 2009. There are also five deep space manuevers. Data collected during the Mercury flybys will be used to help plan the scientific campaign during the orbital phase. Mercury orbit insertion will take place on 18 March 2011, requiring a deltaV of 0.867 km/s. The nominal orbit is planned to have a periapsis of 200 km at 60 degrees N latitude, an apoapsis of 15,193 km, a period of 12 hours and an inclination of 80 degrees. The periapsis will slowly rise due to solar perturbations to over 400 km at the end of 88 days (one Mercury year) at which point it will be readjusted to a 200 km, 12 hour orbit via a two burn sequence. Data will be collected from orbit for one Earth year, the nominal end of the primary mission will be in March 2012. Global stereo image coverage at 250 m/pixel resolution is expected. The mission should also yield global composition maps, a 3D model of Mercury's magnetosphere, topographic profiles of the northern hemisphere, gravity field to degree and order 16, altitude profiles of elemental species, and a characterization of the volatiles in permanently shadowed craters at the poles. The MESSENGER spacecraft is a squat box (1.27 m x 1.42 m x 1.85 m) with a semicylindrical thermal shade (roughly 2.5 meters tall and 2 meters wide) for protection from the Sun and two solar panel wings extending radially about 6 meters from tip to tip. A 3.6 m magnetometer boom also extends from the craft. The total mass of the spacecraft is 1093 kg, 607.8 kg of this is propellant and helium. The structure is primarily graphitecyanateester (GrCE) composite and consists of two vertical panels which support two large fuel tanks and two vertical panels which support the oxidizer tank and plumbing panel. The four vertical panels make up the center column and are bolted at their aft ends to an aluminum adapter. A single top deck panel mounts the LVA (large velocity adjust) thruster, small thrusters, helium and auxiliary fuel tanks, star trackers and battery. Main propulsion is via the 645N, 317s bipropellant LVA thruster, four 22N monopropellant thrusters provide spacecraft steering during main thruster burns, and ten 4N monopropellant thrusters are used for attitude control. There is also a reactionwheel attitude control system. Knowledge for attitude control is provided by star tracking cameras, an inertial measurement unit, and six solar sensors. Power is provided by the solar panels, which extend beyond the sunshade and are rotatable to balance panel temperature and power generation, which provides a nominal 450 W in Mercury orbit. The panels are 70% optical solar reflectors and 30% GaAs/Ge cells. The power is stored in a commonpressurevessel nickelhydrogen battery, with 11 vessels and 2 cells per vessel. Communications are in Xband with downlink through two fixed phasedarray antenna clusters and uplink and downlink through medium and lowgain antennas on the forward and aft sides of the spacecraft. Passive thermal control, primarily a fixed opaque ceramic cloth sunshade, is utilized to maintain operating temperatures near the Sun. Radiators are built into the structure and the orbit is optimized to minimize infrared and visible light heating of the spacecraft from the surface of Mercury. Multilayer insulation, low conductivity couplings, and heaters are also used to maintain temperatures within operating limits. Five science instruments are mounted externally on the bottom deck of the main body: the Mercury Dual Imaging System (MDIS), GammaRay and Neutron Spectrometer (GRNS), Xray Spectrometer (XRS), Mercury Laser Altimeter (MLA), and Atmospheric and Surface Composition Spectrometer (MASCS). The Energetic Particle and Plasma Spectrometer (EPPS) is mounted on the side and top deck and the magnetometer (MAG) is at the end of the 3.6 m boom. Radio Science (RS) experiments will use the existing communications system. The Messenger MAG instrument is a miniature threeaxis ringcore fluxgate magnetometer with lownoise electronics. It is mounted on a 3.6 m boom in the antisunward direction. The MAG has .. 1530 and ..51300 nT ranges with 20bit internal resolution and 17bit output resolution. The MAG probe samples magnetic field values along the X, Y, and Z axes at a rate of up to 20 samples/second (commandable and can vary). This dataset has 3axis calibrated samples of the magnetic field in heliospheric RTN coordinates in units of nanoTesla, Br, Bt, Bn. The spacecraft position is identified by radial distance from the Sun, latitude above the ecliptic plane, and azimuth with respect to the EarthSun line in the ecliptic plane. Anderson, B. J., M. H. Acuna, D. A. Lohr , J. Scheifele, A. Raval, H. Korth, and J. A. Slavin, \'The Magnetometer instrument on MESSENGER\', Space Science Reviews, 2007.[ANDREWSETAL2007]
Azimuthal angle of MESSENGER spacecraft in the instantaneous ecliptic plane with respect to the EarthSun line in units of degrees, positive in direction of the Earth's orbital motion with Z in J2000 coordinates
Azimuthal angle of MESSENGER spacecraft in the instantaneous ecliptic plane with respect to the EarthSun line in units of degrees, positive in direction of the Earth's orbital motion with Z in J2000 coordinates
Computed on the fly to determine the time res. between points
POES N19 data: POES/MetOp: Particle Precipitation Data (These data have known contamination problems. Please consult provider rob.redmon@noaa.gov for usage recommendations.)
POES N19 data: POES/MetOp: Particle Precipitation Data (These data have known contamination problems. Please consult provider rob.redmon@noaa.gov for usage recommendations.)
K. Torkar et al, Active Spacecraft Potential Control Investigation Space Science Reviews, 2014, DOI: 10.1007/s1121401400493 Further information:  http://www.iwf.oeaw.ac.at/en/research/nearearthspace/mms/  http://mms.space.swri.edu/
150224 Initial version 150831 Minor updates and fixes 160205 CDF file format guide compliant
Calibrated magneticspectral density computed by onboard FFTs by the Digital Signal Processor (DSP) from the Search Coil Magnetometer (SCM) in the SCM123 coordinate system (scm1 =  x sensor; scm2 = z sensor; scm3 = y sensor). This product is computed in space from individual components that are not synchronized to the 1 second pulse. Therefore, the timing between channels can be inaccurate by a fraction of a second. The samples times are interval start times taken from the x component.
electric spectral density
search coil magnetometer spectral density
electric spectral density
EDI ambient data. The EDI instrument paper and data products guide can be found at the following two links: http://link.springer.com/article/10.1007%2Fs1121401501827, https://lasp.colorado.edu/mms/sdc/public/datasets/fields/
v0.0.0  Original version. v1.0.0  Include trajectory vectors and optics state. v1.1.0  Update metadata: counts > flux. v1.2.0  Added flux error. v1.3.0  Trajectory vector errors are now deltas. v1.4.0  Fixed deadtime correction and error values. v1.5.0  Factor of 2 for accumulation time & 2 for abscal factor in srvy mode. v1.6.0  No factor of 2 for accumulation time in srvy mode. v2.0.0  Reduced file size with scalar errors. Update metadata. v2.1.0  Correct fill value for fluxes. v3.0.0  Omnidirectional error for trajectories. YVersion linked to cal file. Single epoch for counts. v4.0.0  Replace data in GSM coordinates with data in DBCS to be consistent with other particle instruments.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
EDI ambient data. The EDI instrument paper and data products guide can be found at the following two links: http://link.springer.com/article/10.1007%2Fs1121401501827, https://lasp.colorado.edu/mms/sdc/public/datasets/fields/
v1.0.0  Original version. v1.1.0  Correct fill value for fluxes. v2.0.0  Omnidirectional error for trajectories. YVersion linked to cal file. Single epoch for counts. v3.0.0  Replace data in GSM coordinates with data in DBCS to be consistent with other particle instruments.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
EDI electric field data. Instrument papers for EDI can be found at: http://link.springer.com/article/10.1007%2Fs1121401501827
v1.0.0  First version. TRITOF selection based on smallest error. v1.1.0  TRITOF merged by weighted average. v1.2.0  Fixed t_delta_plus/minus CDF_type. v1.3.0  Fixed Fixed vdrift SI conversion. v1.4.0  Fixed data duplication caused by multiple l2pre file locations. v1.5.0  Inplemented baseline*beams*Bmag filter for triangulation. v1.6.0  Inplemented null files for no or low quality data.
EDI Q0 data. The EDI instrument paper and data products guidescan be found at the following two links: http://link.springer.com/article/10.1007%2Fs1121401501827, https://lasp.colorado.edu/mms/sdc/public/datasets/fields/
v0.0.0  First version. v0.0.1  Filled energy variables. v0.0.2  Energy written properly. v1.0.0  Update variable names. v1.1.0  Added optics state. v2.0.0  Added electron trajectories. v2.1.0  Deltas on trajectory vectors are now deltas. v3.0.0  Reduced file size with scalar errors. Add VAR_NOTES. v3.1.0  Fixed optics datatype. v4.0.0  Removed unused Epoch variable. v5.0.0  Trajectories are provided in DBCS coordinates.
Q0 data consists of raw electron counts. The error at any one time is the squareroot of the counts. Note that there may be contamination from the EDI electron beams. See the data products guide or contact an EDI team member to learn about beam contamination.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
EDI ambient data. The EDI instrument paper and data products guide can be found at the following two links: http://link.springer.com/article/10.1007%2Fs1121401501827, https://lasp.colorado.edu/mms/sdc/public/datasets/fields/
v0.0.0  Original version. v1.0.0  Include trajectory vectors and optics state. v1.1.0  Update metadata: counts > flux. v1.2.0  Added flux error. v1.3.0  Trajectory vector errors are now deltas. v1.4.0  Fixed deadtime correction and error values. v1.5.0  Factor of 2 for accumulation time & 2 for abscal factor in srvy mode. v1.6.0  No factor of 2 for accumulation time in srvy mode. v2.0.0  Reduced file size with scalar errors. Update metadata. v2.1.0  Correct fill value for fluxes. v3.0.0  Omnidirectional error for trajectories. Correct time deltas. YVersion linked to cal file. Single epoch for counts. v4.0.0  Replace data in GSM coordinates with data in DBCS to be consistent with other particle instruments.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
EDI ambient data. The EDI instrument paper and data products guide can be found at the following two links: http://link.springer.com/article/10.1007%2Fs1121401501827, https://lasp.colorado.edu/mms/sdc/public/datasets/fields/
v1.0.0  Original version. v1.1.0  Correct fill value for fluxes. v2.0.0  Omnidirectional error for trajectories. YVersion linked to cal file. Single epoch for counts. v3.0.0  Replace data in GSM coordinates with data in DBCS to be consistent with other particle instruments. v4.0.0  Each trajectory has its own LABL_PTR_1 variable.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
EDI electric field data. Instrument papers for EDI can be found at: http://link.springer.com/article/10.1007%2Fs1121401501827
v1.0.0  First version. TRITOF selection based on smallest error. v1.1.0  TRITOF merged by weighted average. v1.2.0  Fixed t_delta_plus/minus CDF_type. v1.3.0  Fixed Fixed vdrift SI conversion. v1.4.0  Fixed data duplication caused by multiple l2pre file locations. v1.5.0  Inplemented baseline*beams*Bmag filter for triangulation. v1.6.0  Inplemented null files for no or low quality data.
EDI Q0 data. The EDI instrument paper and data products guidescan be found at the following two links: http://link.springer.com/article/10.1007%2Fs1121401501827, https://lasp.colorado.edu/mms/sdc/public/datasets/fields/
v0.0.0  First version. v0.0.1  Filled energy variables. v0.0.2  Energy written properly. v1.0.0  Update variable names. v1.1.0  Added optics state. v2.0.0  Added electron trajectories. v2.1.0  Deltas on trajectory vectors are now deltas. v3.0.0  Reduced file size with scalar errors. Add VAR_NOTES. v4.0.0  Removed unused Epoch variable. v5.0.0  Trajectories are provided in DBCS coordinates.
Q0 data consists of raw electron counts. The error at any one time is the squareroot of the counts. Note that there may be contamination from the EDI electron beams. See the data products guide or contact an EDI team member to learn about beam contamination.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
https://mms.gsfc.nasa.gov/ For detailed timing information, such as needed for cross spectral analysis, please consult the EDP Data Products Guide.
V.0. Initial release.
L1B AC Electric Field
https://mms.gsfc.nasa.gov/ The full name of PI affiliations: SWRI  Southwest Research Institute. LASP  Laboratory for Atmospheric and Space Physics. KTH  Kungliga Tekniska Hogskolan (Swedish Royal Institute of Technology). For detailed timing information, such as needed for cross spectral analysis, please consult the EDP Data Products Guide.
V.0. Initial release. V.1. QL (v1.0.z), SCPOT (v1.0.z), L2A (v0.1.z) now uses ASPOC srvy l2 and DEFATT, if these are available. Brst QL uses intermediate L2A file from Fast mode for delta offsets. Bitmask changed to uint16 and Quality to uint8. V.2. SCPOT (v2.0.z), L2A (v1.0.z) now uses variable names in accordance with new recommended standard for FIELDS, All products change shortening factor to 1.25 on SDP, offsets applied indicated by GlobalAttribute Calibration_file. V.2. L2a (v2.0.z), QL (v1.6.z) now try to remove solar wind wake which previously left a clear sinusodial signal in the data. V.3. L2a (v3.0.z) Slow Mode probe Gain set to 1.0 when orbital radius less than 5 RE (1.25 otherwise), L2pre (v2.0.z) DSL offsets removed from field is now included in the file as the Slow mode is dependent on scpot product (Fast/Brst is simply based on offset in Calibration_file).
https://mms.gsfc.nasa.gov/ For detailed timing information, such as needed for cross spectral analysis, please consult the EDP Data Products Guide.
V.0. Initial release.
https://mms.gsfc.nasa.gov/ The full name of PI affiliations: SWRI  Southwest Research Institute. LASP  Laboratory for Atmospheric and Space Physics. KTH  Kungliga Tekniska Hogskolan (Swedish Royal Institute of Technology). For detailed timing information, such as needed for cross spectral analysis, please consult the EDP Data Products Guide.
V.0. Initial release. V.1. QL (v1.0.z), SCPOT (v1.0.z), L2A (v0.1.z) now uses ASPOC srvy l2 and DEFATT, if these are available. Brst QL uses intermediate L2A file from Fast mode for delta offsets. Bitmask changed to uint16 and Quality to uint8. V.2. SCPOT (v2.0.z), L2A (v1.0.z) now uses variable names in accordance with new recommended standard for FIELDS, All products change shortening factor to 1.25 on SDP, offsets applied indicated by GlobalAttribute Calibration_file. V.2. L2a (v2.0.z), QL (v1.6.z) now try to remove solar wind wake which previously left a clear sinusodial signal in the data. V.3. L2a (v3.0.z) Slow Mode probe Gain set to 1.0 when orbital radius less than 5 RE (1.25 otherwise), L2pre (v2.0.z) DSL offsets removed from field is now included in the file as the Slow mode is dependent on scpot product (Fast/Brst is simply based on offset in Calibration_file).
https://mms.gsfc.nasa.gov/ For detailed timing information, such as needed for cross spectral analysis, please consult the EDP Data Products Guide.
V.0. Initial release.
https://mms.gsfc.nasa.gov/ The full name of PI affiliations: SWRI  Southwest Research Institute. LASP  Laboratory for Atmospheric and Space Physics. KTH  Kungliga Tekniska Hogskolan (Swedish Royal Institute of Technology). For detailed timing information, such as needed for cross spectral analysis, please consult the EDP Data Products Guide.
V.0. Initial release. V.1. QL (v1.0.z), SCPOT (v1.0.z), L2A (v0.1.z) now uses ASPOC srvy l2 and DEFATT, if these are available. Brst QL uses intermediate L2A file from Fast mode for delta offsets. Bitmask changed to uint16 and Quality to uint8. V.2. SCPOT (v2.0.z), L2A (v1.0.z) now uses variable names in accordance with new recommended standard for FIELDS, All products change shortening factor to 1.25 on SDP, offsets applied indicated by GlobalAttribute Calibration_file. V.2. L2a (v2.0.z), QL (v1.6.z) now try to remove solar wind wake which previously left a clear sinusodial signal in the data. V.3. L2a (v3.0.z) Slow Mode probe Gain set to 1.0 when orbital radius less than 5 RE (1.25 otherwise), L2pre (v2.0.z) DSL offsets removed from field is now included in the file as the Slow mode is dependent on scpot product (Fast/Brst is simply based on offset in Calibration_file).
L1B AC Electric Field
empty
Constantly modifying this code
empty
Constantly modifying this code
empty
Constantly modifying this code
empty
Constantly modifying this code
empty
Constantly modifying this code
http://www.lasp.colorado.edu
Generated at LASP
http://www.lasp.colorado.edu
Generated at LASP
http://www.lasp.colorado.edu
Generated at LASP
http://www.lasp.colorado.edu
Generated at LASP
The Fluxgate Magnetometers (FGM) on Magnetospheric Multiscale consist of a traditional Analog Fluxgate Magnetometer (AFG), and a Digital Fluxgate magnetometer (DFG). The dual magnetometers are operated as a single instrument providing a single intercalibrated data product. Range changes occur at different times on the two instruments so the gains checked each periapsis can be carried out unambiguously to apoapsis. Cross correlation of calibration parameters can separate causes of the any apparent calibration changes. Use of Electron Drift Instrument (EDI) to determine the field along the rotation axis allows accurate monitoring of the zero levels along the rotation axis. Prior to launch the magnetometers were calibrated at the Technical University, Braunschweig, except for the AFG magnetometers on MMS3 and MMS4, which were calibrated at UCLA. Both sets of sensors are operated for the entire MMS orbit, with slow survey (8 samples per second) outside of the Region of Interest (ROI), and fast survey (16 samples per second) inside the ROI. Within the ROI burst mode data (128 samples per second) are also acquired. A detailed description of the MMS fluxgate magnetometers, including science objectives, instrument description, calibration, magnetic cleanliness program, and data flow can be found at http://link.springer.com/article/10.1007%2Fs1121401400573 (DOI 10.1007/s1121401400573).Additional information can also be found at http://wwwspc.igpp.ucla.edu/ssc/mms (UCLA),and http://www.iwf.oeaw.ac.at (IWF, Graz). For the purpose of creating a unified FGM Level2 data product, burst mode data is taken from DFG and survey mode data is taken from AFG. Because AFG and DFG are crosscalibrated on an orbitaveraged basis, small differences in offset may be observed between Level2 burst and survey mode data. Consequently, any differences are within the error of the measurement. Based on preliminary analysis of the data, the absolute error within the Region of Interest (ROI) is estimated to be no more than 0.1 nT in the spinplane, 0.15 nT along the spinaxis and 0.2 nT in total magnitude.
version X=5: * Yversion number comes from cal file entries. * Ensures there are 2 ephemeris points before/after data to enable proper spline. * Fix to depend_0 of rdeltahalf: fixes bug when reading position data. * Lvector for DMPA2GSE transformation is smoothed with a gaussian filter, instead of using a single average value for the day. This shortterm filter avoids introduding artificial jumps at 00:00 UTC and removes 7minute 'wobble' after maneuvers in the GSE result. * Fixes error with DEFATT file selection found when choosing the daily DEFATT files to be used in Phase 2. * Fixed bug where reference Etemp was used for high range gain. Now uses measured Etemp. version X=4: First version for public release of L2. Renamed variables to conform with new MMS variable name guidelines (obs_instr_paramName[_coordSys]_mode_level): Mag field parameters include 'b' for paramName. Use 'r' instead of 'pos' for S/C position paramName. Eliminated 'rate', replaced with 'bdeltahalf'. Added 'rdeltahalf'. l1a_mode is now just 'mode'. version X=3: fixed removal of overlap between modes. fixed a bug that caused stemp and etemp to be empty. version X=2: flag parameter name corrected: was 'status' added bits 4, 5, 6 to flag saturation on B1, B2, and B3, respectively added bit 7 to flag bad data at range changes Added etemp and l1a_mode parameters. rate, hirange, and stemp parameters now comply with MMS CDF Guidlelines, e.g. FILLVAL now defined for stemp and etemp, and is set to !values.f_nan No longer use Var_Parents attribute in stemp  see Parents instead In this version, temperaturecorrected gains are applied. Reference temperatures are used when stemp or etemp are set to FILLVAL. Nonlinearity correction is applied to high rage DFG data. version X=1: added 'flag', rate and hirange parameters (but 'flag' is actually called 'status')
During nominal operatins in the region of interest, DMPA is within 3 degrees of GSE.
During nominal operatins in the region of interest, DMPA is within 3 degrees of GSE.
bit definitions: . 0: TBD, 1: TBD, 2: user flagged, 3: TBD, . 4: B1 saturated, 5: B2 saturated, 6: B3 saturated, 7: rangechange glitch, . 831: TBD
The Fluxgate Magnetometers (FGM) on Magnetospheric Multiscale consist of a traditional Analog Fluxgate Magnetometer (AFG), and a Digital Fluxgate magnetometer (DFG). The dual magnetometers are operated as a single instrument providing a single intercalibrated data product. Range changes occur at different times on the two instruments so the gains checked each periapsis can be carried out unambiguously to apoapsis. Cross correlation of calibration parameters can separate causes of the any apparent calibration changes. Use of Electron Drift Instrument (EDI) to determine the field along the rotation axis allows accurate monitoring of the zero levels along the rotation axis. Prior to launch the magnetometers were calibrated at the Technical University, Braunschweig, except for the AFG magnetometers on MMS3 and MMS4, which were calibrated at UCLA. Both sets of sensors are operated for the entire MMS orbit, with slow survey (8 samples per second) outside of the Region of Interest (ROI), and fast survey (16 samples per second) inside the ROI. Within the ROI burst mode data (128 samples per second) are also acquired. A detailed description of the MMS fluxgate magnetometers, including science objectives, instrument description, calibration, magnetic cleanliness program, and data flow can be found at http://link.springer.com/article/10.1007%2Fs1121401400573 (DOI 10.1007/s1121401400573).Additional information can also be found at http://wwwspc.igpp.ucla.edu/ssc/mms (UCLA),and http://www.iwf.oeaw.ac.at (IWF, Graz). For the purpose of creating a unified FGM Level2 data product, burst mode data is taken from DFG and survey mode data is taken from AFG. Because AFG and DFG are crosscalibrated on an orbitaveraged basis, small differences in offset may be observed between Level2 burst and survey mode data. Consequently, any differences are within the error of the measurement. Based on preliminary analysis of the data, the absolute error within the Region of Interest (ROI) is estimated to be no more than 0.1 nT in the spinplane, 0.15 nT along the spinaxis and 0.2 nT in total magnitude.
version X=5: * Yversion number comes from cal file entries. * Ensures there are 2 ephemeris points before/after data to enable proper spline. * Fix to depend_0 of rdeltahalf: fixes bug when reading position data. * Lvector for DMPA2GSE transformation is smoothed with a gaussian filter, instead of using a single average value for the day. This shortterm filter avoids introduding artificial jumps at 00:00 UTC and removes 7minute 'wobble' after maneuvers in the GSE result. * Fixes error with DEFATT file selection found when choosing the daily DEFATT files to be used in Phase 2. * Fixed bug where reference Etemp was used for high range gain. Now uses measured Etemp. version X=4: First version for public release of L2. Renamed variables to conform with new MMS variable name guidelines (obs_instr_paramName[_coordSys]_mode_level): Mag field parameters include 'b' for paramName. Use 'r' instead of 'pos' for S/C position paramName. Eliminated 'rate', replaced with 'bdeltahalf'. Added 'rdeltahalf'. l1a_mode is now just 'mode'. version X=3: fixed removal of overlap between modes. fixed a bug that caused stemp and etemp to be empty. version X=2: flag parameter name corrected: was 'status' added bits 4, 5, 6 to flag saturation on B1, B2, and B3, respectively added bit 7 to flag bad data at range changes Added etemp and l1a_mode parameters. rate, hirange, and stemp parameters now comply with MMS CDF Guidlelines, e.g. FILLVAL now defined for stemp and etemp, and is set to !values.f_nan No longer use Var_Parents attribute in stemp  see Parents instead In this version, temperaturecorrected gains are applied. Reference temperatures are used when stemp or etemp are set to FILLVAL. Nonlinearity correction is applied to high rage DFG data. version X=1: added 'flag', rate and hirange parameters (but 'flag' is actually called 'status')
During nominal operatins in the region of interest, DMPA is within 3 degrees of GSE.
During nominal operatins in the region of interest, DMPA is within 3 degrees of GSE.
bit definitions: . 0: TBD, 1: TBD, 2: user flagged, 3: TBD, . 4: B1 saturated, 5: B2 saturated, 6: B3 saturated, 7: rangechange glitch, . 831: TBD
FPI usually operates in Fast Survey Mode in the MMS Region Of Interest (ROI) for the current Mission Phase. Data are taken at burst (30/150 ms for DES/DIS) resolution in this mode. Data are also made available at survey (4.5 s, etc) resolution; these form a separate product from this. Per mission design, not all burstresolution data are downlinked. This product contains phasespace distribution maps of those burstresolution data selected for downlink. In particular, the (highest possible quality at the time of release) corrected/converted "Burst SkyMap" distributions are reported with timestamps and other annotation characterizing the state of the instrument system at the indicated time.
See FPI Version Release Notes (https://lasp.colorado.edu/mms/sdc/public/datasets/fpi/) for data set modification history.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Value of zero signifies no quality errors. For nonzero values: Bit0 = manually flagged interval, Bit1 = overcounting/saturation effects likely present in skymap
FPI/DES compression loss indicator, 0=lossless, 1=lossy
FPI/DES alternates between two tables, designated "even" (0) and "odd" (1).
Nominally, spinphase counts range over [0000, 5759] cnts. Each count represents 1/16 deg of observatory spinphase. Zero spinphase count indicates obs +Xaxis aligned with Sun.
Nominally, spinphase angles range over [0, 360) deg. Each count represents 1/16 deg of observatory spinphase. Zero spinphase angle indicates obs +Xaxis aligned with Sun.
Records Pvalue used to despin this burst skymap on board. See FPI docs for details.
see FPI docs for details
Energies (parity 0/1) in the 64step FPI energy table
FPI usually operates in Fast Survey (FS) Mode in the MMS Region Of Interest (ROI) for the current Mission Phase. Data are taken at burst (30/150 ms for DES/DIS) resolution in this mode. Data are also made available at survey (4.5 s, etc) resolution. Per mission design, not all burstresolution data are downlinked, but all survey data are downlinked. Planning around calibration activities, avoidance of Earth radiation belts, etc, when possible, FPI usually operates in Slow Survey (SS) Mode outside of ROI, and then only the 60 s resolution survey data are available. This product contains results from integrating the standard moments of phasespace distributions formed from the indicated data type (DES/DIS burst, FS or SS). For convenience, some additional parameters are included to augment those most commonly found in a moments product of this sort, plus timestamps and other annotation characterizing the state of the instrument system at the indicated time.
See FPI Version Release Notes (https://lasp.colorado.edu/mms/sdc/public/datasets/fpi/) for data set modification history.
Value of zero signifies no quality errors. For nonzero values: Bit0 = manually flagged interval, Bit1 = overcounting/saturation effects likely present in skymap, Bit2 = reported spacecraft potential above 20V, Bit3 = invalid/unavailable spacecraft potential, Bit4 = significant (>25%) cold plasma (<10eV) component, Bit5 = significant (>25%) hot plasma (>30keV) component, Bit6 = high sonic Mach number (v/vth > 2.5), Bit7 = low calculated density (n_DES < 0.05 cm^3), Bit8 = bentPipe magnetic field used instead of brst l2pre magnetic field, Bit9 = srvy l2pre magnetic field used instead of brst l2pre magnetic field, Bit10 = no internally generated photoelectron correction applied
FPI/DES compression loss indicator, 0=lossless, 1=lossy
FPI/DES alternates between two tables, designated "even" (0) and "odd" (1).
Nominally, spinphase counts range over [0000, 5759] cnts. Each count represents 1/16 deg of observatory spinphase. Zero spinphase count indicates obs +Xaxis aligned with Sun.
Nominally, spinphase angles range over [0, 360) deg. Each count represents 1/16 deg of observatory spinphase. Zero spinphase angle indicates obs +Xaxis aligned with Sun.
Records Pvalue used to despin this burst skymap on board. See FPI docs for details.
low energy bin: 0 eV  200 eV. pitchangle bin size: 6 deg.
mid energy bin: 200 eV  2 keV. pitchangle bin size: 6 deg.
high energy bin: 2 keV  30 keV. pitchangle bin size: 6 deg.
Counts, summed over DSC velocitydirs closest to +X_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to X_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to +Y_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to Y_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to +Z_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to Z_DSC, by energy bin.
Counts, summed within 30 degrees parallel bentPipe magnetic field.
Counts, summed within 30 degrees antiparallel to bentPipe magnetic field.
Counts, summed within 60 degrees perpendicular to bentPipe magnetic field.
Differential energy flux, averaged (weighted by solid angle) over all look directions, by energy bin.
Estimated systematic error (positive or negative) in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding. This can be subtracted from bulk velocity to obtain the corrected velocity vector.
Estimated systematic error (positive or negative) in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding. This can be subtracted from bulk velocity to obtain the corrected velocity vector.
Estimated error in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding
Estimated error in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
FPI usually operates in Fast Survey (FS) Mode in the MMS Region Of Interest (ROI) for the current Mission Phase. Data are taken at burst (30/150 ms for DES/DIS) resolution in this mode. Data are also made available at survey (4.5 s, etc) resolution. Per mission design, not all burstresolution data are downlinked, but all survey data are downlinked. Planning around calibration activities, avoidance of Earth radiation belts, etc, when possible, FPI usually operates in Slow Survey (SS) Mode outside of ROI, and then only the 60 s resolution survey data are available. This product contains partial moments that come from performing the standard moment integrals over a limited portion of velocity space. The resulting quantities are named similarly to their corresponding standard moments, but are decorated with 'part' to differentiate. For example, density_part is the density moment integrated from a particular energy step to infinity. These partial moments are formed from the indicated data type (DES/DIS burst, FS or SS). For convenience, some additional parameters are included to augment those most commonly found in a moments product of this sort, plus timestamps and other annotation characterizing the state of the instrument system at the indicated time.
See FPI Version Release Notes (https://lasp.colorado.edu/mms/sdc/public/datasets/fpi/) for data set modification history.
Value of zero signifies no quality errors. For nonzero values: Bit0 = manually flagged interval, Bit1 = overcounting/saturation effects likely present in skymap, Bit2 = reported spacecraft potential above 20V, Bit3 = invalid/unavailable spacecraft potential, Bit4 = significant (>10%) cold plasma (<10eV) component, Bit5 = significant (>25%) hot plasma (>30keV) component, Bit6 = high sonic Mach number (v/vth > 2.5), Bit7 = low calculated density (n_DES < 0.05 cm^3), Bit8 = bentPipe magnetic field used instead of brst l2pre magnetic field, Bit9 = srvy l2pre magnetic field used instead of brst l2pre magnetic field, Bit10 = no internally generated photoelectron correction applied, Bit11 = compression pipeline error, Bit12 = spintone calculation error (DBCS only)
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
Recommended energy index during this burst
FPI usually operates in Fast Survey Mode in the MMS Region Of Interest (ROI) for the current Mission Phase. Data are taken at burst (30/150 ms for DES/DIS) resolution in this mode. Data are also made available at survey (4.5 s, etc) resolution; these form a separate product from this. Per mission design, not all burstresolution data are downlinked. This product contains phasespace distribution maps of those burstresolution data selected for downlink. In particular, the (highest possible quality at the time of release) corrected/converted "Burst SkyMap" distributions are reported with timestamps and other annotation characterizing the state of the instrument system at the indicated time.
See FPI Version Release Notes (https://lasp.colorado.edu/mms/sdc/public/datasets/fpi/) for data set modification history.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Value of zero signifies no quality errors. For nonzero values: Bit0 = manually flagged interval, Bit1 = overcounting/saturation effects likely present in skymap
FPI/DIS compression loss indicator, 0=lossless, 1=lossy
FPI/DIS alternates between two tables, designated "even" (0) and "odd" (1).
Nominally, spinphase counts range over [0000, 5759] cnts. Each count represents 1/16 deg of observatory spinphase. Zero spinphase count indicates obs +Xaxis aligned with Sun.
Nominally, spinphase angles range over [0, 360) deg. Each count represents 1/16 deg of observatory spinphase. Zero spinphase angle indicates obs +Xaxis aligned with Sun.
Records Pvalue used to despin this burst skymap on board. See FPI docs for details.
see FPI docs for details
Energies (parity 0/1) in the 64step FPI energy table
FPI usually operates in Fast Survey (FS) Mode in the MMS Region Of Interest (ROI) for the current Mission Phase. Data are taken at burst (30/150 ms for DES/DIS) resolution in this mode. Data are also made available at survey (4.5 s, etc) resolution. Per mission design, not all burstresolution data are downlinked, but all survey data are downlinked. Planning around calibration activities, avoidance of Earth radiation belts, etc, when possible, FPI usually operates in Slow Survey (SS) Mode outside of ROI, and then only the 60 s resolution survey data are available. This product contains results from integrating the standard moments of phasespace distributions formed from the indicated data type (DES/DIS burst, FS or SS). For convenience, some additional parameters are included to augment those most commonly found in a moments product of this sort, plus timestamps and other annotation characterizing the state of the instrument system at the indicated time.
See FPI Version Release Notes (https://lasp.colorado.edu/mms/sdc/public/datasets/fpi/) for data set modification history.
Value of zero signifies no quality errors. For nonzero values: Bit0 = manually flagged interval, Bit1 = overcounting/saturation effects likely present in skymap, Bit2 = reported spacecraft potential above 20V, Bit3 = invalid/unavailable spacecraft potential, Bit4 = significant (>25%) cold plasma (<10eV) component, Bit5 = significant (>25%) hot plasma (>30keV) component, Bit6 = high sonic Mach number (v/vth > 2.5), Bit7 = low calculated density (n_DIS < 0.05 cm^3), Bit8 = bentPipe magnetic field used instead of brst l2pre magnetic field, Bit9 = srvy l2pre magnetic field used instead of brst l2pre magnetic field, Bit10 = no internally generated photoelectron correction applied
FPI/DIS compression loss indicator, 0=lossless, 1=lossy
FPI/DIS alternates between two tables, designated "even" (0) and "odd" (1).
Nominally, spinphase counts range over [0000, 5759] cnts. Each count represents 1/16 deg of observatory spinphase. Zero spinphase count indicates obs +Xaxis aligned with Sun.
Nominally, spinphase angles range over [0, 360) deg. Each count represents 1/16 deg of observatory spinphase. Zero spinphase angle indicates obs +Xaxis aligned with Sun.
Records Pvalue used to despin this burst skymap on board. See FPI docs for details.
Counts, summed over DSC velocitydirs closest to +X_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to X_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to +Y_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to Y_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to +Z_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to Z_DSC, by energy bin.
Differential energy flux, averaged (weighted by solid angle) over all look directions, by energy bin.
Background differential energy flux by energy bin, averaged (weighted by solid angle) over all directions (flow or look) background level.
Background number density derived via integration of the estimated background differential energy flux.
Estimated systematic error (positive or negative) in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding. This can be subtracted from bulk velocity to obtain the corrected velocity vector.
Estimated systematic error (positive or negative) in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding. This can be subtracted from bulk velocity to obtain the corrected velocity vector.
Estimated error in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding
Estimated error in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
FPI usually operates in Fast Survey (FS) Mode in the MMS Region Of Interest (ROI) for the current Mission Phase. Data are taken at burst (30/150 ms for DES/DIS) resolution in this mode. Data are also made available at survey (4.5 s, etc) resolution. Per mission design, not all burstresolution data are downlinked, but all survey data are downlinked. Planning around calibration activities, avoidance of Earth radiation belts, etc, when possible, FPI usually operates in Slow Survey (SS) Mode outside of ROI, and then only the 60 s resolution survey data are available. This product contains partial moments that come from performing the standard moment integrals over a limited portion of velocity space. The resulting quantities are named similarly to their corresponding standard moments, but are decorated with 'part' to differentiate. For example, density_part is the density moment integrated from a particular energy step to infinity. These partial moments are formed from the indicated data type (DES/DIS burst, FS or SS). For convenience, some additional parameters are included to augment those most commonly found in a moments product of this sort, plus timestamps and other annotation characterizing the state of the instrument system at the indicated time.
See FPI Version Release Notes (https://lasp.colorado.edu/mms/sdc/public/datasets/fpi/) for data set modification history.
Value of zero signifies no quality errors. For nonzero values: Bit0 = manually flagged interval, Bit1 = overcounting/saturation effects likely present in skymap, Bit2 = reported spacecraft potential above 20V, Bit3 = invalid/unavailable spacecraft potential, Bit4 = significant (>10%) cold plasma (<10eV) component, Bit5 = significant (>25%) hot plasma (>30keV) component, Bit6 = high sonic Mach number (v/vth > 2.5), Bit7 = low calculated density (n_DIS <= 0.0 cm^3), Bit8 = bentPipe magnetic field used instead of brst l2pre magnetic field, Bit9 = srvy l2pre magnetic field used instead of brst l2pre magnetic field, Bit10 = no internally generated photoelectron correction applied, Bit11 = compression pipeline error, Bit12 = spintone calculation error (DBCS only), Bit13 = significant (>=20%) penetrating radiation
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
Recommended energy index during this burst
FPI usually operates in Fast Survey Mode in the MMS Region Of Interest (ROI) for the current Mission Phase. Data taken at burst (30/150 ms for DES/DIS) resolution are aggregated on board and made available at survey (4.5 s) resolution in this mode. This product contains phasespace distribution maps of results from surveying the highresolution observations during each 4.5 s period. In particular, the (highest possible quality at the time of release) corrected/converted "Fast Survey SkyMap" distributions are reported with timestamps and other annotation characterizing the state of the instrument system at the indicated time.
See FPI Version Release Notes (https://lasp.colorado.edu/mms/sdc/public/datasets/fpi/) for data set modification history.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Value of zero signifies no quality errors. For nonzero values: Bit0 = manually flagged interval, Bit1 = overcounting/saturation effects likely present in skymap
FPI/DES compression loss indicator, 0=lossless, 1=lossy
Nominally, spinphase counts range over [0000, 5759] cnts. Each count represents 1/16 deg of observatory spinphase. Zero spinphase count indicates obs +Xaxis aligned with Sun.
Nominally, spinphase angles range over [0, 360) deg. Each count represents 1/16 deg of observatory spinphase. Zero spinphase angle indicates obs +Xaxis aligned with Sun.
FPI usually operates in Fast Survey (FS) Mode in the MMS Region Of Interest (ROI) for the current Mission Phase. Data are taken at burst (30/150 ms for DES/DIS) resolution in this mode. Data are also made available at survey (4.5 s) resolution. Per mission design, not all burstresolution data are downlinked, but all survey data are downlinked. Planning around calibration activities, avoidance of Earth radiation belts, etc, when possible, FPI usually operates in Slow Survey (SS) Mode (60 s resolution) outside of ROI. This moments product contains results from integrating the standard moments of phasespace distributions formed from the indicated data type (DES/DIS burst, FS or SS). For convenience, some additional parameters are included to augment those most commonly found in a moments product of this sort, plus timestamps and other annotation characterizing the state of the instrument system at the indicated time.
See FPI Version Release Notes (https://lasp.colorado.edu/mms/sdc/public/datasets/fpi/) for data set modification history.
Value of zero signifies no quality errors. For nonzero values: Bit0 = manually flagged interval, Bit1 = overcounting/saturation effects likely present in skymap, Bit2 = reported spacecraft potential above 20V, Bit3 = invalid/unavailable spacecraft potential, Bit4 = significant (>25%) cold plasma (<10eV) component, Bit5 = significant (>25%) hot plasma (>30keV) component, Bit6 = high sonic Mach number (v/vth > 2.5), Bit7 = low calculated density (n_DES < 0.05 cm^3), Bit8 = bentPipe magnetic field used instead of brst l2pre magnetic field, Bit9 = srvy l2pre magnetic field used instead of brst l2pre magnetic field, Bit10 = no internally generated photoelectron correction applied
FPI/DES compression loss indicator, 0=lossless, 1=lossy
Nominally, spinphase counts range over [0000, 5759] cnts. Each count represents 1/16 deg of observatory spinphase. Zero spinphase count indicates obs +Xaxis aligned with Sun.
Nominally, spinphase angles range over [0, 360) deg. Each count represents 1/16 deg of observatory spinphase. Zero spinphase angle indicates obs +Xaxis aligned with Sun.
low energy bin: 0 eV  200 eV. pitchangle bin size: 6 deg.
mid energy bin: 200 eV  2 keV. pitchangle bin size: 6 deg.
high energy bin: 2 keV  30 keV. pitchangle bin size: 6 deg.
Counts, summed over DSC velocitydirs closest to +X_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to X_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to +Y_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to Y_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to +Z_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to Z_DSC, by energy bin.
Counts, summed within 30 degrees parallel bentPipe magnetic field.
Counts, summed within 30 degrees antiparallel to bentPipe magnetic field.
Counts, summed within 60 degrees perpendicular to bentPipe magnetic field.
Differential energy flux, averaged (weighted by solid angle) over all look directions, by energy bin.
Estimated systematic error (positive or negative) in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding. This can be subtracted from bulk velocity to obtain the corrected velocity vector.
Estimated systematic error (positive or negative) in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding. This can be subtracted from bulk velocity to obtain the corrected velocity vector.
Estimated error in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding
Estimated error in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
FPI usually operates in Fast Survey (FS) Mode in the MMS Region Of Interest (ROI) for the current Mission Phase. Data are taken at burst (30/150 ms for DES/DIS) resolution in this mode. Data are also made available at survey (4.5 s) resolution. Per mission design, not all burstresolution data are downlinked, but all survey data are downlinked. Planning around calibration activities, avoidance of Earth radiation belts, etc, when possible, FPI usually operates in Slow Survey (SS) Mode (60 s resolution) outside of ROI. This product contains partial moments that come from performing the standard moment integrals over a limited portion of velocity space. The resulting quantities are named similarly to their corresponding standard moments, but are decorated with 'part' to differentiate. For example, density_part is the density moment integrated from a particular energy step to infinity. These partial moments are formed from the indicated data type (DES/DIS burst, FS or SS). For convenience, some additional parameters are included to augment those most commonly found in a moments product of this sort, plus timestamps and other annotation characterizing the state of the instrument system at the indicated time.
See FPI Version Release Notes (https://lasp.colorado.edu/mms/sdc/public/datasets/fpi/) for data set modification history.
Value of zero signifies no quality errors. For nonzero values: Bit0 = manually flagged interval, Bit1 = overcounting/saturation effects likely present in skymap, Bit2 = reported spacecraft potential above 20V, Bit3 = invalid/unavailable spacecraft potential, Bit4 = significant (>10%) cold plasma (<10eV) component, Bit5 = significant (>25%) hot plasma (>30keV) component, Bit6 = high sonic Mach number (v/vth > 2.5), Bit7 = low calculated density (n_DES < 0.05 cm^3), Bit8 = bentPipe magnetic field used instead of srvy l2pre magnetic field, Bit10 = no internally generated photoelectron correction applied, Bit11 = compression pipeline error, Bit12 = spintone calculation error (DBCS only)
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
Recommended energy index during this survey
FPI usually operates in Fast Survey Mode in the MMS Region Of Interest (ROI) for the current Mission Phase. Data taken at burst (30/150 ms for DES/DIS) resolution are aggregated on board and made available at survey (4.5 s) resolution in this mode. This product contains phasespace distribution maps of results from surveying the highresolution observations during each 4.5 s period. In particular, the (highest possible quality at the time of release) corrected/converted "Fast Survey SkyMap" distributions are reported with timestamps and other annotation characterizing the state of the instrument system at the indicated time.
See FPI Version Release Notes (https://lasp.colorado.edu/mms/sdc/public/datasets/fpi/) for data set modification history.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Value of zero signifies no quality errors. For nonzero values: Bit0 = manually flagged interval, Bit1 = overcounting/saturation effects likely present in skymap
FPI/DIS compression loss indicator, 0=lossless, 1=lossy
Nominally, spinphase counts range over [0000, 5759] cnts. Each count represents 1/16 deg of observatory spinphase. Zero spinphase count indicates obs +Xaxis aligned with Sun.
Nominally, spinphase angles range over [0, 360) deg. Each count represents 1/16 deg of observatory spinphase. Zero spinphase angle indicates obs +Xaxis aligned with Sun.
FPI usually operates in Fast Survey (FS) Mode in the MMS Region Of Interest (ROI) for the current Mission Phase. Data are taken at burst (30/150 ms for DES/DIS) resolution in this mode. Data are also made available at survey (4.5 s) resolution. Per mission design, not all burstresolution data are downlinked, but all survey data are downlinked. Planning around calibration activities, avoidance of Earth radiation belts, etc, when possible, FPI usually operates in Slow Survey (SS) Mode (60 s resolution) outside of ROI. This moments product contains results from integrating the standard moments of phasespace distributions formed from the indicated data type (DES/DIS burst, FS or SS). For convenience, some additional parameters are included to augment those most commonly found in a moments product of this sort, plus timestamps and other annotation characterizing the state of the instrument system at the indicated time.
See FPI Version Release Notes (https://lasp.colorado.edu/mms/sdc/public/datasets/fpi/) for data set modification history.
Value of zero signifies no quality errors. For nonzero values: Bit0 = manually flagged interval, Bit1 = overcounting/saturation effects likely present in skymap, Bit2 = reported spacecraft potential above 20V, Bit3 = invalid/unavailable spacecraft potential, Bit4 = significant (>25%) cold plasma (<10eV) component, Bit5 = significant (>25%) hot plasma (>30keV) component, Bit6 = high sonic Mach number (v/vth > 2.5), Bit7 = low calculated density (n_DIS < 0.05 cm^3), Bit8 = bentPipe magnetic field used instead of brst l2pre magnetic field, Bit9 = srvy l2pre magnetic field used instead of brst l2pre magnetic field, Bit10 = no internally generated photoelectron correction applied
FPI/DIS compression loss indicator, 0=lossless, 1=lossy
Nominally, spinphase counts range over [0000, 5759] cnts. Each count represents 1/16 deg of observatory spinphase. Zero spinphase count indicates obs +Xaxis aligned with Sun.
Nominally, spinphase angles range over [0, 360) deg. Each count represents 1/16 deg of observatory spinphase. Zero spinphase angle indicates obs +Xaxis aligned with Sun.
Counts, summed over DSC velocitydirs closest to +X_DSC, by energy bin.
Differential energy flux, averaged (weighted by solid angle) over DBCS velocitydirs with 45deg <= theta < 135deg and 135deg <= phi < 225deg, by energy bin.
Counts, summed over DSC velocitydirs closest to +Y_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to Y_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to +Z_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to Z_DSC, by energy bin.
Differential energy flux, averaged (weighted by solid angle) over all look directions, by energy bin.
Background differential energy flux by energy bin, averaged (weighted by solid angle) over all directions (flow or look).
Background number density derived via integration of the estimated background differential energy flux.
Estimated systematic error (positive or negative) in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding. This can be subtracted from bulk velocity to obtain the corrected velocity vector.
Estimated systematic error (positive or negative) in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding. This can be subtracted from bulk velocity to obtain the corrected velocity vector.
Estimated error in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding
Estimated error in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
FPI usually operates in Fast Survey (FS) Mode in the MMS Region Of Interest (ROI) for the current Mission Phase. Data are taken at burst (30/150 ms for DES/DIS) resolution in this mode. Data are also made available at survey (4.5 s) resolution. Per mission design, not all burstresolution data are downlinked, but all survey data are downlinked. Planning around calibration activities, avoidance of Earth radiation belts, etc, when possible, FPI usually operates in Slow Survey (SS) Mode (60 s resolution) outside of ROI. This product contains partial moments that come from performing the standard moment integrals over a limited portion of velocity space. The resulting quantities are named similarly to their corresponding standard moments, but are decorated with 'part' to differentiate. For example, density_part is the density moment integrated from a particular energy step to infinity. These partial moments are formed from the indicated data type (DES/DIS burst, FS or SS). For convenience, some additional parameters are included to augment those most commonly found in a moments product of this sort, plus timestamps and other annotation characterizing the state of the instrument system at the indicated time.
See FPI Version Release Notes (https://lasp.colorado.edu/mms/sdc/public/datasets/fpi/) for data set modification history.
Value of zero signifies no quality errors. For nonzero values: Bit0 = manually flagged interval, Bit1 = overcounting/saturation effects likely present in skymap, Bit2 = reported spacecraft potential above 20V, Bit3 = invalid/unavailable spacecraft potential, Bit4 = significant (>10%) cold plasma (<10eV) component, Bit5 = significant (>25%) hot plasma (>30keV) component, Bit6 = high sonic Mach number (v/vth > 2.5), Bit7 = low calculated density (n_DIS <= 0.0 cm^3), Bit8 = bentPipe magnetic field used instead of srvy l2pre magnetic field, Bit10 = no internally generated photoelectron correction applied, Bit11 = compression pipeline error, Bit12 = spintone calculation error (DBCS only), Bit13 = significant (>=20%) penetrating radiation
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
Recommended energy index during this survey
References
Initial Public Release
References
Initial Public Release
References
Initial Public Release
References
Initial Public Release
MMS MEC Magnetic ephemeris and coordinates, Level 2 science data. PI institution is Los Alamos National Laboratory (LANL)
MMS MEC Magnetic ephemeris and coordinates, Level 2 science data. PI institution is Los Alamos National Laboratory (LANL)
MMS MEC Magnetic ephemeris and coordinates, Level 2 science data. PI institution is Los Alamos National Laboratory (LANL)
MMS MEC Magnetic ephemeris and coordinates, Level 2 science data. PI institution is Los Alamos National Laboratory (LANL)
MMS MEC Magnetic ephemeris and coordinates, Level 2 science data. PI institution is Los Alamos National Laboratory (LANL)
MMS MEC Magnetic ephemeris and coordinates, Level 2 science data. PI institution is Los Alamos National Laboratory (LANL)
The triaxial searchcoil magnetometer (SCM) with its associated preamplifier provides the threedimensional measurement of the magnetic field fluctuations. The analog magnetic waveforms measured by the SCM are digitized and processed inside the digital signal processor (DSP), collected and stored by the central instrument data processor (CIDP) via the Fields central electronics box (CEB). Prior to launch, all SCM Flight models were calibrated by LPP at the National Magnetic Observatory at ChambonlaForet (Orleans). Once per orbit, each SCM transfer function is checked thanks to the onboard calibration signal provided by DSP. SCM is operated for the entire MMS orbit in survey mode. Within the ROI, burst mode data are also acquired as well as high burst mode data. SCM data set corresponds to the AC magnetic field waveforms in nanoTesla and in the GSE frame. The instrument paper for SCM can be found at https://urldefense.proofpoint.com/v2/url?u=http3A__link.springer.com_article_10 .1007_s112142D0142D00962D9&d=DwIFAg&c=c6MrceVCY5m5A_KAUkrdoA&r=bjziExGTRYoZgE 2xb_dDSm9NxNIo0lG6QrB0Y6rHS4&m=CMzo0Vv9zPtWSdbdY1Wq9jIkYS2cOMV9JYZsMV10y0&s=Xb P9PiEAswHGl5lqgsDVI6zs8ivJx7yek9i2undKl10&e=
unpack telemetry, assign sample times 20200712T14:20:04.00004088878319Z  [L1A>L1B (step 1/1)] Calibration (TMcounts>nT). See CALIBRATION_PARAMETERS for details. 20200724T17:40:56.00004941224746Z  [L1B>L2 (step 1/2)] Coordinate transform (SCM123>GSE). See COORD_TRANS_PARAMETERS for details. 20200724T17:41:09.00005936622305Z  [L1B>L2 (step 2/2)] Frequency filtering. See FREQUENCY_FILTER for details.
These calibrated (nT) AC magnetic field waveform data are sampled at 8192S/s. They are highpass filtered above 1.00Hz but not lowpass filtered. See global attributes for details. For more information, please have a look at the SCM Data Products Guide.
Each letter refers to one SCM physical antenna in the SCM123 order. 'G' stands for good data, 'Z' for data that are affected or set to zero by convolution boundary effect, 'S' for saturated data, 'X' for out of range data, 'B' for fillvalue/bad data.
The triaxial searchcoil magnetometer (SCM) with its associated preamplifier provides the threedimensional measurement of the magnetic field fluctuations. The analog magnetic waveforms measured by the SCM are digitized and processed inside the digital signal processor (DSP), collected and stored by the central instrument data processor (CIDP) via the Fields central electronics box (CEB). Prior to launch, all SCM Flight models were calibrated by LPP at the National Magnetic Observatory at ChambonlaForet (Orleans). Once per orbit, each SCM transfer function is checked thanks to the onboard calibration signal provided by DSP. SCM is operated for the entire MMS orbit in survey mode. Within the ROI, burst mode data are also acquired as well as high burst mode data. SCM data set corresponds to the AC magnetic field waveforms in nanoTesla and in the GSE frame. The instrument paper for SCM can be found at https://urldefense.proofpoint.com/v2/url?u=http3A__link.springer.com_article_10 .1007_s112142D0142D00962D9&d=DwIFAg&c=c6MrceVCY5m5A_KAUkrdoA&r=bjziExGTRYoZgE 2xb_dDSm9NxNIo0lG6QrB0Y6rHS4&m=CMzo0Vv9zPtWSdbdY1Wq9jIkYS2cOMV9JYZsMV10y0&s=Xb P9PiEAswHGl5lqgsDVI6zs8ivJx7yek9i2undKl10&e=
unpack telemetry, assign sample times 20200712T14:23:45.00004917382885Z  [L1A>L1B (step 1/1)] Calibration (TMcounts>nT). See CALIBRATION_PARAMETERS for details. 20200724T17:46:53.00004422664344Z  [L1B>L2 (step 1/2)] Coordinate transform (SCM123>GSE). See COORD_TRANS_PARAMETERS for details. 20200724T17:47:02.00003564357421Z  [L1B>L2 (step 2/2)] Frequency filtering. See FREQUENCY_FILTER for details.
These calibrated (nT) AC magnetic field waveform data are sampled at 16384S/s. They are highpass filtered above 32.00Hz but not lowpass filtered. See global attributes for details. For more information, please have a look at the SCM Data Products Guide (https://lasp.colorado.edu/mms/sdc/public/datasets/fields/Science_Data_Products_ Guide_vol2_SCM_v11_20160301.pdf).
The triaxial searchcoil magnetometer (SCM) with its associated preamplifier provides the threedimensional measurement of the magnetic field fluctuations. The analog magnetic waveforms measured by the SCM are digitized and processed inside the digital signal processor (DSP), collected and stored by the central instrument data processor (CIDP) via the Fields central electronics box (CEB). Prior to launch, all SCM Flight models were calibrated by LPP at the National Magnetic Observatory at ChambonlaForet (Orleans). Once per orbit, each SCM transfer function is checked thanks to the onboard calibration signal provided by DSP. SCM is operated for the entire MMS orbit in survey mode. Within the ROI, burst mode data are also acquired as well as high burst mode data. SCM data set corresponds to the AC magnetic field waveforms in nanoTesla and in the GSE frame. The instrument paper for SCM can be found at https://urldefense.proofpoint.com/v2/url?u=http3A__link.springer.com_article_10 .1007_s112142D0142D00962D9&d=DwIFAg&c=c6MrceVCY5m5A_KAUkrdoA&r=bjziExGTRYoZgE 2xb_dDSm9NxNIo0lG6QrB0Y6rHS4&m=CMzo0Vv9zPtWSdbdY1Wq9jIkYS2cOMV9JYZsMV10y0&s=Xb P9PiEAswHGl5lqgsDVI6zs8ivJx7yek9i2undKl10&e=
unpack telemetry, assign sample times 20200710T00:01:29.00004029273986Z  [L1A>L1B (step 1/1)] Calibration (TMcounts>nT). See CALIBRATION_PARAMETERS for details. 20200723T00:02:46.00006520748138Z  [L1B>L2 (step 1/2)] Coordinate transform (SCM123>GSE). See COORD_TRANS_PARAMETERS for details. 20200723T00:05:47.00004905462266Z  [L1B>L2 (step 2/2)] Frequency filtering. See FREQUENCY_FILTER for details.
These calibrated (nT) AC magnetic field waveform data are sampled at 32S/s. They are highpass filtered above 0.50Hz but not lowpass filtered. See global attributes for details. For more information, please have a look at the SCM Data Products Guide.
Each letter refers to one SCM physical antenna in the SCM123 order. 'G' stands for good data, 'Z' for data that are affected or set to zero by convolution boundary effect, 'S' for saturated data, 'X' for out of range data, 'B' for fillvalue/bad data.
K. Torkar et al, Active Spacecraft Potential Control Investigation Space Science Reviews, 2014, DOI: 10.1007/s1121401400493 Further information:  http://www.iwf.oeaw.ac.at/en/research/nearearthspace/mms/  http://mms.space.swri.edu/
150224 Initial version 150831 Minor updates and fixes 160205 CDF file format guide compliant
Calibrated magneticspectral density computed by onboard FFTs by the Digital Signal Processor (DSP) from the Search Coil Magnetometer (SCM) in the SCM123 coordinate system (scm1 =  x sensor; scm2 = z sensor; scm3 = y sensor). This product is computed in space from individual components that are not synchronized to the 1 second pulse. Therefore, the timing between channels can be inaccurate by a fraction of a second. The samples times are interval start times taken from the x component.
electric spectral density
search coil magnetometer spectral density
electric spectral density
EDI ambient data. The EDI instrument paper and data products guide can be found at the following two links: http://link.springer.com/article/10.1007%2Fs1121401501827, https://lasp.colorado.edu/mms/sdc/public/datasets/fields/
v0.0.0  Original version. v1.0.0  Include trajectory vectors and optics state. v1.1.0  Update metadata: counts > flux. v1.2.0  Added flux error. v1.3.0  Trajectory vector errors are now deltas. v1.4.0  Fixed deadtime correction and error values. v1.5.0  Factor of 2 for accumulation time & 2 for abscal factor in srvy mode. v1.6.0  No factor of 2 for accumulation time in srvy mode. v2.0.0  Reduced file size with scalar errors. Update metadata. v2.1.0  Correct fill value for fluxes. v3.0.0  Omnidirectional error for trajectories. YVersion linked to cal file. Single epoch for counts. v4.0.0  Replace data in GSM coordinates with data in DBCS to be consistent with other particle instruments.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
EDI ambient data. The EDI instrument paper and data products guide can be found at the following two links: http://link.springer.com/article/10.1007%2Fs1121401501827, https://lasp.colorado.edu/mms/sdc/public/datasets/fields/
v1.0.0  Original version. v1.1.0  Correct fill value for fluxes. v2.0.0  Omnidirectional error for trajectories. YVersion linked to cal file. Single epoch for counts. v3.0.0  Replace data in GSM coordinates with data in DBCS to be consistent with other particle instruments.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
EDI electric field data. Instrument papers for EDI can be found at: http://link.springer.com/article/10.1007%2Fs1121401501827
v1.0.0  First version. TRITOF selection based on smallest error. v1.1.0  TRITOF merged by weighted average. v1.2.0  Fixed t_delta_plus/minus CDF_type. v1.3.0  Fixed Fixed vdrift SI conversion. v1.4.0  Fixed data duplication caused by multiple l2pre file locations. v1.5.0  Inplemented baseline*beams*Bmag filter for triangulation. v1.6.0  Inplemented null files for no or low quality data.
EDI Q0 data. The EDI instrument paper and data products guidescan be found at the following two links: http://link.springer.com/article/10.1007%2Fs1121401501827, https://lasp.colorado.edu/mms/sdc/public/datasets/fields/
v0.0.0  First version. v0.0.1  Filled energy variables. v0.0.2  Energy written properly. v1.0.0  Update variable names. v1.1.0  Added optics state. v2.0.0  Added electron trajectories. v2.1.0  Deltas on trajectory vectors are now deltas. v3.0.0  Reduced file size with scalar errors. Add VAR_NOTES. v3.1.0  Fixed optics datatype. v4.0.0  Removed unused Epoch variable. v5.0.0  Trajectories are provided in DBCS coordinates.
Q0 data consists of raw electron counts. The error at any one time is the squareroot of the counts. Note that there may be contamination from the EDI electron beams. See the data products guide or contact an EDI team member to learn about beam contamination.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
EDI ambient data. The EDI instrument paper and data products guide can be found at the following two links: http://link.springer.com/article/10.1007%2Fs1121401501827, https://lasp.colorado.edu/mms/sdc/public/datasets/fields/
v0.0.0  Original version. v1.0.0  Include trajectory vectors and optics state. v1.1.0  Update metadata: counts > flux. v1.2.0  Added flux error. v1.3.0  Trajectory vector errors are now deltas. v1.4.0  Fixed deadtime correction and error values. v1.5.0  Factor of 2 for accumulation time & 2 for abscal factor in srvy mode. v1.6.0  No factor of 2 for accumulation time in srvy mode. v2.0.0  Reduced file size with scalar errors. Update metadata. v2.1.0  Correct fill value for fluxes. v3.0.0  Omnidirectional error for trajectories. Correct time deltas. YVersion linked to cal file. Single epoch for counts. v4.0.0  Replace data in GSM coordinates with data in DBCS to be consistent with other particle instruments.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
EDI ambient data. The EDI instrument paper and data products guide can be found at the following two links: http://link.springer.com/article/10.1007%2Fs1121401501827, https://lasp.colorado.edu/mms/sdc/public/datasets/fields/
v1.0.0  Original version. v1.1.0  Correct fill value for fluxes. v2.0.0  Omnidirectional error for trajectories. YVersion linked to cal file. Single epoch for counts. v3.0.0  Replace data in GSM coordinates with data in DBCS to be consistent with other particle instruments. v4.0.0  Each trajectory has its own LABL_PTR_1 variable.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
EDI electric field data. Instrument papers for EDI can be found at: http://link.springer.com/article/10.1007%2Fs1121401501827
v1.0.0  First version. TRITOF selection based on smallest error. v1.1.0  TRITOF merged by weighted average. v1.2.0  Fixed t_delta_plus/minus CDF_type. v1.3.0  Fixed Fixed vdrift SI conversion. v1.4.0  Fixed data duplication caused by multiple l2pre file locations. v1.5.0  Inplemented baseline*beams*Bmag filter for triangulation. v1.6.0  Inplemented null files for no or low quality data.
EDI Q0 data. The EDI instrument paper and data products guidescan be found at the following two links: http://link.springer.com/article/10.1007%2Fs1121401501827, https://lasp.colorado.edu/mms/sdc/public/datasets/fields/
v0.0.0  First version. v0.0.1  Filled energy variables. v0.0.2  Energy written properly. v1.0.0  Update variable names. v1.1.0  Added optics state. v2.0.0  Added electron trajectories. v2.1.0  Deltas on trajectory vectors are now deltas. v3.0.0  Reduced file size with scalar errors. Add VAR_NOTES. v4.0.0  Removed unused Epoch variable. v5.0.0  Trajectories are provided in DBCS coordinates.
Q0 data consists of raw electron counts. The error at any one time is the squareroot of the counts. Note that there may be contamination from the EDI electron beams. See the data products guide or contact an EDI team member to learn about beam contamination.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
https://mms.gsfc.nasa.gov/ For detailed timing information, such as needed for cross spectral analysis, please consult the EDP Data Products Guide.
V.0. Initial release.
L1B AC Electric Field
https://mms.gsfc.nasa.gov/ The full name of PI affiliations: SWRI  Southwest Research Institute. LASP  Laboratory for Atmospheric and Space Physics. KTH  Kungliga Tekniska Hogskolan (Swedish Royal Institute of Technology). For detailed timing information, such as needed for cross spectral analysis, please consult the EDP Data Products Guide.
V.0. Initial release. V.1. QL (v1.0.z), SCPOT (v1.0.z), L2A (v0.1.z) now uses ASPOC srvy l2 and DEFATT, if these are available. Brst QL uses intermediate L2A file from Fast mode for delta offsets. Bitmask changed to uint16 and Quality to uint8. V.2. SCPOT (v2.0.z), L2A (v1.0.z) now uses variable names in accordance with new recommended standard for FIELDS, All products change shortening factor to 1.25 on SDP, offsets applied indicated by GlobalAttribute Calibration_file. V.2. L2a (v2.0.z), QL (v1.6.z) now try to remove solar wind wake which previously left a clear sinusodial signal in the data. V.3. L2a (v3.0.z) Slow Mode probe Gain set to 1.0 when orbital radius less than 5 RE (1.25 otherwise), L2pre (v2.0.z) DSL offsets removed from field is now included in the file as the Slow mode is dependent on scpot product (Fast/Brst is simply based on offset in Calibration_file).
https://mms.gsfc.nasa.gov/ For detailed timing information, such as needed for cross spectral analysis, please consult the EDP Data Products Guide.
V.0. Initial release.
https://mms.gsfc.nasa.gov/ The full name of PI affiliations: SWRI  Southwest Research Institute. LASP  Laboratory for Atmospheric and Space Physics. KTH  Kungliga Tekniska Hogskolan (Swedish Royal Institute of Technology). For detailed timing information, such as needed for cross spectral analysis, please consult the EDP Data Products Guide.
V.0. Initial release. V.1. QL (v1.0.z), SCPOT (v1.0.z), L2A (v0.1.z) now uses ASPOC srvy l2 and DEFATT, if these are available. Brst QL uses intermediate L2A file from Fast mode for delta offsets. Bitmask changed to uint16 and Quality to uint8. V.2. SCPOT (v2.0.z), L2A (v1.0.z) now uses variable names in accordance with new recommended standard for FIELDS, All products change shortening factor to 1.25 on SDP, offsets applied indicated by GlobalAttribute Calibration_file. V.2. L2a (v2.0.z), QL (v1.6.z) now try to remove solar wind wake which previously left a clear sinusodial signal in the data. V.3. L2a (v3.0.z) Slow Mode probe Gain set to 1.0 when orbital radius less than 5 RE (1.25 otherwise), L2pre (v2.0.z) DSL offsets removed from field is now included in the file as the Slow mode is dependent on scpot product (Fast/Brst is simply based on offset in Calibration_file).
https://mms.gsfc.nasa.gov/ For detailed timing information, such as needed for cross spectral analysis, please consult the EDP Data Products Guide.
V.0. Initial release.
https://mms.gsfc.nasa.gov/ The full name of PI affiliations: SWRI  Southwest Research Institute. LASP  Laboratory for Atmospheric and Space Physics. KTH  Kungliga Tekniska Hogskolan (Swedish Royal Institute of Technology). For detailed timing information, such as needed for cross spectral analysis, please consult the EDP Data Products Guide.
V.0. Initial release. V.1. QL (v1.0.z), SCPOT (v1.0.z), L2A (v0.1.z) now uses ASPOC srvy l2 and DEFATT, if these are available. Brst QL uses intermediate L2A file from Fast mode for delta offsets. Bitmask changed to uint16 and Quality to uint8. V.2. SCPOT (v2.0.z), L2A (v1.0.z) now uses variable names in accordance with new recommended standard for FIELDS, All products change shortening factor to 1.25 on SDP, offsets applied indicated by GlobalAttribute Calibration_file. V.2. L2a (v2.0.z), QL (v1.6.z) now try to remove solar wind wake which previously left a clear sinusodial signal in the data. V.3. L2a (v3.0.z) Slow Mode probe Gain set to 1.0 when orbital radius less than 5 RE (1.25 otherwise), L2pre (v2.0.z) DSL offsets removed from field is now included in the file as the Slow mode is dependent on scpot product (Fast/Brst is simply based on offset in Calibration_file).
L1B AC Electric Field
empty
Constantly modifying this code
empty
Constantly modifying this code
empty
Constantly modifying this code
empty
Constantly modifying this code
empty
Constantly modifying this code
http://www.lasp.colorado.edu
Generated at LASP
http://www.lasp.colorado.edu
Generated at LASP
http://www.lasp.colorado.edu
Generated at LASP
http://www.lasp.colorado.edu
Generated at LASP
The Fluxgate Magnetometers (FGM) on Magnetospheric Multiscale consist of a traditional Analog Fluxgate Magnetometer (AFG), and a Digital Fluxgate magnetometer (DFG). The dual magnetometers are operated as a single instrument providing a single intercalibrated data product. Range changes occur at different times on the two instruments so the gains checked each periapsis can be carried out unambiguously to apoapsis. Cross correlation of calibration parameters can separate causes of the any apparent calibration changes. Use of Electron Drift Instrument (EDI) to determine the field along the rotation axis allows accurate monitoring of the zero levels along the rotation axis. Prior to launch the magnetometers were calibrated at the Technical University, Braunschweig, except for the AFG magnetometers on MMS3 and MMS4, which were calibrated at UCLA. Both sets of sensors are operated for the entire MMS orbit, with slow survey (8 samples per second) outside of the Region of Interest (ROI), and fast survey (16 samples per second) inside the ROI. Within the ROI burst mode data (128 samples per second) are also acquired. A detailed description of the MMS fluxgate magnetometers, including science objectives, instrument description, calibration, magnetic cleanliness program, and data flow can be found at http://link.springer.com/article/10.1007%2Fs1121401400573 (DOI 10.1007/s1121401400573).Additional information can also be found at http://wwwspc.igpp.ucla.edu/ssc/mms (UCLA),and http://www.iwf.oeaw.ac.at (IWF, Graz). For the purpose of creating a unified FGM Level2 data product, burst mode data is taken from DFG and survey mode data is taken from AFG. Because AFG and DFG are crosscalibrated on an orbitaveraged basis, small differences in offset may be observed between Level2 burst and survey mode data. Consequently, any differences are within the error of the measurement. Based on preliminary analysis of the data, the absolute error within the Region of Interest (ROI) is estimated to be no more than 0.1 nT in the spinplane, 0.15 nT along the spinaxis and 0.2 nT in total magnitude.
version X=5: * Yversion number comes from cal file entries. * Ensures there are 2 ephemeris points before/after data to enable proper spline. * Fix to depend_0 of rdeltahalf: fixes bug when reading position data. * Lvector for DMPA2GSE transformation is smoothed with a gaussian filter, instead of using a single average value for the day. This shortterm filter avoids introduding artificial jumps at 00:00 UTC and removes 7minute 'wobble' after maneuvers in the GSE result. * Fixes error with DEFATT file selection found when choosing the daily DEFATT files to be used in Phase 2. * Fixed bug where reference Etemp was used for high range gain. Now uses measured Etemp. version X=4: First version for public release of L2. Renamed variables to conform with new MMS variable name guidelines (obs_instr_paramName[_coordSys]_mode_level): Mag field parameters include 'b' for paramName. Use 'r' instead of 'pos' for S/C position paramName. Eliminated 'rate', replaced with 'bdeltahalf'. Added 'rdeltahalf'. l1a_mode is now just 'mode'. version X=3: fixed removal of overlap between modes. fixed a bug that caused stemp and etemp to be empty. version X=2: flag parameter name corrected: was 'status' added bits 4, 5, 6 to flag saturation on B1, B2, and B3, respectively added bit 7 to flag bad data at range changes Added etemp and l1a_mode parameters. rate, hirange, and stemp parameters now comply with MMS CDF Guidlelines, e.g. FILLVAL now defined for stemp and etemp, and is set to !values.f_nan No longer use Var_Parents attribute in stemp  see Parents instead In this version, temperaturecorrected gains are applied. Reference temperatures are used when stemp or etemp are set to FILLVAL. Nonlinearity correction is applied to high rage DFG data. version X=1: added 'flag', rate and hirange parameters (but 'flag' is actually called 'status')
During nominal operatins in the region of interest, DMPA is within 3 degrees of GSE.
During nominal operatins in the region of interest, DMPA is within 3 degrees of GSE.
bit definitions: . 0: TBD, 1: TBD, 2: user flagged, 3: TBD, . 4: B1 saturated, 5: B2 saturated, 6: B3 saturated, 7: rangechange glitch, . 831: TBD
The Fluxgate Magnetometers (FGM) on Magnetospheric Multiscale consist of a traditional Analog Fluxgate Magnetometer (AFG), and a Digital Fluxgate magnetometer (DFG). The dual magnetometers are operated as a single instrument providing a single intercalibrated data product. Range changes occur at different times on the two instruments so the gains checked each periapsis can be carried out unambiguously to apoapsis. Cross correlation of calibration parameters can separate causes of the any apparent calibration changes. Use of Electron Drift Instrument (EDI) to determine the field along the rotation axis allows accurate monitoring of the zero levels along the rotation axis. Prior to launch the magnetometers were calibrated at the Technical University, Braunschweig, except for the AFG magnetometers on MMS3 and MMS4, which were calibrated at UCLA. Both sets of sensors are operated for the entire MMS orbit, with slow survey (8 samples per second) outside of the Region of Interest (ROI), and fast survey (16 samples per second) inside the ROI. Within the ROI burst mode data (128 samples per second) are also acquired. A detailed description of the MMS fluxgate magnetometers, including science objectives, instrument description, calibration, magnetic cleanliness program, and data flow can be found at http://link.springer.com/article/10.1007%2Fs1121401400573 (DOI 10.1007/s1121401400573).Additional information can also be found at http://wwwspc.igpp.ucla.edu/ssc/mms (UCLA),and http://www.iwf.oeaw.ac.at (IWF, Graz). For the purpose of creating a unified FGM Level2 data product, burst mode data is taken from DFG and survey mode data is taken from AFG. Because AFG and DFG are crosscalibrated on an orbitaveraged basis, small differences in offset may be observed between Level2 burst and survey mode data. Consequently, any differences are within the error of the measurement. Based on preliminary analysis of the data, the absolute error within the Region of Interest (ROI) is estimated to be no more than 0.1 nT in the spinplane, 0.15 nT along the spinaxis and 0.2 nT in total magnitude.
version X=5: * Yversion number comes from cal file entries. * Ensures there are 2 ephemeris points before/after data to enable proper spline. * Fix to depend_0 of rdeltahalf: fixes bug when reading position data. * Lvector for DMPA2GSE transformation is smoothed with a gaussian filter, instead of using a single average value for the day. This shortterm filter avoids introduding artificial jumps at 00:00 UTC and removes 7minute 'wobble' after maneuvers in the GSE result. * Fixes error with DEFATT file selection found when choosing the daily DEFATT files to be used in Phase 2. * Fixed bug where reference Etemp was used for high range gain. Now uses measured Etemp. version X=4: First version for public release of L2. Renamed variables to conform with new MMS variable name guidelines (obs_instr_paramName[_coordSys]_mode_level): Mag field parameters include 'b' for paramName. Use 'r' instead of 'pos' for S/C position paramName. Eliminated 'rate', replaced with 'bdeltahalf'. Added 'rdeltahalf'. l1a_mode is now just 'mode'. version X=3: fixed removal of overlap between modes. fixed a bug that caused stemp and etemp to be empty. version X=2: flag parameter name corrected: was 'status' added bits 4, 5, 6 to flag saturation on B1, B2, and B3, respectively added bit 7 to flag bad data at range changes Added etemp and l1a_mode parameters. rate, hirange, and stemp parameters now comply with MMS CDF Guidlelines, e.g. FILLVAL now defined for stemp and etemp, and is set to !values.f_nan No longer use Var_Parents attribute in stemp  see Parents instead In this version, temperaturecorrected gains are applied. Reference temperatures are used when stemp or etemp are set to FILLVAL. Nonlinearity correction is applied to high rage DFG data. version X=1: added 'flag', rate and hirange parameters (but 'flag' is actually called 'status')
During nominal operatins in the region of interest, DMPA is within 3 degrees of GSE.
During nominal operatins in the region of interest, DMPA is within 3 degrees of GSE.
bit definitions: . 0: TBD, 1: TBD, 2: user flagged, 3: TBD, . 4: B1 saturated, 5: B2 saturated, 6: B3 saturated, 7: rangechange glitch, . 831: TBD
FPI usually operates in Fast Survey Mode in the MMS Region Of Interest (ROI) for the current Mission Phase. Data are taken at burst (30/150 ms for DES/DIS) resolution in this mode. Data are also made available at survey (4.5 s, etc) resolution; these form a separate product from this. Per mission design, not all burstresolution data are downlinked. This product contains phasespace distribution maps of those burstresolution data selected for downlink. In particular, the (highest possible quality at the time of release) corrected/converted "Burst SkyMap" distributions are reported with timestamps and other annotation characterizing the state of the instrument system at the indicated time.
See FPI Version Release Notes (https://lasp.colorado.edu/mms/sdc/public/datasets/fpi/) for data set modification history.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Value of zero signifies no quality errors. For nonzero values: Bit0 = manually flagged interval, Bit1 = overcounting/saturation effects likely present in skymap
FPI/DES compression loss indicator, 0=lossless, 1=lossy
FPI/DES alternates between two tables, designated "even" (0) and "odd" (1).
Nominally, spinphase counts range over [0000, 5759] cnts. Each count represents 1/16 deg of observatory spinphase. Zero spinphase count indicates obs +Xaxis aligned with Sun.
Nominally, spinphase angles range over [0, 360) deg. Each count represents 1/16 deg of observatory spinphase. Zero spinphase angle indicates obs +Xaxis aligned with Sun.
Records Pvalue used to despin this burst skymap on board. See FPI docs for details.
see FPI docs for details
Energies (parity 0/1) in the 64step FPI energy table
FPI usually operates in Fast Survey (FS) Mode in the MMS Region Of Interest (ROI) for the current Mission Phase. Data are taken at burst (30/150 ms for DES/DIS) resolution in this mode. Data are also made available at survey (4.5 s, etc) resolution. Per mission design, not all burstresolution data are downlinked, but all survey data are downlinked. Planning around calibration activities, avoidance of Earth radiation belts, etc, when possible, FPI usually operates in Slow Survey (SS) Mode outside of ROI, and then only the 60 s resolution survey data are available. This product contains results from integrating the standard moments of phasespace distributions formed from the indicated data type (DES/DIS burst, FS or SS). For convenience, some additional parameters are included to augment those most commonly found in a moments product of this sort, plus timestamps and other annotation characterizing the state of the instrument system at the indicated time.
See FPI Version Release Notes (https://lasp.colorado.edu/mms/sdc/public/datasets/fpi/) for data set modification history.
Value of zero signifies no quality errors. For nonzero values: Bit0 = manually flagged interval, Bit1 = overcounting/saturation effects likely present in skymap, Bit2 = reported spacecraft potential above 20V, Bit3 = invalid/unavailable spacecraft potential, Bit4 = significant (>25%) cold plasma (<10eV) component, Bit5 = significant (>25%) hot plasma (>30keV) component, Bit6 = high sonic Mach number (v/vth > 2.5), Bit7 = low calculated density (n_DES < 0.05 cm^3), Bit8 = bentPipe magnetic field used instead of brst l2pre magnetic field, Bit9 = srvy l2pre magnetic field used instead of brst l2pre magnetic field, Bit10 = no internally generated photoelectron correction applied
FPI/DES compression loss indicator, 0=lossless, 1=lossy
FPI/DES alternates between two tables, designated "even" (0) and "odd" (1).
Nominally, spinphase counts range over [0000, 5759] cnts. Each count represents 1/16 deg of observatory spinphase. Zero spinphase count indicates obs +Xaxis aligned with Sun.
Nominally, spinphase angles range over [0, 360) deg. Each count represents 1/16 deg of observatory spinphase. Zero spinphase angle indicates obs +Xaxis aligned with Sun.
Records Pvalue used to despin this burst skymap on board. See FPI docs for details.
low energy bin: 0 eV  200 eV. pitchangle bin size: 6 deg.
mid energy bin: 200 eV  2 keV. pitchangle bin size: 6 deg.
high energy bin: 2 keV  30 keV. pitchangle bin size: 6 deg.
Counts, summed over DSC velocitydirs closest to +X_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to X_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to +Y_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to Y_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to +Z_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to Z_DSC, by energy bin.
Counts, summed within 30 degrees parallel bentPipe magnetic field.
Counts, summed within 30 degrees antiparallel to bentPipe magnetic field.
Counts, summed within 60 degrees perpendicular to bentPipe magnetic field.
Differential energy flux, averaged (weighted by solid angle) over all look directions, by energy bin.
Estimated systematic error (positive or negative) in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding. This can be subtracted from bulk velocity to obtain the corrected velocity vector.
Estimated systematic error (positive or negative) in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding. This can be subtracted from bulk velocity to obtain the corrected velocity vector.
Estimated error in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding
Estimated error in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
FPI usually operates in Fast Survey (FS) Mode in the MMS Region Of Interest (ROI) for the current Mission Phase. Data are taken at burst (30/150 ms for DES/DIS) resolution in this mode. Data are also made available at survey (4.5 s, etc) resolution. Per mission design, not all burstresolution data are downlinked, but all survey data are downlinked. Planning around calibration activities, avoidance of Earth radiation belts, etc, when possible, FPI usually operates in Slow Survey (SS) Mode outside of ROI, and then only the 60 s resolution survey data are available. This product contains partial moments that come from performing the standard moment integrals over a limited portion of velocity space. The resulting quantities are named similarly to their corresponding standard moments, but are decorated with 'part' to differentiate. For example, density_part is the density moment integrated from a particular energy step to infinity. These partial moments are formed from the indicated data type (DES/DIS burst, FS or SS). For convenience, some additional parameters are included to augment those most commonly found in a moments product of this sort, plus timestamps and other annotation characterizing the state of the instrument system at the indicated time.
See FPI Version Release Notes (https://lasp.colorado.edu/mms/sdc/public/datasets/fpi/) for data set modification history.
Value of zero signifies no quality errors. For nonzero values: Bit0 = manually flagged interval, Bit1 = overcounting/saturation effects likely present in skymap, Bit2 = reported spacecraft potential above 20V, Bit3 = invalid/unavailable spacecraft potential, Bit4 = significant (>10%) cold plasma (<10eV) component, Bit5 = significant (>25%) hot plasma (>30keV) component, Bit6 = high sonic Mach number (v/vth > 2.5), Bit7 = low calculated density (n_DES < 0.05 cm^3), Bit8 = bentPipe magnetic field used instead of brst l2pre magnetic field, Bit9 = srvy l2pre magnetic field used instead of brst l2pre magnetic field, Bit10 = no internally generated photoelectron correction applied, Bit11 = compression pipeline error, Bit12 = spintone calculation error (DBCS only)
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
Recommended energy index during this burst
FPI usually operates in Fast Survey Mode in the MMS Region Of Interest (ROI) for the current Mission Phase. Data are taken at burst (30/150 ms for DES/DIS) resolution in this mode. Data are also made available at survey (4.5 s, etc) resolution; these form a separate product from this. Per mission design, not all burstresolution data are downlinked. This product contains phasespace distribution maps of those burstresolution data selected for downlink. In particular, the (highest possible quality at the time of release) corrected/converted "Burst SkyMap" distributions are reported with timestamps and other annotation characterizing the state of the instrument system at the indicated time.
See FPI Version Release Notes (https://lasp.colorado.edu/mms/sdc/public/datasets/fpi/) for data set modification history.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Value of zero signifies no quality errors. For nonzero values: Bit0 = manually flagged interval, Bit1 = overcounting/saturation effects likely present in skymap
FPI/DIS compression loss indicator, 0=lossless, 1=lossy
FPI/DIS alternates between two tables, designated "even" (0) and "odd" (1).
Nominally, spinphase counts range over [0000, 5759] cnts. Each count represents 1/16 deg of observatory spinphase. Zero spinphase count indicates obs +Xaxis aligned with Sun.
Nominally, spinphase angles range over [0, 360) deg. Each count represents 1/16 deg of observatory spinphase. Zero spinphase angle indicates obs +Xaxis aligned with Sun.
Records Pvalue used to despin this burst skymap on board. See FPI docs for details.
see FPI docs for details
Energies (parity 0/1) in the 64step FPI energy table
FPI usually operates in Fast Survey (FS) Mode in the MMS Region Of Interest (ROI) for the current Mission Phase. Data are taken at burst (30/150 ms for DES/DIS) resolution in this mode. Data are also made available at survey (4.5 s, etc) resolution. Per mission design, not all burstresolution data are downlinked, but all survey data are downlinked. Planning around calibration activities, avoidance of Earth radiation belts, etc, when possible, FPI usually operates in Slow Survey (SS) Mode outside of ROI, and then only the 60 s resolution survey data are available. This product contains results from integrating the standard moments of phasespace distributions formed from the indicated data type (DES/DIS burst, FS or SS). For convenience, some additional parameters are included to augment those most commonly found in a moments product of this sort, plus timestamps and other annotation characterizing the state of the instrument system at the indicated time.
See FPI Version Release Notes (https://lasp.colorado.edu/mms/sdc/public/datasets/fpi/) for data set modification history.
Value of zero signifies no quality errors. For nonzero values: Bit0 = manually flagged interval, Bit1 = overcounting/saturation effects likely present in skymap, Bit2 = reported spacecraft potential above 20V, Bit3 = invalid/unavailable spacecraft potential, Bit4 = significant (>25%) cold plasma (<10eV) component, Bit5 = significant (>25%) hot plasma (>30keV) component, Bit6 = high sonic Mach number (v/vth > 2.5), Bit7 = low calculated density (n_DIS < 0.05 cm^3), Bit8 = bentPipe magnetic field used instead of brst l2pre magnetic field, Bit9 = srvy l2pre magnetic field used instead of brst l2pre magnetic field, Bit10 = no internally generated photoelectron correction applied
FPI/DIS compression loss indicator, 0=lossless, 1=lossy
FPI/DIS alternates between two tables, designated "even" (0) and "odd" (1).
Nominally, spinphase counts range over [0000, 5759] cnts. Each count represents 1/16 deg of observatory spinphase. Zero spinphase count indicates obs +Xaxis aligned with Sun.
Nominally, spinphase angles range over [0, 360) deg. Each count represents 1/16 deg of observatory spinphase. Zero spinphase angle indicates obs +Xaxis aligned with Sun.
Records Pvalue used to despin this burst skymap on board. See FPI docs for details.
Counts, summed over DSC velocitydirs closest to +X_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to X_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to +Y_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to Y_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to +Z_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to Z_DSC, by energy bin.
Differential energy flux, averaged (weighted by solid angle) over all look directions, by energy bin.
Background differential energy flux by energy bin, averaged (weighted by solid angle) over all directions (flow or look) background level.
Background number density derived via integration of the estimated background differential energy flux.
Estimated systematic error (positive or negative) in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding. This can be subtracted from bulk velocity to obtain the corrected velocity vector.
Estimated systematic error (positive or negative) in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding. This can be subtracted from bulk velocity to obtain the corrected velocity vector.
Estimated error in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding
Estimated error in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
FPI usually operates in Fast Survey (FS) Mode in the MMS Region Of Interest (ROI) for the current Mission Phase. Data are taken at burst (30/150 ms for DES/DIS) resolution in this mode. Data are also made available at survey (4.5 s, etc) resolution. Per mission design, not all burstresolution data are downlinked, but all survey data are downlinked. Planning around calibration activities, avoidance of Earth radiation belts, etc, when possible, FPI usually operates in Slow Survey (SS) Mode outside of ROI, and then only the 60 s resolution survey data are available. This product contains partial moments that come from performing the standard moment integrals over a limited portion of velocity space. The resulting quantities are named similarly to their corresponding standard moments, but are decorated with 'part' to differentiate. For example, density_part is the density moment integrated from a particular energy step to infinity. These partial moments are formed from the indicated data type (DES/DIS burst, FS or SS). For convenience, some additional parameters are included to augment those most commonly found in a moments product of this sort, plus timestamps and other annotation characterizing the state of the instrument system at the indicated time.
See FPI Version Release Notes (https://lasp.colorado.edu/mms/sdc/public/datasets/fpi/) for data set modification history.
Value of zero signifies no quality errors. For nonzero values: Bit0 = manually flagged interval, Bit1 = overcounting/saturation effects likely present in skymap, Bit2 = reported spacecraft potential above 20V, Bit3 = invalid/unavailable spacecraft potential, Bit4 = significant (>10%) cold plasma (<10eV) component, Bit5 = significant (>25%) hot plasma (>30keV) component, Bit6 = high sonic Mach number (v/vth > 2.5), Bit7 = low calculated density (n_DIS <= 0.0 cm^3), Bit8 = bentPipe magnetic field used instead of brst l2pre magnetic field, Bit9 = srvy l2pre magnetic field used instead of brst l2pre magnetic field, Bit10 = no internally generated photoelectron correction applied, Bit11 = compression pipeline error, Bit12 = spintone calculation error (DBCS only), Bit13 = significant (>=20%) penetrating radiation
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
Recommended energy index during this burst
FPI usually operates in Fast Survey Mode in the MMS Region Of Interest (ROI) for the current Mission Phase. Data taken at burst (30/150 ms for DES/DIS) resolution are aggregated on board and made available at survey (4.5 s) resolution in this mode. This product contains phasespace distribution maps of results from surveying the highresolution observations during each 4.5 s period. In particular, the (highest possible quality at the time of release) corrected/converted "Fast Survey SkyMap" distributions are reported with timestamps and other annotation characterizing the state of the instrument system at the indicated time.
See FPI Version Release Notes (https://lasp.colorado.edu/mms/sdc/public/datasets/fpi/) for data set modification history.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Value of zero signifies no quality errors. For nonzero values: Bit0 = manually flagged interval, Bit1 = overcounting/saturation effects likely present in skymap
FPI/DES compression loss indicator, 0=lossless, 1=lossy
Nominally, spinphase counts range over [0000, 5759] cnts. Each count represents 1/16 deg of observatory spinphase. Zero spinphase count indicates obs +Xaxis aligned with Sun.
Nominally, spinphase angles range over [0, 360) deg. Each count represents 1/16 deg of observatory spinphase. Zero spinphase angle indicates obs +Xaxis aligned with Sun.
FPI usually operates in Fast Survey (FS) Mode in the MMS Region Of Interest (ROI) for the current Mission Phase. Data are taken at burst (30/150 ms for DES/DIS) resolution in this mode. Data are also made available at survey (4.5 s) resolution. Per mission design, not all burstresolution data are downlinked, but all survey data are downlinked. Planning around calibration activities, avoidance of Earth radiation belts, etc, when possible, FPI usually operates in Slow Survey (SS) Mode (60 s resolution) outside of ROI. This moments product contains results from integrating the standard moments of phasespace distributions formed from the indicated data type (DES/DIS burst, FS or SS). For convenience, some additional parameters are included to augment those most commonly found in a moments product of this sort, plus timestamps and other annotation characterizing the state of the instrument system at the indicated time.
See FPI Version Release Notes (https://lasp.colorado.edu/mms/sdc/public/datasets/fpi/) for data set modification history.
Value of zero signifies no quality errors. For nonzero values: Bit0 = manually flagged interval, Bit1 = overcounting/saturation effects likely present in skymap, Bit2 = reported spacecraft potential above 20V, Bit3 = invalid/unavailable spacecraft potential, Bit4 = significant (>25%) cold plasma (<10eV) component, Bit5 = significant (>25%) hot plasma (>30keV) component, Bit6 = high sonic Mach number (v/vth > 2.5), Bit7 = low calculated density (n_DES < 0.05 cm^3), Bit8 = bentPipe magnetic field used instead of brst l2pre magnetic field, Bit9 = srvy l2pre magnetic field used instead of brst l2pre magnetic field, Bit10 = no internally generated photoelectron correction applied
FPI/DES compression loss indicator, 0=lossless, 1=lossy
Nominally, spinphase counts range over [0000, 5759] cnts. Each count represents 1/16 deg of observatory spinphase. Zero spinphase count indicates obs +Xaxis aligned with Sun.
Nominally, spinphase angles range over [0, 360) deg. Each count represents 1/16 deg of observatory spinphase. Zero spinphase angle indicates obs +Xaxis aligned with Sun.
low energy bin: 0 eV  200 eV. pitchangle bin size: 6 deg.
mid energy bin: 200 eV  2 keV. pitchangle bin size: 6 deg.
high energy bin: 2 keV  30 keV. pitchangle bin size: 6 deg.
Counts, summed over DSC velocitydirs closest to +X_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to X_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to +Y_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to Y_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to +Z_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to Z_DSC, by energy bin.
Counts, summed within 30 degrees parallel bentPipe magnetic field.
Counts, summed within 30 degrees antiparallel to bentPipe magnetic field.
Counts, summed within 60 degrees perpendicular to bentPipe magnetic field.
Differential energy flux, averaged (weighted by solid angle) over all look directions, by energy bin.
Estimated systematic error (positive or negative) in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding. This can be subtracted from bulk velocity to obtain the corrected velocity vector.
Estimated systematic error (positive or negative) in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding. This can be subtracted from bulk velocity to obtain the corrected velocity vector.
Estimated error in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding
Estimated error in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
FPI usually operates in Fast Survey (FS) Mode in the MMS Region Of Interest (ROI) for the current Mission Phase. Data are taken at burst (30/150 ms for DES/DIS) resolution in this mode. Data are also made available at survey (4.5 s) resolution. Per mission design, not all burstresolution data are downlinked, but all survey data are downlinked. Planning around calibration activities, avoidance of Earth radiation belts, etc, when possible, FPI usually operates in Slow Survey (SS) Mode (60 s resolution) outside of ROI. This product contains partial moments that come from performing the standard moment integrals over a limited portion of velocity space. The resulting quantities are named similarly to their corresponding standard moments, but are decorated with 'part' to differentiate. For example, density_part is the density moment integrated from a particular energy step to infinity. These partial moments are formed from the indicated data type (DES/DIS burst, FS or SS). For convenience, some additional parameters are included to augment those most commonly found in a moments product of this sort, plus timestamps and other annotation characterizing the state of the instrument system at the indicated time.
See FPI Version Release Notes (https://lasp.colorado.edu/mms/sdc/public/datasets/fpi/) for data set modification history.
Value of zero signifies no quality errors. For nonzero values: Bit0 = manually flagged interval, Bit1 = overcounting/saturation effects likely present in skymap, Bit2 = reported spacecraft potential above 20V, Bit3 = invalid/unavailable spacecraft potential, Bit4 = significant (>10%) cold plasma (<10eV) component, Bit5 = significant (>25%) hot plasma (>30keV) component, Bit6 = high sonic Mach number (v/vth > 2.5), Bit7 = low calculated density (n_DES < 0.05 cm^3), Bit8 = bentPipe magnetic field used instead of srvy l2pre magnetic field, Bit10 = no internally generated photoelectron correction applied, Bit11 = compression pipeline error, Bit12 = spintone calculation error (DBCS only)
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
Recommended energy index during this survey
FPI usually operates in Fast Survey Mode in the MMS Region Of Interest (ROI) for the current Mission Phase. Data taken at burst (30/150 ms for DES/DIS) resolution are aggregated on board and made available at survey (4.5 s) resolution in this mode. This product contains phasespace distribution maps of results from surveying the highresolution observations during each 4.5 s period. In particular, the (highest possible quality at the time of release) corrected/converted "Fast Survey SkyMap" distributions are reported with timestamps and other annotation characterizing the state of the instrument system at the indicated time.
See FPI Version Release Notes (https://lasp.colorado.edu/mms/sdc/public/datasets/fpi/) for data set modification history.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Az bin: sector ind=00 looks "after" (spinphase) Sun, ..., sector ind=31 looks "before" Sun dir. Head fieldofview: pixel index=00 looks to zenith, ..., pixel index=15 looks to nadir. FPI operations nominally bin data from 64 energy filters into 32 pairwise energy bins, indexed 031. Nominally, bins are indexed in increasing energy order. See FPI docs for details.
Value of zero signifies no quality errors. For nonzero values: Bit0 = manually flagged interval, Bit1 = overcounting/saturation effects likely present in skymap
FPI/DIS compression loss indicator, 0=lossless, 1=lossy
Nominally, spinphase counts range over [0000, 5759] cnts. Each count represents 1/16 deg of observatory spinphase. Zero spinphase count indicates obs +Xaxis aligned with Sun.
Nominally, spinphase angles range over [0, 360) deg. Each count represents 1/16 deg of observatory spinphase. Zero spinphase angle indicates obs +Xaxis aligned with Sun.
FPI usually operates in Fast Survey (FS) Mode in the MMS Region Of Interest (ROI) for the current Mission Phase. Data are taken at burst (30/150 ms for DES/DIS) resolution in this mode. Data are also made available at survey (4.5 s) resolution. Per mission design, not all burstresolution data are downlinked, but all survey data are downlinked. Planning around calibration activities, avoidance of Earth radiation belts, etc, when possible, FPI usually operates in Slow Survey (SS) Mode (60 s resolution) outside of ROI. This moments product contains results from integrating the standard moments of phasespace distributions formed from the indicated data type (DES/DIS burst, FS or SS). For convenience, some additional parameters are included to augment those most commonly found in a moments product of this sort, plus timestamps and other annotation characterizing the state of the instrument system at the indicated time.
See FPI Version Release Notes (https://lasp.colorado.edu/mms/sdc/public/datasets/fpi/) for data set modification history.
Value of zero signifies no quality errors. For nonzero values: Bit0 = manually flagged interval, Bit1 = overcounting/saturation effects likely present in skymap, Bit2 = reported spacecraft potential above 20V, Bit3 = invalid/unavailable spacecraft potential, Bit4 = significant (>25%) cold plasma (<10eV) component, Bit5 = significant (>25%) hot plasma (>30keV) component, Bit6 = high sonic Mach number (v/vth > 2.5), Bit7 = low calculated density (n_DIS < 0.05 cm^3), Bit8 = bentPipe magnetic field used instead of brst l2pre magnetic field, Bit9 = srvy l2pre magnetic field used instead of brst l2pre magnetic field, Bit10 = no internally generated photoelectron correction applied
FPI/DIS compression loss indicator, 0=lossless, 1=lossy
Nominally, spinphase counts range over [0000, 5759] cnts. Each count represents 1/16 deg of observatory spinphase. Zero spinphase count indicates obs +Xaxis aligned with Sun.
Nominally, spinphase angles range over [0, 360) deg. Each count represents 1/16 deg of observatory spinphase. Zero spinphase angle indicates obs +Xaxis aligned with Sun.
Counts, summed over DSC velocitydirs closest to +X_DSC, by energy bin.
Differential energy flux, averaged (weighted by solid angle) over DBCS velocitydirs with 45deg <= theta < 135deg and 135deg <= phi < 225deg, by energy bin.
Counts, summed over DSC velocitydirs closest to +Y_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to Y_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to +Z_DSC, by energy bin.
Counts, summed over DSC velocitydirs closest to Z_DSC, by energy bin.
Differential energy flux, averaged (weighted by solid angle) over all look directions, by energy bin.
Background differential energy flux by energy bin, averaged (weighted by solid angle) over all directions (flow or look).
Background number density derived via integration of the estimated background differential energy flux.
Estimated systematic error (positive or negative) in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding. This can be subtracted from bulk velocity to obtain the corrected velocity vector.
Estimated systematic error (positive or negative) in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding. This can be subtracted from bulk velocity to obtain the corrected velocity vector.
Estimated error in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding
Estimated error in spinplane bulk velocity (km/s) due to imperfect sensor suite flatfielding
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
FPI usually operates in Fast Survey (FS) Mode in the MMS Region Of Interest (ROI) for the current Mission Phase. Data are taken at burst (30/150 ms for DES/DIS) resolution in this mode. Data are also made available at survey (4.5 s) resolution. Per mission design, not all burstresolution data are downlinked, but all survey data are downlinked. Planning around calibration activities, avoidance of Earth radiation belts, etc, when possible, FPI usually operates in Slow Survey (SS) Mode (60 s resolution) outside of ROI. This product contains partial moments that come from performing the standard moment integrals over a limited portion of velocity space. The resulting quantities are named similarly to their corresponding standard moments, but are decorated with 'part' to differentiate. For example, density_part is the density moment integrated from a particular energy step to infinity. These partial moments are formed from the indicated data type (DES/DIS burst, FS or SS). For convenience, some additional parameters are included to augment those most commonly found in a moments product of this sort, plus timestamps and other annotation characterizing the state of the instrument system at the indicated time.
See FPI Version Release Notes (https://lasp.colorado.edu/mms/sdc/public/datasets/fpi/) for data set modification history.
Value of zero signifies no quality errors. For nonzero values: Bit0 = manually flagged interval, Bit1 = overcounting/saturation effects likely present in skymap, Bit2 = reported spacecraft potential above 20V, Bit3 = invalid/unavailable spacecraft potential, Bit4 = significant (>10%) cold plasma (<10eV) component, Bit5 = significant (>25%) hot plasma (>30keV) component, Bit6 = high sonic Mach number (v/vth > 2.5), Bit7 = low calculated density (n_DIS <= 0.0 cm^3), Bit8 = bentPipe magnetic field used instead of srvy l2pre magnetic field, Bit10 = no internally generated photoelectron correction applied, Bit11 = compression pipeline error, Bit12 = spintone calculation error (DBCS only), Bit13 = significant (>=20%) penetrating radiation
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Pxx Pxy Pxz, Row2) Pyx Pyy Pyz, Row3) Pzx Pzy Pzz. Note that Pij=Pji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
The 3x3 matrix is represented as: Row1) Txx Txy Txz, Row2) Tyx Tyy Tyz, Row3) Tzx Tzy Tzz. Note that Tij=Tji.
Recommended energy index during this survey
References
Initial Public Release
References
Initial Public Release
References
Initial Public Release
References
Initial Public Release
MMS MEC Magnetic ephemeris and coordinates, Level 2 science data. PI institution is Los Alamos National Laboratory (LANL)
MMS MEC Magnetic ephemeris and coordinates, Level 2 science data. PI institution is Los Alamos National Laboratory (LANL)
MMS MEC Magnetic ephemeris and coordinates, Level 2 science data. PI institution is Los Alamos National Laboratory (LANL)
MMS MEC Magnetic ephemeris and coordinates, Level 2 science data. PI institution is Los Alamos National Laboratory (LANL)
MMS MEC Magnetic ephemeris and coordinates, Level 2 science data. PI institution is Los Alamos National Laboratory (LANL)
MMS MEC Magnetic ephemeris and coordinates, Level 2 science data. PI institution is Los Alamos National Laboratory (LANL)
The triaxial searchcoil magnetometer (SCM) with its associated preamplifier provides the threedimensional measurement of the magnetic field fluctuations. The analog magnetic waveforms measured by the SCM are digitized and processed inside the digital signal processor (DSP), collected and stored by the central instrument data processor (CIDP) via the Fields central electronics box (CEB). Prior to launch, all SCM Flight models were calibrated by LPP at the National Magnetic Observatory at ChambonlaForet (Orleans). Once per orbit, each SCM transfer function is checked thanks to the onboard calibration signal provided by DSP. SCM is operated for the entire MMS orbit in survey mode. Within the ROI, burst mode data are also acquired as well as high burst mode data. SCM data set corresponds to the AC magnetic field waveforms in nanoTesla and in the GSE frame. The instrument paper for SCM can be found at https://urldefense.proofpoint.com/v2/url?u=http3A__link.springer.com_article_10 .1007_s112142D0142D00962D9&d=DwIFAg&c=c6MrceVCY5m5A_KAUkrdoA&r=bjziExGTRYoZgE 2xb_dDSm9NxNIo0lG6QrB0Y6rHS4&m=CMzo0Vv9zPtWSdbdY1Wq9jIkYS2cOMV9JYZsMV10y0&s=Xb P9PiEAswHGl5lqgsDVI6zs8ivJx7yek9i2undKl10&e=
unpack telemetry, assign sample times 20200712T14:21:17.00004726648009Z  [L1A>L1B (step 1/1)] Calibration (TMcounts>nT). See CALIBRATION_PARAMETERS for details. 20200724T17:42:26.00004404782925Z  [L1B>L2 (step 1/2)] Coordinate transform (SCM123>GSE). See COORD_TRANS_PARAMETERS for details. 20200724T17:42:40.00004857778225Z  [L1B>L2 (step 2/2)] Frequency filtering. See FREQUENCY_FILTER for details.
These calibrated (nT) AC magnetic field waveform data are sampled at 8192S/s. They are highpass filtered above 1.00Hz but not lowpass filtered. See global attributes for details. For more information, please have a look at the SCM Data Products Guide.
Each letter refers to one SCM physical antenna in the SCM123 order. 'G' stands for good data, 'Z' for data that are affected or set to zero by convolution boundary effect, 'S' for saturated data, 'X' for out of range data, 'B' for fillvalue/bad data.
The triaxial searchcoil magnetometer (SCM) with its associated preamplifier provides the threedimensional measurement of the magnetic field fluctuations. The analog magnetic waveforms measured by the SCM are digitized and processed inside the digital signal processor (DSP), collected and stored by the central instrument data processor (CIDP) via the Fields central electronics box (CEB). Prior to launch, all SCM Flight models were calibrated by LPP at the National Magnetic Observatory at ChambonlaForet (Orleans). Once per orbit, each SCM transfer function is checked thanks to the onboard calibration signal provided by DSP. SCM is operated for the entire MMS orbit in survey mode. Within the ROI, burst mode data are also acquired as well as high burst mode data. SCM data set corresponds to the AC magnetic field waveforms in nanoTesla and in the GSE frame. The instrument paper for SCM can be found at https://urldefense.proofpoint.com/v2/url?u=http3A__link.springer.com_article_10 .1007_s112142D0142D00962D9&d=DwIFAg&c=c6MrceVCY5m5A_KAUkrdoA&r=bjziExGTRYoZgE 2xb_dDSm9NxNIo0lG6QrB0Y6rHS4&m=CMzo0Vv9zPtWSdbdY1Wq9jIkYS2cOMV9JYZsMV10y0&s=Xb P9PiEAswHGl5lqgsDVI6zs8ivJx7yek9i2undKl10&e=
unpack telemetry, assign sample times 20200712T14:25:35.00005602836283Z  [L1A>L1B (step 1/1)] Calibration (TMcounts>nT). See CALIBRATION_PARAMETERS for details. 20200724T17:47:12.00006186961791Z  [L1B>L2 (step 1/2)] Coordinate transform (SCM123>GSE). See COORD_TRANS_PARAMETERS for details. 20200724T17:47:21.00005328654906Z  [L1B>L2 (step 2/2)] Frequency filtering. See FREQUENCY_FILTER for details.
These calibrated (nT) AC magnetic field waveform data are sampled at 16384S/s. They are highpass filtered above 32.00Hz but not lowpass filtered. See global attributes for details. For more information, please have a look at the SCM Data Products Guide (https://lasp.colorado.edu/mms/sdc/public/datasets/fields/Science_Data_Products_ Guide_vol2_SCM_v11_20160301.pdf).
The triaxial searchcoil magnetometer (SCM) with its associated preamplifier provides the threedimensional measurement of the magnetic field fluctuations. The analog magnetic waveforms measured by the SCM are digitized and processed inside the digital signal processor (DSP), collected and stored by the central instrument data processor (CIDP) via the Fields central electronics box (CEB). Prior to launch, all SCM Flight models were calibrated by LPP at the National Magnetic Observatory at ChambonlaForet (Orleans). Once per orbit, each SCM transfer function is checked thanks to the onboard calibration signal provided by DSP. SCM is operated for the entire MMS orbit in survey mode. Within the ROI, burst mode data are also acquired as well as high burst mode data. SCM data set corresponds to the AC magnetic field waveforms in nanoTesla and in the GSE frame. The instrument paper for SCM can be found at https://urldefense.proofpoint.com/v2/url?u=http3A__link.springer.com_article_10 .1007_s112142D0142D00962D9&d=DwIFAg&c=c6MrceVCY5m5A_KAUkrdoA&r=bjziExGTRYoZgE 2xb_dDSm9NxNIo0lG6QrB0Y6rHS4&m=CMzo0Vv9zPtWSdbdY1Wq9jIkYS2cOMV9JYZsMV10y0&s=Xb P9PiEAswHGl5lqgsDVI6zs8ivJx7yek9i2undKl10&e=
unpack telemetry, assign sample times 20200710T00:02:31.00006610155105Z  [L1A>L1B (step 1/1)] Calibration (TMcounts>nT). See CALIBRATION_PARAMETERS for details. 20200723T00:06:51.0000640153885Z  [L1B>L2 (step 1/2)] Coordinate transform (SCM123>GSE). See COORD_TRANS_PARAMETERS for details. 20200723T00:09:55.0000315904617Z  [L1B>L2 (step 2/2)] Frequency filtering. See FREQUENCY_FILTER for details.
These calibrated (nT) AC magnetic field waveform data are sampled at 32S/s. They are highpass filtered above 0.50Hz but not lowpass filtered. See global attributes for details. For more information, please have a look at the SCM Data Products Guide (https://lasp.colorado.edu/mms/sdc/public/datasets/fields/Science_Data_Products_ Guide_vol2_SCM_v11_20160301.pdf).
K. Torkar et al, Active Spacecraft Potential Control Investigation Space Science Reviews, 2014, DOI: 10.1007/s1121401400493 Further information:  http://www.iwf.oeaw.ac.at/en/research/nearearthspace/mms/  http://mms.space.swri.edu/
150224 Initial version 150831 Minor updates and fixes 160205 CDF file format guide compliant
Calibrated magneticspectral density computed by onboard FFTs by the Digital Signal Processor (DSP) from the Search Coil Magnetometer (SCM) in the SCM123 coordinate system (scm1 =  x sensor; scm2 = z sensor; scm3 = y sensor). This product is computed in space from individual components that are not synchronized to the 1 second pulse. Therefore, the timing between channels can be inaccurate by a fraction of a second. The samples times are interval start times taken from the x component.
electric spectral density
search coil magnetometer spectral density
electric spectral density
EDI ambient data. The EDI instrument paper and data products guide can be found at the following two links: http://link.springer.com/article/10.1007%2Fs1121401501827, https://lasp.colorado.edu/mms/sdc/public/datasets/fields/
v0.0.0  Original version. v1.0.0  Include trajectory vectors and optics state. v1.1.0  Update metadata: counts > flux. v1.2.0  Added flux error. v1.3.0  Trajectory vector errors are now deltas. v1.4.0  Fixed deadtime correction and error values. v1.5.0  Factor of 2 for accumulation time & 2 for abscal factor in srvy mode. v1.6.0  No factor of 2 for accumulation time in srvy mode. v2.0.0  Reduced file size with scalar errors. Update metadata. v2.1.0  Correct fill value for fluxes. v3.0.0  Omnidirectional error for trajectories. YVersion linked to cal file. Single epoch for counts. v4.0.0  Replace data in GSM coordinates with data in DBCS to be consistent with other particle instruments.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
EDI ambient data. The EDI instrument paper and data products guide can be found at the following two links: http://link.springer.com/article/10.1007%2Fs1121401501827, https://lasp.colorado.edu/mms/sdc/public/datasets/fields/
v1.0.0  Original version. v1.1.0  Correct fill value for fluxes. v2.0.0  Omnidirectional error for trajectories. YVersion linked to cal file. Single epoch for counts. v3.0.0  Replace data in GSM coordinates with data in DBCS to be consistent with other particle instruments.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
EDI electric field data. Instrument papers for EDI can be found at: http://link.springer.com/article/10.1007%2Fs1121401501827
v1.0.0  First version. TRITOF selection based on smallest error. v1.1.0  TRITOF merged by weighted average. v1.2.0  Fixed t_delta_plus/minus CDF_type. v1.3.0  Fixed Fixed vdrift SI conversion. v1.4.0  Fixed data duplication caused by multiple l2pre file locations. v1.5.0  Inplemented baseline*beams*Bmag filter for triangulation. v1.6.0  Inplemented null files for no or low quality data.
EDI Q0 data. The EDI instrument paper and data products guidescan be found at the following two links: http://link.springer.com/article/10.1007%2Fs1121401501827, https://lasp.colorado.edu/mms/sdc/public/datasets/fields/
v0.0.0  First version. v0.0.1  Filled energy variables. v0.0.2  Energy written properly. v1.0.0  Update variable names. v1.1.0  Added optics state. v2.0.0  Added electron trajectories. v2.1.0  Deltas on trajectory vectors are now deltas. v3.0.0  Reduced file size with scalar errors. Add VAR_NOTES. v3.1.0  Fixed optics datatype. v4.0.0  Removed unused Epoch variable. v5.0.0  Trajectories are provided in DBCS coordinates.
Q0 data consists of raw electron counts. The error at any one time is the squareroot of the counts. Note that there may be contamination from the EDI electron beams. See the data products guide or contact an EDI team member to learn about beam contamination.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
EDI ambient data. The EDI instrument paper and data products guide can be found at the following two links: http://link.springer.com/article/10.1007%2Fs1121401501827, https://lasp.colorado.edu/mms/sdc/public/datasets/fields/
v0.0.0  Original version. v1.0.0  Include trajectory vectors and optics state. v1.1.0  Update metadata: counts > flux. v1.2.0  Added flux error. v1.3.0  Trajectory vector errors are now deltas. v1.4.0  Fixed deadtime correction and error values. v1.5.0  Factor of 2 for accumulation time & 2 for abscal factor in srvy mode. v1.6.0  No factor of 2 for accumulation time in srvy mode. v2.0.0  Reduced file size with scalar errors. Update metadata. v2.1.0  Correct fill value for fluxes. v3.0.0  Omnidirectional error for trajectories. Correct time deltas. YVersion linked to cal file. Single epoch for counts. v4.0.0  Replace data in GSM coordinates with data in DBCS to be consistent with other particle instruments.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
EDI ambient data. The EDI instrument paper and data products guide can be found at the following two links: http://link.springer.com/article/10.1007%2Fs1121401501827, https://lasp.colorado.edu/mms/sdc/public/datasets/fields/
v1.0.0  Original version. v1.1.0  Correct fill value for fluxes. v2.0.0  Omnidirectional error for trajectories. YVersion linked to cal file. Single epoch for counts. v3.0.0  Replace data in GSM coordinates with data in DBCS to be consistent with other particle instruments. v4.0.0  Each trajectory has its own LABL_PTR_1 variable.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
EDI electric field data. Instrument papers for EDI can be found at: http://link.springer.com/article/10.1007%2Fs1121401501827
v1.0.0  First version. TRITOF selection based on smallest error. v1.1.0  TRITOF merged by weighted average. v1.2.0  Fixed t_delta_plus/minus CDF_type. v1.3.0  Fixed Fixed vdrift SI conversion. v1.4.0  Fixed data duplication caused by multiple l2pre file locations. v1.5.0  Inplemented baseline*beams*Bmag filter for triangulation. v1.6.0  Inplemented null files for no or low quality data.
EDI Q0 data. The EDI instrument paper and data products guidescan be found at the following two links: http://link.springer.com/article/10.1007%2Fs1121401501827, https://lasp.colorado.edu/mms/sdc/public/datasets/fields/
v0.0.0  First version. v0.0.1  Filled energy variables. v0.0.2  Energy written properly. v1.0.0  Update variable names. v1.1.0  Added optics state. v2.0.0  Added electron trajectories. v2.1.0  Deltas on trajectory vectors are now deltas. v3.0.0  Reduced file size with scalar errors. Add VAR_NOTES. v4.0.0  Removed unused Epoch variable. v5.0.0  Trajectories are provided in DBCS coordinates.
Q0 data consists of raw electron counts. The error at any one time is the squareroot of the counts. Note that there may be contamination from the EDI electron beams. See the data products guide or contact an EDI team member to learn about beam contamination.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
Trajectories are given as unit vectors in spherical coordinates, with phi (theta) representing the azimuthal (polar) directions, in the indicated coordinate system. They are opposite to the nominal lookdirection of the instrument. Errors represent an omnidirectional error. For more details about errors, contact the EDI instrument team.
https://mms.gsfc.nasa.gov/ For detailed timing information, such as needed for cross spectral analysis, please consult the EDP Data Products Guide.
V.0. Initial release.
L1B AC Electric Field
https://mms.gsfc.nasa.gov/ The full name of PI affiliations: SWRI  Southwest Research Institute. LASP  Laboratory for Atmospheric and Space Physics. KTH  Kungliga Tekniska Hogskolan (Swedish Royal Institute of Technology). For detailed timing information, such as needed for cross spectral analysis, please consult the EDP Data Products Guide.
V.0. Initial release. V.1. QL (v1.0.z), SCPOT (v1.0.z), L2A (v0.1.z) now uses ASPOC srvy l2 and DEFATT, if these are available. Brst QL uses intermediate L2A file from Fast mode for delta offsets. Bitmask changed to uint16 and Quality to uint8. V.2. SCPOT (v2.0.z), L2A (v1.0.z) now uses variable names in accordance with new recommended standard for FIELDS, All products change shortening factor to 1.25 on SDP, offsets applied indicated by GlobalAttribute Calibration_file. V.2. L2a (v2.0.z), QL (v1.6.z) now try to remove solar wind wake which previously left a clear sinusodial signal in the data. V.3. L2a (v3.0.z) Slow Mode probe Gain set to 1.0 when orbital radius less than 5 RE (1.25 otherwise), L2pre (v2.0.z) DSL offsets removed from field is now included in the file as the Slow mode is dependent on scpot product (Fast/Brst is simply based on offset in Calibration_file).
https://mms.gsfc.nasa.gov/ For detailed timing information, such as needed for cross spectral analysis, please consult the EDP Data Products Guide.
V.0. Initial release.
https://mms.gsfc.nasa.gov/ The full name of PI affiliations: SWRI  Southwest Research Institute. LASP  Laboratory for Atmospheric and Space Physics. KTH  Kungliga Tekniska Hogskolan (Swedish Royal Institute of Technology). For detailed timing information, such as needed for cross spectral analysis, please consult the EDP Data Products Guide.
V.0. Initial release. V.1. QL (v1.0.z), SCPOT (v1.0.z), L2A (v0.1.z) now uses ASPOC srvy l2 and DEFATT, if these are available. Brst QL uses intermediate L2A file from Fast mode for delta offsets. Bitmask changed to uint16 and Quality to uint8. V.2. SCPOT (v2.0.z), L2A (v1.0.z) now uses variable names in accordance with new recommended standard for FIELDS, All products change shortening factor to 1.25 on SDP, offsets applied indicated by GlobalAttribute Calibration_file. V.2. L2a (v2.0.z), QL (v1.6.z) now try to remove solar wind wake which previously left a clear sinusodial signal in the data. V.3. L2a (v3.0.z) Slow Mode probe Gain set to 1.0 when orbital radius less than 5 RE (1.25 otherwise), L2pre (v2.0.z) DSL offsets removed from field is now included in the file as the Slow mode is dependent on scpot product (Fast/Brst is simply based on offset in Calibration_file).
https://mms.gsfc.nasa.gov/ For detailed timing information, such as needed for cross spectral analysis, please consult the EDP Data Products Guide.
V.0. Initial release.
https://mms.gsfc.nasa.gov/ The full name of PI affiliations: SWRI  Southwest Research Institute. LASP  Laboratory for Atmospheric and Space Physics. KTH  Kungliga Tekniska Hogskolan (Swedish Royal Institute of Technology). For detailed timing information, such as needed for cross spectral analysis, please consult the EDP Data Products Guide.
V.0. Initial release. V.1. QL (v1.0.z), SCPOT (v1.0.z), L2A (v0.1.z) now uses ASPOC srvy l2 and DEFATT, if these are available. Brst QL uses intermediate L2A file from Fast mode for delta offsets. Bitmask changed to uint16 and Quality to uint8. V.2. SCPOT (v2.0.z), L2A (v1.0.z) now uses variable names in accordance with new recommended standard for FIELDS, All products change shortening factor to 1.25 on SDP, offsets applied indicated by GlobalAttribute Calibration_file. V.2. L2a (v2.0.z), QL (v1.6.z) now try to remove solar wind wake which previously left a clear sinusodial signal in the data. V.3. L2a (v3.0.z) Slow Mode probe Gain set to 1.0 when orbital radius less than 5 RE (1.25 otherwise), L2pre (v2.0.z) DSL offsets removed from field is now included in the file as the Slow mode is dependent on scpot product (Fast/Brst is simply based on offset in Calibration_file).
L1B AC Electric Field
empty
Constantly modifying this code