From: Catherine L. <clo...@mt...> - 2017-03-21 18:43:36
|
Hi everyone, I'm trying to run some rotating models (1.2-2.2 solar masses), and I've run into a problem. For now, I'm trying to include rotation in the simplest way possible, so I've got an inlist that has the following: &star_job show_log_description_at_start = .false. eos_file_prefix = 'mesa' kappa_file_prefix = 'gs98' change_v_flag = .true. new_v_flag = .true. new_rotation_flag = .true. change_rotation_flag = .true. relax_initial_surface_rotation_v = .true. set_surface_rotation_v = .true. new_surface_rotation_v = 100 / ! end of star_job namelist When I run a model, it starts out with whatever rotation rate I set on the last line, but around 30 models in, I see: turn on rotation new_surface_rotation_v = 4.5000000000000000D+01 3.7745766462731172D-05 and the rotation rate of my star drops. I can confirm that this is what happens when I plot omega or v as a function of the age of the star. The rotation velocity starts out where I set it, and then drops to close to 45 km/s and evolves from there. I get a surface rotation of 45 km/s for my model even if I comment all of the rotation commands out of my inlist, so it seems that my version of mesa is reading a velocity from somewhere else, or there's a default that isn't getting changed somehow. I've tried deleting all my inlists and making new ones, as well as recompiling the code, but the problem doesn't go away. Is there another rotation parameter I'm not setting, or another place I should be changing the rotation? I'm running version 8845 on a Mac OSX 10.9.5. Thanks, Catherine Catherine Lovekin Assistant Professor Department of Physics Dunn 222 Mount Allison University clo...@mt... phone: (506) 364-2582 |
From: Bill W. <wm...@ph...> - 2017-03-21 18:54:52
|
Hi Catherine, Is what you’ve pasted the contents of your file called “inlist”? If not, an easy way to get this problem would be for this control to be read from another inlist that you forgot about. Also, if you copied your original work directory from a test suite case, there may be hooks in run_star_extras.f that were relevant for the test but are not relevant to your experiment. Very intriguing if it’s not one of these situations... Bill ________________________ William Wolf wm...@ph... UCSB Department of Physics On March 21, 2017 at 11:45:41 AM, Catherine Lovekin (clo...@mt...) wrote: Hi everyone, I'm trying to run some rotating models (1.2-2.2 solar masses), and I've run into a problem. For now, I'm trying to include rotation in the simplest way possible, so I've got an inlist that has the following: &star_job show_log_description_at_start = .false. eos_file_prefix = 'mesa' kappa_file_prefix = 'gs98' change_v_flag = .true. new_v_flag = .true. new_rotation_flag = .true. change_rotation_flag = .true. relax_initial_surface_rotation_v = .true. set_surface_rotation_v = .true. new_surface_rotation_v = 100 / ! end of star_job namelist When I run a model, it starts out with whatever rotation rate I set on the last line, but around 30 models in, I see: turn on rotation new_surface_rotation_v = 4.5000000000000000D+01 3.7745766462731172D-05 and the rotation rate of my star drops. I can confirm that this is what happens when I plot omega or v as a function of the age of the star. The rotation velocity starts out where I set it, and then drops to close to 45 km/s and evolves from there. I get a surface rotation of 45 km/s for my model even if I comment all of the rotation commands out of my inlist, so it seems that my version of mesa is reading a velocity from somewhere else, or there's a default that isn't getting changed somehow. I've tried deleting all my inlists and making new ones, as well as recompiling the code, but the problem doesn't go away. Is there another rotation parameter I'm not setting, or another place I should be changing the rotation? I'm running version 8845 on a Mac OSX 10.9.5. Thanks, Catherine Catherine Lovekin Assistant Professor Department of Physics Dunn 222 Mount Allison University clo...@mt... phone: (506) 364-2582 ------------------------------------------------------------------------------ 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 |
From: Bill W. <wm...@ph...> - 2017-03-21 18:56:28
|
Ah, for instance, the multimass test case sets initial surface rotation to 45 in its run_star_extras, so did you by chance start from that? Bill ________________________ William Wolf wm...@ph... UCSB Department of Physics On March 21, 2017 at 11:54:44 AM, Bill Wolf (wm...@ph...) wrote: Hi Catherine, Is what you’ve pasted the contents of your file called “inlist”? If not, an easy way to get this problem would be for this control to be read from another inlist that you forgot about. Also, if you copied your original work directory from a test suite case, there may be hooks in run_star_extras.f that were relevant for the test but are not relevant to your experiment. Very intriguing if it’s not one of these situations... Bill ________________________ William Wolf wm...@ph... UCSB Department of Physics On March 21, 2017 at 11:45:41 AM, Catherine Lovekin (clo...@mt...) wrote: Hi everyone, I'm trying to run some rotating models (1.2-2.2 solar masses), and I've run into a problem. For now, I'm trying to include rotation in the simplest way possible, so I've got an inlist that has the following: &star_job show_log_description_at_start = .false. eos_file_prefix = 'mesa' kappa_file_prefix = 'gs98' change_v_flag = .true. new_v_flag = .true. new_rotation_flag = .true. change_rotation_flag = .true. relax_initial_surface_rotation_v = .true. set_surface_rotation_v = .true. new_surface_rotation_v = 100 / ! end of star_job namelist When I run a model, it starts out with whatever rotation rate I set on the last line, but around 30 models in, I see: turn on rotation new_surface_rotation_v = 4.5000000000000000D+01 3.7745766462731172D-05 and the rotation rate of my star drops. I can confirm that this is what happens when I plot omega or v as a function of the age of the star. The rotation velocity starts out where I set it, and then drops to close to 45 km/s and evolves from there. I get a surface rotation of 45 km/s for my model even if I comment all of the rotation commands out of my inlist, so it seems that my version of mesa is reading a velocity from somewhere else, or there's a default that isn't getting changed somehow. I've tried deleting all my inlists and making new ones, as well as recompiling the code, but the problem doesn't go away. Is there another rotation parameter I'm not setting, or another place I should be changing the rotation? I'm running version 8845 on a Mac OSX 10.9.5. Thanks, Catherine Catherine Lovekin Assistant Professor Department of Physics Dunn 222 Mount Allison University clo...@mt... phone: (506) 364-2582 ------------------------------------------------------------------------------ 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 |
From: Bill W. <wm...@ph...> - 2017-03-21 19:08:39
|
Hi Catherine, Please keep replies on the users list so others can learn from any resolution. Short answer: Yep, that should work. Longer answer: you should take a long look at any included run_star_extras file from a directory you start from, especially if you didn’t create it. There may be other surprises in there that you might not want or good surprises you could learn from. In general, test suite cases come with implicit time limits to help determine if the test “fails” by taking too long. You probably want to remove that, too. multimass has some other tricks up its sleeve like changing velocities and maximum timestep durations. Glad we figured it out! Regards, Bill ________________________ William Wolf wm...@ph... UCSB Department of Physics On March 21, 2017 at 12:00:52 PM, Catherine Lovekin (clo...@mt...) wrote: Hi Bill, I do indeed start from the multimass test case. It looks like I should be able to comment out the if statement where that gets set to avoid the problem then? Catherine Catherine Lovekin Assistant Professor Department of Physics Dunn 222 Mount Allison University clo...@mt... phone: (506) 364-2582 From: Bill Wolf <wm...@ph...> Sent: Tuesday, March 21, 2017 3:56 PM To: mes...@li...; Catherine Lovekin Subject: Re: [mesa-users] adding rotation Ah, for instance, the multimass test case sets initial surface rotation to 45 in its run_star_extras, so did you by chance start from that? Bill ________________________ William Wolf wm...@ph... UCSB Department of Physics On March 21, 2017 at 11:54:44 AM, Bill Wolf (wm...@ph...) wrote: Hi Catherine, Is what you’ve pasted the contents of your file called “inlist”? If not, an easy way to get this problem would be for this control to be read from another inlist that you forgot about. Also, if you copied your original work directory from a test suite case, there may be hooks in run_star_extras.f that were relevant for the test but are not relevant to your experiment. Very intriguing if it’s not one of these situations... Bill ________________________ William Wolf wm...@ph... UCSB Department of Physics On March 21, 2017 at 11:45:41 AM, Catherine Lovekin (clo...@mt...) wrote: Hi everyone, I'm trying to run some rotating models (1.2-2.2 solar masses), and I've run into a problem. For now, I'm trying to include rotation in the simplest way possible, so I've got an inlist that has the following: &star_job show_log_description_at_start = .false. eos_file_prefix = 'mesa' kappa_file_prefix = 'gs98' change_v_flag = .true. new_v_flag = .true. new_rotation_flag = .true. change_rotation_flag = .true. relax_initial_surface_rotation_v = .true. set_surface_rotation_v = .true. new_surface_rotation_v = 100 / ! end of star_job namelist When I run a model, it starts out with whatever rotation rate I set on the last line, but around 30 models in, I see: turn on rotation new_surface_rotation_v = 4.5000000000000000D+01 3.7745766462731172D-05 and the rotation rate of my star drops. I can confirm that this is what happens when I plot omega or v as a function of the age of the star. The rotation velocity starts out where I set it, and then drops to close to 45 km/s and evolves from there. I get a surface rotation of 45 km/s for my model even if I comment all of the rotation commands out of my inlist, so it seems that my version of mesa is reading a velocity from somewhere else, or there's a default that isn't getting changed somehow. I've tried deleting all my inlists and making new ones, as well as recompiling the code, but the problem doesn't go away. Is there another rotation parameter I'm not setting, or another place I should be changing the rotation? I'm running version 8845 on a Mac OSX 10.9.5. Thanks, Catherine Catherine Lovekin Assistant Professor Department of Physics Dunn 222 Mount Allison University clo...@mt... phone: (506) 364-2582 ------------------------------------------------------------------------------ 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 |