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

level ghost fill pattern #223

Open
nicolasaunai opened this issue Mar 28, 2023 · 0 comments
Open

level ghost fill pattern #223

nicolasaunai opened this issue Mar 28, 2023 · 0 comments

Comments

@nicolasaunai
Copy link

This is somewhat related to the discussion in #170.

Using a basic schedule

algo->createSchedule(level, level->getNextCoarserHierarchyLevelNumber(), hierarchy),

it seems that the nodes exactly on the border of the coarse-to-fine boundary are overwritten. Even though we provide a VariableFillPattern that explicitly sets overwrite_interior=false.

#170 says, calcluateOverlap methods is for overlaps within the same level of resolution.,

so I think what happens is that overlaps for coarse-to-fine areas are found by the Geometry setUpOverlap (?) which disregards our overwrite_interior trick.

I would like not to overwrite level border nodes, and assign only the "real" ghost nodes.

I had the idea of using two schedules, one restricted to the current level, with overwrite_interior set to false.
And a second for level borders exclusively, and that would be done by using a PatchLevelBorderFillPattern.

But it seems that this fill pattern also lead to the overwritting of border nodes.

This is not clear to me because the doc says :

The fill boxes will consist of the ghost regions lying outside of the level interior

and comments in the code :

* To get the level border, grow each patch box and remove * the level from it.

I was thus expecting the border node not to be overwritten.

Is that a bug or am I misunderstanding and that fill pattern intends to overwrite the border node?
Can you help to adapt that fill pattern to a new one that would only leave real ghost nodes ?

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