Skip to content

Update code for PESummary v0.1.7

Charlie Hoy requested to merge charlie.hoy/lalsuite:pesummary_v0.1.7 into master

Summary

Update lalinference_pipe_utils.py and lalinference_pipe.py for PESummary v0.1.7 @vivien

Description

I have added two new options to resultspage section in lalinference_pipe_example.ini. These options are plot-strain-data= and labels. If the plot-strain-data is passed and the results page executable is summarypages, then the data around merger and the maxL waveform is plotted (see MR 89 for PESummary).

The labels argument can either be a single string or a comma separated list and is only used if the results page executable is summarypages. If it is a single string, then this is passed directly to the summarypages executable. If it is a comma separated list, then I have edited the add_variations and generate_variations functions in lalinference_pipe.py so labels corresponding to that particular variation are passed to the specific config file.

I am currently running tests for the following examples:

  • running lalinferencenest with the summarypages executable and a single approximant
  • running lalinferencemcmc with the summarypages executable and a single approximant
  • running lalinferencenest with the cbcBayesPostproc executable and a single approximant
  • running lalinferencemcmc with the cbcBayesPostProc executable and a single approximant
  • running lalinferencenest with the summarypages executable and coherence test and a single approximant
  • running lalinferencenest with the summarypages executable and 2 approximants
  • running lalinferencemcmc with the summarypages executable and 2 approximants
  • running lalinferencenest with the cbcBayesPostProc executable and 2 approximants
  • running lalinferencemcmc with the cbcBayesPostProc executable and 2 approximants
  • running lalinferencenest with the summarypages executable and coherence test and a 2 approximants

I can add the lalinference.sh files for these examples below in the discussion.

API Changes and Justification

Backwards Compatible Changes

  • This change introduces no API changes
  • This change adds new API calls

Backwards Incompatible Changes

  • This change modifies an existing API
  • This change removes an existing API

Review Status

Edited by Ghost User

Merge request reports