You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How to handle preferences and parameters for trimming (Integration rule parameters are currently transferred via a singelton object)
check implementation of TrimmedReferenceElement
think about IndexSet, currently index for elements is unique, but should be independent index Set for trimmed and full, this will break the basis implementation atm
Ensure that boundarySegmentIndex is consecutive for trimmed patches
Enable checkBoundarySegment test, either its not correctly implemented or the test fails because its not suited for none-reference elements
This is meant to keep track of unfinished buisiness. These points don't have to be adressed before merging #46
TrimmedReferenceElement
IndexSet
, currentlyindex
for elements is unique, but should be independent index Set for trimmed and full, this will break the basis implementation atmboundarySegmentIndex
is consecutive for trimmed patchesIdType
dune-iga/dune/iga/nurbsbasis.hh
Line 666 in 6cb633b
dune-iga/dune/iga/nurbsbasis.hh
Lines 700 to 702 in 3c55b2f
false
)Backlog
FIxed
volume
function for trimmed elements ingeometrylocalView
globalRefine
crashes when called with a value greater 1volume()
methods for trimmed geometriesGeometry<griddim>
to be constructable from aFieldVector
center()
method is currently invoked viaDefaultGeometryImplementation
whereglobal(0.5)
is called which doesn't make sense for trimmed geometriesThe text was updated successfully, but these errors were encountered: