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: Marlin C. <mar...@ya...> - 2017-07-10 21:56:34
|
I need tutoring at the most fundamental level in MESA. I can enter data in a windows program but nothing more sophisticated involving language.I live in Fresno California but I can travel to the Bay area or LA for a few days.I am 72, an amateur astronomer and will audit a graduate course at CAL in stellar interiors involving MESA.Can someone work for me at regular tutoring fees?Marlin CostelloTelescope Garden, Fresno |
|
From: Pablo M. <pa...@gm...> - 2017-07-07 12:20:22
|
Hi, thanks for the reminder, this has been fixed in version 9867, and will be up in the next release. Let me know if you find anything else! cheers On Thu, Jul 6, 2017 at 3:09 AM, Glenn-Michael Oomen < gle...@ku...> wrote: > Hi Mesa, > > > A reminder that this has not yet been fixed. > > > So users that use the binary module and are simulating eccentric orbits > with the effect of tides included should be careful for this issue. > > > Best regards, > > Glenn-Michael Oomen > ------------------------------ > *Van:* Glenn-Michael Oomen > *Verzonden:* dinsdag 21 maart 2017 17:56 > *Aan:* mes...@li... > *Onderwerp:* Bug in edot mechanism in binary module > > > Dear developers, > > > I would like to report on a bug in the binary_edot file. It concerns the > tidal mechanism from Hut (1981). > > > In line 129 in the code, there is multiplied by pow_cr(1-b% > eccentricity**2,6.5d0) instead of divided by it, which has huge > implications once the eccentricity becomes large (suppose your eccentricity > is 0.9, this results in a discrepancy of almost 10 orders of magnitude!). > > > So basically in binary_edot.f90, line 128-129: > > > edot_tidal = -27.0d0*qratio*(1+qratio)*pow8(r_phot/osep) & > * b% eccentricity*pow_cr(1-b% eccentricity**2,6.5d0)*b% Ftid_1 > > should be > > edot_tidal = -27.0d0*qratio*(1+qratio)*pow8(r_phot/osep) & > * b% eccentricity*pow_cr(1-b% eccentricity**2,-6.5d0)*b% Ftid_1 > > > as it is given in Eq. 10 of Hut (1981). > > Cheers, > Glenn-Michael Oomen > > > > ------------------------------------------------------------ > ------------------ > 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 on Astrophysics, Argelander-Institut für Astronomie, Universität Bonn |
|
From: Glenn-Michael O. <gle...@ku...> - 2017-07-06 08:27:00
|
Hi Mesa,
A reminder that this has not yet been fixed.
So users that use the binary module and are simulating eccentric orbits with the effect of tides included should be careful for this issue.
Best regards,
Glenn-Michael Oomen
________________________________
Van: Glenn-Michael Oomen
Verzonden: dinsdag 21 maart 2017 17:56
Aan: mes...@li...
Onderwerp: Bug in edot mechanism in binary module
Dear developers,
I would like to report on a bug in the binary_edot file. It concerns the tidal mechanism from Hut (1981).
In line 129 in the code, there is multiplied by pow_cr(1-b% eccentricity**2,6.5d0) instead of divided by it, which has huge implications once the eccentricity becomes large (suppose your eccentricity is 0.9, this results in a discrepancy of almost 10 orders of magnitude!).
So basically in binary_edot.f90, line 128-129:
edot_tidal = -27.0d0*qratio*(1+qratio)*pow8(r_phot/osep) &
* b% eccentricity*pow_cr(1-b% eccentricity**2,6.5d0)*b% Ftid_1
should be
edot_tidal = -27.0d0*qratio*(1+qratio)*pow8(r_phot/osep) &
* b% eccentricity*pow_cr(1-b% eccentricity**2,-6.5d0)*b% Ftid_1
as it is given in Eq. 10 of Hut (1981).
Cheers,
Glenn-Michael Oomen
|
|
From: AbdelBassit A. S. <se...@ho...> - 2017-07-05 17:53:49
|
Hi all : I was able to create a sdB star for 0.8 and 1.2 M_sun. Now, i want to create a sd Oxygen star and for that i did not found enough informations about that. What i shoud do exctely start from a higher mass like : 1.5 M_sun ? For the relax mass or the new mass it could be 0.5 M_sun ? Does it make sense ? Thanks for your help ! Abdelbassit |
|
From: Samuel D. <sd...@sp...> - 2017-07-05 00:41:57
|
The problem was with gawk. I used Homebrew to update gawk and the installation went smoothly. Thank you for your help. Sam Dupree |
|
From: Robert F. <rjf...@as...> - 2017-07-04 12:13:38
|
Sorry about the previous half message.
It's looks like your gawk in /usr/local/bin is trying to load the dylib
maybe try reinstalling that?
Rob
On Jul 4, 2017 8:11 AM, "Robert Farmer" <rjf...@as...> wrote:
Hi
It looks like
/usr/local/bin/gawk
Is
On Jul 4, 2017 12:39 AM, "Frank Timmes" <fx...@ma...> wrote:
> might be ${PATH} issue. do a
>
> % echo ${PATH}
>
> and /Applications/mesasdk/bin should be first.
>
> if /Applications/mesasdk/bin is not first, for example
> because you have a macports installation, then some care
> may be needed depending on what is installed.
>
> this assumes you've installed the mesa sdk properly ...
>
> fxt
>
>
>
> > On Jul 3, 2017, at 9:29 PM, Samuel Dupree <sd...@sp...> wrote:
> >
> > I'm attempting to install the latest version of MESA (r9793) on a Mac
> Pro (desktop) running mac OS X ver. 10.12.5 (Sierra) using
> mesasdk-x86_64_osx-10.10-2016404. The problem I'm having at present is
> building crlibm. The issue is loading the library
> /usr/local/opt/readline/lib/libreadline.6.dylib. The actual error message
> I get is
> > configure: creating ./config.status
> > config.status: creating Makefile
> > dyld: Library not loaded: /usr/local/opt/readline/lib/li
> breadline.6.dylib
> > Referenced from: /usr/local/bin/gawk
> > Reason: image not found
> > ./config.status: line 957: 7032 Done(141) eval sed
> \"\$ac_sed_extra\" "$ac_file_inputs"
> > 7033 Abort trap: 6 | $AWK -f "$tmp/subs.awk" > $tmp/out
> > config.status: error: could not create Makefile
> > make: *** [build] Error 1
> > make: *** No targets specified and no makefile found. Stop.
> >
> > /Volumes/Development/AstrophysicsLib/mesa-r9793/crlibm/crlibm
> > ./build_and_test FAILED
> >
> >
> > One my system, I have a soft link from /usr/local/opt/readline as
> follows:
> >
> > readline -> ../Cellar/readline/7.0.3_1
> > Is there any easy way to have the mesa installation use my soft link to
> libreadline.7.dylib as opposed to the wanting /usr/local/opt/readline/lib/li
> breadline.6.dylib?
> >
> > Please advise.
> >
> > Sam Dupree.
>
> ------------------------------------------------------------
> ------------------
> 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-07-04 12:11:40
|
Hi
It looks like
/usr/local/bin/gawk
Is
On Jul 4, 2017 12:39 AM, "Frank Timmes" <fx...@ma...> wrote:
> might be ${PATH} issue. do a
>
> % echo ${PATH}
>
> and /Applications/mesasdk/bin should be first.
>
> if /Applications/mesasdk/bin is not first, for example
> because you have a macports installation, then some care
> may be needed depending on what is installed.
>
> this assumes you've installed the mesa sdk properly ...
>
> fxt
>
>
>
> > On Jul 3, 2017, at 9:29 PM, Samuel Dupree <sd...@sp...> wrote:
> >
> > I'm attempting to install the latest version of MESA (r9793) on a Mac
> Pro (desktop) running mac OS X ver. 10.12.5 (Sierra) using
> mesasdk-x86_64_osx-10.10-2016404. The problem I'm having at present is
> building crlibm. The issue is loading the library
> /usr/local/opt/readline/lib/libreadline.6.dylib. The actual error message
> I get is
> > configure: creating ./config.status
> > config.status: creating Makefile
> > dyld: Library not loaded: /usr/local/opt/readline/lib/
> libreadline.6.dylib
> > Referenced from: /usr/local/bin/gawk
> > Reason: image not found
> > ./config.status: line 957: 7032 Done(141) eval sed
> \"\$ac_sed_extra\" "$ac_file_inputs"
> > 7033 Abort trap: 6 | $AWK -f "$tmp/subs.awk" > $tmp/out
> > config.status: error: could not create Makefile
> > make: *** [build] Error 1
> > make: *** No targets specified and no makefile found. Stop.
> >
> > /Volumes/Development/AstrophysicsLib/mesa-r9793/crlibm/crlibm
> > ./build_and_test FAILED
> >
> >
> > One my system, I have a soft link from /usr/local/opt/readline as
> follows:
> >
> > readline -> ../Cellar/readline/7.0.3_1
> > Is there any easy way to have the mesa installation use my soft link to
> libreadline.7.dylib as opposed to the wanting /usr/local/opt/readline/lib/
> libreadline.6.dylib?
> >
> > Please advise.
> >
> > Sam Dupree.
>
> ------------------------------------------------------------
> ------------------
> 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: Frank T. <fx...@ma...> - 2017-07-04 04:39:08
|
might be ${PATH} issue. do a
% echo ${PATH}
and /Applications/mesasdk/bin should be first.
if /Applications/mesasdk/bin is not first, for example
because you have a macports installation, then some care
may be needed depending on what is installed.
this assumes you've installed the mesa sdk properly ...
fxt
> On Jul 3, 2017, at 9:29 PM, Samuel Dupree <sd...@sp...> wrote:
>
> I'm attempting to install the latest version of MESA (r9793) on a Mac Pro (desktop) running mac OS X ver. 10.12.5 (Sierra) using mesasdk-x86_64_osx-10.10-2016404. The problem I'm having at present is building crlibm. The issue is loading the library /usr/local/opt/readline/lib/libreadline.6.dylib. The actual error message I get is
> configure: creating ./config.status
> config.status: creating Makefile
> dyld: Library not loaded: /usr/local/opt/readline/lib/libreadline.6.dylib
> Referenced from: /usr/local/bin/gawk
> Reason: image not found
> ./config.status: line 957: 7032 Done(141) eval sed \"\$ac_sed_extra\" "$ac_file_inputs"
> 7033 Abort trap: 6 | $AWK -f "$tmp/subs.awk" > $tmp/out
> config.status: error: could not create Makefile
> make: *** [build] Error 1
> make: *** No targets specified and no makefile found. Stop.
>
> /Volumes/Development/AstrophysicsLib/mesa-r9793/crlibm/crlibm
> ./build_and_test FAILED
>
>
> One my system, I have a soft link from /usr/local/opt/readline as follows:
>
> readline -> ../Cellar/readline/7.0.3_1
> Is there any easy way to have the mesa installation use my soft link to libreadline.7.dylib as opposed to the wanting /usr/local/opt/readline/lib/libreadline.6.dylib?
>
> Please advise.
>
> Sam Dupree.
|
|
From: Samuel D. <sd...@sp...> - 2017-07-04 04:29:44
|
I'm attempting to install the latest version of MESA (r9793) on a Mac
Pro (desktop) running mac OS X ver. 10.12.5 (Sierra) using
mesasdk-x86_64_osx-10.10-2016404. The problem I'm having at present is
building crlibm. The issue is loading the library
/usr/local/opt/readline/lib/libreadline.6.dylib. The actual error
message I get is
configure: creating ./config.status
config.status: creating Makefile
dyld: Library not loaded:
/usr/local/opt/readline/lib/libreadline.6.dylib
Referenced from: /usr/local/bin/gawk
Reason: image not found
./config.status: line 957: 7032 Done(141) eval
sed \"\$ac_sed_extra\" "$ac_file_inputs"
7033 Abort trap: 6 | $AWK -f "$tmp/subs.awk" >
$tmp/out
config.status: error: could not create Makefile
make: *** [build] Error 1
make: *** No targets specified and no makefile found. Stop.
/Volumes/Development/AstrophysicsLib/mesa-r9793/crlibm/crlibm
./build_and_test FAILED
One my system, I have a soft link from /usr/local/opt/readline as follows:
readline -> ../Cellar/readline/7.0.3_1
Is there any easy way to have the mesa installation use my soft link to
libreadline.7.dylib as opposed to the wanting
/usr/local/opt/readline/lib/libreadline.6.dylib?
Please advise.
Sam Dupree.
|
|
From: amber l. <amb...@gm...> - 2017-07-02 07:32:20
|
Don't forget to reply all ---------- Forwarded message ---------- From: Ian Foley <ifo...@gm...> Date: Sun, Jul 2, 2017 at 1:56 AM Subject: Re: [mesa-users] Generating version 9793 To: amber lauer <amb...@gm...> Hi Amber, Thanks for the suggestion. Yes, I could go the route you suggest. Problem is I've always been able to use Windows way back with mesa version 2670 in 2011. That's 6 years. Now a change has been made which is blocking my compilation. Of course, I knew I was taking the risk of this happening. However, it is a change that is needed by only a small part of the total mesa package so it would be nice if there was a reasonable work-around as there is for the mesasdk. There is a windows version of hdf5 which I have downloaded, but I have not had time to follow it through and I do not know which parts I need yet. I've had no time to follow it through. I'd like to ask. What parts of hdf5 do I need if I was to import a windows version of the library. How would I go about it? Thanks once again, Kind regards Ian On 2 July 2017 at 13:34, amber lauer <amb...@gm...> wrote: > Just my two cents- If you're willing to consider a dual-boot set up, I > highly recommend it. The lack of windows support is common in physics, and > in these cases is usually limited to OSX and linux. > > Barring that, you might have some success with a virtual machine. > Virtualbox is free and quite powerful, and I use it for the reverse- > windows stuff that can't be run on linux (using wine). > > Dual booting is usually easy to setup without disturbing your current OS > install, other than shrinking the hard drive space. > > > > On Sun, Jun 4, 2017 at 10:50 PM, Ian Foley <ifo...@gm...> wrote: > >> Hi Rob, >> >> I'll give it a go >> >> Thanks >> >> Ian >> >> On 5 June 2017 at 13:39, Robert Farmer <rjf...@as...> wrote: >> >>> Hi >>> >>> Try just replacing ifort with gfortran in the commands. >>> >>> Rob >>> >>> >>> On Jun 4, 2017 20:33, "Ian Foley" <ifo...@gm...> wrote: >>> >>> Hi, >>> >>> I am a user who is not using the mesasdk, so I use the >>> makefile_header_non_mesasdk file to generate the star executable. >>> >>> A new addition with this version is the hdf5 library which I gather has >>> something to do with processing weak rates. There is nothing in the release >>> notes about it. >>> >>> However, the code in the header file shows how to generate the hdf5 >>> library with ifort, but not with gfortran. So before I delve deeper I'm >>> wondering how I create this library and set it up with gfortran. >>> >>> Thanks >>> Ian >>> >>> ------------------------------------------------------------ >>> ------------------ >>> 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 >> >> > > > -- > Amber Lauer. M.S. Physics > PhD Candidate, > Graduate School of Physics, > Louisiana State University > -- Amber Lauer. M.S. Physics PhD Candidate, Graduate School of Physics, Louisiana State University |
|
From: amber l. <amb...@gm...> - 2017-07-02 07:31:50
|
To be clear, it's probably not possible to copy and paste the hdf5 libraries from the sdk to you local machine, you'll probably have to install the windows version, but you'll have to know where it puts the equivalent libraries. On Sun, Jul 2, 2017 at 2:28 AM, amber lauer <amb...@gm...> wrote: > I have to warn you that while I'm good with windows, I'm not experienced > with supporting it in this capacity. Also, you may find some on this > mailing list willing to help, but this is not guaranteed because it's not > officially supported. > > The hdf5 files needed for MESA are found in the SDK under sdk/share/hdf5. > > As for telling mesa how to find your local libraries, you might be able to > edit the makefile_header_non_mesasdk in MESA/utils/ to point to your > libraries, so you'll have to know their location, but I can't guarantee > this will work. The commands you'll probably need are commented out in the > non sdk header. > > Just to restate, you'll probably have an easier time with a virtual > machine if you don't want to go the dual boot route, and it won't break, at > least not in ways that the user list can't/won't troubleshoot. Installing a > virtual machine via virtualbox is very intuitive, and free, with only a few > clicks in the gui interface, you just need an iso for the OS you plan to > virtualize. I can even help you with this if you get stuck. > > The only things you'll have to learn, assuming you use an ubuntu guest, > are how to install the dependency packages via apt (which is easy and has > lots of support online), and a few bash commands such as cd, and cp, many > of which mimic their DOS counterparts (you'll also have to set the > environment variables but the commands are literally outlined line for line > on the MESA install page). Plus, if you have trouble getting started, many > people on the mailing list will happily support you, largely because we all > know how. > > Unless you are using bash for windows... in which case it might be easier, > but again, I don't recommend it and am not experienced enough with it to > support it. > > > > > > On Sun, Jul 2, 2017 at 1:56 AM, Ian Foley <ifo...@gm...> wrote: > >> Hi Amber, >> >> Thanks for the suggestion. >> >> Yes, I could go the route you suggest. >> >> Problem is I've always been able to use Windows way back with mesa >> version 2670 in 2011. That's 6 years. Now a change has been made which is >> blocking my compilation. Of course, I knew I was taking the risk of this >> happening. However, it is a change that is needed by only a small part of >> the total mesa package so it would be nice if there was a reasonable >> work-around as there is for the mesasdk. >> >> There is a windows version of hdf5 which I have downloaded, but I have >> not had time to follow it through and I do not know which parts I need yet. >> I've had no time to follow it through. >> >> I'd like to ask. What parts of hdf5 do I need if I was to import a >> windows version of the library. How would I go about it? >> >> Thanks once again, >> >> Kind regards >> Ian >> >> On 2 July 2017 at 13:34, amber lauer <amb...@gm...> wrote: >> >>> Just my two cents- If you're willing to consider a dual-boot set up, I >>> highly recommend it. The lack of windows support is common in physics, and >>> in these cases is usually limited to OSX and linux. >>> >>> Barring that, you might have some success with a virtual machine. >>> Virtualbox is free and quite powerful, and I use it for the reverse- >>> windows stuff that can't be run on linux (using wine). >>> >>> Dual booting is usually easy to setup without disturbing your current OS >>> install, other than shrinking the hard drive space. >>> >>> >>> >>> On Sun, Jun 4, 2017 at 10:50 PM, Ian Foley <ifo...@gm...> wrote: >>> >>>> Hi Rob, >>>> >>>> I'll give it a go >>>> >>>> Thanks >>>> >>>> Ian >>>> >>>> On 5 June 2017 at 13:39, Robert Farmer <rjf...@as...> wrote: >>>> >>>>> Hi >>>>> >>>>> Try just replacing ifort with gfortran in the commands. >>>>> >>>>> Rob >>>>> >>>>> >>>>> On Jun 4, 2017 20:33, "Ian Foley" <ifo...@gm...> wrote: >>>>> >>>>> Hi, >>>>> >>>>> I am a user who is not using the mesasdk, so I use the >>>>> makefile_header_non_mesasdk file to generate the star executable. >>>>> >>>>> A new addition with this version is the hdf5 library which I gather >>>>> has something to do with processing weak rates. There is nothing in the >>>>> release notes about it. >>>>> >>>>> However, the code in the header file shows how to generate the hdf5 >>>>> library with ifort, but not with gfortran. So before I delve deeper I'm >>>>> wondering how I create this library and set it up with gfortran. >>>>> >>>>> Thanks >>>>> Ian >>>>> >>>>> ------------------------------------------------------------ >>>>> ------------------ >>>>> 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 >>>> >>>> >>> >>> >>> -- >>> Amber Lauer. M.S. Physics >>> PhD Candidate, >>> Graduate School of Physics, >>> Louisiana State University >>> >> >> > > > -- > Amber Lauer. M.S. Physics > PhD Candidate, > Graduate School of Physics, > Louisiana State University > -- Amber Lauer. M.S. Physics PhD Candidate, Graduate School of Physics, Louisiana State University -- Amber Lauer. M.S. Physics PhD Candidate, Graduate School of Physics, Louisiana State University |
|
From: amber l. <amb...@gm...> - 2017-07-02 07:31:34
|
I have to warn you that while I'm good with windows, I'm not experienced with supporting it in this capacity. Also, you may find some on this mailing list willing to help, but this is not guaranteed because it's not officially supported. The hdf5 files needed for MESA are found in the SDK under sdk/share/hdf5. As for telling mesa how to find your local libraries, you might be able to edit the makefile_header_non_mesasdk in MESA/utils/ to point to your libraries, so you'll have to know their location, but I can't guarantee this will work. The commands you'll probably need are commented out in the non sdk header. Just to restate, you'll probably have an easier time with a virtual machine if you don't want to go the dual boot route, and it won't break, at least not in ways that the user list can't/won't troubleshoot. Installing a virtual machine via virtualbox is very intuitive, and free, with only a few clicks in the gui interface, you just need an iso for the OS you plan to virtualize. I can even help you with this if you get stuck. The only things you'll have to learn, assuming you use an ubuntu guest, are how to install the dependency packages via apt (which is easy and has lots of support online), and a few bash commands such as cd, and cp, many of which mimic their DOS counterparts (you'll also have to set the environment variables but the commands are literally outlined line for line on the MESA install page). Plus, if you have trouble getting started, many people on the mailing list will happily support you, largely because we all know how. Unless you are using bash for windows... in which case it might be easier, but again, I don't recommend it and am not experienced enough with it to support it. On Sun, Jul 2, 2017 at 1:56 AM, Ian Foley <ifo...@gm...> wrote: > Hi Amber, > > Thanks for the suggestion. > > Yes, I could go the route you suggest. > > Problem is I've always been able to use Windows way back with mesa version > 2670 in 2011. That's 6 years. Now a change has been made which is blocking > my compilation. Of course, I knew I was taking the risk of this happening. > However, it is a change that is needed by only a small part of the total > mesa package so it would be nice if there was a reasonable work-around as > there is for the mesasdk. > > There is a windows version of hdf5 which I have downloaded, but I have not > had time to follow it through and I do not know which parts I need yet. > I've had no time to follow it through. > > I'd like to ask. What parts of hdf5 do I need if I was to import a windows > version of the library. How would I go about it? > > Thanks once again, > > Kind regards > Ian > > On 2 July 2017 at 13:34, amber lauer <amb...@gm...> wrote: > >> Just my two cents- If you're willing to consider a dual-boot set up, I >> highly recommend it. The lack of windows support is common in physics, and >> in these cases is usually limited to OSX and linux. >> >> Barring that, you might have some success with a virtual machine. >> Virtualbox is free and quite powerful, and I use it for the reverse- >> windows stuff that can't be run on linux (using wine). >> >> Dual booting is usually easy to setup without disturbing your current OS >> install, other than shrinking the hard drive space. >> >> >> >> On Sun, Jun 4, 2017 at 10:50 PM, Ian Foley <ifo...@gm...> wrote: >> >>> Hi Rob, >>> >>> I'll give it a go >>> >>> Thanks >>> >>> Ian >>> >>> On 5 June 2017 at 13:39, Robert Farmer <rjf...@as...> wrote: >>> >>>> Hi >>>> >>>> Try just replacing ifort with gfortran in the commands. >>>> >>>> Rob >>>> >>>> >>>> On Jun 4, 2017 20:33, "Ian Foley" <ifo...@gm...> wrote: >>>> >>>> Hi, >>>> >>>> I am a user who is not using the mesasdk, so I use the >>>> makefile_header_non_mesasdk file to generate the star executable. >>>> >>>> A new addition with this version is the hdf5 library which I gather has >>>> something to do with processing weak rates. There is nothing in the release >>>> notes about it. >>>> >>>> However, the code in the header file shows how to generate the hdf5 >>>> library with ifort, but not with gfortran. So before I delve deeper I'm >>>> wondering how I create this library and set it up with gfortran. >>>> >>>> Thanks >>>> Ian >>>> >>>> ------------------------------------------------------------ >>>> ------------------ >>>> 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 >>> >>> >> >> >> -- >> Amber Lauer. M.S. Physics >> PhD Candidate, >> Graduate School of Physics, >> Louisiana State University >> > > -- Amber Lauer. M.S. Physics PhD Candidate, Graduate School of Physics, Louisiana State University -- Amber Lauer. M.S. Physics PhD Candidate, Graduate School of Physics, Louisiana State University |
|
From: amber l. <amb...@gm...> - 2017-07-02 03:34:35
|
Just my two cents- If you're willing to consider a dual-boot set up, I highly recommend it. The lack of windows support is common in physics, and in these cases is usually limited to OSX and linux. Barring that, you might have some success with a virtual machine. Virtualbox is free and quite powerful, and I use it for the reverse- windows stuff that can't be run on linux (using wine). Dual booting is usually easy to setup without disturbing your current OS install, other than shrinking the hard drive space. On Sun, Jun 4, 2017 at 10:50 PM, Ian Foley <ifo...@gm...> wrote: > Hi Rob, > > I'll give it a go > > Thanks > > Ian > > On 5 June 2017 at 13:39, Robert Farmer <rjf...@as...> wrote: > >> Hi >> >> Try just replacing ifort with gfortran in the commands. >> >> Rob >> >> >> On Jun 4, 2017 20:33, "Ian Foley" <ifo...@gm...> wrote: >> >> Hi, >> >> I am a user who is not using the mesasdk, so I use the >> makefile_header_non_mesasdk file to generate the star executable. >> >> A new addition with this version is the hdf5 library which I gather has >> something to do with processing weak rates. There is nothing in the release >> notes about it. >> >> However, the code in the header file shows how to generate the hdf5 >> library with ifort, but not with gfortran. So before I delve deeper I'm >> wondering how I create this library and set it up with gfortran. >> >> Thanks >> Ian >> >> ------------------------------------------------------------ >> ------------------ >> 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 > > -- Amber Lauer. M.S. Physics PhD Candidate, Graduate School of Physics, Louisiana State University |
|
From: amber l. <amb...@gm...> - 2017-07-02 03:28:26
|
Yes, that is correct. Mesa compiling is smooth and breezy.
On Sat, Jul 1, 2017 at 10:09 PM, Frank Timmes <fx...@ma...> wrote:
> > ... I often get errors when trying to compile using the sdk compilers
>
> just to be clear, i assume by this you mean non-mesa source code.
>
> fxt
>
>
>
>
> > On Jul 1, 2017, at 7:12 PM, amber lauer <amb...@gm...> wrote:
> >
> > Ok, I'll just switch to your way. I wouldn't have even noticed the
> difference except I often get errors when trying to compile using the sdk
> compilers and I don't want to go bug hunting to fix that...
> >
> > On Sat, Jul 1, 2017 at 8:43 PM, Robert Farmer <rjf...@as...> wrote:
> > Yes it is expected as the SDK ships both gcc and gfortran
> >
> > If you don't want it allways on, I use a shell function
> >
> > function mesa-setup {
> > Export vars and source sdk
> > }
> >
> > Then when I want the SDK on I call mesa-setup
> >
> > Rob
> >
> >
> > On Jul 1, 2017 18:38, "amber lauer" <amb...@gm...> wrote:
> > An additional note: the last "export" line is an accidental copy-paste
> error, it doesn't appear in my profile. Also, I've compiled the newest
> version, I just haven't updated this to reflect it.
> >
> > On Sat, Jul 1, 2017 at 8:35 PM, amber lauer <amb...@gm...>
> wrote:
> > In my user profile settings (.bashrc) I have the following values:
> >
> > # set MESA_DIR to be the directory to which you downloaded MESA
> > export MESA_DIR=/home/amber/executables/mesa8845
> >
> > # set OMP_NUM_THREADS to be the number of cores on your machine
> > export OMP_NUM_THREADS=4
> >
> > # you should have done this when you set up the MESA SDK
> > export MESASDK_ROOT=/home/amber/executables/mesasdk_1_16
> > source $MESASDK_ROOT/bin/mesasdk_init.sh
> > export MESASDK_ROOT=/home/amber/executables/mesasdk_1_16
> >
> > and when I do
> >
> > $ which gcc
> >
> > I get
> >
> > $ ~/<mesasdklocation>/bin/gcc
> >
> > Is this the expected behavior? It's not right? I've actually experienced
> this for a few years, but it was easy enough to comment out the lines in
> .bashrc when I wasn't using it so I never bothered to inquire further.
> >
> > --
> > Amber Lauer. M.S. Physics
> > PhD Candidate,
> > Graduate School of Physics,
> > Louisiana State University
> >
>
>
--
Amber Lauer. M.S. Physics
PhD Candidate,
Graduate School of Physics,
Louisiana State University
|
|
From: Frank T. <fx...@ma...> - 2017-07-02 03:09:24
|
> ... I often get errors when trying to compile using the sdk compilers
just to be clear, i assume by this you mean non-mesa source code.
fxt
> On Jul 1, 2017, at 7:12 PM, amber lauer <amb...@gm...> wrote:
>
> Ok, I'll just switch to your way. I wouldn't have even noticed the difference except I often get errors when trying to compile using the sdk compilers and I don't want to go bug hunting to fix that...
>
> On Sat, Jul 1, 2017 at 8:43 PM, Robert Farmer <rjf...@as...> wrote:
> Yes it is expected as the SDK ships both gcc and gfortran
>
> If you don't want it allways on, I use a shell function
>
> function mesa-setup {
> Export vars and source sdk
> }
>
> Then when I want the SDK on I call mesa-setup
>
> Rob
>
>
> On Jul 1, 2017 18:38, "amber lauer" <amb...@gm...> wrote:
> An additional note: the last "export" line is an accidental copy-paste error, it doesn't appear in my profile. Also, I've compiled the newest version, I just haven't updated this to reflect it.
>
> On Sat, Jul 1, 2017 at 8:35 PM, amber lauer <amb...@gm...> wrote:
> In my user profile settings (.bashrc) I have the following values:
>
> # set MESA_DIR to be the directory to which you downloaded MESA
> export MESA_DIR=/home/amber/executables/mesa8845
>
> # set OMP_NUM_THREADS to be the number of cores on your machine
> export OMP_NUM_THREADS=4
>
> # you should have done this when you set up the MESA SDK
> export MESASDK_ROOT=/home/amber/executables/mesasdk_1_16
> source $MESASDK_ROOT/bin/mesasdk_init.sh
> export MESASDK_ROOT=/home/amber/executables/mesasdk_1_16
>
> and when I do
>
> $ which gcc
>
> I get
>
> $ ~/<mesasdklocation>/bin/gcc
>
> Is this the expected behavior? It's not right? I've actually experienced this for a few years, but it was easy enough to comment out the lines in .bashrc when I wasn't using it so I never bothered to inquire further.
>
> --
> Amber Lauer. M.S. Physics
> PhD Candidate,
> Graduate School of Physics,
> Louisiana State University
>
|
|
From: amber l. <amb...@gm...> - 2017-07-02 02:12:51
|
Ok, I'll just switch to your way. I wouldn't have even noticed the
difference except I often get errors when trying to compile using the sdk
compilers and I don't want to go bug hunting to fix that...
On Sat, Jul 1, 2017 at 8:43 PM, Robert Farmer <rjf...@as...> wrote:
> Yes it is expected as the SDK ships both gcc and gfortran
>
> If you don't want it allways on, I use a shell function
>
> function mesa-setup {
> Export vars and source sdk
> }
>
> Then when I want the SDK on I call mesa-setup
>
> Rob
>
>
> On Jul 1, 2017 18:38, "amber lauer" <amb...@gm...> wrote:
>
> An additional note: the last "export" line is an accidental copy-paste
> error, it doesn't appear in my profile. Also, I've compiled the newest
> version, I just haven't updated this to reflect it.
>
> On Sat, Jul 1, 2017 at 8:35 PM, amber lauer <amb...@gm...> wrote:
>
>> In my user profile settings (.bashrc) I have the following values:
>>
>> # set MESA_DIR to be the directory to which you downloaded MESA
>> export MESA_DIR=/home/amber/executables/mesa8845
>>
>> # set OMP_NUM_THREADS to be the number of cores on your machine
>> export OMP_NUM_THREADS=4
>>
>> # you should have done this when you set up the MESA SDK
>> export MESASDK_ROOT=/home/amber/executables/mesasdk_1_16
>> source $MESASDK_ROOT/bin/mesasdk_init.sh
>> export MESASDK_ROOT=/home/amber/executables/mesasdk_1_16
>>
>> and when I do
>>
>> $ which gcc
>>
>> I get
>>
>> $ ~/<mesasdklocation>/bin/gcc
>>
>> Is this the expected behavior? It's not right? I've actually experienced
>> this for a few years, but it was easy enough to comment out the lines in
>> .bashrc when I wasn't using it so I never bothered to inquire further.
>>
>> --
>> Amber Lauer. M.S. Physics
>> PhD Candidate,
>> Graduate School of Physics,
>> Louisiana State University
>>
>
>
>
> --
> Amber Lauer. M.S. Physics
> PhD Candidate,
> Graduate School of Physics,
> Louisiana State University
>
> ------------------------------------------------------------
> ------------------
> 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
>
>
>
--
Amber Lauer. M.S. Physics
PhD Candidate,
Graduate School of Physics,
Louisiana State University
|
|
From: Robert F. <rjf...@as...> - 2017-07-02 01:43:45
|
Yes it is expected as the SDK ships both gcc and gfortran
If you don't want it allways on, I use a shell function
function mesa-setup {
Export vars and source sdk
}
Then when I want the SDK on I call mesa-setup
Rob
On Jul 1, 2017 18:38, "amber lauer" <amb...@gm...> wrote:
An additional note: the last "export" line is an accidental copy-paste
error, it doesn't appear in my profile. Also, I've compiled the newest
version, I just haven't updated this to reflect it.
On Sat, Jul 1, 2017 at 8:35 PM, amber lauer <amb...@gm...> wrote:
> In my user profile settings (.bashrc) I have the following values:
>
> # set MESA_DIR to be the directory to which you downloaded MESA
> export MESA_DIR=/home/amber/executables/mesa8845
>
> # set OMP_NUM_THREADS to be the number of cores on your machine
> export OMP_NUM_THREADS=4
>
> # you should have done this when you set up the MESA SDK
> export MESASDK_ROOT=/home/amber/executables/mesasdk_1_16
> source $MESASDK_ROOT/bin/mesasdk_init.sh
> export MESASDK_ROOT=/home/amber/executables/mesasdk_1_16
>
> and when I do
>
> $ which gcc
>
> I get
>
> $ ~/<mesasdklocation>/bin/gcc
>
> Is this the expected behavior? It's not right? I've actually experienced
> this for a few years, but it was easy enough to comment out the lines in
> .bashrc when I wasn't using it so I never bothered to inquire further.
>
> --
> Amber Lauer. M.S. Physics
> PhD Candidate,
> Graduate School of Physics,
> Louisiana State University
>
--
Amber Lauer. M.S. Physics
PhD Candidate,
Graduate School of Physics,
Louisiana State University
------------------------------------------------------------
------------------
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: amber l. <amb...@gm...> - 2017-07-02 01:37:37
|
An additional note: the last "export" line is an accidental copy-paste error, it doesn't appear in my profile. Also, I've compiled the newest version, I just haven't updated this to reflect it. On Sat, Jul 1, 2017 at 8:35 PM, amber lauer <amb...@gm...> wrote: > In my user profile settings (.bashrc) I have the following values: > > # set MESA_DIR to be the directory to which you downloaded MESA > export MESA_DIR=/home/amber/executables/mesa8845 > > # set OMP_NUM_THREADS to be the number of cores on your machine > export OMP_NUM_THREADS=4 > > # you should have done this when you set up the MESA SDK > export MESASDK_ROOT=/home/amber/executables/mesasdk_1_16 > source $MESASDK_ROOT/bin/mesasdk_init.sh > export MESASDK_ROOT=/home/amber/executables/mesasdk_1_16 > > and when I do > > $ which gcc > > I get > > $ ~/<mesasdklocation>/bin/gcc > > Is this the expected behavior? It's not right? I've actually experienced > this for a few years, but it was easy enough to comment out the lines in > .bashrc when I wasn't using it so I never bothered to inquire further. > > -- > Amber Lauer. M.S. Physics > PhD Candidate, > Graduate School of Physics, > Louisiana State University > -- Amber Lauer. M.S. Physics PhD Candidate, Graduate School of Physics, Louisiana State University |
|
From: amber l. <amb...@gm...> - 2017-07-02 01:36:07
|
In my user profile settings (.bashrc) I have the following values: # set MESA_DIR to be the directory to which you downloaded MESA export MESA_DIR=/home/amber/executables/mesa8845 # set OMP_NUM_THREADS to be the number of cores on your machine export OMP_NUM_THREADS=4 # you should have done this when you set up the MESA SDK export MESASDK_ROOT=/home/amber/executables/mesasdk_1_16 source $MESASDK_ROOT/bin/mesasdk_init.sh export MESASDK_ROOT=/home/amber/executables/mesasdk_1_16 and when I do $ which gcc I get $ ~/<mesasdklocation>/bin/gcc Is this the expected behavior? It's not right? I've actually experienced this for a few years, but it was easy enough to comment out the lines in .bashrc when I wasn't using it so I never bothered to inquire further. -- Amber Lauer. M.S. Physics PhD Candidate, Graduate School of Physics, Louisiana State University |
|
From: Jing L. <jin...@gm...> - 2017-06-29 15:06:47
|
Thank you very much, Matthew :-D :-D Sincerely, Jing On Thu, Jun 29, 2017 at 8:04 AM, Matthew Clayton < mat...@ex...> wrote: > Hi Jing, > > That's right. You'll need 'use ionization_lib', and probably also 'use > ionization_def' in order to tell the routine which species you're > interested in. Take a look in $MESA_DIR/ionization/public/ for the details > of how that works. You can also look at $MESA_DIR/star/private/profile_getval.f90 > for an example of eval_ionization being used. > > Cheers, > > Matthew > ------------------------------ > *From:* Jing Luan [jin...@gm...] > *Sent:* 29 June 2017 15:32 > *To:* Matthew Clayton > *Cc:* mes...@li... > > *Subject:* Re: [mesa-users] ionization fraction or kap table ? > > Hi Matthew, > > Thank you very much! If I want to call eval_ionization() in > run_star_extras.f, do I just need to add a line saying 'use ionization_lib' > near the beginning of that file please? > > Thank you :-) > > Sincerely, > Jing > > On Wed, Jun 28, 2017 at 4:32 AM, Matthew Clayton < > mat...@ex...> wrote: > >> Hi all, >> >> To add to Rich's answer, you can get MESA to output >> neutral_fraction_H >> neutral_fraction_He >> and >> avg_charge_He >> to profiles. Different linear combinations of these 3 values will give >> you all of the ionization fractions of H and He (exercise for reader). >> >> If you're looking to do calculations using ionization fractions within >> MESA itself, you can use the ionization module. Call eval_ionization() from >> ionization_lib and you can get lots of ionization data on a per-cell basis >> (I believe this is where the data in the profile output I mentioned above >> actually comes from). Word of warning though: that routine does >> occasionally give negative ionization fractions (or at least it did last >> time I used it), so I'm not sure how accurate it is in all cases. >> >> Hope that helps. >> >> Cheers, >> >> Matthew >> >> ------------------------------ >> *From:* Jing Luan [jin...@gm...] >> *Sent:* 27 June 2017 16:01 >> *To:* RICHARD H D TOWNSEND >> *Cc:* mes...@li... users >> *Subject:* Re: [mesa-users] ionization fraction or kap table ? >> >> Thank you very much, Rich. It is very useful :-) :-) >> >> Sincerely, >> Jing >> >> On Mon, Jun 26, 2017 at 9:27 PM, RICHARD H D TOWNSEND < >> tow...@as...> wrote: >> >>> Hi Jing — >>> >>> > On Jun 24, 2017, at 9:55 AM, Jing Luan <jin...@gm...> wrote: >>> > >>> > Dear mesa users, >>> > >>> > 1, Are there parameters in mesa that tells the ionization fraction of >>> (HI to HII) and of (HeI to HeII) please? I search around >>> mesa/star/public/star_data.inc, but did not find any. But maybe I miss >>> something there. >>> > >>> >>> I would suspect not. Nowadays, with tabulated EOS’s, it is unusual to >>> actually solve the Saha equation during a stellar evolution calculation. >>> However, MESA *can* tell you the free electron number density, and so you >>> could calculate the ionization fractions yourself, using the Saha equation >>> (for this, I suggest you ignore excited states of the H/He). >>> >>> > 2, For calculating kappa mechanism due to H or He opacity bumps for >>> driving stellar oscillation, which kappa table and eos table should be >>> adopted please? The default in mesa-r8118 are >>> > >>> > kappa_file_prefix = 'gn93' >>> > >>> > eos_file_prefix = 'mesa' >>> > eosDT_Z1_suffix = '_CO_1' >>> > eosPT_Z1_suffix = ‘_ >>> > CO_1' >>> > >>> >>> For the blue edges of the classical (Cepheid) instability strip, plotted >>> in Fig. 14 of Paxton et al (2015), I used: >>> >>> initial_zfracs = 6 ! Asplund et al. (2009) >>> kappa_file_prefix = 'a09' ! Asplund et al. (2009) >>> >>> …in the &star_job namelist, and >>> >>> initial_Y = 0.2703 ! Asplund et al. (2009) / proto-solar >>> initial_Z = 0.0142 ! Asplund et al. (2009) / proto-solar >>> >>> …in the &controls namelist. I expect the metallicity is less important >>> to driving classical Cepheid pulsations than the relative H/He abundances. >>> >>> cheers, >>> >>> Rich >>> >>> > Many thanks 😊😊😊😊 >>> > >>> > Sincerely, >>> > Jing >>> > ------------------------------------------------------------ >>> ------------------ >>> > 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: Matthew C. <mat...@ex...> - 2017-06-29 15:05:29
|
Hi Jing, That's right. You'll need 'use ionization_lib', and probably also 'use ionization_def' in order to tell the routine which species you're interested in. Take a look in $MESA_DIR/ionization/public/ for the details of how that works. You can also look at $MESA_DIR/star/private/profile_getval.f90 for an example of eval_ionization being used. Cheers, Matthew ________________________________ From: Jing Luan [jin...@gm...] Sent: 29 June 2017 15:32 To: Matthew Clayton Cc: mes...@li... Subject: Re: [mesa-users] ionization fraction or kap table ? Hi Matthew, Thank you very much! If I want to call eval_ionization() in run_star_extras.f, do I just need to add a line saying 'use ionization_lib' near the beginning of that file please? Thank you :-) Sincerely, Jing On Wed, Jun 28, 2017 at 4:32 AM, Matthew Clayton <mat...@ex...<mailto:mat...@ex...>> wrote: Hi all, To add to Rich's answer, you can get MESA to output neutral_fraction_H neutral_fraction_He and avg_charge_He to profiles. Different linear combinations of these 3 values will give you all of the ionization fractions of H and He (exercise for reader). If you're looking to do calculations using ionization fractions within MESA itself, you can use the ionization module. Call eval_ionization() from ionization_lib and you can get lots of ionization data on a per-cell basis (I believe this is where the data in the profile output I mentioned above actually comes from). Word of warning though: that routine does occasionally give negative ionization fractions (or at least it did last time I used it), so I'm not sure how accurate it is in all cases. Hope that helps. Cheers, Matthew ________________________________ From: Jing Luan [jin...@gm...<mailto:jin...@gm...>] Sent: 27 June 2017 16:01 To: RICHARD H D TOWNSEND Cc: mes...@li...<mailto:mes...@li...> users Subject: Re: [mesa-users] ionization fraction or kap table ? Thank you very much, Rich. It is very useful :-) :-) Sincerely, Jing On Mon, Jun 26, 2017 at 9:27 PM, RICHARD H D TOWNSEND <tow...@as...<mailto:tow...@as...>> wrote: Hi Jing — > On Jun 24, 2017, at 9:55 AM, Jing Luan <jin...@gm...<mailto:jin...@gm...>> wrote: > > Dear mesa users, > > 1, Are there parameters in mesa that tells the ionization fraction of (HI to HII) and of (HeI to HeII) please? I search around mesa/star/public/star_data.inc, but did not find any. But maybe I miss something there. > I would suspect not. Nowadays, with tabulated EOS’s, it is unusual to actually solve the Saha equation during a stellar evolution calculation. However, MESA *can* tell you the free electron number density, and so you could calculate the ionization fractions yourself, using the Saha equation (for this, I suggest you ignore excited states of the H/He). > 2, For calculating kappa mechanism due to H or He opacity bumps for driving stellar oscillation, which kappa table and eos table should be adopted please? The default in mesa-r8118 are > > kappa_file_prefix = 'gn93' > > eos_file_prefix = 'mesa' > eosDT_Z1_suffix = '_CO_1' > eosPT_Z1_suffix = ‘_ > CO_1' > For the blue edges of the classical (Cepheid) instability strip, plotted in Fig. 14 of Paxton et al (2015), I used: initial_zfracs = 6 ! Asplund et al. (2009) kappa_file_prefix = 'a09' ! Asplund et al. (2009) …in the &star_job namelist, and initial_Y = 0.2703 ! Asplund et al. (2009) / proto-solar initial_Z = 0.0142 ! Asplund et al. (2009) / proto-solar …in the &controls namelist. I expect the metallicity is less important to driving classical Cepheid pulsations than the relative H/He abundances. cheers, Rich > Many thanks 😊😊😊😊 > > Sincerely, > Jing > ------------------------------------------------------------------------------ > 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...<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://sdm.link/slashdot _______________________________________________ mesa-users mailing list mes...@li...<mailto:mes...@li...> https://lists.sourceforge.net/lists/listinfo/mesa-users |
|
From: Jing L. <jin...@gm...> - 2017-06-29 14:32:36
|
Hi Matthew, Thank you very much! If I want to call eval_ionization() in run_star_extras.f, do I just need to add a line saying 'use ionization_lib' near the beginning of that file please? Thank you :-) Sincerely, Jing On Wed, Jun 28, 2017 at 4:32 AM, Matthew Clayton < mat...@ex...> wrote: > Hi all, > > To add to Rich's answer, you can get MESA to output > neutral_fraction_H > neutral_fraction_He > and > avg_charge_He > to profiles. Different linear combinations of these 3 values will give you > all of the ionization fractions of H and He (exercise for reader). > > If you're looking to do calculations using ionization fractions within > MESA itself, you can use the ionization module. Call eval_ionization() from > ionization_lib and you can get lots of ionization data on a per-cell basis > (I believe this is where the data in the profile output I mentioned above > actually comes from). Word of warning though: that routine does > occasionally give negative ionization fractions (or at least it did last > time I used it), so I'm not sure how accurate it is in all cases. > > Hope that helps. > > Cheers, > > Matthew > > ------------------------------ > *From:* Jing Luan [jin...@gm...] > *Sent:* 27 June 2017 16:01 > *To:* RICHARD H D TOWNSEND > *Cc:* mes...@li... users > *Subject:* Re: [mesa-users] ionization fraction or kap table ? > > Thank you very much, Rich. It is very useful :-) :-) > > Sincerely, > Jing > > On Mon, Jun 26, 2017 at 9:27 PM, RICHARD H D TOWNSEND < > tow...@as...> wrote: > >> Hi Jing — >> >> > On Jun 24, 2017, at 9:55 AM, Jing Luan <jin...@gm...> wrote: >> > >> > Dear mesa users, >> > >> > 1, Are there parameters in mesa that tells the ionization fraction of >> (HI to HII) and of (HeI to HeII) please? I search around >> mesa/star/public/star_data.inc, but did not find any. But maybe I miss >> something there. >> > >> >> I would suspect not. Nowadays, with tabulated EOS’s, it is unusual to >> actually solve the Saha equation during a stellar evolution calculation. >> However, MESA *can* tell you the free electron number density, and so you >> could calculate the ionization fractions yourself, using the Saha equation >> (for this, I suggest you ignore excited states of the H/He). >> >> > 2, For calculating kappa mechanism due to H or He opacity bumps for >> driving stellar oscillation, which kappa table and eos table should be >> adopted please? The default in mesa-r8118 are >> > >> > kappa_file_prefix = 'gn93' >> > >> > eos_file_prefix = 'mesa' >> > eosDT_Z1_suffix = '_CO_1' >> > eosPT_Z1_suffix = ‘_ >> > CO_1' >> > >> >> For the blue edges of the classical (Cepheid) instability strip, plotted >> in Fig. 14 of Paxton et al (2015), I used: >> >> initial_zfracs = 6 ! Asplund et al. (2009) >> kappa_file_prefix = 'a09' ! Asplund et al. (2009) >> >> …in the &star_job namelist, and >> >> initial_Y = 0.2703 ! Asplund et al. (2009) / proto-solar >> initial_Z = 0.0142 ! Asplund et al. (2009) / proto-solar >> >> …in the &controls namelist. I expect the metallicity is less important to >> driving classical Cepheid pulsations than the relative H/He abundances. >> >> cheers, >> >> Rich >> >> > Many thanks 😊😊😊😊 >> > >> > Sincerely, >> > Jing >> > ------------------------------------------------------------ >> ------------------ >> > 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: Matthew C. <mat...@ex...> - 2017-06-28 11:54:01
|
Hi all, To add to Rich's answer, you can get MESA to output neutral_fraction_H neutral_fraction_He and avg_charge_He to profiles. Different linear combinations of these 3 values will give you all of the ionization fractions of H and He (exercise for reader). If you're looking to do calculations using ionization fractions within MESA itself, you can use the ionization module. Call eval_ionization() from ionization_lib and you can get lots of ionization data on a per-cell basis (I believe this is where the data in the profile output I mentioned above actually comes from). Word of warning though: that routine does occasionally give negative ionization fractions (or at least it did last time I used it), so I'm not sure how accurate it is in all cases. Hope that helps. Cheers, Matthew ________________________________ From: Jing Luan [jin...@gm...] Sent: 27 June 2017 16:01 To: RICHARD H D TOWNSEND Cc: mes...@li... users Subject: Re: [mesa-users] ionization fraction or kap table ? Thank you very much, Rich. It is very useful :-) :-) Sincerely, Jing On Mon, Jun 26, 2017 at 9:27 PM, RICHARD H D TOWNSEND <tow...@as...<mailto:tow...@as...>> wrote: Hi Jing — > On Jun 24, 2017, at 9:55 AM, Jing Luan <jin...@gm...<mailto:jin...@gm...>> wrote: > > Dear mesa users, > > 1, Are there parameters in mesa that tells the ionization fraction of (HI to HII) and of (HeI to HeII) please? I search around mesa/star/public/star_data.inc, but did not find any. But maybe I miss something there. > I would suspect not. Nowadays, with tabulated EOS’s, it is unusual to actually solve the Saha equation during a stellar evolution calculation. However, MESA *can* tell you the free electron number density, and so you could calculate the ionization fractions yourself, using the Saha equation (for this, I suggest you ignore excited states of the H/He). > 2, For calculating kappa mechanism due to H or He opacity bumps for driving stellar oscillation, which kappa table and eos table should be adopted please? The default in mesa-r8118 are > > kappa_file_prefix = 'gn93' > > eos_file_prefix = 'mesa' > eosDT_Z1_suffix = '_CO_1' > eosPT_Z1_suffix = ‘_ > CO_1' > For the blue edges of the classical (Cepheid) instability strip, plotted in Fig. 14 of Paxton et al (2015), I used: initial_zfracs = 6 ! Asplund et al. (2009) kappa_file_prefix = 'a09' ! Asplund et al. (2009) …in the &star_job namelist, and initial_Y = 0.2703 ! Asplund et al. (2009) / proto-solar initial_Z = 0.0142 ! Asplund et al. (2009) / proto-solar …in the &controls namelist. I expect the metallicity is less important to driving classical Cepheid pulsations than the relative H/He abundances. cheers, Rich > Many thanks 😊😊😊😊 > > Sincerely, > Jing > ------------------------------------------------------------------------------ > 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...<mailto:mes...@li...> > https://lists.sourceforge.net/lists/listinfo/mesa-users |
|
From: Jing L. <jin...@gm...> - 2017-06-27 15:01:14
|
Thank you very much, Rich. It is very useful :-) :-) Sincerely, Jing On Mon, Jun 26, 2017 at 9:27 PM, RICHARD H D TOWNSEND < tow...@as...> wrote: > Hi Jing — > > > On Jun 24, 2017, at 9:55 AM, Jing Luan <jin...@gm...> wrote: > > > > Dear mesa users, > > > > 1, Are there parameters in mesa that tells the ionization fraction of > (HI to HII) and of (HeI to HeII) please? I search around > mesa/star/public/star_data.inc, but did not find any. But maybe I miss > something there. > > > > I would suspect not. Nowadays, with tabulated EOS’s, it is unusual to > actually solve the Saha equation during a stellar evolution calculation. > However, MESA *can* tell you the free electron number density, and so you > could calculate the ionization fractions yourself, using the Saha equation > (for this, I suggest you ignore excited states of the H/He). > > > 2, For calculating kappa mechanism due to H or He opacity bumps for > driving stellar oscillation, which kappa table and eos table should be > adopted please? The default in mesa-r8118 are > > > > kappa_file_prefix = 'gn93' > > > > eos_file_prefix = 'mesa' > > eosDT_Z1_suffix = '_CO_1' > > eosPT_Z1_suffix = ‘_ > > CO_1' > > > > For the blue edges of the classical (Cepheid) instability strip, plotted > in Fig. 14 of Paxton et al (2015), I used: > > initial_zfracs = 6 ! Asplund et al. (2009) > kappa_file_prefix = 'a09' ! Asplund et al. (2009) > > …in the &star_job namelist, and > > initial_Y = 0.2703 ! Asplund et al. (2009) / proto-solar > initial_Z = 0.0142 ! Asplund et al. (2009) / proto-solar > > …in the &controls namelist. I expect the metallicity is less important to > driving classical Cepheid pulsations than the relative H/He abundances. > > cheers, > > Rich > > > Many thanks 😊😊😊😊 > > > > Sincerely, > > Jing > > ------------------------------------------------------------ > ------------------ > > 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: RICHARD H D T. <tow...@as...> - 2017-06-27 04:27:58
|
Hi Jing — > On Jun 24, 2017, at 9:55 AM, Jing Luan <jin...@gm...> wrote: > > Dear mesa users, > > 1, Are there parameters in mesa that tells the ionization fraction of (HI to HII) and of (HeI to HeII) please? I search around mesa/star/public/star_data.inc, but did not find any. But maybe I miss something there. > I would suspect not. Nowadays, with tabulated EOS’s, it is unusual to actually solve the Saha equation during a stellar evolution calculation. However, MESA *can* tell you the free electron number density, and so you could calculate the ionization fractions yourself, using the Saha equation (for this, I suggest you ignore excited states of the H/He). > 2, For calculating kappa mechanism due to H or He opacity bumps for driving stellar oscillation, which kappa table and eos table should be adopted please? The default in mesa-r8118 are > > kappa_file_prefix = 'gn93' > > eos_file_prefix = 'mesa' > eosDT_Z1_suffix = '_CO_1' > eosPT_Z1_suffix = ‘_ > CO_1' > For the blue edges of the classical (Cepheid) instability strip, plotted in Fig. 14 of Paxton et al (2015), I used: initial_zfracs = 6 ! Asplund et al. (2009) kappa_file_prefix = 'a09' ! Asplund et al. (2009) …in the &star_job namelist, and initial_Y = 0.2703 ! Asplund et al. (2009) / proto-solar initial_Z = 0.0142 ! Asplund et al. (2009) / proto-solar …in the &controls namelist. I expect the metallicity is less important to driving classical Cepheid pulsations than the relative H/He abundances. cheers, Rich > Many thanks 😊😊😊😊 > > Sincerely, > Jing > ------------------------------------------------------------------------------ > 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.
