
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 https://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 https://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 https://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 https://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 https://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 https://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 https://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 https://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 https://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 https://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 https://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 https://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 https://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 https://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 https://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 https://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.
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.
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 https://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.
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.
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.
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 https://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 https://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 https://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 https://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 https://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 https://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.
Dataset in CDAWeb
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 https://spdf.gsfc.nasa.gov/pub/data/imp/imp8/mag/15s_ascii_v3/00_IMP8_15s_data_d ocum.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 https://spdf.gsfc.nasa.gov/pub/data/imp/imp8/mag/320ms_ascii/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)
Dataset in CDAWeb
Generated by SSCWeb from Heather Franz's "Second Experimental Ephemeris" as approved by IMP8 PIs
Originated 03/14/96
Dataset in CDAWeb
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 (6 monthscadence) IBEXHi map data for the first seven years, 20092015, with multiple versions of data sets including no corrections, full corrections for spacecraft motion, and corrections for ENA survival probability between 1 and 100 AU. 3: The data consist of allsky maps in Solar West Ecliptic angles of 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: 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. 7: nocg = no ComptonGetting corrections 8: 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. 9: noSP  no survival probability corrections have been applied to the data. 10: omni = data from all directions. 11: ram = data was collected when the spacecraft was ramming into the incoming ENAs. 12: antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 13: The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015). 14: Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 15: Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 16: Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 17: Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 18: Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 19: Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 20: Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 21: Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 22: Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 23: Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 24: Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 25: Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 26: Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 27: Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 28: 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 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 (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 (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 (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 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 (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 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 (6 monthscadence) IBEXHi map data for the first seven years, 20092015, with multiple versions of data sets including no corrections, full corrections for spacecraft motion, and corrections for ENA survival probability between 1 and 100 AU. 3: The data consist of allsky maps in Solar West Ecliptic angles of 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: 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. 7: nocg = no ComptonGetting corrections 8: 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. 9: noSP  no survival probability corrections have been applied to the data. 10: omni = data from all directions. 11: ram = data was collected when the spacecraft was ramming into the incoming ENAs. 12: antiram = data was collected when the spacecraft was moving away from the incoming ENAs. 13: The following list associates Release 10 map numbers (114) with mission year (17), orbits (11310b), and dates (12/25/200812/23/2015). 14: Map 1: year 1, orbits 1134, dates 12/25/200806/25/2009 15: Map 2: year 1, orbits 3558, dates 06/25/200912/25/2009 16: Map 3: year 2, orbits 5982, dates 12/25/200906/26/2010 17: Map 4: year 2, orbits 83106, dates 06/26/201012/26/2010 18: Map 5: year 3, orbits 107130a, dates 12/26/201006/25/2011 19: Map 6: year 3, orbits 130b150a, dates 06/25/201112/24/2011 20: Map 7: year 4, orbits 150b170a, dates 12/24/201106/22/2012 21: Map 8: year 4, orbits 170b190b, dates 06/22/201212/26/2012 22: Map 9: year 5, orbits 191a210b, dates 12/26/201206/26/2013 23: Map 10: year 5, orbits 211a230b, dates 06/26/201312/26/2013 24: Map 11: year 6, orbits 231a250b, dates 12/26/201306/26/2014 25: Map 12: year 6, orbits 251a270b, dates 06/26/201412/24/2014 26: Map 13: year 7, orbits 271a290b, dates 12/24/201406/24/2015 27: Map 14: year 7, orbits 291a310b, dates 06/24/201512/23/2015 28: 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 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
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 Mar 1996
15 min averaged value of southern index is repeated for three times.
5 min. resolution
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. For a more detailed description see .http://ulcar.uml.edu/rpi.html.
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
tbd
This is a virtual variable computed in read_myCDF
Counterclockwise defined to be the positive direction. Represents the angle of rotation of the image field necessary to orient the North magnetic field at the top of the user's perspective.
Geo = geographic coordinates
GSM = geocentric solar magnetospheric coordinates
No TEXT global attribute value.
No TEXT global attribute value.
No TEXT global attribute value.
TBD
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
Values 0 to 254 cover 0 to 360 degrees
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)
TBD
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
Dataset in CDAWeb
tbs
tbs
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 https://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 this site https://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 from https://spdf.gsfc.nasa.gov/pub/data/isee/isee3/magnetic_fields/ 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 new CDF by selecting only certain variables from those available in the original barebones CDF (SPHE00414).
Velocity units were changed to km/sec, and Hi, Mid, & Lowest energy channels above SC potential were changed 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.
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 data are provided at a temporal resolution of approximately 60 seconds. They represent moments of individual twodimensional (2D) distributions obtained in approximately 3 or approximately 6 seconds (see below). No time averaging over longer intervals is involved; instead, the temporal resolution of the full data set (approximately 3 / 6 / 12 s) was reduced to approximately 60 s. The UT given indicates the start of the respective sampling interval. For a description of the instrument see Bame et al., 1978 (IEEE Transact. Geosci. Electron. GE16, 216) and Bame et al., 1993 (Rev. Sci. Inst., 64, 1026). Remarks about the computation of the moments may be found in Paschmann et al., 1978 (Space Sci. Rev. 22, 717). The moments were computed for three 'species', but only the ion moments are included here: lop (lowener. ions, ~1eV/e~130eV/e); hip (hiener. ions, ~130eV/e~45keV/e); alle (electrons, ~30eV  ~45keV). 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 a 'SCALETYP' value of 'linear' 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.
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 data cover the solar wind seasons for the spacecraft (roughly July through December) from 1977 through 1983. The temporal resolution is 24 seconds at high data rate and 48 seconds at low data rate. Among the parameters, the flow azimuth is given in degrees, with 0 degrees corresponding to flow from the sun [corrected for aberration] and positive azimuths corresponding to flow toward dawn; flow latitude is in degrees, with positive latitudes corresponding to flow toward the south; an alpha/proton fraction of 0.00 means no determination was 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. References: 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., Magnetospheric plasma analyzer for spacecraft with constrained resources, Rev. Sci. Instrum., 64, 1026 (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 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.
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.
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 data are provided at a temporal resolution of approximately 60 seconds. They represent moments of individual twodimensional (2D) distributions obtained in approximately 3 or approximately 6 seconds (see below). No time averaging over longer intervals is involved; instead, the temporal resolution of the full data set (approximately 3 / 6 / 12 s) was reduced to approximately 60 s. The UT given indicates the start of the respective sampling interval. For a description of the instrument see Bame et al., 1978 (IEEE Transact. Geosci. Electron. GE16, 216) and Bame et al., 1993 (Rev. Sci. Inst., 64, 1026). Remarks about the computation of the moments may be found in Paschmann et al., 1978 (Space Sci. Rev. 22, 717). The moments were computed for three 'species', but only the ion moments are included here: lop (lowener. ions, ~1eV/e~130eV/e); hip (hiener. ions, ~130eV/e~45keV/e); alle (electrons, ~30eV  ~45keV). 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 a 'SCALETYP' value of 'log' 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.
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 Feb 1996
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 Mar 1996
Dataset in CDAWeb