<div dir="ltr"><div class="gmail_extra"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Hi Klaus,</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">As I understand it, if the runtime parameter eos_singleSpeciesZ is not set, then it will have a value of 1. I could set eos_singleSpeciesZ, but since it isn't used in the equation of state for the single species gamma EOS (as I found out from earlier e-mail exchanges with people in this group), I can just as well absorb it into the diff_eleFlCoef runtime parameter, with is supposed to limit the conductive flux.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">I think the flux limiter is perfectly appropriate for the 1T case under the assumption that there is fast equilibration of the electron and ion temperatures. There have been many calculations of cloud evaporation and, as far as I can recall, they all make that assumption. And since Cowie & McKee (1977), it has been recognized that thermal conduction "saturates" when it reaches a level at which the heat flux reaches the maximum that can be carried by the electrons. I'm trying to be careful about how I set the diff_eleFlCoef so as to match the assumptions used in various of the 1D steady flow calculations of cloud evaporation so as to be able to compare the results.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Regards,</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Jon</div><br><div class="gmail_quote">On Sat, Oct 3, 2015 at 1:00 PM, <span dir="ltr"><<a href="mailto:flash-users-request@flash.uchicago.edu" target="_blank">flash-users-request@flash.uchicago.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":14o" class="a3s" style="overflow:hidden">From: Klaus Weide <<a href="mailto:klaus@flash.uchicago.edu">klaus@flash.uchicago.edu</a>><br>To: John ZuHone <<a href="mailto:jzuhone@space.mit.edu">jzuhone@space.mit.edu</a>><br>Cc: flash-users <<a href="mailto:flash-users@flash.uchicago.edu">flash-users@flash.uchicago.edu</a>><br>Date: Fri, 2 Oct 2015 15:59:23 -0500 (CDT)<br>Subject: Re: [FLASH-USERS] value of Ye for single species runs<br>On Fri, 2 Oct 2015, John ZuHone wrote:<br>
<br>
> Just for reference, Jon and I have been discussing this off-list. The<br>
> single-species gamma-law EOS only has a stub for this subroutine.<br>
<br>
Hi John,<br>
<br>
That's not correct if with "this routine" you mean Eos_getAbarZbar.F90.<br>
The implementation of this routine (shared by the single-species gamma-law<br>
EOS implementation and other EOS implementations) is in<br>
physics/Eos/EosMain/Eos_getAbarZbar.F90 .<br>
There are various #ifdef's, but in Jon's case as I understand it (no<br>
FLASH_MULTISPECIES defined, and SUMY_MSCALAR and YE_MSCALAR not both<br>
defined) the returned values should simply be what is set by the<br>
following lines:<br>
if (present(abar)) abar = eos_singleSpeciesA<br>
if (present(zbar)) zbar = eos_singleSpeciesZ<br>
if (present(sumY)) sumY = 1.0/eos_singleSpeciesA<br>
if (present(Ye)) Ye = eos_singleSpeciesZ/eos_singleSpeciesA<br>
<br>
> I suggested copying the Eos_getAbarZbar stub to the simulation directory<br>
> and changing it to set the quantities to whatever he needs,<br>
<br>
That should also work, but why not just set runtime parameters<br>
eos_singleSpeciesZ / eos_singleSpeciesA appropriately.<br>
<br>
> but as I am<br>
> not familiar with this particular diffusion module I think someone with<br>
> more knowledge should comment if this is the right way to go.<br>
<br>
The source file physics/Diffuse/DiffuseMain/Unsplit/diff_advanceTherm.F90<br>
has mainly been developed for 3T situations; it is also supposed to work<br>
in a 1T context, but I don't know how appropriate the flux limiter is in<br>
that case.<br>
<br>
Klaus<br></div></blockquote></div><div><br></div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><br></div></div></div></div>
</div></div>