- GW170403 et al. Five events in total (launched six actually, but 190719 run failed). Rerun because the above runs hit the boundary, Amu was not wide enough or used mass1/mass2 parametrization rather than mchirp-q, and so on) Posterior [here](https://www.atlas.aei.uni-hannover.de/work/yifan.wang/projects/jianyan/rerun/170403_6events/3ogc-parity_output/html/)
- Two BNS events [GW190425](https://www.atlas.aei.uni-hannover.de/work/yifan.wang/projects/jianyan/rerun/BNS/bns-parity_output/html/) and [GW170817](https://www.atlas.aei.uni-hannover.de/work/yifan.wang/projects/jianyan/rerun/BNS/170817html/3._posteriors/3.01_gw170817_124104_dy5k/)
- GW190725 [here](https://www.atlas.aei.uni-hannover.de/work/yifan.wang/projects/jianyan/rerun/BBH/3ogc-parity_output/html/6._config_files/6.01_gw190725_174728/). Rerun because H1 only has data 11s prior to the merger, thus need to make f_lower = 41
- GW190413_134308 [here](https://www.atlas.aei.uni-hannover.de/work/yifan.wang/projects/jianyan/rerun/190413/3ogc-parity_output/html/)(use the default dynesty setting run, because the rwalk2 seems to hit the boundary again). Rerun because the distance in previous run hit the boundary
- Besides the above run, use the results in [here](https://www.atlas.aei.uni-hannover.de/work/yifan.wang/projects/jianyan/allevents/3ogc-parity_output/html/) for the rest of events. Actually, this was the initial attempt, all the above are reruns which are based on drawbacks in this run.
