Avoid duplicated scope names when using `_enter_variable_scope`. about sonnet HOT 3 CLOSED

Thanks for the report and clear example. It looks like it's because the variables were created with tf.Variable rather than tf.get_variable, this is known to interact poorly with variable scopes. It's mentioned in the docs but might be a bit buried.

Here's my code:
https://gist.github.com/tfgg/d815ec514697a16bc1067acdbb6f0e1f
which outputs

[u'main_module/submodule_a/a:0', u'main_module/submodule_b/b:0']
[u'main_module/submodule_a/a:0', u'main_module/submodule_b/b:0']

from sonnet.

@tfgg Thanks for the clarification and the example! I must have missed that bit in the docs. I'm not creating any variables directly so it's probably down to some TF slim utils.

Besides being kind of annoying, does this behaviour cause any unwanted effects on the computation?

Closing the issue, thanks!.

from sonnet.

I'm not 100% sure, but I think variable sharing would fail (since it's creating a new variable each time), but I'd want to check that first :)

It's certainly possible that something in TF-slim caused this, it might not always interact well with Sonnet, though I think that also uses tf.get_variable.

from sonnet.