1.3. Instrument page structure¶
Pages for instruments have a structure containing a selection of these headings. Note that not all headings are present for all instruments. The information for each heading is explained here:
1.3.1. Instrument id¶
The title and page name is the instrument ID code. This is often the model of the instrument (e.g. CL31) but sometimes is less generic (e.g. SWTWXSTATION).
1.3.1.1. Introdction¶
A short paragraph on what the instrument is and any useful information that doesn’t fit into the other categories, listed below.
1.3.1.2. Manufacturer and Model¶
The company that manufactures the instrument and the model and type of the instrument.
1.3.1.3. Output definitions¶
Processed data from instruments is stored in netCDF files. An instrument can have multiple netCDF files for the same time frame due to having multiple output definitions. The output definition defines the name of the output file, the number of levels of data and the time resolution(s) of the output data.
Header |
Explanation |
|---|---|
Output definition ID |
Used to identify the output definition in the “Variables measured by instrument” table. |
File Identifier |
The standard prefix file format to which processed data is saved %SITE and %LETTER are replaced by the instruments’ site and suffix, respectively. |
Level Number |
The code for the processing level of data. Higher levels are processed and quality checked more rigorously. |
QAQC notes |
Quality assurance and quality control notes on this level for this output definition. Notes are non-exhaustive. To see what all each level means in more detail, see the processing code. |
File time resolution |
The time resolution(s) that processed data is outputted to. |
1.3.1.4. Processing code¶
A link to the github repo from which the code used to process data is stored. Most users will not have access to the repos so it will have to be requested from Prof. Sue Grimmond (c.s.grimmond@reading.ac.uk).
1.3.1.5. Variables measured by instrument¶
What the instrument measures. These variables are stored in one or more of the files’ definted in the output definitions table.
Header |
Explanation |
|---|---|
Variable ID |
The id code for the variable. This is the name used in the netCDF file. |
Full Name |
The full name of the variable |
Unit |
Unit of variable. |
Lower threshold |
Lowest value the variable can be once the threshold is applied. The level at which this threshold is applied will be indicated in the “QAQC” notes column of the “Output definitions” table. Values below this threshold are replaced. |
Upper threshold |
Highest value the variable can be once the threshold is applied. The level at which this threshold is applied will be indicated in the “QAQC” notes column of the “Output definitions” table. Values below this threshold are replaced. |
Files present |
In which files the variable is present for this instrument. The output ID, level and time resolution are comma separated. Where the variable is stored within multiple files, these definitions are space separated. |
1.3.1.6. Serials¶
The serial number(s) of the instruments in the mudh database for this model.
Header |
Explanation |
|---|---|
Serial |
Serial number assigned by manufacturer. |
Suffix |
Letter assigned to the instrument with this serial number. This is used to identify the output files for some instruments %LETTER in the “File identifier” (seen in the “Output definitions” table). |
1.3.1.7. Deployments¶
Where and when each individual instrument has been deployed. Note that an instrument can be deployed at the same site twice in a row if the configuration or instrument status changes (see Definitions).
1.3.1.8. Photos¶
Images of the instruments whilst they’re deployed. Most of these have a date attached but where the date is not known, a date range is given.
1.3.1.9. Supplementary information¶
This includes (but is not limited to) instrument manuals. In most cases a download link is given but when this is not permissible a url link is given. If you find an expired url please raise a GitHub Issues. If you are using data for an instrument, please pay close attention to the supplementary info, as it may contain important information on the data.
1.3.1.10. Data acquisition¶
How to get access to data.
1.3.1.11. References¶
These are references, extracted from the Centaur repository. References are automatically harvested based on key words, and some manual additions and omissions are made. However, there is still potential for some references to be missed, or irrelevant references to be included. Please bare this in mind when using this section.
Tip
Stuck? the user guide is a useful place to start.
Please report issues at GitHub Issues. Go from the page with the problem - an automatic link will be inserted. Thanks.