Hi Frank,

Thanks for your feedback.

> You use the ADMBase variables, right?

My ADMBaseMcLachlanTester thorn (math.wvu.edu/~zetienne/ADMBaseMcLachlanTester.tar.gz) reproduces this issue, and uses *only* ADMBase::alp as input. I would encourage everyone interested to take a look at this thorn, as

1) there's nothing complicated about the ADMBaseMcLachlanTester thorn at all (67 lines of code, including ccl files, includes, and whitespace)

2) the included parfiles run on a single desktop computer needing only 5GB of RAM

3) it takes only ~15 mins to evolve to timestep 192

> Could you output the variables your analysis depends on, and see if the nan values come from there?

Absolutely! I just performed a run with ADMBaseMcLachlanTester, setting myadmbaselapse to alp every 64 iterations, and confirmed that there are *no* undefined (nan) values in the (IOASCII 2D output of) ADMBase::alp (at any iteration, upto and including iteration 192), while again, there are a very large number of undefined values in myadmbaselapse at iteration 192...

So myadmbaselapse is not undefined because ADMBase::alp is undefined.

-Zach

* * *
Zachariah Etienne
Assistant Professor of Mathematics

West Virginia University

On Tue, Jun 2, 2015 at 11:22 AM, Frank Loeffler <knarf@cct.lsu.edu> wrote:

On Tue, Jun 02, 2015 at 11:11:15AM -0400, Zach Etienne wrote:
> myadmbaselapse has only one timelevel, and tags are set
> 'InterpNumTimelevels=1 prolongation="none" Checkpoint="no"'. Thus
> prolongation should be disabled on myadmbaselapse...

You use the ADMBase variables, right? They should, by default, be
prolongated, and I don't see a parameter that would disable that in your
parfile. Could you output the variables your analysis depends on, and
see if the nan values come from there?
It does, like Ian suggested, look like something you depend on isn't
properly prolonged by regridding.

Frank