-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New mle abort
subcmd - Clean experiment termination
#68
Labels
core-func
Core functionality
Comments
mle abort
subcommandmle abort
subcommand - Clean experiment termination
mle abort
subcommand - Clean experiment terminationmle abort
subcmd - Clean experiment termination
It would be great to have a keyboard interrupt wrapper that cleans up the protocol/VM instances. Have a look at this thread: https://stackoverflow.com/questions/1187970/how-to-exit-from-python-without-traceback |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I would like to have a subcommand that terminates all jobs associated with an experiment and removes all generated files/the trace of it. Otherwise one has to manually use
qdel
,scancel
orgcloud compute instances delete
. This could for example bemle abort <experiment_id>
or simplymle abort
with an additional user Q/A afterwards (check if the status of the experiment isrunning
). A simple procedure could look as follows:running
and getexperiment
from cmd args or user.experiment_id
is in db and status isrunning
. Repeat Q if not.job name
fromsingle_job_args.job_name
in DB.job_name
. This will depend on the resource.experiment_dir
.aborted
in the DB and push it back to GCP.mle monitor
.Also allow user to choose between termination via experiment config
.yaml
andexperiment_id
.Note: Give credit to Tudor's Liftoff package.
The text was updated successfully, but these errors were encountered: