mapFields & mapFieldsPar decompose cases
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 Code:
mapFields -consistent -parallelSource -parallelTarget -sourceTime 'latestTime' -sourceDecomposeParDict ../run_0_0_Part1/system/decomposeParDict -targetDecomposeParDict ./system/decomposeParDict ../run_0_0_Part1/ if i reconstruct each case Code:
reconstructParMesh -constant Code:
mapFields -consistent -sourceTime 'latestTime' Code:
mapFieldsPar -consistent -fields (U p phi) -sourceTime 1000 -parallel ../run_0_0_Part1/ Quote:
the only thing I nottice in the mapFieldsPar is that the log shows: Code:
Source: "../run_0_0_Part1" "" Code:
Source: "/0HOME_ALT/otaolafr/15.07.21/run_0_0_Part1" "" |
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.
|
Quote:
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.... |
All times are GMT -4. The time now is 17:02. |