cellprofiler you must specify a pipeline filename to run

This is where you specify the pipeline's input catalogs. The Entry Point class name is specific to the pipeline JAR file identified in the template and must be specified correctly. If there are no existing templates to use, you must create a new template in order to proceed. In this case the screen will change and ask where to find the JAR file to be uploaded. Otherwise, you can create a new template by clicking the Upload JAR file button. Note that the JAR file associated with the selected template is displayed so that you can confirm that it is the correct JAR file. In this case, reusing an existing template also reuses the Pipeline JAR file and the runtime configuration specified by that template. If there are existing templates connected to this account, the layout of this page changes so that they are available for you to select as shown in Figure 2. Configure the Pipeline Version (Stream) Use an Existing Template For example, stream pipelines and batch pipelines do not have the same execution options, so the available execution options will change on the screen depending on the pipeline type specified. Fields may change as a result of how other fields are completed.

Required fields are identified by an asterisk '*' and all others are optional. The example below (Figure 2) is setting up a stream processing pipeline. In turn, the Template ID is associated with the specified JAR file's Pipeline ID and creates a new Pipeline Version with its own unique Pipeline Version ID (UUID). Upon submission, the pipeline service will assign a unique Pipeline Template ID (UUID) that identifies your template. The JAR file to be run on the pipeline service must be correctly specified by its file name and location. In some stream pipeline cases, the input and output catalog can be the same if configured for that purpose.Įnter or select all of the parameters that describe how your pipeline should run. It is possible to specify more than one input data catalog. Also, you must specify at least one input catalog layer as a data source and one output catalog layer as a data sink these are the defaults used unless overridden by specific job information at run time. This template information will be applied to the pipeline instance you have created by its Pipeline ID. Most of this screen deals with runtime information to be applied to the pipeline JAR file by the pipeline service, the combination of which is uniquely identified as an executable Pipeline Version. Next, you must create the Pipeline Template and Pipeline Version. To learn more about UUIDs, see the article Universally unique identifier.Ĭlick the Next button to continue to the next page and define the Pipeline Version's runtime parameters using the pipeline template. This simply means that the ID used a UUID designation as its unique identifier. It is common to find references in the HERE platform documentation as the ID name with (UUID) appended to it. The term globally unique identifier (GUID) is another name for this ID.

The HERE platform typically assign IDs (such as a Pipeline ID and a Pipeline Version ID) using a Universally Unique Identifier, abbreviated as UUID. Only 1 email address is allowed, so if multiple people need to be notified, you should use a group email address. The Notification Email information is used in case the HERE platform needs to send you a message. You must supply the pipeline's Name, Description, and identify the Group that will share access to the pipeline. Add a PipelineĪdding a Pipeline to the Pipeline Service begins by creating a pipeline instance. Do not attempt to finalize the deployment unless all required information is complete.

All of the fields with an asterisk (*) beside their names are required information. There are two GUI pages devoted to pipeline deployment. While you can do this from the command line using the OLP CLI or through a custom application interfacing directly with the Pipeline API, the platform portal provides a quick and easy way to deploy and run a pipeline. The object of the exercise is to load a pipeline JAR file onto the pipeline service and define the run time parameters that are needed to create a Pipeline Version, which is the operational form of the pipeline. This section of the platform portal UI focuses on the process of setting up the pipeline to run.

Configure Pipeline Version and TemplateĪs described on the Pipeline Lifecycle page, deploying a pipeline is necessary to process any data catalogs.

Deploying a Pipeline via Web Portal Topics

Cellprofiler you must specify a pipeline filename to run