[mesa-users] how to definite surface?

Bill Paxton paxton at kitp.ucsb.edu
Wed Jun 15 00:08:54 EDT 2016


Rather than reporting the value for a single cell, the "surface" value is an average over a specified fraction of the mass of the model.  A similar operation is done for "center" values -- they are also averages.  You can control the size of the averaging regions by changing these controls in your inlist:

         !### center_avg_value_dq

         ! reported center values are averages over this fraction of star mass

      center_avg_value_dq = 1d-8

         !### surface_avg_abundance_dq

         ! reported surface abundances are averages over this fraction of star mass

      surface_avg_abundance_dq = 1d-8

If you want the history values to match the single innermost (or outermost) cell, set the abundance dq to 0d0.


On Jun 14, 2016, at 8:38 PM, 熊赫然 wrote:

> Dear all,
> I try to understand the surface abundance for comparing with observational data. So i employ the zone's information in profiles.data and mass fractions near surface in history.data (e.g. surface h2, surface h4, etc.). But the  two groups of data are different. My question is how do mesa definite these surface __ in history.data and which group is proper to compare with observation.
>                                                                                                                                                                       &nb sp;                                                                                                                                      With kind regards
>                                                                                                                                                                                                                                                                                                              Heran Xiong
> ------------------------------------------------------------------------------
> 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://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381_______________________________________________
> mesa-users mailing list
> mesa-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mesa-users

More information about the Mesa-users mailing list