Home > Workflows > Using Workflows > Import and Export Workflows > Deploying Workflows > Object Generation Scripts > Scripts Generated
Several general scripts and related items are generated:
Master Script: A script that invokes all the required scripts in the appropriate order. The Master Script performs some validation, such as testing to determine if the version of the script is compatible with the version of the Data Miner Repository that is installed. The Master Script creates a workflow master table that contains entries for all the underlying objects created by the workflow script. The Master Script also contains generated documentation covering key usage information necessary to understand operation of scripts.
Cleanup Script: A script that drops all objects created by the workflow script. The Cleanup script drops hidden objects (such as the table generated for Explore Data) as well as public objects (such as Model Names created by Build nodes, and Tables created by a Create Table node).
Workflow Diagram Image: An image (.png
file) of the workflow at the time the script was generated. The entire workflow is displayed.
The remaining scripts that are generated depend on the nodes in the chain:
Node | Script Functionality |
---|---|
Data Source Node, Transform Node, Aggregate Node, Join Node, Filter Rows Node, Sample Node, Model Details Node, Apply Node, Apply Text Node, Filter Columns Details Node | Creates a view reflecting the output of the node |
Filter Columns Node. | Creates a view reflecting the output of the Filter Column node (like other transform type nodes)
If the Attribute Importance setting is specified, a table is generated containing the AI result (private) |
Build Text Node | For each text transformation the following objects are created: Feature Table Name and Oracle Text Policy Object
Creates a view reflecting the output of the Build Text node. This is essentially the same output as an Apply Text node |
Classification Build Node | A model is created for each model build specification
A master test result table is generated to store the list of test result tables generated per model GLM Model Row Diagnostics Table is created if row diagnostics turned on Each Model Test has one table generated for each of the following test results: Performance, Performance Matrix, ROC (for binary classification only) Each Model Test has one table for each of the following tests per target value (up to 100 maximum target values): Lift and Profit |
Regression Build Node | A model is created for each model build specification
GLM Model Row Diagnostics Table is created if row diagnostics turned on A master test result table is generated to store the list of test result tables generated per model Each Model Test will have one table generated for each of the following test results: Performance and Residual |
Clustering Build, Anomaly Detection Build, Feature Extraction Build, Association Build | A model is created for each model build specification |
Test Node (Classification) | A master test result table is generated to store the list of test result tables generated per model
GLM Model Row Diagnostics Table is created if row diagnostics turned on Each Model Test has one table generated for each of these test results: Performance, Performance Matrix, ROC (binary classification only) Each Model Test has one table for each of Lift and Profit per target value (up to 100 maximum target values): |
Test Node (Regression) | GLM Model Row Diagnostics Table is created if row diagnostics turned on
A master test result table is generated to store the list of test result tables generated per model Each Model Test has one table generated for each of Performance and Residual |
Model Node, Text Reference Node | No scripts generated. These nodes are just reference nodes to metadata |