You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The user should be able check on the status of model runs from rbabylon and reliably get one of the following responses: not submitted, in queue, running, finished, failed.
Implementation requirements
The function that does this (we'll call it check_nonmem_progress) should accept either a model object or a valid path to the model (YAML, ctl, or output dir).
model_summary() should call this under the hood and return a meaningful response for models that are not successfully finished.
run_log() should call this under the hood and add a column for model_status reflecting the status of each model. Consider if this can/should be done in parallel.
Implementation details
This will likely require looking at output folders, as well as something like qstat (or maybe top for the local models?). It is not clear how this should be implemented, but it will likely require some consultation with both the scientists and @shairozan to consider all the edge cases.
The text was updated successfully, but these errors were encountered:
Summary
The user should be able check on the status of model runs from rbabylon and reliably get one of the following responses:
not submitted
,in queue
,running
,finished
,failed
.Implementation requirements
check_nonmem_progress
) should accept either a model object or a valid path to the model (YAML, ctl, or output dir).model_summary()
should call this under the hood and return a meaningful response for models that are not successfullyfinished
.run_log()
should call this under the hood and add a column formodel_status
reflecting the status of each model. Consider if this can/should be done in parallel.Implementation details
This will likely require looking at output folders, as well as something like
qstat
(or maybetop
for the local models?). It is not clear how this should be implemented, but it will likely require some consultation with both the scientists and @shairozan to consider all the edge cases.The text was updated successfully, but these errors were encountered: