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
Error when aux depends on block restricted aux #9734
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
Thanks for the test case.
…On Wed, Aug 23, 2017 at 11:07 PM Topher Matthews ***@***.***> wrote:
Description of the enhancement or error report
When an aux depends on a block restricted aux, a moose assertion is thrown
when executing in dbg:
Assertion `i < _size' failed
Access out of bounds in MooseArray (i: 0 size: 0)
Rationale for the enhancement or information for reproducing the error
The simplest input deck can be run with any dbg executable:
[Mesh]
type = GeneratedMesh
nx = 2
ny = 2
dim = 2
[]
[MeshModifiers]
[./split]
type = SubdomainBoundingBox
block_id = 1
bottom_left = '0 0 0'
top_right = '0.5 0.5 0.5'
[../]
[]
[Variables]
[./var]
[../]
[]
[AuxVariables]
[./u]
block = '0 1'
[../]
[./v]
block = 1
[../]
[]
[Kernels]
[./var]
type = TimeDerivative
variable = var
[../]
[]
[AuxKernels]
[./u_aux]
type = ParsedAux
variable = u
args = v
function = v
[../]
[./v_aux]
type = ConstantAux
variable = v
[../]
[]
[Executioner]
type = Transient
[]
Identified impact
Is seems that this should throw a descriptive error, and perhaps not even
work in opt? This will help prevent errors and help debugging.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#9734>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC5XINMkLT0cmF9bMaT_vC959V3o0f_7ks5sbOjygaJpZM4PA1dr>
.
|
permcody
added
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.
labels
Aug 28, 2017
Fixed somewhere along the way:
|
this still happens in AD
|
I'll try and figure out a good input file |
It's something with |
lindsayad
added a commit
to lindsayad/moose
that referenced
this issue
May 17, 2022
Makes sure that variable dependencies have degrees of freedom on all nodes along the boundaries of a boundary restricted object Closes idaholab#9734
lindsayad
added a commit
to lindsayad/moose
that referenced
this issue
May 17, 2022
Makes sure that variable dependencies have degrees of freedom on all nodes along the boundaries of a boundary restricted object Closes idaholab#9734
lindsayad
added a commit
to lindsayad/moose
that referenced
this issue
May 18, 2022
Makes sure that variable dependencies have degrees of freedom on all nodes along the boundaries of a boundary restricted object Closes idaholab#9734
lindsayad
added a commit
to lindsayad/moose
that referenced
this issue
May 18, 2022
Makes sure that variable dependencies have degrees of freedom on all nodes along the boundaries of a boundary restricted object Closes idaholab#9734
lindsayad
added a commit
to lindsayad/moose
that referenced
this issue
May 18, 2022
Makes sure that variable dependencies have degrees of freedom on all nodes along the boundaries of a boundary restricted object Closes idaholab#9734
lindsayad
added a commit
to lindsayad/moose
that referenced
this issue
May 18, 2022
Makes sure that variable dependencies have degrees of freedom on all nodes along the boundaries of a boundary restricted object Closes idaholab#9734
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.
Description of the enhancement or error report
When an aux depends on a block restricted aux, a moose assertion is thrown when executing in dbg:
Rationale for the enhancement or information for reproducing the error
The simplest input deck can be run with any dbg executable:
Identified impact
Is seems that this should throw a descriptive error, and perhaps not even work in opt? This will help prevent errors and help debugging.
The text was updated successfully, but these errors were encountered: