Generalize nurbs #52
Merged
Generalize nurbs #52
Conversation
This file contains 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
|
@eulovi this might also be a good way to use the MeshPy NURBS with the new solid elements. |
|
Thanks for implementing this @isteinbrecher! I think this is a nice solution to add the new solid elements :) |
eulovi
previously approved these changes
Apr 3, 2024
isteinbrecher
force-pushed
the
generalize_nurbs
branch
from
5f51e7d to
d6f85f9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This merge allows to set the "element string" for a NURBS patch directly in the script, i.e., we don't have to implement all relevant cases.
Similarly, now there is a class
MaterialStringwhich allows to directly set a material from the calling script so we don't have to implement each material case in MeshPy.