Difference: HAL (37 vs. 38)

  Short-term 
Target: CRC/initial release
 Frontend
  Important 
mostly to (substantially) improve UI responsiveness
-<
<
+ Connection pooling
->
>
+ CN Connection pooling done (contingent on rest of DataManager refactor, above)
  Caching analysis results
-<
<
+ Query optimization
->
>
+ CN Query optimization (CN: in progress)
  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
->
>
+ CN DataManager API refinement (in progress as part of DataManager refactor)
  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
->
>
+ CN Read-only DataManager connection for use by individual MA procedures done (as part of DataManager refactor)
  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