setup_indices for boundary variables are read_var in precice
space-time function we are not able to use 'idx' created here as input for
get_valOfIndex for write_vars.Therefore we have to do setup_indices for
write_vars once during initialization and then store the idx in
precice_coupling type. This is done for the non-equidistant points. We also
set the vertices and the edges as well as the triangles for the
Interpolation between the domains.
Obtain the point coordinates to get values for
get the number of unquie points ( xyz should be same number)
VK write(,) 'number of Points to write to precice is 0, cycle &
VK & this spacetimefunction'
shift the points via the offset bit for the get_point routine
get the unquie list of points
get the unquie list of points serialize them since precice needs
a 1d array transform offet bit back
shift the points according to the offset bit * small fraction
of the boundingCubeLength hence it is mesh independent
loop over the variables to write to precice
get_point routine for unquie array of points of that variable
get the setup_indices for the shifted points
Since we are sending 5 times the same idx, for the unique
Points and all of them have the same idx, we just need to
store it once
send the points to precice and get back the positionID
allocate posID array
From here on the Nearest-Projection is introduced, which has to
be activated by the user in the ateles-config file.
We assume here, that all points for a specific face are grouped
together in order to make use of the posIDs
Call to create the edges and triangles acoording to the
dimension
Nodes of different colours represent the following:
Solid arrows point from a procedure to one which it calls. Dashed
arrows point from an interface to procedures which implement that interface.
This could include the module procedures in a generic interface or the
implementation in a submodule of an interface in a parent module.
Nodes of different colours represent the following:
Solid arrows point from a procedure to one which it calls. Dashed
arrows point from an interface to procedures which implement that interface.
This could include the module procedures in a generic interface or the
implementation in a submodule of an interface in a parent module.