Data Files

Products Characterization Schedules Software Raw Data

NEUBrew Data Products

UV Product Files

UV data products having ascending levels of quality control (QC) applied to the data. As new improved QC algorithms are designed and implemented, new data files will be produced using the following file naming conventions:

yyyyDDDssssssBBBpp.SCR

yyyy Four-Digit Year 2000-2010
DDD Three-Digit day of year 001-366
ssssss Six-Character Station ID Code. First four characters denote abbreviation for a location. Last two characters denote a state code. TMTFCO represents Table Mountain Test Facility, CO.
BBB Three-digit serial number of a Brewer Instrument. Example: 101-154
pp Two-character code identifying the product. Examples: UV or UX
SCR Three-Digit code identifying the quality control level applied to the data:
S - Level of QC applied to the Signal or counts from the Spectrometer.
C - Level of Cosine correction applied to the data.
R - Level of Responsivity applied to the data.

For instance: SCR=000 would denote file of raw data; SCR=111 would denote file where counts were corrected, cosine was corrected and responsivity was applied. SCR=212 would denote data with better count corrections and better responsivity estimate than SCR=111.

SCR Description
100 Dark Counts and PMT Dead Time corrections applied to data.
101 UV Irradiance obtained from the most recent CUCF responsivity.
201 Applies stray light correction and spike correction.
211 Basic cosine correction.
312 Irradiance obtained using Langley Regressions from Direct to Diffuse Irradiance Ratios.

Ozone Daily Average Product Files

Ozone data products having ascending levels of quality control (QC) applied to the data. As new improved QC algorithms are designed and implemented, new data files will be produced using the following file naming conventions:

yyyyssssss_o3.vvv

yyyy Four-Digit Year 2000-2020
ssssss Six-Character Station ID Code. First four characters denote abbreviation for a location. Last two characters denote a state code. TMTFCO represents Table Mountain Test Facility, CO.
_o3 Character code identifying the product as Ozone
vvv QC Version code identifying the quality control level applied to the data:
  • Level 100 - Ozone values produced by the Brewer's internal algorithms and processing
  • Level 200 - Ozone values produced by external processing. Corrected for changes in the Extra-Terrestrial Constant (ETC) using a Delta-R6 technique to modify B1 values in the ozone calculation.
  • Level 300 - Ozone values produced by external processing. Corrected using a Langley derived ETC bias applied in addition to the Delta R6 correction.

Characterization

Brewer characterization files include;

  • CUCF Lamp Calibration Data - data files and images about the precision lamps used to calibrate the NEUBrew Network Instruments for UV.
  • CI Reference Scan Data - file containing the baseline reference CI Scan. These data are used to generate ratio plots of the Brewer's internal Halogen Quarts reference lamp
  • Brewer Calibration Responsivity Data - data files containing the responsivity from all the UV calibrations that have been performed on the NEUBrew Network instruments.


Brewer Automatic Operation Schedules

To achieve autonomous operation Brewers require an operation schedule. The schedules consist of a solar elevation angle followed by a string of one or more two-character subroutine commands on a single line. Numbers between 2 and 99 can be appended to the end of a command string to cause the command string to be repeated n-times (or until the next solar zenith angle is reached.) There are two forms of the schedule A and B. Examples of the A and B schedules are shown below:


SCHEDULE A SCHEDULE B
 
-115.0 
jdb2w1cib0 
-105.0 
pfpdo3b1hgb0rssldtsln2slb0 
-94.0 
pfpdn2zszszszszs 
-92.40 
pfpdo3b1hgb0kaum 
-90.0 
pfpdo3kaum 
-85.0 
pfpdo3uxkeum30 
-80.0 
pfpdo3kcumuxdskdumuxkcum30 
-70.0 
pfpdo3b1uxhguxpsdszsuxpsdszsuxpsdszsuxapn2dszs30 
70.0 
pfpdo3kdumo3uxdskdumux30 
80.0 
pfpdo3keumo3ux30 
85.0 
pfpdo3kaum 
91.0 
pfpdn2zszszszszs 
94.0 
pfpdo3b1hgb0rssln2slb0 
105.0 
pfo3 
180.0 
07150A2				 
				
-115.0
jdb2w1cib0sr
-105.0
pfpdo3b1hgb0rssldtsln2slb0
-94.0
pfpdn2zszszszszs
-92.40
pfpdo3b1hgb0kaum
-90.0
pfpdo3kaum
-85.0
pfpdo3uxkeum30
-80.0
pfpdo3kcumuxdskdumuxkcum30
-70.0
pfpdo3b1uxhguxpsdszsuxpsdszsuxpsdszsuxn2dszsap30 
70.0
pfpdo3kdumo3uxdskdumux30
80.0
pfpdo3keumo3ux30
85.0
pfpdo3kaum
91.0
pfpdn2zszszszszs
94.0
pfpdo3b1hgb0rssln2slb0
105.0
pfo3
180.0
07150A1				
				

Form A of the schedule runs four consecutive days, then B is run for one day, the succession then starts over as show in the Figure below:

Brewer Schedule Succession

The naming convention for schedule files is yydddFs:
where: yy = two-digit year, ddd=three-digit day of year, F=form A or B, s=sequence number 1-5.
yyyddd = the date timestamp the schedule was created.


NEUBrew Brewer Software

The Brewer software and sub-routines used by the NEUBrew Network instruments is based on the baseline version 3.75f software provided by International Ozone Services IOS. Several of the sub-routines have been modified to suit NEUBrew mission goals. New routines have been added to allow more flexibility to the Umkehr sub-routine. UV and CI routines have been modified to allow the NEUBrew version of the Brewer software to run on Linux platforms and Windows XP. All the source code for the NEUBrew software, modified routines, and newly added routines can be found on our FTP server (click on the link above).


Brewer Raw Data Files

Brewer raw data files are provided as produced by the Brewer instrument and its internal processing. No quality control are applied to these data. Raw data are intended for diagnostic purposes only.