Specified C++11: please drop specification unless essential
checkRd: (-1) pcoxtimecv.Rd:51: Lost braces; missing escapes or markup?
    51 | \item{foldids}{an optional sequence of values between \code{1} and {nfolds} specifying what fold each observation is in. This is important when comparing performance across models. If specified, \code{nfolds} can be missing.}
       |                                                                    ^
checkRd: (-1) pcoxtimecv.Rd:89: Lost braces
    89 | If more than one \code{alphas} is specified, say code{(0.2, 0.5, 1)}, the \code{pcoxtimecv} will search (experimental) for optimal values for alpha with respect to the corresponding lambda values. In this case, optimal alpha and lambda sequence will be returned, i.e., the \code{(alphas, lambdas)} pair that corresponds to the lowest predicted cross-validated error (likelihood deviance).
       |                                                      ^
checkRd: (-1) simtdc.Rd:67: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:69: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:70: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:71: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:72: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:73: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:74: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:76: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:77: Lost braces in \itemize; \value handles \item{}{} directly
Documented arguments not in \usage in Rd file 'getResponse.Rd':
  ‘model’

Functions with \usage entries need to have the appropriate \alias
entries, and all their arguments documented.
The \usage entries must correspond to syntactically valid R code.
See chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.
Specified C++11: please drop specification unless essential
checkRd: (-1) pcoxtimecv.Rd:51: Lost braces; missing escapes or markup?
    51 | \item{foldids}{an optional sequence of values between \code{1} and {nfolds} specifying what fold each observation is in. This is important when comparing performance across models. If specified, \code{nfolds} can be missing.}
       |                                                                    ^
checkRd: (-1) pcoxtimecv.Rd:89: Lost braces
    89 | If more than one \code{alphas} is specified, say code{(0.2, 0.5, 1)}, the \code{pcoxtimecv} will search (experimental) for optimal values for alpha with respect to the corresponding lambda values. In this case, optimal alpha and lambda sequence will be returned, i.e., the \code{(alphas, lambdas)} pair that corresponds to the lowest predicted cross-validated error (likelihood deviance).
       |                                                      ^
checkRd: (-1) simtdc.Rd:67: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:69: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:70: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:71: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:72: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:73: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:74: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:76: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:77: Lost braces in \itemize; \value handles \item{}{} directly
Documented arguments not in \usage in Rd file 'getResponse.Rd':
  ‘model’

Functions with \usage entries need to have the appropriate \alias
entries, and all their arguments documented.
The \usage entries must correspond to syntactically valid R code.
See chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.
Specified C++11: please drop specification unless essential
checkRd: (-1) pcoxtimecv.Rd:51: Lost braces; missing escapes or markup?
    51 | \item{foldids}{an optional sequence of values between \code{1} and {nfolds} specifying what fold each observation is in. This is important when comparing performance across models. If specified, \code{nfolds} can be missing.}
       |                                                                    ^
checkRd: (-1) pcoxtimecv.Rd:89: Lost braces
    89 | If more than one \code{alphas} is specified, say code{(0.2, 0.5, 1)}, the \code{pcoxtimecv} will search (experimental) for optimal values for alpha with respect to the corresponding lambda values. In this case, optimal alpha and lambda sequence will be returned, i.e., the \code{(alphas, lambdas)} pair that corresponds to the lowest predicted cross-validated error (likelihood deviance).
       |                                                      ^
checkRd: (-1) simtdc.Rd:67: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:69: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:70: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:71: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:72: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:73: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:74: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:76: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:77: Lost braces in \itemize; \value handles \item{}{} directly
Documented arguments not in \usage in Rd file 'getResponse.Rd':
  ‘model’

Functions with \usage entries need to have the appropriate \alias
entries, and all their arguments documented.
The \usage entries must correspond to syntactically valid R code.
See chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.
Specified C++11: please drop specification unless essential
checkRd: (-1) pcoxtimecv.Rd:51: Lost braces; missing escapes or markup?
    51 | \item{foldids}{an optional sequence of values between \code{1} and {nfolds} specifying what fold each observation is in. This is important when comparing performance across models. If specified, \code{nfolds} can be missing.}
       |                                                                    ^
checkRd: (-1) pcoxtimecv.Rd:89: Lost braces
    89 | If more than one \code{alphas} is specified, say code{(0.2, 0.5, 1)}, the \code{pcoxtimecv} will search (experimental) for optimal values for alpha with respect to the corresponding lambda values. In this case, optimal alpha and lambda sequence will be returned, i.e., the \code{(alphas, lambdas)} pair that corresponds to the lowest predicted cross-validated error (likelihood deviance).
       |                                                      ^
checkRd: (-1) simtdc.Rd:67: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:69: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:70: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:71: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:72: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:73: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:74: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:76: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:77: Lost braces in \itemize; \value handles \item{}{} directly
Documented arguments not in \usage in Rd file 'getResponse.Rd':
  ‘model’

Functions with \usage entries need to have the appropriate \alias
entries, and all their arguments documented.
The \usage entries must correspond to syntactically valid R code.
See chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.
Specified C++11: please drop specification unless essential
checkRd: (-1) pcoxtimecv.Rd:51: Lost braces; missing escapes or markup?
    51 | \item{foldids}{an optional sequence of values between \code{1} and {nfolds} specifying what fold each observation is in. This is important when comparing performance across models. If specified, \code{nfolds} can be missing.}
       |                                                                    ^
checkRd: (-1) pcoxtimecv.Rd:89: Lost braces
    89 | If more than one \code{alphas} is specified, say code{(0.2, 0.5, 1)}, the \code{pcoxtimecv} will search (experimental) for optimal values for alpha with respect to the corresponding lambda values. In this case, optimal alpha and lambda sequence will be returned, i.e., the \code{(alphas, lambdas)} pair that corresponds to the lowest predicted cross-validated error (likelihood deviance).
       |                                                      ^
checkRd: (-1) simtdc.Rd:67: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:69: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:70: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:71: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:72: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:73: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:74: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:76: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:77: Lost braces in \itemize; \value handles \item{}{} directly
Documented arguments not in \usage in Rd file 'getResponse.Rd':
  ‘model’

Functions with \usage entries need to have the appropriate \alias
entries, and all their arguments documented.
The \usage entries must correspond to syntactically valid R code.
See chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.
Specified C++11: please drop specification unless essential
checkRd: (-1) pcoxtimecv.Rd:51: Lost braces; missing escapes or markup?
    51 | \item{foldids}{an optional sequence of values between \code{1} and {nfolds} specifying what fold each observation is in. This is important when comparing performance across models. If specified, \code{nfolds} can be missing.}
       |                                                                    ^
checkRd: (-1) pcoxtimecv.Rd:89: Lost braces
    89 | If more than one \code{alphas} is specified, say code{(0.2, 0.5, 1)}, the \code{pcoxtimecv} will search (experimental) for optimal values for alpha with respect to the corresponding lambda values. In this case, optimal alpha and lambda sequence will be returned, i.e., the \code{(alphas, lambdas)} pair that corresponds to the lowest predicted cross-validated error (likelihood deviance).
       |                                                      ^
checkRd: (-1) simtdc.Rd:67: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:69: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:70: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:71: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:72: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:73: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:74: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:76: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:77: Lost braces in \itemize; \value handles \item{}{} directly
Documented arguments not in \usage in Rd file 'getResponse.Rd':
  'model'

Functions with \usage entries need to have the appropriate \alias
entries, and all their arguments documented.
The \usage entries must correspond to syntactically valid R code.
See chapter 'Writing R documentation files' in the 'Writing R
Extensions' manual.
Specified C++11: please drop specification unless essential
checkRd: (-1) pcoxtimecv.Rd:51: Lost braces; missing escapes or markup?
    51 | \item{foldids}{an optional sequence of values between \code{1} and {nfolds} specifying what fold each observation is in. This is important when comparing performance across models. If specified, \code{nfolds} can be missing.}
       |                                                                    ^
checkRd: (-1) pcoxtimecv.Rd:89: Lost braces
    89 | If more than one \code{alphas} is specified, say code{(0.2, 0.5, 1)}, the \code{pcoxtimecv} will search (experimental) for optimal values for alpha with respect to the corresponding lambda values. In this case, optimal alpha and lambda sequence will be returned, i.e., the \code{(alphas, lambdas)} pair that corresponds to the lowest predicted cross-validated error (likelihood deviance).
       |                                                      ^
checkRd: (-1) simtdc.Rd:67: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:69: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:70: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:71: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:72: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:73: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:74: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:76: Lost braces in \itemize; \value handles \item{}{} directly
checkRd: (-1) simtdc.Rd:77: Lost braces in \itemize; \value handles \item{}{} directly
Documented arguments not in \usage in Rd file 'getResponse.Rd':
  ‘model’

Functions with \usage entries need to have the appropriate \alias
entries, and all their arguments documented.
The \usage entries must correspond to syntactically valid R code.
See chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.
Specified C++11: please drop specification unless essential
Specified C++11: please drop specification unless essential
Specified C++11: please drop specification unless essential
Specified C++11: please drop specification unless essential