You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our current behavior is to pickle policies and value/q-functions so that they are pickled in their exact state, whether they are on gpu or not. This is bad because it forces users to use work-arounds to open torch pkled experiments on cpu only devices. A good example of this is when a user trains their policy on a server, but wants to see the policy in action, and they open it on their laptop, but their laptop doesn't have a gpu.
The text was updated successfully, but these errors were encountered:
Our current behavior is to pickle policies and value/q-functions so that they are pickled in their exact state, whether they are on gpu or not. This is bad because it forces users to use work-arounds to open torch pkled experiments on cpu only devices. A good example of this is when a user trains their policy on a server, but wants to see the policy in action, and they open it on their laptop, but their laptop doesn't have a gpu.
The text was updated successfully, but these errors were encountered: