List view

• Release version 1.0

  Criteria for requiring an issue/PR be fixed before the initial release: 1) It is critical for making a proof of concept HTM system, 2) Fixing it would break compatibility

  No due date

  •28/30 issues closed
  93% complete2 open28 closed

• Modular repo, bindings

  Make the repository more modular by introducing: standalone, optional modules. Examples: py bindings, tests, NAPI, ...

  No due date

  •5/6 issues closed
  83% complete1 open5 closed

• optimization

  No due date

  •6/17 issues closed
  35% complete11 open6 closed

• cleanup

  Removing (old, obsoleted) code.

  No due date

  •36/38 issues closed
  94% complete2 open36 closed

• interfaces

  Use more templates & interfaces in the codebase to ensure better code quality, easier refactoring etc. Ie. SDR-type wrapping all data going between (and inside) layers (what is array[] now) will make it easier to switch to vector, CUDA sparse array, ... Or a proper Serializable interface would allow to switch to/from capnp,...

  No due date

  •5/8 issues closed
  62% complete3 open5 closed