-
Notifications
You must be signed in to change notification settings - Fork 174
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
SP plot: similarity values in legends appear only after running the simulation #992
Comments
Not sure if that's a bug or a feature, but before running the simulation there is no data on which a similarity could be computed (one could assume 0, but one could equally well argue that it is undefined) |
The numbers I'm talking about are read-outs from the SP plot and they are computed real time. So at t=0 it should be 0 and after that whatever the plot is showing. When you press the play button first time the plot displays the similarities but the legend doesn't reflect those (there are just labels) |
Maybe we should discuss this in person. (Or an image might help.) |
I still can't reproduce it, but I understand now what the bug is. The steps to reproduce would be (if the bug appears on your machine which it might not):
|
I can reproduce the bug given those steps! What branches are you on @jgosmann? Also, should we move this issue to https://github.com/nengo/nengo_gui ? |
both current master (nengo: 8158ea2, nengo_gui: nengo/nengo-gui@47500695ad)
I would say so, I didn't realize that this is on the Nengo issue tracker. |
Can someone of you try this with the nengo_gui |
(moved to nengo/nengo-gui#709) |
The similarity values in the legend (numbers next to the semantic pointer labels) of a semantic pointer plot appear only after I run the simulation for the first time, and then press the simulation reset button (or play again). They never appear right away.
I have observed this with two different browsers on my machine (and my laptop), so I have been wondering if anyone else can reproduce this?
The text was updated successfully, but these errors were encountered: