MESAHub / MESAHub/mesa

running MESA+STELLA

Open
#793 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Fortran
Stars
249
Forks
82
Avg merge
1d 3h
Merged PRs (30d)
3

Description

This is probably a basic question, but I could not find in the documentation the information I was searching.

I'm trying to run some MESA+ STELLA models to get SNIIP light curve following Goldberg et al 2019, but the test_suite have changed names with the MESA version.
I'm using MESA version 24.08.01

My understanding is that I could try to run 2 different test_suit and then STELLA using the output of the previous stage as input for the next stage. In particular I was trying to use:

- 12M_pre_ms_to_core_collapse to evolve the star until pre-collapse
- ccsn_IIp: give as input the "final.mod" profile from previous step to follow the collapse with ccsn_IIp
- STELLA: use the output from ccsn_IIp (mesa.abn, mesa.hyd) as input for STELLA.

However, while this is working for 9-14 solar masses does not seems to succeed for larger masses. I'm not exploring too many parameters at the moment. I'm just changing mass and mass loss (eta ).
So while I'm still trying to understand the pattern of different error I'm getting, my main question is more to understand if I'm "starting correctly". If this is the way of go from ZAMS to collapse and then Stella.
And In particular, if for larger masses it would be better to start from the test_suite case 20M_pre_ms_to_core_collapse.

thanks
s.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the documentation and the test_suite cases named 12M_pre_ms_to_core_collapse, 20M_pre_ms_to_core_collapse, and ccsn_IIp, along with the STELLA inputs mesa.abn and mesa.hyd. Determine whether the proposed ZAMS-to-collapse-to-STELLA workflow is supported and whether the larger-mass behavior needs clarification. Done means documenting the correct workflow, relevant case selection, and any known limitations or errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
fortran
Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.