Skip to content

Fix domain specification in OrderedLogistic and OrderedProbit documentation #7732

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

coderpheonix
Copy link

@coderpheonix coderpheonix commented Mar 21, 2025

This PR corrects the domain specification in the documentation of the OrderedLogistic and OrderedProbit distributions. It ensures that the indexing is clearly mentioned as 0-based to avoid errors.


📚 Documentation preview 📚: https://pymc--7732.org.readthedocs.build/en/7732/

Copy link

welcome bot commented Mar 21, 2025

Thank You Banner]
💖 Thanks for opening this pull request! 💖 The PyMC community really appreciates your time and effort to contribute to the project. Please make sure you have read our Contributing Guidelines and filled in our pull request template to the best of your ability.

Copy link
Member

@OriolAbril OriolAbril left a comment

Choose a reason for hiding this comment

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

Thanks!

Would you mind also updating the parameters section?

  • cutpoints : tensor_like of array -> cutpoints : tensor_like of float
  • compute_p: boolean, default True needs a space before the colon as numpydoc requires spaces both before and after the colon that separates name and type of parameters

from 1 to K as a function of some predictor, :math:`\eta`. The
from 0 to K-1 as a function of some predictor, :math:`\eta`
Copy link
Member

Choose a reason for hiding this comment

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

It looks like you also removed the ". The" part which makes the docstring confusing:

imatge

Seems there are eta cutpoints with this updated wording which is not the case.

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