From 5220c8b7dcbbf73e1396c6325b3f1787b402f4f9 Mon Sep 17 00:00:00 2001 From: Daniel Toyama Date: Tue, 11 Jul 2023 07:57:10 -0700 Subject: [PATCH] Remove references to `extras_spec` in `tasks_guide.md`. `Task.extras_spec` is not a reliable mechanism since tasks can "lie" about their extras (or it can also be incomplete and/or just wrong). It also doesn't play well with dynamic tasks that change shape and/or data types during their lifetime, which is especially common in continual learning settings. The field will eventually be removed from the `Task` protobuf message. PiperOrigin-RevId: 547189863 --- docs/tasks_guide.md | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/docs/tasks_guide.md b/docs/tasks_guide.md index bad5072..0cb13bd 100644 --- a/docs/tasks_guide.md +++ b/docs/tasks_guide.md @@ -69,9 +69,6 @@ how to put these into code. of the form `reward: 1.0`, then the task will capture this info using the regexp `^[Rr]eward: ([-+]?[0-9]*\\.?[0-9]*)$`. -* `extras_spec`: Determines the type and shape of extras exposed by the task. - Extras are usually parsed from logcat messages. -
@@ -169,16 +166,6 @@ log_parsing_config: { json_extra: "^json_extra: (?P.*)$" } } - -# Capture expected shape and type of extras -extras_spec: [ - # Grid representing the state of the board. - { name: "grid" shape: [4, 4], dtype: INT32}, - # Direction of the last swipe action that prompted that change in the state. - # 0: up, 1: right, 2: down, 3: left - { name: "direction" shape: [1], dtype: INT32 } -] - ```