flightconflicts

Tools to analyze conflicts between aircraft.
git clone https://git.eamoncaddigan.net/flightconflicts.git
Log | Files | Refs | README | LICENSE

commit 1654b30618366e7d5008e97355662f2afbc11009
parent 199f13d8a6f3ec39e7a15c51feec06ee1e781cee
Author: eamoncaddigan <eamon.caddigan@gmail.com>
Date:   Fri, 20 May 2016 15:47:55 -0400

Tidier docs.

Diffstat:
MR/identifyNMAC.R | 8++++----
Mman/identifyNMAC.Rd | 8++++----
2 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/R/identifyNMAC.R b/R/identifyNMAC.R @@ -1,10 +1,10 @@ #' Determine whether an NMAC (near mid air collision) has occurred at each time #' point. #' -#' @param trajectory1 A flighttrajectory object corresponding to the first -#' aircraft. -#' @param trajectory2 A flighttrajectory object corresponding to the second -#' aircraft. +#' @param trajectory1 A \code{flighttrajectory} object corresponding to the +#' first aircraft. +#' @param trajectory2 A \code{flighttrajectory} object corresponding to the +#' second aircraft. #' @return The logical vector indicating whether NMAC criteria are met at each #' time point. #' diff --git a/man/identifyNMAC.Rd b/man/identifyNMAC.Rd @@ -8,11 +8,11 @@ point.} identifyNMAC(trajectory1, trajectory2) } \arguments{ -\item{trajectory1}{A flighttrajectory object corresponding to the first -aircraft.} +\item{trajectory1}{A \code{flighttrajectory} object corresponding to the +first aircraft.} -\item{trajectory2}{A flighttrajectory object corresponding to the second -aircraft.} +\item{trajectory2}{A \code{flighttrajectory} object corresponding to the +second aircraft.} } \value{ The logical vector indicating whether NMAC criteria are met at each