-
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
Bnb32/issue46 #47
Bnb32/issue46 #47
Conversation
…oop. Pass this check to eagle to skip running and just update status file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me, did you try it out?
Yeah a bunch. The one thing that annoys me is the dummy runs are interpreted as failed so we get a message about that on new submissions. Changing that would require digging in reV though I guess. Otherwise it works well. |
Thats fine though, its good if those jobs "fail" because then the pipeline wont move past the current step and those jobs will be submitted once you disable the debug feature |
Yeah I'd just rather it not move past but not say theyre failed. Just nitpicking though. |
Added ability to specify "debug_day" in config_nsrdb.json. If this is null things will run normally. If not null only debug_day will be run and all other jobs in doy_range will only be included in the status file.