-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plot memory interactions with multiple heads #38
Comments
Indeed that dashboard functionality was intended to be very simple, and does not generalize to multi-head read and write. For anything more complex, I usually had to write code for my specific use-cases. Visualizing all the heads at once seems to be challenging. The best option might be to plot each head individually on individual axes, which might not be ideal. I'm sorry I can't be of much help here, but I suggest you have a look at the code for As for the almost all white columns, this is most likely a problem of normalization. I didn't explicitly normalize the plots in [0, 1], which means that if the weights are almost all the same (~1/128), then the normalization will display them all as white. I will fix this, than you noticing it! |
Ok, got it! Can you please point me out at the code in the |
From memory, this is the relevant part for plotting the read and write heads. |
Thanks @tristandeleu, I'll surely have a look a the code you pointed me to. In case I can make it work for multiple heads I'll surely create a pull request. |
I need to plot the weights and the interactions with the memory for models with multiple read and write heads, but the current implementation of the Dashboard just shows it for a single head (there is a single white square for each time step in the memory column-like plot). Also, for some models (expecially when using the LSTMController) I got weird memory plots, like an almost entirely white read column (that should mean that the controller is interacting with each memory row with a degree of 1, that is not possible or correct)
The text was updated successfully, but these errors were encountered: