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
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.
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.
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
awsm/awsm/framework/CoreConfig.ini
Line 238 in dd323c0
Location of the wyh_restart in framework.py
awsm/awsm/framework/framework.py
Line 774 in dd323c0
The text was updated successfully, but these errors were encountered: