This function gives an encompassing overview over the computational status on your system. The status can be one or many of the following:
“defined”: Jobs which are defined via batchMap
or addExperiments
, but are not yet submitted.
“submitted”: Jobs which are submitted to the batch system via submitJobs
, scheduled for execution.
“started”: Jobs which have been started.
“done”: Jobs which terminated successfully.
“error”: Jobs which terminated with an exception.
“running”: Jobs which are listed by the cluster functions to be running on the live system. Not supported for all cluster functions.
“queued”: Jobs which are listed by the cluster functions to be queued on the live system. Not supported for all cluster functions.
“system”: Jobs which are listed by the cluster functions to be queued or running. Not supported for all cluster functions.
“expired”: Jobs which have been submitted, but vanished from the live system. Note that this is determined heuristically and may include some false positives.
Here, a job which terminated successfully counts towards the jobs which are submitted, started and done.
To retrieve the corresponding job ids, see findJobs
.
getStatus(ids = NULL, reg = getDefaultRegistry())
ids | [ |
---|---|
reg | [ |
[data.table
] (with class “Status” for printing).
#>#>#>#>#> Error in (function (i) : 3#> [1] FALSE#> Status for 5 jobs at 2020-10-21 09:39:26: #> Submitted : 4 ( 80.0%) #> -- Queued : 0 ( 0.0%) #> -- Started : 4 ( 80.0%) #> ---- Running : 0 ( 0.0%) #> ---- Done : 3 ( 60.0%) #> ---- Error : 1 ( 20.0%) #> ---- Expired : 0 ( 0.0%)#> Classes ‘Status’, ‘data.table’ and 'data.frame': 1 obs. of 9 variables: #> $ defined : int 5 #> $ submitted: int 4 #> $ started : int 4 #> $ done : int 3 #> $ error : int 1 #> $ queued : int 0 #> $ running : int 0 #> $ expired : int 0 #> $ system : int 0 #> - attr(*, ".internal.selfref")=<externalptr>