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.

Sign up for GitHub

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

Jump to bottom

Force Output Dimension #9205

Closed
friedmud opened this issue Jun 1, 2017 · 1 comment
Closed

Force Output Dimension #9205

friedmud opened this issue Jun 1, 2017 · 1 comment
Labels
C: Framework Good first issue P: normal A defect affecting operation with a low possibility of significantly affects. T: task An enhancement to the software.

Comments

@friedmud
Copy link
Contributor

friedmud commented Jun 1, 2017

Description of the enhancement or error report

Sometimes you need to be able to force the output dimension of an Exodus mesh. I have a problem I'm currently running that reads in a 2D Mesh and does a 2D solve... but generates 3D displacement fields (think "elevations" on a 2D mesh). Those displacement fields are only properly read by Peacock/Paraview if the output mesh dimension is also 3.

We already have Outputs/use_problem_dimension... but it doesn't cover this case.

I propose having a MooseEnum driven option called output_dimension. The options can be default, problem_dimension, 1, 2, 3

This would supersede the use_problem_dimension option (it would get deprecated). You would get that behavior by specifying output_dimension = problem_dimension.

Rationale for the enhancement or information for reproducing the error

Sometimes you need full control over the output dimension.

Identified impact

One parameter would get deprecated. That deprecated parameter should be able to live on for a long time beside the new option.
@friedmud friedmud added C: Framework Good first issue P: normal A defect affecting operation with a low possibility of significantly affects. T: task An enhancement to the software. labels Jun 1, 2017
@friedmud
Copy link
Contributor Author

friedmud commented Jun 1, 2017

This should also ref #5821 and #5822

friedmud added a commit to friedmud/moose that referenced this issue Feb 7, 2018
@friedmud
Allow the specification of output dimension directly closes idaholab#…
9fed351 
…9205
@friedmud friedmud mentioned this issue Feb 7, 2018
Merged
friedmud added a commit to friedmud/moose that referenced this issue Feb 7, 2018
@friedmud
Add some doco refs idaholab#9205
14c52d7
andrsd added a commit to andrsd/moose that referenced this issue Feb 8, 2018
@andrsd
Adding API for setting output dimension
083b0f9 
When using lower dimensional elements in higher dimensional space, an
application might require to force the dimension of the Exodus output.
If this is supposed to happen via an action, an API for this is needed.
The manipulation of input parameters is not possible, becuase the object
already exists.

Also, requiring users to enter an extra line into all their input files
is not friendly, becuase we know what the dimension always is, so we
just need to set it for them.

Refs idaholab#9205
@andrsd andrsd mentioned this issue Feb 8, 2018
Merged
andrsd added a commit to andrsd/moose that referenced this issue Feb 8, 2018
@andrsd
Adding API for setting output dimension
a63fb3c 
When using lower dimensional elements in higher dimensional space, an
application might require to force the dimension of the Exodus output.
If this is supposed to happen via an action, an API for this is needed.
The manipulation of input parameters is not possible, becuase the object
already exists.

Also, requiring users to enter an extra line into all their input files
is not friendly, becuase we know what the dimension always is, so we
just need to set it for them.

Refs idaholab#9205
andrsd added a commit to andrsd/moose that referenced this issue Feb 9, 2018
@andrsd
Adding API for setting output dimension
85b1121 
When using lower dimensional elements in higher dimensional space, an
application might require to force the dimension of the Exodus output.
If this is supposed to happen via an action, an API for this is needed.
The manipulation of input parameters is not possible, becuase the object
already exists.

Also, requiring users to enter an extra line into all their input files
is not friendly, becuase we know what the dimension always is, so we
just need to set it for them.

Refs idaholab#9205
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C: Framework Good first issue P: normal A defect affecting operation with a low possibility of significantly affects. T: task An enhancement to the software.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@friedmud