-
Notifications
You must be signed in to change notification settings - Fork 356
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
Parallelize optimal_snr jobs #3413
Parallelize optimal_snr jobs #3413
Conversation
Instead of adding the new script |
I'm not sure - I hadn't seen that functionality before |
I am thinking about this:
I do not see an obvious reason why a specific script would be needed instead, as it is just merging tables. |
@GarethDaviesGW ligolw_add is an executable. I think @titodalcanton is saying why invent a new executable instead of using an existing one that likely already can do this. It takes options slightly differently, but otherwise, I think it should work. |
thanks - I hadnt seen the executable - I'll put that in rather than the optimal_snr_merge code |
I've updated to use the ligolw_add executable as well and removed the optimal_snr_merge |
The last codeclimate and codebeat issues are ones which we have generally ignored before - the overwriting of create_node in particular looks to be something done a lot elsewhere |
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.
Assuming you tested that the workflow builds and the dax looks sane, this seems fine.
tested with and without the parallelize option in config for workflow, and using the updated optimal_snr exe |
* add in codes and workflow to parallelize optimal_snr
* add in codes and workflow to parallelize optimal_snr
Given certain approximants and amount of injections, optimal_snr jobs can take a long time causing jobs to be evicted/restarted in the workflow
This splits optimal_snr jobs in the same way as the findtrigs jobs, and recombines using a new executable, pycbc_optimal_snr_merge
This will break current configs due to changing the way optimal_snr is used and optimal_snr_merge config requirements.
Newly required config tags:
[executables]
,optimal_snr_merge = ${which:pycbc_optimal_snr_merge}
[workflow-optimal-snr]
:parallelization-factor = 5
[optimal_snr_merge]
Tested in multiifo workflow, but as the 2-ifo workflow calls it in the same way, this should work there as well