-
Notifications
You must be signed in to change notification settings - Fork 357
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
Created option to set a high-frequency cutoff in pycbc_make_skymap #3414
Created option to set a high-frequency cutoff in pycbc_make_skymap #3414
Conversation
Changes: -Added a --f-upper option to pycbc_make_skymap. It passes those to pycbc_make_single template and SingleCoincForGraceDB. -Added high-frequency cutoff to SingleCoincForGraceDB. PSDs may now be truncated at a high-frequency cutoff.
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.
@MarlinSchaefer See the other comments, but the biggest one is that we need to pass the final cutoff information. You can do this by adding keys to the coinc_results dict which is passed to the SnglCoinc class.
I think you need to add the following key for each ifo being considered.
'foreground/IFO/f_final' where IFO should be replaced with the actual ifo.
If the key is passed correctly it will set the table entry at this line automatically https://github.com/gwastro/pycbc/blob/master/pycbc/io/live.py#L184
pycbc_make_skymap. Changes: -Reverted changes to pycbc/io/live.py -Made sure --f-upper option in pycbc_make_skymap is optional -Passing upper frequency limit to BAYSTAR via coinc_result
@MarlinSchaefer It looks like you've addressed the specific comments we had. |
…wastro#3414) * Started adding high-frequency cutoff. * Implemented high-frequency cutoffs. Changes: -Added a --f-upper option to pycbc_make_skymap. It passes those to pycbc_make_single template and SingleCoincForGraceDB. -Added high-frequency cutoff to SingleCoincForGraceDB. PSDs may now be truncated at a high-frequency cutoff. * Wrapped lines for CodeClimate. * Finished implementing a high-frequency cutoff for pycbc_make_skymap. Changes: -Reverted changes to pycbc/io/live.py -Made sure --f-upper option in pycbc_make_skymap is optional -Passing upper frequency limit to BAYSTAR via coinc_result
…wastro#3414) * Started adding high-frequency cutoff. * Implemented high-frequency cutoffs. Changes: -Added a --f-upper option to pycbc_make_skymap. It passes those to pycbc_make_single template and SingleCoincForGraceDB. -Added high-frequency cutoff to SingleCoincForGraceDB. PSDs may now be truncated at a high-frequency cutoff. * Wrapped lines for CodeClimate. * Finished implementing a high-frequency cutoff for pycbc_make_skymap. Changes: -Reverted changes to pycbc/io/live.py -Made sure --f-upper option in pycbc_make_skymap is optional -Passing upper frequency limit to BAYSTAR via coinc_result
Added an optional argument to pycbc_make_skymap.
This argument is passed to pycbc_single_template and SingleCoincForGraceDB.
For SingleCoincForGraceDB to accept a high-frequency cutoff changes to pycbc/io/live.py were required. I think the place I put these changes at don't interfere with anything else. I also think that implementing the high-frequency cutoff the way done here will pass it to Baystar.