-
Notifications
You must be signed in to change notification settings - Fork 57
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
[constraint] adds JointConstraint #274
Conversation
* Update CI to build v23.06 branch. * Disable MacOS CI build for now.
* Fix install SofaPython3 CI action. Use non-nightly SofaPython3 builds for CI. * Allow macOS CI build but do not stop on deploy failure.
…ource Fix source code archives assets from release branch and not master.
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.
It would be great to have an example scene.
Well if no one disagree I'll make the changes I proposed. |
- changes maxPositiveDisp/maxNegativeDisp to maxDisplacement/minDisplacement - removes references to angle - renames imposedValue to value - updates example wrt changes
This is good for me. I'll merge it in two weeks, unless you need more time to look at it @TanguyNav @alxbilger ? |
|
||
def createScene(rootNode): | ||
rootNode.addObject('RequiredPlugin', name='SoftRobots') | ||
rootNode.addObject('RequiredPlugin', name='SoftRobots.Inverse') |
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.
@EulalieCoevoet Could you make sure that this plugin is not required? Thanks
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.
Oups sorry. Not needed indeed.
Thank you @TanguyNav for this work!
Proposition of changes:
maxPositiveDisp
/maxNegativeDisp
, I would prefer usingmaxDisplacement
/minDisplacement
. When we want a positive minimum it's really weird to give a negative value. Even in the general case I find it confusing (I don't like it either in CableConstraint...).angle
.value
andvalueType
in the other constraints (CableConstraint, SurfacePressureConstraint, PositionConstraint). I would prefer to keep it uniform and thus avoid usingimposedValue
instead ofvalue
.