Skip to content
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

MRBF enabling working with scalar DOF #167

Merged
merged 7 commits into from
Jan 18, 2021
Merged

Conversation

roccoarpa
Copy link
Collaborator

@roccoarpa roccoarpa commented Jan 13, 2021

The pull enabling the use of scalar DOFs in MRBF class, in order to calculate "scalar" output field on the whole target geometry.
This scalar field used into Apply block, with setScalarInput method, let the User to simulate a deformation, whose displacement vectors, in each point, are normal of target surface, and have modulus equal to the local scalar field value.

Example of usage is reported in manipulators_example_00008.

The pull integrates also miscellaneous fixes.
Compiled and tested with bitpit @ optimad/bitpit@15952d8
(reference pull request bipit optimad/bitpit#127 )

AFTER MERGE
compliant with master bitpit@optimad/bitpit@17d63a8

MPI 1 proc run of SHARED points mode of the method did not rebuilt
properly the field of signed distance.
When Scalar input is enforced, and vertex normals are required to get
the deformation field to apply, enforcing update Adjacencies for
safeness
The class now can create a final "scalar" displacement field on geometry
(as a "surface normal" referred displacement field), starting from
scalar inputs as DoF of RBF nodes.
the example show the usage of MRBF in scalar mode to get a final
deformation driven along the surface normals of the target geometry
@roccoarpa roccoarpa merged commit b10766d into master Jan 18, 2021
@roccoarpa roccoarpa deleted the mrbf.enable.DoF.normal branch January 18, 2021 11:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants