| | HAL 1.0 Task List
Backend 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.
|
|
<
< |
- (~2d) Algorithm specification screen changes, as per previous HAL meeting.
|
>
> |
- (~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
|
| |
- (~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, from the landing page
|
|
<
< | |
| | |
|
<
< |
-
- Execution environment
- Configuration
|
>
> | |
| |
- (~0.5d) Database deletion of HAL top-level objects, from a separate screen
- Algorithm
- Instance set
- Experiments
|
|
>
> | |
| |
-
- Execution environment
- Configuration
|
| |
Unprioritized |
|
<
< |
- (~0.5d after backend functionality exists) UI elements for user-specified annotations of HAL objects (eg, descriptions of instance sets, etc.)
|
| |
- Define New Inst Distr
- (~0.25d) hide type (until we have > 1 types)
|
Copyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.