We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
We should have API functions for most standard matrix decompositions.
In particular we should have:
Naming is TDB, we have various proposals:
lu
decompose-lu
lu-decompose
decomposition-lu
lu-decomposition
Need to decide on a consistent and logical naming scheme before we commit to a public API.
Also need to define return values. Current thinking is a map (or defrecord?) that contains clearly labeller values e.g.
(decompose-lu matrix) => {lower: [matrix1] :upper: [matrix 2] :determinant [double value]
See:
The text was updated successfully, but these errors were encountered:
I vote for short names: ld, svd, qr etc.
Sorry, something went wrong.
I'm more in favour of being a bit more explicit:
It's a close call I admit. But see my reasoning in the newsgroup:
Closing this as now complete.
Opted for the longer names so we can do stuff like:
(let [qr (qr-decomposition m)] .... do stuff with qr)
No branches or pull requests
We should have API functions for most standard matrix decompositions.
In particular we should have:
Naming is TDB, we have various proposals:
lu
decompose-lu
lu-decompose
decomposition-lu
lu-decomposition
Need to decide on a consistent and logical naming scheme before we commit to a public API.
Also need to define return values. Current thinking is a map (or defrecord?) that contains clearly labeller values e.g.
See:
The text was updated successfully, but these errors were encountered: