-
Notifications
You must be signed in to change notification settings - Fork 13
set up sphinx doc #138
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
set up sphinx doc #138
Conversation
|
Hello @marcobarilari! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found: There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻 Comment last updated at 2020-10-31 19:23:08 UTC |
Codecov Report
@@ Coverage Diff @@
## dev #138 +/- ##
=======================================
Coverage 21.63% 21.63%
=======================================
Files 55 55
Lines 795 795
=======================================
Hits 172 172
Misses 623 623
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
|
Hey @Remi-Gau, I followed the instructions in the spm pipeline repo and something happened but I have no idea about I am doing and if it is working. Sphinx is still very unclear to me |
|
Are you saying you can't figure out the riddles that Sphinx is throwing you? Will have a look right away. |
docs/.readthedocs.yml0
Outdated
| @@ -0,0 +1,26 @@ | |||
| # .readthedocs.yml | |||
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.
Not sure why you have several .readthedocs.yml files in the docs folder.
As long as you have one in the root folder, you are good to go.
Also the read the docs part comes later and is only to use the website "read the docs" to display the documentation on line. So this is not purely "sphinx" related.
For example "read the docs" can also render docs written with "mkdocs".
docs/source/conf.py
Outdated
| # add these directories to sys.path here. If the directory is relative to the | ||
| # documentation root, use os.path.abspath to make it absolute, like shown here. | ||
| # | ||
| # import os |
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 are going to need to uncomment those.
You also need to modify the path in os.path.abspath so it points to the root of this repo.
You can just do like in conf.py of the CPP_SPM repo
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.
I did change these parts but I suspect I made a mistake and ignore the changes while committing. My bad
|
Looks like you are on good track to me. You need to make some changes to the Once you are done you can try to build the doc with the following command: to run from within the This creates a set of html file in the |
Co-authored-by: Remi Gau <remi_gau@hotmail.com>
Co-authored-by: Remi Gau <remi_gau@hotmail.com>
Co-authored-by: Remi Gau <remi_gau@hotmail.com>
Co-authored-by: Remi Gau <remi_gau@hotmail.com>
Co-authored-by: Remi Gau <remi_gau@hotmail.com>
Co-authored-by: Remi Gau <remi_gau@hotmail.com>
Co-authored-by: Remi Gau <remi_gau@hotmail.com>
Co-authored-by: Remi Gau <remi_gau@hotmail.com>
|
Also looking around to other repo that use Sphinx it seems that we do not need to commit the content of the So you can remove all that of that from the repo and add the |
|
Oh by the way you can add several comments at once through the github graphic interface. I learnt that on the BIDS specs and I still to update their doc there to help others with this. |
|
ok, I have rebuild sphinx doc with the new |
docs/source/function_description.rst
Outdated
|
|
||
| .. autofunction:: initPTB() | ||
|
|
||
| :func:`initPTB` |
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.
I don't understand this part, what is it the point to have :func:initPTB`` and .. autofunction:: getExperimentStart after it?
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.
| :func:`initPTB` |
You are right: this one can be removed and autofunction getExpStart brought up. :-)
|
I have added all the function in the |
I think you can try using the If you feel like it. |
|
sure, but somehow the sphinx updates should be in a branch (master) of the repo, shouldn't they? Or there is a way to build the rtd from a PR? |
|
If it builds locally you can merge this into See here: https://readthedocs.org/dashboard/cpp-bids-spm/advanced/ Let me know if you can't access I might need to add you as Maintainers on RTD. You can also start transferring some content from the old markdown |
I see this (lol) |
|
oh dear... Tried to add you using your github username. Let me know if this works |
|
it worked! thank you |
|
All right, I added an installation section (also to try sphynx synstax) and going to merge this and publish it to see if it works. Will add more docs in the future in other PRs, LMK |
No description provided.