[Users] bug or feature?
ian.hinder at aei.mpg.de
Fri Sep 11 04:02:07 CDT 2015
On 10 Sep 2015, at 15:10, Comer Duncan <comer.duncan at gmail.com> wrote:
> Sorry! I have attached the .err file and the larger .out file is http://pastebin.com/JLPRb2sw and I hope this helps.
In the parameter file, you have set
Carpet::prolongation_order_time = 2
and Carpet is simply checking the number of timelevels for all variables that have prolongation enabled, and aborting because there are some such variables with only one timelevel (3 are required).
In your case, since you are only using prolongation for multigrid, I don't think that time interpolation is required, and additional timelevels should not be necessary. I think it would be better if Carpet only checked this if time interpolation actually happened, i.e. during the run.
There are many aspects of timelevel handling in Cactus/Carpet which are not ideal; there was some recent work on this, but it's not quite there yet.
The first thing to try is setting
Carpet::prolongation_order_time = 0
This seems like the cleanest solution, in the absence of Carpet relaxing its too-strict checks, at least for a parameter file which just constructs initial data.
If this doesn't work (something else might go wrong), take a look in the param.ccl file of CT_BrillAnalytic. You should find a "timelevels" parameter which you can try setting to 3.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users