plotLagProfiles: plot lag profiles
In ilkkavir/LPI.gdf: Lag Profile Inversion with gdf files

View source: R/plotLagProfiles.R

plotLagProfiles

R Documentation

plot lag profiles

Description

Plot lag profiles as function of time and range.

Usage

 plotLagProfiles( data , lags=c(1) , f=nothing, re=TRUE , im=FALSE , mod=FALSE , arg=FALSE , err=FALSE, xlim=NULL , ylim=NULL , relim=NULL , imlim=NULL , errlim=NULL , modlim=NULL , arglim=c(-pi,pi)  , stdThresh=NULL , cex=1.0  , col=beer , yheight=FALSE , llhT=NULL , azelT=NULL , llhR=NULL , SIunits=TRUE , tickRes=NULL , figNum=NULL , pdf=NULL , jpg=NULL , width=8.24 , height=5.845 , paper='special' , res=NA  )

Arguments

`data`	Data directory path(s) or an output list from readLPIdir or plotLagProfilfes. The data path is a vector that may contain both full paths to files and directory names.
`lags`	Lags to integrate before plotting. Numbered starting from shortest lag in result files. Default 1. See details.
`f`	Function to apply to the data points before plotting. The default function "nothing" does nothing.
`re`	Logical, include a plot of the lag profile real parts?
`im`	Logical, include a plot of the lag profile imaginary parts?
`mod`	Logical, include a plot of the lag profile modulus?
`arg`	Logical, include a plot of the lag profile argument (phase angle) ?
`err`	Logical, include a plot of the lag profile standard deviation?
`xlim`	x (time) axis limits in hours. Counting starts from the beginning of the day when the first integration period found from "dpath" ended.
`ylim`	Range / height limits in the plot
`relim`	z limits for real part
`imlim`	z limits for imaginary part
`errlim`	z limits for standard deviation
`modlim`	z limits for modulus
`arglim`	z limits for argument (phase)
`stdThresh`	Standard deviation threshold to pass to the function readLPIdir.
`cex`	Scaling factor for figure labels and titles.
`col`	Color scale to use. Default "beer" is Lovibond scale.
`yheight`	Logical, should the range be converted to height? Works only if the result files contain site positions and pointing directions.
`llhT`	c( Latitude [deg], longitude [deg], height [m] ) of the transmitter site
`azelT`	c(azimuth [deg] , elevation [deg]) of the transmitter beam
`llhR`	c( Latitude [deg], longitude [deg], height [m] ) of the receiver site
`SIunits`	Logical, should range be expressed in km and lag in ms? Works only if range.km and lag.us are stored in the data files
`tickRes`	Time tick resolution in seconds, NULL=automatic
`figNum`	Device number to use for plotting
`pdf`	pdf output file name
`jpg`	jpg output file name
`width`	plot width
`height`	plot height
`paper`	paper seletion
`res`	resolution for jpg images