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
As our networks have grown more complex, we've needed more ability to debug the models "in vivo" which means having the model output not just the action values but some internal values computed at different points in the network. We can then take these internal values and log them or even use them for debug rendering in the environment.
So far we've hacked this up by adding actions to the network, but that's clearly suboptimal, so we wanted to see if there was a recommended way for having the model output "side channel" values, which we could then use to pass out the results of internal calculations.
Any advice or pointers would be much appreciated.
The text was updated successfully, but these errors were encountered:
nathanmartz
changed the title
Emitting internal network state
Best way to emit/output internal network state
Aug 28, 2023
nathanmartz
changed the title
Best way to emit/output internal network state
Best way to emit/output internal network state (for debugging)
Aug 28, 2023
As our networks have grown more complex, we've needed more ability to debug the models "in vivo" which means having the model output not just the action values but some internal values computed at different points in the network. We can then take these internal values and log them or even use them for debug rendering in the environment.
So far we've hacked this up by adding actions to the network, but that's clearly suboptimal, so we wanted to see if there was a recommended way for having the model output "side channel" values, which we could then use to pass out the results of internal calculations.
Any advice or pointers would be much appreciated.
The text was updated successfully, but these errors were encountered: