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: Falk H. <fh...@uv...> - 2011-06-14 02:20:20
|
We used to run MESA on Fedora 12 64 bits before upgrading to 13 and 14. I can not recall that there where ever problems which were Fedora specific. We ran with intel for sure, and I believe also with gfortran. Falk. On 8-Jun-11, at 10:22 AM, Bill Paxton wrote: > Hi, > > Is there someone out there who has gotten mesa to work with Fedora > 12 64 bits? > Could you please help a new user get started? He's had no luck > with either ifort or gfortran. > > Thanks, > Bill > > > > ------------------------------------------------------------------------------ > EditLive Enterprise is the world's most technically advanced content > authoring tool. Experience the power of Track Changes, Inline Image > Editing and ensure content is compliant with Accessibility Checking. > http://p.sf.net/sfu/ephox-dev2dev > _______________________________________________ > mesa-users mailing list > mes...@li... > https://lists.sourceforge.net/lists/listinfo/mesa-users -- Falk Herwig Dept of Physics & Astronomy, U of Victoria fh...@uv..., tel: +1 (250) 721-7743 |
|
From: Ehsan M. <mor...@ia...> - 2011-06-10 18:51:10
|
<html><div> Dear MESA users. Hi. I tried to install MESA on a rather old machine, but with a recent Ubuntu distribution, hence the last up-to-dated gfortran compiler, but I received the following error: gfortran -fopenmp -o ../sample sample_eos.o -L../../make -leos -L../../../lib -lchem -lnum -lmtx -lmesalapack -lmesablas -lalert -linterp_2d -linterp_1d -lutils -lconst ../utils/build_and_test: line 33: 21696 Segmentation fault ./test_quietly /home/emoravveji/mesa/eos/test FAILED I would appreciate if someone help me with this. With kind regards. Ehsan Moravveji. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
|
From: Ming Y. <my...@ma...> - 2011-06-10 16:15:31
|
Dear all: I try to run the sample code in /mesa/star/test_suite/pluse. But it is just says that: failed in el_sig_loop 1 =.= Well...what's this meaning for??? Thanks! --------------------------------- Ming Yang Department of Astronomy Beijing Normal University 19 Xinjiekou Wai Street Beijing, 100875 P.R.China E-mail: my...@ma... --------------------------------- |
|
From: Ming Y. <my...@ma...> - 2011-06-10 08:54:45
|
Dear all: I can't find the meaning of "xa_scale" in run_star_default.dek or star_default.dek. What is it for??? Thanks! Best Regards --------------------------------- Ming Yang Department of Astronomy Beijing Normal University 19 Xinjiekou Wai Street Beijing, 100875 P.R.China E-mail: my...@ma... --------------------------------- |
|
From: Bill P. <pa...@ki...> - 2011-06-09 17:31:29
|
Hi, Oops -- I lied when I said we didn't have a test suite case showing the new way to do irradiated planets. What a surprise to find that the test called 'irradiated_planet' is actually demonstrating the new way! I answered your earlier email before I'd had a morning cup of coffee -- bad idea. ;-) The irradiated_planet example works in 2 steps. The 1st (inlist1) prepares a model for changing to the constant pressure surface boundary condition, and the 2nd (inlist2) switches to the new BC and evolves the planet with it. -B On Jun 9, 2011, at 8:24 AM, Bill Paxton wrote: > Also, you should know that there is another way > to deal with irradiated planets that uses a constant > pressure surface boundary condition following > Guillot & Havel, A&A 527, A20 (2011). > I haven't added a test_suite case for it yet (I'll do that soon!), > but let me know if you are interested in trying it > and I'll provide some more info for you. |
|
From: Bill P. <pa...@ki...> - 2011-06-09 15:24:21
|
Hi Shih-Hsin,
I don't know if there is a "first prinicples" way to decide
on the value for column_depth_for_irradiation.
As a rule of thumb, you're looking for a value that is
small enough so that the energy is deposited in a region
of "not too large" optical depth (something < 10 for sure),
but at the same time large enough so that mesa can
deal with it (too tiny means it will try to deposit
all of the energy in one or two cells and that might
be tough for convergence.) The test suite example
uses a column depth of 1 g cm^2 -- you might try that
and check to see the optical depth corresponding to that.
BTW: just a reminder to use
kappa_file_prefix = 'gs98f'
so that you get the new Freedman low T opacities.
Also, you should know that there is another way
to deal with irradiated planets that uses a constant
pressure surface boundary condition following
Guillot & Havel, A&A 527, A20 (2011).
I haven't added a test_suite case for it yet (I'll do that soon!),
but let me know if you are interested in trying it
and I'll provide some more info for you.
Cheers,
Bill
On Jun 9, 2011, at 12:48 AM, 張世昕 wrote:
> Hi,
>
> Two parameters are needed in the &controls namelist
> when the irradiation is involved.
> I could figure out the irradiation_flux, but don't know
> how to determine the column_depth_for_irradiation (i.e. m_irradiation).
>
> ex.
> a planet (0.001Msun & atm=simple_photosphere) with a 3 day period
> around a solar-type star. What's the column_depth_for_irradiation?
>
> Thanks!!
> Shih-Hsin
>
>
|
|
From: 張世昕 <ss...@as...> - 2011-06-09 07:48:44
|
Hi, Two parameters are needed in the &controls namelist when the irradiation is involved. I could figure out the irradiation_flux, but don't know how to determine the column_depth_for_irradiation (i.e. m_irradiation). ex. a planet (0.001Msun & atm=simple_photosphere) with a 3 day period around a solar-type star. What's the column_depth_for_irradiation? Thanks!! Shih-Hsin |
|
From: Bill P. <pa...@ki...> - 2011-06-08 17:23:05
|
Hi, Is there someone out there who has gotten mesa to work with Fedora 12 64 bits? Could you please help a new user get started? He's had no luck with either ifort or gfortran. Thanks, Bill |
|
From: M. Y. <my...@ma...> - 2011-06-05 16:22:49
|
Dear Aaron: Thanks very much for answer my question! After trying several times...I find that it's...an...anthropic factor which cause this error...you know, because some political events...whole networks of my country have been contaminated in these day...a lots of files through svn cannot be downloaded correctly...maybe I can only get the correct files a few days later...Thanks! Best Regards --------------------------------- Ming Yang Department of Astronomy Beijing Normal University 19 Xinjiekou Wai Street Beijing, 100875 P.R.China E-mail: my...@ma... --------------------------------- 发件人： Aaron Dotter 发送时间： 2011-06-05 23:16:43 收件人： Ming Yang 抄送： mesa-users 主题： Re: [mesa-users] About some parameters in the samples Hi Ming, The test_suite directory contains many cases that demonstrate broad (but incomplete) set of MESA capabilities. However, some of these cases are fairly advanced and not the best way to get started using the code. The 15 Msun Si burn is there first and foremost as a test of MESA's ability to do this challenging calculation. In mesa/star/test/ you will find an inlist called 'inlist_first_thing_to_try' and this is a great place to start. It's a very simple example of a 3 Msun star. Once you've read the inlist and done the computation, you can start to modify the options in that inlist and/or add additional parameters. All of the parameters in the inlist must be found in either mesa/star/test/src/run_star_defaults.dek or mesa/star/public/star_defaults.dek. You can read both of these files to find the parameters and learn something about how they're used and what typical values are. For example, mesh_delta_coeff is set in the mesh_adjustment section of star_defaults.dek. There is no documentation (other than the source code) for MESA at present, but it is something we are beginning to focus on. If you have more specific questions, feel free to ask on the mesa-users list. Aaron |
|
From: Aaron D. <aar...@gm...> - 2011-06-05 15:08:03
|
Hi Ming, The test_suite directory contains many cases that demonstrate broad (but incomplete) set of MESA capabilities. However, some of these cases are fairly advanced and not the best way to get started using the code. The 15 Msun Si burn is there first and foremost as a test of MESA's ability to do this challenging calculation. In mesa/star/test/ you will find an inlist called 'inlist_first_thing_to_try' and this is a great place to start. It's a very simple example of a 3 Msun star. Once you've read the inlist and done the computation, you can start to modify the options in that inlist and/or add additional parameters. All of the parameters in the inlist must be found in either mesa/star/test/src/run_star_defaults.dek or mesa/star/public/star_defaults.dek. You can read both of these files to find the parameters and learn something about how they're used and what typical values are. For example, mesh_delta_coeff is set in the mesh_adjustment section of star_defaults.dek. There is no documentation (other than the source code) for MESA at present, but it is something we are beginning to focus on. If you have more specific questions, feel free to ask on the mesa-users list. Aaron |
|
From: Ming Y. <my...@ma...> - 2011-06-05 14:26:07
|
Hello World.... Well, MESA is a great tool for Astrophysics. Thanks for the developers! Recently, I have found MESA and try to use it to modelling the RSGs. And I do note that there are some samples in the "test_suite" directory. But I don't know how the parameters in the code are got involved. e.g. in the inlist file of "15M_si_burn", there are some parameters I can't find in run_star_default.dek and star_default.dek, such as mesh_delta_coeff, log_center_density_limit, xa_scale and so on. Is there some other introduction files about these parameters existing? And I also wondering that where the vaule of these parameters comes from( e.g. log_center_density_limit=12 )? Because I have searched some papers and not find such vaule. Thanks very much! Best Regards --------------------------------- Ming Yang Department of Astronomy Beijing Normal University 19 Xinjiekou Wai Street Beijing, 100875 P.R.China E-mail: my...@ma... --------------------------------- |
|
From: Bill P. <pa...@ki...> - 2011-05-26 17:47:54
|
Hi Ehsan, On May 26, 2011, at 10:24 AM, Ehsan Moravveji wrote: > 1- Do you have some specific object in mind? not some astrophysical object if that is what you mean. the "object" of the effort is to get mesa to the level of the current best codes, and that will require detailed comparisons to the results of those codes. > 2- Are you going to publish this work? yes The comparison results will eventually appear in a new mesa "update" paper like the previous "instrument" paper. The new paper will present the evidence supporting mesa as being ready to use in creating stellar models for astroseismology. Just like the previous instrument paper, it won't itself contains any new science -- instead, it will provide a reference for those who will then use the new things in mesa to do new science (I hope!). So anyone who hopes to publish papers using models from mesa with applications to astroseismology should be highly motivated to make sure that there are relevant comparison cases include in the mesa astroseismology verification effort! Cheers, Bill |
|
From: Bill P. <pa...@ki...> - 2011-05-26 17:07:03
|
Hi, I'll be working with a couple students this summer testing mesa's ability to make models for astroseismology. For "normal" stars from ZAMS to SGB, we will compare against the data from the wonderful CoRoT website (thanks to Yveline Lebreton!) http://www.astro.up.pt/corot/compmod/ They supply many models from many codes in FGONG format that we can use for comparisons -- it has already revealed a lot. It would be tremendously useful to have similar comparison data for other cases such as evolved stars and WDs. Preferably, FGONG output for lots of important cases created by lots of codes that are the current state-of-the-art. If you care about astroseismology and would like to see mesa be able to make stellar models for use doing science with the wonderful data that is flooding in, please help us get good comparison data! If you know someone who has such data or could create it, please do some "out-reach". ;-) Thanks, Bill |
|
From: Bill P. <pa...@ki...> - 2011-05-21 19:50:23
|
Here are the main changes since the last release (3251).
Move rate caching and interpolation from net to rates to make them available for more general use.
Add Traxler option for thermohaline (not verified yet)
thermohaline_option = 'Kippenhahn'
! determines which method to use for calculating thermohaline diffusion coef
! if == 'Traxler', use method of Traxler, Garaud, & Stellmach, ApJ Letters, 728:L29 (2011).
! if == 'Kippenhahn', use method of Kippenhahn, R., Ruschenplatt, G., & Thomas, H.-C. 1980, A&A, 91, 175.
Bug fixes for element diffusion -- now gives smoother brunt (see attached slide)
As usual, let me know if you run into problems. I've checked this with ifort and gfortran, but you never know....
Cheers,
Bill
|
|
From: Bill P. <pa...@ki...> - 2011-05-18 15:34:56
|
Hi Ilka, I'm glad to hear that you are digging into mesa. And don't hesitate to send emails with questions (please send them to mesa-users). There are a lot of changes happening in mesa related to nets. The jina reaclib rates are now available in a separate module (called reaclib) and the net module is now able to call reaclib and weaklib for rates. Net is also able to take a set of isotopes and automatically add all relevant reactions. With those changes, the jina module was redundant and it has been removed. In terms of sparse matrix solvers, we no longer support sparskit, but PARDISO works fine. I suggest you start by running some 1 zone burns using the new tool provided in net/test. Edit net/test/inlist_one_zone_burn to select the net and set other control parameters. For a start, use a small net (basic.net is the smallest there is), and set which_decsol = 1 ! lapack Once you have that working you can try bigger nets and other matrix solvers (e.g. which_decsol = 3 ! mkl_pardiso) Then do ./burn to run it. You can take a look at the code in net/test/src/one_zone_burn.f to get an idea for what it is doing. For doing net definitions for large number of isotopes using all relevant reactions from reaclib and weaklib, you can just create a simple text file such as this one from mesa/data/net_data/nets: |
|
From: Aaron D. <aar...@gm...> - 2011-05-06 15:52:14
|
Dear MESA users, Thanks to everyone who filled out an entry in the user info spreadsheet already. We've had a good response already but I know there are more of you out there... Mass emails like this are annoying and I won't continue to send them every few days, I promise. If you haven't filled out your information yet, please do so at your earliest convenience. It will just take a minute and provides information that is valuable to the MESA project. http://goo.gl/kLxNm Thanks again, Aaron On Tue, May 3, 2011 at 1:07 PM, Aaron Dotter <aar...@gm...> wrote: > Dear MESA users, > > We are attempting to better understand the MESA user population. The email > list registration is the only thing we have to go on right now, and it's not > much. > > We ask you to please fill in one line in the following google spreadsheet. > It only takes a few seconds and will be most helpful to us. > > http://goo.gl/kLxNm > > > Thanks, > Aaron > on behalf of the MESA Council > |
|
From: Lars B. <bil...@ki...> - 2011-05-06 03:01:06
|
Theodore, Yes, you are welcome to attend! Just send me a title, and let wa...@ki... know your name and affiliation so that he can make a nametag! South Coast Inn may still have rooms, so dig back in the emails to make the reservation. Cheers Lars On May 5, 2011, at 7:56 PM, Theodore Arthur Sande wrote: > Dear Lars, Bill, Frank, Aaron and Falk, > > A belated thanks for the invitation to MESA FEST. At the time, I did not > consider attending since my mother had been recently diagnosed with > glioblastoma multiforme IV, the most deadly cancer known. I was spending my > time at MIT working on the final 6 months of my thesis research with Prof. Paul > Joss, with the remainder devoted to working with my mother's doctors on > experimental treatments, thus forseeably precluding attendance. > > The experimental treatments have just been this week exhausted, and my mother is > now in hospice. After a discussion with her, I was wondering if it is possible > to still attend MESA fest? Given the circumstances, I am not sure if I could > prepare a presentation* in time, but I could dicuss my research with MESA in > depth in the breakout sessions. I have generated 1000+ evotionary runs for low > mass stars, and thus have a unique users perspective in this regime. I would be > happy to share any insights I have gained. I would also like to discuss in depth > possible future modifications, e.g. evolutionary time-step "accuracy" control, > which I think remains an unresolved issue in most, if not all, henyey codes > extant. > > Some associates have kindly offered to pay my expenses. I am at present working > on my thesis in WI near my mother. I think attending would be a mutually > beneficial experience, since I will have one of the first "MESA thesi". Thank > you for your consideration on this request. > > Sicnerely, > > Theodore Arthur Sande > > MIT Department of Physics > ta...@mi... > 262-527-1776 > > *Prof Joss presented my first research at the IAU 2009 in Rio. > > > ----- End forwarded message ----- > > > Theodore Arthur Sande > > MIT Department of Physics > ta...@mi... |
|
From: Theodore A. S. <ta...@MI...> - 2011-05-06 02:57:09
|
Dear Lars, Bill, Frank, Aaron and Falk, A belated thanks for the invitation to MESA FEST. At the time, I did not consider attending since my mother had been recently diagnosed with glioblastoma multiforme IV, the most deadly cancer known. I was spending my time at MIT working on the final 6 months of my thesis research with Prof. Paul Joss, with the remainder devoted to working with my mother's doctors on experimental treatments, thus forseeably precluding attendance. The experimental treatments have just been this week exhausted, and my mother is now in hospice. After a discussion with her, I was wondering if it is possible to still attend MESA fest? Given the circumstances, I am not sure if I could prepare a presentation* in time, but I could dicuss my research with MESA in depth in the breakout sessions. I have generated 1000+ evotionary runs for low mass stars, and thus have a unique users perspective in this regime. I would be happy to share any insights I have gained. I would also like to discuss in depth possible future modifications, e.g. evolutionary time-step "accuracy" control, which I think remains an unresolved issue in most, if not all, henyey codes extant. Some associates have kindly offered to pay my expenses. I am at present working on my thesis in WI near my mother. I think attending would be a mutually beneficial experience, since I will have one of the first "MESA thesi". Thank you for your consideration on this request. Sicnerely, Theodore Arthur Sande MIT Department of Physics ta...@mi... 262-527-1776 *Prof Joss presented my first research at the IAU 2009 in Rio. ----- End forwarded message ----- Theodore Arthur Sande MIT Department of Physics ta...@mi... |
|
From: Aaron D. <aar...@gm...> - 2011-05-03 17:08:05
|
Dear MESA users, We are attempting to better understand the MESA user population. The email list registration is the only thing we have to go on right now, and it's not much. We ask you to please fill in one line in the following google spreadsheet. It only takes a few seconds and will be most helpful to us. http://goo.gl/kLxNm Thanks, Aaron on behalf of the MESA Council |
|
From: Jean-Claude P. <jc...@gm...> - 2011-05-03 17:07:48
|
Thanks Bill and Aaron. Checking out revision 3251 fixed the issue. Cheers, JC On 02/05/11 20:23, Aaron Dotter wrote: > Hi Jean-Claude, > > The jina module became obsolete in 3190, so my guess is that when you > did svn update, it didn't do it's job completely. Please try to > udpate again and, while you're at it, go to 3251 since it is the > current release. > > Aaron > > > > On Mon, May 2, 2011 at 8:17 PM, Jean-Claude Passy <jc...@gm... > <mailto:jc...@gm...>> wrote: > > Dear MESA users, > > I am encountering an error when trying to build revision 3190: > > ################################################## > > /rpod2/jcpassy/MESA/mesa/atm > building atm package. > > make: `libatm.a' is up to date. > make: `libatm.a' is up to date. > ifort -openmp -threads -o ../plotter plot_atm.o -L../../make -latm > -L../../../lib -leos -lkap -ljina -lweak -lnet -lscreen -lrates > -lreaclib -lneu -lchem -linterp_2d -linterp_1d -lnum -lutils -lalert > -lconst -lmtx -lmkl_intel_lp64 -lmkl_intel_thread -lmkl_lapack95_lp64 > -lmkl_core -liomp5 -lpthread > ld: cannot find -ljina > make: *** [plotter] Error 1 > > /rpod2/jcpassy/MESA/mesa/atm/test > FAILED > ################################################## > > It is weird because libjina is supposed to be mesa/lib but I cannot find it: > > ################################################## > > [14:01:45] helix:$ locate libjina > > ... > > /rpod2/jcpassy/MESA/mesa/jina/make/libjina.a > > /rpod2/jcpassy/MESA/mesa/lib/libjina.a > > ... > > [14:02:07] helix:$ ls /rpod2/jcpassy/MESA/mesa/lib > > libalert.a libconst.a libinterp_2d.a libnet.a librates.a libutils.a > > libchem.a libeos.a libkap.a libneu.a libreaclib.a libweak.a > > libcolors.a libinterp_1d.a libmtx.a libnum.a libscreen.a > > ################################################# > > I would really appreciate if someone could help me to fix this. > > Thanks a lot, > > JC > > > > > ------------------------------------------------------------------------------ > WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > _______________________________________________ > mesa-users mailing list > mes...@li... > <mailto:mes...@li...> > https://lists.sourceforge.net/lists/listinfo/mesa-users > > |
|
From: Aaron D. <aar...@gm...> - 2011-05-03 00:23:30
|
Hi Jean-Claude, The jina module became obsolete in 3190, so my guess is that when you did svn update, it didn't do it's job completely. Please try to udpate again and, while you're at it, go to 3251 since it is the current release. Aaron On Mon, May 2, 2011 at 8:17 PM, Jean-Claude Passy <jc...@gm...> wrote: > Dear MESA users, > > I am encountering an error when trying to build revision 3190: > > ################################################## > /rpod2/jcpassy/MESA/mesa/atm > building atm package. > > make: `libatm.a' is up to date. > make: `libatm.a' is up to date. > ifort -openmp -threads -o ../plotter plot_atm.o -L../../make -latm > -L../../../lib -leos -lkap -ljina -lweak -lnet -lscreen -lrates > -lreaclib -lneu -lchem -linterp_2d -linterp_1d -lnum -lutils -lalert > -lconst -lmtx -lmkl_intel_lp64 -lmkl_intel_thread -lmkl_lapack95_lp64 > -lmkl_core -liomp5 -lpthread > ld: cannot find -ljina > make: *** [plotter] Error 1 > > /rpod2/jcpassy/MESA/mesa/atm/test > FAILED > ################################################## > > It is weird because libjina is supposed to be mesa/lib but I cannot find it: > > ################################################## [14:01:45] helix:$ > locate libjina ... /rpod2/jcpassy/MESA/mesa/jina/make/libjina.a > /rpod2/jcpassy/MESA/mesa/lib/libjina.a ... [14:02:07] helix:$ ls > /rpod2/jcpassy/MESA/mesa/lib libalert.a libconst.a libinterp_2d.a libnet.a > librates.a libutils.a libchem.a libeos.a libkap.a libneu.a libreaclib.a > libweak.a libcolors.a libinterp_1d.a libmtx.a libnum.a libscreen.a > ################################################# > > I would really appreciate if someone could help me to fix this. > > Thanks a lot, > > JC > > > > > > ------------------------------------------------------------------------------ > WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > _______________________________________________ > mesa-users mailing list > mes...@li... > https://lists.sourceforge.net/lists/listinfo/mesa-users > > |
|
From: Bill P. <pa...@ki...> - 2011-05-03 00:22:07
|
On May 2, 2011, at 5:17 PM, Jean-Claude Passy wrote: > 3190 Hi, Please try 3251-- it is the current release. Do the following in your mesa directory: svn update -r 3251 ./clean ./install If that runs into problems, it may be necessary to do a fresh checkout: svn co -r 3251 http://mesa.svn.sourceforge.net/svnroot/mesa/trunk mesa Good luck, Bill |
|
From: Jean-Claude P. <jc...@gm...> - 2011-05-03 00:12:24
|
Dear MESA users, I am encountering an error when trying to build revision 3190: ################################################## /rpod2/jcpassy/MESA/mesa/atm building atm package. make: `libatm.a' is up to date. make: `libatm.a' is up to date. ifort -openmp -threads -o ../plotter plot_atm.o -L../../make -latm -L../../../lib -leos -lkap -ljina -lweak -lnet -lscreen -lrates -lreaclib -lneu -lchem -linterp_2d -linterp_1d -lnum -lutils -lalert -lconst -lmtx -lmkl_intel_lp64 -lmkl_intel_thread -lmkl_lapack95_lp64 -lmkl_core -liomp5 -lpthread ld: cannot find -ljina make: *** [plotter] Error 1 /rpod2/jcpassy/MESA/mesa/atm/test FAILED ################################################## It is weird because libjina is supposed to be mesa/lib but I cannot find it: ################################################## [14:01:45] helix:$ locate libjina ... /rpod2/jcpassy/MESA/mesa/jina/make/libjina.a /rpod2/jcpassy/MESA/mesa/lib/libjina.a ... [14:02:07] helix:$ ls /rpod2/jcpassy/MESA/mesa/lib libalert.a libconst.a libinterp_2d.a libnet.a librates.a libutils.a libchem.a libeos.a libkap.a libneu.a libreaclib.a libweak.a libcolors.a libinterp_1d.a libmtx.a libnum.a libscreen.a ################################################# I would really appreciate if someone could help me to fix this. Thanks a lot, JC |
|
From: Kent G. B. <kg...@la...> - 2011-05-02 22:10:26
|
3251 seems to be building and running on my 64-bit Intel Linux box. MESA++ release 97 has been checked in; it builds and runs on 3251. Bill Paxton wrote: > Hi, > > gfortran didn't like the changes I made for round 1 of the bug fix, so we're going a second round. > 3251 seems happy with both ifort and gfortran, at least on my mac. > as usual, I regret the bugs, but I can promise to give them top priority. > sorry for the inconvenience. > > I should also mention a change in the opacity tables. > We now have a separate set of tables for folks who'd like to use > the Freedman low T tables -- > ------------------------------------------------------------------------ > > > request them by setting > kappa_file_prefix = 'gs98f' > that will give you tables that are like gs98 except at low T > where they use Freedman values where possible. > this is a huge improvement for brown dwarfs & planets > since it gives us real data to go on for logR > 1 whereas > without it we were forced to hope that convection would > make the opacities irrelevant. > > this plot shows the new regions for gs98f. > the excellent coverage at low T is an enabling step > for modeling irradiated giant planets that have > large isothermal regions at the surface that are > radiative and therefore require accurate opacities. > ------------------------------------------------------------------------ > > > if you want Freedman + some abundances other than gs98, > let me know -- you can easily produce other combinations > in the kap/preprocessor. > > -Bill > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > ------------------------------------------------------------------------ > > _______________________________________________ > mesa-news mailing list > mes...@li... > https://lists.sourceforge.net/lists/listinfo/mesa-news |
|
From: Bill P. <pa...@ki...> - 2011-04-30 14:42:03
|
Hi, gfortran didn't like the changes I made for round 1 of the bug fix, so we're going a second round. 3251 seems happy with both ifort and gfortran, at least on my mac. as usual, I regret the bugs, but I can promise to give them top priority. sorry for the inconvenience. I should also mention a change in the opacity tables. We now have a separate set of tables for folks who'd like to use the Freedman low T tables -- |
138 messages has been excluded from this view by a project administrator.
