Mapfields takes long Time!

alinuman15 · August 1, 2017, 06:35

Dear All:-
I have successfully run a two phase flow case on Stampede with 252 processors such that it produced files with very big sizes. However, it was clear afterward that I had missed the water field setting ( just the air field had been set). Therefore, I prepared the same case again with setting the proper field and created a mapfieldsDict with an empty patchMap and cuttingPatches to map the solution. I have copied the mapfieldsDict into the source and target system files where each of target and source is located in different locations. Then, I run :-
mapFields "source Directory" -case "target Directory" -sourceTime latestTime

the terminal is still running since around 8 hours and it shows the following:-
Source time: 0.4
Target time: 0

Create meshes

Source mesh size: 11666176 Target mesh size: 11666176

Creating and mapping fields for time 0.4

Creating mesh-to-mesh addressing for region0 and region0 regions using cellVolumeWeight

Does that look normal ?
Thanks!

Antimony · August 2, 2017, 06:17

Hi,

You can change your mapMethod and see if that performs better. I have heard that some of them help to perform the mapping process faster.

Cheers,
Antimony

api · December 7, 2018, 16:08

Maybe this issue is already resolved. However, for the benefit of others I state my findings.

As of writing this, the mapFields utility does not seem to handle the typographical errors in the input dictionary.

For eg. In my target case, I had one of the entries in "nut" input dictionary as follows
("pipe_wall|gate)" as opposed to "(pipe_wall|gate)" [note the location of the double quotes is wrong]

With the above typo, mapFields continues without complaining.

So, if mapFields appears to be running for a long time, please recheck the syntax of your input files.

August 1, 2017, 06:35	Mapfields takes long Time!	#1
alinuman15 Member Ali Noaman Ibrahim Join Date: Sep 2015 Location: US_Chicago Posts: 97 Rep Power: 10	Dear All:- I have successfully run a two phase flow case on Stampede with 252 processors such that it produced files with very big sizes. However, it was clear afterward that I had missed the water field setting ( just the air field had been set). Therefore, I prepared the same case again with setting the proper field and created a mapfieldsDict with an empty patchMap and cuttingPatches to map the solution. I have copied the mapfieldsDict into the source and target system files where each of target and source is located in different locations. Then, I run :- mapFields "source Directory" -case "target Directory" -sourceTime latestTime the terminal is still running since around 8 hours and it shows the following:- Source time: 0.4 Target time: 0 Create meshes Source mesh size: 11666176 Target mesh size: 11666176 Creating and mapping fields for time 0.4 Creating mesh-to-mesh addressing for region0 and region0 regions using cellVolumeWeight Does that look normal ? Thanks!

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
AMI speed performance	danny123	OpenFOAM	21	October 24, 2020 04:13
High Courant Number @ icoFoam	Artex85	OpenFOAM Running, Solving & CFD	11	February 16, 2017 13:40
Micro Scale Pore, icoFoam	gooya_kabir	OpenFOAM Running, Solving & CFD	2	November 2, 2013 13:58
dynamic Mesh is faster than MRF????	sharonyue	OpenFOAM Running, Solving & CFD	14	August 26, 2013 07:47
mixerVesselAMI2D's mass is not balancing	sharonyue	OpenFOAM Running, Solving & CFD	6	June 10, 2013 09:34

August 2, 2017, 06:17		#2
Antimony Senior Member Join Date: Aug 2013 Posts: 407 Rep Power: 15	Hi, You can change your mapMethod and see if that performs better. I have heard that some of them help to perform the mapping process faster. Cheers, Antimony

December 7, 2018, 16:08		#3
api New Member Ashwin Join Date: Mar 2018 Location: Houston Texas Posts: 10 Rep Power: 8	Maybe this issue is already resolved. However, for the benefit of others I state my findings. As of writing this, the mapFields utility does not seem to handle the typographical errors in the input dictionary. For eg. In my target case, I had one of the entries in "nut" input dictionary as follows ("pipe_wall\|gate)" as opposed to "(pipe_wall\|gate)" [note the location of the double quotes is wrong] With the above typo, mapFields continues without complaining. So, if mapFields appears to be running for a long time, please recheck the syntax of your input files.