The table name(s) where samples will be written to.
An integer. max_sequence_length used
to write to the replay buffer tables. This defines the size of the
internal buffer controlling the upper limit of the number of timesteps
which can be referenced in a single prioritized item. Note that this is
the maximum number of trajectories across all the cached episodes that
you are writing into the replay buffer (e.g. number_of_episodes).
max_sequence_length is not a limit of how many timesteps or
items that can be inserted into the replay buffer. Note that,
since max_sequence_length controls the size of internal buffer, it is
suggested not to set this value to a very large number. If the number of
steps in an episode is more than max_sequence_length, only items up to
max_sequence_length is written into the table.
Initial priority for the table.
If False (default) and an episode length is
greater than max_sequence_length, a ValueError is raised. If set to
True, the episodes with length more than max_sequence_length do not
cause a ValueError. These episodes are bypassed (will NOT be written
into the replay buffer) and an error message is shown to the user.
Note that in this case (bypass_partial_episodes=True), the steps for
episodes with length more than max_sequence_length are wasted and
thrown away. This decision is made to guarantee that the replay buffer
always has FULL episodes. Note that, max_sequence_length is just an