Loop End

This Node Is Deprecated — This version of the node has been replaced with a new and improved version. The old version is kept for backwards-compatibility, but for all new workflows we suggest to use the version linked below.

Go to Suggested ReplacementLoop End

Node at the end of a loop. It is used to mark the end of a workflow loop and collects the intermediate results by row-wise concatenation of the incoming tables. The start of the loop is defined by the loop start node, in which you can define how often the loop should be executed (either fixed or derived from data, e.g. the "group loop start"). All nodes in between are executed that many times.

Options

Row ID policy

It specifies how to deal with the row IDs.

Generate new row IDs - row IDs are newly generated (Row0, Row1, ...)
Unique row IDs by appending a suffix - the iteration number is added to each row ID from the incoming table, thus making the row IDs unique over all iterations
Leave row IDs unmodified - the incoming row IDs are not altered. In this case you have to make sure that there are not duplicate row IDs in different iterations. Otherwise an error occurs.

Add iteration column

Allows you to add a column containing the iteration number to the output table.

Propagate modified loop variables

If checked, variables whose values are modified within the loop are exported by this node. These variables must be declared outside the loop, i.e. injected into the loop from a side-branch or be available upstream of the corresponding loop start node. For the latter, any modification of a variable is passed back to the start node in subsequent iterations (e.g. moving sum calculation). Note that variables defined by the loop start node itself are excluded as these usually represent loop controls (e.g. "currentIteration").

Ignore empty input tables

If this option is checked empty input tables and there structure are ignored and will not cause the node to fail.

Allow variable column types

If checked, the loop does not fail when the column types between different table iterations change.

Allow changing table specifications

If checked, the table specifications between iterations can differ. If column have been added or removed between iterations, missing values are inserted accordingly in the result table. If not checked and the table specifications differ, the node will fail.

Input Ports

: Any datatable

Output Ports

: Collected results from the loop body

Popular Predecessors

Popular Successors

Views

This node has no views

Workflows

Developers

You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.

Installation

To use this node in KNIME, install the extension KNIME Base nodes from the below update site following our NodePit Product and Node Installation Guide:

v5.3

A zipped version of the software site can be downloaded here.

Plugin provider: KNIME AG, Zurich, Switzerland

Plugin version: 5.3.3.v202410291553

On NodePit since: 2024-07-09

Last update: 2024-11-21

Tags: Deprecated

KNIME versions: Since v3.6

Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.

Try NodePit Runner!