This repository has been archived by the owner on Aug 31, 2022. It is now read-only.
Solving Issue #18 when no epsilon is passed to a geometry defined with a kernel matrix #20
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
…h a kernel matrix. In that case default to 1 by testing whether epsilon_init was None and avoid "autoepsilon" computations that would cause an infinite recursion.
marcocuturi
added a commit
that referenced
this pull request
Nov 19, 2021
PiperOrigin-RevId: 411071648
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When defining a geometry using only a kernel, default to epsilon=1 by testing whether epsilon_init was None and avoid "autoepsilon" computations that would cause an infinite recursion.