@RDunn and @physicboy ,
Thanks for your feedback.
I was trying to avoid another input that validates the first step values. For example I would add a “init” or “reset” input that would take a Behavioral Voltage Source. The Equation of the BV would be V=(data0==<data0_1st_step>) & (data1==<data1_1st_step>) & (data2==<data2_1st_step>). [Yes, I’m using a 3–dimensional step sim.]
However if I have too many places to change values it would be too easy to neglect a parameter value needed to changed when I change the step parameters for the next sim run. Hence, having a step # as a variable available to the C-block would be advantageous.
Robert, You mentioned about a batch method available. This might be of interest. I’d like to learn more about it. I’d like to try a batch version of my current sim as it stands and compare how much sim time savings I can get by ditching the GUI interface.
Having said that, I think it safe to say, most users of this tool will probably “visual” people. The GUI is extremely useful for detecting issues quickly.
Len