Update Action Items authored by NV Krishnendu's avatar NV Krishnendu
[[_TOC_]] * **Action items for data release, figures, macros and tables in the paper:**
* For creating data release repo:
* We need <span dir="">/home/tgr.o3/o3b-tgr/results/sim/o1o2o3a</span> and <span dir="">/home/tgr.o3/o3b-tgr/results/sim/o</span>3b
* Get events for <span dir="">/home/tgr.o3/o3b-tgr/results/sim/o1o2o3a</span> by running <https://git.ligo.org/muhammed.saleem/o3siqm-updates/-/blob/master/script/clone_repo.py>, this script has to be updated commenting out the events that don't pass the selection criteria. See, <https://git.ligo.org/muhammed.saleem/o3siqm-updates/-/blob/master/o3b/scripts/simplot.ipynb> for these events
* Now we need: /home/tgr.o3/o3b-tgr/release/sim
* Pull data script: <https://git.ligo.org/muhammed.saleem/o3siqm-updates/-/blob/master/o3b/scripts/hier_analysis/pull_data_updated_knv.ipynb>
* This script will be at: /home/tgr.o3/o3b-tgr/release/sim
* That means we have all the .dat.dz files created here like [O3a](https://git.ligo.org/publications/O3/o3a-cbc-tgr/-/tree/master/release/sim)
* We have to update [simplot](https://git.ligo.org/muhammed.saleem/o3siqm-updates/-/blob/master/o3b/scripts/simplot.ipynb) script including all the macros following [o3a](https://git.ligo.org/publications/O3/o3a-cbc-tgr/-/blob/master/release/sim/sim_plot.ipynb)
* [Listing down the main action items for the O3b TGR analysis](#listing-down-the-main-action-items-for-the-o3b-tgr-analysis)
* [Comments from results so far (26 July 2021)](#comments-from-results-so-far-26-july-2021)
* [Results review readiness](#results-review-readiness)
* [Results review:](#results-review)
* [Numbers into the paper section:](#numbers-into-the-paper-section)
* [Plotting script](#plotting-script)
* [Event list](#event-list)
* [Review](#review)
* [PE](#pe)
# Listing down the main action items for the O3b TGR analysis # Listing down the main action items for the O3b TGR analysis
## Comments from results so far (26 July 2021) ## Comments from results so far (26 July 2021)
- S200316bj: - S200316bj:
- LAPLACE, https://ldas-jobs.ligo-wa.caltech.edu/~sayantani.datta/LSC/lalinference/O3/o3_b_tgr/sim/SummaryPages/S200316bj/Prod2/LAPLACE/laplace_bbh.txt, not passed? - LAPLACE, <https://ldas-jobs.ligo-wa.caltech.edu/\~sayantani.datta/LSC/lalinference/O3/o3_b_tgr/sim/SummaryPages/S200316bj/Prod2/LAPLACE/laplace_bbh.txt>, not passed?
- Extra features in mass posteriors for both SIQM and BBH runs - Extra features in mass posteriors for both SIQM and BBH runs
- Does the Mc-q prior translates to a boundary at lower m1-prior? I mean the m1 prior hits the lower mass end. Probably the Mc prior has to be widened - Does the Mc-q prior translates to a boundary at lower m1-prior? I mean the m1 prior hits the lower mass end. Probably the Mc prior has to be widened
- I think the mass features are more dominant for BBH runs. - I think the mass features are more dominant for BBH runs.
...@@ -13,12 +30,9 @@ ...@@ -13,12 +30,9 @@
- S191216ap: - S191216ap:
- dKs, long-tail on the positive side? could be a sampling issue? - dKs, long-tail on the positive side? could be a sampling issue?
- Mass parameters prior have to be checked here too. See total-masses for instance, are they hitting the boundary or is it just a sharp end of posterior - Mass parameters prior have to be checked here too. See total-masses for instance, are they hitting the boundary or is it just a sharp end of posterior
- S200225q - S200225q
- For S200225q (this is the event with final results available) - For S200225q (this is the event with final results available) Railing against mass prior? I think this is a common issue for all events
Railing against mass prior? I think this is a common issue for all events - Mc bimodal for PE Prod but not for dKs run, see here Compare to other events, there is more difference b/w BBH and dKs runs (masses, spins, distance)
- Mc bimodal for PE Prod but not for dKs run, see here
Compare to other events, there is more difference b/w BBH and dKs runs (masses, spins, distance)
- dKs looks fine - dKs looks fine
- S191204r - S191204r
- Mc-q prior transformation to m1-m2 has to be checked. (like all other events LAPLACE complaints about mtotal railing) - Mc-q prior transformation to m1-m2 has to be checked. (like all other events LAPLACE complaints about mtotal railing)
...@@ -28,42 +42,45 @@ Compare to other events, there is more difference b/w BBH and dKs runs (masses, ...@@ -28,42 +42,45 @@ Compare to other events, there is more difference b/w BBH and dKs runs (masses,
- Only event with mass prior issues not shown? - Only event with mass prior issues not shown?
## Results review readiness ## Results review readiness
### Results review: ### Results review:
1. The config file review readiness requires the following: 1. The config file review readiness requires the following:
1. Link config files of each event from the event wiki page 1. Link config files of each event from the event wiki page
2. Link LOGIC output for each case: BBH-PE_config comparison and SIQM-PE_config comparison 2. Link LOGIC output for each case: BBH-PE_config comparison and SIQM-PE_config comparison
3. Each event table should have one or more columns for the reviewer's comments on the config files. 3. Each event table should have one or more columns for the reviewer's comments on the config files.
2. The results review readiness requires the following: 2. The results review readiness requires the following:
1. BBH and SIQM posteriors (make cbcBayesPostProc and SummaryPages). SummaryPages should have config, PSD, Calibration files, etc. The 'label' used should be the same for all the events. 1. BBH and SIQM posteriors (make cbcBayesPostProc and SummaryPages). SummaryPages should have config, PSD, Calibration files, etc. The 'label' used should be the same for all the events.
2. Create BBH-PE_Run and SIQM-PE_Run comparison pages. Use SummaryPages or cbcBayesCompPos for this. 2. Create BBH-PE_Run and SIQM-PE_Run comparison pages. Use SummaryPages or cbcBayesCompPos for this.
3. Update the [summary_table](https://git.ligo.org/nv.krishnendu/lalsuite/-/wikis/O3b-analysis#summary-table) 3. Update the [summary_table](https://git.ligo.org/nv.krishnendu/lalsuite/-/wikis/O3b-analysis#summary-table)
4. Each event table should have one or more columns for the reviewer's comments on the posteriors. 4. Each event table should have one or more columns for the reviewer's comments on the posteriors.
## Numbers into the paper section: ## Numbers into the paper section:
- [ ] Bayes factors * [ ] Bayes factors
- [ ] Combined Bayes factors * [ ] Combined Bayes factors
- [ ] Combined bounds from restricted as well as HIR analysis * [ ] Combined bounds from restricted as well as HIR analysis
- [ ] Inclusion of a table with Q_GR and so on? * [ ] Inclusion of a table with Q_GR and so on?
## Plotting script ## Plotting script
- [ ] HIR analysis
- [ ] Which waveform to use for 190412 and 200115 (only two events with HMs?) for combined results? * [ ] HIR analysis
* [ ] Which waveform to use for 190412 and 200115 (only two events with HMs?) for combined results?
## Event list ## Event list
- [ ] Cross check again once the final PE results are available and try to avoid any bugs on event selection
- [ ] Make sure that no events left * [ ] Cross check again once the final PE results are available and try to avoid any bugs on event selection
* [ ] Make sure that no events left
## Review ## Review
- [ ] Event selection script, LAPLACE and LOGIC scripts
- [ ] Config files (along with the diff/LOGIC results) * [ ] Event selection script, LAPLACE and LOGIC scripts
- [ ] Available PE results * [ ] Config files (along with the diff/LOGIC results)
- [ ] Other plotting scripts * [ ] Available PE results
* [ ] Other plotting scripts
## PE ## PE
- [ ] Keep an eye on final PE status
- [ ] Status update on NSBH MCMC runs
- [ ] Start Bilby runs using Pv2 and compare results with LAL for Bilby review
* [ ] Keep an eye on final PE status
* [ ] Status update on NSBH MCMC runs
* [ ] Start Bilby runs using Pv2 and compare results with LAL for Bilby review
\ No newline at end of file