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

Strict checking for valid assignment locations in mutable matrices #32

Open

5 tasks

armcknight opened this issue Apr 12, 2015 · 0 comments

Open

5 tasks

Strict checking for valid assignment locations in mutable matrices #32

armcknight opened this issue Apr 12, 2015 · 0 comments

Owner

armcknight commented Apr 12, 2015

Currently, assigning to an invalid location (outside band or triangular component) in a mutable matrix will throw an assertion.

Should be able to configure via build setting at compile time:

strict asserts on assigning a value:

in the lower triangular component of an upper-triangular matrix and vice versa
outside the bandwidth of a band matrix

lazy assignment lets you assign anywhere in the matrix and invalidate state accordingly:

symmetry
bandwidth
triangular component

This would also convert the internal representation to conventional if the symmetry/band/triangular property is violated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment