CQ WW Trends, 2005 to 2016

The availability of the CQ WW public logs covering the period 2005 to 2016 allows us to look at various trends over that period, in addition to the trends in hourly QSO rates already documented..

We start with the simplest graph, the raw number of entries:

It will be interesting to see next year whether the 2016 points are an aberration (although I caution against reading much into the mere number of logs submitted; still, the reversal between CW and SSB in 2016 is worth at least a mention).

Breaking it down between unassisted and assisted, we see:

Last year I wondered whether the assisted numbers would exceed the unassisted numbers in 2016; they didn't, but it's getting very close (on CW). This, I expect, is a reflection of the utility of the RBN, which can make the assisted category far more attractive, especially for the mass of relatively casual operators whose QSOs come solely from point-and-click QSOs.

We can examine the geographical distribution of entrants over time, first on CW:

Very little change there.

And on SSB:

Nothing much there either, except that the recent small increased percentages from zones 28 and 11appear to be maintained.

We can look at the numbers of QSOs in the logs:

The long-term downward trend in the numbers of QSOs in the assisted logs continues, as does the difference of roughly one hundred QSOs between CW and SSB logs (in favour of CW).

Let's look at how the number of calls in CQ WW logs, which is a reasonable metric for the basic popularity of the contest, has changed over the years.

On CW:

On SSB:

Both modes show that 2016 is more or less identical to 2005, with no obvious underlying growth over the past solar cycle.

It's also of some interest to plot the year-by-year number of distinct QSOs made on each band. By "distinct" I mean that a QSO both sides of which are logged by entrants counts just once.

For CW:

As usual, 40m and 20m support roughly the same number of QSOs, with all bands except 10m and 15m more or less unaffected by the solar cycle.

For SSB:

In 2016, the situation on SSB reverted to its low-sunspot-number configuration.

Over the course of the last cycle, the total number of QSOs in CQ WW CW has increased slightly (but one could hardly conclude that contesting is experiencing any kind of surge in popularity), and on SSB that has been no perceptible overall change in the number of logged QSOs since the last minimum.

And finally, what I think are the most interesting graphs of all, which show a sea change in contesting, at least in CQ WW. They also show a tremendous difference between CW and SSB contesting for the CQ WW contests. (The SSB graphs were presented earlier in the year, but I include them here so that they can be compared easily to the CW graphs.)

Call Busts and Reverse Busts in CQ WW, 2005 to 2014

These tables show the stations with the most busts and reverse busts in CQ WW (both CW and SSB) over the period from 2005 to 2014. These tables are based on the augmented versions of the CQ WW public logs.

2005 to 2014 SSB -- Most Busts
Position	Call	QSOs	Busts	% Busts
1	OT5A	96,307	1,257	1.3
2	LZ9W	98,852	1,012	1.0
3	PJ2T	113,858	1,008	0.9
4	LY7A	79,383	908	1.1
5	HG1S	60,709	897	1.5
6	A73A	59,234	821	1.4
7	CN3A	97,786	811	0.8
8	JA7YRR	44,706	790	1.8
9	V26B	94,989	681	0.7
10	ZW5B	44,322	680	1.5

2005 to 2014 SSB -- Most Reverse Busts
Position	Call	QSOs	Reverse Busts	% Reverse Busts
1	OH5BM	12,334	1,979	16.0
2	DF0HQ	105,347	1,940	1.8
3	JA3YBK	60,630	1,200	2.0
4	WE3C	55,590	1,017	1.8
5	S52ZW	47,810	988	2.1
6	K3LR	107,460	953	0.9
7	GM2T	48,518	937	1.9
8	HG1S	60,709	887	1.5
9	HB0/HB9AON	45,504	713	1.6
10	JA5FDJ	32,761	710	2.2

2005 to 2014 SSB -- Highest Percentage of Busts (≥500 QSOs)
Position	Call	QSOs	% Busts
1	PV8ADI	682	11.9
2	K2JMY	1,464	11.7
3	OH1FJ	523	10.9
4	EA1BGV	617	9.7
5	YO7LYM	644	9.0
6	K8TS	855	8.7
7	HA6VA	501	8.6
8	W0PPF	574	8.4
9	SQ6POM	572	7.9
10	PU2TRX	839	7.7

2005 to 2014 SSB -- Highest Percentage of Reverse Busts (≥500 QSOs)
Position	Call	QSOs	% Reverse Busts
1	ON46CQ	566	81.8
2	TA2YA	508	26.8
3	CW90A	1,815	23.4
4	TA2IK	558	16.8
5	OH5BM	12,334	16.0
6	KH6SP/W5	532	13.0
7	BA8AG	1,011	12.2
8	YB6DE	547	10.2
9	HE70FG	1,597	9.1
10	S580A	1,087	8.6

In tables of reverse busts, one sometimes finds what seems like an unreasonable number of reverse busts (as, in this table, for ON46CQ). This is generally caused by a discrepancy between the call actually sent by the listed station and the one recorded as being sent in at least some QSOs in the station's log.

2005 to 2014 CW -- Most Busts
Position	Call	QSOs	Busts	% Busts
1	PJ2T	119,899	1,120	0.9
2	HG1S	48,531	892	1.8
3	LZ9W	107,790	877	0.8
4	PV8ADI	7,307	798	10.9
5	LY7A	77,281	795	1.0
6	OZ5E	37,392	717	1.9
7	D4C	88,441	710	0.8
8	PJ4A	94,041	686	0.7
9	LX7I	80,477	685	0.9
10	PI4CC	37,652	670	1.8

2005 to 2014 CW -- Most Reverse Busts
Position	Call	QSOs	Reverse Busts	% Reverse Busts
1	DF0HQ	98,064	2,493	2.5
2	JS3CTQ	20,906	2,093	10.0
3	DR1A	88,958	1,692	1.9
4	IR4X	63,809	1,553	2.4
5	K3LR	93,561	1,269	1.4
6	W0AIH	37,400	1,257	3.4
7	V26K	61,068	1,174	1.9
8	W2FU	66,345	1,159	1.7
9	EE2W	27,427	1,027	3.7
10	4O3A	56,331	980	1.7

2005 to 2014 CW -- Highest Percentage of Busts (≥500 QSOs)
Position	Call	QSOs	% Busts
1	YO7LYM	962	18.9
2	EA2GC	507	18.1
3	AD4TR	738	17.2
4	EA2NA	906	16.0
5	AE3D	698	15.8
6	WF5W	762	15.7
7	OH2MO	554	15.5
8	JA3AHY	597	15.4
9	BD3MV	1,029	15.1
10	EA3AJP	542	14.4

2005 to 2014 CW -- Highest Percentage of Reverse Busts (≥500 QSOs)
Position	Call	QSOs	% Reverse Busts
1	G3RWF	1,103	85.4
2	HA8FW	1,256	71.7
3	RZ3VO	2,025	44.2
4	BG0AAI	586	33.6
5	OG55W	1,005	31.9
6	HA505BA	660	20.8
7	5K0A	2,882	20.6
8	YO7HHI	1,104	18.0
9	SB0A	1,215	14.1
10	YP0HQ	2,223	11.2

Further Rationalisation of the LANL GPS Charged-Particle Dataset

Earlier posts in this series:

• Original data
• Stages 1 to 4
• Revised stages 1 to 5  
• Stages 6 to 10

We continue to rationalise the data by removing fields that are unused or provide no useful information, and marking invalid values.

Stage 11: remove double precision values that are out of range

In the discussion for stage 9, I briefly mentioned values that are less than the maximum subnormal double precision number representable in accordance with the current (2008) IEEE 754 standard. It turns out that such numbers appear throughout the dataset, so it is useful to replace them with a more explicit indication that data should be ignored. We can do this using the string "NA" to replace all such numbers.

To be more precise, we generate stage 11 by running the following code on the stage 10 files:

#!/usr/bin/env python
# -*- coding: utf8 -*-

# replace all fields that contain "e-31[0123456789]" with "NA"

import re
import sys

filename = sys.argv[1]

with open(filename) as records:
  for line in records:
    fields = line.split()
   
    for i in xrange(len(fields)):

      m = re.search('e-31[0123456789]', fields[i])
      if m:
        fields[i] = "NA"
   
    newline = " ".join(fields)
   
    print newline

I note that although the maximum subnormal double precision number exceeds e-310, no occurrences of such numbers appear in the dataset; hence the use above of the search term "e-31[0123456789]".

Stage 12: correct values of proton_activity

The documentation for the proton_activity field states only: 
  =1 if there is significant proton activity 

Some expansion is in order. In private communication with the authors of the dataset, I have learned that the definition of significant in the above is:
  For NS41 and NS48 (i.e., the Burst Detector-Dosimeter (BDD) instrument): the P1 rate is greater than 10 events per second, and the L shell is greater than 24.99;
  For the other satellites (i.e., the Combined X-ray/Dosimeter (CXD) instrument): the P1 rate is greater than 5 events per second.

Although the documentation does not describe the meaning of values other than one, the dataset authors inform me that the intention is that the value zero implies no significant proton activity, and any non-zero value should be treated as if it were unity.

Consequently, it is useful to replace all values other than zero and one for the proton_activity field with the value one.

It turns out that only ns41 has invalid values of proton_activity; these can be replaced by:

awk '$49!="0" && $49!="1" {$49="1"}; {print $0};'  ns41 > ../gps-stage-12/ns41

The equivalent command for the CXD instrument, although it is unnecessary with this dataset, is:

awk '$55!="0" && $55!="1" {$55="1"}; {print $0};'  ns<nn> > ../gps-stage-12/ns<nn>

Stage 13: Mark bad values associated with L = 0

The ns41 and ns48 satellites have one field that is associated with the L shell (called, reasonably enough, L_shell). Some records have a value of zero for this field, which is obviously not a legitimate value. Such records appear to have illegal values for other fields associated with the magnetic field: b_coord_radius, b_coord_height, magnetic_longitude, bfield_ratio, b_sattelite (sic) and b_equator. Consequently, for these two satellites, if L_shell is zero, all these fields, and L_shell itself, should be set to "NA":

awk '$28=="0.000000e+00" {$25=$26=$27=$28=$29=$31=$32="NA"}; {print $0}' ns<nn> > ../gps-stage-13/ns<nn>

The L_shell field associated with most of the other satellites seems never to be set to zero; however, for ns59, ns60 and ns61, there are records that have many values, including L_shell, filled with zeroes. In these records, it seems that all values after the SVN_number field are set to zero. The records are not completely useless, though, since the data up to and including the SVN_number field appear reasonable. Hence for these spacecraft, all fields after number 25 (which corresponds to SVN_number) should be set to "NA":

awk '$29=="0.000000e+00" {for(i=26;i<=NF;++i)$i="NA"}; {print $0}' ns<nn> > ../gps-stage-13/ns<nn>

Stage 14: Remove redundant field L_LGM_T891GRF

On satellites ns53 to ns73 (i.e., the CXD instrument), the documentation for the L_shell field states: currently this is the same as L_LGM_T89IGRF. Thus, the field L_LGM_T89IGRF is redundant and can be removed without loss of information.

At stage 13, the data table for the CXD satellites looks like this:

Column	Variable name	type	Dim.	description
1	decimal_day	double	1	GPS time, a number from 1 (1-Jan 00:00) to 366 (31-Dec 24:00) or 367 in leap years.
2	Geographic_Latitude	double	1	Latitude of satellite (deg)
3	Geographic_Longitude	double	1	Longitude of satellite (deg)
4	Rad_Re	double	1	(radius of satellite)/Rearth
5-15	rate_electron_measured	double	11	Measured rate (Hz) in each of the 11 CXD electron channels
16-20	rate_proton_measured	double	5	Measured rate (Hz) in each of the 5 CXD proton channels (P1-P5)
21	LEP_thresh	double	1	LEP threshold in E1 channels (0 means low, 1 means high)
22	collection_interval	int	1	dosimeter collection period (seconds)
23	year	int	1	year (e.g. 2015)
24	decimal_year	double	1	decimal year = year + (decimal_day-1.0)/(days in year)
25	SVN_number	int	1	SVN number of satellite
26	b_coord_radius	double	1	radius from earth's dipole axis (earth radii)
27	b_coord_height	double	1	height above the earth's dipole equatorial plane (earth radii)
28	magnetic_longitude	double	1	Magnetic longitude (degrees)
29	L_shell	double	1	L_shell (earth radii) – currently this is the same as L_LGM_T89IGRF but this is intended to be our suggested choice for the L shell calculation in the long run.
30	L_LGM_TS04IGRF	double	1	LanlGeoMag L-shell McIlwain calculation, TS04 External Field, IGRF Internal Field.
31	L_LGM_OP77IGRF	double	1	LanlGeoMag L-shell McIlwain calculation, OP77 External Field, IGRF Internal Field (not currently filled)
32	L_LGM_T89CDIP	double	1	LanlGeoMag L-shell McIlwain calculation, T89 External Field, Centered Dipole Internal Field
33	L_LGM_T89IGRF	double	1	LanlGeoMag L-shell McIlwain calculation, T89 External Field, IGRF Internal Field
34	bfield_ratio	double	1	Bsatellite/Bequator
35	local_time	double	1	magnetic local time (0-24 hours)
36	utc_lgm	double	1	UTC (0-24 hours)
37	b_sattelite	double	1	B field at satellite (gauss)
38	b_equator	double	1	B field at equator (on this field line I think) (gauss)
39-49	electron_background	double	11	estimated background in electron channels E1-E11 (Hz)
50-54	proton_background	double	5	estimated background in proton channels P1-P5 (Hz)
55	proton_activity	int	1	=1 if there is significant proton activity
56	proton_temperature_fit	double	1	characteristic momentum -- R0 in the expression given above (MeV/c)
57	proton_density_fit	double	1	N0 parameter in fit to proton flux ((protons/(cm2 sec sr MeV))
58	electron_temperature_fit	double	1	electron temperature from a one Maxwellian fit (MeV)
59	electron_density_fit	double	1	electron number density from a one Maxwellian fit (cm-3)
60-70	model_counts_electron_fit_pf	double	11	E1-E11 rates due to proton background based on proton flux fit -- currently not filled (all -1's)
71-75	model_counts_proton_fit_pf	double	5	P1-P5 rate from proton fit (using proton_temperature_fit, proton_density_fit)
76-86	model_counts_electron_fit	double	11	E1-E11 rates from the 9-parameter electron flux model
87-91	model_counts_proton_fit	double	5	P1-P5 rates from electron background -- currently not filled (all -1's)
92-97	proton_integrated_flux_fit	double	6	integral of proton flux (based on fit) above 10, 15.85, 25.11, 30, 40, 79.43 MeV (proton kinetic energy)
98-128	proton_flux_fit	double	31	intended to be proton flux at 31 energies, not filled currently
129-134	proton_fluence_fit	double	6	not filled currently
135-164	integral_flux_instrument	double	30	(based on 9 parameter fit) integral of electron flux above integral_flux_energy[i] particles/(cm2 sec)
165-194	integral_flux_energy	double	30	energies for the integral of integral_flux_instrument (MeV)
195-209	electron_diff_flux_energy	double	15	energies for the fluxes in electron_diff_flux_energy (MeV)
210-224	electron_diff_flux	double	15	(based on 9 parameter fit) electron flux at energies electron_diff_flux[i] (particle/(cm2 sr MeV sec))
225-233	Efitpars	double	9	fit parameters for 9 parameter electron fit

So we remove L_LGM_T89IGRF:

awk '{$33=""; print $0}' ns<nn> | tr -s " " > ../gps-stage-14/ns<nn>

Leaving us with the following data table (NB: I have edited the description so as to preserve the derivation information for the L_shell field):

Column	Variable name	type	Dim.	description
1	decimal_day	double	1	GPS time, a number from 1 (1-Jan 00:00) to 366 (31-Dec 24:00) or 367 in leap years.
2	Geographic_Latitude	double	1	Latitude of satellite (deg)
3	Geographic_Longitude	double	1	Longitude of satellite (deg)
4	Rad_Re	double	1	(radius of satellite)/Rearth
5-15	rate_electron_measured	double	11	Measured rate (Hz) in each of the 11 CXD electron channels
16-20	rate_proton_measured	double	5	Measured rate (Hz) in each of the 5 CXD proton channels (P1-P5)
21	LEP_thresh	double	1	LEP threshold in E1 channels (0 means low, 1 means high)
22	collection_interval	int	1	dosimeter collection period (seconds)
23	year	int	1	year (e.g. 2015)
24	decimal_year	double	1	decimal year = year + (decimal_day-1.0)/(days in year)
25	SVN_number	int	1	SVN number of satellite
26	b_coord_radius	double	1	radius from earth's dipole axis (earth radii)
27	b_coord_height	double	1	height above the earth's dipole equatorial plane (earth radii)
28	magnetic_longitude	double	1	Magnetic longitude (degrees)
29	L_shell	double	1	L shell: McIlwain calculation according to model with T89 External Field, IGRF Internal Field.
30	L_LGM_TS04IGRF	double	1	LanlGeoMag L-shell McIlwain calculation, TS04 External Field, IGRF Internal Field.
31	L_LGM_OP77IGRF	double	1	LanlGeoMag L-shell McIlwain calculation, OP77 External Field, IGRF Internal Field (not currently filled)
32	L_LGM_T89CDIP	double	1	LanlGeoMag L-shell McIlwain calculation, T89 External Field, Centered Dipole Internal Field
33	bfield_ratio	double	1	Bsatellite/Bequator
34	local_time	double	1	magnetic local time (0-24 hours)
35	utc_lgm	double	1	UTC (0-24 hours)
36	b_sattelite	double	1	B field at satellite (gauss)
37	b_equator	double	1	B field at equator (on this field line I think) (gauss)
38-48	electron_background	double	11	estimated background in electron channels E1-E11 (Hz)
49-53	proton_background	double	5	estimated background in proton channels P1-P5 (Hz)
54	proton_activity	int	1	=1 if there is significant proton activity
55	proton_temperature_fit	double	1	characteristic momentum -- R0 in the expression given above (MeV/c)
56	proton_density_fit	double	1	N0 parameter in fit to proton flux ((protons/(cm2 sec sr MeV))
57	electron_temperature_fit	double	1	electron temperature from a one Maxwellian fit (MeV)
58	electron_density_fit	double	1	electron number density from a one Maxwellian fit (cm-3)
59-69	model_counts_electron_fit_pf	double	11	E1-E11 rates due to proton background based on proton flux fit -- currently not filled (all -1's)
70-74	model_counts_proton_fit_pf	double	5	P1-P5 rate from proton fit (using proton_temperature_fit, proton_density_fit)
75-85	model_counts_electron_fit	double	11	E1-E11 rates from the 9-parameter electron flux model
86-90	model_counts_proton_fit	double	5	P1-P5 rates from electron background -- currently not filled (all -1's)
91-96	proton_integrated_flux_fit	double	6	integral of proton flux (based on fit) above 10, 15.85, 25.11, 30, 40, 79.43 MeV (proton kinetic energy)
97-127	proton_flux_fit	double	31	intended to be proton flux at 31 energies, not filled currently
128-133	proton_fluence_fit	double	6	not filled currently
134-163	integral_flux_instrument	double	30	(based on 9 parameter fit) integral of electron flux above integral_flux_energy[i] particles/(cm2 sec)
164-193	integral_flux_energy	double	30	energies for the integral of integral_flux_instrument (MeV)
194-208	electron_diff_flux_energy	double	15	energies for the fluxes in electron_diff_flux_energy (MeV)
209-223	electron_diff_flux	double	15	(based on 9 parameter fit) electron flux at energies electron_diff_flux[i] (particle/(cm2 sr MeV sec))
224-232	Efitpars	double	9	fit parameters for 9 parameter electron fit

 Stage 15: Remove proton_fluence_fit

The documentation for the CXD field proton_fluence_fit says simply:

128-133

proton_fluence_fit

double

6

not filled currently

I note that at least some records appear to have plausible data in these fields, but I take the documentation at its word -- after all, these data constitute an official release from LANL, and are provided by NOAA; although it is manifest that the data were not completely corrected before release, users must be able to trust the documentation. Further, and more pragmatically, to second-guess the documentation would render the task of trying to establish a ready-to-process version of the data almost endless.

So we remove the fields corresponding to the proton_fluence_fit variable:

awk '{$128=$129=$130=$131=$132=$133=""; print $0}' ns<nn> | tr -s " " > ../gps-stage-15/ns<nn>

Note that there is no proton_fluence_fit field for the BBD instrument, so we make no changes to the files for ns41 and ns48.

At this point, we checkpoint the data again. The checkpointed data file has the MD5 checksum 06ddd2268edb93c2c040d604a4b9fa7a.

The data table for ns41 and ns48 is unchanged from the last checkpoint (at stage 10):

Column	Variable name	type	Dim.	Description
1	decimal_day	double	1	GPS time -- a number from 1 (1-Jan 00:00) to 366 (31-Dec 24:00) or 367 in leap years
2	Geographic_Latitude	double	1	Latitude of satellite (deg)
3	Geographic_Longitude	double	1	Longitude of satellite (deg)
4	Rad_Re	double	1	(radius of satellite)/Rearth
5-12	rate_electron_measured	double	8	Measured rate (Hz) in each of the 8 BDD electron channels (E1-E8)
13-20	rate_proton_measured	double	8	Measured rate (Hz) in each of the 8 BDD proton channels (P1-P8)
21	collection_interval	int	1	dosimeter collection period (seconds)
22	year	int	1	year (e.g. 2015)
23	decimal_year	double	1	decimal year = year + (decimal_day-1.0)/(days in year)
24	svn_number	int	1	SVN number of satellite
25	b_coord_radius	double	1	radius from earth's dipole axis (earth radii)
26	b_coord_height	double	1	height above the earth's dipole equatorial plane (earth radii)
27	magnetic_longitude	double	1	Magnetic longitude (degrees)
28	L_shell	double	1	L_shell (earth radii) -- I do not clearly understand the origin of the calculation, but it seems to be a dipole field/T-89
29	bfield_ratio	double	1	Bsatellite/Bequator
30	local_time	double	1	magnetic local time (0-24 hours)
31	b_sattelite	double	1	B field at satellite (gauss)
32	b_equator	double	1	B field at equator (on this field line I think) (gauss)
33-40	electron_background	double	8	estimated background in electron channels E1-E8 (Hz)
41-48	proton_background	double	8	estimated background in proton channels P1-P8 (Hz)
49	proton_activity	int	1	=1 if there is significant proton activity
50	electron_temperature	double	1	electron temperature from a one Maxwellian fit (MeV)
51	electron_density_fit	double	1	electron number density from a one Maxwellian fit (cm-3)
52-59	model_counts_electron_fit	double	8	E1-E8 rates from the 2-parameter Maxwellian fit to the electron data
60-67	dtc_counts_electron	double	8	Dead time corrected electron rates (from data, not fit)
68-97	integral_flux_instrument	double	30	(based on 2 parameter Maxwellian fit) integral of electron flux above integral_flux_energy[i] particles/(cm2sec)
98-127	integral_flux_energy	double	30	energies for the integral of integral_flux_instrument (MeV)
128-142	electron_diff_flux_energy	double	15	energies for the fluxes in electron_diff_flux_energy (MeV)
143-157	electron_diff_flux	double	15	(based on 2 parameter Maxwellian fit) electron flux at energies electron_diff_flux[i] (particle/(cm2 sr MeV sec))

The data table for ns53 to ns73 now looks like this:

Column	Variable name	type	Dim.	description
1	decimal_day	double	1	GPS time, a number from 1 (1-Jan 00:00) to 366 (31-Dec 24:00) or 367 in leap years.
2	Geographic_Latitude	double	1	Latitude of satellite (deg)
3	Geographic_Longitude	double	1	Longitude of satellite (deg)
4	Rad_Re	double	1	(radius of satellite)/Rearth
5-15	rate_electron_measured	double	11	Measured rate (Hz) in each of the 11 CXD electron channels
16-20	rate_proton_measured	double	5	Measured rate (Hz) in each of the 5 CXD proton channels (P1-P5)
21	LEP_thresh	double	1	LEP threshold in E1 channels (0 means low, 1 means high)
22	collection_interval	int	1	dosimeter collection period (seconds)
23	year	int	1	year (e.g. 2015)
24	decimal_year	double	1	decimal year = year + (decimal_day-1.0)/(days in year)
25	SVN_number	int	1	SVN number of satellite
26	b_coord_radius	double	1	radius from earth's dipole axis (earth radii)
27	b_coord_height	double	1	height above the earth's dipole equatorial plane (earth radii)
28	magnetic_longitude	double	1	Magnetic longitude (degrees)
29	L_shell	double	1	L shell: McIlwain calculation according to model with T89 External Field, IGRF Internal Field.
30	L_LGM_TS04IGRF	double	1	LanlGeoMag L-shell McIlwain calculation, TS04 External Field, IGRF Internal Field.
31	L_LGM_OP77IGRF	double	1	LanlGeoMag L-shell McIlwain calculation, OP77 External Field, IGRF Internal Field (not currently filled)
32	L_LGM_T89CDIP	double	1	LanlGeoMag L-shell McIlwain calculation, T89 External Field, Centered Dipole Internal Field
33	bfield_ratio	double	1	Bsatellite/Bequator
34	local_time	double	1	magnetic local time (0-24 hours)
35	utc_lgm	double	1	UTC (0-24 hours)
36	b_sattelite	double	1	B field at satellite (gauss)
37	b_equator	double	1	B field at equator (on this field line I think) (gauss)
38-48	electron_background	double	11	estimated background in electron channels E1-E11 (Hz)
49-53	proton_background	double	5	estimated background in proton channels P1-P5 (Hz)
54	proton_activity	int	1	=1 if there is significant proton activity
55	proton_temperature_fit	double	1	characteristic momentum -- R0 in the expression given above (MeV/c)
56	proton_density_fit	double	1	N0 parameter in fit to proton flux ((protons/(cm2 sec sr MeV))
57	electron_temperature_fit	double	1	electron temperature from a one Maxwellian fit (MeV)
58	electron_density_fit	double	1	electron number density from a one Maxwellian fit (cm-3)
59-69	model_counts_electron_fit_pf	double	11	E1-E11 rates due to proton background based on proton flux fit -- currently not filled (all -1's)
70-74	model_counts_proton_fit_pf	double	5	P1-P5 rate from proton fit (using proton_temperature_fit, proton_density_fit)
75-85	model_counts_electron_fit	double	11	E1-E11 rates from the 9-parameter electron flux model
86-90	model_counts_proton_fit	double	5	P1-P5 rates from electron background -- currently not filled (all -1's)
91-96	proton_integrated_flux_fit	double	6	integral of proton flux (based on fit) above 10, 15.85, 25.11, 30, 40, 79.43 MeV (proton kinetic energy)
97-127	proton_flux_fit	double	31	intended to be proton flux at 31 energies, not filled currently
128-157	integral_flux_instrument	double	30	(based on 9 parameter fit) integral of electron flux above integral_flux_energy[i] particles/(cm2 sec)
158-187	integral_flux_energy	double	30	energies for the integral of integral_flux_instrument (MeV)
188-202	electron_diff_flux_energy	double	15	energies for the fluxes in electron_diff_flux_energy (MeV)
203-217	electron_diff_flux	double	15	(based on 9 parameter fit) electron flux at energies electron_diff_flux[i] (particle/(cm2 sr MeV sec))
218-226	Efitpars	double	9	fit parameters for 9 parameter electron fit