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.

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

features for beta, not to be started till after the alpha #2

Open
19 tasks
cartazio opened this issue May 19, 2014 · 2 comments
Open
19 tasks

features for beta, not to be started till after the alpha #2

cartazio opened this issue May 19, 2014 · 2 comments
Milestone

Comments

@cartazio
Copy link
Member

These are just some near term goals for after the initial alpha release

Array tooling pieces

  • More fancy formats
    • Symmetric (padded and packed)
    • Hermitian (padded and packed)
    • Banded (all the various formulation)
    • Triangular (Padded and Packed)
    • Blocked Formats (and associated blocked reads and writes and custom simd as applicable)
  • Larger than ram Off heap vectors, both MemMapped to disk and ephemeral
  • Quadrant decomposition machinery (needed for Morton order, Symmetric formats)
  • Dense Rectilinear projection / slicing machinery (needed to express general rectilinear slicing on arbitrary rank dense row/column major arrays, plus the rank varying static projections)
  • index queries for valid starting locations (some of this is sneaking into the alpha, but not much )

Generalization pieces

  • generalized Array/layout classes to support sparse/dense time series indexed arrays

numerical computation tooling

  • Linear solvers
    • starting with textbook / blas standards
    • sparse friendly direct/iterative solvers
  • Least Square solvers
  • Eigenvalue / Eigenvector solvers
  • Preconditioners

sparse numerical tooling

  • see above, but trickier and sparse friendly, though some prelim support snuck into the alpha

good test coverage

  • should aim for 100% coverage wrt quickcheck/unit tests. For precision sensitive routines also be sure to test on inputs known to trigger problems with incorrect routines
@cartazio cartazio added this to the V0.2.0.0 milestone May 20, 2014
@cartazio
Copy link
Member Author

blocker: need to have randomv2 out before doing the right approach on some general algorithms, shouldn't be too bad

@ocramz
Copy link

ocramz commented Mar 14, 2017 via email

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

No branches or pull requests

2 participants