-
Notifications
You must be signed in to change notification settings - Fork 175
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
Add some advanced features documentation. #1130
Conversation
docs/improving_performance.rst
Outdated
build of a model will still take about the same time (technically a bit longer, | ||
because the computed decoders will be stored), but all subsequent builds of the | ||
same model can just load the stored decoders and will be faster. This will also | ||
work to some degree if changes to the model are made, but of course only for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove of course
. It's kind of condescending. Maybe people don't know what caching is in this context.
Left some inline comments to fix some phrasing. |
I set this to "needs second review". Those changes can be easily made by whoever merges this if I don't get to it beforehand. |
Made minor changes to the phrasing. Added @Seanny123's suggested changes. |
I also took a look at this, only partly in order to get my review in for the week ;) Docs look great, really nice addition, and nice to have an advanced features section for more esoteric information 👍 I pushed a commit with some slight rewordings. I also added the WIP label because this is blocked by #1035. One thing that I would like to do (but am not sure how to do best) is not duplicate the One thing that matplotlib does is link to and include a copy of a sample rc file in there, which we could also do with the |
I think it is nice to have a verbose sample rc file because then I can edit it and have all the required information right there without the need to navigate to the documentation. |
'kay, then why don't we include the verbose sample in the docs rather than duplicating the information? |
Sure, but the sample file will need some updating (probably should've been updated in the first place). |
Pushed a commit updating the sample file and If you want to see the generated docs, I can send put the HTML files up somewhere, or you can try building the docs yourself. I do |
|
(I didn't have the requirement installed, but the error message is not really helpful in that case.) |
Yeah... we could add something to |
To dos:
|
I did in my commit, I think... at least, I added the ones that were in the |
Seem to be missing to me ... (or maybe I forgot to add those in the first place) |
The |
I added two options, see https://github.com/nengo/nengo/pull/1130/files#diff-e6c6a36ed8df7b1bd3ac3887920554ccR60, not sure if there are more... |
Ah, right you are! Should probably be |
It needs to match the class name with the current implementation. |
Fixed those things. |
As per the discussion at the dev meeting, when this is merged, it should close #340. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This still looks good to me. Special thanks to @mgserafi for the fixes I pointed out and really should have fixed myself.
Added commits to update this to match what has actually been merged to master. |
This is still good. The |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pushed a fixup with a few final touchups. I'll merge on @jgosmann's OK!
LGTM 🍰 |
* Methods to improve the performance. * Nengo RC file and documentation of possible settings. This mostly involves updating the docstrings in nengo/rc.py and including them in the documentation. Also included an intersphinx mapping to the Python 3 docs so that we can reference Python objects easily.
Description:
Extends the documentation with some advanced topics. In particular:
Motivation and context:
The performance documentation is probably useful for new users who start to build larger models. Also it provides documentation for how to activate/deactivate the operator graph optimizer which is important because it provides a trade off between build time and simulation time.
In this documentation I had to reference the Nengo RC files which prompted me to add the missing documentation for that file and the settings too.
This PR closes #1119, addresses #1017.
Interactions with other PRs:
This adds documentation for the yet to be merged PR #1035. This assumes that the optimizer is active by default, but I could see this being changed. In that case this PR needs to be updated.
How has this been tested?
Build the docs and skimmed over it and tested cross-reference links. Should probably get a more careful read, preferably by a native speaker.
Where should a reviewer start?
Build the docs and start reading the "Advanced Topics" section.
How long should this take to review?
Types of changes:
Checklist:
Still to do: