We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
Examples of behavior that contributes to a positive environment for our community include:
Examples of unacceptable behavior include:
Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [INSERT CONTACT METHOD]. All complaints will be reviewed and investigated promptly and fairly.
All community leaders are obligated to respect the privacy and security of the reporter of any incident.
Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
Community Impact: A violation through a single incident or series of actions.
Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
Community Impact: A serious violation of community standards, including sustained inappropriate behavior.
Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
Consequence: A permanent ban from any sort of public interaction within the community.
This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
Community Impact Guidelines were inspired by Mozilla’s code of conduct enforcement ladder.
For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.
🙏 Thank you for taking the time to contribute!
Your input is deeply valued, whether an issue, a pull request, or even feedback, regardless of size, content or scope.
👶 Getting started
📔 Code of Conduct
🗃 License
Please refer the project documentation for a brief introduction. Please also see other articles within the project documentation for additional information.
A Code of Conduct governs this project. Participants and contributors are expected to follow the rules outlined therein.
All your contributions will be covered by this project’s license.
We use GitHub to track issues, feature requests, and bugs. Before submitting a new issue, please check if the issue has already been reported. If the issue already exists, please upvote the existing issue 👍.
For new feature requests, please elaborate on the context and the benefit the feature will have for users, developers, or other relevant personas.
This repository uses the GitHub Flow model for collaboration. To submit a pull request:
Create a branch
Please see the branch naming convention below. If you don’t have write access to this repository, please fork it.
Make changes
Make sure your code
Create a pull request (PR)
In the pull request description, please link the relevant issue (if any), provide a detailed description of the change, and include any assumptions.
Suppose your changes are related to a current issue in the current project; please name your branch as follows: <issue_id>_<short_description>. Please use underscore (_) as a delimiter for word separation. For example, 420_fix_ui_bug would be a suitable branch name if your change is resolving and UI-related bug reported in issue number 420 in the current project.
<issue_id>_<short_description>
_
420_fix_ui_bug
420
If your change affects multiple repositories, please name your branches as follows: <issue_id>_<issue_repo>_<short description>. For example, 69_awesomeproject_fix_spelling_error would reference issue 69 reported in project awesomeproject and aims to resolve one or more spelling errors in multiple (likely related) repositories.
<issue_id>_<issue_repo>_<short description>
69_awesomeproject_fix_spelling_error
69
awesomeproject
monorepo
staged.dependencies
Sometimes you might need to change upstream dependent package(s) to be able to submit a meaningful change. We are using staged.dependencies functionality to simulate a monorepo behavior. The dependency configuration is already specified in this project’s staged_dependencies.yaml file. You need to name the feature branches appropriately. This is the only exception from the branch naming convention described above.
staged_dependencies.yaml
Please refer to the staged.dependencies package documentation for more details.
This repository follows some unified processes and standards adopted by its maintainers to ensure software development is carried out consistently within teams and cohesively across other repositories.
This repository follows the standard tidyverse style guide and uses lintr for lint checks. Customized lint configurations are available in this repository’s .lintr file.
tidyverse
lintr
.lintr
Lightweight is the right weight. This repository follows tinyverse recommedations of limiting dependencies to minimum.
If the code is not compatible with all (!) historical versions of a given dependenct package, it is required to specify minimal version in the DESCRIPTION file. In particular: if the development version requires (imports) the development version of another package - it is required to put abc (>= 1.2.3.9000).
DESCRIPTION
abc (>= 1.2.3.9000)
We continuously test our packages against the newest R version along with the most recent dependencies from CRAN and BioConductor. We recommend that your working environment is also set up in the same way. You can find the details about the R version and packages used in the R CMD check GitHub Action execution log - there is a step that prints out the R sessionInfo().
R CMD check
sessionInfo()
If you discover bugs on older R versions or with an older set of dependencies, please create the relevant bug reports.
pre-commit
We highly recommend that you use the pre-commit tool combined with R hooks for pre-commit to execute some of the checks before committing and pushing your changes.
R hooks for pre-commit
Pre-commit hooks are already available in this repository’s .pre-commit-config.yaml file.
.pre-commit-config.yaml
As mentioned previously, all contributions are deeply valued and appreciated. While all contribution data is available as part of the repository insights, to recognize a significant contribution and hence add the contributor to the package authors list, the following rules are enforced:
git blame
*Excluding auto-generated code, including but not limited to roxygen comments or renv.lock files.
roxygen
renv.lock
The package maintainer also reserves the right to adjust the criteria to recognize contributions.
If you have further questions regarding the contribution guidelines, please contact the package/repository maintainer.
If you believe you have found a security vulnerability in any of the repositories in this organization, please report it to us through coordinated disclosure.
Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.
Instead, please send an email to vulnerability.management[@]roche.com.
Please include as much of the information listed below as you can to help us better understand and resolve the issue:
This information will help us triage your report more quickly.
Please make sure that while reporting issues in the form a bug, feature, or pull request, all sensitive information such as PII, PHI, and PCI is completely removed from any text and attachments, including pictures and videos.
Nick Paszty. Author, maintainer.
F. Hoffmann-La Roche AG. Copyright holder, funder.
Paszty N, Kaledkowski D, Hallal M, Rucki P, Liu W, Tomlinson J, Toth B, Zhao J, Nasinski M (2024). teal.goshawk: Longitudinal Visualization 'teal' Modules. -R package version 0.2.0.9016, +R package version 0.2.0.9017, https://github.com/insightsengineering/teal.goshawk/, https://insightsengineering.github.io/teal.goshawk/.
@Manual{, title = {teal.goshawk: Longitudinal Visualization `teal` Modules}, author = {Nick Paszty and Dawid Kaledkowski and Mahmoud Hallal and Pawel Rucki and Wenyi Liu and Jeffrey Tomlinson and Bali Toth and Junlue Zhao and Maciej Nasinski}, year = {2024}, - note = {R package version 0.2.0.9016, + note = {R package version 0.2.0.9017, https://github.com/insightsengineering/teal.goshawk/}, url = {https://insightsengineering.github.io/teal.goshawk/}, }
teal_data
teal::init()
Show Warnings
teal.logger
tm_g_gh_lineplot
tm_g_gh_correlationplot
shinyvalidate::InputValidator
shiny::validate
ui_arbitrary_lines
chunks
qenv
datasets
FilteredData
data
tdata
filter_panel_api
FilterPanelAPI
tm_g_gh_scatterplot
scda
teal.reporter
plot_relative_height_value
nestcolor
srv_arbitrary_lines
_FILTERED
teal.slice
pkgdown
hline
hline_arb
hline_arb_color
hline_arb_label
moduleServer
teal.devel
teal::root_modules
teal::modules
teal
tm_g_gh_spaghettiplot
tm_g_gh_boxplot
tm_g_gh_density_distribution_plot
R >= 3.6
test.nest
utils.nest
checkmate
LOQs
vline
vline_arb_var
vline_arb_color
vline_arb_label
AVISITCD
Visit
LICENCE
README
random.cdisc.data
error_on_lint: TRUE
tidyr
gather
spread
pivot_wider
pivot_longer
g_lineplot
brushedPoints
clean_brushedPoints
toggle_slider_server
toggle.R
toggleable.R
facet_var
font_size
plot_font_size
code
cdisc_dataset
cdisc_data
plot_with_settings
templ_ui_params_vars
optionalSelectInput
shape_choices
choices_selected
LLOQ
ULOQ
.data
PARAMCD
LoQ
get_choices(choices)
An object that contains choices.
A vector of choices.
CSS
/inst/css/
include_css_files(pattern = "*")
(character) pattern of files to be included
character
HTML code that includes CSS files
These modules render the UI and call the respective longitudinal visualization function
tm_g_gh_boxplot()
tm_g_gh_correlationplot()
tm_g_gh_density_distribution_plot()
tm_g_gh_lineplot()
tm_g_gh_spaghettiplot()
Utility functions
maptrt()
These functions have been deprecated
tm_g_gh_scatterplot()
maptrt(df_armvar, code = c("M", "O"))
the dataframe and column name containing treatment code. e.g. ADSL$ARMCD
ADSL$ARMCD
controls whether mapping or ordering code is written to console. Valid values: "M" and "O".
"M"
"O"
SPA configure study specific pre-processing for deploying goshawk. writing the code for ARM mapping and ordering is tedious. this function helps to get that started by providing the left hand side of the mapping and ordering syntax. call the function and then copy and paste the resulting code from the console @@ -117,8 +75,7 @@
goshawk
ARM
ADSL <- rADSL # get treatment mapping code @@ -137,19 +94,17 @@ ExamplesOn this page - -
TealReportCard
teal.goshawk
R/utils.R
report_card_template_goshawk.Rd
report_card_template_goshawk( title, label, @@ -106,76 +69,59 @@ Usage
(character(1)) title of the card (unless overwritten by label)
character(1)
(character(1)) label provided by the user when adding the card
(logical(1)) flag indicating to add filter state
logical(1)
(FilterPanelAPI) object with API that allows the generation of the filter state in the report
(list) a list containing constraint variables, including:
list
constraint_var (character(1)) the constraint variable name.
constraint_range_min (numeric(1)) the minimum constraint range value.
numeric(1)
constraint_range_max (numeric(1)) the maximum constraint range value.
(character(1)) description of the constraints.
(character(1)) style of the constraint text block. options: default, verbatim (default is default).
default
verbatim
(TealReportCard) populated with a title, description, and filter state
srv_arbitrary_lines(id)
An ID string that corresponds with the ID used to call the module's UI function.
(reactive) returning a list containing line_arb, line_arb_color, line_arb_label which are validated and could be passed to goshawk plot functions.
reactive
line_arb
line_arb_color
line_arb_label
The data used for teal.goshawk have some constraints. It must contain the columns AVISITCD, BASE, BASE2, AVALU, LBSTRESC, LOQFL, CHG2, and PCHG2.
BASE
BASE2
AVALU
LBSTRESC
LOQFL
CHG2
PCHG2
Useful links:
https://insightsengineering.github.io/teal.goshawk/
https://github.com/insightsengineering/teal.goshawk/
Report bugs at https://github.com/insightsengineering/teal.goshawk/issues
Maintainer: Nick Paszty nick.paszty@gene.com
Authors:
Dawid Kaledkowski dawid.kaledkowski@roche.com
Mahmoud Hallal mahmoud.hallal@roche.com
Pawel Rucki pawel.rucki@roche.com
Wenyi Liu liu.wenyi@roche.com
Bali Toth toth.balazs@gene.com
Junlue Zhao
Maciej Nasinski
Other contributors:
Maximilian Mordig [contributor]
F. Hoffmann-La Roche AG [copyright holder, funder]
tm_g_gh_boxplot( label, dataname, @@ -121,167 +85,135 @@ Usage
menu item label of the module in the teal app.
analysis data passed to the data argument of init. E.g. ADaM structured laboratory data frame ALB.
init
ADaM
ALB
name of variable containing biomarker codes e.g. PARAMCD.
list of biomarkers of interest.
name of variable containing biomarker results displayed on y-axis e.g. AVAL. When not provided, it defaults to choices_selected(c("AVAL", "CHG"), "AVAL").
AVAL
choices_selected(c("AVAL", "CHG"), "AVAL")
variable to categorize the x-axis. When not provided, it defaults to choices_selected("AVISITCD", "AVISITCD").
choices_selected("AVISITCD", "AVISITCD")
variable to facet the plots by. When not provided, it defaults to choices_selected(c("ARM", "ACTARM"), "ARM").
choices_selected(c("ARM", "ACTARM"), "ARM")
choices_selected object with available choices and pre-selected option for variable names representing treatment group e.g. ARM.
vector of colors applied to treatment values.
vector of symbols applied to LOQ values.
LOQ
numeric value indicating number of facets per row.
loq legend toggle.
loq
45 degree rotation of x-axis values.
x-axis
numeric vector of at most 2 values identifying intercepts for arbitrary horizontal lines.
a character vector of at most length of hline_arb. naming the color for the arbitrary horizontal lines.
a character vector of at most length of hline_arb. naming the label for the arbitrary horizontal lines.
a character vector to name the columns that will define additional horizontal lines.
a character vector naming the colors for the additional horizontal lines.
a character vector naming the labels for the additional horizontal lines that will appear in the legend.
controls plot height.
optional, controls plot width.
font size control for title, x-axis label, y-axis label and legend.
y-axis
plot dot size.
numeric vector to define transparency of plotted points.
(shiny.tag) optional, with text placed before the output to put the output into context. For example a title.
shiny.tag
(shiny.tag) optional, with text placed after the output to put the output into context. For example the shiny::helpText() elements are useful.
shiny::helpText()
an module object
module
Jeff Tomlinson (tomlinsj) jeffrey.tomlinson@roche.com
Balazs Toth (tothb2) toth.balazs@gene.com
# Example using ADaM structure analysis dataset. data <- teal_data() data <- within(data, { @@ -290,10 +222,10 @@ Examples library(stringr) # use non-exported function from goshawk - h_identify_loq_values <- getFromNamespace("h_identify_loq_values", "goshawk") + .h_identify_loq_values <- getFromNamespace("h_identify_loq_values", "goshawk") # original ARM value = dose value - arm_mapping <- list( + .arm_mapping <- list( "A: Drug X" = "150mg QD", "B: Placebo" = "Placebo", "C: Combination" = "Combination" @@ -301,7 +233,7 @@ Examples set.seed(1) ADSL <- rADSL ADLB <- rADLB - var_labels <- lapply(ADLB, function(x) attributes(x)$label) + .var_labels <- lapply(ADLB, function(x) attributes(x)$label) ADLB <- ADLB %>% mutate( AVISITCD = case_when( @@ -322,9 +254,9 @@ Examples ARMCD == "ARM B" ~ 2, ARMCD == "ARM A" ~ 3 ), - ARM = as.character(arm_mapping[match(ARM, names(arm_mapping))]), + ARM = as.character(.arm_mapping[match(ARM, names(.arm_mapping))]), ARM = factor(ARM) %>% reorder(TRTORD), - ACTARM = as.character(arm_mapping[match(ACTARM, names(arm_mapping))]), + ACTARM = as.character(.arm_mapping[match(ACTARM, names(.arm_mapping))]), ACTARM = factor(ACTARM) %>% reorder(TRTORD), ANRLO = 50, ANRHI = 75 @@ -341,20 +273,17 @@ Examples )) %>% ungroup() - attr(ADLB[["ARM"]], "label") <- var_labels[["ARM"]] - attr(ADLB[["ACTARM"]], "label") <- var_labels[["ACTARM"]] + attr(ADLB[["ARM"]], "label") <- .var_labels[["ARM"]] + attr(ADLB[["ACTARM"]], "label") <- .var_labels[["ACTARM"]] attr(ADLB[["ANRLO"]], "label") <- "Analysis Normal Range Lower Limit" attr(ADLB[["ANRHI"]], "label") <- "Analysis Normal Range Upper Limit" # add LLOQ and ULOQ variables - ALB_LOQS <- h_identify_loq_values(ADLB, "LOQFL") + ALB_LOQS <- .h_identify_loq_values(ADLB, "LOQFL") ADLB <- left_join(ADLB, ALB_LOQS, by = "PARAM") }) -datanames <- c("ADSL", "ADLB") -datanames(data) <- datanames - -join_keys(data) <- default_cdisc_join_keys[datanames] +join_keys(data) <- default_cdisc_join_keys[names(data)] app <- init( data = data, @@ -386,19 +315,17 @@ ExamplesOn this page - -
tm_g_gh_correlationplot( label, dataname, @@ -127,206 +91,166 @@ Usage
analysis data passed to the data argument of init. E.g. ADaM structured laboratory data frame ADLB.
ADLB
biomarker selected for x-axis.
name of variable containing biomarker results displayed on x-axis e.g. BASE.
biomarker selected for y-axis.
name of variable containing biomarker results displayed on y-axis e.g. AVAL.
visit facet toggle.
facet by treatment group trt_group.
trt_group
include regression line and annotations for slope and coefficient in visualization. Use with facet TRUE.
a character vector naming the labels for the additional horizontal lines that will appear
a character vector of at most length of vline_arb. naming the color for the arbitrary horizontal lines.
vline_arb
a character vector of at most length of vline_arb. naming the label for the arbitrary horizontal lines.
a character vector to name the columns that will define additional vertical lines.
a character vector naming the colors for the additional vertical lines.
a character vector naming the labels for the additional vertical lines that will appear
font size control for regression line annotations.
Nick Paszty (npaszty) paszty.nicholas@gene.com
# Example using ADaM structure analysis dataset. data <- teal_data() data <- within(data, { @@ -334,22 +258,22 @@ Examples library(stringr) # use non-exported function from goshawk - h_identify_loq_values <- getFromNamespace("h_identify_loq_values", "goshawk") + .h_identify_loq_values <- getFromNamespace("h_identify_loq_values", "goshawk") # original ARM value = dose value - arm_mapping <- list( + .arm_mapping <- list( "A: Drug X" = "150mg QD", "B: Placebo" = "Placebo", "C: Combination" = "Combination" ) - color_manual <- c("150mg QD" = "#000000", "Placebo" = "#3498DB", "Combination" = "#E74C3C") + .color_manual <- c("150mg QD" = "#000000", "Placebo" = "#3498DB", "Combination" = "#E74C3C") # assign LOQ flag symbols: circles for "N" and triangles for "Y", squares for "NA" - shape_manual <- c("N" = 1, "Y" = 2, "NA" = 0) + .shape_manual <- c("N" = 1, "Y" = 2, "NA" = 0) set.seed(1) ADSL <- rADSL ADLB <- rADLB - var_labels <- lapply(ADLB, function(x) attributes(x)$label) + .var_labels <- lapply(ADLB, function(x) attributes(x)$label) ADLB <- ADLB %>% mutate(AVISITCD = case_when( AVISIT == "SCREENING" ~ "SCR", @@ -379,7 +303,7 @@ Examples ifelse(grepl("A", ARMCD), 3, NA) ) )) %>% - mutate(ARM = as.character(arm_mapping[match(ARM, names(arm_mapping))])) %>% + mutate(ARM = as.character(.arm_mapping[match(ARM, names(.arm_mapping))])) %>% mutate(ARM = factor(ARM) %>% reorder(TRTORD)) %>% mutate( @@ -407,19 +331,16 @@ Examples paste(">", round(runif(1, min = 70, max = 75))), LBSTRESC )) %>% ungroup() - attr(ADLB[["ARM"]], "label") <- var_labels[["ARM"]] + attr(ADLB[["ARM"]], "label") <- .var_labels[["ARM"]] attr(ADLB[["ANRHI"]], "label") <- "Analysis Normal Range Upper Limit" attr(ADLB[["ANRLO"]], "label") <- "Analysis Normal Range Lower Limit" # add LLOQ and ULOQ variables - ADLB_LOQS <- h_identify_loq_values(ADLB, "LOQFL") + ADLB_LOQS <- .h_identify_loq_values(ADLB, "LOQFL") ADLB <- left_join(ADLB, ADLB_LOQS, by = "PARAM") }) -datanames <- c("ADSL", "ADLB") -datanames(data) <- datanames - -join_keys(data) <- default_cdisc_join_keys[datanames] +join_keys(data) <- default_cdisc_join_keys[names(data)] app <- init( data = data, @@ -471,19 +392,17 @@ ExamplesOn this page - -
tm_g_gh_density_distribution_plot( label, dataname, @@ -115,133 +79,107 @@ Usage
biomarker selected.
name or hex value for combined treatment color.
plot line thickness.
display combined treatment line toggle.
None
# Example using ADaM structure analysis dataset. data <- teal_data() data <- within(data, { @@ -249,14 +187,14 @@ Examples library(stringr) # original ARM value = dose value - arm_mapping <- list( + .arm_mapping <- list( "A: Drug X" = "150mg QD", "B: Placebo" = "Placebo", "C: Combination" = "Combination" ) ADSL <- rADSL ADLB <- rADLB - var_labels <- lapply(ADLB, function(x) attributes(x)$label) + .var_labels <- lapply(ADLB, function(x) attributes(x)$label) ADLB <- ADLB %>% mutate( AVISITCD = case_when( @@ -277,19 +215,17 @@ Examples ARMCD == "ARM B" ~ 2, ARMCD == "ARM A" ~ 3 ), - ARM = as.character(arm_mapping[match(ARM, names(arm_mapping))]), + ARM = as.character(.arm_mapping[match(ARM, names(.arm_mapping))]), ARM = factor(ARM) %>% reorder(TRTORD), - ACTARM = as.character(arm_mapping[match(ACTARM, names(arm_mapping))]), + ACTARM = as.character(.arm_mapping[match(ACTARM, names(.arm_mapping))]), ACTARM = factor(ACTARM) %>% reorder(TRTORD) ) - attr(ADLB[["ARM"]], "label") <- var_labels[["ARM"]] - attr(ADLB[["ACTARM"]], "label") <- var_labels[["ACTARM"]] + attr(ADLB[["ARM"]], "label") <- .var_labels[["ARM"]] + attr(ADLB[["ACTARM"]], "label") <- .var_labels[["ACTARM"]] }) -datanames <- c("ADSL", "ADLB") -datanames(data) <- datanames -join_keys(data) <- default_cdisc_join_keys[datanames] +join_keys(data) <- default_cdisc_join_keys[names(data)] app <- init( data = data, @@ -326,19 +262,17 @@ ExamplesOn this page - -
tm_g_gh_lineplot( label, dataname, @@ -124,196 +88,159 @@ Usage
single name of variable in analysis data that includes parameter labels.
single name of variable in analysis data that is used as x-axis in the plot for the respective goshawk function.
single name of variable in analysis data that is used as summary variable in the respective goshawk function.
vector that can be used to define the factor level of xvar. Only use it when xvar is character or factor.
xvar
data constraint variable.
data constraint variable choices.
vector that can be used to define factor level of trt_group.
Vector or choices_selected object with names of ADSL variables which can be used to change shape
ADSL
string of statistics
string vector representing customized colors
numeric vector to define the tick values of x-axis when x variable is numeric. Default value is waive().
vector with same length of xtick to define the label of x-axis tick values. Default value is waive().
xtick
logical(1) value indicating whether to rotate x-axis labels.
control font size for title, x-axis, y-axis and legend font.
controls the position dodge of error bar
minimum count of observations (as listed in the output table) to plot nodes on the graph
controls the font size of values in the table
numeric value between 500 and 5000 for controlling the starting value of the relative plot height slider
shiny object
shiny
Wenyi Liu (luiw2) wenyi.liu@roche.com
# Example using ADaM structure analysis dataset. data <- teal_data() data <- within(data, { @@ -322,7 +249,7 @@ Examples library(nestcolor) # original ARM value = dose value - arm_mapping <- list( + .arm_mapping <- list( "A: Drug X" = "150mg QD", "B: Placebo" = "Placebo", "C: Combination" = "Combination" @@ -330,7 +257,7 @@ Examples ADSL <- rADSL ADLB <- rADLB - var_labels <- lapply(ADLB, function(x) attributes(x)$label) + .var_labels <- lapply(ADLB, function(x) attributes(x)$label) ADLB <- ADLB %>% mutate( AVISITCD = case_when( @@ -351,18 +278,16 @@ Examples ARMCD == "ARM B" ~ 2, ARMCD == "ARM A" ~ 3 ), - ARM = as.character(arm_mapping[match(ARM, names(arm_mapping))]), + ARM = as.character(.arm_mapping[match(ARM, names(.arm_mapping))]), ARM = factor(ARM) %>% reorder(TRTORD), - ACTARM = as.character(arm_mapping[match(ACTARM, names(arm_mapping))]), + ACTARM = as.character(.arm_mapping[match(ACTARM, names(.arm_mapping))]), ACTARM = factor(ACTARM) %>% reorder(TRTORD) ) - attr(ADLB[["ARM"]], "label") <- var_labels[["ARM"]] - attr(ADLB[["ACTARM"]], "label") <- var_labels[["ACTARM"]] + attr(ADLB[["ARM"]], "label") <- .var_labels[["ARM"]] + attr(ADLB[["ACTARM"]], "label") <- .var_labels[["ACTARM"]] }) -datanames <- c("ADSL", "ADLB") -datanames(data) <- datanames -join_keys(data) <- default_cdisc_join_keys[datanames] +join_keys(data) <- default_cdisc_join_keys[names(data)] app <- init( data = data, @@ -390,19 +315,17 @@ ExamplesOn this page - -
tm_g_gh_scatterplot( label, dataname, @@ -120,137 +84,110 @@ Usage
y-axis value to position of horizontal line.
x-axis value to position a vertical line.
# Example using ADaM structure analysis dataset. data <- teal_data() data <- within(data, { @@ -258,7 +195,7 @@ Examples library(stringr) # original ARM value = dose value - arm_mapping <- list( + .arm_mapping <- list( "A: Drug X" = "150mg QD", "B: Placebo" = "Placebo", "C: Combination" = "Combination" @@ -266,7 +203,7 @@ Examples ADSL <- rADSL ADLB <- rADLB - var_labels <- lapply(ADLB, function(x) attributes(x)$label) + .var_labels <- lapply(ADLB, function(x) attributes(x)$label) ADLB <- ADLB %>% mutate( AVISITCD = case_when( @@ -287,18 +224,16 @@ Examples ARMCD == "ARM B" ~ 2, ARMCD == "ARM A" ~ 3 ), - ARM = as.character(arm_mapping[match(ARM, names(arm_mapping))]), + ARM = as.character(.arm_mapping[match(ARM, names(.arm_mapping))]), ARM = factor(ARM) %>% reorder(TRTORD), - ACTARM = as.character(arm_mapping[match(ACTARM, names(arm_mapping))]), + ACTARM = as.character(.arm_mapping[match(ACTARM, names(.arm_mapping))]), ACTARM = factor(ACTARM) %>% reorder(TRTORD) ) - attr(ADLB[["ARM"]], "label") <- var_labels[["ARM"]] - attr(ADLB[["ACTARM"]], "label") <- var_labels[["ACTARM"]] + attr(ADLB[["ARM"]], "label") <- .var_labels[["ARM"]] + attr(ADLB[["ACTARM"]], "label") <- .var_labels[["ACTARM"]] }) -datanames <- c("ADSL", "ADLB") -datanames(data) <- datanames -join_keys(data) <- default_cdisc_join_keys[datanames] +join_keys(data) <- default_cdisc_join_keys[names(data)] app <- init( @@ -340,19 +275,17 @@ ExamplesOn this page - -
tm_g_gh_spaghettiplot( label, dataname, @@ -127,202 +91,164 @@ Usage
name of unique subject id variable.
vector that can be used to define the factor level of xaxis_var. Only use it when xaxis_var is character or factor.
xaxis_var
control group mean or median overlay.
waive()
logical(1) value indicating whether to rotate x-axis labels
logical(1) should scales be "fixed" (FALSE) of "free" (TRUE) for x-axis in facet_wrap scales parameter.
"fixed"
FALSE
"free"
TRUE
facet_wrap
scales
# Example using ADaM structure analysis dataset. data <- teal_data() data <- within(data, { @@ -330,10 +256,10 @@ Examples library(stringr) # use non-exported function from goshawk - h_identify_loq_values <- getFromNamespace("h_identify_loq_values", "goshawk") + .h_identify_loq_values <- getFromNamespace("h_identify_loq_values", "goshawk") # original ARM value = dose value - arm_mapping <- list( + .arm_mapping <- list( "A: Drug X" = "150mg QD", "B: Placebo" = "Placebo", "C: Combination" = "Combination" @@ -341,7 +267,7 @@ Examples set.seed(1) ADSL <- rADSL ADLB <- rADLB - var_labels <- lapply(ADLB, function(x) attributes(x)$label) + .var_labels <- lapply(ADLB, function(x) attributes(x)$label) ADLB <- ADLB %>% mutate( AVISITCD = case_when( @@ -362,9 +288,9 @@ Examples ARMCD == "ARM B" ~ 2, ARMCD == "ARM A" ~ 3 ), - ARM = as.character(arm_mapping[match(ARM, names(arm_mapping))]), + ARM = as.character(.arm_mapping[match(ARM, names(.arm_mapping))]), ARM = factor(ARM) %>% reorder(TRTORD), - ACTARM = as.character(arm_mapping[match(ACTARM, names(arm_mapping))]), + ACTARM = as.character(.arm_mapping[match(ACTARM, names(.arm_mapping))]), ACTARM = factor(ACTARM) %>% reorder(TRTORD), ANRLO = 30, ANRHI = 75 @@ -378,19 +304,17 @@ Examples paste(">", round(runif(1, min = 70, max = 75))), LBSTRESC )) %>% ungroup() - attr(ADLB[["ARM"]], "label") <- var_labels[["ARM"]] - attr(ADLB[["ACTARM"]], "label") <- var_labels[["ACTARM"]] + attr(ADLB[["ARM"]], "label") <- .var_labels[["ARM"]] + attr(ADLB[["ACTARM"]], "label") <- .var_labels[["ACTARM"]] attr(ADLB[["ANRLO"]], "label") <- "Analysis Normal Range Lower Limit" attr(ADLB[["ANRHI"]], "label") <- "Analysis Normal Range Upper Limit" # add LLOQ and ULOQ variables - ALB_LOQS <- h_identify_loq_values(ADLB, "LOQFL") + ALB_LOQS <- .h_identify_loq_values(ADLB, "LOQFL") ADLB <- left_join(ADLB, ALB_LOQS, by = "PARAM") }) -datanames <- c("ADSL", "ADLB") -datanames(data) <- datanames -join_keys(data) <- default_cdisc_join_keys[datanames] +join_keys(data) <- default_cdisc_join_keys[names(data)] app <- init( data = data, @@ -431,19 +355,17 @@ ExamplesOn this page - -
toggle_slider_ui(id, label) toggle_slider_server(id, data_state, ...) @@ -101,47 +65,38 @@ Usage
character module id
label label for input field, e.g. slider or numeric inputs
label
additional parameters to pass to sliderInput
sliderInput
NULL.
NULL
ui_arbitrary_lines( id, line_arb, @@ -97,63 +61,52 @@ Usage
(character(1)) defining namespace of the shiny module.
(numeric) default values for the textInput defining values of arbitrary lines
numeric
textInput
(character) default values for the textInput defining labels of arbitrary lines
(character) default values for the textInput defining colors of arbitrary lines
(character(1)) title of the arbitrary lines input. The default is "Arbitrary Horizontal Lines".
(shiny.tag) an input to define values, colors and labels for arbitrary straight lines.
