From e5ac7e0b05ebf0ef84e47f1cc601434552ed376c Mon Sep 17 00:00:00 2001 From: Dominik Roth Date: Tue, 25 Oct 2022 15:02:33 +0200 Subject: [PATCH] README: Documentation for ConfigDefined Example --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index af0a8ed..79331ec 100644 --- a/README.md +++ b/README.md @@ -21,7 +21,7 @@ Contains the ColumbusEnv. There exist two ways to implement new envs: - Subclassing ColumbusEnv and expanding _init_ and overriding _setup_. -- Using the ColumbusConfigDefined with a desired configuration. This makes configuring ColumbusEnvs via ClusterWorks2-configs possible. (See ColumbusConfigDefinedExample.md for an example of how the parameters are supposed to look like (uses yaml format), I don't have time to write a better documentation right now...) +- Using the ColumbusConfigDefined with a desired configuration. This makes configuring ColumbusEnvs via ClusterWorks2-configs possible. (See ColumbusConfigDefinedExample.yaml for an example of how the parameters are supposed to look like (uses yaml format), I don't have time to write a better documentation right now...) (To test this run 'python humanPlayer.py', select 5, give path to ColumbusConfigDefinedExample.yaml, select 0) ##### Some caveats / infos