Skip to content
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

Rewrite FEValues/FiniteElement/Mapping interfaces #1198

Closed
bangerth opened this issue Jul 26, 2015 · 5 comments
Closed

Rewrite FEValues/FiniteElement/Mapping interfaces #1198

bangerth opened this issue Jul 26, 2015 · 5 comments

Comments

@bangerth
Copy link
Member

Fixing #1152, I realized again that I do not understand (and have never really understood) the way FEValues, FiniteElement and Mapping classes interact. Looking at how all of this works I find that much isn't well documented, some of the interfaces could be improved, etc.

This issue is simply a catch-all for all of the patches I'm doing to improve the situation.

@guidokanschat
Copy link
Contributor

I do not believe we should invest heavily in FEValues anymore. It is inherently memory bound and does not support tensor product integration like it is used in MatrixFree. Let's rather focus on replacing it and while we are doing so, separate Mapping in a way consistent with manifold descriptions.

@bangerth
Copy link
Member Author

Fortunately, ours is a project big enough so that different people can work on different parts :-) (I'm not implementing new functionality, just cleaning up interfaces.)

@bangerth
Copy link
Member Author

bangerth commented Feb 9, 2016

This is as far as I intend to take it for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants