Fixing examples - Revision history

Knarf at 05:40, 14 August 2015

2015-08-14T05:40:32Z

2015-08-14T03:37:14Z

‎13-Aug-2015

2015-08-14T03:12:51Z

‎14-Aug-2015

2015-08-14T03:10:01Z

‎14-Aug-2015

2015-08-14T03:09:25Z

‎14-Aug-2015

2015-08-14T03:08:17Z

‎14-Aug-2015

2015-08-14T02:57:14Z

‎14-Aug-2015

2015-08-14T02:55:03Z

‎14-Aug-2015

2015-08-14T02:40:04Z

2015-08-14T01:30:40Z

‎Project to fix the Einstein Toolkit example parameter files

@@ Line 15: / Line 15: @@
 * jpeg_amr
 * jpeg
-* http
+* http -> is supposed to take long. It starts an (empty) simulation and pauses it for user interaction at the web interface)
 The current status of the examples is listed at [http://damiana2.aei.mpg.de/~ianhin/ETExamples/examples.xml Einstein Toolkit Examples Status].  This is regenerated manually at the moment.

←Older revision		Revision as of 03:37, 14 August 2015
Line 8:		Line 8:

	I have submitted all arrangements///par/*.par files on 12 cores on datura, to get a first estimate of what happens.		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 ===		=== 14-Aug-2015 ===

←Older revision		Revision as of 03:12, 14 August 2015
Line 65:		Line 65:
	\| 1		\| 1
	\|}		\|}
		+
		+	Proposals:
		+	* Make sure that the examples all run in a resonable amount of time, e.g. less than one hour. Most of them are much quicker than this. For the long-running ones, see if it actually is necessary to have them take so long. Ideally they should run in a few seconds, unless there is a good reason.
		+	* It would be good to have a list of the examples which can be run with just the ET on the web page, automatically generated, so that people can use these as the master list. We could also add a comment to the parfiles indicating whether they can be run using just the the ET.
		+	* Fix the errors

@@ Line 28: / Line 28: @@
 Key:
-{|
+{| class="wikitable" style="text-align:left;"
 ! Status indicator
 ! Description

@@ Line 29: / Line 29: @@
 {|
 | Done
 | Run ended with "Done."  (TODO: eventually check that these are actually "good" somehow)

@@ Line 31: / Line 31: @@
 | Done
 | Run ended with "Done."  (TODO: eventually check that these are actually "good" somehow)
 |-
 | ExternalThorns
 | Failed due to depending on non-ET thorns
 |-
 | Assertion
 | Assertion failure
 |-
 | CCTK_Abort
 | Warning level 0
 |-
 | 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
 |}

@@ Line 28: / Line 28: @@
 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

←Older revision		Revision as of 02:40, 14 August 2015
Line 15:		Line 15:

	So 228 - 88 - 27 = -33 probably failed with some sort of fatal error. Something is wrong there. Need to check.		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 [http://damiana2.aei.mpg.de/~ianhin/ETExamples/examples.xml 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

@@ Line 1: / Line 1: @@
 == Project to fix the Einstein Toolkit example parameter files ==
-See [https://trac.einsteintoolkit.org/ticket/641].
+See [https://trac.einsteintoolkit.org/ticket/641 #641].
--Aug-2015, Ian: I have submitted all arrangements/*/*/par/*.par files on 12 cores on datura, to get a first estimate of what happens.
+=== 13-Aug-2015 ===
 * There are 228 such files (in my current trunk checkout)