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

Allow block IDs of 0 and non-contiguous subdomain IDs #38

Open
aprilnovak opened this issue Jan 12, 2023 · 1 comment
Open

Allow block IDs of 0 and non-contiguous subdomain IDs #38

aprilnovak opened this issue Jan 12, 2023 · 1 comment

Comments

@aprilnovak
Copy link
Contributor

MOOSE technically allows blocks to have a subdomain ID of 0, but Aurora will throw this error:

if(blk < 1 || blk > maxBlockID){
          std::string errmsg="Block ID "+std::to_string(blk)+" for material "+mat
            +" is inconsistent with mesh (max subdomains = "
            +std::to_string(maxBlockID)+")";
            mooseError(errmsg);
        }
@aprilnovak
Copy link
Contributor Author

More generally, Aurora seems to require that block IDs in the [Mesh] are ordered as 1, 2, 3, ... sequentially. However, MOOSE itself does not mandate this and use any unsigned integer values to represent the subdomains.

@aprilnovak aprilnovak changed the title Allow block IDs of 0 Allow block IDs of 0 and non-contiguous subdomain IDs Jan 12, 2023
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