Skip to content
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

Restart automation #52

Open
micahjohnson150 opened this issue Oct 18, 2019 · 1 comment
Open

Restart automation #52

micahjohnson150 opened this issue Oct 18, 2019 · 1 comment

Comments

@micahjohnson150
Copy link
Contributor

After chatting with @etrujil who is running awsm right now, a crash restart should be an automated thing if the restart_crash = True. As of now (I think) the restart also requires a wyh_restart_output to restart at, but its description says its the last output prior to the crash which seems to me to be determinable. By having this automated it will certainly make us more reproducible and by having the control crash_restart we aren't losing control.

Coreconfig description

description = last iSnobal output wyhr. Program will look at output files

Location of the wyh_restart in framework.py

if config.cfg['isnobal restart']['restart_crash']:

@scotthavens
Copy link
Contributor

I'm working through this as well. However, we have to specify what happens when a restart is needed. I think that throwing out depth is a last resort and the thresholds should be changed first to see if it can be made through.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants