distinguish between direct and iterative methods #81
Conversation
This file contains 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
schillic
approved these changes
Jun 7, 2022
Co-authored-by: Christian Schilling <git@christianschilling.net>
mforets
approved these changes
Jun 8, 2022
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 PR introduces the subtypes
AbstractDirectRangeAlgorithmandAbstractIterativeRangeAlgorithmto distinguish between algorithms that directly evaluate the function over a domain (currently natural enclosure and taylor, in principle also affine arithmetic and mid-value form) from methods that refine the enclosure estimation using optimization methods. The end goal is to allow iterative backends to use different direct backends (e.g. moore-skelboe with either natural enclosure or mean value form) as described in #77.