From 9778e5c1298c8888214725f968badcbab516ea82 Mon Sep 17 00:00:00 2001 From: Benji Dial Date: Fri, 7 Jun 2024 01:11:49 -0400 Subject: redo evolver, add warrior serialization / deserialization to library --- readme.txt | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) (limited to 'readme.txt') diff --git a/readme.txt b/readme.txt index ffb5eac..fa275a1 100644 --- a/readme.txt +++ b/readme.txt @@ -41,8 +41,11 @@ Note that tabulator expects at least two processes (one head process and at leas === evolver === -The "evolver" program attempts to create warriors who are good against a particular other warrior via a process similar to genetic -evolution. It is highly experimental and does not always work. I may or may not attempt to improve it in the future. +The experimental "evolver" program attempts to create warriors who are good against a particular other +warrior via a process similar to genetic evolution. I may or may not attempt to improve it in the future. -To evolve a warrior against the included Epson warrior, with the outputs from each round stored in a directory named output, run - bin/evolver warriors/epson.red output +The evolver takes an arbitrary number of input warriors as "seeds". To evolve a warrior against Dwarf, using +all of the included warriors as seeds, and storing the outputs from each round in a directory named output, run + mpirun bin/evolver warriors/dwarf.red output warriors/*.red + +As with tabulator, evolver requires at least two processes, and you will have to oversubscribe if you only have one core. -- cgit v1.2.3