|
|
|
# Mass Gap
|
|
|
|
|
|
|
|
## Development teams
|
|
|
|
|
|
|
|
Sushant Sharma Chaudhury, Deep Chatterjee
|
|
|
|
|
|
|
|
|
|
|
|
## Reviewers and sign-off
|
|
|
|
|
|
|
|
|
|
|
|
| Reviewer | Status | version/tag | Sign-off hash |
|
|
|
|
| ----------- | ------- | --------------------- | ------------- |
|
|
|
|
| M. Coughlin | ongoing | ligo.em-bright v1.1.0 | :x: |
|
|
|
|
| S. Antier | ongoing | ligo.em-bright v1.1.0 | :x: |
|
|
|
|
|
|
|
|
## Supervisions and associated LIGO-Virgo-Kagra groups
|
|
|
|
|
|
|
|
- Low-latency group and CBC group
|
|
|
|
- Shaon Ghosh, Roberto De Pietri, Soichiro Morisaki
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## Review charge
|
|
|
|
|
|
|
|
## Deliverables
|
|
|
|
|
|
|
|
|
|
|
|
1. Reviewers must ensure compatibility of all new codes related to mass-gap and existing codes (the version of EM bright validated on Jan 2022 with EOS Marginalization + changes for compatibility of external packages) with the Python version (3.8 and 3.9 for the production code and 3.10 for the testing) to be used by GWcelery (another merge-request is made to include the EM-Bright package with HasMassgap) --> Approved with Shaon
|
|
|
|
Need to check if the pickle files produced by the package is readable by the GWCelery task that will be running in low-latency system → this has been already checked, see this example --> under discussion
|
|
|
|
|
|
|
|
2. Reviewers will set up acceptance criteria for the MassGap probabilities accuracy to be included in the 4th observing run. The reviewers will then enforce this requirement via the O3 MDCs (below 8) --> under discussion
|
|
|
|
|
|
|
|
3. Reviewers will review the software documentation after task 2, testing (under discussion) and deployment procedure
|
|
|
|
|
|
|
|
3. Reviewers will ensure the configuration control as delineated in the following RODA document is followed during the O4 run.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## Step-wise installation of packages:
|
|
|
|
1. Clone the repository in a desired directory.
|
|
|
|
```
|
| ... | ... | @@ -50,25 +89,6 @@ This outputs (p_NS, p_EMB, p_massgap) |
|
|
|
2. High mass data analysis [Notebook](https://git.ligo.org/emfollow/em-properties/mass_gap/-/blob/main/high_mass_artifact_study.ipynb)
|
|
|
|
3. Parameter grid search [Notebook](https://git.ligo.org/emfollow/em-properties/mass_gap/-/blob/main/mass_gap_grid_search.ipynb)
|
|
|
|
|
|
|
|
## Deliverables
|
|
|
|
|
|
|
|
|
|
|
|
1. Reviewers must ensure compatibility of all new codes related to mass-gap and existing codes (the version of EM bright validated on Jan 2022 with EOS Marginalization + changes for compatibility of external packages) with the Python version (3.8 and 3.9 for the production code and 3.10 for the testing) to be used by GWcelery (another merge-request is made to include the EM-Bright package with HasMassgap) --> Approved with Shaon
|
|
|
|
Need to check if the pickle files produced by the package is readable by the GWCelery task that will be running in low-latency system → this has been already checked, see this example --> under discussion
|
|
|
|
|
|
|
|
2. Reviewers will set up acceptance criteria for the MassGap probabilities accuracy to be included in the 4th observing run. The reviewers will then enforce this requirement via the O3 MDCs (below 8) --> under discussion
|
|
|
|
|
|
|
|
3. Reviewers will review the software documentation after task 2, testing (under discussion) and deployment procedure
|
|
|
|
|
|
|
|
3. Reviewers will ensure the configuration control as delineated in the following RODA document is followed during the O4 run.
|
|
|
|
|
|
|
|
## Sign-off
|
|
|
|
|
|
|
|
|
|
|
|
| Reviewer | Status | version/tag | Sign-off hash |
|
|
|
|
| ----------- | ------- | --------------------- | ------------- |
|
|
|
|
| M. Coughlin | ongoing | ligo.em-bright v1.1.0 | :x: |
|
|
|
|
| S. Antier | ongoing | ligo.em-bright v1.1.0 | :x: |
|
|
|
|
|
|
|
|
## Review Comments
|
|
|
|
|
| ... | ... | |
