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

Fix LaplacianJumpIndicator test with Parallel Mesh #2190

Closed
friedmud opened this issue Feb 14, 2014 · 1 comment
Closed

Fix LaplacianJumpIndicator test with Parallel Mesh #2190

friedmud opened this issue Feb 14, 2014 · 1 comment
Labels
C: Framework P: normal A defect affecting operation with a low possibility of significantly affects. T: defect An anomaly, which is anything that deviates from expectations.

Comments

@friedmud
Copy link
Contributor

It is giving incorrect values for the second derivatives with Parallel Mesh - I can't see why so for now it's been marked as distribution=serial

@ghost ghost assigned friedmud Feb 14, 2014
@friedmud
Copy link
Contributor Author

In 97eecc9:

error if you try to use laplacianjumpindicator with parallelmesh refs #2190

@friedmud friedmud removed their assignment Apr 3, 2014
permcody added a commit to permcody/moose that referenced this issue Nov 9, 2017
Make sure it works for recover and distributed mesh.
closes idaholab#2190
permcody added a commit to permcody/moose that referenced this issue Nov 13, 2017
Make sure it works for recover and distributed mesh.
closes idaholab#2190
permcody added a commit to permcody/moose that referenced this issue Nov 13, 2017
Make sure it works for recover and distributed mesh.
closes idaholab#2190
permcody added a commit to permcody/moose that referenced this issue Nov 13, 2017
Make sure it works for recover and distributed mesh.
closes idaholab#2190
permcody added a commit to permcody/moose that referenced this issue Nov 14, 2017
Make sure it works for recover and distributed mesh.
closes idaholab#2190
permcody added a commit to permcody/moose that referenced this issue Nov 15, 2017
Make sure it works for recover and distributed mesh.
closes idaholab#2190
jwpeterson added a commit to jwpeterson/moose that referenced this issue Nov 15, 2017
jwpeterson added a commit to jwpeterson/moose that referenced this issue Nov 17, 2017
* Drop redundant periodic, FunctionNeumannBCs, and associated Functions
  since they are not needed for anything.
* We have to use FunctionPenaltyDirichletBC with Hermites because
  MOOSE does not correctly handle the setting of DirichletBCs for
  HERMITE elements.
* Switch test to use new [Adaptivity] system. Note that this changes
  this output of the 'dofs' postprocessor since there are now
  elemental dofs for the marker variable in the system. This required
  regolding the test, but I checked to make sure that the solutions
  were still the same.
* Drop gold files that were not used for exodiffing.

Refs idaholab#2190.
jwpeterson added a commit to jwpeterson/moose that referenced this issue Nov 17, 2017
* Drop unused BCs and associated Functions. If you use periodic BCs, you
  should not apply any other kind of BC on that boundary.
* Update to new [Adaptivity] block. This changes the number of dofs
  produced by the test, hence I also regolded.
* Reduce the order of the custom quadrature rule used. This seemed to
  make no difference in the results and might speed up the test just a
  bit.

Refs idaholab#2190.
jwpeterson added a commit to jwpeterson/moose that referenced this issue Nov 17, 2017
* Drop redundant periodic, FunctionNeumannBCs, and associated Functions.
* We have to use FunctionPenaltyDirichletBC with Hermites because
  MOOSE does not correctly handle the setting of DirichletBCs for
  HERMITE elements.
* Switch test to use new [Adaptivity] system. Note that this changes
  this output of the 'dofs' postprocessor since there are now
  elemental dofs for the marker variable in the system. This required
  regolding the tests, but I checked to make sure that the solutions
  were still the same.
* Drop gold files that were not used for anything.
* If you use periodic BCs, you should not apply any other kind of BC
  on that boundary.
* Reduce the order of the custom quadrature rule used. This seemed to
  make no difference in the results and might speed up the test just a
  bit.

Refs idaholab#2190.
jwpeterson added a commit to jwpeterson/moose that referenced this issue Nov 17, 2017
These Kernels/BCs are needed for properly testing the
LaplacianJumpIndicator, but they are probably general enough that they
could be added to MOOSE proper, if desired.

Refs idaholab#2190.
jwpeterson added a commit to jwpeterson/moose that referenced this issue Nov 17, 2017
These new tests are based on the Biharmonic equation (and its
transient variant) so the Laplacian jump indicator is appropriate for
estimating the error.

In the process of developing these tests, it was discovered that MOOSE
is not currently imposing Dirichlet BCs for Hermite elements
correctly. Specifically, MOOSE constrains only the *value* degrees of
freedom when Dirichlet BCs are imposed, but setting BCs for Hermite
elements involves the gradient degrees of freedom as well, according
to @roystgnr. The current workaround is to use a penalty approach for
enforcing the boundary conditions, but this comes with the obvious
drawbacks of dramatically increasing the initial residual and changing
the conditioning of the system.

Refs idaholab#2190.
jwpeterson added a commit to jwpeterson/moose that referenced this issue Nov 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: Framework P: normal A defect affecting operation with a low possibility of significantly affects. T: defect An anomaly, which is anything that deviates from expectations.
Projects
None yet
Development

No branches or pull requests

1 participant