Answers.Body: <p>There is a strong relationship between a value function and a return. Namely that a value function calculates the <em>expected</em> return from being in a certain state, or taking a specific action in a specific state. A value function is not a "return function", it is an "expected return function" and that is an important difference.</p>
  
  <p>A return is a measured value (or a random variable, when discussed in the abstract) representing the actual (discounted) sum of rewards seen following a specific state or state/action pair.</p>
  
  <p>Typically there is no need to express an individual return as a "return function", although you may find many formulae in RL for sampling or estimating specific return values in order to calculate targets or errors for the value function.</p>
  
  <blockquote>
    <p>A return (or cumulative reward) function effectively adds up the rewards from the current state to the goal state. This implies it's model-based.</p>
  </blockquote>
  
  <p>If you have a simple MDP, already accurately modelled, where you can calculate expected return directly from that model, then, yes, in theory, that would be a value function. However, this could be more computationally intensive to resolve than dynamic programming (e.g. Policy Iteration or Value Iteration), and in many cases you don't have any such model, but can still apply RL approaches to learn a value function from experience.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-03-18T10:45:28.473Z
Answers.Text: so in DP, return function must use data from existing trials only to calculate value for a state signal? the value function can estimate rewards for actions not yet taken on explored states?
Answers.UserDisplayName: user3168961
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-03-18T12:39:43.323Z
Answers.Text: @user3168961: Yes, sort of. There are individual returns, which you can experience or sample. In practice, you may use some kind of function for that, which may blur the line between expected and actual return when bootstrapping as in value iteration or TD learning etc. Then there are expected returns, which are learned by the value functions.
Answers.UserDisplayName: Neil Slater
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-03-17T21:34:58.353Z
Answers.LastActivityDate: 2019-02-15T01:57:56.220Z
Answers.LastEditDate: 2019-02-15T01:57:56.220Z
Answers.UserDisplayName: Neil Slater
Body: <p>I've seen numerous mathematical explanations of reward, value functions <span class="math-container">$V(s)$</span>, and return functions. The reward provides an immediate return for being in a specific state. The better the reward, the better the state. </p>
  
  <p>As I understand it, it can be better to be in a low-reward state sometimes because we can accumulate more long term, which is where the expected return function comes in. An expected return, return or cumulative reward function effectively adds up the rewards from the current state to the goal state. This implies it's model-based. However, it seems a value function does exactly the same.</p>
  
  <p>Is a value function a return function? Or are they different?</p>
  
Tags: <reinforcement-learning><comparison><rewards><value-functions><return>
Title: What is the difference between expected return and value function?
UserDisplayName: user3168961
ThreadText: # What is the difference between expected return and value function?
  
  (Asked by: username_0 on 2018-03-17)
  
  I've seen numerous mathematical explanations of reward, value functions $V(s)$, and return functions. The reward provides an immediate return for being in a specific state. The better the reward, the better the state.
  
  As I understand it, it can be better to be in a low-reward state sometimes because we can accumulate more long term, which is where the expected return function comes in. An expected return, return or cumulative reward function effectively adds up the rewards from the current state to the goal state. This implies it's model-based. However, it seems a value function does exactly the same.
  
  Is a value function a return function? Or are they different?
  
  **Tags:** reinforcement-learning, comparison, rewards, value-functions, return
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-03-17. Score: 7 | Accepted answer
  
  There is a strong relationship between a value function and a return. Namely that a value function calculates the *expected* return from being in a certain state, or taking a specific action in a specific state. A value function is not a "return function", it is an "expected return function" and that is an important difference.
  
  A return is a measured value (or a random variable, when discussed in the abstract) representing the actual (discounted) sum of rewards seen following a specific state or state/action pair.
  
  Typically there is no need to express an individual return as a "return function", although you may find many formulae in RL for sampling or estimating specific return values in order to calculate targets or errors for the value function.
  
  > A return (or cumulative reward) function effectively adds up the rewards from the current state to the goal state. This implies it's model-based.
  
  If you have a simple MDP, already accurately modelled, where you can calculate expected return directly from that model, then, yes, in theory, that would be a value function. However, this could be more computationally intensive to resolve than dynamic programming (e.g. Policy Iteration or Value Iteration), and in many cases you don't have any such model, but can still apply RL approaches to learn a value function from experience.
  
  > **Comments:**
  > **username_0**: so in DP, return function must use data from existing trials only to calculate value for a state signal? the value function can estimate rewards for actions not yet taken on explored states?  
  > **username_1**: @user3168961: Yes, sort of. There are individual returns, which you can experience or sample. In practice, you may use some kind of function for that, which may blur the line between expected and actual return when bootstrapping as in value iteration or TD learning etc. Then there are expected returns, which are learned by the value functions.  
  
  ---
  
  