From c08977d5c7b6e3282026f9223e155e750d01ea37 Mon Sep 17 00:00:00 2001 From: mlerik <baerenjesus@gmail.com> Date: Tue, 30 Jul 2019 20:39:38 +0000 Subject: [PATCH] Update intro_observationbuilder.rst --- docs/intro_observationbuilder.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/intro_observationbuilder.rst b/docs/intro_observationbuilder.rst index af1a9b96..494711ad 100644 --- a/docs/intro_observationbuilder.rst +++ b/docs/intro_observationbuilder.rst @@ -167,7 +167,7 @@ Any custom predictor can be passed to the observation builder and then be used t The observation is incomplete as it only contains information about potential conflicts and has no feature about the agent objectives. In addition to using your custom predictor you can also make your custom observation ready for rendering. (This can be done in a similar way for your predictor). -All you need to do in order to render your custom observation is to populate `self.env.dev_obs_dict[handle]` for every agent (all handles). (For the predictor use `self.env.dev_pred_dict[handle]`). +All you need to do in order to render your custom observation is to populate :code:`self.env.dev_obs_dict[handle]` for every agent (all handles). (For the predictor use :code:`self.env.dev_pred_dict[handle]`). .. _ShortestPathPredictorForRailEnv: https://gitlab.aicrowd.com/flatland/flatland/blob/master/flatland/envs/predictions.py#L81 .. _example: https://gitlab.aicrowd.com/flatland/flatland/blob/master/examples/custom_observation_example.py#L110 -- GitLab