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

Bounds Vectors #951

Closed
friedmud opened this issue Feb 14, 2014 · 3 comments
Closed

Bounds Vectors #951

friedmud opened this issue Feb 14, 2014 · 3 comments
Assignees
Labels
C: Framework 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

Dmitry needs two solution vector sized vectors for SNESVI. One for the lower bound and one for the upper bound. He also needs a way to fill them with the information.

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

Because this whole idea is still in flux I'm going to do a quick implementation that relies on the Auxiliary Kernel system. The idea is to make a nodal aux kernel that, instead of filling in it's own solution vector, it will fill in the lower and upper bound vectors for the variable we tell it.

To tell it the right variable we're going to use the coupling system. This will give us access access to that variable's dofs on that node. Note that this whole thing will only work for Lagrange variables... but that's ok because this is just a testing system.

As for actually adding the vectors, I'm going to add a new main block called [Bounds] with an action associated with it that adds the bounds vectors at the right moment.

@friedmud
Copy link
Contributor Author

In 72ae577:

add initial implementation allowing specification of bounds on a variable references #951

@friedmud
Copy link
Contributor Author

Marking this as fixed... we'll open another ticket if we need something more.

friedmud added a commit that referenced this issue Feb 14, 2014
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: task An enhancement to the software.
Projects
None yet
Development

No branches or pull requests

1 participant