EnsembleProblem safetycopy clarification #561
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
@ChrisRackauckas , I think there might be a typo in your edit (the commit you have added to this PR). It looks like you deleted a closing triple backquote and now the code block does not end where it should. |
Member
|
oh shit. yeah... |
Member
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These are minor documentation clarification concerning Ensemble problems. If an SDE problem contains a custom noise process,
safetycopyis insufficient for properly setting up multiple trajectories. The previous version of the documentation was not clear about that, leading to confusion like this one: https://discourse.julialang.org/t/sde-ensembleproblem-unhappy-with-trajectories-2/82098