Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Generalize first- and second-order information in HessianTracer #114

Closed
adrhill opened this issue May 31, 2024 · 0 comments · Fixed by #119
Closed

Generalize first- and second-order information in HessianTracer #114

adrhill opened this issue May 31, 2024 · 0 comments · Fixed by #119
Assignees
@adrhill
Labels
patterns Features regarding sparsity pattern representation
Milestone
Paper

Comments

@adrhill
Copy link
Owner

adrhill commented May 31, 2024

Currently, first- and second-order information are kept in separate AbstractSet and AbstractSet{<:Tuple} types.

The code should be generalized to support "shared" representations of second order information, similar to the dictionary of sets pre #57 and global "tape" with shared objects proposed in #107.
@adrhill adrhill self-assigned this May 31, 2024
@adrhill adrhill mentioned this issue Jun 5, 2024
Merged
@adrhill adrhill added this to the Paper milestone Jun 6, 2024
@adrhill adrhill mentioned this issue Jun 26, 2024
Merged
@adrhill adrhill added the patterns Features regarding sparsity pattern representation label Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@adrhill adrhill

Labels
patterns Features regarding sparsity pattern representation
Projects
None yet
Milestone
Paper
Development

Successfully merging a pull request may close this issue.

Generalize sparsity pattern representations adrhill/SparseConnectivityTracer.jl
1 participant
@adrhill