I would like to collect some opinions on the mapping topic for local RBFs. Currently, the user has the option to define either a support radius or a shape parameter through a global variable in the xml config. A good choice is, however, usually not available for the user, even if he or she knows ‘enough’ about the mapping method, e.g. I would like to cover 4 vertices in each direction in my local RBF function in order to get a good trade off. The reason is mainly the missing information of the vertex distance in the coupling mesh.
I know we have some information on the website including a script and the reference paper, but using a script before each run is tedious.
However, the information is usually available in the solver (and or adapter). Would it be possible to add an option in the interface in order to determine the support radius/shape through the solverinterface?
I think it would simplify things and it would enable to spend some thoughts once when implementing a suitable algorithm in the adapter rather than each time when starting a simulation, e.g.
my_average_radius = // my algorithm SolverInterface.set_support_radius(my_average_radius)
Using this method, the shape parameter definition would be independent of the global refinement level (or similar things) of my mesh (say you want to test on a coarse mesh before starting the real refined case).
What do others think?