Repository navigation
Conversation
wip fix different xtip wip wip2 wip3 wip4 working mapping optimize computations add timer remove bogus test not setting a topology is not an error
The mapping only implements apply() (applyJ/applyJT are empty), so it must never be treated as a mechanical mapping. Setting mapForces/mapConstraints/ mapMasses in the scene file is too late: Node::addObject categorizes the mapping before parse() reads the attributes. With the defaults false, the mapping can feed a MechanicalObject (e.g. an X-ray tube surface) without the constraint pass emitting an applyJT error every step.
fredroy
added
enhancement
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For creating a visual model of the beam, the typical scene uses edge2quad, creating quads around the centerline, and then adaptivebeammapping, mapping the vertices of the quads with the interpolation
It makes much more sense to map first and then create the quads around the mapped centerline.
Benches on 3instru_collis.scn (launched with glfw and offscreen mode to make sure the visual path is executed)
5000 iterations done in 39.477 s ( 126.656 FPS)5000 iterations done in 30.995 s ( 161.316 FPS)Bonus: it can also generate a second layer to add thickness (useful for fluoroscopic images)