Getting/calling the Item
The module used for automation parameter testing (there are sequence of modules - Float array, Generate file name.See examples). It receives collection of items and index and returns item with this index. It can be used for running the same procedure with different value of a parameter.
The Get item module is a workflow automation utility that extracts a single item from a collection based on a specified index position. It is typically used inside a looping workflow together with modules such as Float array or Generate file name, enabling the same processing sequence to be repeated automatically with a different parameter value on each pass. On each iteration, the module reads the current iteration number, picks the corresponding item from the collection, and passes it downstream as an output item that other modules in the workflow can use as an input.
A common use case is parameter sweep testing: build a collection of velocity values or file names, then use Get item inside a loop so that each iteration of the workflow processes data with the next value in the list. When the selected item is itself a group of multiple values (a container), its individual sub-items are automatically unpacked into Output items 2 through 5, allowing multi-parameter combinations to be distributed to separate downstream connections in a single step.
Input collection - specifies the input collection items.
Connect a collection of items here — typically the output of a Float array or Generate file name module. The collection must contain at least one item; if it is empty the module will report an error and stop processing. Each element of the collection corresponds to one iteration of the workflow loop.
Number of iteration - specifies total number of iterations. By default, 1.
This is a 1-based index that controls which element is retrieved from the Input collection. A value of 1 returns the first item, a value of 2 returns the second, and so on. In a typical looping workflow this value is updated automatically by the loop controller on each pass; you do not normally edit it manually. The default value is 1. If the index is greater than the number of items in the collection, the module will report an error.
There are no parameters available for this module.
Skip - By default, FALSE(Unchecked). This option helps to bypass the module from the workflow.
Output item 1 -
The item selected from the Input collection at the position given by Number of iteration. This output is always populated when the collection contains a valid element at that position. Connect this output to the parameter of the downstream processing module that you want to vary across iterations. The current item value is also written to the workflow log to help track which value is being used on each pass.
Output item 2 -
When the selected item is a container (a group of multiple values), this output receives the second sub-item within that group. If the selected item is a simple scalar value rather than a container, this output remains empty.
Output item 3 -
When the selected item is a container, this output receives the third sub-item within that group. Use this alongside Output items 2, 4, and 5 to distribute multiple coordinated parameter values to different downstream connections in the same iteration.
Output item 4 -
When the selected item is a container, this output receives the fourth sub-item within that group. Remains empty if the selected item is a simple value or if the container has fewer than four sub-items.
Output item 5 -
When the selected item is a container, this output receives the fifth sub-item within that group. This is the last of the expanded outputs; containers with more than five sub-items will have only the first five distributed across Output items 1 through 5.
There is no information available for this module.
There are no action items available for this module.
YouTube video lesson, click here to open [VIDEO IN PROCESS...]
Yilmaz. O., 1987, Seismic data processing: Society of Exploration Geophysicist
* * * If you have any questions, please send an e-mail to: support@geomage.com * * *