File: popEpi-package.Rd

package info (click to toggle)
r-cran-popepi 0.4.13%2Bdfsg-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 1,656 kB
  • sloc: sh: 13; makefile: 2
file content (58 lines) | stat: -rw-r--r-- 2,321 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
% Generated by roxygen2: do not edit by hand
% Please edit documentation in R/popEpi-package.R
\docType{package}
\name{popEpi-package}
\alias{popEpi}
\alias{popEpi-package}
\title{popEpi: Functions for large-scale epidemiological analysis}
\description{
\pkg{popEpi} is built for the needs of registry-based (large-scale)
epidemiological analysis. This is in most part enabled by the
efficient \pkg{data.table} package for handling and aggregating large data sets.

\pkg{popEpi} currently supplies some utility functions such as \verb{[splitMulti]}
and \verb{[get.yrs]} for preparing large data sets for epidemiological analysis.
Included are also a a few functions that can be used in
epidemiological analysis such as \verb{[sir]} for estimating
standardized incidence/mortality ratios (SIRs/SMRs) and \verb{[survtab]} for
estimating observed and relative/net survival as well as cumulative incidence
functions (CIFs). In particular, \code{survtab} implements the Ederer II
(Ederer and Heise (1959)) and
Pohar Perme estimators (Pohar Perme, Stare, and Esteve (2012)
\doi{10.1111/j.1541-0420.2011.01640.x}) and allows for easy
age-standardisation.

Since there are many benefits to using \code{data.tables}, \pkg{popEpi} returns
outputs by default in the \code{data.table} format where appropriate.
Since \code{data.table}
objects are usually modified by reference, this may have surprising side
effects for users uninitiated in using \code{data.table}. To ensure
that appropriate outputs are in the \code{data.frame} format, set
\code{options("popEpi.datatable" = FALSE)}. However, \code{data.table}
usage is recommended due to better performance and testing coverage.
\code{data.table} is used
by most functions internally in both cases.
}
\seealso{
Useful links:
\itemize{
  \item \url{https://github.com/FinnishCancerRegistry/popEpi}
  \item Report bugs at \url{https://github.com/FinnishCancerRegistry/popEpi/issues}
}

}
\author{
\strong{Maintainer}: Joonas Miettinen \email{joonas.miettinen@cancer.fi} (\href{https://orcid.org/0000-0001-8624-6754}{ORCID})

Authors:
\itemize{
  \item Matti Rantanen \email{matti.rantanen@statfinn.com}
}

Other contributors:
\itemize{
  \item Karri Seppa \email{karri.seppa@cancer.fi} [contributor]
}

}
\keyword{internal}