[mesa-users] terminate because of overflowing initial model

Ying Qin Ying.Qin at unige.ch
Mon Aug 24 15:22:26 EDT 2015


Hi Pablo,

Thank you so much for your answer, and I want to bother you again.
I have been trying to run mesa by replacing your run_star_extras.f and referring to inlist1. As you all said, this actually results in convergence problem.
The first question about the run_star_extras.f, I checked the WR wind, and found:
      if(log10_cr(Lsurf/Lsun) > 4.5) then
             w = -11.95+1.5*log10_cr(Lsurf/Lsun)-2.85*Xs
         else
             w = -35.8+6.8*log10_cr(Lsurf/Lsun)
         end if
so can you tell me why you add this term ‘-2.85*Xs’ ? Because it is not shown in Detmers et al. 2008.


Although I know mesa stops by convergence problem, I check the evolution of log_abs_mdot and find that it is different from the result in Fig 1 from Detmers et al. 2008.
So I think it should be my incorrect understanding of mesa using, and now I clarify my motivation clearly and show the corresponding settings in inlist_project or inlist1 respectively.
I want to compute the evolution of Wolf- Rayet binaries(WR companion is approximated as a point mass). About the binaries, I need to consider FIVE factors, including
the tidal angular momentum exchange, different rotation of the Wolf-Rayed star, internal magnetic fields, stellar wind mass loss, and mass transfer.
M1 = 10, M2 = 1.4, P = 4.8 hrs, and add the WR wind(It is answered in last email)

Setting from inlist_project and inlist1
1. Tidal angular momentum exchange (included in &binary_controls of inlist_project)

              do_tidal_sync = .true.
       do_initial_orbit_sync_1 = .true.
       sync_type_1 = “Hut_rad"

2.  Rotation of WR star(include in &star_job of inlist1)
      !Rotation
      change_rotation_flag = .true.
      new_rotation_flag = .true.
      change_initial_rotation_flag = .true.

      set_surface_rotation_v = .true.
      set_initial_surface_rotation_v = .true.
      new_surface_rotation_v = 200 ! km/sec
3. internal magnetic fields (included in &controls of inlist1)

        !Magnetic field
      am_nu_visc_factor = 1
      am_D_mix_factor = 0.0333333333333333d00
      D_DSI_factor = 0
      D_SH_factor = 1
      D_SSI_factor = 1
      D_ES_factor = 1
      D_GSF_factor = 1
      D_ST_factor = 1

4. stellar wind mass loss (included in &controls of inlist1)

        !Wind
      RGB_wind_scheme = 'Dutch'
      AGB_wind_scheme = 'Dutch'
      RGB_to_AGB_wind_switch = 1d-4
      Reimers_wind_eta = 0.5


5. mass transfer (included in &binary_controls of inlist_project)

      mdot_scheme = “Ritter"

So could you please give me some comments about my settings for the five factors and explain why I got the different result(evolution of log_abs_mdot) Fig 1 from Detmers et al. 2008(in attachment) ?

Thanks for your patient reading in advance, and I am looking forward to your answers to update my understanding.

With my best regards,
Ying

On 23 Aug 2015, at 23:58, Pablo Marchant <pamarca at gmail.com<mailto:pamarca at gmail.com>> wrote:

Ying, I happen to have the implementation for that wind prescription, as it was used for some of the models in the last MESA paper (paxton et al. 2015 in case you haven't seen it) that reproduce the results of Wellstein & Langer 1999. You can download the required inlists and run_star_extras.f from

http://mesastar.org/results/mesa-iii-instrument-paper-inlists

The files you need are in the folder section2_binaries/6_massive_binary of the compressed file. Just copy the inlists into your work directory and the run_star_extras.f into the src folder of your work directory, and do a ./clean and a ./mk to recompile. Please go through the run_star_extras.f to understand what is being done, the code essentially switches to the prescription you want when X<0.4 at the surface, and uses the wind scheme defined in the inlist otherwise.

And regarding the error, it's just what Rob says, your system is too compact and one model is above its Roche lobe radius. You can remove the terminating condition by setting

terminate_if_initial_overflow = .false.

in the &binary_controls section of inlist_project, but this will likely result in convergence problems as you would obtain a very large mass transfer rate, and even if it works, results might not make much sense. So, I don't recommend you do this, just start with a longer orbital period.

On Sun, Aug 23, 2015 at 11:45 PM, Robert Farmer <rjfarmer at asu.edu<mailto:rjfarmer at asu.edu>> wrote:
Hi
You get this error becuase the first time step your star1 will be roche lobe overflowing. Try increasing the intial period such that the first step wont transfer mass.

Rob

On Sun, Aug 23, 2015 at 2:29 PM, Ying Qin <Ying.Qin at unige.ch<mailto:Ying.Qin at unige.ch>> wrote:
Hi mesa users,

I want to computer the evolution of close Wolf-Rayet binaries(The WR companion is approximated as a point mass), including tidal angular momentum exchange, different rotation of the Wolf-Rayet star, internal magnetic fields, stellar wind mass loss, and mass transfer.

1. About the tidal angular momentum exchange, I add the following lines in inlist_project
   do_tidal_sync = .true.
   do_initial_orbit_sync_1 = .true.


2. I also added the rotation and magnetic fields in inlist1, please see them in  inlist1.


3. The mass loss of WR star is calculated according to Hamann et al. 1995 and and Hanann et al.1982.

          log(Mdot/Msun yr^-1) =  eta * (-11.95 + 1.5logL/Lsun ),  where logL/L_sun > 4.5(Hamann et al. 1995)

          log(Mdot/Msun yr^-1) =  eta * (-35.8 + 6.8logL/Lsun ),  where logL/L_sun < 4.5(Hamann et al. 1982)

I know other winds are used in mesa,  but can I bother you to tell me how to use this wind mass loss.

4. About mass transfer, I chose mdot_scheme = “Kolb” in inlist_project.

I tried to use 'Dutch wind’ , not the wind I listed above,  to run mesa, but it stopped with error:
termination code: Terminate because of overflowing initial model


In the attachment are my inlist1 and inlist_project, any comments are kindly welcome, and thank you in advance!
If possible, could you please explain them clearly, because I am learning to use mesa.

Ying


------------------------------------------------------------------------------

_______________________________________________
mesa-users mailing list
mesa-users at lists.sourceforge.net<mailto:mesa-users at lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/mesa-users



------------------------------------------------------------------------------

_______________________________________________
mesa-users mailing list
mesa-users at lists.sourceforge.net<mailto:mesa-users at lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/mesa-users




--
Pablo Marchant Campos
M.Sc on Astrophysics, Universidad Católica de Chile
PhD student, Argelander-Institut für Astronomie

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20150824/29da0474/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1.pdf
Type: application/pdf
Size: 20644 bytes
Desc: 1.pdf
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20150824/29da0474/attachment.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: aap2008Detmers.pdf
Type: application/pdf
Size: 373163 bytes
Desc: aap2008Detmers.pdf
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20150824/29da0474/attachment-0001.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: inlist_project
Type: application/octet-stream
Size: 1211 bytes
Desc: inlist_project
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20150824/29da0474/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: inlist1
Type: application/octet-stream
Size: 1312 bytes
Desc: inlist1
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20150824/29da0474/attachment-0001.obj>


More information about the Mesa-users mailing list