POSYDON-code / POSYDON-code/POSYDON
[FEATURE]: SN_type defintion to distinguish between failed and successful SNe
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 45
- Forks
- 37
- Avg merge
- 8d 20h
- Merged PRs (30d)
- 5
Description
Right now we use "WD", "ECSN", "CCSN", "P(P)ISN" but there are ideas to be able to say
"ECSN", "succ_CC", "failed_CC"
minor: we can maybe even change the namins "SN_type" to sth like "End_outcome" (taking into account that maybe do not have a SN, and maybe not even a core-collapse for low masses)
THis is connected with #786 Maltsev+2025 prescription too, where there is the possibility for SN with BH formation.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing SN_type definition and the related Maltsev+2025 prescription in issue #786. Resolve whether the outcome should distinguish successful and failed core-collapse supernovae, account for black-hole formation, and be renamed to End_outcome; done means the project has an agreed definition and terminology.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100