| | Short-term
Target: CRC/initial release
Frontend |
| |
- 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
|
|
>
> | |
| | Support/QA/Misc. |
|
>
> | Release Critical
- more unittests; also functional/integration tests
|
| | Important
- user-facing documentation (help)
- Better logging/error-reporting (to console/within HAL). eg: log4j
- Better handling of overhead runtime vs. target algorithm runtime
|
|
<
< |
- WAY more unittests; also functional/integration tests
|
| |
Nice-to-have
- developer-facing documentation (javadocs)
|
| |
Long-term/Unprioritized
Feature requests should be initially added here |
|
<
< |
- (FH) Probably simple: Support PAR-10 as one parameter for ParamILS
- (FH) Probably simple: Support single-CPU arrow runs with csh shell (currently, I can only run ParamILS using 2 CPUs, one of which is then idle)
|
| |
- (FH) Support for complete configuration experiment, front to back: run configurator N times on a training set, report the N training and test set performances
- (FH) Developers of configurators should be able to swap in new versions of a configurator
- (FH) Configuration scenarios, specifying a complete configuration task including the test set; only missing part being the configurator
|
Copyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.