v4.0.0 parameter files

v4.0.0 parameter files

With '-p ' or 'params ' you can specify a file from where to load tuo parameters.

parameter file structure:

The first line applies to all following lines. Each command in the lines after the first gets executed. The optimized resulting deck from the previous line gets used as the input for the next

Example file "test.tuo":

sim 1000
// This is a comment
random
evaluate
flex

Then "./tuo deck1 deck2 -p test.tuo" will first execute 1000 random sims, then 1k evalute' sims and finally 1k flex sims.

Tips:

• use "timeout 0.5" for the sim to stop after 30 minutes and continue with the next (command-)line
• use "target 50" if you want the sim to stop at a score of 50 and continue with the next (command-)line
• you can use "-p " also in your file to get some bigger structure (and eventually bugs)

Future:

• A way to stop after given amount of iterations will be implemented.
• swaping the enemy deck/gauntlet might get added. (v4.0.1)
• Only considering a (random) partition of a gauntlet might get added.

Breaking:

• This version breaks previous behaviour where a command like "sim 100 debug 5 climb 4" would execute all three operations after each other. Now only the last operation is executed

This version hasn't been tested much so there might be some errors please report them or ideas

v4.0.1

flags 'deck' and 'enemy:deck' will overwrite previously set decks

v4.0.2

Add "@X@" dynamic parameters to parameter files.

With this variable you can reference previous results in a paramerter file. Example:

climb 1000
random
evaluate deck "Mission#142"
random enemy:deck "Mission#142" deck @1@

climb_forts 100 yfpool 3 yf "Phobos Station#2, Lightning Cannon#2,TC#2"
random enemy:deck "Mission#142" yf @4@ deck @3@ deck @0@

The fouth line uses the result of the first sim (random) as deck seed. Climb forts tries to find the best fortresses, it's result is used in the following line "yf @4@" and the original passed deck (@0@) is used as starting deck.

v4.1.0

Add "$X$" external parameters to parameter files.

With this variable you can pass parameters to the parameters file.

// 0.017*60 = 1 minute
timeout 0.017 anneal $1$ 100 0.01 random

deck @0@ 
deck @0@ 
deck @0@ 
deck @0@ 
deck @0@ 

genetic $2$ deck "@1@;@2@;@3@;@4@;@5@" timeout 0

Called via e.g.:

./tuo "Krellus,Obsidian Overlord" "TUTitan_Def" -p "params/train" 100 100000 -t 16 

$1$ is 100 and $2$ is 100000.

$0$ is the path name of the file after '-p' if you need that for some reason.

You can also use gauntlets/modes/orders/etc. as $X$ passed variable.

I hope this overall allows for enough customization. If someone has an interesting setup we could include that in the default tuo in e.g. a "params" folder or alternatively keep them stored in a separate forums post.