Skip to content

Resolves an issue that appeared in #1305 with some TPAGB stars in the ECSN range (but not satisfying ECSN conditions) exploding as CCSNe#1400

Merged
ilyamandel merged 4 commits into
devfrom
Matlab
Jun 19, 2025
Merged

Resolves an issue that appeared in #1305 with some TPAGB stars in the ECSN range (but not satisfying ECSN conditions) exploding as CCSNe#1400
ilyamandel merged 4 commits into
devfrom
Matlab

Conversation

@ilyamandel

Copy link
Copy Markdown
Collaborator

In #1305, I tried to address a situation where TPAGB stars entered the ResolveSupernova() function but were not, in fact, supposed to explode in a supernova because they did not satisfy the ECSN criteria (most likely because --allow-non-stripped-ECSN was false). Prior to that fix, we allowed these to become white dwarfs, but that created problems such as the impact of a sudden mass change associated with instantaneous envelope removal from the binary (e.g., a Blaauw kick, a non-conservation of a*M, etc.). In that fix, I opted to treat all systems that did not qualify for ECSN as regular core-collapse SNe. However, as @pauldisberg pointed out, this created a different set of problems, such as an abundance of low-kick NSs forming from stars that really should not have experienced CCSNe at all. In this update, I am fixing the treatment properly, by modifying the calculation of whether a star should go supernova to return false in cases when neither the ECSN nor CCSN criteria are satisfied. To achieve this, I added a new parameter (threshold mass, generally expected to be MCH or MECS) to CalculateCoreMassAtSupernova_Static(). I also removed McSN from GBParams, instead computing it on the fly when needed.

Finally, I cleaned up documentation in a couple of places, such as adding output column descriptions directly to Quick Links for easier navigation.

I am also starting to upload some more Matlab post-processing scripts; these do not require review (and are still works in progress).

@ilyamandel ilyamandel changed the title Fix to #1305 Resolves an issue that appeared in #1305 with some TPAGB stars in the ECSN range (but not satisfying ECSN conditions) exploding as CCSNe Jun 18, 2025

@jeffriley jeffriley left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Looks good - approved

@ilyamandel

Copy link
Copy Markdown
Collaborator Author

Just to prove that all is still well with conservation of a*Mtot for binaries making WDs without tides, GWs, or mass transfer (plot made with latest code version):

image

@pauldisberg pauldisberg left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Approved: NS kick distributions look good, the peak caused by stars that would have gone ECSN if they were stripped but now undergo CCSNe is reduced.

@ilyamandel

Copy link
Copy Markdown
Collaborator Author

Thanks, @pauldisberg ! If you happen to have a plot showing the impact of this change (say, the single NS kick distributions before and after the change with default assumptions, i.e., without allowing for ECSNe from non-stripped donors), could you post it here -- useful to have such information handy when we try to remember a year later why we made this change. :-)

@ilyamandel
ilyamandel merged commit c12800a into dev Jun 19, 2025
3 checks passed
@ilyamandel
ilyamandel deleted the Matlab branch June 19, 2025 02:00
@pauldisberg

pauldisberg commented Jun 19, 2025

Copy link
Copy Markdown
Collaborator

v_kick_comparison
As requested: the kick distributions for individual NSs (through ./COMPAS -n 100000 --mode SSE --random-seed 1714388113). The figure shows interpolated histograms with bins of 10 km/s, for varying v_NS and sigma_kick (Mandel & Müller 2020), for the COMPAS version before Ilya's fix (v03.20.02) and the version after Ilya's fix (cf. Fig. 2 of Kapil et al. 2023).

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