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
Range checking for vector parameters #3988
Labels
C: Framework
P: normal
A defect affecting operation with a low possibility of significantly affects.
T: task
An enhancement to the software.
Comments
dschwen
added a commit
to dschwen/moose
that referenced
this issue
Oct 3, 2014
dschwen
added a commit
to dschwen/moose
that referenced
this issue
Oct 3, 2014
dschwen
added a commit
to dschwen/moose
that referenced
this issue
Oct 3, 2014
dschwen
added a commit
to dschwen/moose
that referenced
this issue
Oct 3, 2014
dschwen
added a commit
to dschwen/moose
that referenced
this issue
Oct 4, 2014
dschwen
added a commit
to dschwen/moose
that referenced
this issue
Oct 5, 2014
permcody
added
C: Framework
P: normal
A defect affecting operation with a low possibility of significantly affects.
T: task
An enhancement to the software.
labels
Oct 6, 2014
dschwen
added a commit
to dschwen/moose
that referenced
this issue
Oct 6, 2014
dschwen
added a commit
to dschwen/moose
that referenced
this issue
Oct 6, 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.
I'm implementing range checking for std::vector type parameters. I want three types of checks
In the existing range check function one FParser variable is defined: the parameter short_name. The vector range checking will make three kinds of variables available short_name (which will be iterated and checked for every element of the vector), short_name_i (where i is a component index into the vector), and short_name_size which is the length of the vector.
The text was updated successfully, but these errors were encountered: