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
Allow SpatialUserObjectVectorPostprocessor to get points from UO #18931
Labels
T: task
An enhancement to the software.
Comments
aprilnovak
added a commit
to aprilnovak/moose
that referenced
this issue
Sep 27, 2021
aprilnovak
added a commit
to aprilnovak/moose
that referenced
this issue
Sep 27, 2021
…automate points. Refs idaholab#18931
aprilnovak
added a commit
to aprilnovak/moose
that referenced
this issue
Sep 27, 2021
aprilnovak
added a commit
to aprilnovak/moose
that referenced
this issue
Sep 27, 2021
aprilnovak
added a commit
to aprilnovak/moose
that referenced
this issue
Sep 27, 2021
aprilnovak
added a commit
to aprilnovak/moose
that referenced
this issue
Sep 27, 2021
aprilnovak
added a commit
to aprilnovak/moose
that referenced
this issue
Sep 27, 2021
aprilnovak
added a commit
to aprilnovak/moose
that referenced
this issue
Sep 27, 2021
aprilnovak
added a commit
to aprilnovak/moose
that referenced
this issue
Sep 27, 2021
aprilnovak
added a commit
to aprilnovak/moose
that referenced
this issue
Sep 27, 2021
aprilnovak
added a commit
to aprilnovak/moose
that referenced
this issue
Sep 27, 2021
aprilnovak
added a commit
to aprilnovak/moose
that referenced
this issue
Sep 27, 2021
aprilnovak
pushed a commit
to aprilnovak/moose
that referenced
this issue
Sep 27, 2021
aprilnovak
added a commit
to aprilnovak/moose
that referenced
this issue
Sep 27, 2021
aprilnovak
added a commit
to aprilnovak/moose
that referenced
this issue
Sep 27, 2021
aprilnovak
added a commit
to aprilnovak/moose
that referenced
this issue
Sep 28, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reason
The
SpatialUserObjectVectorPostprocessor
lets you specify a number ofpoints
at which to output the value of a spatial user object. For the spatial user objects of typeNearestPointLayered...
, there is one unique value of the user object innum_points * num_layers
"bins." For instance, if the user object is defined like this:this will result in 12 bin integrals (4 points times 3 layers). If you wanted to get the value for each user object in the
SpatialUserObjectVectorPostprocessor
, you'd need to provide:Writing a script or manually typing out these points is cumbersome. In Cardinal, we have a spatial user object that defines the "nearest point" bins based on a subchannel discretization, which is even more tedious to provide the points to the
SpatialUserObjectVectorPostprocessor
because the points themselves are never provided explicitly to the spatial UO.Design
Add a
UserObject::spatialPoints()
interface that provides points that theSpatialUserObjectVectorPostprocessor
can use instead of the user providing something viapoints
orpoints_file
. For theNearestPointLayered...
user objects, this interface should provide thepoints
in the abovespatial_manually_provided
VPP example.Impact
Big improvement in usability for spatial user objects in Cardinal. New feature.
The text was updated successfully, but these errors were encountered: