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

Combined distance policy #154

Open
gasteigerjo opened this issue Dec 5, 2016 · 0 comments
Open

Combined distance policy #154

gasteigerjo opened this issue Dec 5, 2016 · 0 comments

Comments

@gasteigerjo
Copy link

Using the periodic_distance policy everywhere introduces significant overhead, since this method is very central to the package. In the inner cells, a normal cartesian distance would suffice.
Furthermore, I am working on an additional boundary condition right now, that further complicates the distance calculation and introduces more overhead.

Therefore, I propose a combined distance policy. Using this policy, one (simple) distance policy for inner cells can be set and additional ones for each boundary (i.e. x, y and z, maybe even x+/x-, y+/y- and z+/z-). Using a combined distance policy as an interface between CellLists and DistanceInterface reduces the refactoring necessary to a minimum and enables extensibility in the future.

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

No branches or pull requests

1 participant