-
Notifications
You must be signed in to change notification settings - Fork 33
Adds support for variable order mfem nurbs curve meshes #1821
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
Open
kennyweiss
wants to merge
17
commits into
develop
Choose a base branch
from
feature/kweiss/arbitrary-order-mfem-nurbs
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+1,852
−67
Open
Changes from all commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
cb5c5c1
Adds option to step reader example to write out patch trimming curves…
kennyweiss 244f6db
Update MFEMReader to read in NURBS patches (when supported)
kennyweiss 0627a45
Extract the wire index of each trimming curve per patch and use as mf…
kennyweiss f33b94e
Adds primal::NURBSCurve::isLinear
kennyweiss e88a42e
Adds NURBSPatch::isTriviallyTrimmed predicate
kennyweiss 060b0b1
Adds an option to output a stats file per patch in quest_step_file ex…
kennyweiss 97613f6
Adds additional patch stats (isTriviallyTrimmed & num knot spans in u…
kennyweiss 2dda7c0
Adds stats to indicate original periodicity of each patch
kennyweiss 06f644b
Improves output command line options for quest_step_reader example
kennyweiss 8b18d94
Updates svg2contours to optionally output mfem meshes using patches f…
kennyweiss 8cdea67
Output elliptic arcs as rational quadratics instead of rational cubics
kennyweiss c7aa8f7
Adds option to 2D winding number example to output degree `elevated` …
kennyweiss 327f788
Misc comments and cleanup
kennyweiss ba6a109
Fixes file filters for code checks
kennyweiss da15e3e
Guard against calling log(0)
kennyweiss b771046
Updates RELEASE-NOTES
kennyweiss 71a2dba
MSVC appears to not like `near` as a variable name
kennyweiss File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
I still don't know if I agree with the idea that "no trimming curves" should be treated the same way as "has trimming curves which don't really do anything." In particular, I can imagine a use case where you'd want to call
and with this definition, you'd end up with
patchescontaining potentially two very different kinds of surfaces, some which are the same as untrimmed, and some which are totally invisible.I think this next one is potentially more controversial, but I also think that if the internal flag for trimmed-ness
m_isTrimmedis false, this should probably return false too. In general, I think the semantics ofisTriviallyTrimmed()should really mirrormakeTriviallyTrimmed(), and the latter means "mark the patch as trimmed, and add four curves around the patch boundaries.Uh oh!
There was an error while loading. Please reload this page.
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.
So
if(!isTrimmed()) return false;if(numCurves != 4) return false;That could work
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.
Yes, I think so. Do you feel like that's intuitive enough, to have untrimmed patches return false if
isTriviallyTrimmedis called on them?