-
Notifications
You must be signed in to change notification settings - Fork 46
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
Static Mesh Refinement #133
Comments
@asalmgren will this involve re-deriving all the flux computation for refined mesh since the indices will change? |
I'm not sure what you mean by that. Can you elaborate?
…On Fri, Oct 29, 2021 at 12:20 PM Pankaj Jha ***@***.***> wrote:
@asalmgren <https://github.com/asalmgren> will this involve re-deriving
all the flux computation for refined mesh since the indices will change?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#133 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACRE6YXYLFOWEBTKN2IXSVLUJLXZHANCNFSM5G6AFYQA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
Ann Almgren
Senior Scientist; CCSE Group Lead
Pronouns: she/her/hers
|
@asalmgren I meant if we will need to write the discretization schemes like this (https://erf.readthedocs.io/en/latest/NavierStokes_Discretization.html#momentum-conservation-u-momentum) at all the levels of refinement taking into account the indexing at that level. |
Yes -- the schemes can be used exactly as written -- I'm not sure what you
mean by "taking into account the indexing at that level"
Just FYI, we use a global index space, so the node i = 37 at level 0 would
be the same as the node i = 74 at refined level with refinement ratio 2.
Cell i = 37 at level 0 would correspond to cells i = 74 and i = 75 at level
1
When we're doing the time advance at level 1, we don't see level 0 data
directly -- we instead pre-fill ghost cells so that everything is in the
fine index space
Does that help?
…On Fri, Oct 29, 2021 at 12:33 PM Pankaj Jha ***@***.***> wrote:
@asalmgren <https://github.com/asalmgren> I meant if we will need to
write the discretization schemes like this (
https://erf.readthedocs.io/en/latest/NavierStokes_Discretization.html#momentum-conservation-u-momentum)
at all the levels of refinement taking into account the indexing at that
level.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#133 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACRE6YR7RHQO7WE3GHYMJQ3UJLZHPANCNFSM5G6AFYQA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
Ann Almgren
Senior Scientist; CCSE Group Lead
Pronouns: she/her/hers
|
Yes, thanks for clarification. |
Implement user-specifiable static mesh refinement.
Includes:
The text was updated successfully, but these errors were encountered: