[mesa-users] sacred variables

[Ehsan Moravveji]

Thanks Bill for your reply.
Actually, I use the loop that I sent simultaneously in all the following subroutines, and still do not get the effect I desire:
- s% other_mlt
- s% other_D_mix
- extras_check_model
- extras_finish_step

I expect, e.g. gradL(i) == grada(i) for those cells, i, that I prescribe, which does not happen afterwards. I would like to enforce convective mixing in some layers on top of the core for some "experiments".
I think that a hook like "other_gradients" could be useful.
I will see where in the code these can be placed/called.

Regards
Ehsan.


On Jun 15, 2014, at 8:49 PM, Bill Paxton wrote:

> 
> 
> 
> On Jun 15, 2014, at 11:30 AM, Ehsan Moravveji wrote:
> 
>> Hello Bill,
>> I notice that in my run_star_extras, whatever value I assign to the following variables, and locally change them in some zones, the change is not applied, and the run_star_extras does not listen to me.
>> 
>>           do i = itop, ibot
>>              s% D_mix_non_rotation(i) = max_D
>>              s% gradL_composition_term(i) = 0d0
>>              s% adjust_mlt_gradT_fraction(i) = 1d0
>>              s% gradT(i) = s% grada_at_face(i)
>>              s% gradL(i) = s% grada(i)
>>              s% mixing_type(i) = convective_mixing
>>           enddo
>> 
>> Is there a way that a user would apply his desired changes to these variables?
>> Now, I use v. 6208. 
>> 
>> Kind regards
>> Ehsan.
>> 
> 
> 
> You haven't given enough information.   In which routine in run_star_extras are you making the changes?  What do you mean when you say that "run_star_extras does not listen"?    What do you think is going to happen?  
> 
> Most of those variables are calculated at the start of a step, but gradT is recalculated on each newton iteration.   If you want to have your code called on each newton iteration, then you should use the "other_mlt" hook.    If you are willing to skip setting gradT at each iteration, you can change the others at the start of the step by use the "other_D_mix" hook and make consistent changes to all of the following: D_mix, cdc, conv_vel, and mixing_type.  Note that you do not set D_mix_non_rotation in this case; the code sets it to D_mix after the place where it optionally calls your other_D_mix hook routine.
> 
> btw: I've found that making changes to various variables in mesa without understanding how they are used in the code seldom works!   so it would be a good idea to grep for each of the variables in star/private and read-read-read until it is clear when they need to be set in order to take effect.  hopefully there will be a hook that lets your code be called from the right place at the right time; if not, send a message to mesa-users and something can probably be added so you can do what you want.
> 
> -Bill
> 
> 
> 
> ------------------------------------------------------------------------------
> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
> Find What Matters Most in Your Big Data with HPCC Systems
> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
> Leverages Graph Analysis for Fast Processing & Easy Data Exploration
> http://p.sf.net/sfu/hpccsystems
> _______________________________________________
> 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/20140615/a6c2643d/attachment.html>