Hi, could someone apply the attached patch to EinsteinBase/TmunuBase? It just makes the parameters restricted, so that other thorns can easily use their values (e.g. Whisky checking if Tmunu has been stored in memory,...). I use it already in my version of Cactus/Whisky and I didn't encounter any problem.
Thanks, Bruno
Dr. Bruno Giacomazzo Department of Astronomy University of Maryland College Park MD 20742-2421 USA
Tel. : +1 301 405 0676 Fax : +1 301 314 9067 Tel. : +1 301 286 3809 (NASA/GSFC) Fax : +1 301 286 7230 (NASA/GSFC) email : bgiacoma@astro.umd.edu web: http://www.brunogiacomazzo.org
---------------------------------------------------------------------- There are only 10 types of people in the world: Those who understand binary, and those who don't ----------------------------------------------------------------------
Hello Bruno,
Hi, could someone apply the attached patch to EinsteinBase/TmunuBase? It just makes the parameters restricted, so that other thorns can easily use their values (e.g. Whisky checking if Tmunu has been stored in memory,...). I use it already in my version of Cactus/Whisky and I didn't encounter any problem.
Can be done yes. There is already a grid scalar TmunuBase::stress_energy_state which is set to non-zero if stress_energy_storage is true (in BaseGrid by TmunuBase_SetStressEnergyState).
You should already have access to it through Whisky inheriting from TmunuBase.
For the Cactus experts: what is the current preferred Cactus way of handling this? Parameter or grid scalar?
Yours, Roland
On Thu, Jun 09, 2011 at 09:56:32AM -0400, Roland Haas wrote:
Can be done yes. There is already a grid scalar TmunuBase::stress_energy_state which is set to non-zero if stress_energy_storage is true (in BaseGrid by TmunuBase_SetStressEnergyState).
You should already have access to it through Whisky inheriting from TmunuBase.
For the Cactus experts: what is the current preferred Cactus way of handling this? Parameter or grid scalar?
Roland is right: it would be best to use TmunuBase::stress_energy_state and not the parameter. This is a situation similar to, e.g., shift_state.
The main argument is that TmunuBase::stress_energy_state might change during the evolution, but the corresponding parameter might be set in a restart parameter file which would lead to problems while restarting.
Bruno: would using TmunuBase::stress_energy_state work for you as well?
Frank
users@lists.einsteintoolkit.org
-
Bruno Giacomazzo -
Frank Loeffler -
Roland Haas