In v0.2.1, calling generate! always trigger a backpropagation from the score, even if that isn't necessary. I did this to simplify the code during the earlier refactoring, but it should probably be fixed in the next major update.
@mirisr Noticed performance drop from version v0.1.0 to version v0.2.1
In v0.2.1, calling
generate!
always trigger a backpropagation from the score, even if that isn't necessary. I did this to simplify the code during the earlier refactoring, but it should probably be fixed in the next major update.@mirisr Noticed performance drop from version v0.1.0 to version v0.2.1