-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathsiman_table.sthlp
73 lines (51 loc) · 2.73 KB
/
siman_table.sthlp
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
{smcl}
{* *! version 0.5 21nov2022}{...}
{vieweralsosee "Main siman help page" "siman"}{...}
{viewerjumpto "Syntax" "siman_table##syntax"}{...}
{viewerjumpto "Description" "siman_table##description"}{...}
{viewerjumpto "Authors" "siman_table##authors"}{...}
{title:Title}
{phang}
{bf:siman table} {hline 2} Tabulates the performance measures data created by {bf:{help siman analyse}}
{marker syntax}{...}
{title:Syntax}
{phang}
{cmdab:siman table} [{it:performancemeasures}] [if], [column({it:varname})]
{pstd}{it:performancemeasures} are any {help siman analyse##perfmeas:performance measures} calculated by {help siman analyse} and {help simsum:simsum}. If not specified, all available performance measures are calculated.
{pstd}
{opt if} must be applied to {bf:dgm}, {bf:target} and/or {bf:method} only.
{synoptset 20 tabbed}{...}
{synopthdr}
{synoptline}
{synopt:{opt c:olumn(varname)}}specifies which factors are placed in the columns.{p_end}
{synoptline}
{marker description}{...}
{title:Description}
{pstd}
{cmd:siman table} uses the inbuilt Stata program {help tabdisp:tabdisp} to display the performance measures created by {bf:{help siman analyse}},
split by dgms, targets and methods.
{pstd}
If {opt column()} is not specified, the column variable is decided as follows.
If there is more than one method, then method is placed in the columns.
Otherwise, if there is more than one target, then target is placed in the columns.
Otherwise, the first dgm variable is placed in the columns.
All the other variables are then placed in the rows.
However, if this leaves more than four variables in the rows, then {cmd:siman table} exits with error.
{pstd}
Where there are 2 entries per row in the table, the first entry is the performance measure value,
and the second is its Monte Carlo Standard Error (MCSE).
MSCEs quantify the simulation uncertainty.
They provide an estimate of the standard error of the performance estimate, as a finite number of repetitions are used.
For example, for the performance measure bias, the Monte Carlo standard error shows the uncertainty around the estimate of the bias.
{pstd}
{cmd:siman table} is called automatically by {bf:{help siman analyse}} (unless the {cmd:notable} option is used),
but it can also be called on its own once the performance measures data
has been created by the {bf:siman} suite.
{pstd}For examples, see {bf:{help siman analyse##examples:siman analyse}}.
{marker authors}{...}
{title:Authors}
{pstd}Ella Marley-Zagar, MRC Clinical Trials Unit at UCL{break}
{pstd}Ian White, MRC Clinical Trials Unit at UCL{break}
Email: {browse "mailto:[email protected]":Ian White}
{pstd}Tim Morris, MRC Clinical Trials Unit at UCL, London, UK.{break}
Email: {browse "mailto:[email protected]":Tim Morris}