Skip to content

Commit

Permalink
resolve green ci (#1293)
Browse files Browse the repository at this point in the history
close #1282

---------

Signed-off-by: Davide Garolini <[email protected]>
Signed-off-by: Joe Zhu <[email protected]>
Co-authored-by: Davide Garolini <[email protected]>
  • Loading branch information
shajoezhu and Melkiades authored Sep 20, 2024
1 parent 0817483 commit 0bc1963
Show file tree
Hide file tree
Showing 5 changed files with 8 additions and 5 deletions.
3 changes: 2 additions & 1 deletion DESCRIPTION
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,8 @@ Suggests:
testthat (>= 3.1.9),
withr (>= 2.0.0)
VignetteBuilder:
knitr
knitr,
rmarkdown
RdMacros:
lifecycle,
Rdpack
Expand Down
1 change: 0 additions & 1 deletion tests/testthat/setup.R
Original file line number Diff line number Diff line change
@@ -1,6 +1,5 @@
# Extra libraries (suggested) for tests
library(dplyr)
library(nestcolor)

# skip_if_too_deep
skip_if_too_deep <- function(depth) {
Expand Down
3 changes: 3 additions & 0 deletions tests/testthat/test-individual_patient_plot.R
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,9 @@ adlb <- tern_ex_adlb %>%
slice(1:36)

testthat::test_that("h_g_ipp works correctly", {
skip_if_not_installed("nestcolor")
require("nestcolor", quietly = TRUE)

testthat::expect_silent(h_g_ipp(
df = adlb,
xvar = "AVISIT",
Expand Down
2 changes: 1 addition & 1 deletion vignettes/tables.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ The table layout is materialized with the `rtables::build_table` function and th
The `tern` analyze functions are wrappers around `rtables::analyze` function, they offer various methods useful from the perspective of clinical trials and other statistical projects.

Examples of the `tern` analyze functions are `count_occurrences`, `summarize_ancova` or `analyze_vars`.
As there is no one prefix to identify all `tern` analyze functions it is recommended to use the [the tern website functions reference](https://insightsengineering.github.io/tern/main/reference/index.html).
As there is no one prefix to identify all `tern` analyze functions it is recommended to use the [the tern website functions reference](https://insightsengineering.github.io/tern/latest-tag/reference/index.html).

### Internals of `tern` Analyze Functions

Expand Down
4 changes: 2 additions & 2 deletions vignettes/tern.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ data visualizations helper functions:
- ...


The reference of `tern` functions is available on [the tern website functions reference](https://insightsengineering.github.io/tern/main/reference/index.html).
The reference of `tern` functions is available on [the tern website functions reference](https://insightsengineering.github.io/tern/latest-tag/reference/index.html).

---------

Expand All @@ -82,7 +82,7 @@ The table layout is materialized with the `rtables::build_table` function and th
The `tern` analytical functions are wrappers around the `rtables::analyze` function; they offer various methods useful from the perspective of clinical trials and other statistical projects.

Examples of the `tern` analytical functions are `count_occurrences`, `summarize_ancova` and `analyze_vars`.
As there is no one prefix to identify all `tern` analytical functions it is recommended to use the reference subsection on [the tern website](https://insightsengineering.github.io/tern/main/reference/index.html).
As there is no one prefix to identify all `tern` analytical functions it is recommended to use the reference subsection on [the tern website](https://insightsengineering.github.io/tern/latest-tag/reference/index.html).

In the `rtables` code below we first describe the two tables and assign the descriptions to the variables `lyt` and `lyt2`. We then built the tables using the actual data with `rtables::build_table`. The description of a table is called a table **layout**. The **analyze instruction** adds to the layout that the `ARM` variable should be analyzed with the `mean` analysis function and the result should be rounded to 1 decimal place.
Hence, a **layout** is “pre-data”; that is, it’s a description of **how to build a table once we get data**.
Expand Down

0 comments on commit 0bc1963

Please sign in to comment.