At this point in time, selecting a doSth task from the GUI creates a batch job in the local cluster.
This should probably be generalized through the Queue script in the default folder. Here you should be able to switch between local or remote cluster, or maybe even serial execution.
All the relative "routing" of the doSth task should be handled by the qOperations function(line 327) in the Dashboard class or a similar function located somewhere else.
The job should be a communicating one, in order to retrieve the progress of the job and update the waitbar (this part is handled by the remoteMonitor function inside the dashboard class).
m053m716
commented
5 years ago
At this point in time, selecting a doSth task from the GUI creates a batch job in the local cluster.
This should probably be generalized through the Queue script in the default folder. Here you should be able to switch between local or remote cluster, or maybe even serial execution.
All the relative "routing" of the doSth task should be handled by the qOperations function(line 327) in the Dashboard class or a similar function located somewhere else.
The job should be a communicating one, in order to retrieve the progress of the job and update the waitbar (this part is handled by the remoteMonitor function inside the dashboard class).