Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upFix shape parameter inconsistencies in developer's guide #18175
Comments
Hello, I can take it provided no one else is working on it now. |
@glemaitre @lorentzenchr this issue slightly overlaps with #14312 and #15761 but it is not a duplicate. |
At least they are cross-referenced now :) |
@glemaitre @cmarmo Thanks for cross-referencing. I'm not sure how to unify all in one issue. Note that #14312 and #15761 are about docstrings of classes and functions, not about examples and developer's guide (or user guide). I think one PR per file seems reasonable and might motivate some new contributors. |
My bad, I omit the fact that you pointed out the UG and example only. So this issue should be fixed pretty quickly then. |
I edited one of the specified files, e.g. develop.rst, here is my PR #18191 |
I noticed that in the documentation guidelines for “References” in docstrings it is suggested to look at the Silhouette Coefficient, which itself does not follow documentation writing guidelines for shapes and arrays. Is there a better example that can be provided in the documentation guidelines or should fix that docstring as a part of this issue? |
The docstring of the silhoutte coefficient is not that good but the "References" section is fine:
I think this is what the documentation is referring too. The simplest would be to make a PR solving the issue in the class and we merge it quickly :) |
I added a new PR #18214 that fixes the issue with the Silhouette Coefficient. |
I reopen for the 3 left files in examples and user guide not inlcuded - in my understanding - in the above mentioned issues. |
Describe the issue linked to the documentation
https://scikit-learn.org/stable/developers/contributing.html#guidelines-for-writing-documentation specifies how to write parameters with a
shape
attribute in a docstring, e.g.There are a few instances in the developer's guide, examples and user guide that do still not follow that example: