Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update of resampling methods #348

Merged

Conversation

haukekoehn
Copy link
Contributor

Added maximum-mass-constraint as a command, so one can sample from a joint GW+EM posterior and get an upper limit on the TOV mass.

The TOV solver here is different from the ones already present in
eos/tov.py, because here we are interested in the density profile of the
star, whereas the other only provides bulk properties.

Conversion factors are now fixed to astropy values.

haukekoehn added 2 commits March 25, 2024 13:23
correlation between chirp mass and mass ratio.

Added maximum-mass-constraint as a command, so one can sample from a
joint GW+EM posterior and get an upper limit on the TOV mass.
… correlation between chirp mass and mass ratio (and potentially spin in NSBH systems).

Added maximum-mass-constraint as a command, so one can sample from a joint GW+EM posterior and get an upper limit on the TOV mass.

The TOV solver here is different from the ones already present in
eos/tov.py, because here we are interested in the density profile of the
star, whereas the other only provides bulk properties.

Conversion factors are now fixed to astropy values.
@haukekoehn
Copy link
Contributor Author

you can find a test on the Potsdam cluster at /home/aya/work/hkoehn/EOS_analysis/inference_multimessenger/perlmutter/maximum_mass_test

@mcoughlin mcoughlin requested a review from tsunhopang March 25, 2024 16:52
@tsunhopang
Copy link
Collaborator

No, I meant a CI test within the nmma repo

@haukekoehn
Copy link
Contributor Author

ah ok, like in nmma/tests?

@tsunhopang
Copy link
Collaborator

Yes, you can check nmma/tests/analysis.py as an example

@haukekoehn
Copy link
Contributor Author

I think this should work now 🤞

@mcoughlin
Copy link
Member

@haukekoehn I think usually we don't keep the EOS suite in NMMA directly. I think a better test would just be the same test but with the first 10 EOSs.

@tsunhopang
Copy link
Collaborator

tsunhopang commented Mar 27, 2024

Indeed, a full EOS set is way too big for nmma, especially if it is for testing only. I agree with @mcoughlin that 10 EOS should be sufficient

@haukekoehn
Copy link
Contributor Author

Sure (it was already reduced from 25k EOS originally :D) I would also add some documentation probably.

Is there anywhere some info/guidelines how these tests should look like? Because i guess they should mainly show that the code runs and not produce any meaningful results?

Copy link
Collaborator

@tsunhopang tsunhopang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@tsunhopang tsunhopang merged commit 26b30af into nuclear-multimessenger-astronomy:main Mar 28, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants