We enabled a new, much scalable implementation of the bboxset class in Carpet. This class describes sets of "bounding boxes", i.e. the locations and shapes of the components of Carpet's grids. (This new implementation requires C++11 features, and is thus only available by default if the C++ compiler supports the C++11 standard.)
As it turns out, the new class numbers these components differently than the old code. This numbering scheme is ultimately arbitrary; if there are two refined regions, then it does not matter for physics which one is labelled #0 and which one is labelled #1. However, since the old and the new code differ, some ASCII output will now differ. In the Einstein Toolkit test cases, this is triggered by the test ml-gw1d-small-amr of PeriodicCarpet. Inspection shows that, apart from this re-labelling, the test output is identical.
The new bboxset code has a defined ordering of the bboxes; they are ordered lexicographically by their upper left corner. (This is implemented in the "less" functions in bbox.hh and vect.hh, following STL conventions.) The old code used no particular ordering, although the ordering was guaranteed to remain the same between runs.
I suggest to ignore the test case failures caused by this transition, and to update this (and potentially other) test cases.
I plan to update the old bboxset code to explicitly sort bboxes in the same order.
-erik
-- Erik Schnetter schnetter@gmail.com http://www.perimeterinstitute.ca/personal/eschnetter/
My email is as private as my paper mail. I therefore support encrypting and signing email messages. Get my PGP key from https://sks-keyservers.net.