User parameters are strictly hierarchical
But when checking Update Once Per Iteration it saves before iteration the
variables beforehand
So that second User Parameter will have P and Q as not exists variables and
therefore
P1 ${P} ,
On Sun, Nov 12, 2017 at 3:38 PM, minerva001 <[email protected]> wrote:
> I noticed when having in a simple controller with several User Parameters
> (Preprocessors) with the "Update Once Per Iteration" flag marked, that the
> Preprocessors are run in reverse order.
>
>
>
> Simple Controller
>
> User Parameter
>
> P XX
>
> Q ${Q}q1
>
> User Parameter
>
> P1 ${P}
>
> Q ${Q}q2
>
> Debug Sampler
>
>
>
> In case "Update Once Per Iteration" is marked, P1=${P}, Q=${Q}q2q1
>
> When not marked, P1=XX, Q=${Q}q1q2
>
>
>
> Why does "Update Once Per Iteration" reverses the execution sequence of
> Preprocessors?
>
> Is this behavior intended and somewhere documented?
>
>
>
>
