moose Fixed mesh (caching) nearest node transfer mapping is incorrect

Bug Description

The nearest node transfer does not get the right map when using split meshes. But ok with distributed or replicated. contact @muelcm for inputs

We need to build a MWE for this. The simulation where this is happening is too expensive and uses a lot of apps.

Incorrect results, though obvious when looking at the output.

May 05 '22 18:05 GiudGiud

Split meshes are distributed meshes. Can not see what are special here. If it works with distributed meshes, it should work with split meshes

May 11 '22 15:05 fdkong

It does not work with split. I'm not sure about distributed since it has been about a week since we went through this

May 11 '22 16:05 muelcm

I ll check distributed and report back

May 11 '22 16:05 GiudGiud

this was investigated to be an issue with fixed meshes in the end

Aug 02 '22 17:08 GiudGiud

We are hitting an issue when the number of procs is higher than the number of subapps, hence the PR above. I ll work again on this in next FY

Sep 02 '22 00:09 GiudGiud

so it sounds like this is still an issue

Nov 21 '22 17:11 lindsayad

Yes it is for the current transfers.

The tests for the general field transfers will cover this case

Nov 21 '22 22:11 GiudGiud