[Users] Carpet::baseextents, failed assertion

Scott Hawley scott.hawley at belmont.edu
Sun Jun 19 20:37:07 CDT 2011


I'm now able to get the code to run until it gives a complaint I've never seen:

-> The variable "ADMBASE::gxx" has only 1 active timelevels, which is not enough for boundary prolongation order 1

This is an initial data thorn.  I've never had to specify the number of timelevels.  I started going through ADMBase and declaring timelevels for various quantities, and also for ADMConstraints, but the list kept getting longer and the code would still not run to completion because of more such errors.

I noticed that such definitions do not typically appear in par files that come with the various thorns.

Is there a way around this?

-Scott

%Sent from my iPhone

On Jun 19, 2011, at 5:33 PM, "Erik Schnetter" <schnetter at cct.lsu.edu> wrote:

> On Sat, Jun 18, 2011 at 6:55 PM, Scott Hawley <scott.hawley at belmont.edu> wrote:
>> Hey.  I updated the section code which was using basextent.at() in an earlier version of Carpet, to the new syntax of baseextents.at(0).at()   (Marked with "HERE" in below snippet of code.)
>> 
>> The code compiles, but when it runs, there is a failed assertion.
>> It seems the only value which changes in the entire run is "istr".
>> 
>> Is there some other part of the code that also needs to change?
> 
> Scott
> 
> I don't know what other part of the code may need changing... The
> error message indicates that the lower and upper bounds of the bbox
> are not compatible, i.e. that their distance is not a multiple of the
> stride. It could be that the code is using a stride from the wrong
> refinement level.
> 
> -erik
> 
> -- 
> Erik Schnetter <schnetter at cct.lsu.edu>   http://www.cct.lsu.edu/~eschnett/
> 


More information about the Users mailing list