[mesa-users] bad angular_momentum_j

[Pablo Marchant]

You are trying to get the turnover time for an outer convection zone,
right? I see you take the sum of dr/conv_vel for radii above

envelope_edge = max(s% conv_mx1_bot_r, s% conv_mx2_bot_r)

you should be careful as small convective regions can turn on and off, and
that can cause a sudden change on your turnover time. Do you know if you
are capturing the same convective zone all the time? What is the mass
coordinate corresponding to that? In particular, you have a system where,
if I have it right, a 1 msun star at TAMS is stripped by a mysterious
object (I'll guess a NS as you chose a mass of 1.4 msun) and goes down to
0.26 msun. Does this star even have a relevant outer convective zone left
at this point?

Check the structure of your star to see if what you are doing makes sense,
doing some Kippenhahn plots should be useful. In this note, it is very
useful if you actually summarize what is your initial setup, what your
model is doing, what you believe it should be doing, and at which point its
crashing,

Also quick comment

#########################################################
         if (turnover_time .lt. 0.0) then
             turnover_Time = 2.8d6
            ! If the turnover time is less than zero, set it so that the
            ! MB tt boost is 1
         end if
#########################################################

Why do you create a check to silently ignore something that should not
happen?

On Sat, Aug 13, 2016 at 3:32 AM, Kenny Van <kvan at ualberta.ca> wrote:

> Hi Josiah,
>
> Yes. there are sometimes oscillations in the results. I was trying to take
> the sum of all of the dr/conv_vel as the integral of dr/conv_vel in my code.
>
> On 12 August 2016 at 19:30, Josiah Schwab <jwschwab at berkeley.edu> wrote:
>
>> Hi Kenny,
>>
>> Isn't this the only way to calculate the convective turnover time though?
>>> It's normally calculated as
>>>
>>
>>>
>> integral from surface of star to bottom of convective envelope dr /
>>> convective velocity.
>>>
>>> I'm not sure how else to calculate this value except by taking
>>> dr/conv_vel in MESA
>>>
>>
>> Bill's point is that dr/conv_vel itself isn't a physical quantity,
>> because that's just a statement about the resolution.  The integral of
>> dr/conv_vel is a physical quantity, and should be resolution-independent in
>> a converged simulation.  Is the integral having large model-to-model jumps?
>>
>> Josiah
>>
>>
>
>
> ------------------------------------------------------------
> ------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning reports. http://sdm.link/zohodev2dev
> _______________________________________________
> mesa-users mailing list
> mesa-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mesa-users
>
>


-- 
Pablo Marchant Campos
M.Sc on Astrophysics, Universidad Católica de Chile
PhD student, Argelander-Institut für Astronomie
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20160813/cba2dc7f/attachment.html>