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
Please describe the problem you are trying to solve.
It is sometimes difficult to quickly see whether a mapping does a good job or not. For a consistent mapping, one wants that the distribution of values (e.g. the average) stays the same (is this actually true?).
Describe the solution you propose.
We already give statistics on the computeMapping of NN and NP:
I did not yet think much about details and wording.
For parallel participants, this would, of course, require global communication. So, there should be a way to switch this off, e.g. only have this for Debug builds.
What could be the equivalent for conservative mappings?
The text was updated successfully, but these errors were encountered:
Please describe the problem you are trying to solve.
It is sometimes difficult to quickly see whether a mapping does a good job or not. For a consistent mapping, one wants that the distribution of values (e.g. the average) stays the same (is this actually true?).
Describe the solution you propose.
We already give statistics on the
computeMapping
of NN and NP:We could log similar information for the actual values in each
map
call.I did not yet think much about details and wording.
For parallel participants, this would, of course, require global communication. So, there should be a way to switch this off, e.g. only have this for Debug builds.
What could be the equivalent for conservative mappings?
The text was updated successfully, but these errors were encountered: