Fig. 3. Job executions at the master node.

Job executions follow a closed-loop experimentation process involving several components, the job in the executing queue, the resource manager, the task generator, the task scheduler, the action translator, the action executor, and the database. When a job is ready for execution, it is matched in the job storage, initiating the experiment. Experiment information is transferred to the task generator, which generates tasks based on experimental conditions and device information. The task scheduler manages task executions, and the action translator converts task information into device commands. After executing the commands, the results are stored in the database, and the job recommends the next experimental conditions in a closed-loop manner.