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
There are several cases across the package where variables are hard coded into the modules. would like to have this scrubbed so that there is more flexibility for example to use treatment variables other than ARM and ACTARM.
What this causes is potential disconnect between study analysis and visualizations in the app. when study analysis uses TRT01P and TRT01A treatment variables then there are cases where the values can differ for the same patient between let's say ACTARM and TRT01A.
users should be able to configure the trt_group input to include treatment variables other then ARM and ACTARM.
There are several cases across the package where variables are hard coded into the modules. would like to have this scrubbed so that there is more flexibility for example to use treatment variables other than ARM and ACTARM.
What this causes is potential disconnect between study analysis and visualizations in the app. when study analysis uses TRT01P and TRT01A treatment variables then there are cases where the values can differ for the same patient between let's say ACTARM and TRT01A.
users should be able to configure the trt_group input to include treatment variables other then ARM and ACTARM.
Current
Users should be able to do
but then code like this will be troublesome. note spelling of facetting should be faceting
would be very helpful to have hard coded references to variables across the teal.goshawk package to be removed.
The text was updated successfully, but these errors were encountered: