Alexander Sidorov e0e124e617 Fix RNN scoping situation ...

Summary:
There is a long lasting problem of scoping which was introduced in original python wrappers early in H1. Basically each RNNCell implemented has to manually scope outputs of each of the operators. If somebody forgets, then there could be weird bugs with layers etc.

Approach is the following. User has to explicitly specify current scope when using  apply_over_sequence function and others if the function is going to be called several times (like for stacking layers). This way we use Caffe2 native scoping approach instead of inventing one extra API people have to use (i.e. passing scope name as an argument to the RNNCell constructor).
Closes https://github.com/caffe2/caffe2/pull/1681

Differential Revision: D6777536

Pulled By: salexspb

fbshipit-source-id: 73d860b8d4857589e04bdea5a6fcd3080d68427c

2018-02-07 17:35:29 -08:00

..

seq2seq

Fix RNN scoping situation

2018-02-07 17:35:29 -08:00

__sym_init__.py

Re-license to Apache

2017-09-28 16:22:00 -07:00

download.py

Allow for all of the names we have in our model zoo.

2018-02-05 08:52:55 -08:00

resnet_test.py

Re-license to Apache

2017-09-28 16:22:00 -07:00

resnet.py

Fix pool op custom path issue 2, wrongful routing to global pooling

2018-01-09 00:54:45 -08:00