Francesco Pannarale

`pycbc_create_injections` ---> `pycbc_dark_vs_bright_injections` ---> `pycbc_hdf5_splitbank`. So I think the first thing to do is to enable hdf5 stuff in `pycbc_dark_vs_bright_injections`

So, is the suggestion to do this via the `constraints` attribute of `pycbc.distributions`?

From `pycbc_create_injections`: "The parameter that constraints are applied to may be any parameter in variable_params or any output parameter of the transforms. Functions may be applied on these parameters to...

Still missing from the old pages - [x] GRB trigger information - [x] table of loudest offsource events with details - [ ] Values of 50% and 90% exclusion distances

Known requests - [x] Include GPS times of injections in tables - [x] Follow up of loudest missed injections - [x] Follow up of loudest offsource events - [x] Sample...

I'm closing this issue as it is superseded by https://github.com/gwastro/pycbc/pull/4288 (and future PRs that will follow it).

https://github.com/gwastro/pycbc/pull/4639 may need some fixes downstream in the post-processing, as noted in the PR's thread.

- [ ] @jakeb245, per the discussion we had today about `extract_basic_trig_properties`, please add the argument `opts` in `pycbc_pygrb_efficiency` when the `extract_basic_trig_properties` function call happens.

Moving more webpage/post-processing tasks here from issue [#4419](https://github.com/gwastro/pycbc/issues/4419). Comparing the [latest results webpage](https://ldas-jobs.ligo.caltech.edu/~francesco.pannarale/LVC/pygrb_dev_webpage2/) to the [most complete one](https://ldas-jobs.ligo.caltech.edu/~francesco.pannarale/LVC/py3_pygrb_webpage_3/) generated when using old xml results files, the items missing are -...

On the basis of the April 2024 [test](https://ldas-jobs.ligo.caltech.edu/~francesco.pannarale/LVC/pygrb_apr2024_test2/) I am marking some of the items in the previous comment as done. The remaining items are - [ ] reporting the...