<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Thanks Roland,</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">2021년 3월 12일 (금) 오전 12:03, Roland Haas <<a href="mailto:rhaas@illinois.edu">rhaas@illinois.edu</a>>님이 작성:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello Hee Il,<br>
<br>
> I have encountered a bug in using HydroBase::temperature_evolution_method.<br>
> If it is given explicitly by taking its default value "GRHydro", my<br>
> runs crashed while reading a Lorene data. But if it's not given in the<br>
> parameter file, it run smoothly but the results are the same with the case<br>
> of taking "none".<br>
The default value for HydroBase::temperature_evolution_method is "none"<br>
(see<br>
<a href="http://einsteintoolkit.org/thornguide/EinsteinBase/HydroBase/documentation.html#TBL-15-7-1" rel="noreferrer" target="_blank">http://einsteintoolkit.org/thornguide/EinsteinBase/HydroBase/documentation.html#TBL-15-7-1</a>) so not setting it explicitly is identical to setting it to "none".<br></blockquote><div><br></div><div> Yes, I was mistaken. I confirmed that "none" is the default value.</div><div> [khi@hygra GRHydro]$ ~/ET/Turing/exe/cactus_bns_turing -o HydroBase::temperature_evolution_method</div><div>Parameter: HydroBase::temperature_evolution_method, HydroBase::temperature_evolution_method</div><div>Description: "Evolution method for temperature"</div><div>Type: KEYWORD</div><div>Default: none</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
> I found this bug when I was testing Hybrid EOS. I've tried to realize pure<br>
> Polytrope (or Ideal_Fluid) by using the piecewise Hybrid EOS interface. But<br>
> the results are showing around 10% more variations in rhomax compared to<br>
> the pure Polytrope/Ideal_Fluid cases.<br>
Can you provide the full log output (and ideally a parfile to reproduce<br>
the issue) for stdout and stderr as well as any backtract.X.txt files<br>
created?<br></blockquote><div><br></div><div> I attached the log file and the parfile. No backtrace.X.txt files were created and the core dump contains no infos other than "No Stack".</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
If it crashes with a SEGFAULT or similar that would indeed be a bug.<br>
Note that most of the LORENE data has been used with equations of<br>
state that do not use temperature (usually tabulated ones only) so if<br>
you are using one of LORENE's sample data sets and set this parameter<br>
then even if the code apparently succeeds the evolution may not be<br>
correct or what you expect. </blockquote><div><br></div><div> I agree. My main issue might not be related to the crash. Due to the confusion mentioned above, I've tried to turn off keytemp in order to see if I get better results having no extra pulsations. Actually there's no difference but it only increased the chance of crashes. What I get at the moment is extra >10% pulsations if I use Hybrid EOS (green line) compared with the redline (Ideal_Fluid). Similar pulsations were found for the case of SLy as well. I've used both Lorene and Lorene2 IDs (by using either table and piecewised poly eos). Would you check the parfile to see if I'm making a simple mistake?</div><div><br></div><div>Yours,</div><div><br></div><div>Hee Il </div></div></div></div></div></div>