Requesting more informative field names for SharedTrajectory

[Sid-Bhatia-0]

Inside SharedTrajectory, how about having a field name like window or range in place of meta? Something that provides more information about the purpose of the field.

Similarly in place of x, maybe we could use something like buffer?

[Sid-Bhatia-0]

And if I understand it correctly, then traces in a Trajectory plays a role similar to x in a SharedTrajectory. Maybe we could keep the same for those fields. traces, or buffer or something else.

Personally, I like the name buffer, since it connects well to the concept of a replay buffer. And one of the primary uses of trajectories is to be used as a replay buffer. 😄

[findmyway]

yes, that would be better 发自我的iPhone

…

------------------ Original ------------------ From: Sid-Bhatia-0 <notifications@github.com&gt; Date: Wed,Oct 28,2020 1:28 AM To: JuliaReinforcementLearning/ReinforcementLearningCore.jl <ReinforcementLearningCore.jl@noreply.github.com&gt; Cc: Subscribed <subscribed@noreply.github.com&gt; Subject: Re: [JuliaReinforcementLearning/ReinforcementLearningCore.jl] Requesting more informative field names for SharedTrajectory (#150) Inside SharedTrajectory, how about having a field name like window or range in place of meta? Something that provides more information about the purpose of the field. Similarly in place of x, maybe we could use something like buffer? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[findmyway]

SharedTrajectory is now removed to make the code easier to understand.