WebHome » MeasurementFile


Last modified by Michael Sibayan on 2014/07/11 12:24

The "Measurement File" or "m-file" is an ASCII text, human readable, tab-delimited file which holds information pertaining to a measurement or group of measurements. In general, a measurement file will hold all data from sensors sampled at a particular time (i.e. - measure a group of five thermocouples at 11:30am on Dec. 1, 2012). However, it is not limited to this, as one could group a single sensor, or even a group of sensors, over an extended period of time.

The measurement file has strict conventions. Measurement files uploaded to the LEO Data Server must follow these guidelines.

Each measurement file must be named using the following convention:

LOCATION-ID is LEO-E,LEO-C,LEO-W with some other information tagged on using only hyphens delete, such as LEO-E-P01 identifies the P01 cRIO within LEO East. It is imperative the first five characters correspond to a database identifier. The LEODataGateway application uses this information to open the appropriate database connection. Opening the incorrect database will result in multiple errors and no data inserted into the database.
 Timestamp is in the format YYYYMMDDhhmmss and is used for archiving purposes. Incorrectly formatted time stamps may result in difficult to find archived data.

Data within a measurement file must be formatted as follows:

The DATETIMESTAMP has the format:
 YYYY-MM-DD hh:mm:ss

SENSORCODE corresponds to the sensor's human readable identifier as used in the database. If this sensor does not exist in the database, an error will occur.
 The current naming convention for sensors is as follows:

LOCATION refers to the biome and/or location within the facility (e.g. LEO-E refers to LEO east bay, DESERT would refer to the Desert Biome).
 The PositionID refers to the position within the location, generally coordinates or some useful identifier. For LEO, I used UpSlope_CrossSlope_Depth (the coordinates in relation to the slope axis) as the position identifier.

SENOSORTYPE is any valid sensor type code defined in the database

An example of the text within a measurement file is shown below:
2012-12-03 11:30:00  LEO-E_24_4_1_HFP-1  0.0045221299
2012-12-03 11:30:00  LEO-E_24_0_1_HFP-1  0.0050794184
2012-12-03 11:30:00  LEO-E_24_-4_1_HFP-1  0.0050061792
2012-12-03 11:30:00  LEO-E_18_0_1_HFP-1  0.0041005462
2012-12-03 11:30:00  LEO-E_24_4_3_GMM222  0.0810752401
2012-12-03 11:30:00  LEO-E_24_4_2_GMM222  0.0915027962
2012-12-03 11:30:00  LEO-E_24_4_1_GMM222  0.1632088861
2012-12-03 11:30:00  LEO-E_24_1_4_GMM222  0.0838307142

Created by Michael Sibayan on 2014/07/11 12:24

This wiki is licensed under a Creative Commons 2.0 license
XWiki Enterprise 6.0.1 - Documentation