Skip to content

Refactor the API Ref #1639

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

Closed
wants to merge 7 commits into from
Closed

Conversation

nanjekyejoannah
Copy link
Contributor

@nanjekyejoannah nanjekyejoannah commented Sep 7, 2022

@LPereira95 before I commit everything, can we go through this draft API ref for the geometry module and verify what we want before I modify the rest of the docs.

Copy link
Collaborator

@luisfpereira luisfpereira left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @nanjekyejoannah!

For the changes with autosummary I agree (it is exactly what I was thinking).

One thing I wonder is if we can simplify the name in the left table of contents (e.g. if I'm within geomstats.geometry.manifold.Manifold, it suffices to have the name manifold.Manifold - and later even Manifold will suffice).

For the changes in the docstrings, please take a look to linting errors (see link below). Additionally, check in the contributing guide how you can run flake8 locally, so you can immediately see what are the (linting) errors you may introduce.

Comment on lines 9 to 10
"""
Class for Euclidean spaces.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Notice this is not allowed by linting (check e.g. here).

It is expected that the first line of the docstring contains a brief description of the class/function/method.

@@ -828,7 +887,11 @@ def squared_dist(self, point_a, point_b, **kwargs):
def parallel_transport(
self, tangent_vec, base_point, direction=None, end_point=None
):
r"""Compute the parallel transport of a tangent vector.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When escapes are used within the docstrings, e.g. within math expressions, we need to add "r" to allow proper rendering. Notice that linting also checks it.

@nanjekyejoannah
Copy link
Contributor Author

nanjekyejoannah commented Sep 21, 2022

I have the API ref PR updated, several things:

  • There is lots of fixing for doc strings, I have separated this in separate PRs
  • Autosummary now shows many errors to be fixed in imports
  • Notebooks has so many errors
    I know we had agreed that we will try to address all the sphinx-related errors but I am now worried if its realistic, many areas are affected and most are not related to docs.

We can chat tomorrow and scope what we can reasonably address.

@luisfpereira luisfpereira marked this pull request as draft September 22, 2022 15:03
@luisfpereira
Copy link
Collaborator

I'll close this as we decide to move in smaller steps. #1663 addresses the same issues as here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants