BUG: vmap is applied on variables which are not arguments of function

[timmens]

LCM Version: af6661e

Example

A state variable that only influences the next period. In this case, the last period utility compute_ccv function does not depend on this state variable, since the next_-functions are not included. But, since it is a state variable, LCM tries to vmap over it, resulting in an error.

Potential Solution

For each period compare variables over which we want to vmap, and variables that are in the signature of the functions we wish to vmap over. Then update the state space and space info accordingly.

Current Fix

Add all state variables as arguments to the utility function, no matter whether they are actually used or not.