Dzmitry Bahdanau
Dzmitry Bahdanau
(5) You are absolutely right, but we do not do it any more! #378 fixes that.
(2) Lazy initialization and allocation is almost the only way to deal with the situation when a complex brick A has a few bricks B, C, ... as his components...
(4) No, because `push_initialization_config` called implicitly by `initialize` in this case will wipe all your changes away. It is important to first propagate the initialization schemes, and then overwrite the...
(3) I am not sure I fully understand your reasoning, but I would like to emphasize the fact that children not necessarily form a sequence. This was one of PyLearn2...
1. Thanks for this idea, this one has not yet been considered. I would probably not support it, because filling my model with some `NoOpScheme` every time before loading from...
As for `LoadingFromDiskScheme`: it would be rather problematic to implement loading by a scheme because the names of different bricks' parameters are not unique in Blocks. It is the hierarchical...