-
Notifications
You must be signed in to change notification settings - Fork 151
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
[DOC] Add 'Raises' section to docstring (#1766) #2484
base: main
Are you sure you want to change the base?
Conversation
Thank you for contributing to
|
Raises | ||
------ | ||
ValueError | ||
Raised when `min_window` is greater than `max_window + 1`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as a general rule use double ticks, e.g. min_window
otherwise it does not get rendered properly
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for pointing that out! I've updated the docstring to use double backticks around min_window for proper rendering. The changes have been pushed to the branch.
"""Calculate max_window based on max_win_len_prop or other parameters.""" | ||
return int(self.max_win_len_prop * 100) | ||
|
||
def validate_window_sizes(self): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could you make these protected?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I've updated both methods (calculate_max_window and validate_window_sizes) to be protected. The changes have been pushed to the branch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please fill out the template instead of leaving it blank, and title the PR appropriately. See the contributor guide on our website.
A lot of the changes seem unnecessary. Raises should only contain known exceptions/errors being intentionally raised in the code, not any possible unintended error. There is already a check for the window sizes, not sure why we need another.
Hey @MatthewMiddlehurst, thank you for your feedback. I've filled out the template and updated the title of the PR as suggested. Regarding the Raises section, I noticed that the check if self.min_window > max_window + 1 is already implemented to validate the window sizes. Could you clarify if you see this as redundant or if there's a different approach you would recommend for validating the window sizes? I'm happy to make adjustments based on your suggestions |
1770319
to
7e4af72
Compare
Updated text so the PR does not close the issue. I would say the new attribute and functions are redundant given that it is already checked in |
…aeon into add-docstring-raises
Hi @MatthewMiddlehurst and @TonyBagnall, I’ve made the requested changes. Please review it and let me know if there’s anything else. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR contains a lot of unnecessary whitespace additions and some of the documentation has been duplicated for some reason. Please resolve.
f"Error in ContractableBOSS, ``min_window`` =" | ||
f"{self.min_window} is bigger" | ||
f" than max_window ={max_window}." | ||
f" Try set min_window to be smaller than series length in " | ||
f" Try set ``min_window`` to be smaller than series length in " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this does not need to be changed, the formatting wont work with print outs im pretty sure
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added the double backticks in the error message as per @TonyBagnall's earlier suggestion. Could you clarify if I should revert this change for proper print formatting, or is there a different approach you'd recommend?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is only required for the docstrings, not warning and error.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have made the requested changes. Please let me know if there are any further adjustments needed.
@@ -328,6 +335,7 @@ def _predict_proba(self, X) -> np.ndarray: | |||
------- | |||
2D np.ndarray | |||
Predicted class labels shape = (n_cases). | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
unnecessary white space
Raised when ``min_window`` is greater than ``max_window + 1``. | ||
This ensures that ``min_window`` does not exceed ``max_window``, | ||
preventing invalid window size configurations. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should be indented
Reference Issues/PRs
See #1766.
What does this implement/fix? Explain your changes.
This PR adds a "Raises" section to the docstring of the ContractableBOSS class to document the ValueError exception. It also fixes line endings. Testing: I’ve updated relevant tests to ensure that the ValueError exception is correctly handled.
Does your contribution introduce a new dependency? If yes, which one?
No
Any other comments?
This PR improves code documentation and ensures consistent line endings for cross-platform compatibility.
PR checklist
For all contributions
For new estimators and functions
__maintainer__
at the top of relevant files and want to be contacted regarding its maintenance. Unmaintained files may be removed. This is for the full file, and you should not add yourself if you are just making minor changes or do not want to help maintain its contents.For developers with write access