Configuring pipeline nodes
Configuring pipeline nodes Configure the nodes of your pipeline to specify inputs and to create outputs as part of your pipeline. Specifying the workspace scope By default, the scope for a pipeline is the project that contains the pipeline. You can explicitly specify a scope other than the default, to locate an asset used in the pipeline. The scope is the project, catalog, or space that contains the asset. From the user interface, you can browse for the scope. Changing the input mode When you are configuring a node, you can specify any resources that include data and notebooks in various ways. Such as directly entering a name or ID, browsing for an asset, or by using the output from a prior node in the pipeline to populate a field. To see what options are available for a field, click the input icon for the field. Depending on the context, options can include: * Select resource: use the asset browser to find an asset such as a data file. * Assign pipeline parameter: assign a value by using a variable configured with a pipeline parameter. For more information, see [Configuring global objects](https://dataplatform.cloud.ibm.com/docs/content/wsj/analyze-data/ml-orchestration-flow-param.html). * Select from another node: use the output from a node earlier in the pipeline as the value for this field. * Enter the expression: enter code to assign values or identify resources. For more information, see [Coding elements](https://dataplatform.cloud.ibm.com/docs/content/wsj/analyze-data/ml-orchestration-expr-builder.html). Pipeline nodes and parameters Configure the following types of pipeline nodes: Copy nodes Use Copy nodes to add assets to your pipeline or to export pipeline assets. * Copy assets Copy selected assets from a project or space to a nonempty space. You can copy these assets to a space: - AutoAI experiment - Code package job - Connection - Data Refinery flow - Data Refinery job - Data asset - Deployment job - Environment - Function - Job - Model - Notebook - Notebook job - Pipelines job - Script - Script job - SPSS Modeler job #### Input parameters |Parameter|Description| |---|---| |Source assets |Browse or search for the source asset to add to the list. You can also specify an asset with a pipeline parameter, with the output of another node, or by entering the asset ID| |Target|Browse or search for the target space| |Copy mode|Choose how to handle a case where the flow tries to copy an asset and one of the same name exists. One of: ignore, fail, overwrite| #### Output parameters |Parameter|Description| |---|---| |Output assets |List of copied assets| * Export assets Export selected assets from the scope, for example, a project or deployment space. The operation exports all the assets by default. You can limit asset selection by building a list of resources to export. #### Input parameters |Parameter|Description| |---|---| |Assets |Choose Scope to export all exportable items or choose List to create a list of specific items to export| |Source project or space |Name of project or space that contains the assets to export| |Exported file |File location for storing the export file| |Creation mode (optional)|Choose how to handle a case where the flow tries to create an asset and one of the same name exists. One of: ignore, fail, overwrite| #### Output parameters |Parameter|Description| |---|---| |Exported file|Path to exported file| Notes: - If you export a project that contains a notebook, the latest version of the notebook is included in the export file. If the Pipeline with the Run notebook job node was configured to use a different notebook version other than the latest version, the exported Pipeline is automatically reconfigured to use the latest version when imported. This might produce unexpected results or require some reconfiguration after the import. - If assets are self-contained in the exported project, they are retained when you import a new project. Otherwise, some configuration might be required following an import of exported assets. * Import assets Import assets from a ZIP file that contains exported assets. #### Input parameters |Parameter|Description| |---|---| |Path to import target |Browse or search for the assets to import| |Archive file to import |Specify the path to a ZIP file or archive| Notes: After you import a file, paths and references to the imported assets are updated, following these rules: - References to assets from the exported project or space are updated in the new project or space after the import. - If assets from the exported project refer to external assets (included in a different project), the reference to the external asset will persist after the import. - If the external asset no longer exists, the parameter is replaced with an empty value and you must reconfigure the field to point to a valid asset. Create nodes Configure the nodes for creating assets in your pipeline. * Create AutoAI experiment Use this node to train an [AutoAI classification or