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

Add Mesh method to get all possible boundary regions #2307

Merged
merged 3 commits into from
May 7, 2021

Conversation

ZedThree
Copy link
Member

@ZedThree ZedThree commented May 7, 2021

Add a method to return a set of all possible boundary region names in a given configuration.

Merging into #2245 to reduce diff

Needed for #2210

@ZedThree ZedThree added this to the BOUT-5.0 milestone May 7, 2021
// each possible boundary. We only need to do this at PE_XIND==0, as
// the other X boundary is covered by the case above
for (const auto& y_index :
{0, jyseps1_1, jyseps1_2, ny_inner - 1, ny_inner, jyseps2_1, jyseps2_2, ny - 1}) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Is it necessary to do jyseps* here? I think the targets (where we actually apply y-boundary conditions) are only at 0, ny-1, and (if jyseps2_1==jyseps1_2) ny_inner-1 and ny_inner.

Copy link
Member Author

Choose a reason for hiding this comment

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

It's definitely possible there's a smaller set we can check, but we also need to check for any inner x-boundary, so I think we do need to check at least one jyseps.

Copy link
Contributor

Choose a reason for hiding this comment

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

ah, right. makes sense!

@ZedThree ZedThree merged commit 3f0a33b into split-boutmesh-load May 7, 2021
@ZedThree ZedThree deleted the boutmesh-get-possible-boundaries branch May 7, 2021 14:07
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.

None yet

2 participants