[otaolafr]

Hello,

I am trying to recover the results of a case to apply it to the same case but with a finner mesh. to recover the different fields and interpolate them to the new mesh I wanted to use mapFields (or mapFieldsPar).

mapFields, has a strange behavior, if I use it in decomposed cases (target and source cases) with

mapFields -consistent  -parallelSource -parallelTarget -sourceTime 'latestTime' -sourceDecomposeParDict ../run_0_0_Part1/system/decomposeParDict -targetDecomposeParDict ./system/decomposeParDict ../run_0_0_Part1/

mapFields runs, it splits some warnings but no error, it finish running and when I go to the processors folders in my target case I do not get any time... like if I did nothing.

if i reconstruct each case

reconstructParMesh -constant
reconstructPar -time '1000'

and then do the mapFields it works correctly

mapFields -consistent  -sourceTime 'latestTime'

with mapFieldsPar I did not get luck in any case.... I get the following error when runing:

mapFieldsPar -consistent -fields (U p phi) -sourceTime 1000 -parallel ../run_0_0_Part1/

new cannot satisfy memory request.
This does not necessarily mean you have run out of virtual memory.
It could be due to a stack violation caused by e.g. bad use of pointers or an out-of-date shared library

the only thing I nottice in the mapFieldsPar is that the log shows:

Source: "../run_0_0_Part1" ""
Target: "/home/0HOME_ALT/otaolafr/15.07.21" "run_0_2_Part1"

when in the case of mapFields it shows:

Source: "/0HOME_ALT/otaolafr/15.07.21/run_0_0_Part1" ""
Target: "/0HOME_ALT/otaolafr/15.07.21" "run_0_2_Part1"

[wildfire230]

I'm not sure if you found the answer to this, but it does seem like mapFieldsPar uses far more memory than mapFields. I have the impression that it loads the entire mesh into memory per processor for some reason. I'm not sure if that is true.

[otaolafr]

Originally Posted by wildfire230

I'm not sure if you found the answer to this, but it does seem like mapFieldsPar uses far more memory than mapFields. I have the impression that it loads the entire mesh into memory per processor for some reason. I'm not sure if that is true.

hi,
thanks for the answer, well the only solution I found, was to reconstruct the case (mesh and desired time) in the source case, (and can not remember if also for the target case too). in any case the issue was coming from the cases being decomposed.... the memory was not a problem at all in my case. it was only that it was running without errors but no time was being created....