As far as I understand ADMMass uses metric and lapse thought ADMMacros and it calculates derivatives of the metric inside. All those GF looks fine. The problem appears when I use mesh refinement.
On Thu, Oct 4, 2012 at 3:00 PM, Ian Hinder ian.hinder@aei.mpg.de wrote:
On 4 Oct 2012, at 10:02, Petr Tsatsin wrote:
Hello, I recently started using ADMMass thorn and I found out the following problem. If I use it on the unigrid set up everything works fine, however if i use mesh refinement it gives correct values at t=0 but then all the values become something like this -3.50039744772644e+244. I was wondering if anybody experience such a problem? I used standard static_tov.par for testing purposes. Thank you.
I haven't used this thorn, but this looks like poison. i.e. variables which are initialised to a fixed large number in order to catch bugs. This indicates that something is accessing data which has not been initialised properly. Can you output the grid functions that are being used in the ADMMass computation and see if they are reasonable? Alternatively, you could compute their norm, which should also be strongly affected by this.
-- Ian Hinder http://numrel.aei.mpg.de/people/hinder