You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In teal.modules.clinical::tm_a_mmrm, one of the variables needed for the analysis allows for "interaction" terms. These are passed into the template in this form: variable1:variable2 or variable1*variable2.
If we are using a data_extract_input and data_merge_module, these variables do not exist in the data - but their component variables do (and they must).
What we need from data_extract_input is to optionally accept some split criteria to separate interaction selections into their component variables. Or maybe this has to be done at the data_merge_module level.
In
teal.modules.clinical::tm_a_mmrm
, one of the variables needed for the analysis allows for "interaction" terms. These are passed into the template in this form:variable1:variable2
orvariable1*variable2
.If we are using a
data_extract_input
anddata_merge_module
, these variables do not exist in the data - but their component variables do (and they must).What we need from
data_extract_input
is to optionally accept some split criteria to separate interaction selections into their component variables. Or maybe this has to be done at thedata_merge_module
level.The goal is to enable something like this:
Such that the
data_extract_input
shows this in the module:But is doing this behind the scenes (Show R Code):
Note how the "variables" being selected are
BASE
,AVISIT
, andSEX
(BASE:AVISIT
has been split).You may see the current workaround in
tm_a_mmrm
which currently uses 2data_extract_inputs
to accomplish this.Provenance:
The text was updated successfully, but these errors were encountered: