|
34 | 34 | #' ``` |
35 | 35 | #' |
36 | 36 | #' The key takeaway from the predictions is that there are two prediction |
37 | | -#' classes: (-Inf, 0.25] and (0.25, Inf). This is because for our goal of |
| 37 | +#' classes: `(-Inf, 0.25]` and `(0.25, Inf)`. This is because for our goal of |
38 | 38 | #' classification the classes must be discrete. The discretization of the |
39 | 39 | #' real-valued outcome is controlled by the `breaks` argument, which defaults |
40 | | -#' to 0.25. Such breaks will be automatically extended to cover the entire |
41 | | -#' real line. For example, the default break of 0.25 is silently extended to |
42 | | -#' breaks = c(-Inf, .25, Inf) and, therefore, results in two classes: [-Inf, |
43 | | -#' 0.25] and (0.25, Inf). These two classes are used to discretize the |
44 | | -#' outcome. The conversion of the outcome to such classes is handled |
| 40 | +#' to `0.25`. Such breaks will be automatically extended to cover the entire |
| 41 | +#' real line. For example, the default break of `0.25` is silently extended to |
| 42 | +#' `breaks = c(-Inf, .25, Inf)` and, therefore, results in two classes: |
| 43 | +#' `[-Inf, 0.25]` and `(0.25, Inf)`. These two classes are used to discretize |
| 44 | +#' the outcome. The conversion of the outcome to such classes is handled |
45 | 45 | #' internally. So if discrete classes already exist for the outcome in the |
46 | 46 | #' `epi_df`, then we recommend to code a classifier from scratch using the |
47 | 47 | #' `epi_workflow` framework for more control. |
|
0 commit comments