[mesa-users] ZAMS - abundances

[Aaron Dotter]

Hi Jakub,

Have a look at mesa/star/test_suite/create_zams/src/run_star_extras.f,
specifically subroutine do_create_zams.  From there, grep is your friend.
Or ack, if you prefer.

Follow the progression of subroutine and function calls back to the star
module, with files in star/private and star/public.  Most of the star data
type parameters are left as the defaults but it would certainly be possible
to add these values to of the create_zams inlist.  See what's being set and
what isn't, and decide what *you'd* like to set and how you'd like to set
it.  This is a great mental exercise.

It would be great if you would make create_zams more flexible and
up-to-date!

Aaron

On Wed, Jul 13, 2016 at 1:07 PM, Jakub Ostrowski <
ostrowski at astro.uni.wroc.pl> wrote:

> Hi,
>
> I’d like to understand how abundances are treated when a ZAMS file is
> loaded. Let me carefully explain what I mean.
>
> Let’s assume I want to create a new ZAMS and I’m not happy with the
> default choice of Z fractions. Modification of inlist_create_zams allows me
> to change metal fractions (by the way - it’s 2016, why GS98 is still
> default?) so the calculations could be more suitable for real projects. As
> a result, we could obtain nice PMS models with uniform composition and the
> metal mixture of choice, let’s say AGSS09. It’s awesome at this point, but
> when ZAMS is saved we are left with a file that contains abundances for
> only 8 species from the basic net. And here we got a problem: we load our
> shiny new ZAMS into our model and we got abundances we wanted for 8
> species. What about the rest of the metals? I’m sure they’re not from
> AGSS09. How are they loaded? Where can I found the suitable piece of code
> (if I was able to find it I wouldn’t write this mail ;-) )?
>
> Thank you for any guidance and cheers,
> Jakub
>
>
>
> ------------------------------------------------------------------------------
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20160713/6fe60bdd/attachment.html>