ReporterPointSource

A ReporterPointSource reads in multiple point sources from a Reporter. The point source values and coordinates are updated as the Reporter values are changed.

An example of a ReporterPointSource using a ConstantReporter and a VectorPostprocessor of type CSVReaderVectorPostprocessor is given by:

[DiracKernels<<<{"href": "../../syntax/DiracKernels/index.html"}>>>]
  [reporter_point_source]
    type = ReporterPointSource<<<{"description": "Apply a point load defined by Reporter.", "href": "ReporterPointSource.html"}>>>
    variable<<<{"description": "The name of the variable that this residual object operates on"}>>> = u
    value_name<<<{"description": "reporter value name.  This uses the reporter syntax <reporter>/<name>."}>>> = 'reporterData/u'
    x_coord_name<<<{"description": "reporter x-coordinate name.  This uses the reporter syntax <reporter>/<name>."}>>> = 'reporterData/x'
    y_coord_name<<<{"description": "reporter y-coordinate name.  This uses the reporter syntax <reporter>/<name>."}>>> = 'reporterData/y'
    z_coord_name<<<{"description": "reporter z-coordinate name.  This uses the reporter syntax <reporter>/<name>."}>>> = 'reporterData/z'
    weight_name<<<{"description": "Name of vector-postprocessor or reporter vector containing weights to scale value, default is assumed to be all 1s."}>>> = 'reporterData/weight'
  []
[]

The ConstantReporter provides the following data:

[Reporters<<<{"href": "../../syntax/Reporters/index.html"}>>>]
  [reporterData]
    type = ConstantReporter<<<{"description": "Reporter with constant values to be accessed by other objects, can be modified using transfers.", "href": "../reporters/ConstantReporter.html"}>>>
    real_vector_names<<<{"description": "Names for each vector of reals value."}>>> = 'x y z u weight'
    real_vector_values<<<{"description": "Values for vectors of reals."}>>> = '0.2 0.2 0.0; 0.3 0.8 0.0; 0 0 0; 1 -.5 0; 1 1 1'
  []
[]

The CSVReaderVectorPostprocessor is given by:

[VectorPostprocessors<<<{"href": "../../syntax/VectorPostprocessors/index.html"}>>>]
  [csv_reader]
    type = CSVReader<<<{"description": "Converts columns of a CSV file into vectors of a VectorPostprocessor.", "href": "../vectorpostprocessors/CSVReaderVectorPostprocessor.html"}>>>
    csv_file<<<{"description": "The name of the CSV file to read. Currently, with the exception of the header row, only numeric values are supported."}>>> = point_value_file.csv
  []
[]

reading from the following csv file:

x,y,z,id,u,x3,y3,z3,value3
0.2,0.3,0.0,0,1.0,0.2,0.3,0,0.1
0.2,0.8,0.0,1,-0.5,0.2,0.8,0.0,-0.1
0.0,0.0,0.0,2,0.0,0.8,0.5,0.8,-1.0

The Reporter and VectorPostprocessor for the above example produce the same ReporterPointSource (e.g. same magnitude and location).

The next example applies a ReporterPointSource in a transient simulation given by:

[DiracKernels<<<{"href": "../../syntax/DiracKernels/index.html"}>>>]
  [vpp_point_source]
    type = ReporterPointSource<<<{"description": "Apply a point load defined by Reporter.", "href": "ReporterPointSource.html"}>>>
    variable<<<{"description": "The name of the variable that this residual object operates on"}>>> = u
    value_name<<<{"description": "reporter value name.  This uses the reporter syntax <reporter>/<name>."}>>> = point_sample_source/u
    x_coord_name<<<{"description": "reporter x-coordinate name.  This uses the reporter syntax <reporter>/<name>."}>>> = point_sample_source/x
    y_coord_name<<<{"description": "reporter y-coordinate name.  This uses the reporter syntax <reporter>/<name>."}>>> = point_sample_source/y
    z_coord_name<<<{"description": "reporter z-coordinate name.  This uses the reporter syntax <reporter>/<name>."}>>> = point_sample_source/z
  []
[]

using the following VectorPostprocessor to provide x,y,z coordinates and value_name = u

[VectorPostprocessors<<<{"href": "../../syntax/VectorPostprocessors/index.html"}>>>]
  [point_sample_out]
    type = PointValueSampler<<<{"description": "Sample a variable at specific points.", "href": "../vectorpostprocessors/PointValueSampler.html"}>>>
    variable<<<{"description": "The names of the variables that this VectorPostprocessor operates on"}>>> = u
    points<<<{"description": "The points where you want to evaluate the variables"}>>> = '0.2 0.8 0.0'
    sort_by<<<{"description": "What to sort the samples by. Options include 'x', 'y', 'z', 'id', and the name of any of the sampled quantities (which each create a vector of the same name)."}>>> = id
    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'
    contains_complete_history<<<{"description": "Set this flag to indicate that the values in all vectors declared by this VPP represent a time history (e.g. with each invocation, new values are added and old values are never removed). This changes the output so that only a single file is output and updated with each invocation"}>>> = true
    outputs<<<{"description": "Vector of output names where you would like to restrict the output of variables(s) associated with this object"}>>> = 'csv'
  []
[]

In the above input file, the ReporterPointSource is applying loads at two different locations. Note that the PointValueSampler has execute_on = timestep_begin to force the VectorPostprocessor to execute prior to being used by ReporterPointSource.