1 Introduction
This document describes the FACTS XML file (“.facts”) file format FACTS Platform Trial for Continuous & Dichotomous endpoints.
It is intended for expert FACTS users who wish to create modified versions of “.facts” files using scripts. A full and deep understanding of the FACTS Platform Trial simulator is assumed.
1.1 IDs
There are number of parameters that IDs, such as “guid”, “SetId”, “qoi_id” … these are Microsoft “unique” identifiers, there should be no need to change these. It does not matter if the same Ids are used in successive “.facts” files, for instance if creating a range of sub-versions of a single original file.
1.2 Defaults
FACTS stores a super-set of the FACTS parameters in the “.facts” file - even storing parameters for the Dichotomous endpoint in a file for a Continuous design. There are so many parameters in the FACTS file that we cannot check the behavior of FACTS if some of these are missing, so our advice is to include *all* the parameters even if not required. The only parameters that it is clear can be omitted are those in the optional parameter sets: BaselineParameterSet and LongitudinalParameterSet that are not required if the respective features are not enabled.
1.3 Parameter Order
FACTS processes the parameters in the “.facts” file in the order in which the appear in the file. Some parameters depend on other parameters to have been already defined, so it is recommended that the order given here (the order FACTS itself uses when writing out the parameters) is retained. For many parameters changing their order should not be a problem, but we are not going to define, or guarantee, which those are.
2 The values in a “.facts” file
2.1 Numbers of items
D: The number of arms in the design
I: The number of milestones
LM: The number of longitudinal models
MT: The Maximum number of concurrent Treatments allowed in the trial.
PostQ: The number of Posterior Probability QOIs
PredQ: The number of Predictive Probability QOIs
PvQ: The number of p-value QOIs
R: The number of regions in an accrual profile
S: The number of scenarios
TQ: The number of target QOIs
V: The number of patient visits
Var: The number of variants
LM*V: This is the value used when a different prior is used at different visits. The values are stored as lists of lists (nested <item>s). The outer dimension is the number of LM and the inner dimension the number of visits. If the priors are common across all models, just the first lists of values for visits is used, the others are present but ignored.
2.2 Common structures
2.2.1 Gamma prior
The parameters are stored in a <gamma> value as <mu> – the central value of the prior, and <n> - the weight of the prior in equivalent number of observations. E.g.:
<gamma>
<mu>10</mu>
<n>1</n>
</gamma>2.2.2 Normal prior
The parameters are stored in a <meansdpair> value as <mean> - the mean of the prior and <sd> - the standard deviation. E.g.:
<meansdpair>
<mean>0</mean>
<sd>10</sd>
</meansdpair>2.2.3 Posterior probability QOI
The parameters stored in a <post_prob_qoi> structure are:
analysis_population: 0=all controls, 1=concurrent controls
condition: 3=greater than, 4=less than
tte_qoi_type: leave at 1 for non-tte endpoints
relation
is_absolute: “True” or “False”
comparison arm: id is_absolute=False, this is the name of the comparison arm, the name must appear as a name in the <dose_names> property.
delta: the value of the delta in the comparison
qoi_parametrization_type: 0=standard parametrization, 1=log-odds parametrization (dichotomous endpoint only), 2=hazard rate parametrization (TTE endpoint only).
alt_name: the short name for the QOI, the default QOIs have specific names, the user added QOIs have names of the form QOI_1_N for the nth posterior probability QOI
is_default_qoi: “True” or “False”, if the QOI is a default QOI its values should not be changed.
qoi_id: this is a Microsoft unique id, so that the QOI can be referenced from other parameters where the QOI is used.
Example:
<post_prob_qoi>
<analysis_population>0<\analysis_population>
<condition>3<\condition>
<tte_qoi_type>1<tte_qoi_type>
<relation>
<is_absolute>False</is_absolute>
<comparison_arm>Control</comparison_arm>
<delta>1</delta>
</relation>
<qoi_parametrization_type>0</qoi_parametrization_type>
<alt_name>Pr(CSD)</alt_name>
<is_default_qoi>True</is_default_qoi>
<qoi_id>ac13283c-dffc-47d6-9ba1-a371a633e626</qoi_id>
<\post_prob_qoi>2.2.4 Predictive probability QOI
The parameters stored in a <pred_prob_qoi> structure are:
analysis_population: 0=all controls, 1=concurrent controls
pred_prob_type: 1=Bayesian, 2=Conditional Power
phase: 2=Future trial
test_type: 1=superiority, 2=non-inferiority
subjects_per_arm: number of participants per arm
margin: Superiority/Non-inferiority margin
alpha: one-sided alpha
alt_name: the short name for the QOI, the default QOIs have specific names, the user added QOIs have names of the form QOI_2_N for the nth predictive probability QOI
is_default_qoi: “True” or “False”, if the QOI is a default QOI its values should not be changed.
qoi_id: this is a Microsoft unique id, so that the QOI can be referenced from other parameters where the QOI is used.
Example:
<pred_prob_qoi>
<analysis_population>0<\analysis_population>
<pred_prob_type>1</pred_prob_type>
<phase>2</phase>
<test_type>1</test_type>
<subjects_per_arm>250</subjects_per_arm>
<margin>0</margin>
<alpha>0.025</alpha>
<alt_name>Pr(SS)</alt_name>
<is_default_qoi>True</is_default_qoi>
<qoi_id>2556a9c6-7277-4437-865c-5e5b7d451634</qoi_id>
</pred_prob_qoi>2.2.5 P-value QOI
The parameters stored in a <pvalue_ qoi> structure are:
analysis_population: 0=all controls, 1=concurrent controls
pvalue_dropout_type: 0=LOCF, 2=Ignore
test_type: 1=Unadjusted
alt_name: the short name for the QOI, the default QOIs have specific names, the user added QOIs have names of the form QOI_3_N for the nth pvalue QOI
is_default_qoi: “True” or “False”, if the QOI is a default QOI its values should not be changed.
qoi_id: this is a Microsoft unique id, so that the QOI can be referenced from other parameters where the QOI is used.
Example:
<pvalue_qoi>
<analysis_population>1<\analysis_population>
<pvalue_dropouts_type>0</pvalue_dropouts_type>
<test_type>1</test_type>
<alt_name>QOI_3_2</alt_name>
<is_default_qoi>False</is_default_qoi>
<qoi_id>44ba7e29-da1f-4de8-913b-24aa0ed6b3c9</qoi_id>
</pvalue_qoi>2.2.6 Target Dose QOI
The parameters stored in a <target_dose_qoi> structure are:
target_type: 1=Max
tte_qoi_type: leave at 1 for non-tte endpoints
dose_combo_range_type: 0=All arms, 3=Active arms, 4=Randomizing arms
relation (MED & EDq target types only, present but empty for Max target type)
is_absolute: “True” or “False”
comparison arm: id is_absolute=False, this is the name of the comparison arm, the name must appear as a name in the <dose_names> property.
delta: the value of the delta in the comparison for MED, or the quantile for the EDq
alt_name: the short name for the QOI, the default QOIs have specific names, the user added QOIs have names of the form QOI_4_N for the nth target dose QOI
is_default_qoi: “True” or “False”, if the QOI is a default QOI its values should not be changed.
qoi_id: this is a Microsoft unique id, so that the QOI can be referenced from other parameters where the QOI is used.
Example:
<target_dose_qoi>
<target_type>1</target_type>
<tte_qoi_type>1</tte_qoi_type>
<dose_combo_range_type>0</dose_combo_range_type>
<relation />
<alt_name>Pr(Max)</alt_name>
<is_default_qoi>True</is_default_qoi>
<qoi_id>276464ff-0bfd-4509-b010-564a06e16d85</qoi_id>
</target_dose_qoi>2.2.7 Treatment Interim Criteria
The parameters stored in an <trt_interim_criteria> are
<trt_id>: the treatment ID of the treatment interim criteria. -1 for the criteria which should apply to all treatments.
<trt_name>: the name of the treatment pertaining to the interim criteria. “All Treatments” for the criteria which should apply to all treatments.
<interim_criteria> see below for details
2.2.8 Interim Criteria
The parameters stored in an <interim_criteria> are
interim_number: the number of the interim the criteria apply to, the number 32767 indicates the final success/futility criteria
<success_criteria> see below for details
<futility_criteria> see below for details
<graduation_criteria> see below for details
2.2.9 Success / Futility / Graduation Criteria
The parameters stored in a <success_criteria>, <futility_criteria> or <graduation_criteria> are:
is_enabled: True or False
list of one or more <stopping_criterion>, see below for details
is_and_condition: True if conditions are AND-ed together, False if conditions are OR-ed together
min_info_reqd: ignore. Set to 0.
2.2.10 Stopping Criterion
The parameters stored in a <stopping_criterion> structure are:
qoi_id: the id of the decision QOI being tested
condition: 3=greater than, 4=less than
threshold: the threshold the QOI is to be compared to
2.3 The values
| Tags | Parameter | Number of items | Default Value | Notes |
|---|---|---|---|---|
| <facts | version | 1 | the FACTS GUI version number | FACTS will not open “.facts” files with a higher version number. This test has/will be relaxed to only check the first 2 numbers in the version number. |
| guid | 1 | see general comment on id’s in section 1 | ||
| name | 1 | The name of the “.facts” file | Don’t make it different from the file name, bad things may happen | |
| host | 1 | |||
| <project-notes | CDATA | 1 | All text from the “Notes” text box | |
| </project-notes> | ||||
| < parameterSets | type | 1 | PTContDichParameterSet | Used for all FACTS Platform Trial parameters. Possible values: PTContDichParameterSet for the Continuous and Dichotomous endpoints. |
| <parameterSet | name | 1 | “pt_contdich” | Internal parameter set name |
| SetID | 1 | see general comment on id’s in section 1 | ||
| <property> | type | 1 | 1-3 | The Endpoint type for a given parameterSets type (PTContDichParameterSet, etc.) Possible values: 1 for Continuous and 2 for Dichotomous. |
| QOI Parameters | ||||
| <property> | qoi_parameter_set | |||
| <qoi_types> | ||||
| <post_prob_qois> | ||||
| <post_prob_qoi> | PostQ | 2 | This is a list of the Posterior Probability QOIs, see above for details. There is one default Posterior Probability QOI: Pr(PBO) | |
| </post_prob_qois> | ||||
| <pred_prob_qois> | ||||
| PredQ | 1 | This is the list of the Predictive Probability QOIs, see above for details. | ||
| <\pred_prob_qois> | ||||
| <pvalue_qois> | ||||
| PvQ | 0 | This is the list of the p-value QOIs, see above for details. There are no default p-value QOIs. | ||
| <\pvalue_qois> | ||||
| <target_doses_qoi> | ||||
| TQ | 1 | This is the list of the Target Dose QOIs, see above for details. There are one default Target Dose QOIs: Pr(Max) | ||
| <\target_doses_qoi> | ||||
| </qoi_types> | ||||
| <property> | adaptive_alloc_target_parameter_set | 1 per adaptive allocation targets | “” | If is_adaptive=1 and arm_drop=3 (adaptive allocation), this is a list of adaptive allocation targets |
| <adapt_alloc_target> | target_dose_id | 1 | The id of the target_dose_qoi or the string “static allocation” | |
| <relation> | weight_type_is_probability | 1 | True | True or False, if False weight type is “information” |
| weight | 1 | 1 | The relative weight of this target | |
| </property> | ||||
| <property> | is_adaptive | 1 | 0 | This is the “Enable adaptive features” option on the Trial Info tab. If the flag=1, then the Adaptive box is checked and adaptive options displayed. It needs to be set if adaptive features (interims, allocation) are being used. |
| <property> | alloc_info_type | 1 | 0 | This is the “Participant Information Defined By:” option: 0=Participants Enrolled, 1=Complete Data at Specified Visit, 2=Opportunity to Complete at Specified Visit. |
| <property> | Continuous_endpoint | 1 | 1 | This flag indicates the endpoint type 0=Dichotomous, 1=Continuous |
| <property> | is_longitudinal_enabled | 1 | 0 | Flag – 0=Don’t use longitudinal modelling, 1=Use longitudinal modelling NOTE: longitudinal modelling not used in Platform Trials 7.0, thus this value will always be 0. |
| </parameterSet> | ||||
| </parameterSets> | ||||
| Treatment Arms | Treatment Arms | |||
| <parameterSets | type | 1 | PTTreatmentArmsParameterSet | |
| <parameterSet | name | pt_treatment_arms | ||
| <property> | use_placebo | 1 | 1 | This flag corresponds to the “Include a control treatment arm” option on the Treatment Arms tab. 0=Don’t include, 1=Do include a control treatment arm. Should always be set to 1 in FACTS 7.0 |
| <property> | treatments_save | D | 0, 1 | An item list of identifiers of the trial arms. The length of this list defines ‘D’ the total number of arms in the trial. Control, if present, always has an identifier of ‘0’. If Control is not present, there should not be an arm with an identifier of ‘0’. |
| <property> | treatment_names | D | Control, Treatment 1 | An item list of the names of the trial arms |
| </parameterSet> | ||||
| </parametersets | ||||
| Interim Stopping Criteria | ||||
| <parameterSets | type | 1 | PTInterimStoppingCriteriaParameterSet | |
| <parameterSet | name | pt_interim_stopping_criteria | ||
| <property> | trt_interim_stopping_criterias | This comprises a <interims_criteria> which is a list of <interim_criteria> one per all treatments, per interim, and one per treatment, per interim, for which criteria have been defined. See details above. | ||
| </parameterSet> | ||||
| </parametersets | ||||
| Visit Parameters | Visit Parameters | |||
| <parameterSets | type | 1 | VisitInfoParameterSet | |
| <parameterSet> | name | visit_info | ||
| <property> | study_weeks | V | FUTURE If is_longitudinal_modeled=0 this is an empty <item /> list, if is_longitudinal_modeled=1, this is a list of items, one per visit, the value of each is the week of the visit. (As listed in the “Schedule of Post-Baseline Visits) NOTE In Platform Trial 7.0, longitudinal modeling is not used, thus this list will always be empty. |
|
| <property> | final_visit | 1 | 1 | FUTURE This is the week of the last visit, if is_longitudinal_modeled=1 this value should be the same as the last entry in the study_weeks list. NOTE In Platform Trial 7.0, longitudinal modeling is not used, thus this value will be the value of the final endpoint in weeks. |
| <property> | visit_names | V | FUTURE If is_longitudinal_modeled=0 this is a single entry <items> </items> list, with single entry: <item> Visit 1 </item>. if is_longitudinal_modeled=1, this is a list of items, one per visit, the value of each is the visit name. (As listed in the “Schedule of Post-Baseline Visits” on the Study Info tab) NOTE In Platform Trial 7.0, longitudinal modeling is not used, thus this list will always contain only 1 item, “Visit 1” |
|
| </parameterSet> | ||||
| </parameterSets> | ||||
| Study Info | Study Info | |||
| <parameterSets | type | 1 | PTContDichStudyInfoParameterSet | |
| <parameterSet | name | pt_contdich_study_info | ||
| <property> | use_max_accrual_time | 1 | 1 | A flag to indicate whether to use a maximum enrollment (accrual) time |
| <property> | max_accrual_time | 1 | 500 | The number of weeks for the maximum enrollment time in weeks |
| <property> | use_max_subjects | 1 | 0 | A flag to indicate whether to use a maximum number of participants |
| <property> | max_subjects | 1 | 300 | The maximum number of participants |
| <property> | use_max_number_of_successes | 1 | 0 | A flag to indicate whether to use a maximum number of successful treatments |
| <property> | max_number_of_successes | 1 | 2 | The maximum number of successful treatments |
| <property> | max_subjects_trt | 1 | 100 | The maximum number of participants per treatment |
| <property> | max_concurrrent_treatments | 1 | 4 | The maximum number of concurrent treatments |
| <property> | Is_noninferiority | 1 | 0 | Flag for the default QOIs, defining the trial type: 0=Superiority, 1=Non-inferiority. |
| <property> | include_baseline | 1 | 0 | An option for the Continuous endpoint. A flag to indicate whether including simulation of baseline: 0=Don’t simulate baseline, 1= Simulate baseline |
| <property> | is_change_from_baseline | 1 | 0 | An option for the Continuous endpoint, if simulating baseline. A flag to indicate whether response analyzed is absolute or change from baseline: 0=Change from baseline, 1= Final endpoint value |
| <property> | use_special_long | 1 | 0 | FUTURE: An option for the Dichotomous endpoint. A flag indicating if a special longitudinal feature is enabled: 0=None enabled, 1=One is enabled |
| <property> | special_long_feature | 1 | 0 | FUTURE: An option for the Dichotomous endpoint. If use_special_long=1, this flag indicates which special longitudinal feature is enabled: 0=Dichotomized continuous-valued response, 1=Restricted Markov |
| <property> | dichot_threshold_greater | 1 | 0 | FUTURE: An option for the Dichotomous endpoint. If use_special_long=1 AND special_long_feature=0, this flag indicates whether the response (“Y”) needs to be less than or greater than the threshold for the subject to be classed as a responder. 0=Less, 1=Greater. |
| <property> | dichot_threshold_value | 1 | 0 | FUTURE: An option for the Dichotomous endpoint. If use_special_long=1 AND special_long_feature=0, this value is the dichotomizing threshold value. |
| <property> | csd | 1 | 1/0.1 | Not used. |
| <property> | target_is_rel | 1 | 1 | Not used. |
| <property> | high_is_good | 1 | 1 | This flag corresponds to the “Higher/Lower response is improvement” selection on the Trial Info tab. 0=Lower, 1=Higher. If this is a Dichotomous endpoint design it corresponds to the equivalent “Response indicates positive/negative outcome” selection on the Trial Info tab. 0=negative, 1=positive |
| <property> | final_stable_success | 1 | 0 | FUTURE: An option for the Dichotomous endpoint. If use_special_long=1 AND special_long_feature=1, this flag indicates whether a subject whose final state is “stable” will be counted as a Responder or Failure, 0=Failure, 1=Responder |
| <property> | freq_noninferiority _delta | 1 | 0 | Not used. |
| <property> | freq_noninferiority _qoi_only | 1 | 1 | Not used. |
| <property> | use_fisher_exact | 1 | 0 | A flag for whether to use a Fisher exact test for p-value calculation, including current trial predictive probability QOIs. Only applies for a dichotomous endpoint. |
| <property> | should_succeed_threshold | 1 | 0 | Treatment effect threshold for classifying a simulated treatment as ‘Good’. If this treatment effect is greater than this value, the treatment is considered ‘Good’. |
| <property> | should_fail_threshold | 1 | 0 | Treatment effect threshold for classifying a simulated treatment as ‘Unacceptable’. If this treatment effect is less than this value, the treatment is considered to be ‘Unacceptable’. |
| <property> | trt_outcome_thesholds_spec | 1 | 0 | For dichotomous endpoint only. Specifies whether the simulated treatment classification thresholds are specified in rates or log-odds. 0=Rates, 1=Log-Odds |
| Variants | ||||
| <property> | has_variants | 1 | 0 | A flag to indicate if there are variants. |
| <property> | num_variants | 1 | 5 | if has_variants=1 this value is the number of variants |
| <property> | variant_names | Var | “Var 1”, “Var 2”, … | The names of the “variants” to be included in the scenario names to indicate which variant was being simulated. |
| <property> | var_max_subjects_trt | Var | 100, 100, … | The different values of max_subjects_trt to be used in each variant. |
| <property> | var_max_concurrent_treatments | Var | 4, 4, … | The different values of max_concurrent_treatments to be used in each variant. |
| </parameterSet> | ||||
| </parametersets | ||||
| Control Response Parameters | Control Response Parameters | |||
| <parameterSets> | type | 1 | PTControlResponseParameterSet | |
| <parameterSet | name | pt_control_response | ||
| <property> | historical_data_save | 1 | 0 | Always set to 0. |
| <property> | model_placebo_separately | 1 | 1 | Always set to 1. |
| <property> | control_prior | <meansd pair> | 0, 10 for Cont 0,2 for Dich |
If (model_placebo_separately=1 OR no_model_single_prior=0) AND historical_data_save=0, then these values are the Normal prior for the estimate for the treatment effect of the Control arm |
| <property> | concurrent_control_num_weeks | 1 | 0 | The number of weeks from treatment entering control for which to include subjects for the concurrent control comparison |
| <property> | concurrent_control_prior | <meansd pair> | 0,10 Cont 0,2 Dich |
These values are the Normal prior for the estimate for the treatment effect of the Concurrent control arms |
| </parameterSet> | ||||
| </parametersets | ||||
| Hierarchical Prior Parameters | Hierarchical Prior Parameters | |||
| <parameterSets> | type | 1 | HierarchicalPriorParameterSet | FUTURE USE: |
| <parameterSet | name | hierarchical_prior | ||
| <property> | bac_study_names | CS | “” | If historical_data_save=1, this is the list of study names for the hierarchical prior for control |
| <property> | hyperprior_mean | 1 | 0 | If historical_data_save=1, this value is the mean of the prior of the mean of the hierarchical model of the response on the control arm (μ0) |
| <property> | hyperprior_sd | 1 | 1 Cont 0.2 Dich |
If historical_data_save=1, this value is the SD of the prior of the mean of the hyperprior of the hierarchical model for the response on the control arm (μ0) |
| <property> | hyperprior_tau | <gamma> | 1, 1 | Contains the values for the inverse-gamma prior for the variance of the hyperprior of a hierarchical prior on Control (τ02). |
| <property> | ss_bac_study | CS | “” | If historical_data_save=1, this is the list of sample sizes for each study for the prior for control |
| <property> | cont_resp_bac_study | CS | “” | If historical_data_save=1, this is the list of mean responses for each study for the prior for control |
| <property> | dich_resp_bac_study | CS | “” | If historical_data_save=1, this is the list of response rates for each study for the prior for control |
| <property> | sd_bac_study | CS | “” | If historical_data_save=1, this is the list of SDs of the response for each study for the prior for control |
| </parameterSet> | ||||
| </parametersets | ||||
| Treatment Response Parameters | Treatment Response Parameters | |||
| <parameterSets> | type | 1 | PTTreatmentResponseParameterSet | |
| <parameterSet | name | pt_treatment_response | ||
| <property> | efficacy_model | 1 | 10 | A flag indicating the type of the treatment response model: 10=Independent Treatment Model – this is the only model available in the Platform Trial 7.0 simulator |
| <property> | no_model_single_prior | 1 | 1 | Flag indicating whether (if using the independent treatment model) the same prior applies to all study doses 1=Same prior, 0=Prior per treatment If flag=1 then the values for the prior for all treatments are stored in Init_treatment_prior If flag=0 then the prior values per study arm are stored in no_model_mean and no_model_sd |
| <property> | no_model_mean | D | 0,0,… | If no_model_single_prior=0, then these values are the mean of the Normal prior for the treatment effect for each treatment |
| <property> | no_model_sd | D | 10, 10, … Cont 2,2,… Dich |
If no_model_single_prior=0, then these values are the SD of the Normal prior for the treatment effect for each treatment |
| <property> | init_treatment_prior | <meansdpair> | 0, 10 Cont 0, 2 Dich |
If no_model_single_prior=1, then this value is the Normal prior for the estimate for the treatment effect for all treatments |
| <property> | prior_sigma | <gamma> | 10, 1 | A parameter for the Continuous endpoint. Contains the values for the inverse-gamma prior for ’sigma” the estimate of the SD of the endpoint. |
| <property> | dropout_imputation | 1 | 0 | Flag indicating how missing data due to dropout will be handled, 0=Bayesian multiple imputation post baseline, 1=Baseline carried forward, 2=Last observation carried forward |
| <property> | baseline_in_model | 1 | 0 | Flag indicating (if baseline is being simulated) if the treatment effect includes a baseline adjustment. 0=No baseline adjustment, 1=Use baseline adjusted model |
| <property> | baseline_beta | <meansdpair> | 0, 1 | The vales for the Normal prior for the estimate of the baseline coefficient |
| </parameterSet> | ||||
| </parametersets | ||||
| Longitudinal Model Parameters | Longitudinal Model Parameters | |||
| <parameterSets> | type | 1 | LongitudinalModelParameterSet1 | FUTURE USE: |
| <parameterSet | name | longitudinal_model | ||
| <property> | long_model_type | 1 | 3 | Flag that indicates the type of the longitudinal model. For a Continuous endpoint these are: 1=linear regression, 3=last observation carried forward, 4=time course hierarchical, 5=kernel density, 8=ITP For a Dichotomous endpoint: 2=Beta binomial 3=last observation carried forward, 7=Logistic regression |
| <property> | long_model_spec | 1 | 0 | This flag indicates the number of longitudinal model instances 0=Single model for all arms 1=Model control separately 2=Model comparator separately 3=Model control and comparator separately 4=Model all arms separately |
| <property> | long_prior_spec | 1 | 0 | This flag indicates the number of separate priors for the longitudinal model parameters 0=Same prior across all model instances and visits 1=Specify per visit, across all model instances 2=Specify priors per model instance and visit |
| <property> | long_alpha_mu | 1 | 0 | When long_prior_spec=0, contains the values for the mean of the Normal prior for the intercept of the linear regression, models (αt) to be used for all models This is the value used when the same prior is used across all model instances and visits. |
| <property> | long_alpha_mu_matrix | LM*V | 0, 0, … | When long_prior_spec=1 or 2, contains the values for the mean of the Normal prior for the intercept of the linear regression, models (αt) with different values for each visit, and possibly each model. See the description of LM*V parameters before this table. |
| <property> | long_alpha_stdv | When long_prior_spec=0, contains the values for the SD of the Normal prior for the intercept of the linear regression, models (αt) to be used for all models This is the value used when the same prior is used across all model instances and visits. |
||
| <property> | long_alpha_sd_matrix | When long_prior_spec=1 or 2, contains the values for the SD of the Normal prior for the intercept of the linear regression, models (αt) with different values for each visit, and possibly each model. See the description of LM*V parameters before this table. |
||
| <property> | long_beta_mu | When long_prior_spec=0, contains the values for the mean of the Normal prior for the slope of the linear regression, models (βt) to be used for all models This is the value used when the same prior is used across all model instances and visits. |
||
| <property> | long_beta_mu_matrix | When long_prior_spec=1 or 2, contains the values for the mean of the Normal prior for the slope of the linear regression, models (βt) with different values for each visit, and possibly each model. See the description of LM*V parameters before this table. |
||
| <property> | long_beta_stdv | When long_prior_spec=0, contains the values for the SD of the Normal prior for the slope of the linear regression, models (βt) to be used for all models This is the value used when the same prior is used across all model instances and visits. |
||
| <property> | long_beta_sd_matrix | When long_prior_spec=1 or 2, contains the values for the SD of the Normal prior for the slope of the linear regression, models (βt) with different values for each visit, and possibly each model. See the description of LM*V parameters before this table. |
||
| <property> | tch_tau | <gamma>*LM | 0.5, 1 | Contains the values for the inverse-gamma prior for the variance of the inter-subject error term (δi) of the Time Course Hierarchical longitudinal model (τ2). The number of prior values depends on the number of longitudinal models, even if the same priors are used across all models. In which case the first values are used for all models. |
| <property> | tch_alpha | <meansdpair>*LM*V | 0, 2, … | Whether long_prior_spec=0 or 2, these are the priors for the αt parameter in the Time Course Hierarchical longitudinal model. αt is the log of the fraction of the final response seen at visit t. Unlike other LMs there always separate prior values for each visit. If long_prior_spec=0 only the values for the first model in the list are set. See the description of LM*V parameters before this table. |
| <property> | itp_k | <meansdpair>*LM | 1,1 | Contains the values for the Normal prior for the ITP shape parameter (k) of the ITP longitudinal model. The number of prior values depends on the number of longitudinal models, even if the same priors are used across all models. In which case the first values are used for all models. |
| <property> | itp_tau | <gamma>*LM | 1,1 | Contains the values for the inverse-gamma prior for the variance of the inter-subject error term (si) (subject specific random effect) of the ITP longitudinal model (τ2). The number of prior values depends on the number of longitudinal models, even if the same priors are used across all models. In which case the first values are used for all models. |
| <property> | itp_omega | <meansdpair>*LM | 1,1 | Contains the values for the Normal prior for the mean final response of the ITP longitudinal model. The number of prior values depends on the number of longitudinal models, even if the same priors are used across all models. In which case the first values are used for all models. |
| <property> | long_lambda_single | <gamma> | 0.5, 1 | Contains the values for the inverse-gamma prior for the variance of the residual error of the linear regression, time course hierarchical and ITP longitudinal models (λ2). This is the value used when the same prior is used across all model instances and visits. |
| <property> | long_lambda_list | <gamma>*LM | 0.5, 1 | Contains the values for the inverse-gamma prior for the variance of the residual error of the time course hierarchical and ITP longitudinal models (λ2). This is the value used when a different prior is used across all model instances. These models do not have separate estimates of this parameter per visit, unlike the linear regression… |
| <property> | long_lambda_matrix | <gamma>*LM*V | 0.5, 1 | Contains the values for the inverse-gamma prior for the variance of the residual error of the linear regression longitudinal model (λ2). See the description of LM*V parameters before this table. |
| <property> | kernel_bandwidth | LM | 2 | This is the value of the kernel bandwidth parameter for the Kernel Density longitudinal model. The value is a list of items - one for each LM model. If long_prior_spec=0, and there are multiple models, just the first value in the list is used, even though entries for the other models are present. |
| <property> | kernel_min_subj | LM | 6 | This is the value of the “minimum number of subjects before using” parameter for the Kernel Density longitudinal model. The value is a list of items - one for each LM model. If long_prior_spec=0, and there are multiple models, just the first value in the list is used, even though entries for the other models are present. |
| <property> | kernel_sd | LM | 2 | This is the value of the “standard deviation of the prior mean” parameter for the Kernel Density longitudinal model. The value is a list of items - one for each LM model. If long_prior_spec=0, and there are multiple models, just the first value in the list is used, even though entries for the other models are present. |
| <property> | bb_alpha_mu_1 | 1 | 1 | When long_prior_spec=0, this is the single prior for the αμ1 parameter for the Beta Binomial prior for the probability that a subject with a response at a visit will have a response at the final visit – for all models and all visits. |
| <property> | bb_alpha_mu_1_full | LM*V | 1, 1, … | When long_prior_spec=1 or 2, these are the priors for the αμ1 parameter for the Beta Binomial prior for the probability that a subject with a response at a visit will have a response at the final visit across the different visits or models and visits. See the description of LM*V parameters before this table. |
| <property> | bb_beta_mu_1 | 1 | 1 | When long_prior_spec=0, this is the single prior for the βμ1 parameter for the Beta Binomial prior for the probability that a subject with a response at a visit will have a response at the final visit – for all models and all visits. |
| <property> | bb_beta_mu_1_full | LM*V | 1, 1, … | When long_prior_spec=1 or 2, these are the priors for the βμ1 parameter for the Beta Binomial prior for the probability that a subject with a response at a visit will have a response at the final visit across the different visits or models and visits. See the description of LM*V parameters before this table. |
| <property> | bb_alpha_mu_0 | 1 | 1 | When long_prior_spec=0, this is the single prior for the αμ0 parameter for the Beta Binomial prior for the probability that a subject without a response at a visit will have a response at the final visit – for all models and all visits. |
| <property> | bb_alpha_mu_0_full | LM*v | 1, 1, … | When long_prior_spec=1 or 2, these are the priors for the αμ0 parameter for the Beta Binomial prior for the probability that a subject without a response at a visit will have a response at the final visit across the different visits or models and visits. See the description of LM*V parameters before this table. |
| <property> | bb_beta_mu_0 | 1 | 1 | When long_prior_spec=0, this is the single prior for the βμ0 parameter for the Beta Binomial prior for the probability that a subject without a response at a visit will have a response at the final visit – for all models and all visits. |
| <property> | bb_beta_mu_0_full | LM*V | 1, 1, … | When long_prior_spec=1 or 2, these are the priors for theβμ0 parameter for the Beta Binomial prior for the probability that a subject without a response at a visit will have a response at the final visit across the different visits or models and visits. See the description of LM*V parameters before this table. |
| <property> | long_rmm_alpha_0 | LM*V | 1, 1, … | Whether long_prior_spec=0 or 2, these are the priors for the α0 parameter for the Dirichlet prior in the Restricted Markov Model, for the probability that stable subject will be a fail at the final visit across the different visits. Unlike other LMs there always separate prior values for each visit. If long_prior_spec=0 only the values for the first model in the list are set. See the description of LM*V parameters before this table. |
| <property> | long_rmm_alpha_S | LM*V | 1, 1, … | Whether long_prior_spec=0 or 2, these are the priors for the α0 parameter for the Dirichlet prior in the Restricted Markov Model, for the probability that stable subject will be stable at the final visit across the different visits. Unlike other LMs there always separate prior values for each visit. If long_prior_spec=0 only the values for the first model in the list are set. See the description of LM*V parameters before this table |
| <property> | long_rmm_alpha_1 | LM*V | 1, 1, … | Whether long_prior_spec=0 or 2, these are the priors for the α0 parameter for the Dirichlet prior in the Restricted Markov Model, for the probability that stable subject will be respnder at the final visit across the different visits. Unlike other LMs there always separate prior values for each visit. If long_prior_spec=0 only the values for the first model in the list are set. See the description of LM*V parameters before this table |
| <property> | lr_mu_1 | 1 | 0.5 | When long_prior_spec=0, this is the single prior for the μ1 parameter for the Normal prior in the Logistic Regression longitudinal model, for the logit of the probability that a subject with a response at a visit will have a response at the final visit – for all models and all visits. |
| <property> | lr_mu_1_matrix | LM*V | 0.5, 0.5 | When long_prior_spec=1 or 2, these are the priors for the μ1 parameters for the Normal prior in the Logistic Regression longitudinal model, for the logit of the probability that a subject with a response at a visit will have a response at the final visit across the different visits or models and visits. See the description of LM*V parameters before this table. |
| <property> | lr_mu_0 | 1 | 0.5 | When long_prior_spec=0, this is the single prior for the μ0 parameter for the Normal prior in the Logistic Regression longitudinal model, for the logit of the probability that a subject without a response at a visit will have a response at the final visit – for all models and all visits. |
| <property> | lr_mu_0_matrix | LM*V | 0.5, 0.5 | When long_prior_spec=1 or 2, these are the priors for the μ0 parameters for the Normal prior in the Logistic Regression longitudinal model, for the logit of the probability that a subject without a response at a visit will have a response at the final visit across the different visits or models and visits. See the description of LM*V parameters before this table. |
| <property> | lr_sd_1 | 1 | 0.5 | When long_prior_spec=0, this is the single prior for the σ1 parameter for the Normal prior in the Logistic Regression longitudinal model, for the logit of the probability that a subject with a response at a visit will have a response at the final visit – for all models and all visits. |
| <property> | lr_sd_1_matrix | LM*V | 0.5, 0.5 | When long_prior_spec=1 or 2, these are the priors for the σ1 parameters for the Normal prior in the Logistic Regression longitudinal model, for the logit of the probability that a subject with a response at a visit will have a response at the final visit across the different visits or models and visits. See the description of LM*V parameters before this table. |
| <property> | lr_sd_0 | 1 | 0.5 | When long_prior_spec=0, this is the single prior for the σ0 parameter for the Normal prior in the Logistic Regression longitudinal model, for the logit of the probability that a subject without a response at a visit will have a response at the final visit – for all models and all visits. |
| <property> | lr_sd_0_matrix | LM*V | 0.5, 0.5 | When long_prior_spec=1 or 2, these are the priors for the σ0 parameters for the Normal prior in the Logistic Regression longitudinal model, for the logit of the probability that a subject without a response at a visit will have a response at the final visit across the different visits or models and visits. See the description of LM*V parameters before this table. |
| <property> | ||||
| </parameterSet> | ||||
| </parametersets | ||||
| Allocation Parameters | Allocation Parameters | |||
| <parameterSets> | type | 1 | PTAllocationParameterSet | |
| <parameterSet | name | pt_allocation_data | ||
| <property> | arm_drop | 1 | 1 | If is_adaptive=1 then this flag (despite its name) actually indicates the type of allocation to be used: 2=fixed allocation 3=adaptive allocation |
| <property> | alloc_by_numtrt_style | 1 | 1 | A flag to indicate the Allocation Options: 0 = Constant proportion allocated to control 1 = Allocation dependent on number of treatments |
| <property> | alloc_constantratio_treatment | 1 | 6 | The number of participants to allocate to treatments per sub-block |
| <property> | alloc_constantratio_control | 1 | 2 | The number of participants to allocate to control per sub-block |
| <property> | alloc_block_bytrt_treatment | MT | If alloc_by_numtrt_style = 1, these values are the allocation to each treatment depending on the current number of treatments in the trial | |
| <property> | alloc_block_bytrt_control_fixed | MT | If alloc_by_numtrt_style = 1, these values are the allocation to control depending on the current number of treatments in the trial | |
| <property> | alloc_block_bytrt_for_RAR | MT | if is_adaptive=1 and alloc_by_numtrt_style = 2, these values are the slots allocated adaptively depending on the current number of treatments in the trial | |
| <property> | alloc_block_bytrt_control_for_RAR | MT | if is_adaptive=1 and alloc_by_numtrt_style = 2, these values are the allocation to control depending on the current number of treatments in the trial | |
| <property> | num_subj_alloc_new_treat_before_adaptive | 1 | if is_adaptive=1 and arm_drop = 3, this is the number of subjects allocated to a new treatment before being included in adaptive randomization | |
| <property> | min_alloc_prob | 1 | 0 | if is_adaptive=1 and arm_drop=0 or 3 (adaptive allocation), this is the floor probability for allocation, if an arm has less than this probability of allocation its probability is set to zero and the probabilities |
| <property> | static_alloc | D | 0, 1, 1,… | if is_adaptive=1 and arm_drop=3 (adaptive allocation) and if the adaptive allocation includes some static allocation this list is the static weights to each arm |
| <property> | rr_power | 1 | 1 | if is_adaptive=1 and arm_drop=3 (adaptive allocation) this is the power to raise the allocation probabilities by |
| </parameterSet> | ||||
| </parametersets | ||||
| Trial Updates Parameters | Trial Updates Parameters | |||
| <parameterSets> | type | 1 | PTInterimsParameterSet | |
| <parameterSet | name | pt_interims_data | ||
| <property> | interims_only_at_trt_milestones | 1 | 0 | A flag indicating whether updates occur only when a treatment milestone is met. If arm_drop = 3, this value should be set to 0, otherwise 0 or 1 are valid options |
| <property> | arms_enter_trial_between_updates | 1 | 0 | A flag indicating whether treatments can enter the trial between updates. |
| <property> | first_alloc_update_type | 1 | 0 | A flag indicating whether the first update is specified by time or information 0 = Time 1 = Information |
| <property> | subsequent_alloc_update_type | 1 | 0 | A flag indicating whether subsequent updates are specified by time or information 0 = Time 1 = Information |
| <property> | global_first_update_tim | 1 | 4 | If first_alloc_update_type = 0, this is the number of weeks for the first update |
| <property> | global_interval_time | 1 | 4 | If subsequent_alloc_update_type = 0, this is the number of weeks between each subsequent update |
| <property> | always_evaluate_milestones | 1 | 1 | A flag to indicate whether to evaluate milestone criteria at each update, or only when milestone first reached 0 = Evaluate milestone criteria when milestone first reached 1 = Evaluate milestone criteria at each update |
| <property> | update_subjects | I | 1, … | If updates are defined by the amount of information, these values are the number of participants enrolled / complete / opportunity to complete at each update |
| <property> | treatment_milestones_visits | I | ““,”“, | By default blank but if participant information is defined by “Complete Data at Specified Visit” or “Opportunity to Complete at Specified Visit, this is the visit number of the information |
| <property> | first_single_burnin_new | 1 | 100 | If first_alloc_update_type = 1, this is the number of participants required for the first update to be triggered |
| <property> | global_first_update_visit | 1 | 1 | If first_alloc_update_type = 1, this is the Visit number for the update |
| <property> | subsequent_single_burnin_new | 1 | 1 | If subsequent_alloc_update_type = 1, this is the number of participants before the update occurs passed the first update |
| <property> | global_interval_visit | 1 | If subsequent_alloc_update_type = 0, this is the Visit number for the update | |
| <property> | continue_follow_success | 1 | 1 | A flag indicating whether follow-up will continue if treatment stops for success |
| <property> | continue_follow_futility | 1 | 1 | A flag indicating whether follow-up will continue if treatment stops for futility |
| </parameterSet> | ||||
| </parametersets | ||||
| Dropout Parameters | Dropout Parameters | |||
| <parameterSets> | type | 1 | DropoutParameterSet | |
| <parameterSet | name | <Profile name> | The name of the dropout profile | |
| SetID | see general comment on id’s in section 1 | |||
| <property> | is_stage_two_data | 1 | 0 | Future: flag used to indicate that (if=1) the profile is to be used in stage 2 of a staged design |
| <property> | enable_per_visit_dropouts | 1 | 1 | A flag to indicate the type of dropout: 0 = No Dropouts 1 = Dropouts Per Arm |
| <property> | dropout_rate | D | 0, … | The probability of dropping out, per Treatment |
| <property> | visit_dropout_rate | D | 0, … | FUTURE: The dropouts per Treatment |
| <property> | use_common_dropout_profile | 1 | 1 | Not used. |
| </parameterSet> | ||||
| </parametersets | ||||
| Treatment Arrival Parameters | Treatment Arrival Parameters | |||
| <parameterSets> | type | 1 | PTTreatmentArrivalParameterSet | |
| <parameterSet | name | <Profile name> | The name of the arrival profile | |
| SetID | see general comment on id’s in section | |||
| <property> | treatment_available_from_weeks_gui | D | 0, 1, … | A list, per Treatment, of the earliest a treatment can enter the trial, in weeks |
| <property> | treatment_date_delta_weeks_gui | D | 0, 1, … | A list, per Treatment, of the latest a treatment can enter the trial, in weeks. |
| <property> | treatment_max_wait_time_weeks_gui | D | 0, 1, … | A list, per Treatment, of the number of weeks before a Treatment will be withdrawn from the trial if not used |
| </parameterSet> | ||||
| </parametersets | ||||
| Treatment Distribution Parameters | Treatment Distribution Parameters | |||
| <parameterSets> | type | 1 | PTTreatmentDistributionParameterSet | |
| <parameterSet | name | <Profile name> | The name of the treatment distribution profile | |
| SetID | see general comment on id’s in section | |||
| <property> | treatment_sampling_type_option | 1 | 1 | A flag indicating whether the Treatment Sampled Mean is Response or Effect 0 = Response / Response rate if dichotomous 1 = Effect 2 = Response (Log-Odds) – Dichotomous only 3 = Effect (Log-Odds) – Dichotomous only |
| <property> | treatment_prob_same_as_control | 1 | 0.5 | If treatment_sampling_type_options = 1 or 3, this is the probability effect size relative to control. If treatment_sampling_type_options = 0 or 2, this is the probability the response / response rate is the same as control. |
| <property> | treatment_distribution_type | 1 | 0 Cont 5 Dich |
The distribution type: 0 = Normal 2 = Truncated Normal 5 = Beta |
| <property> | treatment_normal_dist_prior | <meansd pari> | 0,10 Cont 0,2 Dich |
If treatment_distribution_type = 0, then these values are the Normal prior for the estimate for the response/effect of the treatment |
| <property> | treatment_truncated_normal_dist_min | 1 | 0 | If treatment_distribution_type = 2, then this value is the minimum value for the distribution. |
| <property> | treatment_truncated_normal_dist_max | 1 | 1 | If treatment_distribution_type = 2, then this value is the minimum value for the distribution. |
| <property> | treatment_beta_dist_prior_mean | 1 | 0.5 | If treatment_distribution_type = 5, then this value is the beta prior men for the estimate for the response/effect of the treatment |
| <property> | Treatment_beta_dist_prior_sd | 1 | 0.289 | If treatment_distribution_type = 5, then this value is the beta prior standard deviation for the estimate for the response/effect of the treatment |
| <property> | treatment_beta_dist_min | 1 | 0 | If treatment_distribution_type = 5, then this value is the minimum value for the beta distribution |
| <property> | treatment_beta_dist_max | 1 | 1 | If treatment_distribution_type = 5, then this value is the maximum value for the beta distribution |
| </parameterSet> | ||||
| </parametersets | ||||
| Efficacy Parameters | Efficacy Parameters | |||
| <parameterSets> | type | 1 | PTEfficacyParameterSet | The collection of treatment response profiles |
| <parameterSet | name | <Profile name> | The name of the treatment response profile | |
| SetID | see general comment on id’s in section | |||
| <property> | true_endpoint_response | D | 0 | This is the simulated mean change from baseline for each treatment |
| <property> | enable_per_dose_sigma | 1 | 0 | This flag indicates whether 0: there is just one value for sigma used for all treatments or 1: a value for sigma has been supplied for each treatment |
| <property> | true_sigma_save | 1 | 10 | The single value for sigma (used when enable_per_dose_sigma=0) |
| <property> | true_sigma_per_dose_save | D | 10 | A list of values for sigma, one per treatment (use when enable_per_dose_sigma=1) |
| <property> | true_response_rate | D | 0.5 | Used in the Dichotomous endpoint response simulation method |
| <property> | treatment_distribution_profile_guids | D | Guid | If the value in the list is a GUID, the value is a pointer to the same GUID found in the SetID in the Distribution profiles (PTTreatmentDistributionParameterSet), else: -1 = Fixed Mean Response -2 = Fixed Mean Effect -3 = Sampled |
| <property> | Longitudinal_profile_guid | D | Guid | If the value in the list is a GUID, the value is a pointer to the same GUID found in the SetID in the Distribution profiles (LongitudinalModelParameterSet1), else: -1 = Fixed Mean Response -2 = Fixed Mean Effect -3 = Sampled |
| <property> | control_distribution_type | 1 | 0 Cont 5 Dich |
The distribution type for control. Control does not use distribution, thus this value is always 0 |
| <property> | control_normal_dist_prior | <meansd pair> | 0, 10 Cont 0, 2 Dich |
The mean and sd values for the prior for the normal distribution for control. Control does not use distribution, this this value is always 0, 10 |
| <property> | control_truncated_normal_dist_min | 1 | 0 | If treatment_distribution_type = 2, then this value is the minimum value for the distribution for control |
| <property> | control_truncated_normal_dist_max | 1 | If treatment_distribution_type = 2, then this value is the maximum value for the distribution for control | |
| <property> | control_beta_dist_prior_mean | 1 | 0 | If treatment_distribution_type = 5, then this value is the beta prior men for the estimate for the response/effect of the control |
| <property> | control_beta_dist_prior_sd | 1 | 10 | If treatment_distribution_type = 5, then this value is the beta prior men for the estimate for the response/effect of the control |
| </parameterSet> | control_beta_dist_min | 1 | If treatment_distribution_type = 5, then this value is the minimum value for the beta distribution for control | |
| Recruitment Parameters | control_beta_dist_max | 1 | If treatment_distribution_type = 5, then this value is the maximum value for the beta distribution for control | |
| <parameterSets> | ||||
| <parameterSet | Recruitment Parameters | |||
| type | 1 | PTRecruitmentParameterSet | ||
| <property> | name | <Profile name> | The name of the recruitment profile | |
| <property> | SetID | see general comment on id’s in section | ||
| <property> | location_names | R=number of profiles in accrual profile | <rRegion_Name> | The name of the regions – with an entry (<item>) for each region. All properties in this profile should have the same number of items. |
| <property> | recruit_rates | R | 5 | The peak mean accrual rate per region |
| <property> | start_dates | R | 0 | The start date (in weeks from the start of the trial) of accrual per region |
| <property> | ramp_up | R | 0 | A flag per region indicating if there is an initial ramp up stage (0= no ramp up, 1=ramp up) |
| <property> | peak_start | R | Include but leave blank if no ramp up. A per region value of the end (in weeks from the start of the trial) of ramp up in that region | |
| <property> | ramp_down | R | 0 | A flag per region indicating if there is a ramp down stage (0= no ramp down, 1=ramp down) |
| </parameterSet> | start_day | R | 0 | A flag per region indicating if there is a ramp down stage (0= no ramp down, 1=ramp down) |
| </parametersets | last_day | R | Include but leave blank if no ramp down. A per region value of the start (in weeks – despite the parameter name - from the start of the trial) of ramp down in that region | |
| Baseline Parameters | ||||
| <parameterSets> | ||||
| <parameterSet | Baseline Parameters | |||
| type | 1 | BaselineParameterSet | ||
| <property> | name | <Profile name> | The name of the baseline profile | |
| <property> | SetID | see general comment on id’s in section | ||
| <property> | baseline_vsr_mean | 1 | 0 | The baseline mean |
| <property> | baseline_vsr_sd | 1 | 1 | The SD of the baseline |
| <property> | constrain_lower | 1 | 0 | Flag to indicate if the lower bound of the baseline is constrained 0: Not constrained, 1: Constrained |
| <property> | constrain_upper | 1 | 0 | Flag to indicate if the upper bound of the baseline is constrained 0: Not constrained, 1: Constrained |
| <property> | lower_bound | 1 | 0 | The lower bound on the baseline score if it is constrained. |
| <property> | upper_bound | 1 | 0 | The upper bound on the baseline score if it is constrained |
| <property> | baseline_adj | 1 | 0 | Flag to indicate if the subjects final response is to be adjusted for baseline, 0: No adjustment, 1: Adjusted |
| <property> | baseline_beta_adj | 1 | 1 | The value for “Beta” the coefficient of the adjustment |
| </parameterSet> | baseline_vsr_center | 1 | 0 | The centering value for the adjustment |
| </parametersets> | baseline_vsr_scane | 1 | 1 | The scaling value for the adjustment |
| Simulation Settings | ||||
| <simulation-settings | ||||
| <property> | Simulation Settings | |||
| <property> | ||||
| <property> | num_sims | 1 | 5 | The number of simulations to run |
| <property> | burn | 1 | 1000 | The number of iterations of the MCMC loop that are initially ignored before sampling starts |
| <property> | length | 1 | 2500 | The number of iterations of the MCMC loop used to estimate the parameters |
| <property> | rv_seed_1 | 1 | 3500 | The first part (32 bits) of the random number seed for all simulations. |
| <property> | rv_seed_2 | 1 | 1 | The second part (32 bits) of the random number seed for all simulations. |
| <property> | num_weeks_out | 1 | 100 | The number of simulations which will have their interim analysis results written out to file. |
| <property> | num_freq_weeks_out | 1 | 1 | The number of simulations which will have their interim frequentist analysis results written out to file. |
| <property> | num_subj_out | 1 | 1 | The number of simulations which will have their participant data written out to file. |
| <property> | num_mcmc_files | 1 | 0 | The number of simulations which will have their MCMC samples written out to file. |
| <property> | mcmc_thin | 1 | 1 | This is the factor by which the MCMC samples are thinned *when writing out the MCMC file*, it does not thin the samples used within FACTS. There is no option to thin the sampling within FACTS. |
| </simulation-settings> | mcmc_per_imputation | 1 | 1 | The number of MCMC samples between each imputation of missing data using the longitudinal model |
| is_local | 1 | 1 | Flag specifying where FACTS simulations are performed. 0=grid, 1=locally | |
| <setup-simulation-settings> | ||||
| … | The setup-simulation-settings record the simulation settings in force for each scenario at the time of its simulation. This is used by the FACTS GUI to determine if the simulation results are out-of-date. | |||
| </setup-simulation-settings> | Name | S | The name of the scenario | |
| </facts> | The same properties as in the simulation-settings. | |||