Skip to content
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

analysis.calculus directional_names documentation #3563

Closed
trexfeathers opened this issue Nov 26, 2019 · 1 comment · Fixed by #5680
Closed

analysis.calculus directional_names documentation #3563

trexfeathers opened this issue Nov 26, 2019 · 1 comment · Fixed by #5680

Comments

@trexfeathers
Copy link
Contributor

calculus.curl expects input cubes to begin with their directional name followed by whitespace/underscore - achieved via calculus.spatial_vectors_with_phenom_name. This behaviour should be documented.

The list of accepted directional names should also be documented. This is currently held in the directional_names set within spatial_vectors_with_phenom_name, which is a private method. To expose the list for documentation directional_names needs to become global, and to get Sphinx to pick up the values and any lines of text I think we would need to use Sphinx autodata. May need some sphinx config changes but not sure yet.

This is something I will need to learn more about when I have some time, so just documenting in an issue for now. Any better ideas for how to document directional_names will be welcomed.

Copy link
Contributor

github-actions bot commented Jan 7, 2024

In order to maintain a backlog of relevant issues, we automatically label them as stale after 500 days of inactivity.

If this issue is still important to you, then please comment on this issue and the stale label will be removed.

Otherwise this issue will be automatically closed in 28 days time.

@github-actions github-actions bot added the Stale A stale issue/pull-request label Jan 7, 2024
@trexfeathers trexfeathers removed the Stale A stale issue/pull-request label Jan 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants