
This ionogram was digitized from the original ISIS 1 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 673). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at https://spdf.gsfc.nasa.gov/isis/isisstatus.html
created December 2017
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
This ionogram was digitized from the original ISIS 1 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 673). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at https://spdf.gsfc.nasa.gov/isis/isisstatus.html
created December 2017
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
This ionogram was digitized from the original ISIS 1 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 673). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at https://spdf.gsfc.nasa.gov/isis/isisstatus.html
created December 2017
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
This ionogram was digitized from the original ISIS 1 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1998
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
seperates the fixed and swept portions
This ionogram was digitized from the original ISIS 1 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1998
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This ionogram was digitized from the original ISIS 1 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1998
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This ionogram was digitized from the original ISIS 1 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1998
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This ionogram was digitized from the original ISIS 1 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1998
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This ionogram was digitized from the original ISIS 1 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1998
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This ionogram was digitized from the original ISIS 1 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1998
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This ionogram was digitized from the original ISIS 1 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1998
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This ionogram was digitized from the original ISIS 1 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1998
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This ionogram was digitized from the original ISIS 1 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1998
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This ionogram was digitized from the original ISIS 1 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1998
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This ionogram was digitized from the original ISIS 1 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1998
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This ionogram was digitized from the original ISIS 1 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1998
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This ionogram was digitized from the original ISIS 1 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1998
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This data set, provided by the Communications Research Centre (CRC) in Ottawa, Canada, consists of electron density profiles for the ionosphere above the F2 maximum (topside ionosphere). The data were computed from the orginal ionograms using Jackson's method (Jackson, Proceedings of the IEEE., p. 960, June 1969). ISIS1 was launched on 19690130 into an elliptical orbit (5003500km) with an inclination of 88.4 degrees and ISIS2 was launched on 19710401 into an circular orbit at 1400 km with an inclination of 88.1 degrees. Both satellites were fully instrumented ionospheric observatories including sweep and fixedfrequequency ionosondes, a VLF receiver, energetic and soft particle detectors, an ion mass spectrometer, an electrostatic analyzer, an Langmuir probe, a beacon transmitter, a cosmic noise experiment and ISIS 2 also carried two photometers. A tape recorder with 1h capacity was included on both satellites. Data were also collected during overflights of several telemetry stations. The telemetry stations were in areas that provided primary data coverage near the 80degW meridian and in areas near Hawaii, Singapore, Australia, the UK, Norway, India, Japan, Antarctica, New Zealand, and Central Africa.
This ionogram was digitized from the original ISIS 2 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1995
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
A 7track ISIS 2 analog telemetry tape from Ottawa (#561) has been digitized using the GSFC facilities of the Data Evaluation Laboratory (DEL) within the Mission Operations and Data Systems Directorate (Code 500) at Goddard. The digitization was performed using an A/D converter board and software device driver compatible with the OS/2 operating system used by the 486based Programmable Telemetry Processor (PTP) associated software has been installed on their PTP and debugged so that we now have a working system for making digital ISIS ionograms directly from the telemetry tapes. Earlier, we successfully digitized the PCM and NASA 36 bit timecode data from this same tape. The ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz appropriate for the postdetection ISIS 2 sounderreceiver video output which extends from DC to 15 kHz (see p. 50 of the 1971 ISIS 2 report by Daniels). The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (ct/2) interval of 3.747 km. With the ISIS 2 prf of 45 sounder pulses/s, there are (1/45)/(2.5**(5)) = 888.89 samples between each of the approximately 1015 sounder pulses per ionogram (including the fixedfrequency portion) or nearly 10**6 16bit samples/ionogram (approximately 1.8 MBytes) for just the sounderreceiver video data. Adding header information, and the pcm data containing data from the other instruments, yields about 2 MBytes of data for the 22.5 s period corresponding to one ionogram. Two steps were taken in order to reduce this large volume of nearly 2 MBytes/ionogram. First, every four 25 microsecond samples following the sounder pulse were averaged. Second, the 16 bit samples were reduced to 8 bit samples. The first step decreased the apparentrange resolution to 15 km, but yielded highquality ionograms because of the improved S/N due to the averaging.
created April 1995
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This ionogram was digitized from the original ISIS 2 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1995
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This ionogram was digitized from the original ISIS 2 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1995
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This ionogram was digitized from the original ISIS 2 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1995
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This ionogram was digitized from the original ISIS 2 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1995
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This ionogram was digitized from the original ISIS 2 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1995
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This ionogram was digitized from the original ISIS 2 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1995
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This ionogram was digitized from the original ISIS 2 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1995
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This ionogram was digitized from the original ISIS 2 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1995
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
This ionogram was digitized from the original ISIS 2 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1995
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This ionogram was digitized from the original ISIS 2 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1995
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
A 7track ISIS 2 analog telemetry tape from Ottawa (#561) has been digitized using the GSFC facilities of the Data Evaluation Laboratory (DEL) within the Mission Operations and Data Systems Directorate (Code 500) at Goddard. The digitization was performed using an A/D converter board and software device driver compatible with the OS/2 operating system used by the 486based Programmable Telemetry Processor (PTP) associated software has been installed on their PTP and debugged so that we now have a working system for making digital ISIS ionograms directly from the telemetry tapes. Earlier, we successfully digitized the PCM and NASA 36 bit timecode data from this same tape. The ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz appropriate for the postdetection ISIS 2 sounderreceiver video output which extends from DC to 15 kHz (see p. 50 of the 1971 ISIS 2 report by Daniels). The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (ct/2) interval of 3.747 km. With the ISIS 2 prf of 45 sounder pulses/s, there are (1/45)/(2.5**(5)) = 888.89 samples between each of the approximately 1015 sounder pulses per ionogram (including the fixedfrequency portion) or nearly 10**6 16bit samples/ionogram (approximately 1.8 MBytes) for just the sounderreceiver video data. Adding header information, and the pcm data containing data from the other instruments, yields about 2 MBytes of data for the 22.5 s period corresponding to one ionogram. Two steps were taken in order to reduce this large volume of nearly 2 MBytes/ionogram. First, every four 25 microsecond samples following the sounder pulse were averaged. Second, the 16 bit samples were reduced to 8 bit samples. The first step decreased the apparentrange resolution to 15 km, but yielded highquality ionograms because of the improved S/N due to the averaging.
created April 1995
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
A 7track ISIS 2 analog telemetry tape from Ottawa (#561) has been digitized using the GSFC facilities of the Data Evaluation Laboratory (DEL) within the Mission Operations and Data Systems Directorate (Code 500) at Goddard. The digitization was performed using an A/D converter board and software device driver compatible with the OS/2 operating system used by the 486based Programmable Telemetry Processor (PTP) associated software has been installed on their PTP and debugged so that we now have a working system for making digital ISIS ionograms directly from the telemetry tapes. Earlier, we successfully digitized the PCM and NASA 36 bit timecode data from this same tape. The ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz appropriate for the postdetection ISIS 2 sounderreceiver video output which extends from DC to 15 kHz (see p. 50 of the 1971 ISIS 2 report by Daniels). The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (ct/2) interval of 3.747 km. With the ISIS 2 prf of 45 sounder pulses/s, there are (1/45)/(2.5**(5)) = 888.89 samples between each of the approximately 1015 sounder pulses per ionogram (including the fixedfrequency portion) or nearly 10**6 16bit samples/ionogram (approximately 1.8 MBytes) for just the sounderreceiver video data. Adding header information, and the pcm data containing data from the other instruments, yields about 2 MBytes of data for the 22.5 s period corresponding to one ionogram. Two steps were taken in order to reduce this large volume of nearly 2 MBytes/ionogram. First, every four 25 microsecond samples following the sounder pulse were averaged. Second, the 16 bit samples were reduced to 8 bit samples. The first step decreased the apparentrange resolution to 15 km, but yielded highquality ionograms because of the improved S/N due to the averaging.
created April 1995
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This ionogram was digitized from the original ISIS 2 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1995
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This ionogram was digitized from the original ISIS 2 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1995
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This ionogram was digitized from the original ISIS 2 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1995
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
This ionogram was digitized from the original ISIS 2 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1995
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
A 7track ISIS 2 analog telemetry tape from Ottawa (#561) has been digitized using the GSFC facilities of the Data Evaluation Laboratory (DEL) within the Mission Operations and Data Systems Directorate (Code 500) at Goddard. The digitization was performed using an A/D converter board and software device driver compatible with the OS/2 operating system used by the 486based Programmable Telemetry Processor (PTP) associated software has been installed on their PTP and debugged so that we now have a working system for making digital ISIS ionograms directly from the telemetry tapes. Earlier, we successfully digitized the PCM and NASA 36 bit timecode data from this same tape. The ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz appropriate for the postdetection ISIS 2 sounderreceiver video output which extends from DC to 15 kHz (see p. 50 of the 1971 ISIS 2 report by Daniels). The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (ct/2) interval of 3.747 km. With the ISIS 2 prf of 45 sounder pulses/s, there are (1/45)/(2.5**(5)) = 888.89 samples between each of the approximately 1015 sounder pulses per ionogram (including the fixedfrequency portion) or nearly 10**6 16bit samples/ionogram (approximately 1.8 MBytes) for just the sounderreceiver video data. Adding header information, and the pcm data containing data from the other instruments, yields about 2 MBytes of data for the 22.5 s period corresponding to one ionogram. Two steps were taken in order to reduce this large volume of nearly 2 MBytes/ionogram. First, every four 25 microsecond samples following the sounder pulse were averaged. Second, the 16 bit samples were reduced to 8 bit samples. The first step decreased the apparentrange resolution to 15 km, but yielded highquality ionograms because of the improved S/N due to the averaging.
created April 1995
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
This ionogram was digitized from the original ISIS 2 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1995
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
Virtual variable.
This ionogram was digitized from the original ISIS 2 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1995
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
This ionogram was digitized from the original ISIS 2 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1995
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
This ionogram was digitized from the original ISIS 2 analog telemetry data on 7track tape using the facilities of the Data Evaluation Laboratory at GSFC (Code 500). This data restoration project is headed by Dr. R.F. Benson (GSFC, Code 692). Ionograms were digitized at the rate of 40,000 16bit samples/sec. This sample rate is higher than the Nyquist frequency of 30 kHz. The sample frequency of 40 kHz provides a measurement every 25 microseconds corresponding to an apparent range (c*t/2) interval of 3.747 km. Each ionogram consists of a fixedfrequency and and a sweptfrequency portion. The time resolution is typically 24 seconds. More information can be found at http://nssdc/space/isis/isisstatus.html
created April 1995
This variable could be used as xaxis on amplitude spectrograms if fixed part is subtracted.
ISIS 2 was an ionospheric observatory instrumented with a sweep and a fixedfrequency ionosonde, a VLF receiver, energetic and soft particle detectors, an ion mass spectrometer, an electrostatic probe, a retarding potential analyzer, a beacon transmitter, a cosmic noise experiment, and two photometers. Two long crosseddipole antennas (73 and 18.7 m) were used for the sounding, VLF, and cosmic noise experiments. The spacecraft was spinstabilized to about 2 rpm after antenna deployment. There were two basic orientation modes for the spacecraft, cartwheel and orbitaligned. The spacecraft operated approximately the same length of time in each mode, remaining in one mode typically 3 to 5 months. The cartwheel mode with the axis perpendicular to the orbit plane was made available to provide ram and wake data for some experiments for each spin period, rather than for each orbit period. Attitude and spin information was obtained from a threeaxis magnetometer and a sun sensor. Control of attitude and spin was possible by means of magnetic torquing. The experiment package also included a programmable tape recorder with a one hour capacity. For nonrecorded observations, data from satellite and subsatellite regions were telemetered when the spacecraft was in the line of sight of a telemetry station. Telemetry stations were located so that primary data coverage was near the 80degW meridian and near Hawaii, Singapore, Australia, England, France, Norway, India, Japan, Antarctica, New Zealand, and Central Africa. NASA support of the ISIS project was terminated on October 1, 1979. A significant amount of experimental data, however, was acquired after this date by the Canadian project team. ISIS 2 operations were terminated in Canada on March 9, 1984. The Radio Research Laboratories (Tokyo, Japan) then requested and received permission to reactivate ISIS 2. Regular ISIS 2 operations were started from Kashima, Japan, in early August 1984. ISIS 2 was deactivated effective 24, 1990. A data restoration effort began in the late 1990s and successfully saved a considerable portion of the highresolution data before the telemetry tapes were discarted. The data set was generated from the averaged ionogram binary data (SPIO00318) recorded by the Topside Sounder. The data are obtained with the TOPIST program, which analyzes the data, automatically scales the ionogram traces and resonances, and inverts the traces into an electron density profile. The same program is available for use to handscale the data if desired. Output data items include spacecraft position, electron density profile, assessment of quality, resonance and cutoff frequencies, and both the Otrace and Xtrace.
This data set, provided by the Communications Research Centre (CRC) in Ottawa, Canada, consists of electron density profiles for the ionosphere above the F2 maximum (topside ionosphere). The data were computed from the orginal ionograms using Jackson's method (Jackson, Proceedings of the IEEE., p. 960, June 1969). ISIS1 was launched on 19690130 into an elliptical orbit (5003500km) with an inclination of 88.4 degrees and ISIS2 was launched on 19710401 into an circular orbit at 1400 km with an inclination of 88.1 degrees. Both satellites were fully instrumented ionospheric observatories including sweep and fixedfrequequency ionosondes, a VLF receiver, energetic and soft particle detectors, an ion mass spectrometer, an electrostatic analyzer, an Langmuir probe, a beacon transmitter, a cosmic noise experiment and ISIS 2 also carried two photometers. A tape recorder with 1h capacity was included on both satellites. Data were also collected during overflights of several telemetry stations. The telemetry stations were in areas that provided primary data coverage near the 80degW meridian and in areas near Hawaii, Singapore, Australia, the UK, Norway, India, Japan, Antarctica, New Zealand, and Central Africa.
This 15.36s data set was created in 20089 at GSFC/SPDF from a newly created 320ms data set, with some gaps filled with data from the prior 15.36s data set. Full documentation may be found at ftp://nssdcftp.gsfc.nasa.gov/spacecraft_data/imp/imp8/mag/15s_ascii_v3/00_IMP8_1 5s_data_docum.txt. Creation of the new 320ms and 15.36s data sets was done by N. Papitashvili and J. King, with guidance from Adam Szabo.
Master CDF made 02/16/10 by N. E. Papitashvili, SPDF Modified to revised form v03 on 02/16/10.
..
For detailed documentation on the creation of this data set see ftp://omniweb.gsfc.nasa.gov/imp8/mag/320ms_ascii/cleaned/doc/imp8_mag_320ms_proc .txt
30min avg flex I8 GME
v0.1 (vv01) May/Aug97 orig 30min design V0.2 (vv02) Nov97 split protons into two vars by energies (not needed virvars) V0.3 (vv03) Jul/Aug98 cleaned up var names & set up for virvars V0.4 (vv04) Aug98 defined virvars for alternate views
See online MIT documentation
CDF versions created August 2004
1:time solar wind, 2:time solar wind or magnetosheath, 3:time magnetosheath or magnetospheric
1:Nontracking (NTMS), 2:Tracking (TMS), 3:Acquisition (AQM)
GROUP 1 Satellite Resolution Factor imp8 720 1 Start Time Stop Time 2004 1 00:00 2004 182 24:00 Coord/ Min/Max Range Filter Filter Component Output Markers Minimum Maximum Mins/Maxes GSE X YES       GSE Y YES       GSE Z YES       GSE Lat YES       GSE Lon YES       GSE LT YES       GSM X YES       GSM Y YES       GSM Z YES       GSM Lat YES       GSM Lon YES       Addtnl Min/Max Range Filter Filter Options Output Markers Minimum Maximum Mins/Maxes dEarth YES     Formats and units: Day/Time format: YYYY DDD HH:MM Degrees/Hemisphere format: Decimal degrees with 2 place(s). Longitude 0 to 360, latitude 90 to 90. Distance format: Earth radii with 2 place(s).
Originated 03/14/96
Measurements of spectra and anisotropy of electrons witin energy ranges 2040 keV from two timeofflight detectors EM11 and EM12. The field of view of these detectors are directed oppositely and perpendicular to the satellite rotation axis. Data description: http://www.iki.rssi.ru/inte rball.html
created Sep 1998
No TEXT global attribute value.
created Apr 1997
sensor offset at an angle 180 deg withrespect to the sunward directed spacecraft spin axis
sensor offset at an angle 180 deg withrespect to the sunward directed spacecraft spin axis
sensor offset at an angle 180 deg withrespect to the sunward directed spacecraft spin axis
The value is taken from the sensorthat can scan the angle's interval 45180deg or can be fixed at angles 45, 90,135, 180 deg. with respect to the sunward directed spacecraft spin axis
Count rate of H+, O+ ions in 2 min, three directions, (130 keV) Status flag shows instrument mode. Data description: http://www.iki.rssi.ru/interball.html
created Sep 1998
Full description: http://www.iki.rssi.ru/interball.html Full description: http://www.iki.rssi.ru/interball.html
created May 1997
2 min. average, IMAP
2 min average
Full description: http://www.iki.rssi.ru/interball.html Full description: http://www.iki.rssi.ru/interball.html
created May 1997 edited global attributes Apr 1996
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 14 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 oneyear IBEXHi map data for the first seven years, 20092015, in the form of antiramdirection fluxes with corrections for spacecraft motion (cg: ComptonGetting) but with no corrections (sp) for ENA survival probability between 1 and 100 AU. 3. The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXHi energy bands 26 in numerical data form. Energy channels 26 have FWHM ranges of 0.520.95, 0.841.55, 1.362.50, 1.993.75, 3.136.00 keV, respectively. The corresponding centerpoint energies are 0.71, 1.11, 1.74, 2.73, and 4.29 keV. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: McComas, D. J., et al. (2017), Seven Years of Imaging the Global Heliosphere with IBEX, Astrophys. J. Supp. Ser., 229(2), 41 (32 pp.), 5: http://doi.org/10.3847/15384365/aa66d8 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015); each year is associated with two consecutive maps; Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: This particular data set, denoted in the original ascii files as hvset_noSP_antiram_cg_yearN for N=1,7, includes pixel map data from antiram direction, CG, noSP, 1 year cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Computed from Flux4/sqrt(Fvar4).
Computed from Flux4/sqrt(Fvar4).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Total exposure 4 (s)
Total exposure 4 (s)
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 14 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 sevenyear IBEXHi map data for 20092015, in the form of antiramdirection fluxes with corrections for spacecraft motion (cg: ComptonGetting) but with no corrections (sp) for ENA survival probability between 1 and 100 AU. 3. The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXHi energy bands 26 in numerical data form. Energy channels 26 have FWHM ranges of 0.520.95, 0.841.55, 1.362.50, 1.993.75, 3.136.00 keV, respectively. The corresponding centerpoint energies are 0.71, 1.11, 1.74, 2.73, and 4.29 keV. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: McComas, D. J., et al. (2017), Seven Years of Imaging the Global Heliosphere with IBEX, Astrophys. J. Supp. Ser., 229(2), 41 (32 pp.), 5: http://doi.org/10.3847/15384365/aa66d8 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015); each year is associated with two consecutive maps; Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: This particular data set, denoted in the original ascii files as hvset_noSP_antiram_cg_ single, includes pixel map data from antiram direction, CG, noSP, 7 year cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Computed from Flux4/sqrt(Fvar4).
Computed from Flux4/sqrt(Fvar4).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Total exposure 4 (s)
Total exposure 4 (s)
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 14 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 (6 monthscadence) IBEXHi map data for the first seven years, 20092015, in the form of omnidirectional ENA (hydrogen) fluxes with ComptonGetting correction (cg) of flux spectra for spacecraft motion and no correction (nosp) for ENA survival probability between 1 and 100 AU. 3. The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXHi energy bands 26 in numerical data form. Energy channels 26 have FWHM ranges of 0.520.95, 0.841.55, 1.362.50, 1.993.75, 3.136.00 keV, respectively. The corresponding centerpoint energies are 0.71, 1.11, 1.74, 2.73, and 4.29 keV. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: McComas, D. J., et al. (2017), Seven Years of Imaging the Global Heliosphere with IBEX, Astrophys. J. Supp. Ser., 229(2), 41 (32 pp.), 5: http://doi.org/10.3847/15384365/aa66d8 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015): Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: This particular data set, denoted in the original ascii files as hvset_cg_mapN for N=1,14, includes pixel map data from all directions (omnidirectional), CG, no SP, 6 month cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Computed from Flux4/sqrt(Fvar4).
Computed from Flux4/sqrt(Fvar4).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Total exposure 4 (s)
Total exposure 4 (s)
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 14 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 sevenyear IBEXHi map data for 20092015, in the form of omnidirection fluxes with corrections for spacecraft motion (cg: ComptonGetting) but with no corrections (sp) for ENA survival probability between 1 and 100 AU. 3. The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXHi energy bands 26 in numerical data form. Energy channels 26 have FWHM ranges of 0.520.95, 0.841.55, 1.362.50, 1.993.75, 3.136.00 keV, respectively. The corresponding centerpoint energies are 0.71, 1.11, 1.74, 2.73, and 4.29 keV. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: McComas, D. J., et al. (2017), Seven Years of Imaging the Global Heliosphere with IBEX, Astrophys. J. Supp. Ser., 229(2), 41 (32 pp.), 5: http://doi.org/10.3847/15384365/aa66d8 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015); each year is associated with two consecutive maps; Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: This particular data set, denoted in the original ascii files as hvset_cg_ single, includes pixel map data from omni direction, CG, noSP, 7 year cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Computed from Flux4/sqrt(Fvar4).
Computed from Flux4/sqrt(Fvar4).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Total exposure 4 (s)
Total exposure 4 (s)
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 14 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 oneyear IBEXHi map data for the first seven years, 20092015, in the form of ramdirection fluxes with corrections for spacecraft motion (cg: ComptonGetting) but with no corrections (sp) for ENA survival probability between 1 and 100 AU. 3. The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXHi energy bands 26 in numerical data form. Energy channels 26 have FWHM ranges of 0.520.95, 0.841.55, 1.362.50, 1.993.75, 3.136.00 keV, respectively. The corresponding centerpoint energies are 0.71, 1.11, 1.74, 2.73, and 4.29 keV. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: McComas, D. J., et al. (2017), Seven Years of Imaging the Global Heliosphere with IBEX, Astrophys. J. Supp. Ser., 229(2), 41 (32 pp.), 5: http://doi.org/10.3847/15384365/aa66d8 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015); each year is associated with two consecutive maps; Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: This particular data set, denoted in the original ascii files as hvset_noSP_ram_cg_yearN for N=1,7, includes pixel map data from RAM direction (ramdirection), CG, noSP, 1 year cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Computed from Flux4/sqrt(Fvar4).
Computed from Flux4/sqrt(Fvar4).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Total exposure 4 (s)
Total exposure 4 (s)
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 14 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 sevenyear IBEXHi map data for 20092015, in the form of ramdirection fluxes with corrections for spacecraft motion (cg: ComptonGetting) but with no corrections (sp) for ENA survival probability between 1 and 100 AU. 3. The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXHi energy bands 26 in numerical data form. Energy channels 26 have FWHM ranges of 0.520.95, 0.841.55, 1.362.50, 1.993.75, 3.136.00 keV, respectively. The corresponding centerpoint energies are 0.71, 1.11, 1.74, 2.73, and 4.29 keV. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: McComas, D. J., et al. (2017), Seven Years of Imaging the Global Heliosphere with IBEX, Astrophys. J. Supp. Ser., 229(2), 41 (32 pp.), 5: http://doi.org/10.3847/15384365/aa66d8 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015); each year is associated with two consecutive maps; Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: This particular data set, denoted in the original ascii files as hvset_noSP_ram_cg_ single, includes pixel map data from ram direction, CG, noSP, 7 year cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Computed from Flux4/sqrt(Fvar4).
Computed from Flux4/sqrt(Fvar4).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Total exposure 4 (s)
Total exposure 4 (s)
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 14 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 (1yearcadence) IBEXHi map data for the first seven years, 20092015, in the form of antiRAMdirectional fluxes with corrections for spacecraft motion (cg: ComptonGetting) and with corrections (sp) for ENA survival probability between 1 and 100 AU. 3. The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXHi energy bands 26 in numerical data form. Energy channels 26 have FWHM ranges of 0.520.95, 0.841.55, 1.362.50, 1.993.75, 3.136.00 keV, respectively. The corresponding centerpoint energies are 0.71, 1.11, 1.74, 2.73, and 4.29 keV. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: McComas, D. J., et al. (2017), Seven Years of Imaging the Global Heliosphere with IBEX, Astrophys. J. Supp. Ser., 229(2), 41 (32 pp.), 5: http://doi.org/10.3847/15384365/aa66d8 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015); each year is associated with two consecutive maps; Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: This particular data set, denoted in the original ascii files as hvset_tabular_antiram_cg_yearN for N=1,7, includes pixel map data from antiRAM direction (antiRAMdirectional), CG, SP, 1 year cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Computed from Flux4/sqrt(Fvar4).
Computed from Flux4/sqrt(Fvar4).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Total exposure 4 (s)
Total exposure 4 (s)
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 14 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 sevenyear IBEXHi map data for 20092015, in the form of antiramdirection fluxes with corrections for spacecraft motion (cg: ComptonGetting) and with corrections (sp) for ENA survival probability between 1 and 100 AU. 3. The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXHi energy bands 26 in numerical data form. Energy channels 26 have FWHM ranges of 0.520.95, 0.841.55, 1.362.50, 1.993.75, 3.136.00 keV, respectively. The corresponding centerpoint energies are 0.71, 1.11, 1.74, 2.73, and 4.29 keV. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: McComas, D. J., et al. (2017), Seven Years of Imaging the Global Heliosphere with IBEX, Astrophys. J. Supp. Ser., 229(2), 41 (32 pp.), 5: http://doi.org/10.3847/15384365/aa66d8 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015); each year is associated with two consecutive maps; Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: This particular data set, denoted in the original ascii files as hvset_tabular_antiram_cg_single, includes pixel map data from antiram direction, CG,SP, 7 year cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Computed from Flux4/sqrt(Fvar4).
Computed from Flux4/sqrt(Fvar4).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Total exposure 4 (s)
Total exposure 4 (s)
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 14 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 (6 monthscadence) IBEXHi map data for the first seven years, 20092015, in the form of omnidirectional fluxes with corrections (cg) for spacecraft motion (ComptonGetting) and corrections (sp) for ENA survival probability between 1 and 100 AU. 3. The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXHi energy bands 26 in numerical data form. Energy channels 26 have FWHM ranges of 0.520.95, 0.841.55, 1.362.50, 1.993.75, 3.136.00 keV, respectively. The corresponding centerpoint energies are 0.71, 1.11, 1.74, 2.73, and 4.29 keV. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: McComas, D. J., et al. (2017), Seven Years of Imaging the Global Heliosphere with IBEX, Astrophys. J. Supp. Ser., 229(2), 41 (32 pp.), 5: http://doi.org/10.3847/15384365/aa66d8 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015): Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: This particular data set, denoted in the original ascii files as hvset_cg_tabular_mapN for N=1,14, includes pixel map data from all directions (omnidirectional), CG, SP, 6 month cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Computed from Flux4/sqrt(Fvar4).
Computed from Flux4/sqrt(Fvar4).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Total exposure 4 (s)
Total exposure 4 (s)
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 14 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 sevenyear IBEXHi map data for 20092015, in the form of omnidirection fluxes with corrections for spacecraft motion (cg: ComptonGetting) and with corrections (sp) for ENA survival probability between 1 and 100 AU. 3. The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXHi energy bands 26 in numerical data form. Energy channels 26 have FWHM ranges of 0.520.95, 0.841.55, 1.362.50, 1.993.75, 3.136.00 keV, respectively. The corresponding centerpoint energies are 0.71, 1.11, 1.74, 2.73, and 4.29 keV. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: McComas, D. J., et al. (2017), Seven Years of Imaging the Global Heliosphere with IBEX, Astrophys. J. Supp. Ser., 229(2), 41 (32 pp.), 5: http://doi.org/10.3847/15384365/aa66d8 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015); each year is associated with two consecutive maps; Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: This particular data set, denoted in the original ascii files as hvset_cg_tabular_ single, includes pixel map data from omni direction, CG,SP, 7 year cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Computed from Flux4/sqrt(Fvar4).
Computed from Flux4/sqrt(Fvar4).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Total exposure 4 (s)
Total exposure 4 (s)
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 14 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 (1yearcadence) IBEXHi map data for the first seven years, 20092015, in the form of RAMdirectional fluxes with corrections for spacecraft motion (cg: ComptonGetting) and with corrections (sp) for ENA survival probability between 1 and 100 AU. 3. The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXHi energy bands 26 in numerical data form. Energy channels 26 have FWHM ranges of 0.520.95, 0.841.55, 1.362.50, 1.993.75, 3.136.00 keV, respectively. The corresponding centerpoint energies are 0.71, 1.11, 1.74, 2.73, and 4.29 keV. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: McComas, D. J., et al. (2017), Seven Years of Imaging the Global Heliosphere with IBEX, Astrophys. J. Supp. Ser., 229(2), 41 (32 pp.), 5: http://doi.org/10.3847/15384365/aa66d8 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015); each year is associated with two consecutive maps; Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: This particular data set, denoted in the original ascii files as hvset_tabular_ram_cg_yearN for N=1,7, includes pixel map data from RAM direction (RAMdirectional), CG, SP, 1 year cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Computed from Flux4/sqrt(Fvar4).
Computed from Flux4/sqrt(Fvar4).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Total exposure 4 (s)
Total exposure 4 (s)
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 14 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 sevenyear IBEXHi map data for 20092015, in the form of ramdirection fluxes with corrections for spacecraft motion (cg: ComptonGetting) and with corrections (sp) for ENA survival probability between 1 and 100 AU. 3. The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXHi energy bands 26 in numerical data form. Energy channels 26 have FWHM ranges of 0.520.95, 0.841.55, 1.362.50, 1.993.75, 3.136.00 keV, respectively. The corresponding centerpoint energies are 0.71, 1.11, 1.74, 2.73, and 4.29 keV. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: McComas, D. J., et al. (2017), Seven Years of Imaging the Global Heliosphere with IBEX, Astrophys. J. Supp. Ser., 229(2), 41 (32 pp.), 5: http://doi.org/10.3847/15384365/aa66d8 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015); each year is associated with two consecutive maps; Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: This particular data set, denoted in the original ascii files as hvset_tabular_ram_cg_single, includes pixel map data from ram direction, CG,SP, 7 year cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Computed from Flux4/sqrt(Fvar4).
Computed from Flux4/sqrt(Fvar4).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Total exposure 4 (s)
Total exposure 4 (s)
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 14 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 oneyear IBEXHi map data for the first seven years, 20092015, in the form of antiramdirection fluxes with no corrections for spacecraft motion (nocg: no ComptonGetting) and with no corrections (nosp) for ENA survival probability between 1 and 100 AU. 3. The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXHi energy bands 26 in numerical data form. Energy channels 26 have FWHM ranges of 0.520.95, 0.841.55, 1.362.50, 1.993.75, 3.136.00 keV, respectively. The corresponding centerpoint energies are 0.71, 1.11, 1.74, 2.73, and 4.29 keV. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: McComas, D. J., et al. (2017), Seven Years of Imaging the Global Heliosphere with IBEX, Astrophys. J. Supp. Ser., 229(2), 41 (32 pp.), 5: http://doi.org/10.3847/15384365/aa66d8 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015); each year is associated with two consecutive maps; Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: This particular data set, denoted in the original ascii files as hvset_noSP_antiram_yearN for N=1,7, includes pixel map data from antiram direction, CG, noSP, 1 year cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Computed from Flux4/sqrt(Fvar4).
Computed from Flux4/sqrt(Fvar4).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Total exposure 4 (s)
Total exposure 4 (s)
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 14 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 sevenyear IBEXHi map data for 20092015, in the form of antiramdirection fluxes with no corrections for spacecraft motion (nocg: ComptonGetting) and with no corrections (nosp) for ENA survival probability between 1 and 100 AU. 3. The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXHi energy bands 26 in numerical data form. Energy channels 26 have FWHM ranges of 0.520.95, 0.841.55, 1.362.50, 1.993.75, 3.136.00 keV, respectively. The corresponding centerpoint energies are 0.71, 1.11, 1.74, 2.73, and 4.29 keV. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: McComas, D. J., et al. (2017), Seven Years of Imaging the Global Heliosphere with IBEX, Astrophys. J. Supp. Ser., 229(2), 41 (32 pp.), 5: http://doi.org/10.3847/15384365/aa66d8 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015); each year is associated with two consecutive maps; Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: This particular data set, denoted in the original ascii files as hvset_noSP_antiram_single, includes pixel map data from antiram direction, noCG, noSP, 7 year cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Computed from Flux4/sqrt(Fvar4).
Computed from Flux4/sqrt(Fvar4).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Total exposure 4 (s)
Total exposure 4 (s)
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 14 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 (6 monthscadence) IBEXHi map data for the first seven years, 20092015, in the form of omnidirectional fluxes without any corrections (nocg) for spacecraft motion (ComptonGetting) and ENA survival probability (nosp) between 1 and 100 AU. 3: The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXHi energy bands 26 in numerical data form. Energy channels 26 have FWHM ranges of 0.520.95, 0.841.55, 1.362.50, 1.993.75, 3.136.00 keV, respectively. The corresponding centerpoint energies are 0.71, 1.11, 1.74, 2.73, and 4.29 keV. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: McComas, D. J., et al. (2017), Seven Years of Imaging the Global Heliosphere with IBEX, Astrophys. J. Supp. Ser., 229(2), 41 (32 pp.), 5: http://doi.org/10.3847/15384365/aa66d8 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015): Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: This particular data set, denoted in the original ascii files as hvset_mapN for N=1,14, includes pixel map data from all directions (omnidirectional), no CG, no SP, 6 month cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Computed from Flux4/sqrt(Fvar4).
Computed from Flux4/sqrt(Fvar4).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Total exposure 4 (s)
Total exposure 4 (s)
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 14 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 sevenyear IBEXHi map data for 20092015, in the form of omnidirection fluxes with no corrections for spacecraft motion (nocg: ComptonGetting) and with no corrections (nosp) for ENA survival probability between 1 and 100 AU. 3. The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXHi energy bands 26 in numerical data form. Energy channels 26 have FWHM ranges of 0.520.95, 0.841.55, 1.362.50, 1.993.75, 3.136.00 keV, respectively. The corresponding centerpoint energies are 0.71, 1.11, 1.74, 2.73, and 4.29 keV. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: McComas, D. J., et al. (2017), Seven Years of Imaging the Global Heliosphere with IBEX, Astrophys. J. Supp. Ser., 229(2), 41 (32 pp.), 5: http://doi.org/10.3847/15384365/aa66d8 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015); each year is associated with two consecutive maps; Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: This particular data set, denoted in the original ascii files as hvset_single, includes pixel map data from omni direction, noCG, noSP, 7 year cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Computed from Flux4/sqrt(Fvar4).
Computed from Flux4/sqrt(Fvar4).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Total exposure 4 (s)
Total exposure 4 (s)
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 14 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 oneyear IBEXHi map data for the first seven years, 20092015, in the form of ramdirection fluxes with no corrections for spacecraft motion (nocg: no ComptonGetting) and with no corrections (nosp) for ENA survival probability between 1 and 100 AU. 3. The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXHi energy bands 26 in numerical data form. Energy channels 26 have FWHM ranges of 0.520.95, 0.841.55, 1.362.50, 1.993.75, 3.136.00 keV, respectively. The corresponding centerpoint energies are 0.71, 1.11, 1.74, 2.73, and 4.29 keV. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: McComas, D. J., et al. (2017), Seven Years of Imaging the Global Heliosphere with IBEX, Astrophys. J. Supp. Ser., 229(2), 41 (32 pp.), 5: http://doi.org/10.3847/15384365/aa66d8 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015); each year is associated with two consecutive maps; Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: This particular data set, denoted in the original ascii files as hvset_noSP_ram_yearN for N=1,7, includes pixel map data from antiram direction, CG, noSP, 1 year cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Computed from Flux4/sqrt(Fvar4).
Computed from Flux4/sqrt(Fvar4).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Total exposure 4 (s)
Total exposure 4 (s)
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 14 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 oneyear IBEXHi map data for the first seven years, 20092015, in the form of antiramdirection fluxes with no corrections for spacecraft motion (nocg: no ComptonGetting) and with corrections (sp) for ENA survival probability between 1 and 100 AU. 3. The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXHi energy bands 26 in numerical data form. Energy channels 26 have FWHM ranges of 0.520.95, 0.841.55, 1.362.50, 1.993.75, 3.136.00 keV, respectively. The corresponding centerpoint energies are 0.71, 1.11, 1.74, 2.73, and 4.29 keV. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: McComas, D. J., et al. (2017), Seven Years of Imaging the Global Heliosphere with IBEX, Astrophys. J. Supp. Ser., 229(2), 41 (32 pp.), 5: http://doi.org/10.3847/15384365/aa66d8 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015); each year is associated with two consecutive maps; Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: This particular data set, denoted in the original ascii files as hvset_tabular_noSP_antiram_yearN for N=1,7, includes pixelmap data from anti ramdirection, noCG, SP, 1 year cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Computed from Flux4/sqrt(Fvar4).
Computed from Flux4/sqrt(Fvar4).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Total exposure 4 (s)
Total exposure 4 (s)
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 14 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 sevenyear IBEXHi map data for 20092015, in the form of antiramdirection fluxes with no corrections for spacecraft motion (nocg: ComptonGetting) but with corrections (sp) for ENA survival probability between 1 and 100 AU. 3. The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXHi energy bands 26 in numerical data form. Energy channels 26 have FWHM ranges of 0.520.95, 0.841.55, 1.362.50, 1.993.75, 3.136.00 keV, respectively. The corresponding centerpoint energies are 0.71, 1.11, 1.74, 2.73, and 4.29 keV. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: McComas, D. J., et al. (2017), Seven Years of Imaging the Global Heliosphere with IBEX, Astrophys. J. Supp. Ser., 229(2), 41 (32 pp.), 5: http://doi.org/10.3847/15384365/aa66d8 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015); each year is associated with two consecutive maps; Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: This particular data set, denoted in the original ascii files as hvset_tabular_antiram_single, includes pixel map data from antiram direction, noCG, SP, 7 year cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Computed from Flux4/sqrt(Fvar4).
Computed from Flux4/sqrt(Fvar4).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Total exposure 4 (s)
Total exposure 4 (s)
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 14 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 (6 monthscadence) IBEXHi map data for the first seven years, 20092015, in the form of omnidirectional fluxes with no corrections for spacecraft motion (ComptonGetting) but with corrections (sp) for ENA survival probability between 1 and 100 AU. 3. The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXHi energy bands 26 in numerical data form. Energy channels 26 have FWHM ranges of 0.520.95, 0.841.55, 1.362.50, 1.993.75, 3.136.00 keV, respectively. The corresponding centerpoint energies are 0.71, 1.11, 1.74, 2.73, and 4.29 keV. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: McComas, D. J., et al. (2017), Seven Years of Imaging the Global Heliosphere with IBEX, Astrophys. J. Supp. Ser., 229(2), 41 (32 pp.), 5: http://doi.org/10.3847/15384365/aa66d8 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015): Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: This particular data set, denoted in the original ascii files as hvset_tabular_mapN for N=1,14, includes pixel map data from all directions (omnidirectional), no CG, SP, 6 month cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Computed from Flux4/sqrt(Fvar4).
Computed from Flux4/sqrt(Fvar4).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Total exposure 4 (s)
Total exposure 4 (s)
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 14 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 sevenyear IBEXHi map data for 20092015, in the form of omnidirection fluxes with no corrections for spacecraft motion (nocg: ComptonGetting) but with corrections (sp) for ENA survival probability between 1 and 100 AU. 3. The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXHi energy bands 26 in numerical data form. Energy channels 26 have FWHM ranges of 0.520.95, 0.841.55, 1.362.50, 1.993.75, 3.136.00 keV, respectively. The corresponding centerpoint energies are 0.71, 1.11, 1.74, 2.73, and 4.29 keV. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: McComas, D. J., et al. (2017), Seven Years of Imaging the Global Heliosphere with IBEX, Astrophys. J. Supp. Ser., 229(2), 41 (32 pp.), 5: http://doi.org/10.3847/15384365/aa66d8 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015); each year is associated with two consecutive maps; Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: This particular data set, denoted in the original ascii files as hvset_tabular_single, includes pixel map data from omni direction, noCG, noSP, 7 year cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Computed from Flux4/sqrt(Fvar4).
Computed from Flux4/sqrt(Fvar4).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Total exposure 4 (s)
Total exposure 4 (s)
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 14 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 oneyear IBEXHi map data for the first seven years, 20092015, in the form of ramdirection fluxes with no corrections for spacecraft motion (nocg: no ComptonGetting) and with corrections (sp) for ENA survival probability between 1 and 100 AU. 3. The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXHi energy bands 26 in numerical data form. Energy channels 26 have FWHM ranges of 0.520.95, 0.841.55, 1.362.50, 1.993.75, 3.136.00 keV, respectively. The corresponding centerpoint energies are 0.71, 1.11, 1.74, 2.73, and 4.29 keV. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: McComas, D. J., et al. (2017), Seven Years of Imaging the Global Heliosphere with IBEX, Astrophys. J. Supp. Ser., 229(2), 41 (32 pp.), 5: http://doi.org/10.3847/15384365/aa66d8 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015); each year is associated with two consecutive maps; Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: This particular data set, denoted in the original ascii files as hvset_tabular_noSP_ram_yearN for N=1,7, includes pixelmap data from ramdirection, noCG, SP, 1 year cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Computed from Flux4/sqrt(Fvar4).
Computed from Flux4/sqrt(Fvar4).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Total exposure 4 (s)
Total exposure 4 (s)
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 14 releases of IBEXHI and/or IBEXLO data covering 20092018. 2: This data set is from the IBEXHi Release 12 Count Data for Magnetospheric Imaging. This release provides data for various IBEX orbits from 23 (20090326) to 207b (20130530). The data include 21 orbits from IBEXHi 6degree histogram ENA count data, which is primarily what have been used in IBEX magnetospheric studies. 3. The data consist of IBEXHi Count Data for Magnetospheric Imaging during instrument pointing in spin angle 0  360 degrees between the north and south Ecliptic poles. Spin angle zero corresponds to the north Ecliptic pole. Counts come from IBEXHi energy bands 26 in numerical data form corresponding to energy bins 26: 2) ~0.71, 3) ~1.11, 4) ~1.74, 5) ~2.73, 6) ~4.3 keV. Background counts have not been removed. Counts are separated into 6degree latitudinal bins, with each # angle label representing the center of the bin. Details of the data and enabled science from Release 12 are given in the following journal publications: McComas et al. 2011,2012b; Fuselier et al. 2010, 2015; Petrinec et al. 2011; Ogasawara et al. 2013, 2019; and Dayeh et al. 2015Data Location: http://ibex.swri.edu/ibexpublicdata/Data_Release_12/index.htmlContact: Maher Dayeh, Southwest Research Institute, San Antonio, TX maldayeh@swri.edu Orbit Start and End Times: 23: 20090326 21:09:00.318 to 20090403 16:07:51.743 24: 20090403 12:10:21.253 to 20090411 08:15:09.669 25: 20090411 05:06:40.967 to 20090418 22:05:11.125 27: 20090426 08:27:40.916 to 20090504 05:31:06.519 28: 20090504 02:02:57.673 to 20090511 21:13:47.596 29: 20090511 17:27:02.484 to 20090519 19:27:18.831 51: 20091026 08:19:34.905 to 20091103 02:38:01.730 52: 20091102 22:34:07.792 to 20091110 19:03:55.230 53: 20091110 15:46:22.161 to 20091118 10:58:17.674 55: 20091125 23:44:19.069 to 20091203 11:26:37.151 56: 20091203 08:22:31.792 to 20091210 22:03:52.604 57: 20091210 18:55:33.969 to 20091218 06:58:47.247 72: 20100404 11:17:28.386 to 20100412 09:13:51.008 74: 20100419 14:09:01.851 to 20100427 03:44:14.913 77: 20100512 01:33:51.796 to 20100519 20:43:01.583 78: 20100519 17:33:48.047 to 20100527 13:02:03.396 103: 20101126 07:56:05.324 to 20101204 04:11:44.879 187a: 20121121 00:17:13.430 to 20121125 00:40:26.707 188b: 20121203 12:46:18.859 to 20121208 00:44:50.846 206a: 20130513 23:15:27.433 to 20130517 12:19:58.215 207b: 20130526 12:21:08.868 to 20130530 23:14:44.989 For the first two and a half years of science operations (through Orbit 127), IBEX's orbital period was ~7.5 days and the spin axis was repointed once each orbit (around perigee), leading to bands of sky viewing centered 7.5 apart. In June 2011, over Orbits 128 and 129, IBEX was maneuvered into a previously unknown, longterm stable lunar synchronous orbit with apogee still ~50 RE (McComas et al. 2011a). Since then, IBEX's orbital period has been ~9.1 days (onethird of the lunar sidereal period of 27.3 days). Orbit numbers from 130 onward are split into two segments, 'a' and 'b'. Furthermore, starting in orbit segment 184a, the IBEX team modified the IBEXHi energy step sequence and eliminated the lowest energy step (ESA1) in exchange for doubling the statistical sampling of ESA3 (center energy ~1.1 keV).
The IBEX Release 12 data
Spacecraft location on GSE xaxis for Geocentric Solar Ecliptic coordinate system with xaxis towards Sun and zaxis towards Solar Ecliptic north pole.
Spacecraft location on GSE yaxis for Geocentric Solar Ecliptic coordinate system with xaxis towards Sun and zaxis towards Solar Ecliptic north pole.
Spacecraft location on GSE zaxis for Geocentric Solar Ecliptic coordinate system with xaxis towards Sun and zaxis towards Solar Ecliptic north pole.
Spacecraft Radial distance from Earth in earth radii.
Longitude of Spacecraft Zaxis direction in GSE
Latitude of Spacecraft zaxis direction in GSE
Moon distance [km] from Earth along xaxis towards Sun in Geocentric Solar Ecliptic (GSE) coordinate system.
Moon distance [km] from Earth along yaxis in Geocentric Solar Ecliptic (GSE) coordinate system.
Moon distance [km] from Earth along zaxis in Geocentric Solar Ecliptic (GSE) coordinate system.
Distance of Moon relative to Earth in earth radii.
Spin
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 14 releases of IBEXHI and/or IBEXLO data covering 20092018. 2: This data set is from the Release 13 oneyear IBEXHi map data for the nine years, 20092018, in the form of antiramdirection fluxes with corrections for spacecraft motion (cg: ComptonGetting) but with no corrections (sp) for ENA survival probability between 1 and 100 AU. 3. The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXHi energy bands 26 in numerical data form. Energy channels 26 have FWHM ranges of 0.520.95, 0.841.55, 1.362.50, 1.993.75, 3.136.00 keV, respectively. The corresponding centerpoint energies are 0.71, 1.11, 1.74, 2.73, and 4.29 keV. Details of the data and enabled science from Release 13 are given in the following journal publication: 4: McComas, D. J., et al. (2017), Seven Years of Imaging the Global Heliosphere with IBEX, Astrophys. J. Supp. Ser., 229(2), 41 (32 pp.), 5: http://doi.org/10.3847/15384365/aa66d8 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 13 map numbers (120) with mission year (110), orbits (11431bb), and dates (12/25/200812/26/2018); each year is associated with two consecutive maps; Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 Map 15: year 8, orbits 311a330b, dates 12/24/201506/23/2016 Map 16: year 8, orbits 331a351a, dates 06/24/201612/26/2016 Map 17: year 9, orbits 351b371a, dates 12/26/201606/25/2017 Map 18: year 9, orbits 371b391a, dates 06/25/201712/25/2017 Map 19: year 10, orbits 391a411b, dates 12/25/201706/28/2018 Map 20: year 10, orbits 412a431b, dates 06/29/201812/26/2018 8: This particular data set, denoted in the original ascii files as hvset_noSP_antiram_cg_yearN for N=8, includes pixel map data from antiram direction, CG, noSP, 1 year cadence.
The Release 13 data extend through Map 20 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  20 cover the ten years of data during 20092018.
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Computed from Flux4/sqrt(Fvar4).
Computed from Flux4/sqrt(Fvar4).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Total exposure 4 (s)
Total exposure 4 (s)
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 14 releases of IBEXHI and/or IBEXLO data covering 20092018. 2: This data set is from the Release 13 oneyear IBEXHi map data for the nine years, 20092018, in the form of ramdirection fluxes with corrections for spacecraft motion (cg: ComptonGetting) but with no corrections (sp) for ENA survival probability between 1 and 100 AU. 3. The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXHi energy bands 26 in numerical data form. Energy channels 26 have FWHM ranges of 0.520.95, 0.841.55, 1.362.50, 1.993.75, 3.136.00 keV, respectively. The corresponding centerpoint energies are 0.71, 1.11, 1.74, 2.73, and 4.29 keV. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: McComas, D. J., et al. (2017), Seven Years of Imaging the Global Heliosphere with IBEX, Astrophys. J. Supp. Ser., 229(2), 41 (32 pp.), 5: http://doi.org/10.3847/15384365/aa66d8 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 13 map numbers (120) with mission year (110), orbits (11431bb), and dates (12/25/200812/26/2018); each year is associated with two consecutive maps; Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 Map 15: year 8, orbits 311a330b, dates 12/24/201506/23/2016 Map 16: year 8, orbits 331a351a, dates 06/24/201612/26/2016 Map 17: year 9, orbits 351b371a, dates 12/26/201606/25/2017 Map 18: year 9, orbits 371b391a, dates 06/25/201712/25/2017 Map 19: year 10, orbits 391a411b, dates 12/25/201706/28/2018 Map 20: year 10, orbits 412a431b, dates 06/29/201812/26/2018 8: This particular data set, denoted in the original ascii files as hvset_noSP_ram_cg_yearN for N=8, includes pixel map data from antiram direction, CG, noSP, 1 year cadence.
The Release 13 data extend through Map 20 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  20 cover the ten years of data during 20092018.
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Computed from Flux4/sqrt(Fvar4).
Computed from Flux4/sqrt(Fvar4).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
Total exposure 4 (s)
Total exposure 4 (s)
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 15 releases of IBEXHI and/or IBEXLO data covering 20092018. 2: This data set is derived from the Release 14 threeyear IBEXHi map data with twoyear overlaps to adjacent maps, 20092011, 20102012, 20112013, and so forth through 20152017 from ramdirection fluxes with corrections for spacecraft motion (cg: ComptonGetting) but with no corrections (sp) for ENA survival probability between 1 and 100 AU. The data set parameters include lineofsight (LOS) integrated pressures separately computed from the Global Distributed Flux (GDF), the ribbon flux, and the total of both LOS pressures. Additionally there are signal/noise ratios for the GDF, ribbon, and total pressures. Finally, there are powerlaw slope and values for the GDF differential flux, also including signal/noise of the slope. 3: The data consist of ramdirection sky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for the above parameters. 4: Details of the data and enabled science from Release 14 are given in the following journal publication: Schwadron, N. A., et al. (2018), Time Dependence of the IBEX Ribbon and the Globally Distributed Energetic Neutral Atom Flux Using the First 9 Years of Observations https://iopscience.iop.org /article/10.3847/15384365/aae48e/meta 5: The following codes are used to define dataset types in the multiple IBEX data releases: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 6: This particular dataset denoted in the original ascii files as:  GDFPressure: Globally Distributed Flux LineofSight Integrated Pressure in pdyneau/cm^2  GDFSlope: PowerLaw Slope of the differential flux spectrum for the Globally Distributed Flux  GDFSlopeSN: Signal/Noise ratio of the GDF differential flux powerlaw slope where noise represents uncertainty  GDFSN: Globally Distributed Flux Signal/Noise, where Noise is defined as the uncertainty and the Signal is GDF LineofSight integrated pressure  RibbonPressure: Ribbon LineofSight Integrated Pressure in pdyneau/cm^2  RibbonSN: Ribbon Signal/Noise, where Noise is defined as the uncertainty and the Signal is GDF LineofSight integrated pressure  TotPressure: Total Pressure in ENA maps including both the GDF and Ribbon. LineofSight Integrated Pressure in pdyneau/cm^2  TotSN: Total Pressure SignaltoNoise where noise represents uncertainty and signal represents the total LOSintegrated pressure
The Release 14 data extend through Map 20 and contain modifications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  20 cover the ten years of data during 20092018.
This particular dataset denoted in the original ascii files as ibexdatarelease14/gdfPressure/pmapyrXXXXtoYYYY.txt for XXXX=20092015 and YYYY= .20112017
This particular dataset denoted in the original ascii files as ibexdatarelease14/gdfPressure/pmapyrXXXXtoYYYY.txt for XXXX=20092015 and YYYY= .20112017
This particular dataset denoted in the original ascii files as ibexdatarelease14/gdfPressure/pmapyrXXXXtoYYYY.txt for XXXX=20092015 and YYYY= .20112017
This particular dataset denoted in the original ascii files as ibexdatarelease14/gdfSN/pmapyrXXXXtoYYYY.txt for XXXX=20092015 and YYYY= .20112017
This particular dataset denoted in the original ascii files as ibexdatarelease14/gdfSN/pmapyrXXXXtoYYYY.txt for XXXX=20092015 and YYYY= .20112017
This particular dataset denoted in the original ascii files as ibexdatarelease14/gdfSN/pmapyrXXXXtoYYYY.txt for XXXX=20092015 and YYYY= .20112017
This particular dataset denoted in the original ascii files as ibexdatarelease14/gdfSlope/pmapyrXXXXtoYYYY.txt for XXXX=20092015 and YYYY=20112017
This particular dataset denoted in the original ascii files as ibexdatarelease14/gdfSlope/pmapyrXXXXtoYYYY.txt for XXXX=20092015 and YYYY=20112017
This particular dataset denoted in the original ascii files as ibexdatarelease14/gdfSlope/pmapyrXXXXtoYYYY.txt for XXXX=20092015 and YYYY=20112017
This particular dataset denoted in the original ascii files as ibexdatarelease14/gdfSN/pmapyrXXXXtoYYYYsn.txt for XXXX=20092015 and YYYY=20112017
This particular dataset denoted in the original ascii files as ibexdatarelease14/gdfSN/pmapyrXXXXtoYYYYsn.txt for XXXX=20092015 and YYYY=20112017
This particular dataset denoted in the original ascii files as ibexdatarelease14/gdfSN/pmapyrXXXXtoYYYYsn.txt for XXXX=20092015 and YYYY=20112017
This particular dataset denoted in the original ascii files as ibexdatarelease14/ribbonPressure/rmapyrXXXXtoYYYY.txt for XXXX=20092015 and YYYY=20112017
This particular dataset denoted in the original ascii files as ibexdatarelease14/ribbonPressure/rmapyrXXXXtoYYYY.txt for XXXX=20092015 and YYYY=20112017
This particular dataset denoted in the original ascii files as ibexdatarelease14/ribbonSN/rmapyrXXXXtoYYYY.txt for XXXX=20092015 and YYYY=20112017
This particular dataset denoted in the original ascii files as ibexdatarelease14/ribbonSN/rmapyrXXXXtoYYYY.txt for XXXX=20092015 and YYYY=20112017
This particular dataset denoted in the original ascii files as ibexdatarelease14/totPressure/fluxmapyrXXXXtoYYYY.txt for XXXX=20092015 and YYYY=20112017
This particular dataset denoted in the original ascii files as ibexdatarelease14/totPressure/fluxmapyrXXXXtoYYYY.txt for XXXX=20092015 and YYYY=20112017
This particular dataset denoted in the original ascii files as ibexdatarelease14/totSN/fluxmapyrXXXXtoYYYY.txt for XXXX=20092015 and YYYY=20112017
This particular dataset denoted in the original ascii files as ibexdatarelease14/totSN/fluxmapyrXXXXtoYYYY.txt for XXXX=20092015 and YYYY=20112017
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 15 releases of IBEXHI and/or IBEXLO data covering 20082017. 2: This data set is from the Park et al. (2015) subset of Release 9 for IBEXLo Heavy Neutral Maps data for combination and averaging of sixmonth maps 16 into threeyear maps for each energy channel during 20082011 in the form of counting rates and supporting parameters. 3: The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles from the measured direct events identified as 'Oxygen', which are registered between 50 ns and 100 ns in TOF2; i.e. 50ns<=TOF2<=100ns (Park et al. 2015). Because there are no sputtering, corrections, the 'Oxygen'.events may include O, Ne, and other heavier elements. The single O maps are produced by Pipeline code. There are energy bands 58 in numerical data form. Energy channels 58 have FWHM centerpoint energies at 0.209, 0.439, 0.872, 1.821 keV, respectively. Details of the data and enabled science from this part ofRelease 9 are given in the following journal publication: 4: J. Park et al., Statistical Analysis of the Heavy Neutral Atoms Measured by IBEX. The Astrophysical Journal Supplement Series, 220:34 (13pp), 2015 October. http://dx.doi.org/10.1088/00670049/220/2/34 5. The following list associates Release 9 map numbers (16) with mission year (13), orbits (11150a), and dates (12/25/200812/24/2011): Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 6: The energy resolution is deltaE/E = 0.8 for all channels: Energy channel 1: center energy = 0.015 keV Energy channel 2: center energy = 0.029 keV Energy channel 3: center energy = 0.055 keV Energy channel 4: center energy = 0.11 keV Energy channel 5: center energy = 0.209 keV Energy channel 6: center energy = 0.439 keV Energy channel 7: center energy = 0.872 keV Energy channel 8: center energy = 1.821 keV 7: This particular data set, denoted in the original ascii files as combotm1m6 includes combined IBEXLo heavy neutral pixel maps data (map1 + map2 + map3 + map4 + map5 + map6) from all directions
The Release 9 data contains Maps 1  6. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  6 cover the first three years of data during 20092011.
Computed from Rate5/Rsig5.
Computed from Rate5/Rsig5.
Computed from Rate5/Rsig5.
Computed from Rate5/Rsig5.
Computed from Rate7/Rsig7.
Computed from Rate7/Rsig7.
Computed from Rate8/Rsig8
Computed from Rate8/Rsig8
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 15 releases of IBEXHI and/or IBEXLO data covering 20082017. 2: This data set is from the Park et al. (2015) subset of Release 9 for IBEXLo Heavy Neutral Maps (6 monthscadence) data from combined even maps (2,4,6) during 20092011 in the form of counting rates and supporting parameters. 3: The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles from the measured direct events identified as 'Oxygen', which are registered between 50 ns and 100 ns in TOF2; i.e. 50ns<=TOF2<=100ns (Park et al. 2015). Because there are no sputtering, corrections, the 'Oxygen'.events may include O, Ne, and other heavier elements. The single O maps are produced by Pipeline code. There are energy bands 58 in numerical data form. Energy channels 58 have FWHM centerpoint energies at 0.209, 0.439, 0.872, 1.821 keV, respectively. Details of the data and enabled science from this part ofRelease 9 are given in the following journal publication: 4: J. Park et al., Statistical Analysis of the Heavy Neutral Atoms Measured by IBEX. The Astrophysical Journal Supplement Series, 220:34 (13pp), 2015 October. http://dx.doi.org/10.1088/00670049/220/2/34 4. The following list associates Release 9 map numbers (16) with mission year (13), orbits (11150a), and dates (12/25/200812/24/2011): Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 5: The energy resolution is deltaE/E = 0.8 for all channels: Energy channel 1: center energy = 0.015 keV Energy channel 2: center energy = 0.029 keV Energy channel 3: center energy = 0.055 keV Energy channel 4: center energy = 0.11 keV Energy channel 5: center energy = 0.209 keV Energy channel 6: center energy = 0.439 keV Energy channel 7: center energy = 0.872 keV Energy channel 8: center energy = 1.821 keV 6: This particular data set, denoted in the original ascii files as combotm2m4m6 includes combined IBEXLo heavy neutral pixel even maps data (map2 + map4 + map6) from all directions
The Release 9 data contains Maps 1  6. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  6 cover the first three years of data during 20092011.
Computed from Rate5/Rsig5.
Computed from Rate5/Rsig5.
Computed from Rate5/Rsig5.
Computed from Rate5/Rsig5.
Computed from Rate7/Rsig7.
Computed from Rate7/Rsig7.
Computed from Rate8/Rsig8
Computed from Rate8/Rsig8
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 15 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Park et al. (2015) subset of Release 9 for IBEXLo Heavy Neutral Maps (6 monthscadence) data from combined odd maps (1,3,5) during 20082011 in the form of counting rates and supporting parameters. 3: The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles from the measured direct events identified as 'Oxygen', which are registered between 50 ns and 100 ns in TOF2; i.e. 50ns<=TOF2<=100ns (Park et al. 2015). Because there are no sputtering, corrections, the 'Oxygen'.events may include O, Ne, and other heavier elements. The single O maps are produced by Pipeline code. There are energy bands 58 in numerical data form. Energy channels 58 have FWHM centerpoint energies at 0.209, 0.439, 0.872, 1.821 keV, respectively. Details of the data and enabled science from this part ofRelease 9 are given in the following journal publication: 4: J. Park et al., Statistical Analysis of the Heavy Neutral Atoms Measured by IBEX. The Astrophysical Journal Supplement Series, 220:34 (13pp), 2015 October. http://dx.doi.org/10.1088/00670049/220/2/34 5. The following list associates Release 9 map numbers (16) with mission year (13), orbits (11150a), and dates (12/25/200812/24/2011): Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 6: The energy resolution is deltaE/E = 0.8 for all channels: Energy channel 1: center energy = 0.015 keV Energy channel 2: center energy = 0.029 keV Energy channel 3: center energy = 0.055 keV Energy channel 4: center energy = 0.11 keV Energy channel 5: center energy = 0.209 keV Energy channel 6: center energy = 0.439 keV Energy channel 7: center energy = 0.872 keV Energy channel 8: center energy = 1.821 keV 7: This particular data set, denoted in the original ascii files as combotm1m3m5 includes combined IBEXLo heavy neutral pixel odd maps data (map1 + map3 + map5) from all directions
The Release 9 data contains Maps 1  6. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  6 cover the first three years of data during 20092011.
Computed from Rate5/Rsig5.
Computed from Rate5/Rsig5.
Computed from Rate5/Rsig5.
Computed from Rate5/Rsig5.
Computed from Rate7/Rsig7.
Computed from Rate7/Rsig7.
Computed from Rate8/Rsig8
Computed from Rate8/Rsig8
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 15 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Park et al. (2015) subset of the Release 9 The IBEXLo Heavy Neutral Maps (6 monthscadence) data in the form of direct event counts, counting rates and other supporting data 3: The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles from the measured direct events identified as 'Oxygen', which are registered between 50 ns and 100 ns in TOF2; i.e. 50ns<=TOF2<=100ns (Park et al. 2015). Because there are no sputtering corrections, the 'Oxygen'.events may include O, Ne, and other heavier elements. The single O maps are produced by Pipeline code. There are energy bands 58 in numerical data form. Energy channels 58 have FWHM centerpoint energies at 0.209, 0.439, 0.872, 1.821 keV, respectively. Details of the data and enabled science from Release 9 are given in the following journal publication: 4: J. Park et al., Statistical Analysis of the Heavy Neutral Atoms Measured by IBEX. The Astrophysical Journal Supplement Series, 220:34 (13pp), 2015 October. http://dx.doi.org/10.1088/00670049/220/2/34 5. The following list associates Release 9 map numbers (16) with mission year (13), orbits (11150a), and dates (12/25/200812/24/2011): Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 8: The energy resolution is deltaE/E = 0.8 for all channels: Energy channel 1: center energy = 0.015 keV Energy channel 2: center energy = 0.029 keV Energy channel 3: center energy = 0.055 keV Energy channel 4: center energy = 0.11 keV Energy channel 5: center energy = 0.209 keV Energy channel 6: center energy = 0.439 keV Energy channel 7: center energy = 0.872 keV Energy channel 8: center energy = 1.821 keV 6: This particular data set, denoted in the original ascii files as lvset_o_mapN for N=1,6, includes pixel map data from all directions at 6 month cadence.
The Release 9 data contains Maps 1  6. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Rate5/Rsig5.
Computed from Rate5/Rsig5.
Computed from Rate6/Rsig6
Computed from Rate6/Rsig6
Computed from Rate7/Rsig7
Computed from Rate7/Rsig7
Computed from Rate8/Rsig8
Computed from Rate8/Rsig8
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 15 releases of IBEXHI and/or IBEXLO data covering 20082017. This data set is from the Park et al. (2015) subset of Release 9 for IBEXLo Heavy Neutral Maps, mostly of oxygen, averaged over three years, 20082011, from combination of IBEXLo maps 1 to 6. There are four types of maps derived from different statistical filtering approaches: signal/noise filtering, confidence limit method (CLM), cluster analysis method (CLM), and CLUSTER with signal/noise filtering, all as described in Park et al. (2015). Map data for the first two approaches are in counts/second and for the last two in counts/hour (Cluster ID). 3: The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles from the measured direct events identified as 'Oxygen', which are registered between 50 ns and 100 ns in TOF2; i.e. 50ns<=TOF2<=100ns (Park et al. 2015). Because there are no sputtering, corrections, the 'Oxygen'.events may include O, Ne, and other heavier elements. The single O maps are produced by Pipeline code. There are energy bands 58 in numerical data form. Energy channels 58 have FWHM centerpoint energies at 0.209, 0.439, 0.872, 1.821 keV, respectively. Details of the data and enabled science from this part of Release 9 are given in the following journal publication: 4: J. Park et al., Statistical Analysis of the Heavy Neutral Atoms Measured by IBEX. The Astrophysical Journal Supplement Series, 220:34 (13pp), 2015 October. http://dx.doi.org/10.1088/00670049/220/2/34 5. The following list associates Release 9 map numbers (16) with mission year (13), orbits (11150a), and dates (12/25/200812/24/2011): Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 6: The energy resolution is deltaE/E = 0.8 for all channels: Energy channel 1: center energy = 0.015 keV Energy channel 2: center energy = 0.029 keV Energy channel 3: center energy = 0.055 keV Energy channel 4: center energy = 0.11 keV Energy channel 5: center energy = 0.209 keV Energy channel 6: center energy = 0.439 keV Energy channel 7: center energy = 0.872 keV Energy channel 8: center energy = 1.821 keV 7: This particular data set, denoted in the original ascii files as combotm1m6 includes combined IBEXLo heavy neutral pixel maps data (map1 + map2 + map3 + map4 + map5 + map6) for counting rates from all directions
The Release 9 data contains Maps 1  6. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  6 cover the first three years of data during 20092011.
Count rate filtered by confidence level method (CLM) as per Park et al. (2015)
Count rate filtered by confidence level method (CLM) as per Park et al. (2015)
Count rate filtered by confidence level method (CLM) as per Park et al. (2015)
Count rate filtered by confidence level method (CLM) as per Park et al. (2015)
Count rate filtered by confidence level method (CLM) as per Park et al. (2015)
Count rate filtered by confidence level method (CLM) as per Park et al. (2015)
Count rate filtered by confidence level method (CLM) as per Park et al. (2015)
Count rate filtered by confidence level method (CLM) as per Park et al. (2015)
Count rate filtered by signal/noise ratio (SNR)
Count rate filtered by signal/noise ratio (SNR)
Count Rate filtered by signal/noise ratio (SNR)
Count Rate filtered by signal/noise ratio (SNR)
Count rate filtered by signal/noise ratio (SNR) as per Park et al. (2015).
Count rate filtered by signal/noise ratio (SNR) as per Park et al. (2015).
Count rate filtered by signal/noise ratio (SNR) as per Park et al. (2015)
Count rate filtered by signal/noise ratio (SNR) as per Park et al. (2015)
Count rate filtered by signal/noise ratio (SNR) and confidence level method (CLM)
Count rate filtered by signal/noise ratio (SNR) and confidence level method (CLM)
Count rate filtered by signal/noise ratio (SNR) and confidence level method (CLM)
Count rate filtered by signal/noise ratio (SNR) and confidence level method (CLM)
Count rate filtered by signal/noise ratio (SNR) and confidence level method (CLM)
Count rate filtered by signal/noise ratio (SNR) and confidence level method (CLM)
Count rate filtered by signal/noise ratio (SNR) and confidence level method (CLM)
Count rate filtered by signal/noise ratio (SNR) and confidence level method (CLM)
Count rate filtered by Cluster method as per Park et al. (2015)
Count rate filtered by Cluster method as per Park et al. (2015)
Count rate filtered by Cluster method as per Park et al. (2015)
Count rate filtered by Cluster method as per Park et al. (2015)
Count rate filtered by Cluster method as per Park et al. (2015)
Count rate filtered by Cluster method as per Park et al. (2015)
Count rate filtered by Cluster method as per Park et al. (2015)
Count rate filtered by Cluster method as per Park et al. (2015)
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 15 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 (6 monthscadence) IBEXLo map data for the first seven years, 20092015, in the form of omnidirectional fluxes without any corrections (nocg) for spacecraft motion (ComptonGetting) and ENA survival probability (nosp) between 1 and 100 AU. 3: The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXLo energy bands 58 in numerical data form. Energy channels 58 have FWHM centerpoint energies at 0.209, 0.439, 0.872, 1.821 keV, respectively. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: S.A. Fuselier et al., The IBEXLo Sensor. Space Sci Rev (2009) 146: 117...147; DOI 10.1007/s1121400994958 5: https://link.springer.com/article/10.1007/s1121400994958 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015): Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: The energy resolution is deltaE/E = 0.8 for all channels: Energy channel 1: center energy = 0.015 keV Energy channel 2: center energy = 0.029 keV Energy channel 3: center energy = 0.055 keV Energy channel 4: center energy = 0.11 keV Energy channel 5: center energy = 0.209 keV Energy channel 6: center energy = 0.439 keV Energy channel 7: center energy = 0.872 keV Energy channel 8: center energy = 1.821 keV 9: This particular data set, denoted in the original ascii files as lvset_h_mapN for N=1,14, includes pixel map data from all directions (omnidirectional), no CG, no SP, 6 month cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 15 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 (7yearaverage of 6monthcadence maps) IBEXLo map data for the first seven years, 20092015, in the form of omnidirectional fluxes without any corrections for spacecraft motion (nocg) (ComptonGetting) and with no applied ENA survival probability correction (nosp) between 1 and 100 AU. 3: The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXLo energy bands 58 in numerical data form. Energy channels 58 have FWHM centerpoint energies at 0.209, 0.439, 0.872, 1.821 keV, respectively. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: S.A. Fuselier et al., The IBEXLo Sensor. Space Sci Rev (2009) 146: 117...147; DOI 10.1007/s1121400994958 5: https://link.springer.com/article/10.1007/s1121400994958 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015): Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: The energy resolution is deltaE/E = 0.8 for all channels: Energy channel 1: center energy = 0.015 keV Energy channel 2: center energy = 0.029 keV Energy channel 3: center energy = 0.055 keV Energy channel 4: center energy = 0.11 keV Energy channel 5: center energy = 0.209 keV Energy channel 6: center energy = 0.439 keV Energy channel 7: center energy = 0.872 keV Energy channel 8: center energy = 1.821 keV 9: This particular data set, denoted in the original ascii files as lvset_h_single, includes pixel map data from all directions (omnidirectional), no CG, SP, 7 year cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 15 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 (6 monthscadence) IBEXLo map data for the first seven years, 20092015, in the form of omnidirectional fluxes without any corrections for spacecraft motion (nocg) (ComptonGetting) but with the applied ENA survival probability correction (sp) between 1 and 100 AU. 3: The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXLo energy bands 58 in numerical data form. Energy channels 58 have FWHM centerpoint energies at 0.209, 0.439, 0.872, 1.821 keV, respectively. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: S.A. Fuselier et al., The IBEXLo Sensor. Space Sci Rev (2009) 146: 117...147; DOI 10.1007/s1121400994958 5: https://link.springer.com/article/10.1007/s1121400994958 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015): Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: The energy resolution is deltaE/E = 0.8 for all channels: Energy channel 1: center energy = 0.015 keV Energy channel 2: center energy = 0.029 keV Energy channel 3: center energy = 0.055 keV Energy channel 4: center energy = 0.11 keV Energy channel 5: center energy = 0.209 keV Energy channel 6: center energy = 0.439 keV Energy channel 7: center energy = 0.872 keV Energy channel 8: center energy = 1.821 keV 9: This particular data set, denoted in the original ascii files as lvset_h_tabular_mapN for N=1,14, includes pixel map data from all directions (omnidirectional), no CG, SP, 6 month cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
1: The Interstellar Boundary Explorer (IBEX) has operated in space since 2008 updating our knowledge of the outer heliosphere and its interaction with the local interstellar medium. Starttime: 20081225. There are currently 15 releases of IBEXHI and/or IBEXLO data covering 20092017. 2: This data set is from the Release 10 (7yearaverage of 6monthcadence maps) IBEXLo map data for the first seven years, 20092015, in the form of omnidirectional fluxes without any corrections for spacecraft motion (nocg) (ComptonGetting) but with the applied ENA survival probability correction (sp) between 1 and 100 AU. 3: The data consist of allsky maps in Solar Ecliptic Longitude (east and west) and Latitude angles for ENA (hydrogen) fluxes from IBEXLo energy bands 58 in numerical data form. Energy channels 58 have FWHM centerpoint energies at 0.209, 0.439, 0.872, 1.821 keV, respectively. Details of the data and enabled science from Release 10 are given in the following journal publication: 4: S.A. Fuselier et al., The IBEXLo Sensor. Space Sci Rev (2009) 146: 117...147; DOI 10.1007/s1121400994958 5: https://link.springer.com/article/10.1007/s1121400994958 6. The following codes are used to define dataset types: cg = ComptonGetting corrections have been applied to the data to account for the speed of the spacecraft relative to the direction of arrival of the ENAs. nocg = no ComptonGetting corrections sp = survival probability corrections have been applied to the data to account for the loss of ENAs due to radiation pressure, photoionization and ionization via charge exchange with solar wind protons as they stream through the heliosphere. This correction scales the data out from IBEX at 1 AU to ~100 AU. In the original data this mode is denoted as Tabular. noSP  no survival probability corrections have been applied to the data. omni = data from all directions. ram = data was collected when the spacecraft was ramming into the incoming ENAs. antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 7. The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015): Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 8: The energy resolution is deltaE/E = 0.8 for all channels: Energy channel 1: center energy = 0.015 keV Energy channel 2: center energy = 0.029 keV Energy channel 3: center energy = 0.055 keV Energy channel 4: center energy = 0.11 keV Energy channel 5: center energy = 0.209 keV Energy channel 6: center energy = 0.439 keV Energy channel 7: center energy = 0.872 keV Energy channel 8: center energy = 1.821 keV 9: This particular data set, denoted in the original ascii files as lvset_h_tabular_single, includes pixel map data from all directions (omnidirectional), no CG, SP, 7 year cadence.
The Release 10 data extend through Map 14 and contain modications and updates of Maps 12 from Release 2, Maps 16 from Release 4, and Maps 110 from Release 7. The present CDF data set was converted from the originally archived data in ascii list format but otherwise includes no changes in the data. The original data are given in 30 rows for Solar Ecliptic Latitude and 60 columns for Solar Ecliptic East Longitude. The accompanying documentation described the row latitude data as starting from the north Ecliptic pole (+90 degrees) and decreasing in value to the south Ecliptic pole (90 degrees). During preparation of the data set in CDF format, SPDF discovered that the correct order was increasing from row 1 for the South Ecliptic pole to row 30 for the north Ecliptic pole. East longitude is defined correctly for the column order but we have instead used west longitude to better represent the outwardlooking viewpoint from IBEX to the outer heliosphere as typically used in IBEX team plots.
Maps 1  14 cover the first seven years of data during 20092015.
Computed from Flux5/sqrt(Fvar5).
Computed from Flux5/sqrt(Fvar5).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux6/sqrt(Fvar6).
Computed from Flux6/sqrt(Fvar6).
Fllux Variance is the square of standard deviation Sigma
Fllux Variance is the square of standard deviation Sigma
Computed from Flux2/sqrt(Fvar2).
Computed from Flux2/sqrt(Fvar2).
Flux Variance is the square of standard deviation Sigma
Flux Variance is the square of standard deviation Sigma
Computed from Flux3/sqrt(Fvar3).
Computed from Flux3/sqrt(Fvar3).
Flux Variance is the square of standard deviation Sigma.
Flux Variance is the square of standard deviation Sigma.
ICON explores the boundary between Earth and space (the ionosphere) to understand the physical connection between our world and the immediate space environment around us. Visit http://icon.ssl.berkeley.edu for more details.
Geodetic Altitude of Spacecraft in WGS84.
Determined via a nonlinear least squares fit of RPA currents to the Whipple equation
Determined via a nonlinear least squares fit of RPA currents to the Whipple equation
Geodetic latitude of spacecraft in WGS84
Local Solar Time at spacecraft.
Magnetic Local Time at the spacecraft.
Geodetic longitude of spacecraft in WGS84
Ion density uses measured currents and corotating atmosphere to determine density.
Temperature is obtained by assuming single temperature value for all plasma.
Ion velocity relative to corotation along geomagnetic field lines. Positive along the main field vector. Velocity obtained using ion velocities relative to corotation in the instrument frame along with the corresponding unit vectors expressed in the instrument frame to express the observed vector along a geomagnetic basis.
Ion velocity along local magnetic meridional direction, perpendicular to geomagnetic field and within local magnetic meridional plane. The local meridional vector maps to vertical at the magnetic equator, positive is up. Velocity obtained using ion velocities relative to corotation in the instrument frame along with the corresponding unit vectors expressed in the instrument frame to express the observed vector along a geomagnetic basis.
Crosstrack velocity is relative to corotation and in the instrument frame. Positivex is normal to IVM aperture plane and in the direction of satellite motion. Velocity obtained through fitting of RPA currents to the Whipple equation to get a measure of the total along track ion velocity as observed within the instrument. Signals produced by the motion of the spacecraft and the rotation of the Earth are removed to produce this result. Mean offset of 0.0 added by R. A. Heelis.
Crosstrack velocity is relative to corotation and in the instrument frame. Positivey points generally southward when the instrument is pointed along the ram direction. Velocity obtained through conversion of arrival angles measured by the DM into a cross track velocity using trigonometry. Signals produced by the motion of the spacecraft and the rotation of the Earth are removed to produce this result. Mean offset of 0.0 added by R. A. Heelis.
Crosstrack velocity is relative to corotation and in the instrument frame. Positivez is directed towards nadir (Earth). Velocity obtained through conversion of arrival angles measured by the DM into a cross track velocity using trigonometry. Signals produced by the motion of the spacecraft and the rotation of the Earth are removed to produce this result. Mean offset of 0.0 added by R. A. Heelis.
Ion velocity relative to corotation along the magnetic zonal direction, normal to local magnetic meridional plane and the geomagnetic field (positive east). The local zonal vector maps to purely horizontal at the magnetic equator. Velocity obtained using ion velocities relative to corotation in the instrument frame along with the corresponding unit vectors expressed in the instrument frame to express the observed vector along a geomagnetic basis.
This is the total ion velocity along normal direction into the RPA, including s/c motion.
Total observed ion velocity along instrument crosstrack direction, reported in the instrument frame. The translation of DM measured angles to ion velocities uses knowledge of the ram velocity of the plasma and the electric potential of the instrument aperture relative to the ambient plasma, both of which are provided by the RPA.
Total observed ion velocity along instrument crosstrack direction, reported in the instrument frame. The translation of DM measured angles to ion velocities uses knowledge of the ram velocity of the plasma and the electric potential of the instrument aperture relative to the ambient plasma, both of which are provided by the RPA.
The meridional unit vector is perpendicular to the geomagnetic field and maps along magnetic field lines to vertical at the magnetic equator, where positive is up. The unit vector is expressed here in the IVM coordinate system, where x is along the IVM boresight, nominally along ram when in standard pointing. Calculated using the corresponding unit vector in ECEF and the orientation of the IVM also expressed in ECEF (sc_*hat_*).
The meridional unit vector is perpendicular to the geomagnetic field and maps along magnetic field lines to vertical at the magnetic equator, where positive is up. The unit vector is expressed here in the IVM coordinate system, where Y = Z x X, nominally southward when in standard pointing, X along ram. Calculated using the corresponding unit vector in ECEF and the orientation of the IVM also expressed in ECEF (sc_*hat_*).
The meridional unit vector is perpendicular to the geomagnetic field and maps along magnetic field lines to vertical at the magnetic equator, where positive is up. The unit vector is expressed here in the IVM coordinate system, where Z is nadir pointing (towards Earth), when in standard pointing, X along ram. Calculated using the corresponding unit vector in ECEF and the orientation of the IVM also expressed in ECEF (sc_*hat_*).
Incident plasma will have some potential to the IVM aperture plane. The aperture plane voltage matches that of a conductor allowed to float electrically with respect to the spacecraft. The flux of ions (driven by s/c motion) must be balanced by the flux of electrons (driven by electron temperature). The value of the aperture plane potential evolves naturally to limit the collection of electrons such the net flux is zero.
The fieldaligned vector points along the geomagnetic field, with positive values along the field direction, and is expressed here in the IVM instrument frame. The IVMx direction points along the instrument boresight, which is pointed into ram for standard operations.Calculated using the corresponding unit vector in ECEF and the orientation of the IVM also expressed in ECEF (sc_*hat_*).
The fieldaligned vector points along the geomagnetic field, with positive values along the field direction. The unit vector is expressed here in the IVM coordinate system, where Y = Z x X, nominally southward when in standard pointing, X along ram. Calculated using the corresponding unit vector in ECEF and the orientation of the IVM also expressed in ECEF (sc_*hat_*).
The fieldaligned vector points along the geomagnetic field, with positive values along the field direction, and is expressed here in the IVM instrument frame. The IVMZ direction points towards nadir when IVMX is pointed into ram for standard operations.Calculated using the corresponding unit vector in ECEF and the orientation of the IVM also expressed in ECEF (sc_*hat_*).
The zonal vector is perpendicular to the local magnetic field and the magnetic meridional plane. The zonal vector maps to purely horizontal at the magnetic equator, with positive values pointed generally eastward. This vector is expressed here in the IVM instrument frame.The IVMx direction points along the instrument boresight, which is pointed into ram for standard operations.Calculated using the corresponding unit vector in ECEF and the orientation of the IVM also expressed in ECEF (sc_*hat_*).
The zonal vector is perpendicular to the local magnetic field and the magnetic meridional plane. The zonal vector maps to purely horizontal at the magnetic equator, with positive values pointed generally eastward. The unit vector is expressed here in the IVM coordinate system, where Y = Z x X, nominally southward when in standard pointing, X along ram. Calculated using the corresponding unit vector in ECEF and the orientation of the IVM also expressed in ECEF (sc_*hat_*).
The zonal vector is perpendicular to the local magnetic field and the magnetic meridional plane. The zonal vector maps to purely horizontal at the magnetic equator, with positive values pointed generally eastward. This vector is expressed here in the IVM instrument frame.The IVMZ direction points towards nadir when IVMX is pointed into ram for standard operations.Calculated using the corresponding unit vector in ECEF and the orientation of the IVM also expressed in ECEF (sc_*hat_*).
If the magnetic torquers are active during any part of the measurement, it is recorded as active for whole measurement. Decoded from spacecraft housekeeping file: ICON_L0_Spacecraft_HousekeepingMTB_20200305_v01r000.CSV
Data is from predictive ephemeris. 0 = spacecraft in Sun, 1 = spacecraft in Earth Shadow.
Standarized for several missions, not all codes are relevant for ICON where 1: Earth Shadow 2: Lunar Shadow 4: Atmospheric Absorption Zone 8: South Atlantic Anomaly 16: Northern Auroral Zone 32: Southern Auroral Zone 64: Periapsis Passage 128: Inner & Outer Radiation Belts 256: Deep Plasma Sphere 512: Foreshock Solar Wind 1024: Solar Wind Beam 2048: High Magnetic Field 4096: Average Plasma Sheet 8192: Bowshock Crossing 16384: Magnetopause Crossing 32768: Ground Based Observatories 65536: 2Day Conjunctions 131072: 4Day Conjunctions 262144: Time Based Conjunctions 524288: Radial Distance Region 1 1048576: Orbit Outbound 2097152: Orbit Inbound 4194304: Lunar Wake 8388608: Magnetotail 16777216: Magnetosheath 33554432: Science 67108864: Low Magnetic Latitude 134217728: Conjugate Observation
Binary Coded Integer where 1: LVLH Normal Mode 2: LVLH Reverse Mode 4: Earth Limb Pointing 8: Inertial Pointing 16: Stellar Pointing 32: Attitude Slew 64: Conjugate Maneuver 128: Nadir Calibration 256: Lunar Calibration 512: Stellar Calibration 1024: Zero Wind Calibration 204832768: SPARE
Integer Orbit Number.
Quasidipole magnetic latitude of the spacecraft position. These values are obtained from passing the geodectic latitudes, longitudes, and altitudes from ICON_ANCILLARY_IVM_LATITUDE, ICON_ANCILLARY_IVM_LONGITUDE, and ICON_ANCILLARY_IVM_ALTITUDE into apexpy Python module. For details on apexpy see: https://apexpy.readthedocs.org/
Quasidipole magnetic longitude of the spacecraft position. These values are obtained from passing the geodectic latitudes, longitudes, and altitudes from ICON_ANCILLARY_IVM_LATITUDE, ICON_ANCILLARY_IVM_LONGITUDE, and ICON_ANCILLARY_IVM_ALTITUDE into apexpy Python module. For details on apexpy see: https://apexpy.readthedocs.org/
Drift meter quality flag. 0  Good data. 1  Data may have artifacts due to s/c operations. 2  Data temporarily removed for photoemission. 3  Not enough O+ to measure arrival angle.
Status flag for RPA. 0  All RPA parameters are good. Ion temperatures correspond to both O+ and H+. 1  Ram Ion Velocities are not good. Other parameters good. Plasma is presumed to be corotating when fitting RPA curves that have an insufficient quantity of O+. Ion temperatures correspond to H+ only. 2  Geophysical outputs may be impacted by spacecraft operations.
Modified APEX height of the spacecraft position.
Milliseconds since 19800106 00:00:00 TAI (coincident with UTC) at middle of reading. Time is generated from the timecode at byte 1015 of the IVM packet minus the time sync at byte 1019 of the IVM packet. This is the GPS time at the start of the integration period. The integration period is assumed to be 4 seconds so the center time is 2 seconds after that. The formula is (timecode * 1000ms) + 2000ms  (16 * time sync / 1000) in GPS milliseconds then converted to UTC time. See the UTD 206024 Rev A document. Time may be delayed by up to 10 ms due to FSW polling delay. Maximum time is ~2150 UTC and minimum time is ~1970 UTC.
Binary Coded Integer where 1: Earth Day View 2: Earth Night View 4: Calibration Target View 8: Offtarget View 16: Sun Proximity View 32: Moon Proximity View 64: North Magnetic Footpoint View 128: South Magnetic Footpoint View 256: Science Data Collection View 512: Calibration Data Collection View 1024: RAM Proximity View 204832768: SPARE Activity is what the spacecraft was commanded to do while status is the spacecraft's natural state of operations. This means that activity should always be used over status if they differ, but will almost always be the same.
Binary Coded Integer where 1: Earth Day View 2: Earth Night View 4: Calibration Target View 8: Offtarget View 16: Sun Proximity View 32: Moon Proximity View 64: North Magnetic Footpoint View 128: South Magnetic Footpoint View 256: Science Data Collection View 512: Calibration Data Collection View 1024: RAM Proximity View 204832768: SPARE Activity is what the spacecraft was commanded to do while status is the spacecraft's natural state of operations. This means that activity should always be used over status if they differ, but will almost always be the same.
Binary Coded Integer where: 1: Earth Day View 2: Earth Night View 4: Calibration Target View 8: Offtarget View 16: Sun Proximity View 32: Moon Proximity View 64: North Magnetic Footpoint View 128: South Magnetic Footpoint View 256: Science Data Collection View 512: Calibration Data Collection View 1024: RAM Proximity View 204832768: SPARE Activity is what the spacecraft was commanded to do while status is the spacecraft's natural state of operations. This means that activity should always be used over status if they differ, but will almost always be the same.
Binary Coded Integer where: 1: Earth Day View 2: Earth Night View 4: Calibration Target View 8: Offtarget View 16: Sun Proximity View 32: Moon Proximity View 64: North Magnetic Footpoint View 128: South Magnetic Footpoint View 256: Science Data Collection View 512: Calibration Data Collection View 1024: RAM Proximity View 204832768: SPARE Activity is what the spacecraft was commanded to do while status is the spacecraft's natural state of operations. This means that activity should always be used over status if they differ, but will almost always be the same.
Altitude location of the magnetic footpoint in the Northern Hemisphere at 150 km. These data were interpolated using a tricubic algorithm from IGRF and ephemeris data then linearly interploted to IVM times.
At the northern footpoint this is the xcomponent of the unit vector for field aligned ion drifts expressed in the ECEF frame.
At the northern footpoint this is the ycomponent of the unit vector for field aligned ion drifts expressed in the ECEF frame.
At the northern footpoint this is the zcomponent of the unit vector for field aligned ion drifts expressed in the ECEF frame.
Latitude location of the magnetic footpoint in the Northern Hemisphere at 150 km. These data were interpolated using a tricubic algorithm from IGRF and ephemeris data then linearly interploted to IVM times.
Longitude location of the magnetic footpoint in the Northern Hemisphere at 150 km. These data were interpolated using a tricubic algorithm from IGRF and ephemeris data then linearly interploted to IVM times.
Velocity along local magnetic meridional direction, perpendicular to geomagnetic field and within local magnetic meridional plane, fieldline mapped to northern footpoint. The meridional vector is purely vertical at the magnetic equator, positive up. Velocity obtained using ion velocities relative to corotation in the instrument frame along with the corresponding unit vectors expressed in the instrument frame. Fieldline mapping and the assumption of equipotential field lines is used to translate the locally measured ion motion to the magnetic footpoint. The mapping is used to determine the change in magnetic field line distance, which, under assumption of equipotential field lines, in turn alters the electric field at that location (E=V/d).
Calculated value of quasidipole latitude of northern footpoint from IGRF.
Calculated value of quasidipole longitude of northern footpoint from IGRF
At the northern footpoint this is the xcomponent of the unit vector for meridional ion drifts expressed in the ECEF frame.
At the northern footpoint this is the ycomponent of the unit vector for meridional ion drifts expressed in the ECEF frame.
At the northern footpoint this is the zcomponent of the unit vector for meridional ion drifts expressed in the ECEF frame.
Velocity along local magnetic zonal direction, perpendicular to geomagnetic field and the local magnetic meridional plane, fieldline mapped to northern footpoint. The zonal vector is purely horizontal when mapped to the magnetic equator, positive is generally eastward. Velocity obtained using ion velocities relative to corotation in the instrument frame along with the corresponding unit vectors expressed in the instrument frame. Fieldline mapping and the assumption of equipotential field lines is used to translate the locally measured ion motion to the northern footpoint. The mapping is used to determine the change in magnetic field line distance, which, under assumption of equipotential field lines, in turn alters the electric field at that location (E=V/d).
At the northern footpoint this is the xcomponent of the unit vector for zonal ion drifts expressed in the ECEF frame.
At the northern footpoint this is the ycomponent of the unit vector for zonal ion drifts expressed in the ECEF frame.
At the northern footpoint this is the zcomponent of the unit vector for zonal ion drifts expressed in the ECEF frame.
Altitude location of the magnetic footpoint in the Northern Hemisphere at 150 km. These data were interpolated using a tricubic algorithm from IGRF and ephemeris data then linearly interploted to IVM times.
At the Southern footpoint this is the xcomponent of the unit vector for field aligned ion drifts expressed in the ECEF frame.
At the Southern footpoint this is the ycomponent of the unit vector for field aligned ion drifts expressed in the ECEF frame.
At the Southern footpoint this is the zcomponent of the unit vector for field aligned ion drifts expressed in the ECEF frame.
Latitude location of the magnetic footpoint in the Southern Hemisphere at 150 km. These data were interpolated using a tricubic algorithm from IGRF and ephemeris data then linearly interploted to IVM times.
Longitude location of the magnetic footpoint in the Southern Hemisphere at 150 km. These data were interpolated using a tricubic algorithm from IGRF and ephemeris data then linearly interploted to IVM times.
Velocity along local magnetic meridional direction, perpendicular to geomagnetic field and within local magnetic meridional plane, fieldline mapped to southern footpoint. The meridional vector is purely vertical at the magnetic equator, positive up. Velocity obtained using ion velocities relative to corotation in the instrument frame along with the corresponding unit vectors expressed in the instrument frame. Fieldline mapping and the assumption of equipotential field lines is used to translate the locally measured ion motion to the magnetic footpoint. The mapping is used to determine the change in magnetic field line distance, which, under assumption of equipotential field lines, in turn alters the electric field at that location (E=V/d).
Calculated value of quasidipole latitude of southern footpoint from IGRF
Calculated value of quasidipole longitude of southern footpoint from IGRF
At the Southern footpoint this is the xcomponent of the unit vector for meridional ion drifts expressed in the ECEF frame.
At the Southern footpoint this is the ycomponent of the unit vector for meridional ion drifts expressed in the ECEF frame.
At the Southern footpoint this is the zcomponent of the unit vector for meridional ion drifts expressed in the ECEF frame.
Velocity along local magnetic zonal direction, perpendicular to geomagnetic field and the local magnetic meridional plane, fieldline mapped to southern footpoint. The zonal vector is purely horizontal when mapped to the magnetic equator, positive is generally eastward. Velocity obtained using ion velocities relative to corotation in the instrument frame along with the corresponding unit vectors expressed in the instrument frame. Fieldline mapping and the assumption of equipotential field lines is used to translate the locally measured ion motion to the southern footpoint. The mapping is used to determine the change in magnetic field line distance, which, under assumption of equipotential field lines, in turn alters the electric field at that location (E=V/d).
At the Southern footpoint this is the xcomponent of the unit vector for zonal ion drifts expressed in the ECEF frame.
At the Southern footpoint this is the ycomponent of the unit vector for zonal ion drifts expressed in the ECEF frame.
At the Southern footpoint this is the zcomponent of the unit vector for zonal ion drifts expressed in the ECEF frame.
Xcomponent of the magnetic field from IGRF at the spacecarft position, expressed in the ECEF frame.
Ycomponent of the magnetic field from IGRF at the spacecarft position, expressed in the ECEF frame.
Zcomponent of the magnetic field from IGRF at the spacecarft position, expressed in the ECEF frame.
Velocity along local magnetic meridional direction, perpendicular to geomagnetic field and within local magnetic meridional plane, fieldline mapped to apex/magnetic equator. The meridional vector is purely vertical at the magnetic equator, positive up. Velocity obtained using ion velocities relative to corotation in the instrument frame along with the corresponding unit vectors expressed in the instrument frame. Fieldline mapping and the assumption of equipotential field lines is used to translate the locally measured ion motion to the magnetic equator. The mapping is used to determine the change in magnetic field line distance, which, under assumption of equipotential field lines, in turn alters the electric field at that location (E=V/d).
Velocity along local magnetic zonal direction, perpendicular to geomagnetic field and the local magnetic meridional plane, fieldline mapped to apex/magnetic equator. The zonal vector is purely horizontal when mapped to the magnetic equator, positive is generally eastward. Velocity obtained using ion velocities relative to corotation in the instrument frame along with the corresponding unit vectors expressed in the instrument frame. Fieldline mapping and the assumption of equipotential field lines is used to translate the locally measured ion motion to the magnetic equator. The mapping is used to determine the change in magnetic field line distance, which, under assumption of equipotential field lines, in turn alters the electric field at that location (E=V/d).
Velocity of spacecraft in ECI, J2000, cooridinates.
Velocity of spacecraft in ECI, J2000, cooridinates.
Velocity of spacecraft in ECI, J2000, cooridinates.
Component of Earth's corotation velocity vector projected into the IVM instrument axes by taking the dot product of the corotation vector with the instrument's axes and multiplying the Y and Z components by negative 1 (but not the X component by convention).
Component of Earth's corotation velocity vector projected into the IVM instrument axes by taking the dot product of the corotation vector with the instrument's axes and multiplying the Y and Z components by negative 1 (but not the X component by convention).
Component of Earth's corotation velocity vector projected into the IVM instrument axes by taking the dot product of the corotation vector with the instrument's axes and multiplying the Y and Z components by negative 1 (but not the X component by convention).
Solar Zenith Angle at the spacecraft.
References: 1.Troshichev O.A. et al, Planet.Space Sci., 36, 1095, 1988. 2.Vennerstrom S. et al, Report UAG103, World Data Center A for STP, Boulder, April 1994 PCindex is an empirical magnetic activity index based on data from single nearpole station (Thule or Vostok for N or S hemispheres, respectively). Its derivation procedure is optimized to achieve the best correlation of PCindex with the solar wind electric field (SWEF) magnitude ( v*B*sin(teta/2)**2 ). The averaged horizontal magnetic disturbance vector (quiet value subtracted) is projected onto the optimal direction (defined empirically for each UT hour and each season based on the best correlation with the SWEF) and, after normalization to the equivalent value of SWEF, it gives the PCindex (expressed in mV/m). Although PCindex is formally expressed in mV/m, it actually represents the measure of magnetic activity, the normalization procedure (to SWEF) helps to reduce the seasonal/diurnal effects to facilitate the intercomparison. The resolution of the northern cap PCindex is 5 min and of the one from southern cap  15 min. However, one time scale with the 5 min step is used for both indices and each 15 min averaged value of southern index is, hence, repeated for three times. Full description: http://www.iki.rssi.ru/interball.html
created May 1996
15 min averaged value of southern index is repeated for three times.
5 min. resolution
Katus, R. M., D. L. Gallagher, M. W. Liemohn,A. M. Keesee, and L. K. Sarno?Smith (2015), Statistical storm time examination of MLT dependent plasmapause location derived from IMAGE EUV,J. Geophys. Res. Space Physics, 120, 5545?5559, doi:10.1002/2015JA021225.
The electron density values listed in this file are derived from the IMAGE Radio Plasma Imager (B.W. Reinisch, PI) data using an automatic fitting program written by Phillip Webb with manual correction. The electron number densities were produced using an automated procedure (with manual correction when necessary) which attempted to selfconsistently fit an enhancement in the IMAGE RPI Dynamic Spectra to either 1) the Upper Hybrid Resonance band, 2) the Zmode or 3) the continuum edge. The automatic algorithm works by rules determined by comparison of the active and passive RPI data [Benson et al., GRL, vol. 31, L20803, doi:10.1029/2004GL020847, 2004]. The manual data points are not from frequencies chosen freely by a human. Rather the human specifies that the computer should search for a peak or continuum edge in a certain frequency region. Thus even the manual points are determined, in part, by the automatic algorithms. Of course that does not guarantee that the data points are right, but it does eliminate some human bias.
Satellite location in SM coordinates in Re (1 RE=6378.14 km)
Satellite location in SM coordinates in Re (1 RE=6378.14 km)
Satellite location in SM coordinates in Re (1 RE=6378.14 km)
Model electron cyclotron frequency in kHz. T96 model is used for the background magnetic field, which requires the solar wind dynamic pressure, IMF Bz, and the DST index as input.If these parameters were not available, default values of solar wind pressure of 2.1 nPa, IMF Bz of 0 nT, and DST of 10 nT were used
The electron number densities were derived from an automated procedure (with manual correction when necessary) which attempted to selfconsistently fit an enhancement in the IMAGE RPI Dynamic Spectra to either 1) the Upper Hybrid Resonance band, 2) the Zmode or 3) the continuum edge.
tbs
tbs
tbs
tbs
tbs
tbs
tbs
tbs
tbs
tbs
tbs
tbs
The logical_file_id stores the name of the CDF file using the ISTP naming convention (source_name / data_type / descriptor / date / data_version).im_l1_euv_00000000_v01
This is a virtual variable computed in read_myCDF
Geo = geographic coordinates
GSM = geocentric solar magnetospheric coordinates
No TEXT global attribute value.
No TEXT global attribute value.
No TEXT global attribute value.
The logical_file_id stores the name of the CDF file using the ISTP naming convention (source_name / data_type / descriptor / date / data_version).im_k0_rpi_00000000_v01
Master with plasmagram vv's reintegrated with data CDFs 12/6/00 REM; SKTEditor review and corrections applied to master 12/6/00 REM;
TBD
TBD
TBD
TBD
TBD
TBD
TBD
TBD
TBD
TBD
TBD
TBD
Most probable amplitude
TBD
Detailed plasmagram picture has the original number of frequencies as specified by RPI measurement parameters. Frequency axis varies from plasmagram to plasmagram. Plasmagram *thumbnails* have a fixed frequency axis. The original plasmagram data often requires transformation into thumbnail format by averaging.
TBD
Number of Ranges, depending on program setting and processing.
Range readings
electrons SKT version 24July2000 Mende et al: Far Ultraviolet Imaging from the IMAGE Spacecraft,Space Sciences Review 1999
direction of true spin axis at WIC Snapshot Time
direction of true spin axis at WIC Snapshot Time
direction of true spin axis at WIC Snapshot Time
Spacecraft Position at Snapshot Time
Spacecraft Position at Snapshot Time
Spacecraft Position at Snapshot Time
(Phi) flight software uses 315, analysis uses 45
(Theta)
(Omega)
Protons SKT version 24July2000 Mende et al: Far Ultraviolet Imaging from the IMAGE Spacecraft,Space Sciences Review 1999
direction of true spin axis at WIC Snapshot Time
direction of true spin axis at WIC Snapshot Time
direction of true spin axis at WIC Snapshot Time
Spacecraft Position at Snapshot Time
Spacecraft Position at Snapshot Time
Spacecraft Position at Snapshot Time
(Phi) flight software uses 315, analysis uses 45
(Theta)
(Omega)
No TEXT global attribute value.
REM  reset validmin to 250 on 11/29/00; LBH=LymanBirgeHopfield
REM  reset validmin to 250 on 11/29/00
REM  reset validmin to 250 on 11/29/00
REM  reset validmin to 250 on 11/29/00; LBH=LymanBirgeHopfield
REM  reset validmin to 250 on 11/29/00
direction of true spin axis at WIC Snapshot Time
direction of true spin axis at WIC Snapshot Time
direction of true spin axis at WIC Snapshot Time
Spacecraft Position at Snapshot Time
Spacecraft Position at Snapshot Time
Spacecraft Position at Snapshot Time
(Phi) flight software uses 315, analysis uses 45
(Theta)
(Omega)
The logical_file_id stores the name of the CDF file using the ISTP naming convention (source_name / data_type / descriptor / date / data_version).im_k1_rpi_00000000_v01
TBD
TBD
TBD
TBD
TBD
Detailed plasmagram picture has the original number of frequencies as specified by RPI measurement parameters. Frequency axis varies from plasmagram to plasmagram. Plasmagram *thumbnails* have a fixed frequency axis. The original plasmagram data often requires transformation into thumbnail format by averaging.
TBD
tbs
tbs
tbs
tbs
No TEXT global attribute value.
These files provides access to a field/plasmamerged 2min ISEE3 data setcreated at NSSDC as part of preparing ISEE3 data for new OMNI. Input to the data set were 1min MAG magnetic field data, 24splasma data, and daily spacecraft position data, all obtained from theftp://spdf.gsfc.nasa.gov/pub/data/isee/isee3/ from which needed documentation may be found. The annual files of this ASCII data set may be accessed at FTP siteftp://spdf.gsfc.nasa.gov/pub/data/isee/isee3/2_min_merged_mag_plasma/as well. Time span: Mag field: 19780911  19821012 Plasma: 19780911  19800219 Note that Magntic Field is given in SE Spacecraftcentered SolarEcliptic coordinate system.
This data set contains averaged 1minute magnetic field data converted from simple ASCII records. It was created at NSSDC from a more complex, multiresolution data set (NSSDC ID = SPHE00673; Old ID = 78079A02D) provided by the Principal Investigator team and now available fromftp://nssdcftp.gsfc.nasa.gov/spacecraft_data/isee/isee3/magnetic_fields/1min _ascii/ The coordinate system for the Bfield components is the JPLdefined I,S coordinate system (origin at the spacecraft): I is the unit vector in the direction of the ISEE3 spin axis (positive in the northward direction), and S is the unit vector from the spacecraft to the sun. The zaxis is parallel to to I, the yaxis to the crossproduct I x S, and the xaxis to Y x Z. The I,S coordinate system is approximately the same as the Solar Ecliptic (SE) system since the spacecraft zaxis (the spin axis) is maintained within 0.5 degree of perpendicular to the ecliptic plane. (SE is defined the same way as GSE, but with the spacecraft [point of observation] substituted for Earth). For years 19841990 we added spacecraft position in HGI coordinate The HGI coordinates are Suncentered and inertially fixed with respect to an Xaxis directed along the intersection line of theecliptic and solar equatorial planes, and defines zero of the longitude, HGI_LONG. The solar equator plane is inclined at 7.25degrees from the ecliptic. This direction was towards ecliptic longitude of 74.367 deg on 1 January 1900 at 12:00 UT; because of the precession of the Earth"s equator, this longitude increases by 1.4 deg/century. The Zaxis is directed perpendicular to and northward of the solar equator, and the Yaxis completes the righthanded set. The longitude, HGI_LONG increase from zero in the Xdirection towards Ydirection.The latitude HG_LAT increases to +90 deg towards the north pole, and to 90 deg towardsm south pole. Note that here present values averaged in 1minute, e.g. <B>^2 may be not equal <B^2)>.
C. T. Russell (IEEE Trans. Geoscience Electronics, GE16, 239242, 1978). This publication is available online at http://wwwssc.igpp.ucla.edu/personnel/russell/papers/ISEE_fluxgate/.
C. T. Russell (IEEE Trans. Geoscience Electronics, GE16, 239242, 1978). This publication is available online at http://wwwssc.igpp.ucla.edu/personnel/russell/papers/ISEE_fluxgate/.
Model internal field is IGRF 75.
Model internal field is IGRF 75.
Model internal field is IGRF 75.
Model internal field is IGRF 75.
Model field is IGRF 75 + OP 77.
Model field is IGRF 75 + OP 77.
Model field is IGRF 75 + OP 77.
Model field is IGRF 75 + OP 77.
Lshell: http://en.wikipedia.org/wiki/Lshell
Local time is the universal time plus the geographic longitude of the spacecraft converted to hours.
Latitude of spacecraft from magnetic equator
This relative speed is same in ISEE 1 data and the ISEE 2 data.
This relative speed is same in ISEE 1 data and the ISEE 2 data.
This relative speed is the same in the ISEE 1 data and the ISEE 2 data.
This relative speed is the same in the ISEE 1 data and the ISEE 2 data.
This relative separation is the same in the ISEE 1 data and the ISEE 2 data.
This relative separation is the same in the ISEE 1 data and the ISEE 2 data.
This relative separation is the same in the ISEE 1 data and the ISEE 2 data.
This relative separation is the same in the ISEE 1 data and the ISEE 2 data.
This relative separation is the same in the ISEE 1 data and the ISEE 2 data.
This relative separation is the same in the ISEE 1 data and the ISEE 2 data.
This enhanced CDF master was generated by NSSDC, with input from R. Fitzenreiter and A. F.Vinas, to make useable a barebones CDF data set provided earlier to NSSDC. This current CDF master version, Oct. 5, 2007, is used for making a CDF by selecting only certain variables from those available in the original barebones CDF.
Velocity units were changed to km/sec, and Hi, Mid, & Lowest energy channels above SC potential were change from velocity to the corresponding energy value in eV..
Active Harvey experiment causes spikes in electron data.
Active Mozer experiment causes spikes in electron data.
Electron density is obtained 6 times during a spacecraft spin period. The six measurements are separately averaged to make the six elements of this array. We still need to know the delta t from Epoch to the first of these 6 densities.
Electron Temperatue is 1/3 trace of diagonalized pressure tensor. Electron Temperature = (1/3) (parallel temp + two perpendicular eigenvalues)
Norm. Gytotropy made by dividing by Electron Temperature
Highest is channel 1, lowest is given by value of variable INSET, and mid is given by (INSET+1)/2, dropping any remainder.
These experimentersupplied, fast plasma proton fluid parameter data were originally written in BCD character code, but were converted to EBCDIC characters during restoration to new media. Data coverage includes the region from 6 earth radii out to (but excluding) the bow shock. The reasons for selecting this area of coverage are that the solar wind ion distributions are too cold to be adequately resolved by this instrument, and inside the region of 6 earth radii the fast plasma data would be contaminated by the energetic particle background. The physical records on the tapes are blocked with 50 88byte logical records. The first record of each file is a header containing data identification information, orbit number, and start and end times for the file. Each data record contains universal time (in year, day of year, and seconds of day), orbit number, spacecraft position in solar ecliptic coordinates, number density, energy density, a flag indicating the energy range covered, components of the twodimensional bulk velocity in spacecraft coordinates, and the average twodimensional temperature. Time resolution is 60 seconds, but the distributions were obtained over 3 or 6 seconds..Los Alamos Magnetospheric Plasma Analyzer (MPA) [Bame et al., .Rev. Sci. Inst., in press 1993]. ...Los Alamos Magnetospheric Plasma Analyzer (MPA) [Bame et al., .Rev. Sci. Inst., in press 1993]. .The moments are presented in s/c coordinates: the zaxis is aligned with .the spin axis, which points radially toward the center of the Earth; .the xaxis is in the plane containing the spacecraft spin axis and the spin .axis of the Earth, with +X generally northward; and the yaxis points .generally eastward. Polar angles are measured relative to the spin axis .(+Z), and azimuthal angles are measured around the zaxis, with zero along .the +X direction. The moments are computed for three 'species': .lop (lowener. ions, ~1eV/e~130eV/e); hip (hiener. ions, ~130eV/e~45keV/e);. alle (electrons, ~30eV  ~45keV ). The electron measurements are obtained .21.5 secs after the ion measurements. Epoch is the measurement time .appropriate for the ions. The moments are computed after the fluxes are .corrected for background and s/c potential. Algorithms for these corrections. are relatively unsophisticated, so the moments are suspect during times of .high background and/or high spacecraft potential. Because the determined .spacecraft potential is not very precise, the magnitude of the lowenergy .ion flow velocity is probably not accurate, but the flow direction is well .determined. Tperp and Tpara are obtained from diagonalization of the .3dimensional temperature matrix, with the parallel direction assigned .to the eigenvalue which is most different from the other two. .The corresponding eigenvector is the symmetry axis of the distribution and .should be equivalent to the magnetic field direction. The eigenvalue ratio .Tperp/Tmid, which is provided for each species, is a measure of the symmetry .of the distribution and should be ~1.0 for a good determination. Several of .the parameters have a fairly high daily dynamic range and for survey purposes .are best displayed logarithmically. These parameters are indicated by .nonzero 'SCALEMIN' values in this file. A quality flag value of 1 .indicates that the values are suspect because of unreliable .location info. .Los Alamos Magnetospheric Plasma Analyzer (MPA) [Bame et al., .Rev. Sci. Inst., in press 1993]. .The moments are presented in s/c coordinates: the zaxis is aligned with .the spin axis, which points radially toward the center of the Earth; .the xaxis is in the plane containing the spacecraft spin axis and the spin .axis of the Earth, with +X generally northward; and the yaxis points .generally eastward. Polar angles are measured relative to the spin axis .(+Z), and azimuthal angles are measured around the zaxis, with zero along .the +X direction. The moments are computed for three 'species': .lop (lowener. ions, ~1eV/e~130eV/e); hip (hiener. ions, ~130eV/e~45keV/e);. alle (electrons, ~30eV  ~45keV ). The electron measurements are obtained .21.5 secs after the ion measurements. Epoch is the measurement time .appropriate for the ions. The moments are computed after the fluxes are .corrected for background and s/c potential. Algorithms for these corrections. are relatively unsophisticated, so the moments are suspect during times of .high background and/or high spacecraft potential. Because the determined .spacecraft potential is not very precise, the magnitude of the lowenergy .ion flow velocity is probably not accurate, but the flow direction is well .determined. Tperp and Tpara are obtained from diagonalization of the .3dimensional temperature matrix, with the parallel direction assigned .to the eigenvalue which is most different from the other two. .The corresponding eigenvector is the symmetry axis of the distribution and .should be equivalent to the magnetic field direction. The eigenvalue ratio .Tperp/Tmid, which is provided for each species, is a measure of the symmetry .of the distribution and should be ~1.0 for a good determination. Several of .the parameters have a fairly high daily dynamic range and for survey purposes .are best displayed logarithmically. These parameters are indicated by .nonzero 'SCALEMIN' values in this file. A quality flag value of 1 .indicates that the values are suspect because of unreliable .location info. .Los Alamos Magnetospheric Plasma Analyzer (MPA) [Bame et al., .Rev. Sci. Inst., in press 1993]. .The moments are presented in s/c coordinates: the zaxis is aligned with .the spin axis, which points radially toward the center of the Earth; .the xaxis is in the plane containing the spacecraft spin axis and the spin .axis of the Earth, with +X generally northward; and the yaxis points .generally eastward. Polar angles are measured relative to the spin axis .(+Z), and azimuthal angles are measured around the zaxis, with zero along .the +X direction. The moments are computed for three 'species': .lop (lowener. ions, ~1eV/e~130eV/e); hip (hiener. ions, ~130eV/e~45keV/e);. alle (electrons, ~30eV  ~45keV ). The electron measurements are obtained .21.5 secs after the ion measurements. Epoch is the measurement time .appropriate for the ions. The moments are computed after the fluxes are .corrected for background and s/c potential. Algorithms for these corrections. are relatively unsophisticated, so the moments are suspect during times of .high background and/or high spacecraft potential. Because the determined .spacecraft potential is not very precise, the magnitude of the lowenergy .ion flow velocity is probably not accurate, but the flow direction is well .determined. Tperp and Tpara are obtained from diagonalization of the .3dimensional temperature matrix, with the parallel direction assigned .to the eigenvalue which is most different from the other two. .The corresponding eigenvector is the symmetry axis of the distribution and .should be equivalent to the magnetic field direction. The eigenvalue ratio .Tperp/Tmid, which is provided for each species, is a measure of the symmetry .of the distribution and should be ~1.0 for a good determination. Several of .the parameters have a fairly high daily dynamic range and for survey purposes .are best displayed logarithmically. These parameters are indicated by .nonzero 'SCALEMIN' values in this file. A quality flag value of 1 .indicates that the values are suspect because of unreliable .location info. .Los Alamos Magnetospheric Plasma Analyzer (MPA) [Bame et al., .Rev. Sci. Inst., in press 1993]. .The moments are presented in s/c coordinates: the zaxis is aligned with .the spin axis, which points radially toward the center of the Earth; .the xaxis is in the plane containing the spacecraft spin axis and the spin .axis of the Earth, with +X generally northward; and the yaxis points .generally eastward. Polar angles are measured relative to the spin axis .(+Z), and azimuthal angles are measured around the zaxis, with zero along .the +X direction. The moments are computed for three 'species': .lop (lowener. ions, ~1eV/e~130eV/e); hip (hiener. ions, ~130eV/e~45keV/e);. alle (electrons, ~30eV  ~45keV ). The electron measurements are obtained .21.5 secs after the ion measurements. Epoch is the measurement time .appropriate for the ions. The moments are computed after the fluxes are .corrected for background and s/c potential. Algorithms for these corrections. are relatively unsophisticated, so the moments are suspect during times of .high background and/or high spacecraft potential. Because the determined .spacecraft potential is not very precise, the magnitude of the lowenergy .ion flow velocity is probably not accurate, but the flow direction is well .determined. Tperp and Tpara are obtained from diagonalization of the .3dimensional temperature matrix, with the parallel direction assigned .to the eigenvalue which is most different from the other two. .The corresponding eigenvector is the symmetry axis of the distribution and .should be equivalent to the magnetic field direction. The eigenvalue ratio .Tperp/Tmid, which is provided for each species, is a measure of the symmetry .of the distribution and should be ~1.0 for a good determination. Several of .the parameters have a fairly high daily dynamic range and for survey purposes .are best displayed logarithmically. These parameters are indicated by .nonzero 'SCALEMIN' values in this file. A quality flag value of 1 .indicates that the values are suspect because of unreliable .location info. Los Alamos Magnetospheric Plasma Analyzer (MPA) [Bame et al., Rev. Sci. Inst., in press 1993]. The moments are presented in s/c coordinates: the zaxis is aligned with the spin axis, which points radially toward the center of the Earth; the xaxis is in the plane containing the spacecraft spin axis and the spin axis of the Earth, with +X generally northward; and the yaxis points generally eastward. Polar angles are measured relative to the spin axis (+Z), and azimuthal angles are measured around the zaxis, with zero along the +X direction. The moments are computed for three 'species': lop (lowener. ions, ~1eV/e~130eV/e); hip (hiener. ions, ~130eV/e~45keV/e); alle (electrons, ~30eV  ~45keV ). The electron measurements are obtained 21.5 secs after the ion measurements. Epoch is the measurement time appropriate for the ions. The moments are computed after the fluxes are corrected for background and s/c potential. Algorithms for these corrections are relatively unsophisticated, so the moments are suspect during times of high background and/or high spacecraft potential. Because the determined spacecraft potential is not very precise, the magnitude of the lowenergy ion flow velocity is probably not accurate, but the flow direction is well determined. Tperp and Tpara are obtained from diagonalization of the 3dimensional temperature matrix, with the parallel direction assigned to the eigenvalue which is most different from the other two. The corresponding eigenvector is the symmetry axis of the distribution and should be equivalent to the magnetic field direction. The eigenvalue ratio Tperp/Tmid, which is provided for each species, is a measure of the symmetry of the distribution and should be ~1.0 for a good determination. Several of the parameters have a fairly high daily dynamic range and for survey purposes are best displayed logarithmically. These parameters are indicated by nonzero 'SCALEMIN' values in this file. A quality flag value of 1 indicates that the values are suspect because of unreliable location info.
This is a revised version of the data; the PI team reprocessed the data and provided this replacement version in July 1986. The new version can be verified by the wording in the header information, which contains "...FPE 2D IONS 85. LANL/MPE,..." in the revised version....Electron time tags removed Mag Latitude added .Local time added Post Gap flag added .Ratio variables changed Modified SEP 1994 .Changes noted in mail message from M.Kessel .New Dict keys added sep95 .Added new global attr. and variables from M.Kessel Oct 98.Electron time tags removed Mag Latitude added .Local time added Post Gap flag added .Ratio variables changed Modified SEP 1994 .Changes noted in mail message from M.Kessel .New Dict keys added sep95 .Added new global attr. and variables from M.Kessel Oct 98.Electron time tags removed Mag Latitude added .Local time added Post Gap flag added .Ratio variables changed Modified SEP 1994 .Changes noted in mail message from M.Kessel .New Dict keys added sep95 .Added new global attr. and variables from M.Kessel Oct 98.Electron time tags removed Mag Latitude added .Local time added Post Gap flag added .Ratio variables changed Modified SEP 1994 .Changes noted in mail message from M.Kessel .New Dict keys added sep95 .Added new global attr. and variables from M.Kessel Oct 98 Electron time tags removed Mag Latitude added Local time added Post Gap flag added Ratio variables changed Modified SEP 1994 Changes noted in mail message from M.Kessel New Dict keys added sep95 Added new global attr. and variables from M.Kessel Oct 98
0: 50 eV to 20 keV per charge.1: 70 eV to 40 keV per charge
T = (Txx + Tyy)/2. = average 2D temperature (units = Kelvin).
Counting statistics and thus moments parameters are problematic for Den < 0.1 per cm3, including DEN, ENDEN, VX, VY, and T.
Spacecraft coordinate axes normally differ by no more than a few degrees from the respective GSE axes..The 2D bulk velocity essentially represents the projection of the true velocity onto the symmetry plane of the analyzers, i.e., approximately the ecliptic plane.
Spacecraft coordinate axes normally differ by no more than a few degrees from the respective GSE axes..The 2D bulk velocity essentially represents the projection of the true velocity onto the symmetry plane of the analyzers, i.e., approximately the ecliptic plane.
These data are high temporal resolution solar wind ion moments derived from measurements obtained by the Los Alamos XFan Solar Wind Ion Experiment (SWE) on ISEE1. The original magnetic tape contained 7 files, 1 for each of the solar wind seasons for the spacecraft (roughly July through December) from 1977 through 1983. The temporal resolution of these data is 24 seconds in high data rate and 48 seconds in low data rate. Each data record in these files contains the date (YYMMDD), universal time in seconds, universal time in HHMMSS, the proton density (cm3), flow speed (km/sec), flow azimuth (degs., with 0 degrees corresponding to flow from the sun [corrected for aberration] and positive azimuths corresponding to flow toward dawn), flow latitude (degs., with positive latitudes corresponding to flow toward the south), the minimum proton temperature (degrees K), the maximum proton temperature (degrees K), and the alpha/proton fraction (alpha fraction = 0.00 means no determination made). The data providers did not attempt to crosscalibrate density values with those from other experiments. However, they expected that density values will tend to be too low in later years because of detector degradation. Crosscalibration using, for example, IMPderived values would be a useful exercise. Please note also that many of these measurements were obtained within the foreshock region where the solar wind flow is affected by waves in the foreshock. Reference: Los Alamos Magnetospheric Plasma Analyzer (MPA) [Bame et al., ISEE1 and ISEE2 fast plasma experiment and the ISEE1 solar wind experiment, IEEE Trans. Geosci. Electron., GE16, 216, 1978]. Los Alamos Magnetospheric Plasma Analyzer (MPA) [Bame et al., Rev. Sci. Inst., in press 1993]. The moments are presented in s/c coordinates: the zaxis is aligned with the spin axis, which points radially toward the center of the Earth; the xaxis is in the plane containing the spacecraft spin axis and the spin axis of the Earth, with +X generally northward; and the yaxis points generally eastward. Polar angles are measured relative to the spin axis (+Z), and azimuthal angles are measured around the zaxis, with zero along the +X direction. The moments are computed for three 'species': lop (lowener. ions, ~1eV/e~130eV/e); hip (hiener. ions, ~130eV/e~45keV/e); alle (electrons, ~30eV  ~45keV ). The electron measurements are obtained 21.5 secs after the ion measurements. Epoch is the measurement time appropriate for the ions. The moments are computed after the fluxes are corrected for background and s/c potential. Algorithms for these corrections are relatively unsophisticated, so the moments are suspect during times of high background and/or high spacecraft potential. Because the determined spacecraft potential is not very precise, the magnitude of the lowenergy ion flow velocity is probably not accurate, but the flow direction is well determined. Tperp and Tpara are obtained from diagonalization of the 3dimensional temperature matrix, with the parallel direction assigned to the eigenvalue which is most different from the other two. The corresponding eigenvector is the symmetry axis of the distribution and should be equivalent to the magnetic field direction. The eigenvalue ratio Tperp/Tmid, which is provided for each species, is a measure of the symmetry of the distribution and should be ~1.0 for a good determination. Several of the parameters have a fairly high daily dynamic range and for survey purposes are best displayed logarithmically. These parameters are indicated by nonzero 'SCALEMIN' values in this file. A quality flag value of 1 indicates that the values are suspect because of unreliable location info. Los Alamos Magnetospheric Plasma Analyzer (MPA) [Bame et al., Rev. Sci. Inst., in press 1993]. The moments are presented in s/c coordinates: the zaxis is aligned with the spin axis, which points radially toward the center of the Earth; the xaxis is in the plane containing the spacecraft spin axis and the spin axis of the Earth, with +X generally northward; and the yaxis points generally eastward. Polar angles are measured relative to the spin axis (+Z), and azimuthal angles are measured around the zaxis, with zero along the +X direction. The moments are computed for three 'species': lop (lowener. ions, ~1eV/e~130eV/e); hip (hiener. ions, ~130eV/e~45keV/e); alle (electrons, ~30eV  ~45keV ). The electron measurements are obtained 21.5 secs after the ion measurements. Epoch is the measurement time appropriate for the ions. The moments are computed after the fluxes are corrected for background and s/c potential. Algorithms for these corrections are relatively unsophisticated, so the moments are suspect during times of high background and/or high spacecraft potential. Because the determined spacecraft potential is not very precise, the magnitude of the lowenergy ion flow velocity is probably not accurate, but the flow direction is well determined. Tperp and Tpara are obtained from diagonalization of the 3dimensional temperature matrix, with the parallel direction assigned to the eigenvalue which is most different from the other two. The corresponding eigenvector is the symmetry axis of the distribution and should be equivalent to the magnetic field direction. The eigenvalue ratio Tperp/Tmid, which is provided for each species, is a measure of the symmetry of the distribution and should be ~1.0 for a good determination. Several of the parameters have a fairly high daily dynamic range and for survey purposes are best displayed logarithmically. These parameters are indicated by nonzero 'SCALEMIN' values in this file. A quality flag value of 1 indicates that the values are suspect because of unreliable location info. Los Alamos Magnetospheric Plasma Analyzer (MPA) [Bame et al., Rev. Sci. Inst., in press 1993]. The moments are presented in s/c coordinates: the zaxis is aligned with the spin axis, which points radially toward the center of the Earth; the xaxis is in the plane containing the spacecraft spin axis and the spin axis of the Earth, with +X generally northward; and the yaxis points generally eastward. Polar angles are measured relative to the spin axis (+Z), and azimuthal angles are measured around the zaxis, with zero along the +X direction. The moments are computed for three 'species': lop (lowener. ions, ~1eV/e~130eV/e); hip (hiener. ions, ~130eV/e~45keV/e); alle (electrons, ~30eV  ~45keV ). The electron measurements are obtained 21.5 secs after the ion measurements. Epoch is the measurement time appropriate for the ions. The moments are computed after the fluxes are corrected for background and s/c potential. Algorithms for these corrections are relatively unsophisticated, so the moments are suspect during times of high background and/or high spacecraft potential. Because the determined spacecraft potential is not very precise, the magnitude of the lowenergy ion flow velocity is probably not accurate, but the flow direction is well determined. Tperp and Tpara are obtained from diagonalization of the 3dimensional temperature matrix, with the parallel direction assigned to the eigenvalue which is most different from the other two. The corresponding eigenvector is the symmetry axis of the distribution and should be equivalent to the magnetic field direction. The eigenvalue ratio Tperp/Tmid, which is provided for each species, is a measure of the symmetry of the distribution and should be ~1.0 for a good determination. Several of the parameters have a fairly high daily dynamic range and for survey purposes are best displayed logarithmically. These parameters are indicated by nonzero 'SCALEMIN' values in this file. A quality flag value of 1 indicates that the values are suspect because of unreliable location info.
Electron time tags removed Mag Latitude added Local time added Post Gap flag added Ratio variables changed Modified SEP 1994 Changes noted in mail message from M.Kessel New Dict keys added sep95 Added new global attr. and variables from M.Kessel Oct 98
The 3D solar wind flow vector and other 3D moments of the velocity distribution are obtained by combining data from two crossedfan 2D analyzers.
Tmin is obtained from 3D moments of the velocity distribution.
Flow azimuth, in degrees, is given as 0 degrees for flow from the sun [corrected for aberration] and positive azimuths correspond to flow toward dawn.
Tmax is obtained from 3D moments of the velocity distribution.
'The ISEE1 and 2 Plasma Wave Investigation' D. A. Gurnett, F. L. Scarf, R. W. Fredricks, and E. J. Smith, IEEE Transactions on Geoscience Electronics, Vol. GE16, p. 225230, 1978.
These data are collected via the fine wire electric dipole antenna which had a tip to tip length of 215 meters. The Ev antenna was used to collect over 99% of the Efield measurements obtained by the PWI. Most of the time (98.3%) these data were collected via the ESA (Electric Spectrum Analyzer). Though a small fraction of the data are from the MSA (Magnetic Spectrum Analyzer). The two analyzers have almost identical channel centers and bandwidths, except that ESA has 6 more bands above the highest band of the MSA. When the MSA is used to read an electric antenna, the upper 6 bands are marked with fill data. This antenna was shared with the Heppner DC electricfield experiment. The 'E_Quality' variable flags times when known spacecraft noise sources are present in the Efield data.
Less that 0.5% of electric spectra in this data set were collected via the Eu antenna. This variable is almost always <b>empty</b>. The Eu sensor is a twosphere electric antenna which had a spheretosphere separation of 73.5 meters. The spheres on the uaxis have a diameter of 8.0 cm and each contains a highimpedance preamplifier which provides signals to the main electronics box which contained the spectrum analyzers. This antenna was shared with the Mozer quasistatic electricfield instrument. Consult the 'E_Quality' variable for issues regarding Ev_Spectra values.
These data are collected via the zaxis Magnetic Search Coil (Bz) which has an upper cutoff frequency of 10 kHz. It's constructed of a 16 inch mumetal core and wound with 10000 turns wire. Almost 99% of all magnetic field measurements from the PWI were collected via the Bz search coil. NOTE: When they are present at all, the upper 6 frequency indices contain data collected above the search coil's upper cutoff frequency. Though these data are included for completeness, all samples above 10 kHz are *not* calibrated data and should be used with caution. See the 'B_Quality' variable and the 'Quality_note' for issues regarding Bz_Spectra
These data were collected via the Vaxis Magnetic Search Coil (Bv). This coil had the same physical properties as the Bz coil but was mounted perpendicular to the Bz coil. The Bv coil axis pointed along the V direction, which is within the spacecraft spin plane. This variable is usually *empty*. Less than 2.5% of magnetic spectra were collected via this search coil. See the 'B_Quality' variable and the 'Quality_note' for issues regarding Bu_Spectra.
These data were collected via the Uaxis Magnetic Search Coil (Bu). This coil had the same physical properties as the Bv coil but was mounted perpendicular to both the Bz and Bv coils. The Bu coil axis pointed along the U direction, which is also within the spacecraft spin plane. This variable is almost always *empty*. Less than 0.1% of magnetic spectra were collected via this search coil. See the 'B_Quality' variable and the 'Quality_note' for issues regarding Bu_Spectra.
'The ISEE1 and 2 Plasma Wave Investigation' D. A. Gurnett, F. L. Scarf, R. W. Fredricks, and E. J. Smith, IEEE Transactions on Geoscience Electronics, Vol. GE16, p. 225230, 1978.
These data are collected primarily via the fine wire electric dipole antenna which had a tip to tip length of 215 meters. A small fraction of the data in this variable were collected via the Eu antenna. See the 'Eu_Sensor' variable to distinguish the input sources if needed. The Eu and Ev antennas were shared with the Heppner DC electricfield experiment. Consult the 'Quality_Flag' variable for issues regarding E_Series values.
'The ISEE1 and 2 Plasma Wave Investigation' D. A. Gurnett, F. L. Scarf, R. W. Fredricks, and E. J. Smith, IEEE Transactions on Geoscience Electronics, Vol. GE16, p. 225230, 1978.
These data are collected primarily via the fine wire electric dipole antenna which had a tip to tip length of 215 meters. A small fraction of the data, less that 0.5%, in this variable were collected via the Eu and Es antennas. See the 'Eu_Sensor' variable to distinguish the input sources if needed. The Eu and Ev antennas ware shared with the Heppner DC electricfield experiment. Consult the 'Quality_Flag' variable for issues regarding E_Spectra values.
C. T. Russell (IEEE Trans. Geoscience Electronics, GE16, 239242, 1978). This publication is available online at http://wwwssc.igpp.ucla.edu/personnel/russell/papers/ISEE_fluxgate/.
C. T. Russell (IEEE Trans. Geoscience Electronics, GE16, 239242, 1978). This publication is available online at http://wwwssc.igpp.ucla.edu/personnel/russell/papers/ISEE_fluxgate/.
Model internal field is IGRF 75.
Model internal field is IGRF 75.
Model internal field is IGRF 75.
Model internal field is IGRF 75.
Model field is IGRF 75 + OP 77.
Model field is IGRF 75 + OP 77.
Model field is IGRF 75 + OP 77.
Model field is IGRF 75 + OP 77.
Lshell: http://en.wikipedia.org/wiki/Lshell
Local time is the universal time plus the geographic longitude of the spacecraft converted to hours.
Latitude of spacecraft from magnetic equator
This relative speed is same in ISEE 1 data and the ISEE 2 data.
This relative speed is same in ISEE 1 data and the ISEE 2 data.
This relative speed is the same in the ISEE 1 data and the ISEE 2 data.
This relative speed is the same in the ISEE 1 data and the ISEE 2 data.
This relative separation is the same in the ISEE 1 data and the ISEE 2 data.
This relative separation is the same in the ISEE 1 data and the ISEE 2 data.
This relative separation is the same in the ISEE 1 data and the ISEE 2 data.
This relative separation is the same in the ISEE 1 data and the ISEE 2 data.
This relative separation is the same in the ISEE 1 data and the ISEE 2 data.
This relative separation is the same in the ISEE 1 data and the ISEE 2 data.
These experimentersupplied, fast plasma proton fluid parameter data were originally written in BCD character code, but were converted to EBCDIC characters during restoration to new media. Data coverage includes the region from 6 earth radii out to (but excluding) the bow shock. The reasons for selecting this area of coverage are that the solar wind ion distributions are too cold to be adequately resolved by this instrument, and inside the region of 6 earth radii the fast plasma data would be contaminated by the energetic particle background. The physical records on the tapes are blocked with 50 88byte logical records. The first record of each file is a header containing data identification information, orbit number, and start and end times for the file. Each data record contains universal time (in year, day of year, and seconds of day), orbit number, spacecraft position in solar ecliptic coordinates, number density, energy density, a flag indicating the energy range covered, components of the twodimensional bulk velocity in spacecraft coordinates, and the average twodimensional temperature. Time resolution is 60 seconds, but the distributions were obtained over 3 or 6 seconds..Los Alamos Magnetospheric Plasma Analyzer (MPA) [Bame et al., .Rev. Sci. Inst., in press 1993]. ...Los Alamos Magnetospheric Plasma Analyzer (MPA) [Bame et al., .Rev. Sci. Inst., in press 1993]. .The moments are presented in s/c coordinates: the zaxis is aligned with .the spin axis, which points radially toward the center of the Earth; .the xaxis is in the plane containing the spacecraft spin axis and the spin .axis of the Earth, with +X generally northward; and the yaxis points .generally eastward. Polar angles are measured relative to the spin axis .(+Z), and azimuthal angles are measured around the zaxis, with zero along .the +X direction. The moments are computed for three 'species': .lop (lowener. ions, ~1eV/e~130eV/e); hip (hiener. ions, ~130eV/e~45keV/e);. alle (electrons, ~30eV  ~45keV ). The electron measurements are obtained .21.5 secs after the ion measurements. Epoch is the measurement time .appropriate for the ions. The moments are computed after the fluxes are .corrected for background and s/c potential. Algorithms for these corrections. are relatively unsophisticated, so the moments are suspect during times of .high background and/or high spacecraft potential. Because the determined .spacecraft potential is not very precise, the magnitude of the lowenergy .ion flow velocity is probably not accurate, but the flow direction is well .determined. Tperp and Tpara are obtained from diagonalization of the .3dimensional temperature matrix, with the parallel direction assigned .to the eigenvalue which is most different from the other two. .The corresponding eigenvector is the symmetry axis of the distribution and .should be equivalent to the magnetic field direction. The eigenvalue ratio .Tperp/Tmid, which is provided for each species, is a measure of the symmetry .of the distribution and should be ~1.0 for a good determination. Several of .the parameters have a fairly high daily dynamic range and for survey purposes .are best displayed logarithmically. These parameters are indicated by .nonzero 'SCALEMIN' values in this file. A quality flag value of 1 .indicates that the values are suspect because of unreliable .location info. .Los Alamos Magnetospheric Plasma Analyzer (MPA) [Bame et al., .Rev. Sci. Inst., in press 1993]. .The moments are presented in s/c coordinates: the zaxis is aligned with .the spin axis, which points radially toward the center of the Earth; .the xaxis is in the plane containing the spacecraft spin axis and the spin .axis of the Earth, with +X generally northward; and the yaxis points .generally eastward. Polar angles are measured relative to the spin axis .(+Z), and azimuthal angles are measured around the zaxis, with zero along .the +X direction. The moments are computed for three 'species': .lop (lowener. ions, ~1eV/e~130eV/e); hip (hiener. ions, ~130eV/e~45keV/e);. alle (electrons, ~30eV  ~45keV ). The electron measurements are obtained .21.5 secs after the ion measurements. Epoch is the measurement time .appropriate for the ions. The moments are computed after the fluxes are .corrected for background and s/c potential. Algorithms for these corrections. are relatively unsophisticated, so the moments are suspect during times of .high background and/or high spacecraft potential. Because the determined .spacecraft potential is not very precise, the magnitude of the lowenergy .ion flow velocity is probably not accurate, but the flow direction is well .determined. Tperp and Tpara are obtained from diagonalization of the .3dimensional temperature matrix, with the parallel direction assigned .to the eigenvalue which is most different from the other two. .The corresponding eigenvector is the symmetry axis of the distribution and .should be equivalent to the magnetic field direction. The eigenvalue ratio .Tperp/Tmid, which is provided for each species, is a measure of the symmetry .of the distribution and should be ~1.0 for a good determination. Several of .the parameters have a fairly high daily dynamic range and for survey purposes .are best displayed logarithmically. These parameters are indicated by .nonzero 'SCALEMIN' values in this file. A quality flag value of 1 .indicates that the values are suspect because of unreliable .location info. .Los Alamos Magnetospheric Plasma Analyzer (MPA) [Bame et al., .Rev. Sci. Inst., in press 1993]. .The moments are presented in s/c coordinates: the zaxis is aligned with .the spin axis, which points radially toward the center of the Earth; .the xaxis is in the plane containing the spacecraft spin axis and the spin .axis of the Earth, with +X generally northward; and the yaxis points .generally eastward. Polar angles are measured relative to the spin axis .(+Z), and azimuthal angles are measured around the zaxis, with zero along .the +X direction. The moments are computed for three 'species': .lop (lowener. ions, ~1eV/e~130eV/e); hip (hiener. ions, ~130eV/e~45keV/e);. alle (electrons, ~30eV  ~45keV ). The electron measurements are obtained .21.5 secs after the ion measurements. Epoch is the measurement time .appropriate for the ions. The moments are computed after the fluxes are .corrected for background and s/c potential. Algorithms for these corrections. are relatively unsophisticated, so the moments are suspect during times of .high background and/or high spacecraft potential. Because the determined .spacecraft potential is not very precise, the magnitude of the lowenergy .ion flow velocity is probably not accurate, but the flow direction is well .determined. Tperp and Tpara are obtained from diagonalization of the .3dimensional temperature matrix, with the parallel direction assigned .to the eigenvalue which is most different from the other two. .The corresponding eigenvector is the symmetry axis of the distribution and .should be equivalent to the magnetic field direction. The eigenvalue ratio .Tperp/Tmid, which is provided for each species, is a measure of the symmetry .of the distribution and should be ~1.0 for a good determination. Several of .the parameters have a fairly high daily dynamic range and for survey purposes .are best displayed logarithmically. These parameters are indicated by .nonzero 'SCALEMIN' values in this file. A quality flag value of 1 .indicates that the values are suspect because of unreliable .location info. .Los Alamos Magnetospheric Plasma Analyzer (MPA) [Bame et al., .Rev. Sci. Inst., in press 1993]. .The moments are presented in s/c coordinates: the zaxis is aligned with .the spin axis, which points radially toward the center of the Earth; .the xaxis is in the plane containing the spacecraft spin axis and the spin .axis of the Earth, with +X generally northward; and the yaxis points .generally eastward. Polar angles are measured relative to the spin axis .(+Z), and azimuthal angles are measured around the zaxis, with zero along .the +X direction. The moments are computed for three 'species': .lop (lowener. ions, ~1eV/e~130eV/e); hip (hiener. ions, ~130eV/e~45keV/e);. alle (electrons, ~30eV  ~45keV ). The electron measurements are obtained .21.5 secs after the ion measurements. Epoch is the measurement time .appropriate for the ions. The moments are computed after the fluxes are .corrected for background and s/c potential. Algorithms for these corrections. are relatively unsophisticated, so the moments are suspect during times of .high background and/or high spacecraft potential. Because the determined .spacecraft potential is not very precise, the magnitude of the lowenergy .ion flow velocity is probably not accurate, but the flow direction is well .determined. Tperp and Tpara are obtained from diagonalization of the .3dimensional temperature matrix, with the parallel direction assigned .to the eigenvalue which is most different from the other two. .The corresponding eigenvector is the symmetry axis of the distribution and .should be equivalent to the magnetic field direction. The eigenvalue ratio .Tperp/Tmid, which is provided for each species, is a measure of the symmetry .of the distribution and should be ~1.0 for a good determination. Several of .the parameters have a fairly high daily dynamic range and for survey purposes .are best displayed logarithmically. These parameters are indicated by .nonzero 'SCALEMIN' values in this file. A quality flag value of 1 .indicates that the values are suspect because of unreliable .location info. .Los Alamos Magnetospheric Plasma Analyzer (MPA) [Bame et al., .Rev. Sci. Inst., in press 1993]. .The moments are presented in s/c coordinates: the zaxis is aligned with .the spin axis, which points radially toward the center of the Earth; .the xaxis is in the plane containing the spacecraft spin axis and the spin .axis of the Earth, with +X generally northward; and the yaxis points .generally eastward. Polar angles are measured relative to the spin axis .(+Z), and azimuthal angles are measured around the zaxis, with zero along .the +X direction. The moments are computed for three 'species': .lop (lowener. ions, ~1eV/e~130eV/e); hip (hiener. ions, ~130eV/e~45keV/e);. alle (electrons, ~30eV  ~45keV ). The electron measurements are obtained .21.5 secs after the ion measurements. Epoch is the measurement time .appropriate for the ions. The moments are computed after the fluxes are .corrected for background and s/c potential. Algorithms for these corrections. are relatively unsophisticated, so the moments are suspect during times of .high background and/or high spacecraft potential. Because the determined .spacecraft potential is not very precise, the magnitude of the lowenergy .ion flow velocity is probably not accurate, but the flow direction is well .determined. Tperp and Tpara are obtained from diagonalization of the .3dimensional temperature matrix, with the parallel direction assigned .to the eigenvalue which is most different from the other two. .The corresponding eigenvector is the symmetry axis of the distribution and .should be equivalent to the magnetic field direction. The eigenvalue ratio .Tperp/Tmid, which is provided for each species, is a measure of the symmetry .of the distribution and should be ~1.0 for a good determination. Several of .the parameters have a fairly high daily dynamic range and for survey purposes .are best displayed logarithmically. These parameters are indicated by .nonzero 'SCALEMIN' values in this file. A quality flag value of 1 .indicates that the values are suspect because of unreliable .location info. Los Alamos Magnetospheric Plasma Analyzer (MPA) [Bame et al., Rev. Sci. Inst., in press 1993]. The moments are presented in s/c coordinates: the zaxis is aligned with the spin axis, which points radially toward the center of the Earth; the xaxis is in the plane containing the spacecraft spin axis and the spin axis of the Earth, with +X generally northward; and the yaxis points generally eastward. Polar angles are measured relative to the spin axis (+Z), and azimuthal angles are measured around the zaxis, with zero along the +X direction. The moments are computed for three 'species': lop (lowener. ions, ~1eV/e~130eV/e); hip (hiener. ions, ~130eV/e~45keV/e); alle (electrons, ~30eV  ~45keV ). The electron measurements are obtained 21.5 secs after the ion measurements. Epoch is the measurement time appropriate for the ions. The moments are computed after the fluxes are corrected for background and s/c potential. Algorithms for these corrections are relatively unsophisticated, so the moments are suspect during times of high background and/or high spacecraft potential. Because the determined spacecraft potential is not very precise, the magnitude of the lowenergy ion flow velocity is probably not accurate, but the flow direction is well determined. Tperp and Tpara are obtained from diagonalization of the 3dimensional temperature matrix, with the parallel direction assigned to the eigenvalue which is most different from the other two. The corresponding eigenvector is the symmetry axis of the distribution and should be equivalent to the magnetic field direction. The eigenvalue ratio Tperp/Tmid, which is provided for each species, is a measure of the symmetry of the distribution and should be ~1.0 for a good determination. Several of the parameters have a fairly high daily dynamic range and for survey purposes are best displayed logarithmically. These parameters are indicated by nonzero 'SCALEMIN' values in this file. A quality flag value of 1 indicates that the values are suspect because of unreliable location info.
This is a revised version of the data; the PI team reprocessed the data and provided this replacement version in July 1986. The new version can be verified by the wording in the header information, which contains "...FPE 2D IONS 85. LANL/MPE,..." in the revised version....Electron time tags removed Mag Latitude added .Local time added Post Gap flag added .Ratio variables changed Modified SEP 1994 .Changes noted in mail message from M.Kessel .New Dict keys added sep95 .Added new global attr. and variables from M.Kessel Oct 98.Electron time tags removed Mag Latitude added .Local time added Post Gap flag added .Ratio variables changed Modified SEP 1994 .Changes noted in mail message from M.Kessel .New Dict keys added sep95 .Added new global attr. and variables from M.Kessel Oct 98.Electron time tags removed Mag Latitude added .Local time added Post Gap flag added .Ratio variables changed Modified SEP 1994 .Changes noted in mail message from M.Kessel .New Dict keys added sep95 .Added new global attr. and variables from M.Kessel Oct 98.Electron time tags removed Mag Latitude added .Local time added Post Gap flag added .Ratio variables changed Modified SEP 1994 .Changes noted in mail message from M.Kessel .New Dict keys added sep95 .Added new global attr. and variables from M.Kessel Oct 98.Electron time tags removed Mag Latitude added .Local time added Post Gap flag added .Ratio variables changed Modified SEP 1994 .Changes noted in mail message from M.Kessel .New Dict keys added sep95 .Added new global attr. and variables from M.Kessel Oct 98 Electron time tags removed Mag Latitude added Local time added Post Gap flag added Ratio variables changed Modified SEP 1994 Changes noted in mail message from M.Kessel New Dict keys added sep95 Added new global attr. and variables from M.Kessel Oct 98
0: 50 eV to 20 keV per charge.1: 70 eV to 40 keV per charge
T = (Txx + Tyy)/2. = average 2D temperature (units = Kelvin).
Counting statistics and thus moments parameters are problematic for Den < 0.1 per cm3, including DEN, ENDEN, VX, VY, and T.
Spacecraft coordinate axes normally differ by no more than a few degrees from the respective GSE axes..The 2D bulk velocity essentially represents the projection of the true velocity onto the symmetry plane of the analyzers, i.e., approximately the ecliptic plane.
Spacecraft coordinate axes normally differ by no more than a few degrees from the respective GSE axes..The 2D bulk velocity essentially represents the projection of the true velocity onto the symmetry plane of the analyzers, i.e., approximately the ecliptic plane.
No TEXT global attribute value.
TEPC serrial number = 1003 TEPC Analysis SoftwareVersion Number = 3.1
ISS FPMU 1sec Ionosphere Summary Wide Langmuir Probe (WLP) Density and Narrow Langmuir Probe (NLP) Temperature Records
Geodetic Latitude
Geodetic Longitude
Geodetic Altitude
Ion density derived from FPMU Wide Langmuir Probe. Can be used also for electron density assuming quasineutrality
Electron temperature derived from FPMU Narrow Langmuir Probe.
This ISS pitch attitude information is necessary for proper derivation of the NLP density. NLP is a cylindrical Langmuir probe which is symmetric about roll and yaw axes.
Percent solar illumination with no correction for atmospheric refraction
Flag indicating time code was correct in original file (0) or a corrupt time code was corrected during processing (1)
Magnetic field measurements on the Interball Tail satellites are carried out by IZMIRAN and Space Research Institute RAS (SRI) since 1995. Satellite has the orbits with apogee 200000 (30 Re) and perigee 500 km. and provides measurements in the solar wind and in the different regions of the magnetosphere at the same time with Geotail, Polar and InterbalA working in the magnetosphere and Wind, ACE in the solar wind. Magnetic field measurements onboard the Interball Tail Probe are carried out by the FM3I and MFI instruments. FM3I consists of two fluxgate magnetometers M1 and M2 covering two different ranges: 200 nT and 1000 nT. The M2 instrument is mostly used to perform the attitude control of the INTERBALL TAIL spacecraft. M1 magnetometer data are transmitted to the scientific SSNI telemetry system at rates 0.12516 vectors/s depending on the instrument operating mode. The magnetic field data from the M2 magnetometer are transmitted at the rate 1 vectors per 6 sec. to the BNS attitude control system. MFI magnetometer has the next parameters: measured range 0.337.5 nT, frequency range 02 Hz, sampling rate from 1/4 to 8 measurements per second. FM3 M2 magnetometer failed in February 1996, FM3 M1 and MFI are working until now. Data presented here are the combination of the data of all magnetometers. First of all FM3 M1 data are used, if they are absent, used MFI data and if data of both magnetometer are absent, FM3 M2 data presented. In case of FM3 M1 and MFI, data are averaged for 6 seconds intervals.
created CDF August 2000 by Mona Kessel, data provided by Dr. Valery G. Petrov ZMIRAN, Troitsk, Moscow region, 142092, Russia http://antares.izmiran.rssi.ru/projects/PROGNOZMF/
Radioemission flux measured in 100, 252, 500 kHz ranges, the passband 10 kHz. Loop antenna with 1.5 m2 area is used. Full description: http://www.iki.rssi.ru/interball.html
created May 1996
2 min average of spectral amplitudes in three ranges, AKRX instrument
No TEXT global attribute value.
created July 1996
2 min. resolution
2 min. resolution
2 min resolution
2 min resolution
2 min. resolution
No TEXT global attribute value.
created Mar 1996
2 min. resolution
2 min. resolution
2 min. resolution
2 min. resolution
No TEXT global attribute value.
created Mar 1996
sensor offset at an angle 180 deg with respect to the sunward directed spacecraft spin axis
sensor offset at an angle 180 deg with respect to the sunward directed spacecraft spin axis
sensor offset at an angle 180 deg with respect to the sunward directed spacecraft spin axis
The value is taken from the sensor that can scan the angle's interval 45180 deg or can be fixed at angles 45, 90, 135, 180 deg. with respect to the sunward directed spacecraft spin axis
Electron and proton sensors of EV3 subsystem are offset at an angle 135 deg with respect to the sunward directed spacecraft spin axis
Electron and proton sensors of EV3 subsystem are offset at an angle 135 deg with respect to the sunward directed spacecraft spin axis
Count rate of H+, O+ ions in 2 min, three directions, (130 keV) Status flag shows instrument mode. Data description: http://www.iki.rssi.ru/interball.html
created Feb 1996
No TEXT global attribute value.
created Oct 2003
2 min. average, ASPI MIFM/PRAM magnetometer
2 min. average, ASPI MIFM/PRAM magnetometer
2 min. average, ASPI MIFM/PRAM magnetometer
2 min average of spectral amplitudes in two ranges, ASPI MIFM/PRAM magnetometer
No TEXT global attribute value.
created Feb 1997
2 min. resolution
Magnetic field averages and variance are computed from 4 Hz or 1 Hz data Mf1 magnetic field AC amplitudes are measured by fluxgate sensor. Mf2 magnetic field AC amplitudes are measured by searchcoil. Mf3 plasma wave AC amplitudesare measured by Langmuir splitprobe. Full description: http://www.iki.rssi.ru/interball.html
created Jan 1998
2 min average of spectral amplitudes in two ranges, ASPI MIFM/PRAM fluxgate
2 min average of spectral amplitudes in five ranges, ASPI MIFM/PRAM searchcoil
2 min average of spectral amplitudes in five ranges, ASPI MIFM/PRAM split Langmuir probe
2 min. average, ASPI MIFM/PRAM magnetometer
2 min. average, ASPI MIFM/PRAM magnetometer
2 min. average, ASPI MIFM/PRAM magnetometer
2 min. average, ASPI MIFM/PRAM magnetometer
No TEXT global attribute value.
created Jul 1998