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

Investigate use of couple variables for initializing material properties. #6760

Closed
aeslaughter opened this issue Apr 13, 2016 · 5 comments
Closed
Assignees
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

@aeslaughter
Copy link
Contributor

Description of the enhancement or error report

@WilkAndy reports that you cannot use the reference from coupledValue to in initQpStatefulProperties.

Rationale for the enhancement or information for reproducing the error

IC objects can not use Material objects, so it seems like the IC could/should be set prior to initializing materials.

Identified impact

(i.e. Internal object changes, limited interface changes, public API change, or a list of specific applications impacted)
This should help @WilkAndy do something.

@aeslaughter aeslaughter self-assigned this Apr 13, 2016
@aeslaughter aeslaughter added C: Framework T: defect An anomaly, which is anything that deviates from expectations. P: normal A defect affecting operation with a low possibility of significantly affects. labels Apr 13, 2016
@WilkAndy
Copy link
Contributor

Thanks @aeslaughter . I don't like your sentence "Material objects can not use variables" as that's exactly what i want to do. I'm really hoping it is a typo!!

@aeslaughter
Copy link
Contributor Author

@WilkAndy I fixed my typo.

@WilkAndy
Copy link
Contributor

Phew! I was sweating for a while there!

a

@permcody
Copy link
Member

So you're going to change order in initialSetup? Good luck. Don't forget to test Yak/Rattlesnake ;)

@aeslaughter
Copy link
Contributor Author

It is not the order, there is a missing reinitElem I have PR, but there is
one test failing on linux.

On Thu, Apr 14, 2016 at 7:06 AM, Cody Permann notifications@github.com
wrote:

So you're going to change order in initialSetup? Good luck. Don't forget
to test Yak/Rattlesnake ;)


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_idaholab_moose_issues_6760-23issuecomment-2D209933922&d=BQMCaQ&c=54IZrppPQZKX9mLzcGdPfFD1hxrcB__aEkJFOKJFd00&r=h7heP8xwI1i_HikChvhFbEBurKirgfOCdwgBxB9lM8c&m=jikTP-baAhML9IdDvhJ4Ci0KCp3bfQBrhK0nalOjk7k&s=pQ2m71vd9HZ8RL40shDwPqHm5ICh--Ci4lJFK6wflZU&e=

aeslaughter added a commit to aeslaughter/moose that referenced this issue Apr 14, 2016
WilkAndy pushed a commit to WilkAndy/moose that referenced this issue Apr 14, 2016
cpgr pushed a commit to cpgr/moose that referenced this issue May 4, 2016
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

3 participants