Difference between revisions of "Fixing examples"

From Einstein Toolkit Documentation
Jump to: navigation, search
(14-Aug-2015)
(14-Aug-2015)
Line 29: Line 29:
  
 
{|
 
{|
 +
! Status indicator
 +
! Description
 +
! No. of examples
 +
|-
 
| Done
 
| Done
 
| Run ended with "Done."  (TODO: eventually check that these are actually "good" somehow)
 
| Run ended with "Done."  (TODO: eventually check that these are actually "good" somehow)

Revision as of 03:09, 14 August 2015

Project to fix the Einstein Toolkit example parameter files

See #641.

13-Aug-2015

(Ian)

I have submitted all arrangements/*/*/par/*.par files on 12 cores on datura, to get a first estimate of what happens.

  • There are 228 such files (in my current trunk checkout)
  • 146 of them (64%) ran and output the line "Done."
  • 27 (12%) of them took more than a few minutes to run (maybe because they are swapping due to needing more nodes)
  • 88 (34%) failed due to needing thorns which were not available.

So 228 - 88 - 27 = -33 probably failed with some sort of fatal error. Something is wrong there. Need to check.

14-Aug-2015

The following tests take a very long time:

  • jpeg_amr
  • jpeg
  • http

The current status of the examples is listed at Einstein Toolkit Examples Status. This is regenerated manually at the moment.

Key:

Status indicator Description No. of examples
Done Run ended with "Done." (TODO: eventually check that these are actually "good" somehow) 81
ExternalThorns Failed due to depending on non-ET thorns 88
Assertion Assertion failure 5
CCTK_Abort Warning level 0 43
FailedParamCheck Failed Cactus parameter check 3
Signal11 Segmentation fault 4
Signal9 SIGKILL; probably out of memory, need to run on more nodes? 1
Unknown Not categorised, but also includes runs which ran for a long time and were terminated manually for now 1