-
Notifications
You must be signed in to change notification settings - Fork 359
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
snr_IFO labels in PyGRB #4416
Comments
Speaking of ugly PyGRB labels, here is more: https://github.com/gwastro/pycbc/blob/master/bin/pycbc_multi_inspiral#L269 and https://github.com/gwastro/pycbc/blob/master/bin/pycbc_multi_inspiral#L280 (affects |
@pannarale I do not understand your second comment as I think the code has changed in the mean time. What were the other ugly labels? |
The |
@titodalcanton, yes that PR fixes precisely the issues I used to refer to here. As you note there will be a need for fixes downstream once we feed |
https://github.com/gwastro/pycbc/blob/master/pycbc/events/eventmgr.py#L710 causes individual detector SNR labels to end with '1' only when the IFO in question is LHO. In turn, all pygrb post-processing that uses individual detector SNR information has to adapt to this convention: basically an
if ifo == 'H1'
ends up being needed in several places, which is not ideal. Better switch to a consistent naming: 'snr_h1', 'snr_l1', 'snr_v1', 'snr_k1'.The text was updated successfully, but these errors were encountered: