| | Short-term
Target: CRC/initial release
Frontend |
| | 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. (CF): Reopened to account for java/ruby/gnuplot location specification etc.; in progress
- 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: in progress)
- CN Database schema -- speed-related refactor (CN: next up)
- CN Explicit representation of problems/encodings, compatability of algs and instances via problem (encodings).
|
>
> |
- CN Execution environment table. (CF): Reopened to account for java/ruby/gnuplot location specification etc.; mostly done but not checked in
- 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: done for Java objects; not started for DB)
- CN Explicit representation of problems/encodings, compatability of algs and instances via problem (encodings). (CN: in progress)
|
| |
- 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 Refactor Algorithms/Meta-algorithms in code to align class hierarchy with terminology of paper (CN: in progress)
- CN Refactor Algorithm/ParameterSpace/Parameter/Domain structure to allow above done
- CN Database schema -- speed-related refactor
|
| |
Important
mostly to (substantially) improve UI responsiveness |
| |
- (CF) When HAL kills a target algorithm run, it does not also kill all child processes spawned by that run. This can leave zombies and all kinds of other very bad things after a period of time. (CN): fixed 18/05/10
- (FH) If a HAL slave process fails to start, the associated expt. status stays on "queued" forever
- (FH) Database table contention causes locking and high query latency. Likely to be fixed by database changes and use of InnoDB, but I'm reporting it anyway.
|
|
>
> |
- (CN) DataManager-decorated ExecutionManager still requires explicit commit to save results. Also run results cannot be saved unless explicitly associated with an experiment id.
- (CN) Parameter values (eg Instance files) with spaces are split during command string construction; need to enquote them as necessary.
|
| | |
Copyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.