schedulers/dpmsolver_multistep: add missing sde-dpmsolver branch in third-order update#13778
Open
Dev-X25874 wants to merge 1 commit into
Open
Conversation
…hird-order update
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This happens silently after the two lower-order warm-up steps complete (i.e. on step 3+),
making it a hard runtime crash for any user who configures
sde-dpmsolverwithsolver_order=3.The fix adds the missing
elif self.config.algorithm_type == "sde-dpmsolver"branch,derived from the same factor-of-2 doubling pattern that governs the
sde-dpmsolverformulation relative to
dpmsolverat every other order (per Appendix A of theDPMSolver paper), and using the identical
noise term
sigma_t * sqrt(exp(2h) - 1) * noisealready present in the 1st- and2nd-order
sde-dpmsolverbranches.Fixes # (issue)
Before submitting
documentation guidelines, and
here are tips on formatting docstrings.
Who can review?
@yiyixuxu