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
Conversation
jeffriley
approved these changes
Jun 18, 2025
jeffriley
left a comment
Collaborator
There was a problem hiding this comment.
Looks good - approved
Collaborator
Author
pauldisberg
approved these changes
Jun 19, 2025
pauldisberg
left a comment
Collaborator
There was a problem hiding this comment.
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.
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. :-) |
Collaborator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


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).