Dennis Ogiermann

Results 121 issues of Dennis Ogiermann

Towards #848 and #628 . This should show how we could assemble into custom sparse matrix formats. ## TODO * [x] Fix inhomogeneous boundary conditions * [x] Add devdocs *...

awaiting review

These are basically useful to check if we got all assumptions right. Towards https://github.com/Ferrite-FEM/Ferrite.jl/issues/558 . ## TODOs * [ ] Add citations to documenter * [ ] Investigate what is...

This should keep the CI times sane in the long term

refactoring

The shell example is a bit "naked" at the moment. I think we should try to integrate the new CellValues https://github.com/Ferrite-FEM/Ferrite.jl/pull/764 into it for a proper abstraction layer and better...

docs
refactoring

Title should say everything. This should increase cache locality for some problems (e.g. when using our generated grids) and we now have the guarantee that the iteration order for subdofhandlers...

awaiting review

The initial version of our topology was able to handle mixed dimensional constraints, but it was removed to obtain type stability in https://github.com/Ferrite-FEM/Ferrite.jl/pull/753 which made the topology construction a bit...

enhancement

I think it would be nice to develop an example where we show how to do p-multigrid in Ferrite. This technique is nice for matrix-free stuff (xref https://github.com/Ferrite-FEM/Ferrite.jl/pull/766), because the...

enhancement
feature

https://github.com/Ferrite-FEM/FerriteViz.jl/pull/51 revealed another problem with something seemingly simple (i.e. generating triangle grids). With the help of https://github.com/Ferrite-FEM/Ferrite.jl/pull/517 @koehlerson and I were able to track down issues in the build in...

enhancement
help wanted

Pressure handling does not work very consistently for now, because the current choice for the solver does not resolve the constant consistently.

bug

In https://github.com/Ferrite-FEM/Ferrite.jl/pull/780 Maxi develops the main infrastructure for "p4est-type" AMR~1 (which we currently name BGW internally, derived from the author names). In addition I am planning to implement "multilevel-type" AMR...

docs
AMR