Comment 5 for bug 1255632

Hi,

I understand your problem but I'm not sure how to fix it. Since your fix is everything but efficient.
using ntry = 0 each time you call the matrix element slows down the code significantly since you compute again and again vanishing helicities.

I can see two possibilities:
1) if you make some sequential run (all call for one param_card, then all call for the second one) then we can include an option "reset".
2) if you call those in parralel, the correct way would be to modify the class to have those optimization variable linked to each param_card.dat (one way is to have one instance by param_card)

Cheers,

Olivier