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

SysBoundary communicate VDFs only in smaller neighborhood #1049

Open
wants to merge 39 commits into
base: dev
Choose a base branch
from

Conversation

ykempf
Copy link
Contributor

@ykempf ykempf commented Nov 1, 2024

No description provided.

@ykempf ykempf closed this Nov 4, 2024
@ykempf
Copy link
Contributor Author

ykempf commented Nov 4, 2024

This is a subset of #1048 and will need more features/changes in any case.

@ykempf ykempf reopened this Nov 4, 2024
@ykempf
Copy link
Contributor Author

ykempf commented Nov 4, 2024

So this is still not doing fluffy copy, which is used in copysphere, correctly. Will be fixed soon. I came back to this branch/PR as I am not taking in everything that was pushed to #1048. Mainly, I let it create (local) VDFs and compute their moments when needed, instead of adding spaghetti to save on that. What's expensive ar second-neighbour VDFs and their communication, not the actual local L2 VDFs.

@@ -3474,6 +3474,20 @@ namespace SBC {

calculateCellMoments(&templateCell,true,false,true);

for (uint popID=0; popID<getObjectWrapper().particleSpecies.size(); ++popID) {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are these needed?

@@ -395,6 +394,10 @@ namespace SBC {
const uint popID,
const bool calculate_V_moments
) override;
virtual void setupL2OutflowAtRestart(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of having these warnings in all the "wrong" boundaries, I think it should exist in the base class as a warning and be just missing from all the others.

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

Successfully merging this pull request may close these issues.

2 participants