-
Notifications
You must be signed in to change notification settings - Fork 4
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
Improvements for gain selection automation #293
Conversation
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.
Here are some more comments. Looks good overall. IMO some parts are too nested, but I understand that there are different cases you have to cope with
@marialainez, this would allow running the gain selection launcher several times and just re-doing jobs that did not previously succeed, right? |
yes, we have been testing it for the last days and it works as expected |
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 overall, if you have tested it in the cluster for a couple of days I'd say it's good to go
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.
some changes in the log messages, to make following the logs easier. I would just leave some log info messages for general actions happening and maybe just give info at run level.
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.
Find some more comments inline. Test it in the next period for several days and if works smoothly I'd say it's ready to go
src/osa/scripts/sequencer.py
Outdated
log.info(f"Sequencer is still running for date {date_to_iso(options.date)}. Try again later.") | ||
sys.exit(0) | ||
|
||
elif sequencer_finished(options.date) and not options.force: |
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.
when do you foresee using the force option?
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.
Some more comments (I hope the last ones)
A problem with the mamba setup step in CI makes tests fail. Please relaunch the tests after #303. |
@marialainez please rebase the branch with main to make the tests run again |
Co-authored-by: Daniel Morcuende <dmorcuende@iaa.es>
Co-authored-by: Daniel Morcuende <dmorcuende@iaa.es>
Co-authored-by: Daniel Morcuende <dmorcuende@iaa.es>
Co-authored-by: Daniel Morcuende <dmorcuende@iaa.es>
d19e19f
to
d32dbba
Compare
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! Thanks for all the work
Main changes that have been made in this PR: