RL: Collecting States (training data) in real-life. Must use fixed timestep?
$begingroup$
I am using a Reinforcement Learning agent to play a 3D game, but have trouble with collecting the "current and next state" pairs.
To decide what action to perform, the network must perform a forward pass.
It performs forward pass in time $t$, but in the meantime the game could have already skipped like 10 frames or more (a varying amount).
The situation is worsened if I run, say 100 games at once on the same computer.
I don't have the ability to stop the game at each frame to do forwardprop. Anyway it wouldn't be possible were I to train, say a real-life robot to walk.
Question:
Should I stick to a 'fixed timestep' approach, only asking to provide an action every 0.1 seconds? While it computes next action, I could pretend the network keeps outputting the most recent action for all the skipped frames. Good idea?
If that's the only option, then should I avoid at all costs situations where forward prop takes more than the 'fixed timestep'? (more than 0.1 sec in my case) So it's better to choose say, 0.2 seconds just to be safe.
Seems quite unreliable - is there a better way to do it?
Is there a paper that explores the alternatives? (I guess such a paper will be about real-life robot training)
reinforcement-learning
asked yesterday
KariKari
664422
$endgroup$
add a comment |
$begingroup$
I am using a Reinforcement Learning agent to play a 3D game, but have trouble with collecting the "current and next state" pairs.
To decide what action to perform, the network must perform a forward pass.
It performs forward pass in time $t$, but in the meantime the game could have already skipped like 10 frames or more (a varying amount).
The situation is worsened if I run, say 100 games at once on the same computer.
I don't have the ability to stop the game at each frame to do forwardprop. Anyway it wouldn't be possible were I to train, say a real-life robot to walk.
Question:
Should I stick to a 'fixed timestep' approach, only asking to provide an action every 0.1 seconds? While it computes next action, I could pretend the network keeps outputting the most recent action for all the skipped frames. Good idea?
If that's the only option, then should I avoid at all costs situations where forward prop takes more than the 'fixed timestep'? (more than 0.1 sec in my case) So it's better to choose say, 0.2 seconds just to be safe.
Seems quite unreliable - is there a better way to do it?
Is there a paper that explores the alternatives? (I guess such a paper will be about real-life robot training)
reinforcement-learning
asked yesterday
KariKari
664422
$endgroup$
add a comment |
$begingroup$
I am using a Reinforcement Learning agent to play a 3D game, but have trouble with collecting the "current and next state" pairs.
To decide what action to perform, the network must perform a forward pass.
It performs forward pass in time $t$, but in the meantime the game could have already skipped like 10 frames or more (a varying amount).
The situation is worsened if I run, say 100 games at once on the same computer.
I don't have the ability to stop the game at each frame to do forwardprop. Anyway it wouldn't be possible were I to train, say a real-life robot to walk.
Question:
Should I stick to a 'fixed timestep' approach, only asking to provide an action every 0.1 seconds? While it computes next action, I could pretend the network keeps outputting the most recent action for all the skipped frames. Good idea?
If that's the only option, then should I avoid at all costs situations where forward prop takes more than the 'fixed timestep'? (more than 0.1 sec in my case) So it's better to choose say, 0.2 seconds just to be safe.
Seems quite unreliable - is there a better way to do it?
Is there a paper that explores the alternatives? (I guess such a paper will be about real-life robot training)
reinforcement-learning
asked yesterday
KariKari
664422
$endgroup$
I am using a Reinforcement Learning agent to play a 3D game, but have trouble with collecting the "current and next state" pairs.
To decide what action to perform, the network must perform a forward pass.
It performs forward pass in time $t$, but in the meantime the game could have already skipped like 10 frames or more (a varying amount).
The situation is worsened if I run, say 100 games at once on the same computer.
I don't have the ability to stop the game at each frame to do forwardprop. Anyway it wouldn't be possible were I to train, say a real-life robot to walk.
Question:
Should I stick to a 'fixed timestep' approach, only asking to provide an action every 0.1 seconds? While it computes next action, I could pretend the network keeps outputting the most recent action for all the skipped frames. Good idea?
If that's the only option, then should I avoid at all costs situations where forward prop takes more than the 'fixed timestep'? (more than 0.1 sec in my case) So it's better to choose say, 0.2 seconds just to be safe.
Seems quite unreliable - is there a better way to do it?
Is there a paper that explores the alternatives? (I guess such a paper will be about real-life robot training)
reinforcement-learning
reinforcement-learning
asked yesterday
KariKari
664422
asked yesterday
KariKari
664422
edited yesterday
Kari
asked yesterday
KariKari
664422
asked yesterday
KariKari
664422
asked yesterday
KariKari
664422
664422
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
return StackExchange.using("mathjaxEditing", function () {
StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix) {
StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["$", "$"], ["\\(","\\)"]]);
});
});
}, "mathjax-editing");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "557"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdatascience.stackexchange.com%2fquestions%2f47449%2frl-collecting-states-training-data-in-real-life-must-use-fixed-timestep%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Data Science Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
Use MathJax to format equations. MathJax reference.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdatascience.stackexchange.com%2fquestions%2f47449%2frl-collecting-states-training-data-in-real-life-must-use-fixed-timestep%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
