Changeset 1103 for framspy

Timestamp:

03/11/21 19:51:11 (4 years ago)

Author:

Maciej Komosinski

Message:

Added an example of setting a different expdef (experiment definition)

File:

• framspy/frams-test.py (modified) (2 diffs)

framspy/frams-test.py

@@ -3 +3 @@
 For an introduction to Framsticks, its usage and scripting, see https://www.youtube.com/playlist?list=PLkPlXm7pOPatTl3_Gecx8ZaCVGeH4UV1L
 For a list of available classes, objects, methods and fields, see http://www.framsticks.com/files/classdoc/
-For a number of examples of scripting, see the "scripts" directory in Framsticks distribution.
+For a number of examples of scripting, see the "scripts" directory in the Framsticks distribution.
 """
 
 import sys
+import json
 import frams
 
@@ -80 +81 @@
 frams.Simulator.stop()
 
+# changing expdef
+testgenotype = "XrrX[G][-1:80][|,-1:0.9]X[|,-2:-21]"
+evaluations = 100
+print("\nLet's change the experiment definition (expdef) and evaluate genotype '%s' %d times." % (testgenotype, evaluations))
+frams.Simulator.expdef = "standard-eval"
+frams.ExpProperties.evalcount = evaluations
+frams.ExpProperties.cr_v = 1
+frams.ExpProperties.evalplan = ":velocity,vertpos,fit_stdev,time"
+frams.GenePools[0].add(testgenotype)
+frams.ExpProperties.evalsavefile = ""  # no need to store results in a file - we will get evaluations directly from Genotype's "data" field
+frams.Simulator.init()
+frams.Simulator.start()
+step = frams.Simulator.step  # cache reference to avoid repeated lookup in the loop (just for performance)
+while frams.Simulator.running._int():  # standard-eval.expdef sets running to 0 when the evaluation is complete
+        step()
+for g in frams.GenePools[0]:  # loop over all genotypes, even though we know we added only one
+        serialized_dict = frams.String.serialize(g.data[frams.ExpProperties.evalsavedata._value()])
+        print(json.loads(serialized_dict._string()))
+
 # Note that implementing a complete expdef, especially a complex one, entirely in python may be inconvenient or impractical
 # because you do not have access to "event handlers" like you have in FramScript - onStep(), onBorn(), onDied(), onCollision() etc.,