Skip to content
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

Closed
pannarale opened this issue Jun 28, 2023 · 4 comments
Closed

snr_IFO labels in PyGRB #4416

pannarale opened this issue Jun 28, 2023 · 4 comments
Labels
PyGRB PyGRB development

Comments

@pannarale
Copy link
Contributor

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'.

@pannarale pannarale added the PyGRB PyGRB development label Jun 28, 2023
@github-project-automation github-project-automation bot moved this to In Progress in PyGRB Development Jun 28, 2023
@pannarale
Copy link
Contributor Author

@titodalcanton
Copy link
Contributor

@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?

@titodalcanton
Copy link
Contributor

The snr_* field names have now been fixed in #4639.

@pannarale
Copy link
Contributor Author

@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 pycbc_multi_inspiral output to the post processing scripts.

@github-project-automation github-project-automation bot moved this from In Progress to Done in PyGRB Development Feb 21, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
PyGRB PyGRB development
Projects
Status: Done
Development

No branches or pull requests

2 participants