You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Hessian tracer added in #20 keeps track of all first and second-order interactions between indices. However, these aren't all needed due to symmetry.
To make an analogy using Polynomials, we separately keep track of both $x_1x_2$ and $x_2x_1$.
By adding numerical comparisons between indices before updating sets, we could potentially speed up performance on some set types outside of BitSets.
It would be good to add a benchmarking suite with multiple set types before working on this.
The text was updated successfully, but these errors were encountered:
The Hessian tracer added in #20 keeps track of all first and second-order interactions between indices. However, these aren't all needed due to symmetry.$x_1x_2$ and $x_2x_1$ .
To make an analogy using Polynomials, we separately keep track of both
By adding numerical comparisons between indices before updating sets, we could potentially speed up performance on some set types outside of
BitSet
s.It would be good to add a benchmarking suite with multiple set types before working on this.
The text was updated successfully, but these errors were encountered: