In this section Hide
You can view run details in any of the following ways:
Different information appears for MGPS runs and LR runs.
The Detail for Run dialog box provides the following information about an MGPS run:
Field |
Description |
ID |
Automatically assigned, unique numeric identifier of the run. |
Type |
MGPS. |
Name |
Name supplied for the run. |
Description |
Description supplied for the run. |
Project |
The name of the project to which the run is assigned. |
Configuration |
Name of the data configuration used for the run. |
Configuration description |
Description of the configuration used for the run. |
As of date |
As Of date for the run, if the run is for timestamped data. |
Database restriction |
Database restriction, if any, associated with the run. |
Item variables |
Names of the item variables used in the run. |
Custom terms |
Custom terms, if any, specified for the run. |
Stratification variables |
Stratification variables, if any, used for the run. |
Subsets |
Subset variable, if any, as well as whether the subsets are cumulative, the order of subsets (if cumulative), and the subset labels and values. |
Drug Hierarchy |
If the data configuration specifies a drug hierarchy, the name and version of the drug hierarchy used by this run. |
Event Hierarchy |
If the data configuration specifies an event hierarchy, the name and version of the event hierarchy used by this run. |
Highest dimension |
The maximum number of ways in which items are combined. See Specifying data mining parameters. |
Minimum count |
Minimum number of cases in which a combination of items must occur for the combination to be included in the MGPS computations for the run. See Specifying data mining parameters. |
Calculate PRR |
Whether the run includes PRR computations. |
Calculate ROR |
Whether the run includes ROR computations. |
Base counts on cases |
For a run that includes PRR and ROR computations, indicates if counts are based on cases rather than drug-event combinations. |
Use "all drugs" comparator |
For a run that includes PRR computations, whether or not the comparator set includes the drug of interest. |
Apply Yates correction |
For a run that includes PRR computations, whether or not the Yates correction is applied. |
Stratify PRR and ROR |
For a run that includes PRR and ROR computations, whether or not the PRR or ROR computations are stratified. |
Include IC |
Whether the run includes Information Component computations. |
Include RGPS |
Whether the run includes RGPS computations. |
Calculate RGPS interactions |
Whether the run computes Drug+Drug interaction scores using RGPS. |
Minimum interaction count |
Minimum number of times that a drug must appear in Drug+Event reports for the application to calculate interaction estimates for the drug. |
Fill in hierarchy values |
Indicates whether the run option to use hierarchy information was checked. |
Limit results to |
Limitations on which results are kept based on statistical thresholds or specified values of item variables. See Specifying data mining parameters. |
Exclude single itemtypes |
Indicates whether combinations of items of the same type were excluded from run results. See Specifying data mining parameters. |
Fit separate distributions |
Indicates the setting for the advanced parameter to fit separate distributions for the different item type combinations. |
Save intermediate files |
Whether or not intermediate processing files for the run were saved. See Defining data mining run options. |
Created by |
Name of the user who created the run. |
Created on |
Date and time at which the run was submitted. |
User |
Your username (name of the user who is viewing run details). |
Source database |
Information about the source data (from the source description table). |
The Detail for Run dialog box provides the following information about a logistic regression run:
Field |
Description |
ID |
Automatically assigned, unique numeric identifier of the run. |
Type |
LR. For runs completed prior to the installation of Empirica Signal version 7.1, LR (Legacy) appears. |
Name |
Name supplied for the run. |
Description |
Description supplied for the run. |
Project |
The name of the project to which the run is assigned. |
LR type |
The logistic regression used for the run, either extended or standard. |
Configuration |
Name of the data configuration used for the run. |
Configuration description |
Description of the data configuration used for the run. |
As of date |
If the run is for timestamped data, As Of date for the run. |
Database restriction |
Database restriction, if any, associated with the run. |
Item variables |
Names of the selected event and drug variables. |
Custom terms |
Custom terms, if any, specified for the run. |
Covariates |
Variables, if any, selected as covariates for the run. |
Drug values |
Explicitly specified values of the drug variable included in the run, even if they do not meet the minimum number of times a drug must occur in combination with specified events. |
Event values |
Values of the event variable used in the run. |
Minimum count |
Minimum number of cases in which a drug must occur in combination with specified events to be included in the run (except for drugs explicitly specified as Drug values). See Specifying drugs for logistic regression. |
Run interactions |
Whether or not the run calculates statistics for two predictors (such as drug+drug or drug+covariate) and a response. |
Save coefficients |
Whether or not the lr_coefficients.log file produced for the run includes the coefficient and standard deviation values calculated for the run. |
Save intermediate files |
Whether or not intermediate processing files for the run were saved. See Defining data mining run options. |
Created by |
Name of the user who created the run. |
Created on |
Date and time at which the run was submitted. |
User |
Your username (name of the user who is viewing run details). |
Source database |
Information about the source data (from the source description table). |