[Mesa-users] Question

[Being Unique]

Hi~
Sorry for bothering again.

In the example_make_pre_ccsn, what is the difference between inlist_common
and inlist_convert, why Ione of its nitial_mass is 14 and another is 13.0?

And in the inlist_before_remove, it set

      xa_central_lower_limit_species(1) = 'he4'

      xa_central_lower_limit(1) = 1d-6

Why is that set in this way?

By the way, where and what kinds of the result of test_suite case
example_make_pre_ccsn should be put in the example_ccsn_IIp?

Thanks a lot.


Albert

Jared Goldberg <goldberg at ucsb.edu> 於 2018年12月24日 週一 上午10:56寫道：

> Hi Albert (and other interested Mesa users),
>
> Instead of having one run controlled by one inlist, example_ccsn_IIp
> chains together various inlists in a sequence. Take a look at the rn
> script. This will tell you the order they run in. Notice how it calls rn1,
> a script that is nearly identical to the regular rn script you’d find in
> $MESA_DIR/star/work. Note also that example_ccsn_IIp does NOT make a red
> supergiant. It starts with a red supergiant and blows it up.
>
> Loosely speaking, inlist_edep is the inlist that controls the “explosion
> itself” — it tells MESA to inject energy in the innermost region of the
> star until the star reaches a total final energy that you specify (a
> positive number typically on the order of 10^51 ergs). This will create the
> shock that travels through the star’s envelope in shock_part1-4.
>
> You could in principle add rotation settings in any of the steps, although
> some of them may have more problems with rotation than others.  If you want
> to set rotation controls (or any other controls) that are active throughout
> the entire explosion up until shock breakout, set them in the files
> inlist_controls and inlist_star_job, which are called at the same time as
> other inlists which govern specific “steps” in the explosion
> (inlist_*part*). Then double check that the same rotation controls are not
> being reset in the other inlist_part_*.
>
> I am still unsure if rotation can be implemented simply in
> example_ccsn_iip without causing MESA to crash, but you’re more than
> welcome to try! For my purposes I have generally considered models without
> rapid rotation, which we can approximate as non-rotating on the ~1-day
> timescale from core collapse to shock breakout. In many cases, this is
> fine, as the relevant effects of rotation often occur when *making the red
> supergiant* (e.g., by modifying the test_suite case example_make_pre_ccsn),
> where rotation can be turned on more simply. Then, that red supergiant
> model could be used as the input model in inlist_part_infall in
> example_ccsn_IIp.
>
> Hope this is somewhat helpful. Let us know if you have any other
> questions. I’m eager to hear of your success in this endeavor.
>
> Cheers,
> ~Jared
>
>
>
> On Dec 23, 2018, at 1:04 AM, Being Unique via Mesa-users <
> mesa-users at lists.mesastar.org> wrote:
>
> Hello MESA-Users,
>
> Does inlist_edep in the test_suite example_ccsn_IIp mean the star model's
> setting before explosion?
> And is that able for me to add rotation settings in the inlist_edep in the
> test_suite example_ccsn_IIp?
>
> Many thanks !
>
> Albert
>
> _______________________________________________
> mesa-users at lists.mesastar.org
> https://lists.mesastar.org/mailman/listinfo/mesa-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20181225/bbfa7dc8/attachment.html>