CCSD1Z00000100000052CCSD1R00000300000032 DELIMITER=EOF; TYPE=CCSD1F000001; CCSD1C00000400000039 ADI=NURSPE49; SUD=NURSUC01; SUD=NURSPE00; CCSD1R00000300000032 DELIMITER=EOF; TYPE=CCSD1D000002; MEPS PROTON LEVEL 3TP DATA DESCRIPTION IN SFDU FORMAT Whole Data Set ============== DataSetName: MEPS_Proton_Level_3TP_description DataSource: UARS/PEM UARS = Upper Atmosphere Research Satellite PEM = Particle Environment Monitor MEPS = Medium Energy Particle Spectrometer ScientificContact: Dr. J. David Winningham Instrumentation and Space Research Division Southwest Research Institute P.O. Drawer 28510 6220 Culebra Road San Antonio, Texas 78228-0510, USA e-mail: david@dews1.space.swri.edu (Internet) PEM::DAVID (UARSNET) FAX: 210-647-4325 phone: 210-522-3075 Dr. Rudy Frahm Instrumentation and Space Research Division Southwest Research Institute P.O. Drawer 28510 6220 Culebra Road San Antonio, Texas 78228-0510, USA e-mail: rudy@pemrac.space.swri.edu (Internet) PEM::RUDY (UARSNET) SWRI::RUDYF (SPAN) FAX: 210-647-4325 phone: 210-522-3855 SourceCharacteristics: Refer to NURSPE00 InvestigationObjectives: Refer to NURSPE00 InstrumentAttributes: Refer to NURSPE00 MeasuredParameters: Refer to NURSPE00 DataSetQuality: Data quality is presented at level 0 by the Data Capture Facility and reflects the confidence level of the telemetry. These quality values are preserved and along with PEM instrument checks, the quality values are used to generate level 2 quality information. Level 2 read routines apply instrument corrections which may modify the quality fields stored in level 2 and these results are presented along with the data to level 3AT processing, which generates Level 3TP files. Confidence limits in the form of standard deviations for each data point are set using count rate statistics, the data compression error associated with each spectral value, and the range of expected values (based on similar previous satellite measurements). All input data are examined in the level 3AT processing. PEM is an energy input instrument. The Level 3AT and 3TP proton data products are altitude profiles of energy deposition rate determined for incident protons. The program works with the measured spectral form in number intensity [number/(cm**2-s-sr-eV)] which is eventually related to the energy deposition rate [erg/(cm**3-s)] vs. height. In addition to the quality indicators per data point, there is a quality indicator per file stored in the CDHF database. The UARS Science Team discussed the data quality indicators, n.q, which are applied to daily data files in the CDHF, and the following was decided: The n's are defined as: n = 0: machine inspected data, n = 1: qualitative evaluation, n = 2: intensive analysis; The q's are defined as: q = 1: the data in the file are < 50% good; q = 2: the data in the file are 50% to 75% good; q = 3: the data in the file are 76% to 98% good; q = 4: the data in the file are > 98% good; For the PEM Proton Level 3TP files, the production process assigns a value of n = 0 to indicate machine inspected data, and q is determined by the percentage of data actually used in the energy deposition calculations. There are several reasons data are not used in the energy deposition algorithm: (1) fill data, (2) instrument off, (3) data contamination, etc. DataProcessingOverview: The MEPS Proton Level 3TP file is generated by the Level 3AT production program PEMPROTON_DEP. This program uses the PEM Level 2 data for input. The Level 2 read routines are accessed which return corrected data to the Level 3AT process in differential number intensity scientific units. Energy deposition calculations are made and the error terms are computed. Then the energy deposition values are mapped to the correct altitude based on the magnetic field line for that specific time and position of the spacecraft. These values are then written to the PEM proton Level 3AT file. (See the Algorithms section for details.) Both HEPS and MEPS data are used to generate the 3AT data; however, data in the Level 3AT file depends on good quality HEPS AND MEPS data. Level 3TP files are generated for each instrument and require good quality for only that instrument's data. This Level 3TP file contains profiles which were generated by the MEPS instrument only. These MEPS profiles are generated every 2 UARS seconds whereas the Level 3AT data are averaged data for one UARS minute. This detailed 2 UARS second MEPS profile is recorded in the Level 3TP file. DataUsage: Data included in this file is the energy deposited by MEPS every 2 UARS seconds. Its use is unrestricted, however there are three major assumptions which may affect the profile values which are generated. The first assumption is that the particle distribution is isotropic. Assuming isotropy means that the smallest pitch angle sensor was chosen from those active MEPS sensors. In some cases, the sensor at the smallest pitch angle is not active and not considered when determining which sensor's data to use. The spectra from the MEPS sensor chosen are taken to be representative of the proton distribution which is assumed to be isotropic. Therefore, no pitch angle dependence is accounted for in the energy deposition profiles. The second assumption is that the atmosphere is described by the 1976 US Standard Atmosphere (see reference below). The US Standard Atmospheric Mass Density (g/cm**3) can be used to remove the dependence of the atmospheric model using the following table: Atmospheric UARS Mass Density Altitude index (g/cm**3) 88 2905950E-21 87 3168611E-21 86 3457383E-21 85 3775162E-21 84 4125200E-21 83 4511124E-21 82 4937086E-21 81 5407737E-21 80 5928330E-21 79 6504878E-21 78 7144004E-21 77 7853276E-21 76 8641270E-21 75 9516793E-21 74 1049204E-20 73 1158012E-20 72 1279610E-20 71 1415803E-20 70 1568508E-20 69 1739997E-20 68 1932890E-20 67 2150058E-20 66 2395480E-20 65 2673666E-20 64 2989550E-20 63 3349080E-20 62 3758930E-20 61 4226352E-20 60 4762440E-20 59 5380936E-20 58 6095200E-20 57 6921054E-20 56 7880750E-20 55 9000697E-20 54 1031370E-19 53 1186013E-19 52 1369090E-19 51 1586900E-19 50 1847640E-19 49 2161526E-19 48 2542360E-19 47 3007750E-19 46 3581700E-19 45 4295290E-19 44 5193400E-19 43 6335951E-19 42 7811800E-19 41 9743304E-19 40 1232390E-18 39 1583035E-18 38 2073680E-18 37 2775982E-18 36 3826590E-18 35 5446421E-18 34 8138960E-18 33 1284476E-17 32 2217720E-17 31 3312867E-17 30 5136439E-17 29 8222952E-17 28 1353687E-16 27 2277124E-16 26 3888122E-16 25 6697204E-16 24 1156788E-15 23 1990062E-15 22 3401950E-15 21 5791054E-15 20 9661521E-15 19 1569099E-14 18 2513226E-14 17 3973350E-14 16 6191171E-14 15 9475890E-14 14 1423159E-13 13 2107805E-13 12 3082460E-13 11 5653650E-13 10 1022060E-12 9 1956184E-12 8 3977180E-12 7 8424940E-12 6 1832530E-11 5 3989630E-11 4 8851480E-11 3 1938330E-10 2 4116010E-10 1 7329160E-10 "U.S. Standard Atmosphere, 1976", Compiled by the National Oceanic and Atmospheric Administration, National Aeronautics and Space Administration, and the United States Air Force, Washington, DC, (U.S. Government Printing Office) October 1976. The average energy for each ionization may be taken as 35 [eV/ionization]. For ionization rates below 100 km, constant fractions may indicate the ionization rate for several ions. This fraction is listed below: Ionizations of N2+ [fraction of ionization rate] = 0.585 Ionizations of N+ [fraction of ionization rate] = 0.185 Ionizations of O2+ [fraction of ionization rate] = 0.154 Ionizations of O+ [fraction of ionization rate] = 0.076 Most of the proton energy deposited from MEPS will be above 90 km, in the Thermosphere. The third assumption is that particles measured by the proton sensors are protons. This is not always true. The MEPS instrument makes no distinction between particles with a positive charge. At the altitude of UARS, there can be at times significant numbers of ions. In all cases, the MEPS instrument does not discriminate among mass species. Incorrect positive mass species will lead to incorrect estimates of the proton flux. In particular, the sensor efficiency is affected because different ion species are more or less efficient at being detected. Since each ion has a different energy dependence of detection, a constant sensor efficiency is used for all ion measurements. Constants of telemetry reconstruction are performed assuming that all detected ions are protons. Data Use Warning: ----------------- At lower energies (in the thermosphere), the Level 3TP profile is quite consistent with the energy spectra. No abnormal anomalies have been seen. However, there is a slight chance that there may be contamination effects occurring in the upper proton channels. The calibration criterion used for detector noise was less than 1 count per accumulation period due to noise. When noise occurs, it shows strongest in the highest energy channels. Lab calibrations show that there is no noise below 2000 V plate voltage, which corresponds to greater than 26 keV in energy. In the laboratory, tests of the proton channels were conducted with electrons. Since the proton detection efficiency is less, the amount of proton contamination is expected to be even less than that from electrons. Data Gaps: ---------- In order to achieve data in the this Level 3TP file, the MEPS data must be available and producing high quality data. There are times when the instrument does not produce data correctly. There are two effects which usually cause this. These effects are (1) no sensor within the loss cone [defined relative to the magnetic field which separates those particles lost to the atmosphere and those which remain in the magnetosphere, see definition on page 162 of Haymes, R. C., Introduction to Space Science (Wiley: New York) 1971] (pitch angle too big) and (2) charging contamination. The first condition usually occurs around the equator. The second condition occurs when the sun is visible to the spacecraft. Most of the data not reported in the Level 3TP file is due to this second effect. Solar Contamination ------------------- When the spacecraft and sun light meet, an extra plasma occurs around the spacecraft due to photoexcitation of the spacecraft materials and the interaction of the spacecraft power system. The result is that the spacecraft charges. Effects are strongest at local spacecraft sunrise, when the charge can reach 102 volts. During the day, the spacecraft charge has been known to vary between 50-90 volts. Spacecraft charge is always negative. In order to attempt to balance the charges, the spacecraft draws to it positive ions. The energy achieved by these ions is on the order of the spacecraft potential. High ion counting rates have been observed at the spacecraft, at times approaching the limits of the instrument. Ions with this high of an intensity generate two unreal effects in the data. The first is ghost peaks in the proton spectra. Here, even though the probability is small, there is enough intensity to saturate the secondary emission reduction coatings on the internal instrument parts and ions reflect into the sensor. The primary ions also generate secondary electrons. Reflected ions give a signal in the proton detector in the mid-sweep range. Secondary electrons give a signal in the electron detector at the high energy end of the sweep. Reflected ions show as a ghost ion peak which tracks the charging peak in the proton spectra. If atmospheric energy deposition were computed from this proton signal, the profile would show an unrealistic amount of energy being deposited at the highest altitudes (around 350 km). If atmospheric energy deposition were computed from the electron signal, the profile would show an unrealistic amount of energy being deposited at the lowest MEPS altitudes (around 90 km). To avoid misinterpretation of the energy deposition profile, the profile of atmospheric energy deposition is not computed when the spacecraft is charged (which translates to when the spacecraft is in sunlight). DataOrganization: FileClassRelationships: LitReferences: "Particle Environment Monitor Software Specifications, Data Descriptions, and Algorithms," Southwest Research Institute Document 7845-SDD, San Antonio, Texas. Referred to as the SDD document. "The UARS Particle Environment Monitor," J. D. Winningham, J. R. Sharber, R. A. Frahm, J. L. Burch, N. Eaker, R. K. Black, V. A. Blevins, J. P. Andrews, J. Rudzki, M. J. Sablik, D. L. Chenette, D. W. Datlowe, E. E. Gaines, W. I. Imhof, R. W. Nightingale, J. B. Reagan, R. M. Robinson, T. L. Schumaker, E. G. Shelley, R. R. Vondrak, H. D. Voss, P. F. Bythrow, B. J. Anderson, T. A. Potemra, L. J. Zanetti, D. B. Holland, M. H. Rees, D. Lummerzheim, G. C. Reid, R. G. Roble, C. R. Clauer, and P. M. Banks, Journal of Geophysical Research, 98, 10649-10666, 1993. File Class ========== FileClassName: MEPS_PROT_LEVEL3TP RecordTypeNames: SFDU_Label, File_Label_Record, Continuation_Label_Record, Data_Record Algorithms: What is stored in the MEPS Level 3TP proton file: --------------------------------------------------- Three time and position markers are written into this data file. First, the time and position of the center of the UARS EMAF are written in the header portion of each record. The time recorded is in two words, each 4-bytes long. The first word contains the year and day. The second word contains the time in UT milliseconds of day. Next are geodetic latitude and East longitude of the magnetic field line at DEPOSIT_ALTITUDE (about 100 km), expressed in degrees. Both quantities are stored as 4-byte real numbers and represent where the particles measured at the spacecraft would penetrate into the atmosphere. Estimates of the location of precipitation are made using a centered dipole magnetic field model (see below). The first parameters written to the data buffer are the second series of time and position markers. These are similar to the first except that the time computed for a marker is from the center of the UARS minute minus one-third of the time it takes to generate an EMAF (1 EMAF is generated every UARS minute). Geodetic positions for energy deposit are determined and written as 4-byte real numbers. The structure repeats a third time. Here, the time computed for the marker is from the center of the UARS minute plus one-third of the time it takes to generate an EMAF. Geodetic latitude and east longitude are again computed for this time. Next in the data buffer are the energy deposition and corresponding standard deviations. Data are reported for each UARS altitude every 2 UARS seconds. The units for each reported value are erg/(cm**3-s). UARS standard altitudes may be determined by the following: dimension z(88) c determine the defined UARS altitude levels do i=1,88 if (i .le. 12) then Z(I) = float(5*i) else if (i .le. 32) then z(i) = float(60+3*(i-12)) else z(i) = float(120+5*(i-32)) endif enddo These profiles are written as a block of 4-byte real numbers that are 32 2-UARS seconds in duration and 88 altitude levels. The actual profiles are written one after the other for the UARS EMAF. If at least one profile exists in the EMAF, then the entire record is written. Zero values fill the uncomputed profiles. Lastly, the standard deviations in the profiles are written as a block. There is a one-to-one correspondence of the standard deviations to the profile data values. Both are a by-product of the Level 3AT processing. Inputs to the MEPS Level 3TP proton file: ------------------------------------------- Level 3TP data is generated during the processing of Level 3AT data. Inputs to the level 3AT algorithm are the data and quality information which are included in the level 2 HEPS, MEPS, HEPS engineering, MEPS engineering, and VMAG files. Level 0 engineering files and spacecraft O/A services are also accessed. Data corrections are performed in standard read routines of PEM Level 2 data. MEPS Level 3AT data is decimated MEPS Level 3TP data. MEPS Level 3TP data shows much more structure than does Level 3AT data since the Level 3AT data is the UARS minute average of the 3TP data. Processing: ----------- A brief summary of the algorithm process is (1) get the instrument data, (2) correct the instrument data, (3) convert the data into the proper units, (4) select the MEPS sensor whose data is closest to zero degrees pitch angle, (5) search for and estimate missing MEPS data values, (6) apply isotropic assumption, (7) determine the MEPS vertical energy deposition profiles, (8) determine the proper mapping of a vertical profile to one which is along a magnetic field line, (9) map the MEPS vertical profiles to be along the magnetic field, (10) determine the location of where the particles are incident upon the atmosphere. Step (1): The MEPS MA and MB files are accessed and contain zenith MEPS proton sensor data. The proton data in the MB data file has been multiplexed by the spacecraft and data at every-other energy step is missing. The VM data file of VMAG is accessed for the components of the magnetic field. These data form the core of the energy deposition calculations. For the format of the data files, please refer to the SDD document. Step (2): MEPS data suffers from contamination due to spacecraft charging. The negative spacecraft charge accelerates the thermal ion plasma and repels the low energy electron plasma. High velocity, high density thermal ions saturate the internal instrument coatings, which are included on critical surfaces to suppress internal noise. When these surfaces are saturated, incoming ions can reflect into the ion sensor causing ghost signals and they can also generate false electrons within the MEPS detectors causing false electron signals in the electron data. A set of level 2 read routines are supplied to read the level 2 data and apply the appropriate correction. It is suggested that these routines be used when accessing PEM HEPS and MEPS data. Corrections to both HEPS and MEPS data are non-trivial. Incorrect results will be obtained if level 2 data are accessed without using these level 2 read routines. Step (3): The conversion of the data are intertwined with the conversion to science units. Strictly speaking, conversion to the science units are performed by applying the appropriate look-up tables provided in the IDF and SUF files. The level 2 read routines supply the proper science unit as well as correct the data appropriately. Refer to the SDD document for content of the SUF and IDF files. For this application, the data are returned in differential number intensity units: number/(cm**2-s-sr-eV). Conversions are performed with MEPS data to hemispherical flux units, number/(cm**2-s), by multiplication of the energy band width of each step and 2*pi sr. In other words, the flux from each spectral point is computed to be an isotropic value. Magnetic field measurements are averaged and normalized for a UARS minute. The result represents the average magnetic field vector in the UARS minute. This magnetic field value will be used to orient the detected particles and orient the spacecraft within the magnetic field. Step (4): A MEPS energy deposition profile is generated for every two seconds. It determines the pitch angle only at the center of a UARS minute from the average position of the magnetic field and the sensor look directions. Pitch angle information from MEPS is not generated every two seconds. MEPS proton sensors in each look direction are compared with the average magnetic field. The cosine pitch angle is computed against the minute averaged magnetic field. This value is compared against the cosine of 55 degrees in order to exclude measurements made outside of the loss cone (when the particle pitch angle becomes too great, the particles do not enter the atmosphere). From the sensors whose pitch angle is less than 55 degrees, the active sensor with the smallest pitch angle is chosen as providing a representative set of data. Thus, the sensor with the smallest pitch angle is chosen to provide data for analysis. At the UARS altitude, the loss cone is 60 degrees wide. MEPS detector half width is 2.5 degrees. To ensure that MEPS is detecting only precipitating protons requires that the sensor be positioned at about 55 degrees or less in pitch angle. A maximum deviation set of data is generated for each two-second MEPS spectrum from a product of the two-second data and the standard deviation determined for the two-second data. The maximum deviation data set represents the maximum value of each data point. A profile generated from this value represents the maximum statistical value possible for the measurement. Step (5): When data from energy steps of MEPS is missing due to bad quality or multiplexing of sensors, an estimation is made for a reasonable hemispherical flux value and maximum error value. Estimation is accomplished depending on where the bad or missing data is located. If the bad or missing point is at the beginning or end of an energy sweep, the nearest good data value is chosen to be duplicated into the bad or missing data positions and its corresponding maximum error value is also duplicated. For bad or missing points located within the energy sweep, good data values on either side of the bad or missing value are used to estimate what the bad or missing value should have been. The maximum error value is estimated taking the good maximum error values on either side of the bad or missing error value and estimating what the bad or missing error value should have been. Estimation is accomplished by linear interpolation in logarithmic space of the energy values. Step (6): MEPS proton energy deposition profiles are generated at standard energy values. These standard energy values are the average of the energy values determined from the possible detectors whose data might describe the resulting answer. MEPS standard energy values are: Energy Step Standard Energy Number (eV) 33 2.91122E+04 34 1.97480E+04 35 1.39153E+04 36 9.52458E+03 37 6.71471E+03 38 4.60053E+03 39 3.23367E+03 40 2.22585E+03 41 1.54576E+03 42 1.07540E+03 43 7.63316E+02 44 5.24758E+02 45 3.68482E+02 46 2.48661E+02 47 1.77226E+02 48 1.19109E+02 49 8.18583E+01 50 5.80468E+01 51 4.12694E+01 52 2.80626E+01 53 1.98982E+01 54 1.36075E+01 55 9.69931E+00 56 6.56109E+00 57 4.69378E+00 58 3.16407E+00 59 2.27025E+00 60 1.50116E+00 61 1.09042E+00 62 7.11750E-01 63 5.19070E-01 The data generated at the measured energies is the hemispherical flux. This is flux which penetrates through the downward hemisphere. This includes flux at large pitch angles which would never make it to the atmosphere. What we really want is the planar flux, that is, the flux through a planar surface perpendicular to a magnetic field line. The general expression to convert hemispherical flux into planar flux is dependent on the pitch angle (a) which describes the distribution. It is: if a = -1; 1.5*ln(3.0) - 1.0 if a = -2; 2.0 - ln(3.0) otherwise [3.0**(a+2.0) - 2.0*a - 5.0]/[(a + 1.0)*(a + 2.0)*2.0**(a+2)] For the isotropic case, a = 0 degrees. This means that the factor we wish to multiply out flux by in order to change it from a hemispherical flux value to a planar flux value is 0.5. Thus, the MEPS proton standard energy hemispherical flux values are converted to planar flux by multipling by 0.5. The 0.5 factor is also used in order to convert the maximum deviations for the same reason. Step (7): The MEPS energy deposition profiles are computed by using the standard energy step numbers and isotropic assumption (pitch angle of zero degrees) to look up a standard energy deposition profile. The standard energy deposition profile is computed for unit incident flux, so the profile is then adjusted by the fitted flux. The adjusted profile at each standard energy is accumulated to form the two-second deposition profile from MEPS protons at normal incidence. The two-second MEPS energy deposition profile from the maximum deviations is computed by using the standard energy step number and isotropic assumption (pitch angle of zero degrees) to look up a standard energy deposition profile. The maximum error energy deposition profile is computed for unit incident flux, so the profile is then adjusted by the fitted maximum error flux. The adjusted profile for each standard energy is accumulated to form the two-second maximum deviation energy deposition profile from MEPS protons at normal incidence. The MEPS standard deviation profile of the energy deposition values is determined every two seconds by taking the difference between this maximum profile and the profile generated from its corresponding data. Step (8): Energy deposited into the atmosphere is deposited along the magnetic field line and not vertically. Since the magnetic field has a dip angle associated with its direction, in a given altitude range an incident particle will have more atmosphere to interact with. For the UARS altitude and using the centered dipole approximation to the magnetic field, determination of the position of the spacecraft in the magnetic field is made by VMAG data and the shape of the magnetic field line (defined by the dipole assumption). Interpolation in a look-up table, relating the vertical altitude to the altitude along the magnetic field line where amount of atmosphere traversed under both conditions is the same, is made for each energy step. This generates a matrix describing what fraction each UARS vertical altitude is mapped into which UARS altitude as measured along a magnetic field line. The look-up table used to cross reference mapped altitudes is generated at finer resolution than that reported in the 3TP file. The 1976 US Standard Atmosphere is used in order to determine the amount of atmosphere which is traversed at normal incidence for each two kilometers of altitude. At every degree of dipole latitudes from 1 to 80 degrees, the 1976 US Standard Atmosphere is used in order to determine the altitude at which an equivalent amount of atmosphere is traversed along the magnetic field line. Step (9): Each profile and error profile of MEPS is individually converted from the vertical profile to a profile along the magnetic field line. This is done by applying the matrix which relates how each altitude value in the vertical profile is related to a standard altitude in the magnetic field mapped profile. When mapping the vertical altitude values, fractions of the flux can appear at several mapped altitudes. For each vertical altitude, 100 % of the flux is mapped to the magnetic field line profile except at the highest altitudes of the magnetic field mapped profile. The reason is that fractions of flux may deposit above the maximum UARS altitude and less than 100 % of the flux will be deposited below the maximum UARS altitude. Step (10): The latitude and longitude reported in the level 3TP file, expressed in geodetic coordinates, is the position of a dipole magnetic field line at the DEPOSIT_ALTITUDE (= 100 km) which intersects the spacecraft. In other words, this is the position of the top of the atmosphere where the protons which UARS detects would precipitate. Determination of the position of UARS comes from O/A services. The ECI position of UARS is projected into the frame of magnetic coordinates using a Centered Dipole with the pole of the dipole at DIPOLE_LAT (= -78.3 degrees) and DIPOLE_LONG (= 111.0 degrees), also in ECI coordinates. Using the analytic expression of a dipole field line, the magnetic position is determined for the deposition altitude. This position is then rotated back into ECI coordinates. Lastly, the O/A services are used to convert the ECI latitude to geodetic latitude. Refer to the subroutine find_ep_traced_latlong.for and the Orbit/Attitude Services Programmer's Guide for UARS. References for the formulation of the Centered Dipole magnetic field model are described in many beginning texts on space sciences, the magnetosphere, the ionosphere, or in some general reference texts on the near earth environment. Here are some examples: Chapman, S., and J. Bartels, Geomagnetism (Oxford Press: London) 1940. (although a bit abstract, Volume 1 is the best) Hargreaves, J. k., The Upper Atmosphere and Solar-Terrestrial Relations: An Introduction to the Aerospace Environment (Van Nostrand Reinhold: New York) 1979. (pages 149-150 specifically) Haymes, R. C., Introduction to Space Science (Wiley: New York) 1971. (Section 9.4 is the best) Tascione, T. F., Introduction to the Space Environment (Orbit: Malabar FL) 1988. (Chapter 4) United States Air Force, Handbook of Geophysics and the Space Environment, ed. A. S. Jursa, National Technical Information Service, Springfield, VA, 22161, 1985. (page 4-25 is the best) Positions of particle precipitation are computed at the center time for the EMAF. They are also computed at a third of the EMAF interval before and after the center EMAF time. The center time and position are written to the header portion of the data record and the other times and positions are written to the data buffer of each data record in the 3TP MEPS file as the first 32 bytes (two blocks of 16 bytes). They are arranged as 4-byte words, the first two in a block specifying the time and the next two 4-byte real values specifying the latitude and longitude. The MEPS 3TP data buffer is arranged as follows: Word Size Contents 1 integer*4 center minus one third EMAF time: year and day 2 integer*4 center minus one third EMAF time: UARS millisecond 3 real*4 center minus one third EMAF traced latitude 4 real*4 center minus one third EMAF traced longitude 5 integer*4 center plus one third EMAF time: year and day 6 integer*4 center plus one third EMAF time: UARS millisecond 7 real*4 center plus one third EMAF traced latitude 8 real*4 center plus one third EMAF traced longitude 9 | real*4 MEPS proton energy deposition data in a 32 x 88 | array corresponding to 32 2-second profiles for each | of the 88 standard UARS altitudes | real*4 MEPS energy deposition standard deviations in a 32 x 88 | array in one-to-one correspondence with the energy | deposition values \|/ end of data buffer FileClassSyntax: Number of records is specified in the File_Label_Record List of Records in file: #1: SFDU_Label #2: File_Label_Record #3: Continuation_Label_Record Zero or more as specified in the File_Label_Record #4: Data_Record One or more as specified in the File_Label_Record Record ====== 1. SFDU_Label ------------- RecordName: SFDU_Label RecordStructure: Fixed Length RecordLength: 40 Bytes RecordFieldNames: Tz_Field, Lz_Field, Ti_Field, Li_Field RecordSyntax: 4 Fields #1: Tz_Field #2: Lz_Field #3: Ti_Field #4: Li_Field Fields ====== 1.1 Tz_Field ------------ FieldName: Tz_Field FieldSyntax: ASCII Character*12 String FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: SFDU Type (Tz) Field. Constant Value = 'CCSD1Z000001'. FieldRepresentation: 12A FieldDisplayFormat: A12 1.2 Lz_Field ------------ FieldName: Lz_Field FieldSyntax: ASCII Character*8 String FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: SFDU Length (Lz) Field. 20 + l where l is the length of the UARS file. Right justified, zero filled FieldRepresentation: 8A FieldDisplayFormat: A8 1.3 Ti_Field ------------ FieldName: Ti_Field FieldSyntax: ASCII Character*12 String FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: SFDU Type (Ti) Field. Constant value = 'NURS1I00PE49' FieldRepresentation: 12A FieldDisplayFormat: A12 1.4 Li_Field ------------ FieldName: Li_Field FieldSyntax: ASCII Character*8 String FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: SFDU Length (Lz) Field. Length of UARS file. Right justified, zero filled FieldRepresentation: 8A FieldDisplayFormat: A8 Record ====== 2. File_Label_Record -------------------- RecordName: File_Label_Record RecordStructure: Variable Length RecordLength: Max (148 + 28 * n, length of Data_Record) where n = Value (Number_of_Time/Version_Entries_in_Record) RecordFieldNames: Satellite_Identifier Record_Type Instrument_Identifier Data_Subtype_Or_Species Format_Version_Number Physical_Record_Count Number_Of_Continuation_Records_For_File_Label Number_Of_Physical_Records_In_File File_Creation_Time_In_VAX_VMS_ASCII_Format Year_For_First_Data_Record Day_Of_Year_For_First_Data_Record Milliseconds_Of_Day_For_First_Data_Record Year_For_Last_Data_Record Day_Of_Year_For_Last_Data_Record Milliseconds_Of_Day_For_Last_Data_Record Data_Level UARS_Day_Number Number_Of_32-bit_Words Spare Record_Length_In_Bytes CCB_Version_Number File_Cycle_Number Virtual_File_Flag Total_Number_Of_Time/Version_Entries_In_File Number_Of_Time/Version_Entries_In_Record Version_Entries RecordSyntax: 26 Fields #1 : Satellite_Identifier #2 : Record_Type #3 : Instrument_Identifier #4 : Data_Subtype_Or_Species #5 : Format_Version_Number #6 : Physical_Record_Count #7 : Number_Of_Continuation_Records_For_File_Label #8 : Number_Of_Physical_Records_In_File #9 : File_Creation_Time_In_VAX_VMS_ASCII_Format #10: Year_For_First_Data_Record #11: Day_Of_Year_For_First_Data_Record #12: Milliseconds_Of_Day_For_First_Data_Record #13: Year_For_Last_Data_Record #14: Day_Of_Year_For_Last_Data_Record #15: Milliseconds_Of_Day_For_Last_Data_Record #16: Data_Level #17: UARS_Day_Number #18: Number_Of_32-bit_Words #19: Spare #20: Record_Length_In_Bytes #21: CCB_Version_Number #22: File_Cycle_Number #23: Virtual_File_Flag #24: Total_Number_Of_Time/Version_Entries_In_File #25: Number_Of_Time/Version_Entries_In_Record #26: Version_Entries Fields ====== 2.1 Satellite_Identifier ------------------------ FieldName: Satellite_Identifier FieldSyntax: ASCII Character*4 String FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: Satellite identifier. Constant value 'UARS' FieldRepresentation: 4A FieldDisplayFormat: A4 2.2 Record_Type --------------- FieldName: Record_Type FieldSyntax: ASCII Character*2 String FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: Record type. Constant value ' 1' indicates a file label record. FieldRepresentation: 2A FieldDisplayFormat: A2 2.3 Instrument_Identifier ------------------------- FieldName: Instrument_Identifier FieldMnemonic: Data_Type FieldSyntax: ASCII Character*12 String FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: Instrument identifier. Constant value = 'PEM ' FieldRepresentation: 12A FieldDisplayFormat: A12 2.4 Data_Subtype_Or_Species --------------------------- FieldName: Data_Subtype_Or_Species FieldMnemonic: Subtype FieldSyntax: ASCII Character*12 String FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: Data subtype or species. Left justified, blank filled. Constant value = 'MEPS_PROT_ED' FieldRepresentation: 12A FieldDisplayFormat: A12 2.5 Format_Version_Number ------------------------- FieldName: Format_Version_Number FieldSyntax: ASCII Character*4 String FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: Format version number. Constant value ' 1' indicates that this is the first version of the Level 3TP file structure. FieldRepresentation: 4A FieldDisplayFormat: A4 2.6 Physical_Record_Count ------------------------- FieldName: Physical_Record_Count FieldSyntax: ASCII character*8 string FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: Physical record count. Constant value ' 1' indicates the label record is the logical first record in the file. FieldRepresentation: 8A FieldDisplayFormat: A8 2.7 Number_Of_Continuation_Records_For_File_Label ------------------------------------------------- FieldName: Number_Of_Continuation_Records_For_File_Label FieldSyntax: ASCII Character*4 String FieldUnits: n/a FieldResolution: n/a FieldRange: Integer >= 0 FieldDescription: Number of continuation records for file label for a virtual file (a level 3TP file containing a user specified time range that is not on day boundaries). Right justified, blank filled FieldRepresentation: 4A FieldDisplayFormat: A4 2.8 Number_Of_Physical_Records_In_File -------------------------------------- FieldName: Number_Of_Physical_Records_In_File FieldSyntax: ASCII Character*8 String FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: Number of physical records in file. Right justified, blank filled. Does not count SFDU label record. FieldRepresentation: 8A FieldDisplayFormat: A8 2.9 File_Creation_Time_In_VAX_VMS_ASCII_Format ---------------------------------------------- FieldName: File_Creation_Time_In_VAX_VMS_ASCII_Format FieldSyntax: ASCII Character*23 String FieldUnits: dd-mmm-yyyy hh:mm:ss.cc FieldResolution: 0.01 second FieldRange: n/a FieldDescription: File creation time in VAX VMS ASCII format indicates the date and time the file was cataloged in the UCSS. FieldRepresentation: 23A FieldDisplayFormat: A23 2.10 Year_For_First_Data_Record ------------------------------- FieldName: Year_For_First_Data_Record FieldSyntax: ASCII Character*3 String FieldUnits: Years since 1900 FieldResolution: n/a FieldRange: n/a FieldDescription: Year for first data record. Value is Year-1900. Right justified, blank filled. FieldRepresentation: 3A FieldDisplayFormat: A3 2.11 Day_Of_Year_For_First_Data_Record -------------------------------------- FieldName: Day_Of_Year_For_First_Data_Record FieldSyntax: ASCII Character*3 String FieldUnits: Day of Year FieldResolution: n/a FieldRange: Integer >= 1, <= 366 FieldDescription: Day of year for first data record. Right justified, blank filled. FieldRepresentation: 3A FieldDisplayFormat: A3 2.12 Milliseconds_Of_Day_For_First_Data_Record ---------------------------------------------- FieldName: Milliseconds_Of_Day_For_First_Data_Record FieldSyntax: ASCII Character*8 String FieldUnits: Milliseconds FieldResolution: 1 millisecond FieldRange: Integer >=0, <= 86399999 FieldDescription: Milliseconds of day for first data record. Right justified, blank filled. FieldRepresentation: 8A FieldDisplayFormat: A8 2.13 Year_For_Last_Data_Record ------------------------------ FieldName: Year_For_Last_Data_Record FieldSyntax: ASCII Character*3 String FieldUnits: Years since 1900 FieldResolution: n/a FieldRange: n/a FieldDescription: Year for last data record. Value is Year-1900. Right justified, blank filled. FieldRepresentation: 3A FieldDisplayFormat: A3 2.14 Day_Of_Year_For_Last_Data_Record ------------------------------------- FieldName: Day_Of_Year_For_Last_Data_Record FieldSyntax: ASCII Character*3 String FieldUnits: Day of year FieldResolution: n/a FieldRange: Integer >= 1, <= 366 FieldDescription: Day of year for last data record. Right justified, blank filled. FieldRepresentation: 3A FieldDisplayFormat: A3 2.15 Milliseconds_Of_Day_For_Last_Data_Record --------------------------------------------- FieldName: Milliseconds_Of_Day_For_Last_Data_Record FieldSyntax: ASCII Character*8 String FieldUnits: Milliseconds FieldResolution: 1 millisecond FieldRange: Integer >= 0, <= 86399999 FieldDescription: Milliseconds of day for last data record. Right justified, blank filled. FieldRepresentation: 8A FieldDisplayFormat: A8 2.16 Data_Level --------------- FieldName: Data_Level FieldSyntax: ASCII Character*3 String FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: Data level. Constant value '3TP' indicates parameter data that can be used in conjunction with the level 3AT data that has been placed on the standard UARS time and altitude/pressure grid. FieldRepresentation: 3A FieldDisplayFormat: A3 2.17 UARS_Day_Number -------------------- FieldName: UARS_Day_Number FieldMnemonic: UARS_Day FieldSyntax: ASCII Character*4 String FieldUnits: Days FieldResolution: 1 day FieldRange: Integer >= 1 FieldDescription: UARS day number (UARS day 1 = September 12, 1991) Right justified, blank filled. FieldRepresentation: 4A FieldDisplayFormat: A4 2.18 Number_Of_32-bit_Words --------------------------- FieldName: Number_Of_32-bit_Words FieldMnemonic: Max_Np FieldSyntax: Scalar FieldUnits: n/a FieldResolution: n/a FieldRange: Constant integer value = 5640 FieldDescription: Number of 32-bit parameter words. FieldRepresentation: VR4 FieldDisplayFormat: 2.19 Spare ---------- FieldName: Spare FieldSyntax: ASCII Character*2 string FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: Spare. Field contents undefined. FieldRepresentation: 2A FieldDisplayFormat: A2 2.20 Record_Length_In_Bytes --------------------------- FieldName: Record_Length_In_Bytes FieldSyntax: ASCII Character*5 String FieldUnits: Bytes FieldResolution: 4 bytes FieldRange: Constant integer value = 22624 FieldDescription: Record length in bytes. Right justified, blank filled. Value is 4*Integerpart ((Max(148, 64 + 4*n) + 3)/4) where n = Value (Number_Of_32-bit_Words) FieldRepresentation: 5A FieldDisplayFormat: A5 2.21 CCB_Version_Number ----------------------- FieldName: CCB_Version_Number FieldSyntax: ASCII Character*9 String FieldUnits: n/a FieldResolution: n/a FieldRange: Integer >=1, <= 9999 FieldDescription: Version number assigned by the UCSS Configuration Control Board in conjunction with the Principal Investigator to differentiate versions of data. Right justified, blank filled FieldRepresentation: 9A FieldDisplayFormat: A9 2.22 File_Cycle_Number ---------------------- FieldName: File_Cycle_Number FieldSyntax: ASCII Character*5 String FieldUnits: n/a FieldResolution: n/a FieldRange: Integer >=1, <= 31 FieldDescription: File cycle number right justified, blank filled Supplied only during file creation by a Remote Access Computer data transfer, otherwise undefined. The cycle number is incremented if necessary to provide a unique catalog entry at the UARS CDHF. FieldRepresentation: 5A FieldDisplayFormat: A5 2.23 Virtual_File_Flag ---------------------- FieldName: Virtual_File_Flag FieldSyntax: ASCII Character*1 String FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: The Virtual_File_Flag is set to ' ' if a file is a production file containing all the available data for one specific day or 'V' if the file is created by a Remote Access Computer data transfer where a user specified time range is not on day boundaries. FieldRepresentation: 1A FieldDisplayFormat: A1 2.24 Total_Number_Of_Time/Version_Entries_In_File ------------------------------------------------- FieldName: Total_Number_Of_Time/Version_Entries_In_File FieldSyntax: ASCII Character*4 String FieldUnits: n/a FieldResolution: n/a FieldRange: Integer >= 0 FieldDescription: Total number of time/version entries in file. Only used for for virtual files created via RAC data transfer. Right justified, blank filled. FieldRepresentation: 4A FieldDisplayFormat: A4 2.25 Number_Of_Time/Version_Entries_In_Record --------------------------------------------- FieldName: Number_Of_Time/Version_Entries_In_Record FieldSyntax: ASCII Character*4 String FieldUnits: n/a FieldResolution: n/a FieldRange: Integer >= 0 FieldDescription: Number of time/version entries in record. Right justified, blank filled. FieldRepresentation: 4A FieldDisplayFormat: A4 2.26 Version_Entries -------------------- FieldName: Version_Entries FieldSyntax: ASCII Character*28 String 1-D Array (n), where n is value (Number_Of_Time/Version_Entries_In_Record) FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: List of version entries. Each version entry contains: Version_Entries (1:3) start year Version_Entries (4:6) start day of year Version_Entries (7:14) start milliseconds of day Version_Entries (15:24) version number Version_Entries (24:28) cycle number FieldRepresentation: n(28A) FieldDisplayFormat: nA28 Record ====== 3. Continuation_Label_Record ---------------------------- RecordName: Continuation_Label_Record RecordStructure: Variable Length RecordLength: Max (48 + 28 * n, length of Data_Record) where n = Value (Number_of_Time/Version_Entries_in_Record) RecordFieldNames: Satellite_Identifier Record_Type Instrument_Identifier Data_Subtype_Or_Species Format_Version_Number Physical_Record_Count Number_Of_Time/Version_Entries_In_Record Spare Version_Entries RecordSyntax: 9 Fields #1 : Satellite_Identifier #2 : Record_Type #3 : Instrument_Identifier #4 : Data_Subtype_Or_Species #5 : Format_Version_Number #6 : Physical_Record_Count #7 : Number_Of_Time/Version_Entries_In_Record #8 : Spare #9 : Version_Entries Fields ====== 3.1 Satellite_Identifier ------------------------ FieldName: Satellite_Identifier FieldSyntax: ASCII Character*4 String FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: Satellite identifier. Constant value 'UARS' FieldRepresentation: 4A FieldDisplayFormat: A4 3.2 Record_Type --------------- FieldName: Record_Type FieldSyntax: ASCII Character*2 String FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: Record type. Constant value ' 2' for a continuation label record format. FieldRepresentation: 2A FieldDisplayFormat: A2 3.3 Instrument_Identifier ------------------------- FieldName: Instrument_Identifier FieldMnemonic: Data_Type FieldSyntax: ASCII Character*12 String FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: Instrument identifier. Left justified, blank filled. Constant value = 'PEM' FieldRepresentation: 12A FieldDisplayFormat: A12 3.4 Data_Subtype_Or_Species --------------------------- FieldName: Data_Subtype_Or_Species FieldMnemonic: Subtype FieldSyntax: ASCII Character*12 String FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: Data subtype or species. Left justified, blank filled. Constant value = 'MEPS_PROT_ED' FieldRepresentation: 12A FieldDisplayFormat: A12 3.5 Format_Version_Number ------------------------- FieldName: Format_Version_Number FieldSyntax: ASCII Character*4 String FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: Format version number. Constant value ' 1' indicates that this is the first version of the Level 3TP file structure. FieldRepresentation: 4A FieldDisplayFormat: A4 3.6 Physical_Record_Count ------------------------- FieldName: Physical_Record_Count FieldSyntax: ASCII character*8 string FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: Physical record count. Constant value ' 1' indicates the label record is the logical first record in the file. FieldRepresentation: 8A FieldDisplayFormat: A8 3.7 Number_Of_Time/Version_Entries_In_Record -------------------------------------------- FieldName: Number_Of_Time/Version_Entries_In_Record FieldSyntax: ASCII Character*4 String FieldUnits: n/a FieldResolution: n/a FieldRange: Integer >= 0 FieldDescription: Number of time/version entries in record Right justified, blank filled FieldRepresentation: 4A FieldDisplayFormat: A4 3.8 Spare --------- FieldName: Spare FieldSyntax: ASCII Character*2 String FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: Spare. Field contents undefined. FieldRepresentation: 2A FieldDisplayFormat: A2 3.9 Version_Entries ------------------- FieldName: Version_Entries FieldSyntax: ASCII Character*28 String 1-D Array (n), where n is value (Number_Of_Time/Version_Entries_In_Record) FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: List of version entries. Each version entry contains: Version_Entries (1:3) start year Version_Entries (4:6) start day of year Version_Entries (7:14) start milliseconds of day Version_Entries (15:24) version number Version_Entries (24:28) cycle number FieldRepresentation: n(28A) FieldDisplayFormat: nA28 Record ====== 4. Data_Record -------------- RecordName: Data_Record RecordStructure: Variable Length RecordLength: MAX (22624, length of File_Label_Record) RecordFieldNames: Satellite_Identifier Record_Type Instrument_Identifier Physical_Record_Count Spare Maximum_Number_Of_32-bit_Words_In_The_Record Spare Spare Record_Time_In_UDTF_Format Latitude Longitude Spare Number_Of_32-bit_Parameter_Words Parameters RecordSyntax: 14 Fields #1 : Satellite_Identifier #2 : Record_Type #3 : Instrument_Identifier #4 : Physical_Record_Count #5 : Spare #6 : Maximum_Number_Of_32-bit_Words_In_The_Record #7 : Spare #8 : Spare #9 : Record_Time_In_UDTF_Format #10: Latitude #11: Longitude #12: Spare #13: Number_Of_32-bit_Parameter_Words #14: Parameters Fields ====== 4.1 Satellite_Identifier ------------------------ FieldName: Satellite_Identifier FieldSyntax: ASCII Character*4 String FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: Satellite identifier. Constant value 'UARS' FieldRepresentation: 4A FieldDisplayFormat: A4 4.2 Record_Type --------------- FieldName: Record_Type FieldSyntax: ASCII Character*2 String FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: Record type. Constant value ' 3' for the data record format. FieldRepresentation: 2A FieldDisplayFormat: A2 4.3 Instrument_Identifier ------------------------- FieldName: Instrument_Identifier FieldMnemonic: Data_Type FieldSyntax: ASCII Character*12 String FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: Instrument identifier. Left justified, blank filled. Constant value = 'PEM' FieldRepresentation: 12A FieldDisplayFormat: A12 4.4 Physical_Record_Count ------------------------- FieldName: Physical_Record_Count FieldSyntax: ASCII Character*8 String FieldUnits: n/a FieldResolution: n/a FieldRange: Integer >= 2 FieldDescription: Physical record count. Right justified, blank filled. Does not count SFDU label record. FieldRepresentation: 8A FieldDisplayFormat: A8 4.5 Spare --------- FieldName: Spare FieldSyntax: ASCII Character*2 String FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: Spare. Constant value '00' FieldRepresentation: 2A FieldDisplayFormat: A2 4.6 Maximum_Number_Of_32-bit_Words_In_The_Record ------------------------------------------------ FieldName: Maximum_Number_Of_32-bit_Words_In_The_Record FieldMnemonic: Max_Np FieldSyntax: Scalar FieldUnits: n/a FieldResolution: n/a FieldRange: Constant Integer = 5640 FieldDescription: Maximum number of parameters in the data buffer. FieldRepresentation: VI4 FieldDisplayFormat: I4 4.7 Spare --------- FieldName: Spare FieldSyntax: ASCII Character*4 String FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: Spare. Field contents undefined. FieldRepresentation: 4A FieldDisplayFormat: A4 4.8 Spare --------- FieldName: Spare FieldSyntax: ASCII Character*4 String FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: Spare. Field contents undefined. FieldRepresentation: 4A FieldDisplayFormat: A4 4.9 Record_Time_In_UDTF_Format ------------------------------- FieldName: Record_Time_In_UDTF_Format FieldMnemonic: Strt_Dattim FieldSyntax: 1-D Array (2) FieldUnits: 1 millisecond FieldResolution: 1 millisecond FieldRange: n/a FieldDescription: Record time in UDTF format FieldRepresentation: 2VI4 FieldDisplayFormat: I5,I8 4.10 Latitude -------------- FieldName: Latitude FieldMnemonic: REF_LAT FieldSyntax: Scalar FieldUnits: Degrees FieldResolution: n/a FieldRange: Real >= -88.5, <= 88.5 FieldDescription: Geodetic latitude at the UARS reference time. Value provided by the PEM production software which represents the position of a dipole magnetic field line at 100 km which intersects the spacecraft at a time corresponding to the center time of the averaging interval. The position and attitude of UARS are provided by O/A services. FieldRepresentation: VR4 FieldDisplayFormat: F7.3 4.11 Longitude -------------- FieldName: Longitude FieldMnemonic: REF_LONG FieldSyntax: Scalar FieldUnits: Degrees FieldResolution: n/a FieldRange: Real >= 0.0, < 360.0 FieldDescription: Geodetic longitude at the UARS reference time. Value provided by the PEM production software which represents the position of a dipole magnetic field line at 100 km which intersects the spacecraft at a time corresponding to the center time of the averaging interval. The position and attitude of UARS are provided by O/A services. FieldRepresentation: VR4 FieldDisplayFormat: F7.3 4.12 Spare ---------- FieldName: Spare FieldSyntax: ASCII Character*4 String FieldUnits: n/a FieldResolution: n/a FieldRange: n/a FieldDescription: Spare. Field contents undefined. FieldRepresentation: 4A FieldDisplayFormat: A4 4.13 Number_Of_32-bit_Parameter_Words ------------------------------------- FieldName: Number_Of_32-bit_Parameter_Words FieldMnemonic: NP FieldSyntax: Scalar FieldUnits: n/a FieldResolution: n/a FieldRange: Constant Integer = 5640 FieldDescription: Number of actual parameters in the data buffer. FieldRepresentation: VI4 FieldDisplayFormat: I4 4.14 Parameters --------------- FieldName: Parameters FieldSyntax: 1-D Array (n), where n is value (Maximum_Number_Of_32-bit_Words_In_The_Record) FieldUnits: YYDDD, milliseconds for 1/3 time in UDTF format (1-2) Degrees for 1/3 latitude and longitude (3-4) YYDDD, milliseconds for 2/3 time in UDTF format (5-6) Degrees for 2/3 latitude and longitude (7-8) ergs / (cm**3-s) for MEPS energy deposition values (9-2824) ergs / (cm**3-s) for standard deviations (2825-5640) FieldResolution: variable FieldRange: n/a for 1/3 time in UDTF format (1-2) Real >= -88.5, <= 88.5 for 1/3 latitude (3) Real >= 0.0, < 360.0 for 1/3 longitude (4) n/a for 2/3 time in UDTF format (5-6) Real >= -88.5, <= 88.5 for 2/3 latitude (7) Real >= 0.0, < 360.0 for 2/3 longitude (8) 1E-28 to 1E0 for MEPS energy deposition values (9-2824) 1E-28 to 1E0 for standard deviations (2825-5640) FieldDescription: Parameters is a one dimensional array containing the parameters associated with the MEPS Proton energy deposition results. The 5640 parameter values are described as follows: 1-2: 1/3 time refers to the center date/time MINUS one third of an EMAF interval (21845 msec) in UDTF format 3: 1/3 latitude refers to traced latitude at 1/3 time 4: 1/3 longitude refers to traced longitude at 1/3 time 5-6: 2/3 time refers to the center date/time PLUS one third of an EMAF interval (21845 msec) in UDTF format 7: 2/3 latitude refers to traced latitude at 2/3 time 8: 2/3 longitude refers to traced longitude at 2/3 time 9-2824: MEPS energy deposition profiles organized as a 32 x 88 array corresponding to the 32 2-second (2048 msecs) profiles for each of the 88 UARS standard altitudes 2825-5640: Standard deviations organized as a 32 x 88 array in one-to-one correspondence with the energy deposition profile data values FieldRepresentation: 2VI4 for 1/3 time (1-2) VR4 for 1/3 latitude (3) VR4 for 1/3 longitude (4) 2VI4 for 2/3 time (5-6) VR4 for 2/3 latitude (7) VR4 for 2/3 longitude (8) (32x88)VR4 for MEPS energy deposition values (9-2824) (32x88)VR4 for standard deviations (2825-5640) FieldDisplayFormat: I5,I8 for 1/3 time in UDTF format (1-2) F7.3 for 1/3 latitude (3) F7.3 for 1/3 longitude (4) I5,I8 for 2/3 time in UDTF format (5-6) F7.3 for 2/3 latitude (7) F7.3 for 2/3 longitude (8) (32x88)E10.2 for MEPS energy deposition values (9-2824) (32x88)E10.2 for standard deviations (2825-5640)