beams statement inside integrate{...} affects following integrate statement

[sschmidt]

If having an integrate command with some statements attached, e.g.

integrate(uuee) {beams = p,p -> lhapdf
 iterations = 4:10000, 6:10000 }

the rest of the sin-file is affected in a probably unintended way: iterations is reset to the value before (I thinkthis is intended), but the beams are set to something unusable, that is tf there is no new beams-statement the next integrate fails with

*** FATAL ERROR: Evaluator product: no matching states found
***                 -----------------------------------
***              Maybe you chose the wrong initial state
***              for the hard interaction, or there is a
***              mismatch in the structure functions.

Everything is fine if the additional beams statement inside the curly braces is omitted. See the attached file for a complete example.

[Juergen Reuter]

Probably linked to Ticket #231. WK, this is your metier, and it is urgent *lol*

[sschmidt]

I don't think that #231 and #232 are connected: They have the same error message but #232 appears when integrating while #231 appears when simulating.

[kilian]

When run with nagfor, the program crashes with an undefined pointer. I'll check.

[kilian]

[1953].

The problem was unrelated to #231. For the structure function setup, changing local data had a side-effect on global data.

[Juergen Reuter]

Milestone v2.0-rc3 deleted