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
The current implementation of ActorCriticBase makes it a bit trick to have custom actor and critic networks that have shared layers. This is because the instantiation of the networks happen in the ActorCriticBase class. You can probably get around it but it's very tricky. I'd recommend you pass in the actor/critic objects rather than the class types and let the user initialize them.
The text was updated successfully, but these errors were encountered:
Thank you for the comment. Yes, we have that planned for actor-critic methods. Note that for value based methods, we do give the option to users to pass in a network instance.
Just following up on this. We have updated the actor-critic base class to also be able to pass in actor and critic networks as arguments. Thank you for this suggestion. Please let us know if you notice any errors when using it. It will be helpful for us.
The current implementation of
ActorCriticBase
makes it a bit trick to have custom actor and critic networks that have shared layers. This is because the instantiation of the networks happen in theActorCriticBase
class. You can probably get around it but it's very tricky. I'd recommend you pass in the actor/critic objects rather than the class types and let the user initialize them.The text was updated successfully, but these errors were encountered: