HAL < BETA < TWiki

---+ Short-term
Target: CRC/initial release
---++ Frontend
---+++ Release-critical 
_functionality promised in paper_
   * *CF* algorithm specification screen: implement (includes initial design space specification)
   * *CF* left side of landing page:  task selection/presentation according to pattern concept
   * *CF* experiment specification and monitor screens from a pattern template, and procedure-specific requirements, including experiment and incubment naming
   * *CF* instance specification screen: implement
   * *CF* Execution environment specification (incl. R, Gnuplot, java locations)
   * RTDs/per-target-algorithm-run monitoring and navigation
   * design space specification by revision of existing spaces

---+++ Important
_works as-is but end-user experience significantly impacted_
   * Data management interface:
      * deleting runs/expts/etc.
      * data export
   * Error logging/handling/browsing
   * Plotting ex-gnuplot


---++ Backend
---+++ Release-critical
_mostly to enable critical UI tasks_
   * *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* rename objects to match paper terminology *done*

---+++ Important
_mostly to (substantially) improve UI responsiveness_
   * Database schema -- speed-related refactor
   * Connection pooling
   * Caching analysis results
   * Query optimization
   * Selective limitation of run-level archiving (dynamic based on runtime?)
   * add incumbentname semantic input to (design) procedures

---+++ Nice-to-have
_noticeable mostly to developer-users_
   * DataManager API refinement
   * *CF* N-way performance comparison first-cut for Frank.
   * Stale connection issue; incl. robustness to general network issues
   * 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.
---+++ 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)


---+ Medium-term
Planned for future HAL 1.x revisions

   * Packaging complete experiments
   * Windows support
   * libraries of:
      * search/optimization procedures
      * machine learning tools
   * multi-algorithm comparisons
   * scaling analyses
   * bootstrapped analyses
   * robustness analyses
   * parameter response analyses
   * SATzilla in HAL
   * ParamILS in HAL
   * Parallel portfolios in HAL
   * ActiveConfigurator in HAL
   * Iterated F-Race in HAL
   * chained-procedure experiments
   * support for optimization/Monte-Carlo experiments
   * support instance generators
   * Git, not CVS
   * Support text-file inputs and outputs for external algorithms
   * Instance features
   * Explicit representation of problems (e.g. particular instance formats)
   * Experiments calling experiments, not just external target algs
   * array jobs in SGE
   * Hashing everything, including instances, instance sets and configurations.
   * Wider support for working directory requirements of individual algorithm runs, i.e. Concorde's creation of 20 files with fixed names.
   * Validation of form input.
   * Ability to browse algorithms, instances, instance sets, configurations, etc. This includes the ability to see things related to the item being browsed. Performance of different algorithms/configurations on a given instance, performance of algorithms across an instance set, performance of a given configuration.


---+ Long-term/Unprioritized
Feature requests should be initially added here
   * (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
   * (FH) Saveable sets of configuration scenarios to perform (use case: I change the configurator and want to evaluate it)
   * (FH) Taking this a step further: support for optimizing a parameterized configurator (configurator is an algorithm, and the above set of experiments is the set of "instances")
   * (FH) Submitting runs from a machine that is itelf a cluster submit host should not need to go through SSH
   * (JS) public static AlgorithmRun subclasses in most ExecutionManagers should probably be private
   * (CF) Memory usage / CPU time monitoring in HAL of target algorithm runs, in order to report warnings on potential problems (like excessive swapping for example).

---+ Bugs Reports
   * (CN) JSC test reliability issue (compared to R)
   * (CN) end-of-experiment hanging bug (GGA, multinode cluster runs)
   * (JS) InnoDB SQL errors _(CN): fixed 11/05/10_
   * (LX) missing current-time point in solution quality trace, so don't see the final "flat line"
   * (CN) accuracy of mid-run overhead accounting for PILS/GGA
   * (CF) Configuration file callstrings with weird spaces, i.e. "... -param '$val$ blah' ..." where '$val blah' needs to be passed to the target as a single argument. _(CN) does this work with double-quotes instead of single-quotes?_
   * (JS) FixedConfigurationExperiment UI is outdated, unusable.
   * (JS) HAL is not usable on WestGrid. We need a TorqueClusterExecutionManager.
   * (JS) Algorithms with a requirement of a new directory for each run.
   * (JS) one of the ExecutionManagers produces unstarted AlgorithmRuns
   * (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.
This topic: BETA > HAL
Topic revision: r23 - 2010-05-18 - ChrisNell