) for the run, and then click Re-run.Once a data mining run has been submitted, it can be re-run as is or with modified parameters. For example, you need an MGPS run with 5 as the Minimum Count, and another MGPS run with all of the same data mining parameters but with 10 as the Minimum Count. Once you have submitted the first run, instead of creating a new run and supplying all of the same selections again, except for the minimum count, you can re-run and change one parameter.
You can re-run any of the data mining runs that appear on your Data Mining Runs tab, including runs created by other users and runs that are currently running, completed successfully, failed, were canceled, or have not started. You can also re-run runs that are themselves re-runs. Note that:
When you re-run a data mining run, the application treats it as an independent run that is not associated with the original run; you are the owner of the new run. The run uses all parameters and options used for the original run (including the As Of date of the run, if the data configuration supports timestamped data) unless you explicitly modify them. In addition, the re-run uses the user preference, Replace Missing Values with, setting that was in effect for the run creator when the original run was created.
1. On the Data Mining Runs page, click the row menu () for the run, and then click Re-run.
The Re-Run page appears and displays the configuration used for the original run.
2. To select a different data configuration, from the Configuration drop-down list of compatible data configurations, select a data configuration.
3. To limit the run to only cases meeting specified criteria, check Add Database Restriction.
4. Click Next.
If you added or modified a database restriction, the Define Database Restriction page appears. Otherwise, the Run Options page appears.
5. Modify run options as needed. You can also click Back to review all of the selections made for the original run and modify them as needed. For more information, see Defining run options.
Note: The run uses all of the variables, values, and parameters selected for the original run unless you modify them in the new run. For example, if there was a custom term for the original run, it is used as is unless you modify it. Keep in mind that any changes made to queries on the Queries tab have no effect on database restrictions or custom terms that were part of the original run. During the re-run, you must modify the database restriction or custom term, if needed, including reselecting a query that was modified on the Queries tab.
6. Click Next.
The Name Data Mining Run page appears.
7. In the Run name field, enter a name for the run. The name of the run does not need to be unique, although Oracle recommends that you use a unique name. The Empirica Signal application assigns a unique run ID to each run.
8. In the Description field, optionally enter a description. Oracle recommends that you provide an informative description of the run so that users who view run results know which run to use.
9. Optionally, assign the run to a project.
10. Click Next.
The Confirm Run Parameters page appears.
11. On the Confirm Run Parameters page, review the parameters chosen for your run to make sure that they are correct. Different parameters display for MGPS runs and LR runs.
12. If you want to change any parameters, click Back until you are on the appropriate page and make the necessary changes. Then click Next until you are back on the Confirm Run Parameters page
13. When you are satisfied with the run parameters, click Submit.
The application notes that the run has been submitted.
14. Click Continue.
The run status appears on the Data Mining Runs page. To monitor the progress of a run, you can view jobs for the run.
15. Check the Data Mining Runs tab to determine when your run has completed.