From: Pablo M. <pa...@gm...> - 2017-07-18 23:31:03
|
Apparently, you are using the default inlist_zams_specification which only produces a model for a single mass, 20 Msun. This is set by the options mlo = 1.30102999566398d0 mhi = 1.30102999566398d0 dmass = 0.6d0 in that inlist, where mlo and mhi are the logarithm of the masses to be included in the ZAMS file, and dmass is the logarithmic interval between models. So your binary model runs into problems trying to initiate with different initial masses, because the ZAMS file only provides one mass. Actually, if I switch in your inlist project m1=20 and m2=20, it works without problems. The reason the default in the test_suite has those values is just because its a test, what you really want is to sample multiple masses to create your ZAMS models. This is something you only have to do once for a choice of composition, then you can reuse the saved models permanently by putting it in $MESA_DIR/data/star_data/zams_models/. In particular for some of my models I do ! do masses 10**lgm, for lgm = mlo to mhi by dmass mlo = 0 mhi = 2 dmass = 0.02d0 This will take a while, as it has to compute 100 stellar models, but as I said, this is a thing you do only a very limited amount of times. Cheers On Tue, Jul 18, 2017 at 4:22 PM, Talha Irfan <tlh...@gm...> wrote: > I've attached a couple of the more recent models I've been using. The file > 'z1d_2.data' is the most recent, and the one which I was testing with the > inlists from earlier. > > Best, > Talha > > Talha Irfan Khawaja > Physics '19 > Georgia Institute of Technology > > On 18 July 2017 at 15:56, Pablo Marchant <pa...@gm...> wrote: > >> Hi Talha, >> >> can you provide your zams models as well to avoid having to recompute >> them? >> >> On Jul 18, 2017 1:57 PM, "Talha Irfan" <tal...@ga...> wrote: >> >>> Hi everyone, >>> >>> I've been using MESA to investigate population II and III stars by >>> controlling this intial_z value for singular stars. This was working fine >>> until I moved to the binary case, where I used the second set of >>> instructions from this >>> <https://sourceforge.net/p/mesa/mailman/message/34896105/> post to >>> create my own ZAMS model with certain initial_z values, then matching that >>> in the inlists from the binary work folder. >>> >>> I've been having problems trying to evolve the system, even if I set >>> evolve_both_stars to false (after initially trying true). The first >>> termination code read "Terminate because of overflowing initial model", so >>> I tried increasing the initial period as some users had suggested, and >>> later tried setting ignore_rlof to true, both of which resulted in failure >>> to find a suitable model. I'm not really sure where to go from here, so >>> I've attached my inlists (the only ones I edited) and the >>> inlist_zams_specification I used. I'd greatly appreciate any help with this. >>> >>> Thanks! >>> >>> >>> Talha Irfan Khawaja >>> Physics '19 >>> Georgia Institute of Technology >>> >>> >>> ------------------------------------------------------------ >>> ------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>> _______________________________________________ >>> mesa-users mailing list >>> mes...@li... >>> https://lists.sourceforge.net/lists/listinfo/mesa-users >>> >>> > -- Pablo Marchant Campos M.Sc on Astrophysics, Universidad Católica de Chile PhD on Astrophysics, Argelander-Institut für Astronomie, Universität Bonn |