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
getedgeset, addedgeset!, addboundaryedgeset
No direct replacement, but Ferrite.create_edgeset and Ferrite.create_boundaryedgeset gives equivalent functionality (for 3d cases) for sets not stored in the grid.
FaceValues -> FacetValues
AbstractFacetValues -> AbstractFacetValues (why is this exported?)
Ferrite.getcurrentface -> Ferrite.getcurrentfacet
FaceQuadratureRule -> FacetQuadratureRule
nfaces -> nfacets
FaceIterator -> FacetIterator
FaceCache -> FacetCache
collect_periodic_faces -> collect_periodic_facets
PeriodicFacePair -> PeriodicFacetPair (why is this exported?)
Anything else?
The text was updated successfully, but these errors were encountered:
Technically Ferrite.n_faces_per_cell -> Ferrite.n_facets_per_cell as well, but this is not used/tested and seems to only be overloaded for the SmallGrid. Will open PR to remvoe this completely.
Yea, I would also vote for removing such "global" queries on the grid, since they cause more harm than good. Or we rename then to "max_faces_per_cell" or smth, which could be used to create buffers which are "large enough".
#914 is missing changelog entries for user-facing changes:
getfaceset
->getfacetset
,addfaceset!
->addfacetset!
addboundaryfaceset!
->addboundaryfacetset!
getedgeset
,addedgeset!
,addboundaryedgeset
No direct replacement, but
Ferrite.create_edgeset
andFerrite.create_boundaryedgeset
gives equivalent functionality (for 3d cases) for sets not stored in the grid.FaceValues
->FacetValues
AbstractFacetValues
->AbstractFacetValues
(why is this exported?)Ferrite.getcurrentface
->Ferrite.getcurrentfacet
FaceQuadratureRule
->FacetQuadratureRule
nfaces
->nfacets
FaceIterator
->FacetIterator
FaceCache
->FacetCache
collect_periodic_faces
->collect_periodic_facets
PeriodicFacePair
->PeriodicFacetPair
(why is this exported?)Anything else?
The text was updated successfully, but these errors were encountered: