| HAL 1.0 Task List
Backend Tasks |
| Frontend tasks
4-week plan (CF) |
|
< < |
- (~1d) Landing page run status divs should maintain individual state, not have pieces disappear on refresh, and should not appear under more than one heading (or disappear entirely) when the run status changes.
|
> > |
- (~1d)
Landing page run status divs should maintain individual state, not have pieces disappear on refresh, and should not appear under more than one heading (or disappear entirely) when the run status changes.
|
|
- (~2d) Algorithm specification screen changes, as per previous HAL meeting.
|
|
< < |
-
- "add output capture" below info for last string added
- examples for params (call string), output capture
|
> > |
-
-
"add output capture" below info for last string added
-
examples for params (call string), output capture
|
|
- (~1d) Rearranging meta-algorithm specification pages, as previously discussed.
|
|
-
- keep options collapsed by default wherever possible
- (~1d) Notes/annotation for 'top-level' objects.
|
|
> > |
-
-
Algorithm
- Instance set
- Experiment
- Execution environment
- Configuration
|
|
- (~1d) Various minor previously-reported monitor page changes.
- auto-reload of monitor pages, interval configurable in HAL settings - local to client/user
|
|
- (~0.5d) Sub-run information table in the monitor pages, sortable by column headers, not loaded until requested.
|
|
< < |
- (~0.5d) Database deletion of HAL top-level objects, both from the landing page if applicable and a separate screen.
|
> > |
- (~0.5d) Database deletion of HAL top-level objects, from the landing page
- Algorithm
- Instance set
-
Experiments
- Execution environment
- Configuration
- (~0.5d) Database deletion of HAL top-level objects, from a separate screen
- Algorithm
- Instance set
- Experiments
- Execution environment
- Configuration
|
|
- (~1.5d) Viewing/editing/copying of HAL top-level objects
|