-
Notifications
You must be signed in to change notification settings - Fork 21
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
Typo in documentation of opty #297
Comments
The docstring for functions are in the source file right under the associated function signature. The line you mention here in |
I start to see it. (I thought naively that the documentation was some separate document, maybe written in over-leaf or so.) |
Question, just to verify, I start to understand how the documentation is generated:
Am I basically on the right track? |
It depends. cyipopt.Problem documentation should stand indedpendent of opty, but if there is an error in cyipopt or you want to expand the general explanations then you edit cyipopt. If it is something opty specific and you want a different docstring in opy for .solve() than the cyipopt.Problem.solve() we can overwrite the cyipopt docstring inside of opty (only). To overwrite it you do something like: class Problem(cyipopt.Problem):
def solve(self, ...):
"""Override docstring""""
return super().solve(...) |
In the opty documentation there is this explanation, actually at a few places: Then, a bit below, solve is explained: The shape of x given as (n, ) I think is not correct as per the definition of n above. |
That is a good reason to overwrite the |
I will try it. |
In the opty documentation release 1.4.0.dev0 on page 129 it says:
jacobian(free)
Returns.....
Return type
ndarray.shape((2n + q + r + s) * (n(N-1) + o ), )
but in my test it returns
ndarray.shape((2n + q + r + s) * (n(N-1)) + o, ) The bracket to the right of o is moved to the left.
@moorepants confirmed this is a typo.
The text was updated successfully, but these errors were encountered: