Expose Net.copy_trained_layers_from and Net.share_trained_layers_with in pycaffe #1195
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows finetuning from Python, for example.
Misgivings:
copy_trained_layers_from
andshare_trained_layers_with
are very long names, while pycaffe mostly has pretty succinct naming. Also, the layers don't really have to be trained at all, so maybe the simplecopy_from
andshare_with
would be better. But these are the names in the C++ interface.I don't know what will happen if you
share_trained_layers_with
a net, and then delete that net. But it's the same as what will happen if you do the same in C++; does anyone know how that is handled? For the use case I have in mind (the solver), this issue does not arise, because the solver is holding all the nets.