start_gui: Starts graphical user interface for gems

Description Usage Author(s)

Description

This function start rp.panel-based GUI for the package "gems". The GUI can be used to define generalized multistate simulation model, run simulations for this model and analyze simulated cohorts.

start_gui() opens the basic panel of the Graphical User Interface for "gems". This basic panel of GUI_gems is used to define the model for which the cohort will be simulated. I. The basic panel - defining the model.

In GUIgems, there are two ways to define the model for the simulation. One method is loading a pre-defined model, which has been written previously in an R script. There in an examples of pre-defined models in the demo folder: model.R

The second method is to define the model directly within the GUI, it can be saved and reused later.

The main part of this panel is a matrix with states and transitions between states. Only transitions above the diagonal are allowed to assure no cycles in the model progression. One can edit names of transition function using the Edit hf matrix, It opens a separate window with hazard functions matrix.

There is a menu for every allowed transition. One can choose one of the following options:

1. Choose the transition function for the given pair of states. This lets the user change the defined transition function from state "i" to state "j" to one of the predefined functions: "impossible", "Weibull", "multWeibull", "exponential"

2. Edit the parameters for the transition function. par_i_j The table with the parameters for the current transition functions will be opened in the editor. In the same table there is a place to set the covariance of parameters. By default, it is set to 0. If parameters weren't previously defined by the user, the paremeters for the transition function are set to the default value of the parameter (if it exists) or to 0.

Apart from defining the transition matrix, the user can:

Set the number of states It creates a new, empty (all transitions impossible) model with the given number of states.

Set <start rows> and <start columns> If the model has more than 12 states, it is impossible to see the whole matrix. This way the user can choose which part of the transition matrix he/she wants to see. It sets the first row and the first column to be shown.

Set <Cohort size> Sets the size of the cohort to be simulated.

Add new state with a given <state_name>, <after> a given state number The user can write in the textentires the name of the state to be added and the state number, after which the new state should be added. This is possible only, when states after the state to be added do not have history as the parameter in their transition functions.

Load hazard functions Opens a dialog box so that the user can choose a directory. Source() will be called on all the files in the directory. All the functions from the files in the directory will be loaded into the current environment.

Save the model Save the currently defined model using the dialog box. Important - at this level only model is saved, even if the cohort was simulated. For saving the simulated cohort, save the model from the cohort panel.

Load baseline Opens a dialogbox to choose a file. Source() is called on the chosen file. The function from the file will be used to generate baseline with the lenght of cohort size.

Simulate Cohort Simulates the cohort for the model described in the panel using the function simulateCohort(). After the cohort is simulated, the basic cohort panel is opened. See part II.

Load model Loads an .RData file or runs the .R file chosen by the user in a dialog box. The file should either be a model saved in Gems session as an .RData file or be an .R file inluding variables: hf - names of the hazard functions or M - hazard functions defined directly without a name; parameters - a matrix generated by generateParametersMatrix(M) with lists of names parameters for the hazard functions defined in hf or M; cohortSize - a number of items to be simulated,

It may also include variables:

covariances - a matrix generated using

generateParametersCovariances(parameters). If covariances matrix is not set in the file, all covariances are set to 0. bl_function - a function which will be used to generate a data frame with baseline or baseline - a data frame with baseline.

Loaded model can also have a simulated cohort. Then after loading the model,
the basic cohort panel will be opened. See part II.

There are examples of defined models and hazard functions in the directory demo.

Update panel rp.panel after changing a parameter gets refreshed first after the next action. Update panel refreshes the rp.panel and shows current values of variables.

Multiple cohorts This button opens the multiple cohorts panel. See part IV.

Edit ttt matrix Edits mypanel$ttt matrix - the matrix with information about which hazard functions are time to transition functions. mypanel$ttt gets changed.

Edit states names User can edit mypanel$statesNames.

Edit hf matrix User can edit transition functions matrix.

Plot hf graph Plots a graph with all possible transitions between states. Here "possible" means, that the transition between two states is allowed (above the diagonal in the matrix) and not set to "impossible". Compare with plotPath_n() - the function in the cohort panel and
the merged cohort panel to plot paths that were present in the simulations.

II. The cohort panel. The basic cohort panel is opened after simulating a cohort or loading a model with a simulated cohort. The panel is used for running analysis on the cohort. There are following actions possible to run in this panel:

Edit Cohort Shows the baseline and the transition times between states in the cohort.

List subcohorts Shows the list of all subcohorts in the model with the attached numbers, including the main subcohort (=the whole simulated cohort), the used defined subcohorts and subcohorts following different progression paths, if the paths were plotted before using the button plot paths.

List states Shows the list of all states in the model

Save the model Opens the save dialog box to choose the name to save the model with the simulated cohort.

Plot paths Simulated elements of the cohorts can follow different progression paths (go through different states). Plot paths marks on the graph of possible transitions the most frequent progression path in the cohort. The less frequent paths may be shown using plot next path

Plot next paths Marks on the graph of possible transitions next most frequent progression path.

Add subcohort <subcohort query> Creates a new subcohort according to the <subcohort query> in the text entry. Subcohorts can be chosen based on the constraints about baseline characteristics or the simulated progression path and times of transmissions.

Examples of the input into the text entry to define a new subcohort:

View subcohort <subcohort number> Shows using View() the subcohort with the number defined in the text entry. The numbers of cohorts with their definitions can be seen after pressing the list cohorts button.

Plot <function name> <states> <subcohorts>

Function name User can choose from the menu one of the functions to be plotted:

see: ?transitionProbabilities, ?cumulativeIncidence

states A list of states, for which the chosen function will be plotted.

Eg. list(1:4), list(c(1,3,5)). If there is more than 6 states chosen, the plots will be opened in different windows.

subcohorts A list of subcohorts to be plotted.

Eg. list(1:3), list(c(1,3))

User can check the numbers of defined subcohorts by clicking the button List subcohorts

States groups <list of list of states to be merged> This option let merging different states of the model. From the group of states to be merged, the time of entry to the earliest of the states counts as the entry time to the meta-state created from this group of states. The time of leaving of the last state from the group counts as the time of leaving the new meta-state. The name of the new state is a convolution of the names of the states composing it connected by a hyphen.

Not all groups of states may be merged - in order to assure lack of cycles, the states to be merged must be sequent ones. States to be merged must be given in the form of a list of lists.

Eg. list(list(1,2), list(3,4)) will merge the states 1 and 2 into one state, and states 3 and 4.

III. Cost analysis module:

1. Edit cost per unit: User can define in the editor costs per unit during the treatment. Default units are: visit, test, medicine, fibroscan The user can define more cost units or change the current costs.

2. Edit QALY per state: User can modify in the editor QALYs for each state of the model.

3. Edit cost per state: User can define cost of the treatment for each state of the model expressed in cost units in a time unit. Eg. 3*medicine + 4* visit + fibroscan

4. Save cost: Saves cost data in the form cost_list =list(units,qualy,StateCost), where units, qualy and StateCosts are lists.

5. Load cost: Loads the cost from the .RData file in the form as described in Save cost. 6. Count cost: It counts cost and QALY for the given cohort. Units cost multiplied by the averaged time in a given state are put into the equations in cost per state. At the level of one cohort, the cost and the QALYs are only shown in the new tab of R. For a plot of cost vs. QALY, see the cost analysis in the multiple cohort panel.

IV. The merged cohort panel. The merged cohort panel is used to analyse the cohort after merging states. There are possible actions to be chosen:

Edit cohort Shows the cohort in the new R Tab

List subcohorts Shows the list of all subcohorts in the model with the attached numbers, including the main subcohort (=the whole simulated cohort) and subcohorts following different progression paths, if the paths were plotted before (using the button plot paths)

List states Shows the list of all states in the model.

Plot paths Simulated elements of the cohorts can follow different progression paths. Plot paths marks on the graph of possible transitions the most frequent progression path in the cohort. The less frequent paths may be shown using plot next path

Plot next paths Marks on the graph of possible transitions next most frequent progression path.

Add subcohort <subcohort query> Creates a new subcohort according to the <subcohort query> in the text entry. Subcohorts can be chosen based on the constraints about baseline characteristics or the simulated progression path and times of transmissions.

Examples of the input into the text entry to define a new subcohort:

View subcohort <subcohort number> Shows using View() the subcohort with the number defined in the text entry. The numbers of cohorts with their definitions can be seen after pressing the list cohorts button.

V. The multicohort panel. While working with multiple cohorts, the user has similar options as with multiple subcohorts. Different is adding a new cohort. The user can also analyse the cost for different cohorts.

Add cohort Adds a new cohort created by simualteCohort from the .RData file chosen by the user. Cohort's name is then the full path of the file with the cohort.

Edit cohort names User can change in the editor names of the cohorts.

View cost Shows the cost data - unit costs, QALYs for each state and the costs expressed in units for each state.

View cohort <cohort number> Shows the cohort with the <cohort number>

List cohorts Shows the list of all cohorts in the model with the attached numbers

Plot <function name> <states> <cohorts> The same as plotting subcohorts in the cohort panel.

The user can check the numbers of defined cohorts by clicking the button List cohorts

Usage

1
start_gui() # start the rp.panel  with GUI for the package "gems"

Author(s)

Zofia Baranczuk


GUIgems documentation built on May 1, 2019, 8:19 p.m.