1.1.make.import.data: making and importing data

In pems: tools for the analysis and visualisation of pems data

Description

Various pems.utils functions to make and import data as pems objects.

Usage

#making pems objects
 
isPEMS(x, full.test = TRUE, ...)

makePEMS(x, units = NULL, constants = NULL, history = NULL,  
          ...)

#importing data as pems objects

#general

import2PEMS(file.name = file.choose(), time.stamp = NULL, local.time = NULL,
          time.format = NULL, units = NULL, constants = NULL, history = NULL, 
          ..., file.type = NULL, file.reader = read.delim)

importTAB2PEMS(..., file.reader = read.delim)

importCSV2PEMS(..., file.reader = read.csv)


#Horiba OBS

importOBS2PEMS(file.name = file.choose(), pems = "Horiba OBS", 
          constants = NULL, history = NULL, 
          analytes = c("co", "co2", "nox", "hc"),  
          fuel = c("petrol", "diesel", "gasoline"), ...)

#RoyalTek GPS

importRoyalTek2PEMS(file.name = file.choose(), 
          file.type = c("special", "txt", "nmea"),
          vbox = "RoyalTEk", history = NULL, constants = NULL, ...) 

Arguments

x	(A required object) For isPEMS, any object to be tested as a pems object. For makePEMS, an object to be used as the starting point to make a pems objects, so typically a data.frame or another pems object.
full.test	(Logical) For isPEMS, should the full pems test be applied and the pems structure confirmed?
...	(Optional) Other arguments, handling varies. For isPEMS these are ignored. For makePEMS these are added to the pems object unmodified. For import... functions, these are passed on and added to the constants component of the pems object. Note: This different handling is experiment and may be subject to change in future.
units, constants, history	(Default pems arguments) These are arguments that are routinely included generated for pems objects. units holds unit ids for unit management, constants holds constants that should used specifically with data in the pems object, and history holds the pems object modification history.
file.name	(file connection, etc.) For import... functions, the file/source to be imported. Note: the default, file.name = file.choose(), automatically opens a file browser if this argument is not supplied.
time.stamp, local.time, time.format	Relatively crude import... functions are useful for importing data from the clipboard or simple file types. However, these sometimes need careful handling of time data. If supplied, time.stamp and local.time are used as indices or ids (column numbers or names) for data series that the user would like to use as the data time stamp and local time records, respectively. If supplied, time.format sets the format in which the time.stamp should be imported if present/idenified.
file.type, file.reader	Data reader parameters for some import... functions. file.type is the type of file to be imported. Note: Some import... functions can handle more than one file type, and file.type = "[option]" should be used to identify these. (Note: file.type options are typically file type identifiers, such as the file extensions, and a default 'special', which leaves the choice to the function. This way this option can typically be ignored unless, e.g. the function does not recognise the file type but the user knows it and wants to force the method.) file.reader identifies the R method/function that should be used to read data from the supplied file. For example, for importTAB2PEMS and importCSV2PEMS, by default, these are the standard R read... functions read.delim and read.csv, respectively.
pems, vbox	(Character vectors) For some import... functions, data source descriptions may be automatically added to the pems object. pems and vbox are two examples, but others, such as vehicle and fuel descritpions can also be added in a similar fashion. Note: These are for user-reference, so can say whatever you want.
analytes	(Character vector) For import... functions, the names of any pems elements to be tagged as analyte concentrations. Note: If the PEMS unit reports concentrations rather than emissions it is often useful to identify these at import to avoid confusion, and to simplify later handling. So, if encountered, analyte names are prefixed with the term 'conc.'.
fuel	Some import... functions that handle exhaust monitoring system data may assume fuel types when calibrating inputs or calculating constants. In such cases the fuel argument is also included to identify which fuel was used.

Details

isPEMS tests if an object is/is not a pems object.

makePEMS makes a pems object using supplied data and information.

Crude import... functions import simple file structures, and are useful for getting data quickly into R:pems.utils. importTAB2PEMS imports tab delimited files and clipboard content. importCSV2PEMS imports comma delimited files. Both assume a simple file structure (i.e. data series in columns with names as headers), by require some time data management by the user. Note: These are wrappers for import2PEMS.

Other import... import specific file types.

importOBS2PEMS imports standard Horiba OBS files and converts them to pems objects. See Notes below.

importRoyalTek2PEMS imports .txt and .nmea format Royal Tek GPS files and converts them to pems objects. See Notes below.

Value

isPEMS return a logical, TRUE if the supplied object is pems class, otherwise FALSE. If the argument full.test = TRUE is also supplied, additional information about the object is returned as comment(output).

makePEMS returns a pems object, made using the supplied data and any additional information also supplied in the same call.

import... functions return a pems object, made using the supplied file and any additional information also supplied in the same call.

Warning

Currently, makePEMS and import... functions handle extra arguments differently. (See Arguments above for details.) This may be subject to change.

Note

With the crude import... functions (import2PEMS, importTAB2PEMS, importCSV2PEMS) modifications are minimal. Unless any additional changes are requested in the import...(...) call, the data is simply read in as a data.frame and converted to a pems object.

With importOBS2PEMS, OBS data is also modified as follows: data series names are simplified and converted to lower case to simplify use in R; the data series time.stamp and local.time are added (generated using the file time stamp, the row counter and the log.rate constant); data series latitude and longitude are resigned according to set N/S and E/W values, if these are present/valid; latitude and longitude units are also reset to 'd.degLat' and 'd.degLon'. Any data series names in analytes is renamed 'conc.[analyte name]'. If not supplied in the importOBS2PEMS, typical OBS constants are currently assumed. Several of these are based on emission source fuel. Defaults for these are generated according to fuel (default 'petrol').

With importRoyalTek2PEMS, the Royal Tek data modifications are currently being documented.

Author(s)

Karl Ropkins

References

References in preparation.

See Also

See ref.unit.conversions and convertUnits for general unit handling.

Examples

###########
##example 1 
###########

#make little pems
data <- data.frame(speed=1:10, emissions=1:10)
units <- c("m/s", "g/s")
pems <- makePEMS(x = data, units=units, example="my record") 
 
pems                       #the pems object
summary(pems)              #summary of held data
checkInput(speed, pems)    #speed element

pems documentation built on May 2, 2019, 5:20 p.m.