[mesa-users] (resending)Questions about loading of the zams models

Bill Paxton paxton at kitp.ucsb.edu
Wed Feb 26 16:15:08 EST 2014

On Feb 26, 2014, at 12:53 PM, 이현택 wrote:
>  I have one more question about these zams or zahb models.
>  As you suggested I tested the create_zams test suite. And the result is 2 out put files. one is _mod.data and the other one is .data file.
>  Why do we need these 2 result files instead of one?

The "_mod.data" file is a temporary to hold model data while the code constructs the full set of zams models.
The ".data" file is the real thing -- it has an index at the start, followed by the model data copied from the "_mod.data" file.

> In the other test_suite case, if the test run need sum premade data, it usually uses .mod file instead of the .data file.
> Is there any reason that we have to use the different formats for premade data?

The zams data files typically contain a range of masses to enable interpolation to any requested mass.   For example, the zams_z2m2_y28.data file has 32 models over masses from 0.08 to 100 Msun.  Then if you request a 1.3 Msun zams model, it interpolates using the 1.25892541 Msun and 1.58489319 Msun models from the data file.    This can be useful if you plan a project that will explore many zams masses for the same Y and Z.

In addition to zams starting models, you can either create a pre-main-sequence model or use a model you have saved from a previous run.  Those are typically named using ".mod" as you have noticed.  The actual model format is identical in terms of columns of data, etc.  The main difference is that the zams files bundle together many different masses to support interpolation.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20140226/ea0dd5cd/attachment.html>

More information about the Mesa-users mailing list