Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarifications for multi-output networks #614

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jonathanstrong
Copy link

A few additions to clarify how multi-output networks should be handled, per the discussion here: https://groups.google.com/forum/#!topic/lasagne-users/61GbgRqKjAo

A few additions to clarify how multi-output networks should be handled, per the discussion here: https://groups.google.com/forum/#!topic/lasagne-users/61GbgRqKjAo
@f0k
Copy link
Member

f0k commented Feb 17, 2016

Thanks! Some of the lines are too long, though, we have a hard limit of 79 characters to comply with PEP8. (Not your fault, you couldn't tell when using the web interface.)

And I'm not sure where to put the clarification, actually. When re-reading the existing docstrings, they already say thing like "Its main use is to collect all layers of a network just given the output layer(s)." -- so they advertise supplying all output layers. The first sentence of get_all_params should probably say network instead of layer, though. What do you think? Is there a less verbose way of clarifying things such that you'd have known what to do?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants