You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently it is not possible to map to an exchange or intermediary grid -- any field put! in the coupler lives on the space of the simulation that puts it there.
This is because of the current way the mapping is set up which uses a tag (write_sim) to specify the source space/sim when remapping. This tag also (as the name suggests) indicates which simulation has write permissions to that coupled field.
Perhaps the right solution is to remove the double usage of write_sim and add another tag like "space_name" which would be part of the remap operator name.
Adding remapping to the put! side of things creates symmetry and more flexibility for what grids the coupling takes place on. It creates the potential that there could be a coupler-owned field in memory, rather than the coupler only registering pointers.
Currently it is not possible to map to an exchange or intermediary grid -- any field
put!
in the coupler lives on the space of the simulation that puts it there.This is because of the current way the mapping is set up which uses a tag (
write_sim
) to specify the source space/sim when remapping. This tag also (as the name suggests) indicates which simulation has write permissions to that coupled field.Perhaps the right solution is to remove the double usage of
write_sim
and add another tag like "space_name
" which would be part of the remap operator name.Adding remapping to the
put!
side of things creates symmetry and more flexibility for what grids the coupling takes place on. It creates the potential that there could be a coupler-owned field in memory, rather than the coupler only registering pointers.Originally posted by @jb-mackay in #58 (comment)
The text was updated successfully, but these errors were encountered: