Skip to content
Discussion options

You must be logged in to vote

Parallelization becomes tricky when something in your trajectories references the simulation environment (now(bank) in your case). This is mainly because, internally, both trajectories and the simmer environment are pointers to internal objects. My recommendation is to define a function (e.g., simulate) encapsulating everything, and then pass that function to mclapply. You can find an example of this workflow in this vignette.

Replies: 1 comment 3 replies

Comment options

You must be logged in to vote
3 replies
@pgetty
Comment options

@Enchufa2
Comment options

@pgetty
Comment options

Answer selected by Enchufa2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants