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

Should we use a composition for Monge-Ampere? #24

Open
jwallwork23 opened this issue Jun 9, 2023 · 1 comment
Open

Should we use a composition for Monge-Ampere? #24

jwallwork23 opened this issue Jun 9, 2023 · 1 comment
Assignees
Labels
question Further information is requested
Milestone

Comments

@jwallwork23
Copy link
Member

If we apply the same monitor function to an adapted mesh, does the code DTRT?

@jwallwork23 jwallwork23 added the question Further information is requested label Jun 9, 2023
@jwallwork23 jwallwork23 added this to the Version 1 milestone Jun 9, 2023
@jwallwork23 jwallwork23 self-assigned this Jun 9, 2023
@jwallwork23
Copy link
Member Author

The question here wasn't sufficiently well formed for me to still understand what exactly was meant. Assuming that it is about "continuing" adaptation with a new Mover based on the adapted mesh from a different Mover, I don't think this really makes sense. See comment in #48.

If the question is about whether applying the same monitor function to two different (but topologically identical) meshes gives the same mesh then this is an interesting question. I expect that the answer is no because there are many ways that the mesh can be moved and the Monge-Ampere approach is just one "choice". In fact, since it's based on optimal transport theory, the origin mesh is "baked in" because it's all about moving the mesh with minimal "effort" (in some sense). However, it's plausible that we could add an extremely simple test (with one free DoF, say) to test this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
Development

No branches or pull requests

1 participant