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 as not exists variable and Q as
defined in its own declaration
and therefore:
P1 is saved as ${P} , Q is saved as ${Q}q2
Now User Parameter 1 will update Q = ${Q}q1
and User Parameter 2 will update Q = ${Q}q1q2 where ${Q}q1 is the stored
variable
It sounds like a bug, but this is the flow.
On Wed, Nov 15, 2017 at 10:15 AM, minerva001 <minerva...@hispeed.ch> wrote:
> Didn't got a reply on the user list, hoping to get some help from the devs.
>
> 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?
>
>
