Data release (posterior samples, configuration files, run scripts, and frame data) for "Mitigating Systematic Errors in Parameter Estimation of Binary Black Hole Mergers in O1–O3 LIGO–Virgo Data"
收藏资源简介:
Dataset Description This dataset provides the complete set of data products used in the parameter estimation analyses presented in: "Mitigating Systematic Errors in Parameter Estimation of Binary Black Hole Mergers in O1-O3 LIGO-Virgo Data" It includes all materials required to reproduce the analyses, from configuration and execution scripts to posterior samples and detector strain data (for simulations). Contents The dataset includes: Configuration files for all analyses. Run scripts used to execute parameter estimation. Posterior samples for all runs (O1-O3 events and simulations). Simulated detector strain data in frame format (.gwf) Events Included The dataset covers the following binary black hole merger events: GW150914_095045 GW190412_053044 GW190521_030229 GW191109_010717 GW200129_065458 GW200208_222617 These events span the O1–O3 observing runs of the LIGO–Virgo Collaboration. Data Organization The dataset is structured into two top-level directories: o1o2o3_events/ Contains all the data products used in the analyses for real gravitational-wave events listed above. run_scripts/ Run scripts and configuration files organized by event. Each event directory contains subdirectories following the naming convention:{WAVEFORM_MODEL}_marginalized_polarizationThe {WAVEFORM_MODEL} can be IMRPhenomXPHM, IMRPhenomXO4a, or NRSur7dq4. Each subdirectory then contain the run script with following naming convention:run_{EVENTNAME}_{WAVEFORM_MODEL}_marginalized_polarization_{SAMPLER_SETTING}_nlive{NLIVE}_calibration-standard_{RUN_TYPE}.sh The {SAMPLER_SETTING} can take values dynesty_rwalk_v2, dynesty_rwalk_v3, or dynesty_rslice based on which sampler settings are used. The corresponding configuration files are provided.{NLIVE} represent number of live points used in that particular run.{RUN_TYPE} can take values baseline, cubicspline_absolute_wferrors, or cubicspline_relative_wferrors.Runs that make use of deglitched frame files, have -deglitched as suffix in the filename. Apart from the run script, each subdirectory contain the configuration file in a sub-folder named config_files. GW191109_010717 have single detector run scripts as well. These scripts can be found in the subfolder single_detector_runs in the event directory. posterior_files/Posterior samples corresponding to each analysis configuration, organized by event and waveform model. The names of the posterior files are self-explanatory. A typical filename follows the following naming convention:posterior_samples_combined_{EVENTNAME}_{WAVEFORM_MODEL}_{RUN_TYPE}_deglitched_frame_files.hdfor posterior_samples_combined_{EVENTNAME}_{WAVEFORM_MODEL}_{RUN_TYPE}_raw_frame_files.hdfdepending on which .gwf frame files are used: raw or deglitched (See the paper for details).The posterior samples are combined samples from multiple realization (2-3) for each run. The sampler settings are chosen in such a way that PE runs for multiple realizations are consistent. simulations/ This directory contains the data products for GW191109-type signal injected in a detector network consisting of LIGO-Hanford and LIGO-Livingston detectors (H1 and L1 for short). In another scenario, we inject a scatter light glitch close to the signal in LIGO-Livingston detector. The run scripts, configuration files, and frame files along with posterior samples are provided in this folder.



