-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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 documentation to ExperimentDescriptionAPI #3679
Add documentation to ExperimentDescriptionAPI #3679
Conversation
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.
As-is, the RST renders pretty nasty. Please merge scottpurdy#8
RST formatting on exp-description-api
@rhyolight - merged your suggestions. What about the references to other source files? Is there a way to make those links? |
Yes, it is typically: :class:`full.namespace.ClassName`
:mod:`full.namespace`
:meth:`full.namespace.ClassName.methodName` If you don't want the full namespace to each thing displayed, use :class:`~full.namespace.ClassName`
:mod:`~full.namespace`
:meth:`~full.namespace.ClassName.methodName` |
in the experiment files that are passed to it. | ||
The :mod:`~nupic.frameworks.opf.experiment_runner` takes an instance of | ||
this class as the description of the experiment to run. Similarly, | ||
`scripts/run_opf_experiment.py` looks for an instance of this class in a |
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.
you can use double ticks to code-format something:
this is not code ``but this is``.
@rhyolight please advise on how to properly link to other source files and how to properly format the parameters and their lists of keys.
fixes #3678
fixes NUP-2430