NaNs in the AMR boundary closest to Pi symmetry boundary around 10M of evolution

Comments (4)

1. 

   Bruno Mundim reporter

   • removed comment

   Running the same parameter file without RotatingSymmetry180 works just fine: no NaNs observed until around 16M. Some strange interaction between RotatingSymmetry180 and Carpet mercurial version may be causing these NaNs.

   • 2011-05-23T16:39:47+00:00
2. 

   Bruno Mundim reporter

   • removed comment

   I changed VECTORISE_ALIGNED_ARRAYS to "no" according to Erik's comment below:

   "In the light of recent events I would like to point out again that you should not be using the configuration option VECTORISE_ALIGNED_ARRAYS. Some time ago, I accidentally committed (and later undid) a corresponding change to SimFactory. This option enables experimental changes in the Mercurial version of Carpet and is likely to lead to nans or other inconsistencies in your simulations. Please check your configuration options..."

   It didn't solve the problem, but I thought to keep it noted after this test. Note that the Carpet hg changeset was still an old one for this test: tip at 3287. I will update the tree for the next tests.

   • 2011-07-01T00:10:44+00:00
3. 

   Bruno Mundim reporter

   • changed status to resolved
   • removed comment

   On Sun Aug 14 I re-run this parameter file with Pi symmetry and the Carpet/hg and the simulation went on without any problem. I stopped it around 22M. So I am closing this ticket. Please re-open if necessary.

   • 2011-08-27T15:45:06+00:00
4. 

   Roland Haas

   • edited description
   • changed status to closed

   • 2019-02-21T19:54:09+00:00
5. Log in to comment