Menu
▾
▴
mesa-users — open list for mesa comments, questions, & answers
This list is closed, nobody may subscribe to it.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(6) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(8) |
Dec
(5) |
| 2009 |
Jan
(5) |
Feb
(1) |
Mar
(3) |
Apr
(4) |
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
(8) |
Oct
|
Nov
(1) |
Dec
(13) |
| 2010 |
Jan
|
Feb
(6) |
Mar
(4) |
Apr
(1) |
May
(10) |
Jun
(43) |
Jul
(37) |
Aug
(3) |
Sep
(6) |
Oct
(26) |
Nov
(17) |
Dec
(29) |
| 2011 |
Jan
(28) |
Feb
(18) |
Mar
(42) |
Apr
(18) |
May
(13) |
Jun
(32) |
Jul
(32) |
Aug
(25) |
Sep
(46) |
Oct
(41) |
Nov
(36) |
Dec
(43) |
| 2012 |
Jan
(92) |
Feb
(120) |
Mar
(40) |
Apr
(75) |
May
(40) |
Jun
(93) |
Jul
(115) |
Aug
(67) |
Sep
(38) |
Oct
(92) |
Nov
(95) |
Dec
(47) |
| 2013 |
Jan
(171) |
Feb
(200) |
Mar
(100) |
Apr
(134) |
May
(112) |
Jun
(142) |
Jul
(123) |
Aug
(66) |
Sep
(175) |
Oct
(236) |
Nov
(141) |
Dec
(98) |
| 2014 |
Jan
(91) |
Feb
(88) |
Mar
(126) |
Apr
(63) |
May
(123) |
Jun
(122) |
Jul
(105) |
Aug
(83) |
Sep
(114) |
Oct
(90) |
Nov
(181) |
Dec
(85) |
| 2015 |
Jan
(111) |
Feb
(120) |
Mar
(161) |
Apr
(95) |
May
(93) |
Jun
(185) |
Jul
(170) |
Aug
(119) |
Sep
(128) |
Oct
(110) |
Nov
(145) |
Dec
(92) |
| 2016 |
Jan
(105) |
Feb
(106) |
Mar
(101) |
Apr
(59) |
May
(96) |
Jun
(168) |
Jul
(110) |
Aug
(183) |
Sep
(85) |
Oct
(79) |
Nov
(87) |
Dec
(86) |
| 2017 |
Jan
(100) |
Feb
(77) |
Mar
(85) |
Apr
(52) |
May
(60) |
Jun
(63) |
Jul
(67) |
Aug
(24) |
Sep
(1) |
Oct
|
Nov
(2) |
Dec
|
|
From: Josiah S. <jws...@uc...> - 2017-05-19 14:54:14
|
Hi Chulwook, > I would like to find out an *agent-based modeling with continuous > strategies via Fermi rule*. > If someone can recommend any useful example (Jupyter notebook based) for > figuring out how to do it, that would be great, I hope. You have the wrong MESA. This mailing list is about stellar evolution. You probably want https://github.com/projectmesa/mesa Josiah |
|
From: chulwook P. <pc...@gm...> - 2017-05-19 14:38:42
|
Hi ; I would like to find out an *agent-based modeling with continuous strategies via Fermi rule*. If someone can recommend any useful example (Jupyter notebook based) for figuring out how to do it, that would be great, I hope. Cheers, On Wed, May 17, 2017 at 7:58 PM, Ying Qin <Yin...@un...> wrote: > Many thanks for Pablo, Bill and Robert. > > Cheers, > Ying > > On 17 May 2017, at 18:30, Pablo Marchant <pa...@gm...> wrote: > > Also, I want to self-promote my own Kippenhahn plotter which can receive a > list of history.data files as input > > https://github.com/orlox/mkipp > > But if you are already using your own tools for the plotting, I agree that > manual (or automated) merging of the files after the runs might better. > > On Wed, May 17, 2017 at 11:24 AM, Bill Paxton <pa...@ki...> > wrote: > >> >> On May 17, 2017, at 9:14 AM, Robert Farmer wrote: >> >> Hi >> >> Inside the controls inlist you can set the log_directory option to >> control where the output files go, this can then be set differently for >> each set of inlists, then after the mesa run you could merge the files >> together yourself. >> >> >> merging the files will be much easier if you don't reset the time and >> model number to 0 at the start of each inlist. >> >> put these lines in the &star_job section of your following inlists after >> the initial one. >> >> set_initial_age = .false. >> set_initial_model_number = .false. >> >> b >> >> >> >> >> >> Rob >> >> On Wed, May 17, 2017 at 9:05 AM, Ying Qin <Yin...@un...> wrote: >> >>> Hi all, >>> >>> I am currently playing MESA with an example (i.e. make_pre_ccsn) in >>> test_suite. In order to plot the Kippenhahn diagram to see how the star >>> evolves from the Pre-Main sequence to core-collapse, I need >>> one unique history.data and corresponding profile data. However, there >>> are several inlists for this project. It only saves the information >>> corresponding to the last one, and the previous history and profile >>> data will be overwritten. >>> Could any users know how to concatenate all the history data and save >>> all the corresponding profile data for each inlist automatically ? >>> >>> Thank you in advance, >>> Ying >>> ------------------------------------------------------------ >>> ------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org <http://slashdot.org/>! >>> http://sdm.link/slashdot >>> _______________________________________________ >>> mesa-users mailing list >>> mes...@li... >>> https://lists.sourceforge.net/lists/listinfo/mesa-users >>> >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org <http://slashdot.org/>! >> http://sdm.link/slashdot_______________________________________________ >> mesa-users mailing list >> mes...@li... >> https://lists.sourceforge.net/lists/listinfo/mesa-users >> >> >> >> ------------------------------------------------------------ >> ------------------ >> 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 student, Argelander-Institut für Astronomie > > > > ------------------------------------------------------------ > ------------------ > 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: Pablo M. <pa...@gm...> - 2017-05-19 14:36:16
|
Hi Odette, this is straightforward.
In you src/run_binary_extras you can use this
integer function extras_binary_check_model(binary_id)
type (binary_info), pointer :: b
integer, intent(in) :: binary_id
integer :: ierr
call binary_ptr(binary_id, b, ierr)
if (ierr /= 0) then ! failure in binary_ptr
return
end if
!check if mass transfer rate reached maximun, assume merger if it
happens
extras_binary_check_model = keep_going
if(abs(b% mtransfer_rate) >= b% max_implicit_abs_mdot*Msun/secyer)
then
extras_binary_finish_step = terminate
write(*,*) "TERMINATING: Reached maximum mass transfer rate"
end if
end function extras_binary_check_model
and in you inlist you choose the value of max_implicit_abs_mdot. I usually
prefer doing it using max_implicit_abs_mdot instead of directly writing the
limit, because at the onset of unstable MT the code might not be able to
converge to a solution and get stuck.
On Fri, May 19, 2017 at 4:48 AM, Odette Toloza <ode...@gm...>
wrote:
> Hi Mesa users,
>
> I was wondering if I can implement a limit to the mass transfer as a
> stopping condition, when I evolve a binary?
>
> Cheers,
> Odette.
>
> ------------------------------------------------------------
> ------------------
> 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 student, Argelander-Institut für Astronomie
|
|
From: Odette T. <ode...@gm...> - 2017-05-19 09:48:45
|
Hi Mesa users, I was wondering if I can implement a limit to the mass transfer as a stopping condition, when I evolve a binary? Cheers, Odette. |
|
From: Ying Q. <Yin...@un...> - 2017-05-17 17:58:53
|
Many thanks for Pablo, Bill and Robert. Cheers, Ying On 17 May 2017, at 18:30, Pablo Marchant <pa...@gm...<mailto:pa...@gm...>> wrote: Also, I want to self-promote my own Kippenhahn plotter which can receive a list of history.data files as input https://github.com/orlox/mkipp But if you are already using your own tools for the plotting, I agree that manual (or automated) merging of the files after the runs might better. On Wed, May 17, 2017 at 11:24 AM, Bill Paxton <pa...@ki...<mailto:pa...@ki...>> wrote: On May 17, 2017, at 9:14 AM, Robert Farmer wrote: Hi Inside the controls inlist you can set the log_directory option to control where the output files go, this can then be set differently for each set of inlists, then after the mesa run you could merge the files together yourself. merging the files will be much easier if you don't reset the time and model number to 0 at the start of each inlist. put these lines in the &star_job section of your following inlists after the initial one. set_initial_age = .false. set_initial_model_number = .false. b Rob On Wed, May 17, 2017 at 9:05 AM, Ying Qin <Yin...@un...<mailto:Yin...@un...>> wrote: Hi all, I am currently playing MESA with an example (i.e. make_pre_ccsn) in test_suite. In order to plot the Kippenhahn diagram to see how the star evolves from the Pre-Main sequence to core-collapse, I need one unique history.data and corresponding profile data. However, there are several inlists for this project. It only saves the information corresponding to the last one, and the previous history and profile data will be overwritten. Could any users know how to concatenate all the history data and save all the corresponding profile data for each inlist automatically ? Thank you in advance, Ying ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org<http://slashdot.org/>! http://sdm.link/slashdot _______________________________________________ mesa-users mailing list mes...@li...<mailto:mes...@li...> https://lists.sourceforge.net/lists/listinfo/mesa-users ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org<http://slashdot.org/>! http://sdm.link/slashdot_______________________________________________ mesa-users mailing list mes...@li...<mailto:mes...@li...> https://lists.sourceforge.net/lists/listinfo/mesa-users ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org<http://Slashdot.org>! http://sdm.link/slashdot _______________________________________________ mesa-users mailing list mes...@li...<mailto:mes...@li...> 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 |
|
From: Josiah S. <jws...@uc...> - 2017-05-17 17:47:37
|
Hi Andrew, When you reply, please continue to cc mesa-users. > I'm still having some issues. saved_model_name was set to the > correct filename, so it's still unclear to me why MESA isn't loading my > file. For clarity I've attached all the inlists I'm using as well as the > model I'm trying to load. You set save_model_name and not saved_model_name. Josiah |
|
From: Pablo M. <pa...@gm...> - 2017-05-17 16:30:23
|
Also, I want to self-promote my own Kippenhahn plotter which can receive a list of history.data files as input https://github.com/orlox/mkipp But if you are already using your own tools for the plotting, I agree that manual (or automated) merging of the files after the runs might better. On Wed, May 17, 2017 at 11:24 AM, Bill Paxton <pa...@ki...> wrote: > > On May 17, 2017, at 9:14 AM, Robert Farmer wrote: > > Hi > > Inside the controls inlist you can set the log_directory option to > control where the output files go, this can then be set differently for > each set of inlists, then after the mesa run you could merge the files > together yourself. > > > merging the files will be much easier if you don't reset the time and > model number to 0 at the start of each inlist. > > put these lines in the &star_job section of your following inlists after > the initial one. > > set_initial_age = .false. > set_initial_model_number = .false. > > b > > > > > > Rob > > On Wed, May 17, 2017 at 9:05 AM, Ying Qin <Yin...@un...> wrote: > >> Hi all, >> >> I am currently playing MESA with an example (i.e. make_pre_ccsn) in >> test_suite. In order to plot the Kippenhahn diagram to see how the star >> evolves from the Pre-Main sequence to core-collapse, I need >> one unique history.data and corresponding profile data. However, there >> are several inlists for this project. It only saves the information >> corresponding to the last one, and the previous history and profile >> data will be overwritten. >> Could any users know how to concatenate all the history data and save all >> the corresponding profile data for each inlist automatically ? >> >> Thank you in advance, >> Ying >> ------------------------------------------------------------ >> ------------------ >> 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 >> > > ------------------------------------------------------------ > ------------------ > 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 > > > > ------------------------------------------------------------ > ------------------ > 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 student, Argelander-Institut für Astronomie |
|
From: Bill P. <pa...@ki...> - 2017-05-17 16:25:39
|
On May 17, 2017, at 9:14 AM, Robert Farmer wrote:
> Hi
>
> Inside the controls inlist you can set the log_directory option to control where the output files go, this can then be set differently for each set of inlists, then after the mesa run you could merge the files together yourself.
merging the files will be much easier if you don't reset the time and model number to 0 at the start of each inlist.
put these lines in the &star_job section of your following inlists after the initial one.
set_initial_age = .false.
set_initial_model_number = .false.
b
>
> Rob
>
> On Wed, May 17, 2017 at 9:05 AM, Ying Qin <Yin...@un...> wrote:
> Hi all,
>
> I am currently playing MESA with an example (i.e. make_pre_ccsn) in test_suite. In order to plot the Kippenhahn diagram to see how the star evolves from the Pre-Main sequence to core-collapse, I need
> one unique history.data and corresponding profile data. However, there are several inlists for this project. It only saves the information corresponding to the last one, and the previous history and profile
> data will be overwritten.
> Could any users know how to concatenate all the history data and save all the corresponding profile data for each inlist automatically ?
>
> Thank you in advance,
> Ying
> ------------------------------------------------------------------------------
> 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
>
> ------------------------------------------------------------------------------
> 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: Robert F. <rjf...@as...> - 2017-05-17 16:14:47
|
Hi Inside the controls inlist you can set the log_directory option to control where the output files go, this can then be set differently for each set of inlists, then after the mesa run you could merge the files together yourself. Rob On Wed, May 17, 2017 at 9:05 AM, Ying Qin <Yin...@un...> wrote: > Hi all, > > I am currently playing MESA with an example (i.e. make_pre_ccsn) in > test_suite. In order to plot the Kippenhahn diagram to see how the star > evolves from the Pre-Main sequence to core-collapse, I need > one unique history.data and corresponding profile data. However, there are > several inlists for this project. It only saves the information > corresponding to the last one, and the previous history and profile > data will be overwritten. > Could any users know how to concatenate all the history data and save all > the corresponding profile data for each inlist automatically ? > > Thank you in advance, > Ying > ------------------------------------------------------------ > ------------------ > 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: Ying Q. <Yin...@un...> - 2017-05-17 16:06:07
|
Hi all, I am currently playing MESA with an example (i.e. make_pre_ccsn) in test_suite. In order to plot the Kippenhahn diagram to see how the star evolves from the Pre-Main sequence to core-collapse, I need one unique history.data and corresponding profile data. However, there are several inlists for this project. It only saves the information corresponding to the last one, and the previous history and profile data will be overwritten. Could any users know how to concatenate all the history data and save all the corresponding profile data for each inlist automatically ? Thank you in advance, Ying |
|
From: Josiah S. <jws...@uc...> - 2017-05-16 21:46:52
|
Hi Andrew, > How can I resolve this issue? If you need me to send specific files to > diagnose this issue, just let me know. When asking a question, please include enough information for us to reproduce your problem. (That would probably mean attaching your inlist files.) In this case, you almost certainly have set load_saved_model = .true. without setting the value for saved_model_name because its default value is 'undefined'. Josiah |
|
From: Robert F. <rjf...@as...> - 2017-05-16 21:44:09
|
Hi
>failed to open undefined
This suggests that you haven't set the filename properly for the model to
be loaded ('undefined' is the default filename)
Please send the inlists you are using and the model you want to load.
Rob
On Tue, May 16, 2017 at 1:50 PM, Andrew Mizener <ami...@ma...>
wrote:
> Hey everybody,
>
> I've successfully installed MESA and the related packages, and I'm working
> through the tutorial and some of the test cases. In general, stuff is
> working well. However I am encountering some issues when attempting to load
> models. For example, I've attempted to run the commands in the tutorial
> with my inputs (as far as I can tell) line-by-line identical. When I do
> this, however, I get:
>
> open failed 2 30
>
> failed to open undefined
>
> load failed in do_read_saved_model
>
> star_read_model ierr 2
>
> do_load1_star ierr 2
>
> before_evolve_loop ierr 2
>
> DATE: 2017-05-16
>
> TIME: 00:40:54
> How can I resolve this issue? If you need me to send specific files to
> diagnose this issue, just let me know.
>
> Thanks,
> Andrew Mizener
>
> ------------------------------------------------------------
> ------------------
> 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: Andrew M. <ami...@ma...> - 2017-05-16 20:50:44
|
Hey everybody, I've successfully installed MESA and the related packages, and I'm working through the tutorial and some of the test cases. In general, stuff is working well. However I am encountering some issues when attempting to load models. For example, I've attempted to run the commands in the tutorial with my inputs (as far as I can tell) line-by-line identical. When I do this, however, I get: open failed 2 30 failed to open undefined load failed in do_read_saved_model star_read_model ierr 2 do_load1_star ierr 2 before_evolve_loop ierr 2 DATE: 2017-05-16 TIME: 00:40:54 How can I resolve this issue? If you need me to send specific files to diagnose this issue, just let me know. Thanks, Andrew Mizener |
|
From: Warrick B. <wb...@bi...> - 2017-05-16 15:43:10
|
Hi Bruno, The astero/work folder has all the inlists and code that you need. Try copying it to a new location, then running ./mk and ./rn, and see what happens! W ------------ Warrick Ball Postdoc, School of Physics and Astronomy University of Birmingham, Edgbaston, Birmingham B15 2TT wb...@bi... +44 (0)121 414 4552 On Tue, 16 May 2017, bru...@gm... wrote: > Thanks again. It means then that all the templates I want to do I must transcribe to the astero module and not include the $ MESA_DIR / star / work inlists. > > > Bruno > > > 2017-05-16 12:34 GMT-03:00 Warrick Ball <wb...@bi...>: > Hi Bruno, > > If you want to work with the astero module, you should use the folder $MESA_DIR/star/astero/work instead of the usual work folder ($MESA_DIR/star/work). That is, whereas one would usually copy > $MESA_DIR/star/work to a new location and start editing the inlists, you should instead copy $MESA_DIR/star/astero/work. Does that make more sense? > > Cheers, > Warrick > > PS: Keep replies on the list so that they're available for future readers (and so that someone else might help you if I'm unavailable/slow to respond). > > > ------------ > Warrick Ball > Postdoc, School of Physics and Astronomy > University of Birmingham, Edgbaston, Birmingham B15 2TT > wb...@bi... > +44 (0)121 414 4552 > > On Tue, 16 May 2017, bru...@gm... wrote: > > Thanks also. One question: should I just include in the folder astro_serarch? > > Cheers > > Bruno > 2017-05-16 11:21 GMT-03:00 Warrick Ball <wb...@bi...>: > Hi Bruno, > > Not sure if someone has already replied to this but my guess is that you've added the astero stuff to &controls in the usual MESA inlist, rather than to > &astero_search_controls. The astero > module requires extra code that is compiled in addition to the usual MESA code, and that this code has its own set of extra parameters in two namelists called > &astero_search_controls and > &astero_pgstar_controls in the file inlist_astero_search_controls. > > Cheers, > Warrick > > ------------ > Warrick Ball > Postdoc, School of Physics and Astronomy > University of Birmingham, Edgbaston, Birmingham B15 2TT > wb...@bi... > +44 (0)121 414 4552 > > On Tue, 16 May 2017, Bruno Lustosa wrote: > > Hello everyone > > I have a tense question about my model with regard to astero controls. By including chi2_seismo_fraction directly in my inlist in & controls the following: > > ! Seismic data > Chi2_seismo_fraction = 0.667d0 > Include_Teff_in_chi2_spectro = .true. > Teff_target = 4400d0 > Teff_sigma = 100d0 > Include_logg_in_chi2_spectro = .true. > Logg_target = 2.5d0 > Logg_sigma = 0.02d0 > Include_logL_in_chi2_spectro = .true. > LogL_target = 1.62d0 > LogL_sigma = 0.04d0 > Include_FeH_in_chi2_spectro = .true. ! [Fe / H] > FeH_target = 0.1 > FeH_sigma = 0.05 > Include_age_in_chi2_spectro = .true. > Age_target = 8.87d9! (See Bahcall, Serenelli, and Basu, 2006) > Age_sigma = 0.0065d9 > Num_smaller_steps_before_age_target = 50 > Dt_for_smaller_steps_before_age_target = 0.0065d8 > Chi2_seismo_delta_nu_fraction = 0d0 > ! If> 0 then delta_nu and delta_nu_sigma must be set (see below) > Chi2_seismo_nu_max_fraction = 0d0 > ! If> 0 then nu_max and nu_max_sigma must be set (see below) > Chi2_seismo_r_010_fraction = 0d0 > ! If> 0, then include r_010 frequency ratios > Chi2_seismo_r_02_fraction = 0d0 > ! If> 0, then include r_02 frequency ratios > ! Fraction for frequencies = 1 - (frac_r_010_ratios + frac_r_02_ratios + frac_delta_nu + frac_nu_max) > ! Nu_max = 70 > ! Nu_max_sigma = -1 > Delta_nu = -1 > Delta_nu_sigma = -1.0 > Eval_chi2_at_target_age_only = .true. > Search_type = 'use_first_values' > Simplex_itermax = 1000! Each iteration revises the simplex > Simplex_fcn_calls_max = 10000! May use several function calls per iteration > Simplex_x_atol = 1d-10! Tolerance for absolute differences > Simplex_x_rtol = 1d-10! Tolerance for relative differences > Simplex_centroid_weight_power = 0d0 > Simplex_output_filename = '16_maio.data' > Simplex_seed = 1074698122 > Oscillation_code = 'adipls > > The following error is reported: > > At line 1700 of file ../private/ctrls_io.f90 (unit = 30, file = 'inlist_2.0') > Fortran runtime error: Can not match namelist object name chi2_seismo_fraction > > > Have I or should I change some subroutine I did not do? > > > Cheers > > > Bruno > > > > > > |
|
From: Bruno L. <bru...@gm...> - 2017-05-16 15:41:42
|
Thanks again. It means then that all the templates I want to do I must transcribe to the astero module and not include the $ MESA_DIR / star / work inlists. Bruno 2017-05-16 12:34 GMT-03:00 Warrick Ball <wb...@bi...>: > Hi Bruno, > > If you want to work with the astero module, you should use the folder > $MESA_DIR/star/astero/work instead of the usual work folder > ($MESA_DIR/star/work). That is, whereas one would usually copy > $MESA_DIR/star/work to a new location and start editing the inlists, you > should instead copy $MESA_DIR/star/astero/work. Does that make more sense? > > Cheers, > Warrick > > PS: Keep replies on the list so that they're available for future readers > (and so that someone else might help you if I'm unavailable/slow to > respond). > > > ------------ > Warrick Ball > Postdoc, School of Physics and Astronomy > University of Birmingham, Edgbaston, Birmingham B15 2TT > wb...@bi... > +44 (0)121 414 4552 > > On Tue, 16 May 2017, bru...@gm... wrote: > > Thanks also. One question: should I just include in the folder >> astro_serarch? >> >> Cheers >> >> Bruno >> 2017-05-16 11:21 GMT-03:00 Warrick Ball <wb...@bi...>: >> Hi Bruno, >> >> Not sure if someone has already replied to this but my guess is >> that you've added the astero stuff to &controls in the usual MESA inlist, >> rather than to &astero_search_controls. The astero >> module requires extra code that is compiled in addition to the >> usual MESA code, and that this code has its own set of extra parameters in >> two namelists called &astero_search_controls and >> &astero_pgstar_controls in the file inlist_astero_search_controls. >> >> Cheers, >> Warrick >> >> ------------ >> Warrick Ball >> Postdoc, School of Physics and Astronomy >> University of Birmingham, Edgbaston, Birmingham B15 2TT >> wb...@bi... >> +44 (0)121 414 4552 >> >> On Tue, 16 May 2017, Bruno Lustosa wrote: >> >> Hello everyone >> >> I have a tense question about my model with regard to astero >> controls. By including chi2_seismo_fraction directly in my inlist in & >> controls the following: >> >> ! Seismic data >> Chi2_seismo_fraction = 0.667d0 >> Include_Teff_in_chi2_spectro = .true. >> Teff_target = 4400d0 >> Teff_sigma = 100d0 >> Include_logg_in_chi2_spectro = .true. >> Logg_target = 2.5d0 >> Logg_sigma = 0.02d0 >> Include_logL_in_chi2_spectro = .true. >> LogL_target = 1.62d0 >> LogL_sigma = 0.04d0 >> Include_FeH_in_chi2_spectro = .true. ! [Fe / H] >> FeH_target = 0.1 >> FeH_sigma = 0.05 >> Include_age_in_chi2_spectro = .true. >> Age_target = 8.87d9! (See Bahcall, Serenelli, and >> Basu, 2006) >> Age_sigma = 0.0065d9 >> Num_smaller_steps_before_age_target = 50 >> Dt_for_smaller_steps_before_age_target = 0.0065d8 >> Chi2_seismo_delta_nu_fraction = 0d0 >> ! If> 0 then delta_nu and delta_nu_sigma must be set >> (see below) >> Chi2_seismo_nu_max_fraction = 0d0 >> ! If> 0 then nu_max and nu_max_sigma must be set >> (see below) >> Chi2_seismo_r_010_fraction = 0d0 >> ! If> 0, then include r_010 frequency ratios >> Chi2_seismo_r_02_fraction = 0d0 >> ! If> 0, then include r_02 frequency ratios >> ! Fraction for frequencies = 1 - (frac_r_010_ratios >> + frac_r_02_ratios + frac_delta_nu + frac_nu_max) >> ! Nu_max = 70 >> ! Nu_max_sigma = -1 >> Delta_nu = -1 >> Delta_nu_sigma = -1.0 >> Eval_chi2_at_target_age_only = .true. >> Search_type = 'use_first_values' >> Simplex_itermax = 1000! Each iteration revises the simplex >> Simplex_fcn_calls_max = 10000! May use several >> function calls per iteration >> Simplex_x_atol = 1d-10! Tolerance for absolute >> differences >> Simplex_x_rtol = 1d-10! Tolerance for relative >> differences >> Simplex_centroid_weight_power = 0d0 >> Simplex_output_filename = '16_maio.data' >> Simplex_seed = 1074698122 >> Oscillation_code = 'adipls >> >> The following error is reported: >> >> At line 1700 of file ../private/ctrls_io.f90 (unit = 30, file >> = 'inlist_2.0') >> Fortran runtime error: Can not match namelist object name >> chi2_seismo_fraction >> >> >> Have I or should I change some subroutine I did not do? >> >> >> Cheers >> >> >> Bruno >> >> >> >> |
|
From: Warrick B. <wb...@bi...> - 2017-05-16 15:34:31
|
Hi Bruno, If you want to work with the astero module, you should use the folder $MESA_DIR/star/astero/work instead of the usual work folder ($MESA_DIR/star/work). That is, whereas one would usually copy $MESA_DIR/star/work to a new location and start editing the inlists, you should instead copy $MESA_DIR/star/astero/work. Does that make more sense? Cheers, Warrick PS: Keep replies on the list so that they're available for future readers (and so that someone else might help you if I'm unavailable/slow to respond). ------------ Warrick Ball Postdoc, School of Physics and Astronomy University of Birmingham, Edgbaston, Birmingham B15 2TT wb...@bi... +44 (0)121 414 4552 On Tue, 16 May 2017, bru...@gm... wrote: > Thanks also. One question: should I just include in the folder astro_serarch? > > Cheers > > Bruno > 2017-05-16 11:21 GMT-03:00 Warrick Ball <wb...@bi...>: > Hi Bruno, > > Not sure if someone has already replied to this but my guess is that you've added the astero stuff to &controls in the usual MESA inlist, rather than to &astero_search_controls. The astero > module requires extra code that is compiled in addition to the usual MESA code, and that this code has its own set of extra parameters in two namelists called &astero_search_controls and > &astero_pgstar_controls in the file inlist_astero_search_controls. > > Cheers, > Warrick > > ------------ > Warrick Ball > Postdoc, School of Physics and Astronomy > University of Birmingham, Edgbaston, Birmingham B15 2TT > wb...@bi... > +44 (0)121 414 4552 > > On Tue, 16 May 2017, Bruno Lustosa wrote: > > Hello everyone > > I have a tense question about my model with regard to astero controls. By including chi2_seismo_fraction directly in my inlist in & controls the following: > > ! Seismic data > Chi2_seismo_fraction = 0.667d0 > Include_Teff_in_chi2_spectro = .true. > Teff_target = 4400d0 > Teff_sigma = 100d0 > Include_logg_in_chi2_spectro = .true. > Logg_target = 2.5d0 > Logg_sigma = 0.02d0 > Include_logL_in_chi2_spectro = .true. > LogL_target = 1.62d0 > LogL_sigma = 0.04d0 > Include_FeH_in_chi2_spectro = .true. ! [Fe / H] > FeH_target = 0.1 > FeH_sigma = 0.05 > Include_age_in_chi2_spectro = .true. > Age_target = 8.87d9! (See Bahcall, Serenelli, and Basu, 2006) > Age_sigma = 0.0065d9 > Num_smaller_steps_before_age_target = 50 > Dt_for_smaller_steps_before_age_target = 0.0065d8 > Chi2_seismo_delta_nu_fraction = 0d0 > ! If> 0 then delta_nu and delta_nu_sigma must be set (see below) > Chi2_seismo_nu_max_fraction = 0d0 > ! If> 0 then nu_max and nu_max_sigma must be set (see below) > Chi2_seismo_r_010_fraction = 0d0 > ! If> 0, then include r_010 frequency ratios > Chi2_seismo_r_02_fraction = 0d0 > ! If> 0, then include r_02 frequency ratios > ! Fraction for frequencies = 1 - (frac_r_010_ratios + frac_r_02_ratios + frac_delta_nu + frac_nu_max) > ! Nu_max = 70 > ! Nu_max_sigma = -1 > Delta_nu = -1 > Delta_nu_sigma = -1.0 > Eval_chi2_at_target_age_only = .true. > Search_type = 'use_first_values' > Simplex_itermax = 1000! Each iteration revises the simplex > Simplex_fcn_calls_max = 10000! May use several function calls per iteration > Simplex_x_atol = 1d-10! Tolerance for absolute differences > Simplex_x_rtol = 1d-10! Tolerance for relative differences > Simplex_centroid_weight_power = 0d0 > Simplex_output_filename = '16_maio.data' > Simplex_seed = 1074698122 > Oscillation_code = 'adipls > > The following error is reported: > > At line 1700 of file ../private/ctrls_io.f90 (unit = 30, file = 'inlist_2.0') > Fortran runtime error: Can not match namelist object name chi2_seismo_fraction > > > Have I or should I change some subroutine I did not do? > > > Cheers > > > Bruno > > > > |
|
From: Frank T. <fx...@ma...> - 2017-05-16 14:42:22
|
thanks. see warricks's message: > you've added the astero stuff to &controls in the usual MESA inlist, rather than to &astero_search_controls. fxt > On May 16, 2017, at 7:04 AM, Bruno Lustosa <bru...@gm...> wrote: > > mesa-r8845 > > > ########################################################################## > > &star_job > > pause_before_terminate = .true. > create_pre_main_sequence_model = .true. > pre_ms_relax_num_steps = 50 > pre_ms_T_c = 9e5 > > > > !change_initial_net = .true. > !new_net_name = 'agb.net' > !set_abundance = .true. > set_initial_abundance = .true. > chem_name = 'li7' > new_frac = 7.77594697D-09 > !new_frac = 1.06927581475e-08 > !set_abundance_nzlo = -1 > !set_abundance_nzhi = -1 > > > change_net=.true. > eos_file_prefix = 'mesa' > new_net_name = 'pp_extras.net' > kap_cache_dir = '/home/bruno/mesa-r8845/data/kap_data/cache' > kappa_file_prefix = 'OP_gs98' > dump_missing_metals_into_heaviest = .false. > set_uniform_initial_composition = .true. > initial_h1 = 0.6997725177 > !initial y = 0.2797816935 > initial_he3 = 0.0000279782 > initial_he4 = 0.2797537154 > initial_h2 = 0 > > set_rates_preference = .true. > new_rates_preference = 1 > > > new_rotation_flag = .true. > change_rotation_flag = .false. > change_initial_rotation_flag = .true. > > > initial_zfracs = 7 > new_surface_rotation_v = 2 ! solar (km sec^1) > set_near_zams_surface_rotation_v_steps = 10 > > > > pgstar_flag = .true. > > > / ! end of star_job namelist > > &controls > !max_age = 12000000000 > stop_at_TP = .true. > ! check for retries and backups as part of test_suite > ! you can/should delete this for use outside of test_suite > max_number_backups = 200 > max_number_retries = 500 > > > max_model_number = 6000 !958 max > > > initial_mass = 1.08 > initial_z = 0.0204457888 > !initial_z = 0.02 > initial_y = 0.2797816935 > !use_Type2_opacities = .true. > Zbase = 0.0204457888 > > am_nu_visc_factor = 0 > am_D_mix_factor = 0.0333333333333333d0 > D_DSI_factor = 0 > D_SH_factor = 1 > D_SSI_factor = 1 > D_ES_factor = 1 > D_GSF_factor = 1 > D_ST_factor = 1 > > varcontrol_target = 1d-3 > mesh_delta_coeff = 1.5 > > > photo_interval = 10 > profile_interval = 50 > history_interval = 1 > terminal_interval = 10 > write_header_frequency = 10 > > write_pulse_info_with_profile = .true. !.true. ! if true, write pulse info file when write profile > pulse_info_format = 'FGONG' > > log_L_lower_limit = -1 > mixing_length_alpha = 1.9107649497 > MLT_option = 'Cox' > ! options are: > ! 'Cox' MLT as developed in Cox & Giuli 1968, Chapter 14. > ! 'ML1' Bohm-Vitense 1958 > ! 'ML2' Bohm and Cassinelli 1971 > ! 'Mihalas' Mihalas 1978, Kurucz 1979 > ! 'Henyey' Henyey, Vardya, and Bodenheimer 1965 > ! 'Cox' option assumes optically thick material. > ! the other options are various ways of extending to include optically thin material. > > !which_atm_option = 'simple_photosphere' > smooth_convective_bdy = .true. > convective_bdy_weight = 1 > D_visc_factor = 0 > > cool_wind_full_on_T = 9d6 > cool_wind_full_off_T = 1d7 > cool_wind_RGB_scheme = 'Reimers' > cool_wind_AGB_scheme = 'Blocker' > RGB_to_AGB_wind_switch = 1d-4 > Reimers_scaling_factor = 0.5d0 > Blocker_scaling_factor = 0.5d0 > > > ! FOR DEBUGGING > > !report_hydro_solver_progress = .true. ! set true to see info about newton iterations > !report_ierr = .true. ! if true, produce terminal output when have some internal error > !hydro_show_correction_info = .true. > > !max_years_for_timestep = 3.67628942044319d-05 > > !report_why_dt_limits = .true. > !report_all_dt_limits = .true. > > !show_mesh_changes = .true. > !mesh_dump_call_number = 5189 > !okay_to_remesh = .false. > > trace_evolve = .true. > > > ! hydro debugging > !hydro_check_everything = .true. > !hydro_inspectB_flag = .true. > > !hydro_numerical_jacobian = .true. > !hydro_save_numjac_plot_data = .true. > !small_mtx_decsol = 'lapack' > !large_mtx_decsol = 'lapack' > !hydro_dump_call_number = 195 > > !trace_newton_bcyclic_solve_input = .true. ! input is "B" j k iter B(j,k) > !trace_newton_bcyclic_solve_output = .true. ! output is "X" j k iter X(j,k) > > !trace_newton_bcyclic_steplo = 1 ! 1st model number to trace > !trace_newton_bcyclic_stephi = 1 ! last model number to trace > > !trace_newton_bcyclic_iterlo = 2 ! 1st newton iter to trace > !trace_newton_bcyclic_iterhi = 2 ! last newton iter to trace > > !trace_newton_bcyclic_nzlo = 1 ! 1st cell to trace > !trace_newton_bcyclic_nzhi = 10000 ! last cell to trace; if < 0, then use nz as nzhi > > !trace_newton_bcyclic_jlo = 1 ! 1st var to trace > !trace_newton_bcyclic_jhi = 100 ! last var to trace; if < 0, then use nvar as jhi > > !trace_k = 0 > > ! misc > add_atmosphere_to_pulse_info = .true. > add_center_point_to_pulse_info = .true. ! add point for r=0 > stop_at_TP = .true. > > > > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > ! seismic data (frequencies in microHz) > > !nu_max = 1010 > ! nu_max is needed when > ! chi2_seismo_nu_max_fraction > 0 or correction_factor > 0 (see below) > !nu_max_sigma = -1 > ! nu_max_sigma is needed when chi2_seismo_nu_max_fraction > 0 > > !delta_nu = 56.28 > !delta_nu_sigma = 1.0 > > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > / ! end of controls namelist > > > > &pgstar > > Power_win_flag = .false. > Power_win_width = 9 > HR_win_flag = .true. > HR_win_width = 10 > HR_win_aspect_ratio = 1 > logg_logT_win_flag = .false. > logg_logT_win_width = 8 > logg_logT_win_aspect_ratio = 1.0 > Abundance_win_flag = .false. > Abundance_win_width = 6 > Abundance_win_aspect_ratio = 1 > HR_file_flag = .true. > HR_file_dir = 'png' > HR_file_prefix = 'HR_' > HR_title = 'DHR - Bruno' > > ! Mode Propagation window > > Mode_Prop_win_flag = .false. > > Mode_Prop_win_width = 10 > Mode_Prop_win_aspect_ratio = 0.62 ! aspect_ratio = height/width > > Mode_Prop_nu_max_obs = 1000 > > Mode_Prop_xaxis_name = 'r_div_R' > > ! power xaxis limits -- to override system default selections > Mode_Prop_xmin = -101 ! only used if > -100 > Mode_Prop_xmax = 0.3 !-101 ! only used if > -100 > > ! power yaxis limits -- to override system default selections > Mode_Prop_ymin = 2 ! -101 ! only used if > -100 > Mode_Prop_ymax = 5 ! -101 ! only used if > -100 > > ! file output > Mode_Prop_file_flag = .false. > Mode_Prop_file_dir = 'pgstar_out' > Mode_Prop_file_prefix = 'mode_prop' > Mode_Prop_file_interval = 5 ! output when mod(model_number,Mode_Prop_file_interval)==0 > Mode_Prop_file_width = -1 ! negative means use same value as for window > Mode_Prop_file_aspect_ratio = -1 ! negative means use same value as for window > > > / ! end of pgstar namelist > <inlist_2.0> |
|
From: Warrick B. <wb...@bi...> - 2017-05-16 14:21:12
|
Hi Bruno, Not sure if someone has already replied to this but my guess is that you've added the astero stuff to &controls in the usual MESA inlist, rather than to &astero_search_controls. The astero module requires extra code that is compiled in addition to the usual MESA code, and that this code has its own set of extra parameters in two namelists called &astero_search_controls and &astero_pgstar_controls in the file inlist_astero_search_controls. Cheers, Warrick ------------ Warrick Ball Postdoc, School of Physics and Astronomy University of Birmingham, Edgbaston, Birmingham B15 2TT wb...@bi... +44 (0)121 414 4552 On Tue, 16 May 2017, Bruno Lustosa wrote: > Hello everyone > > I have a tense question about my model with regard to astero controls. By including chi2_seismo_fraction directly in my inlist in & controls the following: > > ! Seismic data > Chi2_seismo_fraction = 0.667d0 > Include_Teff_in_chi2_spectro = .true. > Teff_target = 4400d0 > Teff_sigma = 100d0 > Include_logg_in_chi2_spectro = .true. > Logg_target = 2.5d0 > Logg_sigma = 0.02d0 > Include_logL_in_chi2_spectro = .true. > LogL_target = 1.62d0 > LogL_sigma = 0.04d0 > Include_FeH_in_chi2_spectro = .true. ! [Fe / H] > FeH_target = 0.1 > FeH_sigma = 0.05 > Include_age_in_chi2_spectro = .true. > Age_target = 8.87d9! (See Bahcall, Serenelli, and Basu, 2006) > Age_sigma = 0.0065d9 > Num_smaller_steps_before_age_target = 50 > Dt_for_smaller_steps_before_age_target = 0.0065d8 > Chi2_seismo_delta_nu_fraction = 0d0 > ! If> 0 then delta_nu and delta_nu_sigma must be set (see below) > Chi2_seismo_nu_max_fraction = 0d0 > ! If> 0 then nu_max and nu_max_sigma must be set (see below) > Chi2_seismo_r_010_fraction = 0d0 > ! If> 0, then include r_010 frequency ratios > Chi2_seismo_r_02_fraction = 0d0 > ! If> 0, then include r_02 frequency ratios > ! Fraction for frequencies = 1 - (frac_r_010_ratios + frac_r_02_ratios + frac_delta_nu + frac_nu_max) > ! Nu_max = 70 > ! Nu_max_sigma = -1 > Delta_nu = -1 > Delta_nu_sigma = -1.0 > Eval_chi2_at_target_age_only = .true. > Search_type = 'use_first_values' > Simplex_itermax = 1000! Each iteration revises the simplex > Simplex_fcn_calls_max = 10000! May use several function calls per iteration > Simplex_x_atol = 1d-10! Tolerance for absolute differences > Simplex_x_rtol = 1d-10! Tolerance for relative differences > Simplex_centroid_weight_power = 0d0 > Simplex_output_filename = '16_maio.data' > Simplex_seed = 1074698122 > Oscillation_code = 'adipls > > The following error is reported: > > At line 1700 of file ../private/ctrls_io.f90 (unit = 30, file = 'inlist_2.0') > Fortran runtime error: Can not match namelist object name chi2_seismo_fraction > > > Have I or should I change some subroutine I did not do? > > > Cheers > > > Bruno > > |
|
From: Bruno L. <bru...@gm...> - 2017-05-16 14:04:10
|
mesa-r8845
##########################################################################
&star_job
pause_before_terminate = .true.
create_pre_main_sequence_model = .true.
pre_ms_relax_num_steps = 50
pre_ms_T_c = 9e5
!change_initial_net = .true.
!new_net_name = 'agb.net'
!set_abundance = .true.
set_initial_abundance = .true.
chem_name = 'li7'
new_frac = 7.77594697D-09
!new_frac = 1.06927581475e-08
!set_abundance_nzlo = -1
!set_abundance_nzhi = -1
change_net=.true.
eos_file_prefix = 'mesa'
new_net_name = 'pp_extras.net'
kap_cache_dir = '/home/bruno/mesa-r8845/data/kap_data/cache'
kappa_file_prefix = 'OP_gs98'
dump_missing_metals_into_heaviest = .false.
set_uniform_initial_composition = .true.
initial_h1 = 0.6997725177
!initial y = 0.2797816935
initial_he3 = 0.0000279782
initial_he4 = 0.2797537154
initial_h2 = 0
set_rates_preference = .true.
new_rates_preference = 1
new_rotation_flag = .true.
change_rotation_flag = .false.
change_initial_rotation_flag = .true.
initial_zfracs = 7
new_surface_rotation_v = 2 ! solar (km sec^1)
set_near_zams_surface_rotation_v_steps = 10
pgstar_flag = .true.
/ ! end of star_job namelist
&controls
!max_age = 12000000000
stop_at_TP = .true.
! check for retries and backups as part of test_suite
! you can/should delete this for use outside of test_suite
max_number_backups = 200
max_number_retries = 500
max_model_number = 6000 !958 max
initial_mass = 1.08
initial_z = 0.0204457888
!initial_z = 0.02
initial_y = 0.2797816935
!use_Type2_opacities = .true.
Zbase = 0.0204457888
am_nu_visc_factor = 0
am_D_mix_factor = 0.0333333333333333d0
D_DSI_factor = 0
D_SH_factor = 1
D_SSI_factor = 1
D_ES_factor = 1
D_GSF_factor = 1
D_ST_factor = 1
varcontrol_target = 1d-3
mesh_delta_coeff = 1.5
photo_interval = 10
profile_interval = 50
history_interval = 1
terminal_interval = 10
write_header_frequency = 10
write_pulse_info_with_profile = .true. !.true. ! if true, write pulse
info file when write profile
pulse_info_format = 'FGONG'
log_L_lower_limit = -1
mixing_length_alpha = 1.9107649497
MLT_option = 'Cox'
! options are:
! 'Cox' MLT as developed in Cox & Giuli 1968, Chapter 14.
! 'ML1' Bohm-Vitense 1958
! 'ML2' Bohm and Cassinelli 1971
! 'Mihalas' Mihalas 1978, Kurucz 1979
! 'Henyey' Henyey, Vardya, and Bodenheimer 1965
! 'Cox' option assumes optically thick material.
! the other options are various ways of extending to include optically thin
material.
!which_atm_option = 'simple_photosphere'
smooth_convective_bdy = .true.
convective_bdy_weight = 1
D_visc_factor = 0
cool_wind_full_on_T = 9d6
cool_wind_full_off_T = 1d7
cool_wind_RGB_scheme = 'Reimers'
cool_wind_AGB_scheme = 'Blocker'
RGB_to_AGB_wind_switch = 1d-4
Reimers_scaling_factor = 0.5d0
Blocker_scaling_factor = 0.5d0
! FOR DEBUGGING
!report_hydro_solver_progress = .true. ! set true to see info about
newton iterations
!report_ierr = .true. ! if true, produce terminal output when have
some internal error
!hydro_show_correction_info = .true.
!max_years_for_timestep = 3.67628942044319d-05
!report_why_dt_limits = .true.
!report_all_dt_limits = .true.
!show_mesh_changes = .true.
!mesh_dump_call_number = 5189
!okay_to_remesh = .false.
trace_evolve = .true.
! hydro debugging
!hydro_check_everything = .true.
!hydro_inspectB_flag = .true.
!hydro_numerical_jacobian = .true.
!hydro_save_numjac_plot_data = .true.
!small_mtx_decsol = 'lapack'
!large_mtx_decsol = 'lapack'
!hydro_dump_call_number = 195
!trace_newton_bcyclic_solve_input = .true. ! input is "B" j k iter
B(j,k)
!trace_newton_bcyclic_solve_output = .true. ! output is "X" j k iter
X(j,k)
!trace_newton_bcyclic_steplo = 1 ! 1st model number to trace
!trace_newton_bcyclic_stephi = 1 ! last model number to trace
!trace_newton_bcyclic_iterlo = 2 ! 1st newton iter to trace
!trace_newton_bcyclic_iterhi = 2 ! last newton iter to trace
!trace_newton_bcyclic_nzlo = 1 ! 1st cell to trace
!trace_newton_bcyclic_nzhi = 10000 ! last cell to trace; if < 0, then
use nz as nzhi
!trace_newton_bcyclic_jlo = 1 ! 1st var to trace
!trace_newton_bcyclic_jhi = 100 ! last var to trace; if < 0, then use
nvar as jhi
!trace_k = 0
! misc
add_atmosphere_to_pulse_info = .true.
add_center_point_to_pulse_info = .true. ! add point for r=0
stop_at_TP = .true.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
! seismic data (frequencies in microHz)
!nu_max = 1010
! nu_max is needed when
! chi2_seismo_nu_max_fraction > 0 or correction_factor > 0 (see
below)
!nu_max_sigma = -1
! nu_max_sigma is needed when chi2_seismo_nu_max_fraction > 0
!delta_nu = 56.28
!delta_nu_sigma = 1.0
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
/ ! end of controls namelist
&pgstar
Power_win_flag = .false.
Power_win_width = 9
HR_win_flag = .true.
HR_win_width = 10
HR_win_aspect_ratio = 1
logg_logT_win_flag = .false.
logg_logT_win_width = 8
logg_logT_win_aspect_ratio = 1.0
Abundance_win_flag = .false.
Abundance_win_width = 6
Abundance_win_aspect_ratio = 1
HR_file_flag = .true.
HR_file_dir = 'png'
HR_file_prefix = 'HR_'
HR_title = 'DHR - Bruno'
! Mode Propagation window
Mode_Prop_win_flag = .false.
Mode_Prop_win_width = 10
Mode_Prop_win_aspect_ratio = 0.62 ! aspect_ratio = height/width
Mode_Prop_nu_max_obs = 1000
Mode_Prop_xaxis_name = 'r_div_R'
! power xaxis limits -- to override system default selections
Mode_Prop_xmin = -101 ! only used if > -100
Mode_Prop_xmax = 0.3 !-101 ! only used if > -100
! power yaxis limits -- to override system default selections
Mode_Prop_ymin = 2 ! -101 ! only used if > -100
Mode_Prop_ymax = 5 ! -101 ! only used if > -100
! file output
Mode_Prop_file_flag = .false.
Mode_Prop_file_dir = 'pgstar_out'
Mode_Prop_file_prefix = 'mode_prop'
Mode_Prop_file_interval = 5 ! output when
mod(model_number,Mode_Prop_file_interval)==0
Mode_Prop_file_width = -1 ! negative means use same value as for
window
Mode_Prop_file_aspect_ratio = -1 ! negative means use same value
as for window
/ ! end of pgstar namelist
|
|
From: Frank T. <fx...@ma...> - 2017-05-16 13:56:48
|
please post your entire inlist and the version of mesa you are using. fxt > On May 16, 2017, at 5:07 AM, Bruno Lustosa <bru...@gm...> wrote: > > Hello everyone > > I have a tense question about my model with regard to astero controls. By including chi2_seismo_fraction directly in my inlist in & controls the following: > > ! Seismic data > Chi2_seismo_fraction = 0.667d0 > Include_Teff_in_chi2_spectro = .true. > Teff_target = 4400d0 > Teff_sigma = 100d0 > Include_logg_in_chi2_spectro = .true. > Logg_target = 2.5d0 > Logg_sigma = 0.02d0 > Include_logL_in_chi2_spectro = .true. > LogL_target = 1.62d0 > LogL_sigma = 0.04d0 > Include_FeH_in_chi2_spectro = .true. ! [Fe / H] > FeH_target = 0.1 > FeH_sigma = 0.05 > Include_age_in_chi2_spectro = .true. > Age_target = 8.87d9! (See Bahcall, Serenelli, and Basu, 2006) > Age_sigma = 0.0065d9 > Num_smaller_steps_before_age_target = 50 > Dt_for_smaller_steps_before_age_target = 0.0065d8 > Chi2_seismo_delta_nu_fraction = 0d0 > ! If> 0 then delta_nu and delta_nu_sigma must be set (see below) > Chi2_seismo_nu_max_fraction = 0d0 > ! If> 0 then nu_max and nu_max_sigma must be set (see below) > Chi2_seismo_r_010_fraction = 0d0 > ! If> 0, then include r_010 frequency ratios > Chi2_seismo_r_02_fraction = 0d0 > ! If> 0, then include r_02 frequency ratios > ! Fraction for frequencies = 1 - (frac_r_010_ratios + frac_r_02_ratios + frac_delta_nu + frac_nu_max) > ! Nu_max = 70 > ! Nu_max_sigma = -1 > Delta_nu = -1 > Delta_nu_sigma = -1.0 > Eval_chi2_at_target_age_only = .true. > Search_type = 'use_first_values' > Simplex_itermax = 1000! Each iteration revises the simplex > Simplex_fcn_calls_max = 10000! May use several function calls per iteration > Simplex_x_atol = 1d-10! Tolerance for absolute differences > Simplex_x_rtol = 1d-10! Tolerance for relative differences > Simplex_centroid_weight_power = 0d0 > Simplex_output_filename = '16_maio.data' > Simplex_seed = 1074698122 > Oscillation_code = 'adipls > > The following error is reported: > > At line 1700 of file ../private/ctrls_io.f90 (unit = 30, file = 'inlist_2.0') > Fortran runtime error: Can not match namelist object name chi2_seismo_fraction > > > Have I or should I change some subroutine I did not do? > > > Cheers > > > Bruno > ------------------------------------------------------------------------------ > 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: Bruno L. <bru...@gm...> - 2017-05-16 12:07:08
|
Hello everyone
I have a tense question about my model with regard to astero controls. By
including chi2_seismo_fraction directly in my inlist in & controls the
following:
! Seismic data
Chi2_seismo_fraction = 0.667d0
Include_Teff_in_chi2_spectro = .true.
Teff_target = 4400d0
Teff_sigma = 100d0
Include_logg_in_chi2_spectro = .true.
Logg_target = 2.5d0
Logg_sigma = 0.02d0
Include_logL_in_chi2_spectro = .true.
LogL_target = 1.62d0
LogL_sigma = 0.04d0
Include_FeH_in_chi2_spectro = .true. ! [Fe / H]
FeH_target = 0.1
FeH_sigma = 0.05
Include_age_in_chi2_spectro = .true.
Age_target = 8.87d9! (See Bahcall, Serenelli, and Basu, 2006)
Age_sigma = 0.0065d9
Num_smaller_steps_before_age_target = 50
Dt_for_smaller_steps_before_age_target = 0.0065d8
Chi2_seismo_delta_nu_fraction = 0d0
! If> 0 then delta_nu and delta_nu_sigma must be set (see below)
Chi2_seismo_nu_max_fraction = 0d0
! If> 0 then nu_max and nu_max_sigma must be set (see below)
Chi2_seismo_r_010_fraction = 0d0
! If> 0, then include r_010 frequency ratios
Chi2_seismo_r_02_fraction = 0d0
! If> 0, then include r_02 frequency ratios
! Fraction for frequencies = 1 - (frac_r_010_ratios +
frac_r_02_ratios + frac_delta_nu + frac_nu_max)
! Nu_max = 70
! Nu_max_sigma = -1
Delta_nu = -1
Delta_nu_sigma = -1.0
Eval_chi2_at_target_age_only = .true.
Search_type = 'use_first_values'
Simplex_itermax = 1000! Each iteration revises the simplex
Simplex_fcn_calls_max = 10000! May use several function calls per
iteration
Simplex_x_atol = 1d-10! Tolerance for absolute differences
Simplex_x_rtol = 1d-10! Tolerance for relative differences
Simplex_centroid_weight_power = 0d0
Simplex_output_filename = '16_maio.data'
Simplex_seed = 1074698122
Oscillation_code = 'adipls
The following error is reported:
At line 1700 of file ../private/ctrls_io.f90 (unit = 30, file =
'inlist_2.0')
Fortran runtime error: Can not match namelist object name
chi2_seismo_fraction
Have I or should I change some subroutine I did not do?
Cheers
Bruno
|
|
From: Jean M. <je...@nm...> - 2017-05-10 17:27:48
|
r9680. Don't remember why I'm using that one though... I think it is using a newer version of GYRE. I must have over looked the l0_n_obs(:) line when i copied an inlist form some other project over. If I change that to be <0 it no longer produces negative delta_nu! Problem solved, just a user error. I'll try commenting those lines and see if the error goes away. It is clearly calculating the modes, plotting them, and moving on in the code either way. Just a nuisance at this point. 2017-05-10 3:57 GMT-06:00 Warrick Ball <wb...@bi...>: > Hi, > > So I looked into the issue with the "failed to find required l=0 modes" > message to try to make sense of what's going on. I think the segment of > code that causes the error message to be printed is unchanged from my > original report, and I've again concluded that it isn't a cause for > concern, except that the message doesn't correspond to what has happened in > the code. > > Actually, looking at the code, I'd say the line that prints the message > "failed to find required l=0 modes" is almost unnecessary. It relies on > the ouptut of get_radial, which, in almost each case, will print its own > message about why the code didn't proceed to compute the higher-degree > modes. The one case that currently doesn't print an error message is if > the oscillation code itself fails. Here are lines 637--646, inside > get_radial: > > call get_one_el_info(s, 0, & > nu_lower_factor*l0_obs(1), & > nu_upper_factor*l0_obs(nl0), & > iscan_factor_l0*nl0, 1, nl0, store_model, & > code, ierr) > if (ierr /= 0) then > !write(*,'(a65,i6)') 'failed in oscillation code', s% model_number > !stop > return > end if > > Any such early return means the function will return .false. and MESA > won't compute the non-radial mode frequencies. I'm not sure why the error > message "failed in oscillation code" is commented out: I'd find that quite > useful! > > So, for extras_support.f in r9575, I suggest: > - commenting line 374 and > - uncommenting line 643 (maybe with mention that it's in the radial mode > calculation). > > For other angular degrees, MESA just prints an error message if the > oscillation code returns with ierr /= 0, so I don't think any changes are > warranted. > > Cheers, > Warrick > > > > ------------ > Warrick Ball > Postdoc, School of Physics and Astronomy > University of Birmingham, Edgbaston, Birmingham B15 2TT > wb...@bi... > +44 (0)121 414 4552 > > On Wed, 10 May 2017, Warrick Ball wrote: > > Hi Jean, >> >> On the first issue, I started your run a few minutes ago but it looks >> like it'll take a while to finish. Out of curiosity, which revision are >> you using? Your GYRE input gave me a read failure in r9575 (no namelist >> object "diff_scheme") so I've just used the default for now. >> >> Regarding the "failed to find required l=0 modes", I looked into this >> over two years ago: >> >> https://sourceforge.net/p/mesa/mailman/message/33028229/ >> >> Ignore my proposed fix: that wasn't the solution. It seems Rich started >> looking into where the code changed but I couldn't find anything further on >> the mailing lists. I've cc'ed Rich, in case he can recall if he made any >> progress. >> >> As far as I know, it's nothing to worry about. But now that you've >> brought it up again, it's inspired me to have another close look at why the >> message is issued and what should be happening instead. Hopefully more as >> the day progresses here. >> >> Cheers, >> Warrick >> >> PS: I noticed your inlist has the line >> >> l0_n_obs(:) = 6 ! the observed radial orders (ignored if < 0) >> >> AFAIK, this should be the observed radial orders of the radial modes, >> which presumably aren't all 6! (You can choose to let MESA infer the >> radial orders of the modes: see lines 660--686 in >> $MESA_DIR/star/astero/work/astero_support.f.) >> >> >> >> ------------ >> Warrick Ball >> Postdoc, School of Physics and Astronomy >> University of Birmingham, Edgbaston, Birmingham B15 2TT >> wb...@bi... >> +44 (0)121 414 4552 >> >> On Tue, 9 May 2017, Jean McKeever wrote: >> >> Here are the inlists I used. >>> >>> 2017-05-08 17:22 GMT-06:00 Jean McKeever <je...@nm...>: >>> Hello, >>> >>> I am running some models using astero and have ran into an interesting >>> conundrum. As soon as astero starts computing individual frequencies, >>> the >>> delta_nu value, both printed on the graph display and >>> written to the history file, becomes negative. I am using gyre to >>> compute >>> only radial modes. Has anyone else encountered this or something >>> similar? >>> >>> On another note I am constantly getting a "failed to find required l=0 >>> modes" message, however modes appear on the echelle diagram. I have >>> double >>> checked my gyre input files are in the right units and >>> cover the range of observed modes. Is this something to worry about? >>> >>> >>> Jean McKeever >>> >>> >>> >>> >>> |
|
From: Warrick B. <wb...@bi...> - 2017-05-10 09:58:01
|
Hi,
So I looked into the issue with the "failed to find required l=0 modes"
message to try to make sense of what's going on. I think the segment of
code that causes the error message to be printed is unchanged from my
original report, and I've again concluded that it isn't a cause for
concern, except that the message doesn't correspond to what has happened
in the code.
Actually, looking at the code, I'd say the line that prints the message
"failed to find required l=0 modes" is almost unnecessary. It relies on
the ouptut of get_radial, which, in almost each case, will print its own
message about why the code didn't proceed to compute the higher-degree
modes. The one case that currently doesn't print an error message is if
the oscillation code itself fails. Here are lines 637--646, inside
get_radial:
call get_one_el_info(s, 0, &
nu_lower_factor*l0_obs(1), &
nu_upper_factor*l0_obs(nl0), &
iscan_factor_l0*nl0, 1, nl0, store_model, &
code, ierr)
if (ierr /= 0) then
!write(*,'(a65,i6)') 'failed in oscillation code', s% model_number
!stop
return
end if
Any such early return means the function will return .false. and MESA
won't compute the non-radial mode frequencies. I'm not sure why the error
message "failed in oscillation code" is commented out: I'd find that quite
useful!
So, for extras_support.f in r9575, I suggest:
- commenting line 374 and
- uncommenting line 643 (maybe with mention that it's in the radial mode
calculation).
For other angular degrees, MESA just prints an error message if the
oscillation code returns with ierr /= 0, so I don't think any changes are
warranted.
Cheers,
Warrick
------------
Warrick Ball
Postdoc, School of Physics and Astronomy
University of Birmingham, Edgbaston, Birmingham B15 2TT
wb...@bi...
+44 (0)121 414 4552
On Wed, 10 May 2017, Warrick Ball wrote:
> Hi Jean,
>
> On the first issue, I started your run a few minutes ago but it looks like
> it'll take a while to finish. Out of curiosity, which revision are you
> using? Your GYRE input gave me a read failure in r9575 (no namelist object
> "diff_scheme") so I've just used the default for now.
>
> Regarding the "failed to find required l=0 modes", I looked into this over
> two years ago:
>
> https://sourceforge.net/p/mesa/mailman/message/33028229/
>
> Ignore my proposed fix: that wasn't the solution. It seems Rich started
> looking into where the code changed but I couldn't find anything further on
> the mailing lists. I've cc'ed Rich, in case he can recall if he made any
> progress.
>
> As far as I know, it's nothing to worry about. But now that you've brought
> it up again, it's inspired me to have another close look at why the message
> is issued and what should be happening instead. Hopefully more as the day
> progresses here.
>
> Cheers,
> Warrick
>
> PS: I noticed your inlist has the line
>
> l0_n_obs(:) = 6 ! the observed radial orders (ignored if < 0)
>
> AFAIK, this should be the observed radial orders of the radial modes, which
> presumably aren't all 6! (You can choose to let MESA infer the radial orders
> of the modes: see lines 660--686 in
> $MESA_DIR/star/astero/work/astero_support.f.)
>
>
>
> ------------
> Warrick Ball
> Postdoc, School of Physics and Astronomy
> University of Birmingham, Edgbaston, Birmingham B15 2TT
> wb...@bi...
> +44 (0)121 414 4552
>
> On Tue, 9 May 2017, Jean McKeever wrote:
>
>> Here are the inlists I used.
>>
>> 2017-05-08 17:22 GMT-06:00 Jean McKeever <je...@nm...>:
>> Hello,
>>
>> I am running some models using astero and have ran into an interesting
>> conundrum. As soon as astero starts computing individual frequencies, the
>> delta_nu value, both printed on the graph display and
>> written to the history file, becomes negative. I am using gyre to compute
>> only radial modes. Has anyone else encountered this or something similar?
>>
>> On another note I am constantly getting a "failed to find required l=0
>> modes" message, however modes appear on the echelle diagram. I have double
>> checked my gyre input files are in the right units and
>> cover the range of observed modes. Is this something to worry about?
>>
>>
>> Jean McKeever
>>
>>
>>
>>
> |
|
From: Warrick B. <wb...@bi...> - 2017-05-10 09:04:49
|
Hi Jean, On the first issue, I started your run a few minutes ago but it looks like it'll take a while to finish. Out of curiosity, which revision are you using? Your GYRE input gave me a read failure in r9575 (no namelist object "diff_scheme") so I've just used the default for now. Regarding the "failed to find required l=0 modes", I looked into this over two years ago: https://sourceforge.net/p/mesa/mailman/message/33028229/ Ignore my proposed fix: that wasn't the solution. It seems Rich started looking into where the code changed but I couldn't find anything further on the mailing lists. I've cc'ed Rich, in case he can recall if he made any progress. As far as I know, it's nothing to worry about. But now that you've brought it up again, it's inspired me to have another close look at why the message is issued and what should be happening instead. Hopefully more as the day progresses here. Cheers, Warrick PS: I noticed your inlist has the line l0_n_obs(:) = 6 ! the observed radial orders (ignored if < 0) AFAIK, this should be the observed radial orders of the radial modes, which presumably aren't all 6! (You can choose to let MESA infer the radial orders of the modes: see lines 660--686 in $MESA_DIR/star/astero/work/astero_support.f.) ------------ Warrick Ball Postdoc, School of Physics and Astronomy University of Birmingham, Edgbaston, Birmingham B15 2TT wb...@bi... +44 (0)121 414 4552 On Tue, 9 May 2017, Jean McKeever wrote: > Here are the inlists I used. > > 2017-05-08 17:22 GMT-06:00 Jean McKeever <je...@nm...>: > Hello, > > I am running some models using astero and have ran into an interesting conundrum. As soon as astero starts computing individual frequencies, the delta_nu value, both printed on the graph display and > written to the history file, becomes negative. I am using gyre to compute only radial modes. Has anyone else encountered this or something similar? > > On another note I am constantly getting a "failed to find required l=0 modes" message, however modes appear on the echelle diagram. I have double checked my gyre input files are in the right units and > cover the range of observed modes. Is this something to worry about? > > > Jean McKeever > > > > |
|
From: Frank T. <fx...@ma...> - 2017-05-09 20:24:05
|
it may help if you send your inlist(s) to mesa-users and say something more deatiled about what you're trying to accomplish with the inlist(s). fxt > On May 9, 2017, at 10:38 AM, AbdelBassit Abdessamed Senhadji <se...@ho...> wrote: > > Hi all : > > I am trying to repduce the ‘’extrem horizontal branch star’’ on MESA, but i had problems on that i get an evolution after the red geant step. > > Do you have any hint or advice to do the code correctly ! > > > Cheers > > Abdel > > Provenance : Courrier pour Windows 10 > > ------------------------------------------------------------------------------ > 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 |
138 messages has been excluded from this view by a project administrator.
