MicroStrategy ONE

Creating predictive metrics

Predictive metrics allow the results of predictive analysis to be applied to new datasets by executing MicroStrategy reports. You can create these metrics in a number of ways; procedures for these methods follow.

When using either method, it is recommended that you disable report caching for all training reports to insure that the PMML model is always generated. If the report is in the report cache, MicroStrategy does not need to execute the training metric, since the results have already been cached. Therefore, the PMML model is not refreshed, and reflects the state of the training dataset at the time the report was last executed. For more information on report caching, see Report Caching Options dialog box.

If the report includes derived training metrics, these derived training metrics are moved off the report's template, which determines what is displayed for the report. The derived training metrics are still available in the Report Objects of the report, which supplies the definition of the report. Additionally, the derived predictive metrics that are created based on the derived training metrics are included on the report template. If you update the derived training metrics and need to re-create their associated derived predictive metrics, you must add the derived training metrics back to the template of the report.

Automatic creation

Automatic creation of predictive metrics allows you to create predictive metrics quickly and easily from your training metrics.

  1. Using the Training Metric Wizard, create a training metric with the option Automatically create on report execution checked.

  2. Add the training metric to a report or document. This can either be an existing dataset report or new report which contains only the training metric.

    Ensure that the training metric is on the grid of the report. If the training metric is only in the Report Objects but not on the report grid, no predictive metrics are created for the training metric.

  3. Run the report using any of the following techniques:

    • In MicroStrategy Developer, browse to the report and run the report or document. For example, you can right-click the report or document and select Run.

    • If you have reports or documents sent to your History List, you can run the reports or documents by opening them in your History List.

    • Create a cache update subscription for the report or document. Whenever the schedule for the subscription is triggered, the report or document is run. For information on creating cache update subscriptions for reports or documents, see the System Administration Help.

    • The predictive metrics are created, in the location specified by the training metric.

      If you are using derived predictive training metrics and have selected to save the derived predictive metrics to the Report Objects, these derived predictive metrics are created in the following ways:

    • When a report is executed to create predictive metrics, the following occurs:

    • The derived training metrics are moved off the report's template; the template determines what is displayed for the report. The derived training metrics are still available in the Report Objects of the report, which supplies the definition of the report. If you update the derived training metrics and need to re-create their associated derived predictive metrics, you must add the derived training metrics back to the template of the report. When the derived predictive metrics are re-created, new versions are created to keep a history of the predictive modeling.

    • Any derived training metrics that are moved off the report's template during report execution are replaced with the first predictive metric selected to be generated. When the derived training metric is initially replaced with the derived predictive metric, the values are not automatically updated to reflect the predictive metric analysis. Re-execute the report to update the values for the derived predictive metric.

    • All other predictive metrics selected to be generated are added to the Report Objects and are not on the report grid by default. This makes the predictive model available for viewing only. To execute the derived predictive metric, you must add the derived predictive metric to the grid of the report.

    • When a document including the report as a Grid/Graph is executed to create predictive metrics, the following occurs:

    • All predictive metrics are added to the available dataset objects for the report and are not included on the report grid by default. These predictive metrics are not saved in the report itself and are only available with the report as a dataset in the current document. This makes the predictive model available for viewing only. To execute the derived predictive metrics, you must add the derived predictive metrics to the grid of the report or directly to a section within the document.

Manual creation

Manually creating predictive metrics gives you more control over when the predictive metrics are created.

  1. Using the Training Metric Wizard, create a training metric with the option Automatically create on report execution cleared.

  2. Add the training metric to a report. This can either be an existing dataset report or new report which contains only the training metric.

    Ensure that the training metric is on the grid of the report. If the training metric is only in the Report Objects but not on the report grid, no predictive metrics are created for the training metric when the report is executed.

  3. Run the report.

  4. In the Report Editor, select Create Predictive Metric(s) from the Data menu.

  5. Use the Create Predictive Metric(s) dialog box to generate predictive metrics from the training metrics on the report.

Importing the model

If the model exists in a file, it can be imported into MicroStrategy using the Import Data Mining Model dialog box. Models can be written to disk from a MicroStrategy training report using the Create Predictive Metric(s) dialog box.

This functionality is available when running reports in MicroStrategy Developer (for example, not in MicroStrategy Web, not via MicroStrategy Office, not via MicroStrategy Narrowcast Server, and so on).