Remaining issues

New features

Enable editing added schedulers.
Execution: plot the memory and threads usage over time.
Execution: plot a Gantt chart showing the execution of the various nodes in relationship to one another.
Uploading pipeline from YAML file is partially implemented.
IndexedDB is not an ideal solution to store all the system states. On one hand, the user needs to take care of the browser's storage quota; on the other hand, it really takes time for the browser to simply read all the information from the local IndexedDB. Closing a tab or the browser may also cause a loss of data of IndexedDB. A better solution may be storing some of the most storage-consuming data in the backend (for example, execution-related data), and access them by making request to the C-PAC cluster.

Real-time node log file (and crashes?) is currently missing.
C-PAC cluster is not able to build dataConfig from BIDS directory, while the local backend is able to build from BIDS.

The whole page got frozen for several seconds or even minutes (rare) after an execution receives the finishing information from all subjects. This happens during executions with a large number of subjects (100 or more).
In some cases, when running the AWS cluster for a C-PAC execution, the progress of running a local execution at the same time may got stuck.

Further discussion with the usability team is required.