Add links to related functions in docstrings (applies to both links to internal and external functions), also add See also sections where relevant. Follow up of #1184. Places where references are of particular importance are: kwargs description to ease consulting of the documentation relevant to the kwargs so users know what keys are supported; and functions that take as input the output of a previous one
For details on how to do so, read the hyperlinks section in the developer guide. Moreover, the docstring of hdi and plot_hdi are good examples.
An example of internal reference can be found at PyStanSamplingWrapper page (the leading :py: is not needed though).
An example of external references can be found at the description of plot_kwargs in plot_kde page.
An example of See also section can be found at compare page
This should help tracking what has been done. We could open an issue for every single function but that would probably get out of hand fast and make keeping track harder. Functions where work is halfway will be listed below without checkmark, updated functions will be checked and all missing functions are free and unassigned.
If you are interested in working on this, check the list to see what functions are available and comment which (1-4 functions per PR seem like a reasonable number, don't try to work on too many at the same time) would you like to tackle.
backend_kwargs are missing._extend_... cc @percygautam Hey can I have this project?
Yes, thanks!
There are many functions to update, so it is probably better to divide the issue into several pull requests. Does this sound good? What functions were you planning to update first?
@JeevaJyothiSundaram I have just noticed you downvoted the previous comment, were you planning on working on this issue? There are plenty of functions to update.
I this is not assigned to anyone, if not I would like to work on this.
@just-linux you can work on this, thanks!
Comment here the functions you are planning to work on so work is not duplicated and that's about it, once updated I'll take care of updating the checklist in the issue description.
Ok, I will start on the _InferenceData.sel/InferenceData.isel_ part.
Great! Feel free to ask any question here or on gitter
Hi, I would like to work on this issue. Can I work on plot_hdi, compare and InferenceData.sel/InferenceData.isel(since its not completed) if its not taken by anyone? Let me know
Thanks
That would be great @Srijha09. Note I have updated the link in the description to https://arviz-devs.github.io/arviz/contributing/developer_guide.html#hyperlinks. Let us know if you have any doubts
Thanks for updating the link. Just a clarification before I do a PR, I am supposed to add external references on backend_kwargs to bokeh and matplotlib methods, right?
Also, I went through the InferenceData.sel/InferenceData.isel, it looks like all the references and the see also section has been added referencing to each other.
https://arviz-devs.github.io/arviz/api/generated/arviz.InferenceData.isel.html
https://arviz-devs.github.io/arviz/api/generated/arviz.InferenceData.sel.html
I am supposed to add external references on backend_kwargs to bokeh and matplotlib methods, right?
Yes, you'll have to check the source code to see to which function/method they are passed and add a link there using intersphinx.
Also, I went through the InferenceData.sel/InferenceData.isel, it looks like all the references and the see also section has been added referencing to each other.
https://arviz-devs.github.io/arviz/api/generated/arviz.InferenceData.isel.html
https://arviz-devs.github.io/arviz/api/generated/arviz.InferenceData.sel.html
Thanks! I must have forgotten to update the description, I'll do it now
Okay thanks. I'll do that.
Hey, also I see you have added other functions as well. Would it be better if I add all the references to the functions and create a single pull request?
I see you have added other functions as well. Would it be better if I add all the references to the functions and create a single pull request?
yes, I figure the last point about _all_ other functions in the library wasn't clear enough so I tried to be more explicit. I would suggest making several PRs modifying 1-3 files each, otherwise the single PR touching nearly all the library is doomed to have multiple git conflicts and need to be rebased a few times which in the long run will be more work than multiple PRs.
Alright thanks.
Hi just to clarify, since this issue has been closed shall I update the other functions as well by doing some PRs?
Let me know
Yes, the issue is not fixed yet, only partially. It was closed automatically when merging due to using "resolve" right before the issue.
Oh okay.