-
Notifications
You must be signed in to change notification settings - Fork 17
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
Use a simplified formulation of the relative task #82
Conversation
Thank you for this contribution 😃 We can expect the following test to fail: |
Pull Request Test Coverage Report for Build 8483559586Details
💛 - Coveralls |
@stephane-caron I don't get the last formatting error concerning type annotation. Could you help ? |
The previous workaround for this was: if isinstance(self.cost, np.ndarray): # helps mypy
self.cost[0:3] = position_cost MyPy is stating that the type if inferred for Looking at it again we can do better by adding a more precise type annotation in the class itself: class RelativeFrameTask(Task):
cost: np.ndarray
frame: str
... I checked locally and it fixes the MyPy error, so I suggest we go for that one ☝️ |
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.
LGTM 👍 Feel free to merge.
Co-authored-by: Stéphane Caron <[email protected]>
@stephane-caron You can merge if you think its ready ! |
This PR use a simpler formulation of the relative task, discarding some matrix multiplication in the Jacobian computation.
It follows the discussion in: #80
It also changes the cost setting, to match the typing signature of the function and add the calculus of the jacobian in the description.