When multiple trajectories are generated, we end up getting some bogus values. Since there are no global variables used to generate the trajectories, I can only assume there is some memory being shared between each generation that could cause the issue.
When multiple trajectories are generated, we end up getting some bogus values. Since there are no global variables used to generate the trajectories, I can only assume there is some memory being shared between each generation that could cause the issue.