[mesa-users] Turning off neutrino types

[Bill Paxton]

Hi Shane,

This Fortran Primer by Marc Spiegelman might be useful.



-Bill





On Mar 20, 2013, at 6:29 PM, Shane Frewen wrote:

> Hi Josiah and Bill,
> 
> Thanks for your quick reply. I do have that flag set, so my routine is being used. Unfortunately, when I try to change the "flags" variable within it, I get an error. From what I can tell, since the routine expects "flags" to be an input I can't modify it. I've tried using 
> 
>          s% flags = .false.
> 
> and
> 
>          s% flags(pair_neu_type) = .false. 
> 
> (for a single type), both of which give me errors as "flags" isn't recognized by the star pointer. I've also tried changing the intent of "flags" to inout at the beginning of the subroutine: 
>  
>          logical, intent(inout) :: flags(num_neu_types)
> 
>  but this also gives an error since the intent disagrees between my_other_neu and other_neu. Leaving the intent(in), I get an error when I try to change "flags" as well. 
> 
> The variable is defined in micro.f, but when I changed it and ran "clean" and "mk" in mesa/star it didn't change the behavior of my work directory.
> 
> 
> 
> 
> On Wed, Mar 20, 2013 at 6:19 PM, Bill Paxton <paxton at kitp.ucsb.edu> wrote:
> Hi Shane,
> 
> The flag to enable your "other" routine can be set from your inlist.
> 
>          use_other_neu = .true.
> 
> Does that help?
> 
> -Bill
> 
> 
> 
> 
> On Mar 20, 2013, at 6:13 PM, Shane Frewen wrote:
> 
> > Hello all,
> >
> > I'm attempting to look at the effect of various neutrino cooling mechanisms on stellar evolution. With some help from Josiah I tried to adjust the "flags" variable, which gives you access to which mechanisms are on or off.  I wrote a my_other_neu subroutine within run_star_extras, pointing other_neu to it, and varying flags within there. However, there seems to be no way to change the flags variable outside of micro.f, since the intent is input in the other programs. Is there anyway to change this variable (for each mechanism), or must it be done directly in the micro.f program? If the latter is the case, what is the best way to recompile the micro.f within MESA without recompiling everything?
> >
> > Sorry if my description is poor- I'm new to both MESA and Fortran.
> >
> > Thank you very much for your help,
> >   Shane Frewen
> > ------------------------------------------------------------------------------
> > Everyone hates slow websites. So do we.
> > Make your web apps faster with AppDynamics
> > Download AppDynamics Lite for free today:
> > http://p.sf.net/sfu/appdyn_d2d_mar_______________________________________________
> > mesa-users mailing list
> > mesa-users at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/mesa-users
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20130320/06f9028a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Fortran.pdf
Type: application/pdf
Size: 61992 bytes
Desc: not available
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20130320/06f9028a/attachment.pdf>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20130320/06f9028a/attachment-0001.html>