Difference between revisions of "Fixing examples"

From Einstein Toolkit Documentation
Jump to: navigation, search
(14-Aug-2015)
Line 28: Line 28:
 
Key:
 
Key:
  
* Assertion: Assertion failure
+
{|
* CCTK_Abort: Warning level 0
+
| Assertion
* Done: Run ended with "Done."  (TODO: eventually check that these are actually "good" somehow)
+
| Assertion failure
* ExternalThorns: Failed due to depending on non-ET thorns
+
|-
* FailedParamCheck: Failed Cactus parameter check
+
| CCTK_Abort
* Signal11: Segmentation fault
+
| Warning level 0
* Signal9: SIGKILL; probably out of memory, need to run on more nodes?
+
|-
* Unknown: Not categorised, but also includes runs which ran for a long time and were terminated manually for now
+
| Done
 +
| Run ended with "Done."  (TODO: eventually check that these are actually "good" somehow)
 +
|-
 +
| ExternalThorns
 +
| Failed due to depending on non-ET thorns
 +
|-
 +
| FailedParamCheck
 +
| Failed Cactus parameter check
 +
|-
 +
| Signal11
 +
| Segmentation fault
 +
|-
 +
| Signal9
 +
| SIGKILL; probably out of memory, need to run on more nodes?
 +
|-
 +
| Unknown
 +
| Not categorised, but also includes runs which ran for a long time and were terminated manually for now
 +
|}

Revision as of 02:55, 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:

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