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

mesa-users] log_columns.list does not work

[jingluan <jin...@ca...>]

Hello :-)

I uncomment this line in inlist_project:  log_columns_file = 
'log_columns.list' .

but I get this err information:

create pre-main-sequence model
  done build_pre_ms_model
  read log_columns.list
  failed to recognize item for log columns logT
  star_set_log_columns ierr          -1


Thank you :-)

Sincerely
Jing

mesa-users] cannot save star.log

[jingluan <jin...@ca...>]

Hello,

I run a star example, at the terminal it says 'All this and m
re are saved in 'LOGS/star.log' during the run.', but after the run, 
there is nothing in the directory LOGS.

Anyone ever came across such situation please?

Thank you :-)

Sincerely
Jing

mesa-users] what does this mean?

[jingluan <jin...@ca...>]

Hello :-)

What does this mean please ?

star_create_pre_ms_model ierr          -1

Thank you :-)

Sincerely
Jing

mesa-users] ifort 11.1 + Xcode 3.2.2 = trouble

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

Hi,

This is a heads-up for Mac users.   The current ifort is not compatible with the current Xcode!

If like me you find yourself with Xcode 3.2.2, you'll need to replace it by installing the old 3.2.1 version.

You can get that from Apple.    Here's the relevant link that I got from Intel support.


> If you have already upgraded your Xcode to version 3.2.2, we already found a known issue with Intel compiler. More detail is posted on anther Knownleage base article: http://software.intel.com/en-us/articles/intel-fortran-for-mac-os-x-incompatible-with-xcode-322/


-Bill

Re: mesa-users] pgplot

[Ehsan M. <mor...@ia...>]

Dear Jing,
Hi.
I recently managed to implement PGPLOT into my Ubuntu, and learned to do a
modification to have the xwindow appear.
Please, open the file ~/.xinitrc.template and at the end of the file add
the line:
exec PGPLOT
Then give it another try, and see if it works.
Best.

On Wed, June 2, 2010 10:47 am, jingluan wrote:
> Hello:
>
> We have pgplot installed onto my Ubuntu, but when I ran a star model,
> the pgplot window does not come out.....anything wrong?
>
> Thank you :-)
>
> Jing
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> mesa-users mailing list
> mes...@li...
> https://lists.sourceforge.net/lists/listinfo/mesa-users
>


-- 
Moravveji, Ehsan.
Ph.D student of Astrophysics.
Department of Physics, Institute for Advanced Studies in Basic Sciences
(IASBS), GavaZang Road,
Zanjan 45137-66731, Iran.

Office: (+98)241-415 2212
Fax:    (+98)241-415 2104
http://iasbs.ac.ir/students/moravveji

Re: mesa-users] pgplot

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

On Jun 1, 2010, at 11:17 PM, jingluan wrote:

> We have pgplot installed onto my Ubuntu, but when I ran a star model, 
> the pgplot window does not come out.....anything wrong?

Hi,

First thing to do is to make sure you can run PGPLOT by itself without mesa.
Once you have that working, let us know if you still have problems using
it with mesa. 

Thanks,
Bill

mesa-users] pgplot

[jingluan <jin...@ca...>]

Hello:

We have pgplot installed onto my Ubuntu, but when I ran a star model, 
the pgplot window does not come out.....anything wrong?

Thank you :-)

Jing

Re: mesa-users] a question about MESA

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

Hi,

I'm glad you are using MESA.  

It looks like you've run into a problem with the namelist reader
in the gfortran runtime.   It is reporting "end of file" because it
has failed to read the final '/' that terminates the namelist.
And that is because the last line of the inlist_zams_specification
doesn't end in in return.   I'll fix that for the next release,
but for now you should just add a blank line to the end of the
inlist file and try again.   Let us know how it works!

BTW: making a zams file is a big job and probably only
worth the effort if you are going to run a very large number
of cases.   For most applications it is much easier just to
create a single model using create_pre_main_sequence_model.
When you do that, you can specify arbitrary composition and
mass.   You might want to try that too.


--Bill Paxton



> I have a question about how to make zams data under Z=0.01.
> I couldn't find zams data about Z=0.01 in
> mesa/data/star_data/starting_models directory, so I decided to make it.
> I added inlist , inlist_create_zams and inlist_zams_specification to my
> working directory, and changed inlist files like inlist files in
> mesa/star/test_suite/create_zams directory.
> I ran './rn ', but the following error was displayed;
> 
> *********************************************************************************
> Revision: 2341
> Tue May 25 20:54:02 JST 2010
> read extra star_job inlist1 from inlist_create_zams
> loading eos data
> loading kap data
> finished loading
> read extra controls inlist1 from inlist_create_zams
> 
> 
> The terminal output contains the following information
> 
> 'step' is the number of steps since the start of the run,
> 'lg_dt_yr' is log10 timestep in years,
> 'age_yr' is the simulated years since the start run,
> 'lg_Tcntr' is log10 center temperature (K),
> 'lg_Dcntr' is log10 center density (g/cm^3),
> 'lg_Pcntr' is log10 center pressure (ergs/cm^3),
> 'lg_Teff' is log10 surface temperature (K),
> 'lg_R' is log10 surface radius (Rsun),
> 'lg_L' is log10 surface luminosity (Lsun),
> 'lg_LH' is log10 total PP and CNO hydrogen burning power (Lsun),
> 'lg_L3a' is log10 total triple-alpha helium burning power (Lsun),
> 'lg_LZ' is log10 total burning power excluding LH and L3a and
> photodisintegrations (Lsun),
> 'lg_LNuc' is log10 nuclear power excluding photodisintegration (Lsun),
> 'lg_LNeu' is log10 total neutrino power (Lsun),
> 'lg_Psurf' is log10 surface pressure (gas + radiation),
> 'Mass' is the total stellar mass (Msun),
> 'lg_Mdot' is log10 magnitude of rate of change of mass (Msun/year),
> 'lg_Dsurf' is log10 surface density (g/cm^3),
> 'H_rich' is the remaining mass outside of the hydrogen poor core,
> 'H_poor' is the core mass where hydrogen abundance is <= 0.10E-03
> 'He_poor' is the core mass where helium abundance is <= 0.10E-03
> 'H_cntr' is the center H1 mass fraction,
> 'He_cntr' is the center He4 mass fraction,
> 'C_cntr' is the center C12 mass fraction,
> 'N_cntr' is the center N14 mass fraction,
> 'O_cntr' is the center O16 mass fraction,
> 'Ne_cntr' is the center Ne20 mass fraction,
> 'X_avg' is the star average hydrogen mass fraction,
> 'Y_avg' is the star average helium mass fraction,
> 'Z_avg' is the star average metallicity,
> 'gam_cntr' is the center plasma interaction parameter,
> 'eta_cntr' is the center electron degeneracy parameter,
> 'pts' is the number of grid points in the current model,
> 'jacs' is the number of jacobians created in the current step,
> 'retry' is the number of step retries required during the run,
> 'bckup' is the number of step backups required during the run,
> 'dt_limit' is an indication of what limited the timestep.
> 
> All this and more are saved in 'LOGS/star.log' during the run.
> 
> Failed while trying to read control namelist file inlist_zams_specification
> The following runtime error message might help you find the problem
> 
> At line 368 of file ../../../star/test/src/create_zams.f (unit = 9, file
> = 'inlist_zams_specification')
> Fortran runtime error: End of file
> Tue May 25 20:54:06 JST 2010
> *********************************************************************************
> 
> I would like to know what I should do. whould you let me know the reason ?

Re: mesa-users] Extending a previous run

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

Hi Michelle,

In a situation like this it is most helpful to supply the inlist you're
using and also, if possible, a saved model (not a photo) from just before
the problem occurs.

Aaron



On Sun, May 23, 2010 at 4:56 PM, Michelle Dolan <ve...@gm...> wrote:

> I've got it working.  But now I'm having trouble getting MESA to do an
> extended run with Reimer's mass loss.  It ran until ending because there
> were too many backups.  I can restart it from the last dumped photo which
> runs until ending without dumping a photo with this message:
>
> stopping because of too many backups in a row          16
> terminated evolution because nonzero_ierr
>
> Any tips?
>
> ~MDolan
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> mesa-users mailing list
> mes...@li...
> https://lists.sourceforge.net/lists/listinfo/mesa-users
>
>

Re: mesa-users] Extending a previous run

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

Hi,

I'm glad you've got mesa installed.   Now we just need to make it work for you!

To do that we'll need more info.    (We clearly need some guidelines on the website for submitting problems!)

include whatever we'll need to reproduce the problem.  
Ideally, this means saving a model from a few steps before the roof caves in.
	not a photo -- those are binary format specific to particular systems
	this needs to be a model created by setting save_model_number and save_model_filename in your inlist.
Rerun starting from the saved model (using load_saved_model in your inlist) to make sure the problem is reproducible.

Then attach the inlist and the saved model to your email along with a description of the problem.
A copy of the terminal output showing the error can be useful too.

Thanks,
Bill





On May 23, 2010, at 4:56 PM, Michelle Dolan wrote:

> I've got it working.  But now I'm having trouble getting MESA to do an extended run with Reimer's mass loss.  It ran until ending because there were too many backups.  I can restart it from the last dumped photo which runs until ending without dumping a photo with this message:
> 
> stopping because of too many backups in a row          16
> terminated evolution because nonzero_ierr
> 
> Any tips?
> 
> ~MDolan
> ------------------------------------------------------------------------------
> 
> _______________________________________________
> mesa-users mailing list
> mes...@li...
> https://lists.sourceforge.net/lists/listinfo/mesa-users

mesa-users] Extending a previous run

[Michelle D. <ve...@gm...>]

I've got it working.  But now I'm having trouble getting MESA to do an
extended run with Reimer's mass loss.  It ran until ending because there
were too many backups.  I can restart it from the last dumped photo which
runs until ending without dumping a photo with this message:

stopping because of too many backups in a row          16
terminated evolution because nonzero_ierr

Any tips?

~MDolan

Re: mesa-users] MESA Installation trouble on Ubuntu 10.04 with gfortran 4.4

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

Hello,


On May 18, 2010, at 4:07 PM, Raziman T V wrote:

>         procedure (), pointer, nopass :: evolve => null()
>                  1
> Error: Fortran 2003: Procedure components at (1) are not yet implemented in gfortran


Please get the up-to-date, current gfortran and try again.
Procedure pointers are a Fortran 2003 feature that has recently been added to gfortran and ifort.
Since they are now supported by the current versions of both compilers that we use for mesa,
I want to start using them where they'll make a difference.   They are a big help in mesa/star
for allowing user defined "add-ons" for things like winds, mixing, etc.

Let us know how it goes!

Thanks,
Bill Paxton

mesa-users] MESA Installation trouble on Ubuntu 10.04 with gfortran 4.4

[Raziman T V <raz...@gm...>]

Hi,

I run a 64 bit Ubuntu 10.04 (Lucid Lynx) machine and tried to install MESA
today with gfortran 4.4.3. I got the latest version of MESA from SVN and
tried making the numerics only module. That was successful. But when I tried
doing the full install, some packages could be made but the installation
failed during the build of star package with the following error:

****************************************

/home/razimantv/Projects/MESA/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_def.f
star_data.dek:849.18:
   Included at ../public/star_def.f:96:

        procedure (), pointer, nopass :: evolve => null()
                 1
Error: Fortran 2003: Procedure components at (1) are not yet implemented in
gfortran
star_data.dek:850.18:
   Included at ../public/star_def.f:96:

        procedure (), pointer, nopass :: other_wind => null()
                 1
Error: Fortran 2003: Procedure components at (1) are not yet implemented in
gfortran
star_data.dek:851.18:
   Included at ../public/star_def.f:96:

        procedure (), pointer, nopass :: other_mixing => null()
                 1
Error: Fortran 2003: Procedure components at (1) are not yet implemented in
gfortran
make: *** [star_def.o] Error 1

/home/razimantv/Projects/MESA/mesa/star/make
FAILED

****************************************

Could you please tell me how to get over this error? I am not able to get
even the numerics only module working with ifort or the latest gfortran
version due to some library location issues. Hence it will be great if a way
could be found to get MESA working on my system with gfortran 4.4.3

Yours
Raziman T V

Re: mesa-users] A question on installing mesa

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

Hi Jing

If you continue to have problems, please provide us with information about
the system (OS and CPU type) you are trying to install MESA on and the
compiler version (e.g. gfortran --verison).  We know that gfortran 4.3 and
earlier have problems with MESA.  gfortran 4.4 and 4.5 are OK as far as we
know.

If at all possible, we would suggest that you install ifort and compile MESA
with it.  ifort produces binaries that are much faster and generally
supports the MESA code much better than gfortran.  ifort is not free but
intel does offer a free 30-day trial so that you can try it out and decide
if it is worth the money.

Aaron

Re: mesa-users] problem in installing mesa

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

Hi Jing,

I can suggest one thing -- try getting the most recent
release of gfortran.   You can get binaries here:

http://gcc.gnu.org/wiki/GFortranBinaries

Good luck!

-Bill






On May 9, 2010, at 9:34 AM, Jing Luan wrote:

> Hello :-)
>
> I am a new user of mesa, I downloaded mesa and edited the file  
> makefile_header already. I use gfortran.
>
> I tried to install mesa and failed. This is how I did it: I go to  
> the mesa direction, type './install' (without quotes) into the  
> terminal, click the return button on the keyboard; The below is what  
> I got in the terminal window:
>
> checking if ndiff is installed ...
> ./install_num_only: line 50: utils/ndiff/bin/ndiff: No such file or  
> directory
> no! running install_ndiff
> ndiff installed in utils/ndiff/
>
> /Users/jingluan/mesa/const
> building const package.
>
> gfortran -fno-range-check  -fopenmp  -I../public -I../private - 
> I../../include -Wunused-value -Werror -W -fimplicit-none   -O2 -c - 
> ffixed-form -ffixed-line-length-132 ../public/const_def.f
> gfortran -fno-range-check  -fopenmp  -I../public -I../private - 
> I../../include -Wunused-value -Werror -W -fimplicit-none   -O2 -c - 
> ffixed-form -ffixed-line-length-132 ../public/const_lib.f
> ar crs libconst.a const_def.o const_lib.o
> gfortran -fno-range-check  -fopenmp -I../../make -I../../public - 
> I../../../include -fbounds-check -g -c -ffixed-form -ffixed-line- 
> length-132 ../src/test_const.f
> gfortran -fopenmp -o ../tester test_const.o -L../../make -lconst
> /usr/bin/ld: warning unknown -macosx_version_min parameter value:  
> 10.5.8 ignored (using 10.4)
> /usr/bin/ld: /usr/lib/libSystem.dylib unknown flags (type) of  
> section 6 (__TEXT,__literal16) in load command 0
> /usr/bin/ld: /usr/lib/libSystem.B.dylib unknown flags (type) of  
> section 6 (__TEXT,__literal16) in load command 0
> collect2: ld returned 1 exit status
> make: *** [tester] Error 1
>
> /Users/jingluan/mesa/const/test/make
> FAILED
>
>
>
> Would you tell me what to do with it? Any help is highly appreciated !
>
> Thanks a lot :-)
>
> Sincerely
> Jing

mesa-users] A question on installing mesa

[Jing L. <jin...@ca...>]

Hello :-)

I am a new user of mesa, I downloaded mesa and edited the file 
makefile_header already. I use gfortran.

I tried to install mesa and failed. This is how I did it: I go to the 
mesa direction, type './install' (without quotes) into the terminal, 
click the return button on the keyboard; The below is what I got in the 
terminal window:

checking if ndiff is installed ...
./install_num_only: line 50: utils/ndiff/bin/ndiff: No such file or 
directory
no! running install_ndiff
ndiff installed in utils/ndiff/

/Users/jingluan/mesa/const
building const package.

gfortran -fno-range-check  -fopenmp  -I../public -I../private 
-I../../include -Wunused-value -Werror -W -fimplicit-none   -O2 -c 
-ffixed-form -ffixed-line-length-132 ../public/const_def.f
gfortran -fno-range-check  -fopenmp  -I../public -I../private 
-I../../include -Wunused-value -Werror -W -fimplicit-none   -O2 -c 
-ffixed-form -ffixed-line-length-132 ../public/const_lib.f
ar crs libconst.a const_def.o const_lib.o
gfortran -fno-range-check  -fopenmp -I../../make -I../../public 
-I../../../include -fbounds-check -g -c -ffixed-form 
-ffixed-line-length-132 ../src/test_const.f
gfortran -fopenmp -o ../tester test_const.o -L../../make -lconst
/usr/bin/ld: warning unknown -macosx_version_min parameter value: 10.5.8 
ignored (using 10.4)
/usr/bin/ld: /usr/lib/libSystem.dylib unknown flags (type) of section 6 
(__TEXT,__literal16) in load command 0
/usr/bin/ld: /usr/lib/libSystem.B.dylib unknown flags (type) of section 
6 (__TEXT,__literal16) in load command 0
collect2: ld returned 1 exit status
make: *** [tester] Error 1

/Users/jingluan/mesa/const/test/make
FAILED



Would you tell me what to do with it? Any help is highly appreciated !

Thanks a lot :-)

Sincerely
Jing

mesa-users] big fix: 2258 replaces 2244; and improved eos tables

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

Hi,

Sorry for the inconvenience -- 2244 slipped through our test suite in  
spite of a nasty bug in mesa/star
concerning non-solar opacities.  It is fixed (and the test suite is  
updated!) -- so please update to 2258.

Note that 2258 also has a new set of eos data, so you'll need to  
remove data/eosDT_data before installing.
(If you forget, it will remind you.)   The new eos data is actually  
quite significant if you are doing models that
enter the low T, high P range where we use the SCVH EOS.   Thanks to  
Didier Saumon, we now have access
to an extended set of values that make our interpolation much more  
accurate.   The new values do NOT
extend the valid range of the EOS; they are "off-table" values that  
are only useful because they fill out the
rectangle of data needed in order to create good bicubic splines for  
interpolation.   It is ironic but true that
data outside of the range of validity of the eos is helpful with  
interpolating the data in the part of the (logT,logP)
space that we actually want to use.  So thanks again to Didier for  
sharing this with us.  In case you
are curious, here are the new tables we are using with values for the  
high P range;  again, understand
that the extra values are not to be used directly -- they are only  
present to help creating interpolating splines.

Re: mesa-users] log_columns.list file

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

Hi Marcin,

Good to hear from you.

On Mar 27, 2010, at 2:43 AM, Marcin @ astrophysics wrote:

> Hi,
>
> I'd like to put some additional columns into the star.log file.
>
> What parameters to add into log_columns.list file to log data like:
>
> - energy produced by a gravitational collapse,

L_grav has the integrated eps_grav.   but you are right, it isn't in  
log_columns.list

> - total energy production (I think lg_L is not it),

lg_L is the energy leaving as photons, not the energy being produced.
See below for how you can add whatever you want for total energy  
production.

> And also do burn_ne and burn_si stand for burning power of Ne and Si
> burning?

all of the nuclear reactions are assigned a category;  burn_ne and  
burn_si
and 2 of the categories.   to see which reactions are in those  
categories,
look at data/net_data/reactions_list.   Searching for 'burn_ne' shows
reactions such as ne20(a,g)mg24, ne20(a,p)na23,and others.

> Where to look for other parameters, if they do exist but are not
> mentioned in log_columns.list?

Happily, you can add columns yourself by editing run_star_extras.
Change the routine 'how_many_extra_log_columns' to return the
number of extra columns you want to add.  Then change the
routine 'data_for_extra_log_columns' to give the values.
There is a commented out example already there, so you can
use it as a start.

Good luck!

Cheers,
Bill

mesa-users] log_columns.list file

[Marcin @ a. <ast...@o2...>]

Hi,

I'd like to put some additional columns into the star.log file.

What parameters to add into log_columns.list file to log data like:

- energy produced by a gravitational collapse,
- total energy production (I think lg_L is not it),

And also do burn_ne and burn_si stand for burning power of Ne and Si 
burning?
Where to look for other parameters, if they do exist but are not 
mentioned in log_columns.list?

Thanks.

Marcin Mackiewicz

Re: mesa-users] How can I find the base of convective zone in MESA?

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

Hi Zahra,

If you want to know where the base of the surface convection zone is in the
output, you can look for conv_mx1_top, conv_mx1_bot, etc. in the log file.
See the file mesa/data/star_data/log_columns.list for more option.  In the
profiles, you can use conv_mixing_type where the different values are
defined in mesa/mlt/public/mlt_def.f.  If that doesn't answer your question,
please provide more information about what you want to do and we'll try
again.

Best wishes,
Aaron



On Thu, Mar 18, 2010 at 12:45 AM, zahra altaha motahar
<zam...@ya...>wrote:

> Hi,
> I am using the Mesa for study the stellar evolution of low mass stars.
> Actually, I have run the code for 1 solar mass and I need to find the base
> of convective zone and remove the results for larger radius.
> How can I do that ?
> I wanted to add my own code but it doesn't work.
> Thank you
> Zahra
>
>
> ------------------------------
>  New Email addresses available on Yahoo!
> <http://sg.rd.yahoo.com/aa/mail/domainchoice/mail/signature/*http://mail.promotions.yahoo.com/newdomains/aa/>
> Get the Email name you've always wanted on the new @ymail and @rocketmail.
> Hurry before someone else does!
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> mesa-users mailing list
> mes...@li...
> https://lists.sourceforge.net/lists/listinfo/mesa-users
>
>

mesa-users] How can I find the base of convective zone in MESA?

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

Hi, 
I am using the Mesa for study the stellar evolution of low mass stars. Actually, I have run the code for 1 solar mass and I need to find the base of convective zone and remove the results for larger radius. 
How can I do that ? 
I wanted to add my own code but it doesn't work.
Thank you 
Zahra




      Get your new Email address!
Grab the Email name you've always wanted before someone else does!
http://mail.promotions.yahoo.com/newdomains/aa/

Re: mesa-users] Regarding the MESA EOS

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

On Feb 22, 2010, at 7:53 AM, Ricky Olivier wrote:

> Ok, looks like this is going to be harder than I thought. I could  
> subtract off the effect of radiation to the various thermodynamic  
> variables. This should be ok in those parts of the Rho-T plane where  
> the radiation energy density and radiation pressure do not dominate.  
> In other parts of the Rho-T plane it will be dodgy to say the least.



Hi Ricky,

As you know, the MESA/EOS is a blend of SCVH/OPAL/HELM eos's.
HELM is for situations in which it is okay to assume complete  
ionization,
and HELM does provide separate results with/without radiation.
So one possible approach is to by-pass the standard routine and
call the mesa/public/eos_lib routine 'eos_get_helm_results'.
In mesa/public/eos_def you'll find a long list of integer parameter
definitions for the results from HELM.   There are separate items
for pressure ('p'), energy ('e'), and entropy ('s').   The partials are
wrt temperature ('d_t'), density ('d_d' ), zbar ('d_z'), and abar  
('d_a').
And there are 2nd partials, 'd_dt', etc.    The 'total' value is the
sum of the contributions from gas and radiation -- that what mesa/eos
reports of course.  But you will also find the separate terms for
gas and radiation -- e.g., ptot, pgas, prad, etc.

For derived quantities such as specific heats and gammas, you
will find both values based on totals and on for the gas alone:
e.g., h_cp for the total and h_cp_gas for the gas alone.

So for the regions where you are willing to assume complete ionization,
you can go straight to the HELM results and get what you want.

Perhaps that will help?

Let me know.

Cheers,
Bill

Re: mesa-users] Regarding the MESA EOS

[Ricky O. <ol...@sa...>]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
<br>
Ok, looks like this is going to be harder than I thought. I could
subtract off the effect of radiation to the various thermodynamic
variables. This should be ok in those parts of the
Rho-T plane where the radiation energy density and radiation pressure
do not dominate. In other parts of the Rho-T plane it will be dodgy to
say the least.<br>
<br>
One final question, so that I don't waste my time trying something that
won't work. The EOS tables the MESA routines interpolates on, is
radiation already included in these tables, or is it included
afterwards by the routines? <br>
<br>
Thanks,<br>
R.<br>
<br>
Aaron Dotter wrote:
<blockquote
 cite="mid:95e...@ma..."
 type="cite">Hi Ricky,
  <div><br>
  </div>
  <div>Sorry I misunderstood; thanks for clarifying. &nbsp;At present, we do
not have the capability to evaluate things like specific heats, ChiT,
and ChiRho as functions of Pgas rather than total P. &nbsp;It is good to
know that this is of interest. &nbsp;If you write some code to fulfill your
needs, you are certainly encouraged to share it with us!</div>
  <div><br>
  </div>
  <div>Best wishes,</div>
  <div>Aaron</div>
  <div><br>
  </div>
  <div><br>
  </div>
  <div><br>
  <div class="gmail_quote">On Mon, Feb 22, 2010 at 7:10 AM, Ricky
Olivier <span dir="ltr">&lt;<a moz-do-not-send="true"
 href="mailto:ol...@sa...">ol...@sa...</a>&gt;</span>
wrote:<br>
  <blockquote class="gmail_quote"
 style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
    <div bgcolor="#ffffff" text="#000000">
Hi Aaron,<br>
    <br>
I have noticed that with regards to the pressure, but it appears not to
be the case for the internal energy, chiT, chiRho and Cv for example. I
need these quantities as evaluated for the gas only.&nbsp; In the code that
I use,&nbsp; I do not assume LTE and treat the radiation energy density and
radiation pressure separately from the gas.<br>
    <br>
Thanks for your input, and the additional info. I am keen on using the
mesa routines, as it has all the top notch EOS in one place ...<br>
    <font color="#888888"><br>
Ricky</font>
    <div>
    <div class="h5"><br>
    <br>
Aaron Dotter wrote:
    <blockquote type="cite">Hi Ricky,
      <div><br>
      </div>
      <div>Actually, the eos module works with Pgas, see
mesa/eos/public/eos_def.f for a list of variables that it works with.</div>
      <div><br>
      </div>
      <div>So, for example, the eos call that returns P(Rho,T) =
eosDT_get
actually returns Pgas. &nbsp;See also mesa/eos/public/eos_lib.f for a list
of different eos subroutines. &nbsp;A function called Radiation_Pressure(T)
is included in eos_lib as a convenience.</div>
      <div><br>
      </div>
      <div>Best wishes,</div>
      <div>Aaron</div>
      <div><br>
      </div>
      <div><br>
      </div>
      <div><br>
      <br>
      <div class="gmail_quote">On Mon, Feb 22, 2010 at 1:25 AM, Ricky
Olivier <span dir="ltr">&lt;<a moz-do-not-send="true"
 href="mailto:ol...@sa..." target="_blank">ol...@sa...</a>&gt;</span>
wrote:<br>
      <blockquote class="gmail_quote"
 style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br>
        <br>
I am interested in using the MESA EOS and Opacity modules for use with<br>
my stellar pulsation code. As such, I have been poking around the MESA<br>
source files, and hacked the sample_eos.f source file to generate EOS<br>
tables in the format I need. However, it seems the MESA EOS routines<br>
automatically add the contribution due to radiation &nbsp;into the<br>
thermodynamic variables. I could easily subtract the contribution to<br>
radiation out, but is there a way of switching it off inside MESA? I<br>
treat &nbsp;radiation separately from the gas in the code I use.<br>
        <br>
Can anyone help me with this?<br>
        <br>
Regards,<br>
Ricky<br>
        <br>
        <br>
------------------------------------------------------------------------------<br>
Download Intel&amp;#174; Parallel Studio Eval<br>
Try the new software tools for yourself. Speed compiling, find bugs<br>
proactively, and fine-tune applications for parallel performance.<br>
See why Intel Parallel Studio got high marks during beta.<br>
        <a moz-do-not-send="true"
 href="http://p.sf.net/sfu/intel-sw-dev" target="_blank">http://p.sf.net/sfu/intel-sw-dev</a><br>
_______________________________________________<br>
mesa-users mailing list<br>
        <a moz-do-not-send="true"
 href="mailto:mes...@li..." target="_blank">mes...@li...</a><br>
        <a moz-do-not-send="true"
 href="https://lists.sourceforge.net/lists/listinfo/mesa-users"
 target="_blank">https://lists.sourceforge.net/lists/listinfo/mesa-users</a><br>
      </blockquote>
      </div>
      <br>
      </div>
    </blockquote>
    </div>
    </div>
    </div>
  </blockquote>
  </div>
  <br>
  </div>
</blockquote>
</body>
</html>

Re: mesa-users] Regarding the MESA EOS

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

Hi Ricky,

Sorry I misunderstood; thanks for clarifying.  At present, we do not have
the capability to evaluate things like specific heats, ChiT, and ChiRho as
functions of Pgas rather than total P.  It is good to know that this is of
interest.  If you write some code to fulfill your needs, you are certainly
encouraged to share it with us!

Best wishes,
Aaron



On Mon, Feb 22, 2010 at 7:10 AM, Ricky Olivier <ol...@sa...> wrote:

>  Hi Aaron,
>
> I have noticed that with regards to the pressure, but it appears not to be
> the case for the internal energy, chiT, chiRho and Cv for example. I need
> these quantities as evaluated for the gas only.  In the code that I use,  I
> do not assume LTE and treat the radiation energy density and radiation
> pressure separately from the gas.
>
> Thanks for your input, and the additional info. I am keen on using the mesa
> routines, as it has all the top notch EOS in one place ...
>
> Ricky
>
>
> Aaron Dotter wrote:
>
> Hi Ricky,
>
>  Actually, the eos module works with Pgas, see mesa/eos/public/eos_def.f
> for a list of variables that it works with.
>
>  So, for example, the eos call that returns P(Rho,T) = eosDT_get actually
> returns Pgas.  See also mesa/eos/public/eos_lib.f for a list of different
> eos subroutines.  A function called Radiation_Pressure(T) is included in
> eos_lib as a convenience.
>
>  Best wishes,
> Aaron
>
>
>
>
> On Mon, Feb 22, 2010 at 1:25 AM, Ricky Olivier <ol...@sa...> wrote:
>
>> Hi,
>>
>> I am interested in using the MESA EOS and Opacity modules for use with
>> my stellar pulsation code. As such, I have been poking around the MESA
>> source files, and hacked the sample_eos.f source file to generate EOS
>> tables in the format I need. However, it seems the MESA EOS routines
>> automatically add the contribution due to radiation  into the
>> thermodynamic variables. I could easily subtract the contribution to
>> radiation out, but is there a way of switching it off inside MESA? I
>> treat  radiation separately from the gas in the code I use.
>>
>> Can anyone help me with this?
>>
>> Regards,
>> Ricky
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Download Intel&#174; Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> mesa-users mailing list
>> mes...@li...
>> https://lists.sourceforge.net/lists/listinfo/mesa-users
>>
>
>

Re: mesa-users] Regarding the MESA EOS

[Ricky O. <ol...@sa...>]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Aaron,<br>
<br>
I have noticed that with regards to the pressure, but it appears not to
be the case for the internal energy, chiT, chiRho and Cv for example. I
need these quantities as evaluated for the gas only.&nbsp; In the code that
I use,&nbsp; I do not assume LTE and treat the radiation energy density and
radiation pressure separately from the gas.<br>
<br>
Thanks for your input, and the additional info. I am keen on using the
mesa routines, as it has all the top notch EOS in one place ...<br>
<br>
Ricky<br>
<br>
Aaron Dotter wrote:
<blockquote
 cite="mid:95e...@ma..."
 type="cite">Hi Ricky,
  <div><br>
  </div>
  <div>Actually, the eos module works with Pgas, see
mesa/eos/public/eos_def.f for a list of variables that it works with.</div>
  <div><br>
  </div>
  <div>So, for example, the eos call that returns P(Rho,T) = eosDT_get
actually returns Pgas. &nbsp;See also mesa/eos/public/eos_lib.f for a list
of different eos subroutines. &nbsp;A function called Radiation_Pressure(T)
is included in eos_lib as a convenience.</div>
  <div><br>
  </div>
  <div>Best wishes,</div>
  <div>Aaron</div>
  <div><br>
  </div>
  <div><br>
  </div>
  <div><br>
  <br>
  <div class="gmail_quote">On Mon, Feb 22, 2010 at 1:25 AM, Ricky
Olivier <span dir="ltr">&lt;<a moz-do-not-send="true"
 href="mailto:ol...@sa...">ol...@sa...</a>&gt;</span>
wrote:<br>
  <blockquote class="gmail_quote"
 style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br>
    <br>
I am interested in using the MESA EOS and Opacity modules for use with<br>
my stellar pulsation code. As such, I have been poking around the MESA<br>
source files, and hacked the sample_eos.f source file to generate EOS<br>
tables in the format I need. However, it seems the MESA EOS routines<br>
automatically add the contribution due to radiation &nbsp;into the<br>
thermodynamic variables. I could easily subtract the contribution to<br>
radiation out, but is there a way of switching it off inside MESA? I<br>
treat &nbsp;radiation separately from the gas in the code I use.<br>
    <br>
Can anyone help me with this?<br>
    <br>
Regards,<br>
Ricky<br>
    <br>
    <br>
------------------------------------------------------------------------------<br>
Download Intel&amp;#174; Parallel Studio Eval<br>
Try the new software tools for yourself. Speed compiling, find bugs<br>
proactively, and fine-tune applications for parallel performance.<br>
See why Intel Parallel Studio got high marks during beta.<br>
    <a moz-do-not-send="true" href="http://p.sf.net/sfu/intel-sw-dev"
 target="_blank">http://p.sf.net/sfu/intel-sw-dev</a><br>
_______________________________________________<br>
mesa-users mailing list<br>
    <a moz-do-not-send="true"
 href="mailto:mes...@li...">mes...@li...</a><br>
    <a moz-do-not-send="true"
 href="https://lists.sourceforge.net/lists/listinfo/mesa-users"
 target="_blank">https://lists.sourceforge.net/lists/listinfo/mesa-users</a><br>
  </blockquote>
  </div>
  <br>
  </div>
</blockquote>
</body>
</html>