[mesa-users] v_flag

[Yevgeni Kissin]

Thank you Josiah and Rob,

Part of the reason I am confused about it is that it seems as if MESA
tracks radial velocity
regardless of the value of this flag. I am referring to the profile entry
'velocity'. Is the value
it gives when v_flag = .false. an approximation, rather than an explicit
calculation which it
only performs when v_flag = .true.?

Cheers,

Yevgeni Kissin
PhD Candidate
Canadian Institute for Theoretical Astrophysics
University of Toronto

On Thu, May 12, 2016 at 4:56 PM, Robert Farmer <rjfarmer at asu.edu> wrote:

> Hi
>
> > v_flag is one that I am confused about. I do not understand what it
> does, nor can I find an explanation of it in either
> > the star_job.defaults, or this mailing list. Can anybody provide me with
> a physical explanation as to what it does?
>
> The v_flag adds an additional equation to mesa to evolve, so that you can
> model the radial velocity of material (say when a star is collapsing )
>
> http://mesa.sourceforge.net/star_job_defaults.html#velocity_variables
>
>
> > And while I have your (collective) brains to pick, I am also surprised
> at the choice of overshoot parameters in this
> > inlist. Specifically, the choice of 0.001 for non_burn and h which is
> below the recommended value in the MESA
> > paper on massive stars, and 0 for he and z.
>
> The test suite should be considered good places to start a problem from,
> but do not define a "recommended" set of values. A better way to think
> about them is they define the options you should probably be considering
> when evolving a star  but not necessarily with those values.
>
> Rob
>
>
> On Thu, May 12, 2016 at 1:23 PM, Yevgeni Kissin <kissin at astro.utoronto.ca>
> wrote:
>
>> Dear MESA community,
>>
>> I am currently working on massive star evolution and am basing my model
>> on the 'inlist_massive_defaults' file, in
>> version 7503. There are plenty of flags explicitly included in this
>> inlist, some of which are simply set to the default.
>> But ignoring these, I am attempting to reduce the flags set to
>> non-default values, by understanding what each
>> represents.
>>
>> v_flag is one that I am confused about. I do not understand what it does,
>> nor can I find an explanation of it in either
>> the star_job.defaults, or this mailing list. Can anybody provide me with
>> a physical explanation as to what it does?
>>
>> And while I have your (collective) brains to pick, I am also surprised at
>> the choice of overshoot parameters in this
>> inlist. Specifically, the choice of 0.001 for non_burn and h which is
>> below the recommended value in the MESA
>> paper on massive stars, and 0 for he and z.
>>
>> Thank you very much,
>>
>> Yevgeni Kissin
>> PhD Candidate
>> Canadian Institute for Theoretical Astrophysics
>> University of Toronto
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Mobile security can be enabling, not merely restricting. Employees who
>> bring their own devices (BYOD) to work are irked by the imposition of MDM
>> restrictions. Mobile Device Manager Plus allows you to control only the
>> apps on BYO-devices by containerizing them, leaving personal data
>> untouched!
>> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
>> _______________________________________________
>> mesa-users mailing list
>> mesa-users at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/mesa-users
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20160512/9cd12d4e/attachment.html>