mesa-users — open list for mesa comments, questions, & answers

Re: [mesa-users] attempt to compile revision 2808 with ifort 11.1/046

[Aaron D. <aar...@gm...>]

Hi Georgios,

First, was this a fresh install or an update?

If it was an update, did you run the clean script first?  That is the most
common cause of such an error (if it is not inherent).

The amount of info provided is not enough for me to say more without some
additional information.  ifort 11.1.072 and above seem to work fine.  Does
anyone have results from an earlier version of 11.1?

Aaron

Re: [mesa-users] attempt to compile revision 2808 with ifort 11.1/046

[Bill P. <pa...@ki...>]

Hi Georgios,

I'm sad to hear you are having problems, especially since they are unnecessary.
Perhaps you'll be able to track this one down or someone else with more free
time than I have will be able to help you out.   I personally want to spend my
time on developing mesa rather than tracking down problems caused by old
versions of compilers.

I think your best option is to talk to your advisor(s) and light a fire under your
so-called "support" team.

-Bill








On Dec 3, 2010, at 10:14 AM, Georgios Magkotsios wrote:

> Dear MESA developers,
> 
> I am aware that MESA requires the latest compiler versions to compile 
> successfully. Unfortunately, our machines have ifort 11.1/046 and gcc 
> version 4.4.4. Both fail some tests during installation (ifort in eos 
> and gfortran in diffusion modules).
> 
> I requested from our support team if they could update the compilers, 
> but they would like to confirm first that compilation cannot work under 
> any circumstances. With ifort they used some debugging options and see 
> the error message below. Could you please explain what this error means, 
> and whether you think it is really a compiler problem? Thank you.
> 
> Georgios
> 
> <snip>
>                      tolerance  1.0000000000000000E-04
> 
>  do_eos_look_for_brackets returned ierr          -1
>                                        x   -7.3010299956639813E+00
>                                       dx    1.0000000000000001E-01
>                                      xb1   -7.5010299956639814E+00
>                                      xb3   -7.1010299956639811E+00
>  ntry         100
>  lrpar         472
>  lipar        5487
>  ierr in test_get_Rho_T          -1
>  alert_message
> </snip>
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
> Tap into the largest installed PC base & get more eyes on your game by
> optimizing for Intel(R) Graphics Technology. Get started today with the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
> http://p.sf.net/sfu/intelisp-dev2dev
> _______________________________________________
> mesa-users mailing list
> mes...@li...
> https://lists.sourceforge.net/lists/listinfo/mesa-users

[mesa-users] attempt to compile revision 2808 with ifort 11.1/046

[Georgios M. <gma...@nd...>]

Dear MESA developers,

I am aware that MESA requires the latest compiler versions to compile 
successfully. Unfortunately, our machines have ifort 11.1/046 and gcc 
version 4.4.4. Both fail some tests during installation (ifort in eos 
and gfortran in diffusion modules).

I requested from our support team if they could update the compilers, 
but they would like to confirm first that compilation cannot work under 
any circumstances. With ifort they used some debugging options and see 
the error message below. Could you please explain what this error means, 
and whether you think it is really a compiler problem? Thank you.

Georgios

<snip>
                      tolerance  1.0000000000000000E-04

  do_eos_look_for_brackets returned ierr          -1
                                        x   -7.3010299956639813E+00
                                       dx    1.0000000000000001E-01
                                      xb1   -7.5010299956639814E+00
                                      xb3   -7.1010299956639811E+00
  ntry         100
  lrpar         472
  lipar        5487
  ierr in test_get_Rho_T          -1
  alert_message
</snip>

Re: [mesa-users] Falure to install Mesa 2808

[Alessandro P. <ale...@gm...>]

Hi Larry,

let me share with you my experience.
First of all, on which OS are you trying to install mesa ?
Consider that on linux Ubuntu the libX11.a file is in /usr/lib/ and not in
/usr/X11R6/lib as you
are using in your makefile.

To use pgplot you need also to change the path "
/Users/bpaxton/pgplot_gfortran_gcc/lib"
to the correct path where you have your pgplot software.
In my case I installed pgplot in  "/usr/local/pgplot/".
To find out where do you have pgplot (assuming you have already installed
it) you can type from a terminal "whereis pgplot".
Then copy the path to the makefile_header and recompile.

Cheers,

A.


On Fri, Dec 3, 2010 at 1:47 AM, Aaron Dotter <aar...@gm...> wrote:

> Hi Larry,
>
> It looks like you've got a non-default option set in your
> utils/makefile_header (likely not your fault).  Assuming that you are not
> trying to install the PGplot interface to star, just edit the following
> lines in mesa/utils/makefile_header:
>
> ifeq ($(FC),gfortran)
>
> #USE_PGSTAR = NO
> #LOAD_PGPLOT =
> USE_PGSTAR = YES
> LOAD_PGPLOT = -L/Users/bpaxton/pgplot_gfortran_gcc/lib -lpgplot
> -L/usr/X11R6/lib -lX11 -lpng
>
> to look like this
>
> ifeq ($(FC),gfortran)
>
> USE_PGSTAR = NO
> LOAD_PGPLOT =
> #USE_PGSTAR = YES
> #LOAD_PGPLOT = -L/Users/bpaxton/pgplot_gfortran_gcc/lib -lpgplot
> -L/usr/X11R6/lib -lX11 -lpng
>
> and run the install script again.  Please let us know if this does not fix
> your problem.
>
> Best wishes,
> Aaron
>
>
>
> On Thu, Dec 2, 2010 at 5:48 PM, Larry Pinsonneault <lpi...@ha...>wrote:
>
>> Installing Mesa version 2808 failed with error message :
>>
>> "
>> /astro/mesa/star
>> building star package.
>>
>> make: `libstar.a' is up to date.
>> gfortran -fno-range-check  -fopenmp  -o ../star \
>>     run_star_extras.o run_star.o  run.o -L../../make -lstar
>> -L../../../lib -ldiffusion -lionization -lmlt -latm -lother_atm -lkaro
>> -lcolors -leos -lother_eos -lkap -lother_kap -ljina -lweak -lnet
>> -lscreen -lrates -lneu -lchem -linterp_2d -linterp_1d -lnum -lutils
>> -lalert -lconst -lmtx -lmesalapack -lmesablas
>> -L/Users/bpaxton/pgplot_gfortran_gcc/lib -lpgplot -L/usr/X11R6/lib -lX11
>> -lpng
>> /usr/bin/ld: cannot find -lX11
>> collect2: ld returned 1 exit status
>> make: *** [star] Error 1
>>
>> /astro/mesa/star/test/make
>> FAILED
>> "
>>
>> This says that file 'libX1.a' could not be found. 'locate libX11.a' found
>> nothing also.
>>
>> How do I find or create this file?
>>
>> Larry Pinsonneault
>>
>>
>> ------------------------------------------------------------------------------
>> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
>> Tap into the largest installed PC base & get more eyes on your game by
>> optimizing for Intel(R) Graphics Technology. Get started today with the
>> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
>> http://p.sf.net/sfu/intelisp-dev2dev
>> _______________________________________________
>> mesa-users mailing list
>> mes...@li...
>> https://lists.sourceforge.net/lists/listinfo/mesa-users
>>
>
>
>
> ------------------------------------------------------------------------------
> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
> Tap into the largest installed PC base & get more eyes on your game by
> optimizing for Intel(R) Graphics Technology. Get started today with the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
> http://p.sf.net/sfu/intelisp-dev2dev
> _______________________________________________
> mesa-users mailing list
> mes...@li...
> https://lists.sourceforge.net/lists/listinfo/mesa-users
>
>

Re: [mesa-users] Falure to install Mesa 2808

[Aaron D. <aar...@gm...>]

Hi Larry,

It looks like you've got a non-default option set in your
utils/makefile_header (likely not your fault).  Assuming that you are not
trying to install the PGplot interface to star, just edit the following
lines in mesa/utils/makefile_header:

ifeq ($(FC),gfortran)

#USE_PGSTAR = NO
#LOAD_PGPLOT =
USE_PGSTAR = YES
LOAD_PGPLOT = -L/Users/bpaxton/pgplot_gfortran_gcc/lib -lpgplot
-L/usr/X11R6/lib -lX11 -lpng

to look like this

ifeq ($(FC),gfortran)

USE_PGSTAR = NO
LOAD_PGPLOT =
#USE_PGSTAR = YES
#LOAD_PGPLOT = -L/Users/bpaxton/pgplot_gfortran_gcc/lib -lpgplot
-L/usr/X11R6/lib -lX11 -lpng

and run the install script again.  Please let us know if this does not fix
your problem.

Best wishes,
Aaron



On Thu, Dec 2, 2010 at 5:48 PM, Larry Pinsonneault <lpi...@ha...>wrote:

> Installing Mesa version 2808 failed with error message :
>
> "
> /astro/mesa/star
> building star package.
>
> make: `libstar.a' is up to date.
> gfortran -fno-range-check  -fopenmp  -o ../star \
>     run_star_extras.o run_star.o  run.o -L../../make -lstar
> -L../../../lib -ldiffusion -lionization -lmlt -latm -lother_atm -lkaro
> -lcolors -leos -lother_eos -lkap -lother_kap -ljina -lweak -lnet
> -lscreen -lrates -lneu -lchem -linterp_2d -linterp_1d -lnum -lutils
> -lalert -lconst -lmtx -lmesalapack -lmesablas
> -L/Users/bpaxton/pgplot_gfortran_gcc/lib -lpgplot -L/usr/X11R6/lib -lX11
> -lpng
> /usr/bin/ld: cannot find -lX11
> collect2: ld returned 1 exit status
> make: *** [star] Error 1
>
> /astro/mesa/star/test/make
> FAILED
> "
>
> This says that file 'libX1.a' could not be found. 'locate libX11.a' found
> nothing also.
>
> How do I find or create this file?
>
> Larry Pinsonneault
>
>
> ------------------------------------------------------------------------------
> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
> Tap into the largest installed PC base & get more eyes on your game by
> optimizing for Intel(R) Graphics Technology. Get started today with the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
> http://p.sf.net/sfu/intelisp-dev2dev
> _______________________________________________
> mesa-users mailing list
> mes...@li...
> https://lists.sourceforge.net/lists/listinfo/mesa-users
>

[mesa-users] Falure to install Mesa 2808

[Larry P. <lpi...@ha...>]

Installing Mesa version 2808 failed with error message :

"
/astro/mesa/star
building star package.

make: `libstar.a' is up to date.
gfortran -fno-range-check  -fopenmp  -o ../star \
     run_star_extras.o run_star.o  run.o -L../../make -lstar 
-L../../../lib -ldiffusion -lionization -lmlt -latm -lother_atm -lkaro 
-lcolors -leos -lother_eos -lkap -lother_kap -ljina -lweak -lnet 
-lscreen -lrates -lneu -lchem -linterp_2d -linterp_1d -lnum -lutils 
-lalert -lconst -lmtx -lmesalapack -lmesablas 
-L/Users/bpaxton/pgplot_gfortran_gcc/lib -lpgplot -L/usr/X11R6/lib -lX11 
-lpng
/usr/bin/ld: cannot find -lX11
collect2: ld returned 1 exit status
make: *** [star] Error 1

/astro/mesa/star/test/make
FAILED
"

This says that file 'libX1.a' could not be found. 'locate libX11.a' found
nothing also.

How do I find or create this file?

Larry Pinsonneault

Re: [mesa-users] Installing problem

[Aaron D. <aar...@gm...>]

Hi,

If you can please provide us with more information, such as the version of
MESA and the OS, it can help to figure out what is wrong.

It can also help to tell us what is happening: does the compile process
hang?  Does the test fail?

Finally, just from looking at the output you sent it seems there is
something not quite right in utils/makefile_header.  You've got both

-fopenmp

and

-openmp

but only one should be enabled.  Also, it looks like you're trying to
compile with the Intel MKL enabled.  Have you tried compiling first without
it?

Aaron




On Tue, Nov 30, 2010 at 2:23 AM, 張世昕 <ss...@as...> wrote:

> Hi,
> When i installed mesa, the process stuck at one place....
>
> /penguin/apps/build/mesa/net
> building net package.
>
> ifort -fopenmp -vec-report0 -traceback -error-limit 6 -openmp -threads
> -I../public -I../private -I../../include -warn all -warn nounused
> -implicitnone -O2 -c -fixed -132 ../public/net_def.f
> ifort: command line warning #10006: ignoring unknown option '-fopenmp'
> ifort -fopenmp -vec-report0 -traceback -error-limit 6 -openmp -threads
> -I../public -I../private -I../../include -warn all -warn nounused
> -implicitnone -O2 -c -fixed -132 ../public/net_lib.f
> ifort: command line warning #10006: ignoring unknown option '-fopenmp'
> ar crs libnet.a net_def.o net_raw_rates.o net_screen.o
> net_derivs_support.o net_derivs.o net_initialize.o net_eval.o net_burn.o
> net_burn_const_P.o net_lib.o
> ifort -openmp -threads -o ../tester test_net_support.o test_burn.o
> test_burn_const_P.o test_net.o -L../../make -lnet -L../../../lib -leos
> -lscreen -lrates -lchem -linterp_2d -linterp_1d -lnum -lutils -lalert
> -lconst -lmtx -L/penguin/apps/intel/composerxe-2011.0.084/mkl
> -I/penguin/apps/intel/composerxe-2011.0.084/mkl/include
> -I/penguin/apps/intel/composerxe-2011.0.084/mkl/include/em64t/lp64
> -L/penguin/apps/intel/composerxe-2011.0.084/mkl/lib/em64t
> -lmkl_intel_lp64 -lmkl_intel_thread -lmkl_lapack -lmkl_core -liomp5
> -lpthread
> ifort -openmp -threads -o ../plotter test_net_support.o test_burn.o
> plot_net.o -L../../make -lnet -L../../../lib -leos -lscreen -lrates
> -lchem -linterp_2d -linterp_1d -lnum -lutils -lalert -lconst -lmtx
> -L/penguin/apps/intel/composerxe-2011.0.084/mkl
> -I/penguin/apps/intel/composerxe-2011.0.084/mkl/include
> -I/penguin/apps/intel/composerxe-2011.0.084/mkl/include/em64t/lp64
> -L/penguin/apps/intel/composerxe-2011.0.084/mkl/lib/em64t
> -lmkl_intel_lp64 -lmkl_intel_thread -lmkl_lapack -lmkl_core -liomp5
> -lpthread
>
> Please tell me what mistake i made. Any comments?
> Thanks!!!
>
>
>
>
> ------------------------------------------------------------------------------
> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
> Tap into the largest installed PC base & get more eyes on your game by
> optimizing for Intel(R) Graphics Technology. Get started today with the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
> http://p.sf.net/sfu/intelisp-dev2dev
> _______________________________________________
> mesa-users mailing list
> mes...@li...
> https://lists.sourceforge.net/lists/listinfo/mesa-users
>
>

Re: [mesa-users] Installing problem

[Bill P. <pa...@ki...>]

Hi,

In the past, problems like this have been resolved by using 
an up-to-date version of the compiler.   Which version of ifort
are you using?   I am currently using 11.1/089, so you would
probably want to update to that as well.

I hope that helps.  If not, please let us know.

Cheers,
Bill Paxton







On Nov 29, 2010, at 11:23 PM, 張世昕 wrote:

>> Hi,
>> When i installed mesa, the process stuck at one place....
>> 
>> /penguin/apps/build/mesa/net
>> building net package.
>> 
>> ifort -fopenmp -vec-report0 -traceback -error-limit 6 -openmp -threads
>> -I../public -I../private -I../../include -warn all -warn nounused
>> -implicitnone -O2 -c -fixed -132 ../public/net_def.f
>> ifort: command line warning #10006: ignoring unknown option '-fopenmp'
>> ifort -fopenmp -vec-report0 -traceback -error-limit 6 -openmp -threads
>> -I../public -I../private -I../../include -warn all -warn nounused
>> -implicitnone -O2 -c -fixed -132 ../public/net_lib.f
>> ifort: command line warning #10006: ignoring unknown option '-fopenmp'
>> ar crs libnet.a net_def.o net_raw_rates.o net_screen.o
>> net_derivs_support.o net_derivs.o net_initialize.o net_eval.o net_burn.o
>> net_burn_const_P.o net_lib.o
>> ifort -openmp -threads -o ../tester test_net_support.o test_burn.o
>> test_burn_const_P.o test_net.o -L../../make -lnet -L../../../lib -leos
>> -lscreen -lrates -lchem -linterp_2d -linterp_1d -lnum -lutils -lalert
>> -lconst -lmtx -L/penguin/apps/intel/composerxe-2011.0.084/mkl
>> -I/penguin/apps/intel/composerxe-2011.0.084/mkl/include
>> -I/penguin/apps/intel/composerxe-2011.0.084/mkl/include/em64t/lp64
>> -L/penguin/apps/intel/composerxe-2011.0.084/mkl/lib/em64t
>> -lmkl_intel_lp64 -lmkl_intel_thread -lmkl_lapack -lmkl_core -liomp5
>> -lpthread
>> ifort -openmp -threads -o ../plotter test_net_support.o test_burn.o
>> plot_net.o -L../../make -lnet -L../../../lib -leos -lscreen -lrates
>> -lchem -linterp_2d -linterp_1d -lnum -lutils -lalert -lconst -lmtx
>> -L/penguin/apps/intel/composerxe-2011.0.084/mkl
>> -I/penguin/apps/intel/composerxe-2011.0.084/mkl/include
>> -I/penguin/apps/intel/composerxe-2011.0.084/mkl/include/em64t/lp64
>> -L/penguin/apps/intel/composerxe-2011.0.084/mkl/lib/em64t
>> -lmkl_intel_lp64 -lmkl_intel_thread -lmkl_lapack -lmkl_core -liomp5
>> -lpthread
>> 
>> Please tell me what mistake i made. Any comments?
>> Thanks!!!
> 
> ------------------------------------------------------------------------------
> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
> Tap into the largest installed PC base & get more eyes on your game by
> optimizing for Intel(R) Graphics Technology. Get started today with the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
> http://p.sf.net/sfu/intelisp-dev2dev_______________________________________________
> mesa-users mailing list
> mes...@li...
> https://lists.sourceforge.net/lists/listinfo/mesa-users

[mesa-users] Installing problem

[張世昕 <ss...@as...>]

Hi,
When i installed mesa, the process stuck at one place....

/penguin/apps/build/mesa/net
building net package.

ifort -fopenmp -vec-report0 -traceback -error-limit 6 -openmp -threads
-I../public -I../private -I../../include -warn all -warn nounused
-implicitnone -O2 -c -fixed -132 ../public/net_def.f
ifort: command line warning #10006: ignoring unknown option '-fopenmp'
ifort -fopenmp -vec-report0 -traceback -error-limit 6 -openmp -threads
-I../public -I../private -I../../include -warn all -warn nounused
-implicitnone -O2 -c -fixed -132 ../public/net_lib.f
ifort: command line warning #10006: ignoring unknown option '-fopenmp'
ar crs libnet.a net_def.o net_raw_rates.o net_screen.o
net_derivs_support.o net_derivs.o net_initialize.o net_eval.o net_burn.o
net_burn_const_P.o net_lib.o
ifort -openmp -threads -o ../tester test_net_support.o test_burn.o
test_burn_const_P.o test_net.o -L../../make -lnet -L../../../lib -leos
-lscreen -lrates -lchem -linterp_2d -linterp_1d -lnum -lutils -lalert
-lconst -lmtx -L/penguin/apps/intel/composerxe-2011.0.084/mkl
-I/penguin/apps/intel/composerxe-2011.0.084/mkl/include
-I/penguin/apps/intel/composerxe-2011.0.084/mkl/include/em64t/lp64
-L/penguin/apps/intel/composerxe-2011.0.084/mkl/lib/em64t
-lmkl_intel_lp64 -lmkl_intel_thread -lmkl_lapack -lmkl_core -liomp5
-lpthread
ifort -openmp -threads -o ../plotter test_net_support.o test_burn.o
plot_net.o -L../../make -lnet -L../../../lib -leos -lscreen -lrates
-lchem -linterp_2d -linterp_1d -lnum -lutils -lalert -lconst -lmtx
-L/penguin/apps/intel/composerxe-2011.0.084/mkl
-I/penguin/apps/intel/composerxe-2011.0.084/mkl/include
-I/penguin/apps/intel/composerxe-2011.0.084/mkl/include/em64t/lp64
-L/penguin/apps/intel/composerxe-2011.0.084/mkl/lib/em64t
-lmkl_intel_lp64 -lmkl_intel_thread -lmkl_lapack -lmkl_core -liomp5
-lpthread

Please tell me what mistake i made. Any comments?
Thanks!!!

Re: mesa-users] Adding a new nuclear reaction rates in MESA

[Aaron D. <aar...@gm...>]

Hi Zahra,

Yes, you can test the rates being used by the rates module.  Bill and I have
looked at this and the easiest way to check the rate is to edit the rates
module test code in mesa/rates/test/src/test_rates.f.  There is a subroutine
called "test1" that prints out the rate of one reaction for one temperature,
though you could easily modify this to do a loop over temperature.

At the very bottom of test_rates.f is the line
      !call test1; stop

Uncomment that line and then modify subroutine test1 to use the rate and
temperature(s) that you want.  Change the rate by setting ir to the rate ID
you've added to rate_list.txt.

Then do a ./mk and ./rn in mesa/rates/test/.  Simply change the entry in
rate_list.txt and then run again to see the difference.

Since mesa/star uses mesa/rates, once you're sure that it's working as you
expect in the rates test code, it should also be working as you expect in
mesa/star.

Aaron


On Mon, Nov 8, 2010 at 3:14 AM, zahra altaha motahar <zam...@ya...>wrote:

> Hi,
>
> Recently, I have added my new nuclear reaction rates in the MESA code. I
> produce a table of temperatures and rates and save it in the
> net_data/rates/directory. Then, I add the filename and reaction name to the
> "rate_list.txt" and run the code.
> How can I make sure that the MESA code uses our added new nuclear reaction
> rates instead of the NACRE rates for its modeling?
>
> Thank you,
> Zahra
>
>
> ------------------------------------------------------------------------------
> The Next 800 Companies to Lead America's Growth: New Video Whitepaper
> David G. Thomson, author of the best-selling book "Blueprint to a
> Billion" shares his insights and actions to help propel your
> business during the next growth cycle. Listen Now!
> http://p.sf.net/sfu/SAP-dev2dev
> _______________________________________________
> mesa-users mailing list
> mes...@li...
> https://lists.sourceforge.net/lists/listinfo/mesa-users
>
>

mesa-users] Adding a new nuclear reaction rates in MESA

[zahra a. m. <zam...@ya...>]

Hi, 



Recently, I have added my new nuclear reaction rates in the MESA code. I
 produce a table of temperatures and rates and save it in the 
net_data/rates/directory. Then, I add the filename and reaction name to 
the "rate_list.txt" and run the code.

How can I make sure that the MESA code uses our added new nuclear reaction rates instead of the NACRE rates for its modeling?



Thank you, 

Zahra

Re: mesa-users] How to evolve a sequence of binaries ?

[Bill P. <pa...@ki...>]

On Nov 3, 2010, at 12:31 PM, Alessandro Patruno wrote:
> 
> I need to evolve a grid of binaries, with different donor and accretor masses (from 0.4 to 2 Msun) 
> and different orbital periods. 
> 
> Can you suggest me a way to do so ? 
> With the Eggleton code it was possible to set a initial and final parameter and the step-size
> of that parameter. 
> I see that something similar is used in the "create_zams" test suite, where you have the "mhi", "mlo" and 
> the mass step "dmass" in log units. 
> Is there something similar I can use for period, accretor and donor mass ? 
> 
> Many thanks !!
> 
> Ale

Hi Ale,

The mesa philosophy on this one is to give some examples, and then
rely on users to create their own "applications".   So you won't find exactly
what you are looking for, but as you mention, create_zams does something
similar.  Please do me the favor of trying to develop what you need using
create_zams as a template.  I'm happy to help you along with this -- and
then please write up some short notes about how to do it that can be added to
the mesa release for future users.

Thanks,
Bill

mesa-users] How to evolve a sequence of binaries ?

[Alessandro P. <ale...@gm...>]

Hi,

sorry to bother again, another question about MESA, possibly the last one.
:-)

I need to evolve a grid of binaries, with different donor and accretor
masses (from 0.4 to 2 Msun)
and different orbital periods.

Can you suggest me a way to do so ?
With the Eggleton code it was possible to set a initial and final parameter
and the step-size
of that parameter.
I see that something similar is used in the "create_zams" test suite, where
you have the "mhi", "mlo" and
the mass step "dmass" in log units.
Is there something similar I can use for period, accretor and donor mass ?

Many thanks !!

Ale

Re: mesa-users] Hydro convergence failure at end of main sequence.

[Bill P. <pa...@ki...>]

Hi Sam,

On Nov 3, 2010, at 3:42 AM, Sam Jones wrote:

> Hi Bill,
> 
> Thanks a lot for all the help. Aaron suggested decreasing the varcontrol_target parameter slightly (which has advanced burning beyond main sequence). I will try using the dX_limit parameters instead of varcontrol parameters, begin from the inlist in test_suite and let you know how I get on!
> 
> Many thanks again,
> Sam.


Good.   It took me a long time and lots of failures to find a recipe for massive stars that works at least some of the time!  While you are of course welcome to start over without using the results of my "blood, sweat, and tears", I think you will make faster progress by doing incremental changes to the relevant inlist from the test_suite.  However, don't treat it as the immutable final answer either!  There are undoubtedly things in there that are not really doing anything useful -- leftovers from my many failed experiments.  And there are also surely things that could be done differently that would improve performance and accuracy.  So I'd encourage you to spend some time to understand the things in that inlist and try making changes to them.

Cheers,
Bill

Re: mesa-users] Problem creating low Z stars and ZAMS models

[Alessandro P. <ale...@gm...>]

Hi Aaron,

you are totally right, I just realized that I was using a 0.9 instead of 0.8
Msun...
Sorry if I wasted your time and thanks for the answer.
Everything is working perfectly !

A.


On Wed, Nov 3, 2010 at 12:04 PM, Aaron Dotter <aar...@gm...>wrote:

> Dear Ale,
>
> If you want a model with a main sequence lifetime of ~12 Gyr for Z=10^-4, I
> recommend choosing M ~ 0.8 Msun. For 0.9 Msun, 7-8 Gyr is perfectly
> reasonable.
>
> If  you look at the MESA paper, we have an example of 0.8 Msun, Z=10^-4
> from four different codes and they all have MS lifetimes of ~12 Gyr (see
> figure 19).
>
> Best wishes,
> Aaron
>
>
>
> On Tue, Nov 2, 2010 at 6:35 PM, Alessandro Patruno <ale...@gm...>wrote:
>
>> Hi everyone,
>>
>> I was playing a bit with the test_suite
>> "low_z" and "create_zams" but I found two problems
>> I can't solve easily
>>
>> 1. How do I tell MESA to use a ZAMS model file that I created with
>> "create_zams" instead of the default ones ? I just created a Z=0.0001
>> ZAMS sequence (for Population II stars) and I'd like to use it now to load
>>
>> initial stellar models...
>>
>>
>> 2. I am creating a single star, a main sequence star of 0.9 Msun,
>> with Z=0.0001. So I use "low_z" in the test_suite.
>> My "inlist_low_z" has the lines:
>>
>> &star_job
>>       mesa_data_dir = '../../../data' ! for eos and opacity tables
>>       create_pre_main_sequence_model = .true.
>>       save_model_number=635
>>       save_model_filename='0p9-z0001.dat'
>>
>>
>> I start with a pre-main sequence model
>> and then let the evolution go until the code tells
>> me "starting main sequence". This happens at the 635-th time step
>> (that's why I wrote save_model_number=635).
>> I save the model in the file (0p9-z0001.dat), and I load it in the
>> test_suite called "rlo" to do binary evolution.
>>
>> The inlist_test_rlo file has these lines n the &star_job section:
>>
>> &star_job
>>
>>       mesa_data_dir = '../../../data' ! for eos and opacity tables
>>       log_columns_file = 'log_columns.list'
>>
>>       load_saved_model=.true.
>>       saved_model_name='../low_z/0p9-z0001.dat'
>>
>>       pgstar_flag = .true.
>>
>>
>> I place the donor at a very large orbital separation (something like 10^10
>> days)
>> to "simulate" a single star evolution before doing the real
>> binary evolution later.
>> However, the evolution is weird, the main sequence lasts for ~7.5 Gyr
>> (instead of the expected 12 Gyr)
>> and the evolution is very quick with the star becoming fully radiative
>> at some point...
>>
>> Any idea what did I do wrong ??
>>
>> Many thanks, I really appreciate your support !
>>
>> Ale
>>
>>
>> ------------------------------------------------------------------------------
>> Achieve Improved Network Security with IP and DNS Reputation.
>> Defend against bad network traffic, including botnets, malware,
>> phishing sites, and compromised hosts - saving your company time,
>> money, and embarrassment.   Learn More!
>> http://p.sf.net/sfu/hpdev2dev-nov
>> _______________________________________________
>> mesa-users mailing list
>> mes...@li...
>> https://lists.sourceforge.net/lists/listinfo/mesa-users
>>
>>
>

Re: mesa-users] Problem creating low Z stars and ZAMS models

[Aaron D. <aar...@gm...>]

Dear Ale,

If you want a model with a main sequence lifetime of ~12 Gyr for Z=10^-4, I
recommend choosing M ~ 0.8 Msun. For 0.9 Msun, 7-8 Gyr is perfectly
reasonable.

If  you look at the MESA paper, we have an example of 0.8 Msun, Z=10^-4 from
four different codes and they all have MS lifetimes of ~12 Gyr (see figure
19).

Best wishes,
Aaron



On Tue, Nov 2, 2010 at 6:35 PM, Alessandro Patruno <ale...@gm...>wrote:

> Hi everyone,
>
> I was playing a bit with the test_suite
> "low_z" and "create_zams" but I found two problems
> I can't solve easily
>
> 1. How do I tell MESA to use a ZAMS model file that I created with
> "create_zams" instead of the default ones ? I just created a Z=0.0001
> ZAMS sequence (for Population II stars) and I'd like to use it now to load
> initial stellar models...
>
>
> 2. I am creating a single star, a main sequence star of 0.9 Msun,
> with Z=0.0001. So I use "low_z" in the test_suite.
> My "inlist_low_z" has the lines:
>
> &star_job
>       mesa_data_dir = '../../../data' ! for eos and opacity tables
>       create_pre_main_sequence_model = .true.
>       save_model_number=635
>       save_model_filename='0p9-z0001.dat'
>
>
> I start with a pre-main sequence model
> and then let the evolution go until the code tells
> me "starting main sequence". This happens at the 635-th time step
> (that's why I wrote save_model_number=635).
> I save the model in the file (0p9-z0001.dat), and I load it in the
> test_suite called "rlo" to do binary evolution.
>
> The inlist_test_rlo file has these lines n the &star_job section:
>
> &star_job
>
>       mesa_data_dir = '../../../data' ! for eos and opacity tables
>       log_columns_file = 'log_columns.list'
>
>       load_saved_model=.true.
>       saved_model_name='../low_z/0p9-z0001.dat'
>
>       pgstar_flag = .true.
>
>
> I place the donor at a very large orbital separation (something like 10^10
> days)
> to "simulate" a single star evolution before doing the real
> binary evolution later.
> However, the evolution is weird, the main sequence lasts for ~7.5 Gyr
> (instead of the expected 12 Gyr)
> and the evolution is very quick with the star becoming fully radiative
> at some point...
>
> Any idea what did I do wrong ??
>
> Many thanks, I really appreciate your support !
>
> Ale
>
>
> ------------------------------------------------------------------------------
> Achieve Improved Network Security with IP and DNS Reputation.
> Defend against bad network traffic, including botnets, malware,
> phishing sites, and compromised hosts - saving your company time,
> money, and embarrassment.   Learn More!
> http://p.sf.net/sfu/hpdev2dev-nov
> _______________________________________________
> mesa-users mailing list
> mes...@li...
> https://lists.sourceforge.net/lists/listinfo/mesa-users
>
>

Re: mesa-users] Problem creating low Z stars and ZAMS models

[Bill P. <pa...@ki...>]

Hi Ale,

On Nov 2, 2010, at 4:35 PM, Alessandro Patruno wrote:

> Hi everyone, 
> 
> I was playing a bit with the test_suite
> "low_z" and "create_zams" but I found two problems
> I can't solve easily 
> 
> 1. How do I tell MESA to use a ZAMS model file that I created with
> "create_zams" instead of the default ones ? I just created a Z=0.0001
> ZAMS sequence (for Population II stars) and I'd like to use it now to load 
> initial stellar models...


The control you want is called 'zams_filename' which is set by default to 'zams_z2m2.data'.
The code tries to open the zams file first in the current directory and, if that fails, next
in mesa/data/star_data/zams_models.


> 
> 
> 2. I am creating a single star, a main sequence star of 0.9 Msun, 
> with Z=0.0001. So I use "low_z" in the test_suite. 
> My "inlist_low_z" has the lines:
> 
> &star_job
>       mesa_data_dir = '../../../data' ! for eos and opacity tables
>       create_pre_main_sequence_model = .true.
>       save_model_number=635'
>       save_model_filename='0p9-z0001.dat'
> 
> 
> I start with a pre-main sequence model 
> and then let the evolution go until the code tells
> me "starting main sequence". This happens at the 635-th time step
> (that's why I wrote save_model_number=635). 
> I save the model in the file (0p9-z0001.dat), and I load it in the 
> test_suite called "rlo" to do binary evolution.
> 
> The inlist_test_rlo file has these lines n the &star_job section:
> 
> &star_job
> 
>       mesa_data_dir = '../../../data' ! for eos and opacity tables
>       log_columns_file = 'log_columns.list' 
>       
>       load_saved_model=.true.
>       saved_model_name='../low_z/0p9-z0001.dat'
>             
>       pgstar_flag = .true.
> 
> 
> I place the donor at a very large orbital separation (something like 10^10 days)
> to "simulate" a single star evolution before doing the real
> binary evolution later. 
> However, the evolution is weird, the main sequence lasts for ~7.5 Gyr
> (instead of the expected 12 Gyr)
> and the evolution is very quick with the star becoming fully radiative
> at some point...
> 
> Any idea what did I do wrong ??

Please send the saved model and the inlists so I can try to recreate the problem.

BTW: does the saved model evolve reasonably if you run it outside of the rlo setup?

> 
> Many thanks, I really appreciate your support !

You are very welcome!

Cheers,
Bill

mesa-users] Problem creating low Z stars and ZAMS models

[Alessandro P. <ale...@gm...>]

Hi everyone,

I was playing a bit with the test_suite
"low_z" and "create_zams" but I found two problems
I can't solve easily

1. How do I tell MESA to use a ZAMS model file that I created with
"create_zams" instead of the default ones ? I just created a Z=0.0001
ZAMS sequence (for Population II stars) and I'd like to use it now to load
initial stellar models...


2. I am creating a single star, a main sequence star of 0.9 Msun,
with Z=0.0001. So I use "low_z" in the test_suite.
My "inlist_low_z" has the lines:

&star_job
      mesa_data_dir = '../../../data' ! for eos and opacity tables
      create_pre_main_sequence_model = .true.
      save_model_number=635
      save_model_filename='0p9-z0001.dat'


I start with a pre-main sequence model
and then let the evolution go until the code tells
me "starting main sequence". This happens at the 635-th time step
(that's why I wrote save_model_number=635).
I save the model in the file (0p9-z0001.dat), and I load it in the
test_suite called "rlo" to do binary evolution.

The inlist_test_rlo file has these lines n the &star_job section:

&star_job

      mesa_data_dir = '../../../data' ! for eos and opacity tables
      log_columns_file = 'log_columns.list'

      load_saved_model=.true.
      saved_model_name='../low_z/0p9-z0001.dat'

      pgstar_flag = .true.


I place the donor at a very large orbital separation (something like 10^10
days)
to "simulate" a single star evolution before doing the real
binary evolution later.
However, the evolution is weird, the main sequence lasts for ~7.5 Gyr
(instead of the expected 12 Gyr)
and the evolution is very quick with the star becoming fully radiative
at some point...

Any idea what did I do wrong ??

Many thanks, I really appreciate your support !

Ale

Re: mesa-users] Hydro convergence failure at end of main sequence.

[Bill P. <pa...@ki...>]

On Nov 2, 2010, at 6:25 AM, Sam Jones wrote:

> I am using MESA version 2664 (compiled with ifortran 11.1) on Ubuntu 10.04 to run a 20Mo model up to collapse, but at the end of the main sequence I get an error "hydro_failed_to_converge". I have tried this with two different timestep parameters and attach the inlists for both runs - maybe these values for varcontrol are inappropriate?

Hi Sam,

From the inlists you sent, I see that you've tried changing the following controls:

      varcontrol_h1 = 100.
      varcontrol_he4 = 100.
      varcontrol_c12 = 100.
      varcontrol_o16 = 100.

Let me clarify the situation with those parameters a bit.   First, in recent versions, I've moved varcontrol_h1 and it's friends from public/star_defaults.dek  to private/private_defaults.dek just to avoid the problem you have had!  Those parameters (and several others) are leftovers from various experiments I've done, some of which worked and some of which didn't.   So I'd suggest updating to the current mesa and limiting yourself to controls listed in star/public.  My apologies for not cleaning things up sooner.

Second, as the comments in the file explain, the role of those parameters is to include certain abundances in the decision for the default timestep.   However in my experience, it has worked better to keep the default varcontrol simple and add the abundance limits as a "special" test that applies to reduce the default timestep (that's why I've moved those controls to private; next step will be to delete them).   There are a ton of special limits, and I think the ones you want are there in star_defaults: seach for the string "limits based on max decrease in mass fraction at any location in star" and check things you find.  In particular, you may want to set dX_limit and dX_limit_min_X (and also dH_limit, dHe_limit, etc.).   Take a look at star/test_suite/15M_si_burn/inlist_15_z2m2 for an example.

As to why those settings caused a failure to converge, I cannot guess.  But of course there is NO way that mesa will be able to survive all variations on parameter settings, and failure to converge is its way of dying.   Rather than spend time on this particular case, please give your 20M case another try using the controls I've mentioned above.   I think you might want to adopt the strategy of starting from the inlist from the test_suite and making small changes from that to see what happens. 

Cheers,
Bill

Re: mesa-users] Hydro convergence failure at end of main sequence.

[Kent B. <kg...@la...>]

On Tue, 2010-11-02 at 09:06 -0500, Aaron Dotter wrote:

> It's putting too many zones in around the edge of the core and that's
> causing artificial mixing--so the main sequence never ends.

I find this a bit disturbing. My understanding is that mesa uses
diffusive mix. This should converge as the mesh is refined. What is the
reason for this artificial mixing?

--Kent G. Budge

Re: mesa-users] Hydro convergence failure at end of main sequence.

[Aaron D. <aar...@gm...>]

Hi Sam,

I am using MESA version 2664 (compiled with ifortran 11.1) on Ubuntu 10.04
> to run a 20Mo model up to collapse, but at the end of the main sequence I
> get an error "hydro_failed_to_converge". I have tried this with two
> different timestep parameters and attach the inlists for both runs - maybe
> these values for varcontrol are inappropriate?
>

I expect that the setting you're imposing on the composition variables is
too tight.  I tried the run in your inlist with all set to 10 and it did
indeed fail after about 2400 models.  It's putting too many zones in around
the edge of the core and that's causing artificial mixing--so the main
sequence never ends.

I commented out the varcontrol_* lines (so I just use the default values)
and it runs through to the end of the main sequence with no problem.  Not
sure how far it will go after that!  The default values are reasonably well
tuned, which isn't to say that they will always work for any kind of
problem, but they should be good for H and He burning at most masses 0.1 <
Msun < 100 (?).


> As you can see from the inlists, I am also using the Dutch RGB and AGB wind
> scheme but there is no mass loss on the main sequence - is there a parameter
> for this?
>

As with most wind formulas, the "Dutch" version has an adjustable parameter
that is zero by default (no mass loss).  To set it, you need to include the
following, with your value instead of zero:

      RGB_wind_scheme = 'Dutch'
      Dutch_wind_eta = 0d0

Inlist_standard has all the names of all the etas that correspond to the
different wind schemes.

One last note, I see that you are doing set_uniform_initial_composition in
star_job and initial_z in controls.  It's not necessary to do both.  In
fact, MESA should warn you if you do because you could input conflicting
values.  set_uniform_initial_composition will set all the composition
variables you need in a given run.

Best wishes,
Aaron

mesa-users] Hydro convergence failure at end of main sequence.

[Sam J. <s.w...@ep...>]

# this is the inlist used to create star100.log, which failed to converge at the end of the main sequence.

&star_job

      create_pre_main_sequence_model = .true.
      set_uniform_initial_composition = .true. 

      initial_h1 = 7.199860320000000E-01
      initial_h2 = 1.396800000000000E-05
      initial_he3 = 4.414802000000001E-05
      initial_he4 = 2.659558519800000E-01
      initial_zfracs = 5

/end of star_job namelist


&controls

      initial_mass =  20
      initial_z = 0.014d0
         
      RGB_wind_scheme = 'Dutch'
      AGB_wind_scheme = 'Dutch'

      varcontrol_h1 = 100.
      varcontrol_he4 = 100.
      varcontrol_c12 = 100.
      varcontrol_o16 = 100.

/end of controls namelist

Re: mesa-users] Problem when installing MESA with pgstar

[Alessandro P. <ale...@gm...>]

It works and the interface looks superb, thanks a lot !

For the records: I am not sure anymore I was using the latest gfortran...
I found out that when using the Ubuntu command:
" sudo apt-get install gfortran "
the version installed is still the 4.4.

Probably this was the reason of the wrong compiling, now I'll try with
gfortran 4.5 or 4.6 and see whether
it works without changing the star_lib.f  file.

So: Ubuntu users beware of this problem !
Thanks again to Bill !

Cheers,

Ale




On Sun, Oct 31, 2010 at 1:57 AM, Bill Paxton <pa...@ki...> wrote:

> Hi Ale,
>
> Please try a quick patch and let me know if it fixes the problem.
> In mesa/star/public/star_lib.f, in the read_pgstar_inlist routine,
> please replace
>
>        use mod_pgstar
>
> by
>
>         use mod_pgstar, only: do_read_pgstar_controls
>
> There is in fact another routine named read_pgstar_inlist in different
> module, and the version of gfortran you are using is perhaps
> complaining about it although the other gfortran's don't seem to care.
>
> Thanks.
> Bill
>
>
>
> On Oct 30, 2010, at 4:46 PM, Alessandro Patruno wrote:
>
> > Hi everyone,
> >
> > I've tried to install MESA on Ubuntu 9.10 (64 bit) with the pgstar option
> switched off and everything seem to work
> > perfectly (btw, great job, I'm really amazed at what you did !).
> >
> > I then wanted to try pgstar, so I switched on the pgstar option in
>  ~/mesa/utils/makefile_header
> > (I'm using gfortran, latest version, on Ubuntu 9.10):
> >
> > USE_PGSTAR = YES
> > LOAD_PGPLOT = -L/usr/local/pgplot/ -lpgplot  -lX11 -lxcb -lXau -lXdmcp
> -lXext -lpng -lz
> >
> > Then I went to the main MESA dir (~/mesa) and I typed: "./clean" and then
> again "./install".
> > However, this time the code won't compile and at some point it gives the
> error message:
> >
> >
> **************************************************************************************************************
> > /home/apatruno/mesa/star
> > building star package.
> >
> > gfortran -fno-range-check  -fopenmp  -I../public -I../private
> -I../../include -Wunused-value -Werror -W -fimplicit-none   -O2 -c
> -ffree-form ../public/star_lib.f
> > ../public/star_lib.f:1419.39:
> >
> >       end subroutine read_pgstar_inlist
> >                                        1
> > Error: Name 'read_pgstar_inlist' at (1) is an ambiguous reference to
> 'read_pgstar_inlist' from current program unit
> > make: *** [star_lib.o] Error 1
> >
> > /home/apatruno/mesa/star/make
> > FAILED
> >
> *************************************************************************************************************
> >
> >
> > I'll keep trying to see whether I find a solution. In the meanwhile...do
> you have any suggestion on
> > how to solve this problem ?
> >
> > Many thanks !
> >
> > Cheers,
> >
> > Ale
> >
> >
> ------------------------------------------------------------------------------
> > Nokia and AT&T present the 2010 Calling All Innovators-North America
> contest
> > Create new apps & games for the Nokia N8 for consumers in  U.S. and
> Canada
> > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in
> marketing
> > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
> >
> http://p.sf.net/sfu/nokia-dev2dev_______________________________________________
> > mesa-users mailing list
> > mes...@li...
> > https://lists.sourceforge.net/lists/listinfo/mesa-users
>
>

Re: mesa-users] Problem when installing MESA with pgstar

[Bill P. <pa...@ki...>]

Hi Ale,

Please try a quick patch and let me know if it fixes the problem.
In mesa/star/public/star_lib.f, in the read_pgstar_inlist routine,
please replace

	use mod_pgstar

by

         use mod_pgstar, only: do_read_pgstar_controls

There is in fact another routine named read_pgstar_inlist in different
module, and the version of gfortran you are using is perhaps 
complaining about it although the other gfortran's don't seem to care.

Thanks.
Bill



On Oct 30, 2010, at 4:46 PM, Alessandro Patruno wrote:

> Hi everyone, 
> 
> I've tried to install MESA on Ubuntu 9.10 (64 bit) with the pgstar option switched off and everything seem to work
> perfectly (btw, great job, I'm really amazed at what you did !). 
> 
> I then wanted to try pgstar, so I switched on the pgstar option in  ~/mesa/utils/makefile_header  
> (I'm using gfortran, latest version, on Ubuntu 9.10):
> 
> USE_PGSTAR = YES
> LOAD_PGPLOT = -L/usr/local/pgplot/ -lpgplot  -lX11 -lxcb -lXau -lXdmcp -lXext -lpng -lz
> 
> Then I went to the main MESA dir (~/mesa) and I typed: "./clean" and then again "./install". 
> However, this time the code won't compile and at some point it gives the error message:
> 
> **************************************************************************************************************
> /home/apatruno/mesa/star
> building star package.
> 
> gfortran -fno-range-check  -fopenmp  -I../public -I../private -I../../include -Wunused-value -Werror -W -fimplicit-none   -O2 -c -ffree-form ../public/star_lib.f
> ../public/star_lib.f:1419.39:
> 
>       end subroutine read_pgstar_inlist
>                                        1
> Error: Name 'read_pgstar_inlist' at (1) is an ambiguous reference to 'read_pgstar_inlist' from current program unit
> make: *** [star_lib.o] Error 1
> 
> /home/apatruno/mesa/star/make
> FAILED
> *************************************************************************************************************
> 
> 
> I'll keep trying to see whether I find a solution. In the meanwhile...do you have any suggestion on 
> how to solve this problem ? 
> 
> Many thanks !
> 
> Cheers,
> 
> Ale
> 
> ------------------------------------------------------------------------------
> Nokia and AT&T present the 2010 Calling All Innovators-North America contest
> Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store 
> http://p.sf.net/sfu/nokia-dev2dev_______________________________________________
> mesa-users mailing list
> mes...@li...
> https://lists.sourceforge.net/lists/listinfo/mesa-users

mesa-users] Problem when installing MESA with pgstar

[Alessandro P. <ale...@gm...>]

Hi everyone,

I've tried to install MESA on Ubuntu 9.10 (64 bit) with the pgstar option
switched off and everything seem to work
perfectly (btw, great job, I'm really amazed at what you did !).

I then wanted to try pgstar, so I switched on the pgstar option in
~/mesa/utils/makefile_header
(I'm using gfortran, latest version, on Ubuntu 9.10):

USE_PGSTAR = YES
LOAD_PGPLOT = -L/usr/local/pgplot/ -lpgplot  -lX11 -lxcb -lXau -lXdmcp
-lXext -lpng -lz

Then I went to the main MESA dir (~/mesa) and I typed: "./clean" and then
again "./install".
However, this time the code won't compile and at some point it gives the
error message:

**************************************************************************************************************
/home/apatruno/mesa/star
building star package.

gfortran -fno-range-check  -fopenmp  -I../public -I../private
-I../../include -Wunused-value -Werror -W -fimplicit-none   -O2 -c
-ffree-form ../public/star_lib.f
../public/star_lib.f:1419.39:

      end subroutine read_pgstar_inlist
                                       1
Error: Name 'read_pgstar_inlist' at (1) is an ambiguous reference to
'read_pgstar_inlist' from current program unit
make: *** [star_lib.o] Error 1

/home/apatruno/mesa/star/make
FAILED
*************************************************************************************************************


I'll keep trying to see whether I find a solution. In the meanwhile...do you
have any suggestion on
how to solve this problem ?

Many thanks !

Cheers,

Ale