| Short-term
Target: CRC/initial release
Frontend |
|
Backend
Release-critical |
|
< < | mostly to enable critical UI tasks |
> > | for functionality mentioned in paper for which post-release changes would be problematic |
|
- CN Named instance set table done
- CN Named configuration table done
- CN Execution environment table done
|
|
< < |
- CN Split algorithms and configuration spaces, allowing run reuse for common-binary configuration spaces. Both DB and Java object model.
- CN Explicit representation of problems/encodings, compatability of algs and instances via problem (encodings)
|
> > |
- CN Split algorithms and configuration spaces, allowing run reuse for common-binary configuration spaces. Both DB and Java object model; requires Algorithm refactor below.
- CN Explicit representation of problems/encodings, compatability of algs and instances via problem (encodings).
|
|
- CN rename objects to match paper terminology done
|
|
> > |
- CN Refactor Algorithms/Meta-algorithms in code to align class hierarchy with terminology of paper
- CN Refactor Algorithm/ParameterSpace/Parameter/Domain structure to allow above
- CN Database schema -- speed-related refactor
|
|
Important
mostly to (substantially) improve UI responsiveness |
|
< < |
- Database schema -- speed-related refactor
|
|
- Connection pooling
- Caching analysis results
- Query optimization
|
|
- Read-only DataManager connection for use by individual MA procedures
- Allowing relationships (incl. possible run-reuse) between different-binary "builds" of algorithms, including due to bugfixes, additional exposed parameters, etc. Also for different "versions" (without reuse) corresponding to added funcitonality.
- Ability to quantify membership of configurations to different design spaces
|
|
< < |
- Refactor Algorithms/Meta-algorithms in code to align class hierarchy with terminology of paper
- Refactor/cleanup Algorithm/ParameterSpace/Parameter/Domain structure
|
|
Support/QA/Misc. |