Yes. The normal way, or the way all the Colibri tutorials illustrate, is that we pipe the same slider into the Parameters recorder as we do the Iterator.
This is less than desirable when I use a slider to choose from a list of parameters.
With a list of input choices 7, 23, 37, and 100, whose list indices are 0,1,2, and 3 respectively, I originally used List Item and a slider from 0 to 3 and piped that into the Iterator.
But we can pipe the result of this choice into the Parameters component as well than the index of the list. This gets stored as an output in the csv
Additionally, if the value is run through a parameter component, it can be named something other than the slider name. The slider can have a robust name that makes sense for understanding the definition but the data can be stored in something than simple and small for the Design Explorer header.
The inputs, the index choice sliders, are still recorded as inputs in the CSV, so we don’t lose anything. In design explorer, we can hide those inputs.