- fieldField to apply this object to
C++ Type:MooseEnum
Controllable:No
Description:Field to apply this object to
- pointThe physical point where the field will be evaluated
C++ Type:libMesh::Point
Controllable:No
Description:The physical point where the field will be evaluated
NekPointValue
Uses NekRS's pointInterpolation to query the NekRS solution at a point (does not need to be a grid point).
Description
This postprocessor interpolates the NekRS solution onto a given point (using the actual NekRS solution). The provided point does not need to be a GLL point.
The field is specified with the field parameter, which may be one of:
pressure: pressuretemperature: temperaturevelocity: magnitude of velocityvelocity_x: -component of velocityvelocity_y: -component of velocityvelocity_z: -component of velocityvelocity_x_squared: -component of velocity, squaredvelocity_y_squared: -component of velocity, squaredvelocity_z_squared: -component of velocity, squaredvelocity_component: velocity vector dotted against another vectorscalar01: first non-temperature passive scalarscalar02: second non-temperature passive scalarscalar03: third non-temperature passive scalarunity: the value 1.0zero: the value 0.0 (this is typically used when combining with a function shift, to only apply the operation to the function)
If running NekRS in non-dimensional form (and you have indicated the appropriate nondimensional scales with the Dimensionalize sub-block for the [Problem]) then the value of this object is shown in dimensional units.
A function may also optionally be provided; this function, like all quantities in Cardinal input files, is given in dimensional form. The value at the point is then returned as , where is the field at the point of interest (after being dimensionalized) and is the function at that same point. If the function depends on time, that time is either the time of the start of the next timestep (if using the default of execute_on = timestep_end), or the time of the current timestep (if using execute_on = timestep_begin).
Example Input Syntax
As an example, the following code snippet will interpolate the spectral NekRS solution onto a provided point.
[Postprocessors<<<{"href": "../../syntax/Postprocessors/index.html"}>>>]
[vx]
type = NekPointValue<<<{"description": "Uses NekRS's pointInterpolation to query the NekRS solution at a point (does not need to be a grid point).", "href": "NekPointValue.html"}>>>
field<<<{"description": "Field to apply this object to"}>>> = velocity_x
point<<<{"description": "The physical point where the field will be evaluated"}>>> = '0.25 0.3 0.27'
[]
[vy]
type = NekPointValue<<<{"description": "Uses NekRS's pointInterpolation to query the NekRS solution at a point (does not need to be a grid point).", "href": "NekPointValue.html"}>>>
field<<<{"description": "Field to apply this object to"}>>> = velocity_y
point<<<{"description": "The physical point where the field will be evaluated"}>>> = '0.25 0.3 0.27'
[]
[vz]
type = NekPointValue<<<{"description": "Uses NekRS's pointInterpolation to query the NekRS solution at a point (does not need to be a grid point).", "href": "NekPointValue.html"}>>>
field<<<{"description": "Field to apply this object to"}>>> = velocity_z
point<<<{"description": "The physical point where the field will be evaluated"}>>> = '0.25 0.3 0.27'
[]
[comp]
type = NekPointValue<<<{"description": "Uses NekRS's pointInterpolation to query the NekRS solution at a point (does not need to be a grid point).", "href": "NekPointValue.html"}>>>
field<<<{"description": "Field to apply this object to"}>>> = velocity_component
velocity_direction<<<{"description": "Unit vector to dot with velocity, for 'field = velocity_component'. For example, velocity_direction = '1 1 0' will get the velocity dotted with (1/sqrt(2), 1/sqrt(2), 0)."}>>> = '0.5 0.5 0.5'
point<<<{"description": "The physical point where the field will be evaluated"}>>> = '0.25 0.3 0.27'
[]
[vx2]
type = NekPointValue<<<{"description": "Uses NekRS's pointInterpolation to query the NekRS solution at a point (does not need to be a grid point).", "href": "NekPointValue.html"}>>>
field<<<{"description": "Field to apply this object to"}>>> = velocity_x_squared
point<<<{"description": "The physical point where the field will be evaluated"}>>> = '0.25 0.3 0.27'
[]
[vy2]
type = NekPointValue<<<{"description": "Uses NekRS's pointInterpolation to query the NekRS solution at a point (does not need to be a grid point).", "href": "NekPointValue.html"}>>>
field<<<{"description": "Field to apply this object to"}>>> = velocity_y_squared
point<<<{"description": "The physical point where the field will be evaluated"}>>> = '0.25 0.3 0.27'
[]
[vz2]
type = NekPointValue<<<{"description": "Uses NekRS's pointInterpolation to query the NekRS solution at a point (does not need to be a grid point).", "href": "NekPointValue.html"}>>>
field<<<{"description": "Field to apply this object to"}>>> = velocity_z_squared
point<<<{"description": "The physical point where the field will be evaluated"}>>> = '0.25 0.3 0.27'
[]
[vel]
type = NekPointValue<<<{"description": "Uses NekRS's pointInterpolation to query the NekRS solution at a point (does not need to be a grid point).", "href": "NekPointValue.html"}>>>
field<<<{"description": "Field to apply this object to"}>>> = velocity
point<<<{"description": "The physical point where the field will be evaluated"}>>> = '0.25 0.3 0.27'
[]
[temp]
type = NekPointValue<<<{"description": "Uses NekRS's pointInterpolation to query the NekRS solution at a point (does not need to be a grid point).", "href": "NekPointValue.html"}>>>
field<<<{"description": "Field to apply this object to"}>>> = temperature
point<<<{"description": "The physical point where the field will be evaluated"}>>> = '0.25 0.3 0.27'
[]
[p]
type = NekPointValue<<<{"description": "Uses NekRS's pointInterpolation to query the NekRS solution at a point (does not need to be a grid point).", "href": "NekPointValue.html"}>>>
field<<<{"description": "Field to apply this object to"}>>> = pressure
point<<<{"description": "The physical point where the field will be evaluated"}>>> = '0.25 0.3 0.27'
[]
[scalar01]
type = NekPointValue<<<{"description": "Uses NekRS's pointInterpolation to query the NekRS solution at a point (does not need to be a grid point).", "href": "NekPointValue.html"}>>>
field<<<{"description": "Field to apply this object to"}>>> = scalar01
point<<<{"description": "The physical point where the field will be evaluated"}>>> = '0.25 0.3 0.27'
[]
[scalar02]
type = NekPointValue<<<{"description": "Uses NekRS's pointInterpolation to query the NekRS solution at a point (does not need to be a grid point).", "href": "NekPointValue.html"}>>>
field<<<{"description": "Field to apply this object to"}>>> = scalar02
point<<<{"description": "The physical point where the field will be evaluated"}>>> = '0.25 0.3 0.27'
[]
[scalar03]
type = NekPointValue<<<{"description": "Uses NekRS's pointInterpolation to query the NekRS solution at a point (does not need to be a grid point).", "href": "NekPointValue.html"}>>>
field<<<{"description": "Field to apply this object to"}>>> = scalar03
point<<<{"description": "The physical point where the field will be evaluated"}>>> = '0.25 0.3 0.27'
[]
[unity]
type = NekPointValue<<<{"description": "Uses NekRS's pointInterpolation to query the NekRS solution at a point (does not need to be a grid point).", "href": "NekPointValue.html"}>>>
field<<<{"description": "Field to apply this object to"}>>> = unity
point<<<{"description": "The physical point where the field will be evaluated"}>>> = '0.25 0.3 0.27'
[]
[usrwrk00]
type = NekPointValue<<<{"description": "Uses NekRS's pointInterpolation to query the NekRS solution at a point (does not need to be a grid point).", "href": "NekPointValue.html"}>>>
field<<<{"description": "Field to apply this object to"}>>> = usrwrk00
point<<<{"description": "The physical point where the field will be evaluated"}>>> = '0.25 0.3 0.27'
[]
[usrwrk01]
type = NekPointValue<<<{"description": "Uses NekRS's pointInterpolation to query the NekRS solution at a point (does not need to be a grid point).", "href": "NekPointValue.html"}>>>
field<<<{"description": "Field to apply this object to"}>>> = usrwrk01
point<<<{"description": "The physical point where the field will be evaluated"}>>> = '0.25 0.3 0.27'
[]
[usrwrk02]
type = NekPointValue<<<{"description": "Uses NekRS's pointInterpolation to query the NekRS solution at a point (does not need to be a grid point).", "href": "NekPointValue.html"}>>>
field<<<{"description": "Field to apply this object to"}>>> = usrwrk02
point<<<{"description": "The physical point where the field will be evaluated"}>>> = '0.25 0.3 0.27'
[]
# the value of _t used when evaluating the function will either be the time of the time step (timestep_begin)
# or at the end of the timestep after time has already been incremented (timestep_end). Also, there is no
# need to test all the fields individually, since the shift is applied after dimensionalizing (equivalent
# operation for every field).
[compf_end]
type = NekPointValue<<<{"description": "Uses NekRS's pointInterpolation to query the NekRS solution at a point (does not need to be a grid point).", "href": "NekPointValue.html"}>>>
field<<<{"description": "Field to apply this object to"}>>> = velocity_component
velocity_direction<<<{"description": "Unit vector to dot with velocity, for 'field = velocity_component'. For example, velocity_direction = '1 1 0' will get the velocity dotted with (1/sqrt(2), 1/sqrt(2), 0)."}>>> = '0.5 0.5 0.5'
point<<<{"description": "The physical point where the field will be evaluated"}>>> = '0.25 0.3 0.27'
function<<<{"description": "Function to shift the field by, when applying this object. For example, if 'field = temperature', using this parameter will apply this object to the new combined quantity 'temperature - f', where 'f' is this shifting function."}>>> = f
execute_on<<<{"description": "The list of flag(s) indicating when this object should be executed. For a description of each flag, see https://mooseframework.inl.gov/source/interfaces/SetupInterface.html."}>>> = timestep_end
[]
[compf_begin]
type = NekPointValue<<<{"description": "Uses NekRS's pointInterpolation to query the NekRS solution at a point (does not need to be a grid point).", "href": "NekPointValue.html"}>>>
field<<<{"description": "Field to apply this object to"}>>> = velocity_component
velocity_direction<<<{"description": "Unit vector to dot with velocity, for 'field = velocity_component'. For example, velocity_direction = '1 1 0' will get the velocity dotted with (1/sqrt(2), 1/sqrt(2), 0)."}>>> = '0.5 0.5 0.5'
point<<<{"description": "The physical point where the field will be evaluated"}>>> = '0.25 0.3 0.27'
function<<<{"description": "Function to shift the field by, when applying this object. For example, if 'field = temperature', using this parameter will apply this object to the new combined quantity 'temperature - f', where 'f' is this shifting function."}>>> = f
execute_on<<<{"description": "The list of flag(s) indicating when this object should be executed. For a description of each flag, see https://mooseframework.inl.gov/source/interfaces/SetupInterface.html."}>>> = timestep_begin
[]
[](test/tests/postprocessors/nek_point_value/points.i)Input Parameters
- functionFunction to shift the field by, when applying this object. For example, if 'field = temperature', using this parameter will apply this object to the new combined quantity 'temperature - f', where 'f' is this shifting function.
C++ Type:FunctionName
Unit:(no unit assumed)
Controllable:No
Description:Function to shift the field by, when applying this object. For example, if 'field = temperature', using this parameter will apply this object to the new combined quantity 'temperature - f', where 'f' is this shifting function.
- meshallNekRS mesh to compute postprocessor on
Default:all
C++ Type:MooseEnum
Controllable:No
Description:NekRS mesh to compute postprocessor on
- velocity_componentuserDirection in which to evaluate velocity when 'field = velocity_component.' Options: user (you then need to specify a direction with 'velocity_direction'); normal
Default:user
C++ Type:MooseEnum
Controllable:No
Description:Direction in which to evaluate velocity when 'field = velocity_component.' Options: user (you then need to specify a direction with 'velocity_direction'); normal
- velocity_directionUnit vector to dot with velocity, for 'field = velocity_component'. For example, velocity_direction = '1 1 0' will get the velocity dotted with (1/sqrt(2), 1/sqrt(2), 0).
C++ Type:libMesh::Point
Controllable:No
Description:Unit vector to dot with velocity, for 'field = velocity_component'. For example, velocity_direction = '1 1 0' will get the velocity dotted with (1/sqrt(2), 1/sqrt(2), 0).
Optional Parameters
- allow_duplicate_execution_on_initialFalseIn the case where this UserObject is depended upon by an initial condition, allow it to be executed twice during the initial setup (once before the IC and again after mesh adaptivity (if applicable).
Default:False
C++ Type:bool
Controllable:No
Description:In the case where this UserObject is depended upon by an initial condition, allow it to be executed twice during the initial setup (once before the IC and again after mesh adaptivity (if applicable).
- execute_onTIMESTEP_ENDThe list of flag(s) indicating when this object should be executed. For a description of each flag, see https://mooseframework.inl.gov/source/interfaces/SetupInterface.html.
Default:TIMESTEP_END
C++ Type:ExecFlagEnum
Controllable:No
Description:The list of flag(s) indicating when this object should be executed. For a description of each flag, see https://mooseframework.inl.gov/source/interfaces/SetupInterface.html.
- execution_order_group0Execution order groups are executed in increasing order (e.g., the lowest number is executed first). Note that negative group numbers may be used to execute groups before the default (0) group. Please refer to the user object documentation for ordering of user object execution within a group.
Default:0
C++ Type:int
Controllable:No
Description:Execution order groups are executed in increasing order (e.g., the lowest number is executed first). Note that negative group numbers may be used to execute groups before the default (0) group. Please refer to the user object documentation for ordering of user object execution within a group.
- force_postauxFalseForces the UserObject to be executed in POSTAUX
Default:False
C++ Type:bool
Controllable:No
Description:Forces the UserObject to be executed in POSTAUX
- force_preauxFalseForces the UserObject to be executed in PREAUX
Default:False
C++ Type:bool
Controllable:No
Description:Forces the UserObject to be executed in PREAUX
- force_preicFalseForces the UserObject to be executed in PREIC during initial setup
Default:False
C++ Type:bool
Controllable:No
Description:Forces the UserObject to be executed in PREIC during initial setup
Execution Scheduling Parameters
- control_tagsAdds user-defined labels for accessing object parameters via control logic.
C++ Type:std::vector<std::string>
Controllable:No
Description:Adds user-defined labels for accessing object parameters via control logic.
- enableTrueSet the enabled status of the MooseObject.
Default:True
C++ Type:bool
Controllable:Yes
Description:Set the enabled status of the MooseObject.
- outputsVector of output names where you would like to restrict the output of variables(s) associated with this object
C++ Type:std::vector<OutputName>
Controllable:No
Description:Vector of output names where you would like to restrict the output of variables(s) associated with this object
- use_displaced_meshFalseWhether or not this object should use the displaced mesh for computation. Note that in the case this is true but no displacements are provided in the Mesh block the undisplaced mesh will still be used.
Default:False
C++ Type:bool
Controllable:No
Description:Whether or not this object should use the displaced mesh for computation. Note that in the case this is true but no displacements are provided in the Mesh block the undisplaced mesh will still be used.
Advanced Parameters
- prop_getter_suffixAn optional suffix parameter that can be appended to any attempt to retrieve/get material properties. The suffix will be prepended with a '_' character.
C++ Type:MaterialPropertyName
Unit:(no unit assumed)
Controllable:No
Description:An optional suffix parameter that can be appended to any attempt to retrieve/get material properties. The suffix will be prepended with a '_' character.
- use_interpolated_stateFalseFor the old and older state use projected material properties interpolated at the quadrature points. To set up projection use the ProjectedStatefulMaterialStorageAction.
Default:False
C++ Type:bool
Controllable:No
Description:For the old and older state use projected material properties interpolated at the quadrature points. To set up projection use the ProjectedStatefulMaterialStorageAction.