Update sparsity detection docs #748
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
|
Weird, the previous run on f58c26c only failed the formatting check. |
ChrisRackauckas
force-pushed
the
ah/update-sparsity-detection
branch
from
515a277 to
b03c9e3
Compare
|
This PR doesn't touch |
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.
This PR updates the section "Declaring a Sparse Jacobian with Automatic Sparsity Detection" by using the new ADTypes interface and SparseConnectivityTracer instead of Symbolics, as suggested on Slack.
I'm opening this as a draft PR since I couldn't get the documentation to build.