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

Unique domain IDs #1230

Open
WillTrojak opened this issue Dec 1, 2023 · 1 comment
Open

Unique domain IDs #1230

WillTrojak opened this issue Dec 1, 2023 · 1 comment
Labels

Comments

@WillTrojak
Copy link
Contributor

WillTrojak commented Dec 1, 2023

In PR #1196 a check was added for unique domain IDs. In PyFR, for simplicity, we have been setting the domain ID to f'domain_{rank}_{element type}'. However #1196 assumes that the domain IDs are int32s.

See: ascent_main_runtime.cpp, line: 638

The rendering of ascent still seems fine (ie it doesn't seem to care that the domain IDs are strings) but it throws a warning that the domain IDs aren't unique.

Would it be possible to support non-integer domain IDs in the unique domain checking?

@cyrush
Copy link
Member

cyrush commented Dec 1, 2023

Hi @WillTrojak,

While I expect its not 100% clear from the docs, domain_ids are optional but when present are expected o be integers. I don't think we have strict checks b/c they are optional.

Why integers? domain_ids are used in more advanced parts of the Mesh Blueprint for info like domains connect, or how AMR domains nest, etc.

If you want to use strings, is it possible to store those as something the blueprint won't try to interpret like domain_name instead of domain_id?

@cyrush cyrush added the question label Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants