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

Compute Material Properties at DiracKernel points #2967

Merged
merged 7 commits into from
Apr 23, 2014

Conversation

jwpeterson
Copy link
Member

This branch adds the ability to evaluate and use material properties at the points of DiracKernels, which was not supported before. Stateful material properties are currently not supported for DiracKernels, however. If you try to access one from a DiracKernel, MOOSE will throw an error.

@WilkAndy, this branch causes two of your tests

richards:dirac.test_bh07
richards:gravity_head_2.test_gh02

to diff for me. This may due to them not using correct MaterialProperty values before, so perhaps those tests could just be re-golded. Let me know if you have any questions.

Refs #2379.

You can now specify whether or not the 'swap' step for stateful
materials occurs.

Refs idaholab#2379.
@moosebuild
Copy link
Contributor

Results of testing 62f59db using moose_PR_pre_test recipe:

Passed on: linux

View the results here: https://www.moosebuild.com/view_job/1498

@moosebuild
Copy link
Contributor

Results of testing 62f59db using moose_PR_test recipe:

Failed on: linux

View the results here: https://www.moosebuild.com/view_job/1499

@jwpeterson
Copy link
Member Author

OK @WilkAndy it was just the dirac.test_bh07 test which exodiffed on moosebuild, and you can see the diff on the link above. Let me know if you are OK with regolding and I will add another patch to this PR, I can also send you the Exodus file I get on my system if you'd like to take a closer look.

@WilkAndy
Copy link
Contributor

Yes, please re-gold and send me the exodus file, John. With this PR I will have to re-explore all my dirac tests anyway, but I need the PR into devel before that is easy for me to do.

a

From: jwpeterson <notifications@github.commailto:notifications@github.com>
Reply-To: idaholab/moose <reply@reply.github.commailto:reply@reply.github.com>
Date: Thursday, 24 April 2014 6:10 am
To: idaholab/moose <moose@noreply.github.commailto:moose@noreply.github.com>
Cc: Andy Wilkins <Andrew.Wilkins@csiro.aumailto:Andrew.Wilkins@csiro.au>
Subject: Re: [moose] Compute Material Properties at DiracKernel points (#2967)

OK @WilkAndyhttps://github.com/WilkAndy it was just the dirac.test_bh07 test which exodiffed on moosebuild, and you can see the diff on the link above. Let me know if you are OK with regolding and I will add another patch to this PR, I can also send you the Exodus file I get on my system if you'd like to take a closer look.


Reply to this email directly or view it on GitHubhttps://github.com//pull/2967#issuecomment-41208546.

@jwpeterson
Copy link
Member Author

Yes, please re-gold and send me the exodus file, John. With this PR I will have to re-explore all my dirac tests anyway, but I need the PR into devel before that is easy for me to do.

OK, will do.

John Peterson added 2 commits April 23, 2014 14:54
* Reinitialize materials before computing Dirac kernels, but only
  if those DiracKernels actually call getMaterialProperty().

* Adding MaterialPropertyInterface::statefulPropertiesAllowed(bool).
  This allows classes derived from MaterialPropertyInterface to declare
  that they do not work with stateful material properties.  The only
  class which currently uses this functionality is the DiracKernel.
  The various getMaterialProperty*() interfaces have been updated to
  throw an error is stateful material properties are not allowed and the
  user asks for them.

  Note that only the MaterialPropertyStorage object knows if it has
  stateful material properties, so we had to provide an accessor from
  the MaterialData object which contains it that could be accessed by
  the MaterialPropertyInterface.

Refs idaholab#2379.
Only swap back if the MaterialData has been swapped in the first place.

Refs idaholab#2379.
if ((*dirac_kernel_it)->getMaterialPropertyCalled())
{
need_reinit_materials = true;
break;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hah - I was trying to leave a comment about this issue - but you spotted it before I did and fixed it ;-)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Damn, tried to sneak that one in there...

@moosebuild
Copy link
Contributor

Results of testing a1b0d02 using moose_PR_pre_test recipe:

Passed on: linux

View the results here: https://www.moosebuild.com/view_job/1515


// Note that we do not call swapBackMaterials() here as they were
// never swapped in the first place. This avoids messing up
// stored values of stateful material properties.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea to put this comment here!

@moosebuild
Copy link
Contributor

Results of testing a1b0d02 using moose_PR_test recipe:

Passed on: linux

View the results here: https://www.moosebuild.com/view_job/1516

John Peterson added 4 commits April 23, 2014 15:44
It is a DiracKernel test that uses a MaterialProperty, as has been
implemented by an earlier patch on this branch.

If uncommented, the print statement in
MaterialPointSource::computeQpResidual() should show that the
MaterialProperty is being correctly evaluated at the DiracKernel
point.

Refs idaholab#2379.
stateful material property with a DiracKernel.

Refs idaholab#2379.
@moosebuild
Copy link
Contributor

Results of testing 3ed6ece using moose_PR_pre_test recipe:

Passed on: linux

View the results here: https://www.moosebuild.com/view_job/1519

@moosebuild
Copy link
Contributor

Results of testing 3ed6ece using moose_PR_test recipe:

Passed on: linux

View the results here: https://www.moosebuild.com/view_job/1520

friedmud added a commit that referenced this pull request Apr 23, 2014
Compute Material Properties at DiracKernel points
@friedmud friedmud merged commit 375bfae into idaholab:devel Apr 23, 2014
@friedmud
Copy link
Contributor

Great job John! Thanks for doing this!

@WilkAndy
Copy link
Contributor

Yes, thanks John,. I’ll look at that bh07.e you sent in more detail over the coming days, but by eye it looks absolutely fine. Also all my other dirac tests will need to be re-visited, and I will probably make some more now. I’m so pleased this Materials stuff is done, thanks,

a

From: Derek Gaston <notifications@github.commailto:notifications@github.com>
Reply-To: idaholab/moose <reply@reply.github.commailto:reply@reply.github.com>
Date: Thursday, 24 April 2014 8:04 am
To: idaholab/moose <moose@noreply.github.commailto:moose@noreply.github.com>
Cc: Andy Wilkins <Andrew.Wilkins@csiro.aumailto:Andrew.Wilkins@csiro.au>
Subject: Re: [moose] Compute Material Properties at DiracKernel points (#2967)

Great job John! Thanks for doing this!


Reply to this email directly or view it on GitHubhttps://github.com//pull/2967#issuecomment-41220697.

@jwpeterson jwpeterson deleted the material_point_source branch April 24, 2014 21:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: Framework T: task An enhancement to the software.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants