CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > Software User Forums > OpenFOAM > OpenFOAM Pre-Processing

mapFields returns an inconsistent field

Register Blogs Community New Posts Updated Threads Search

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   July 21, 2021, 07:57
Talking mapFields returns an inconsistent field
  #1
New Member
 
Join Date: Jun 2021
Posts: 5
Rep Power: 5
badreddine0 is on a distinguished road
Hello everyone !!


I have a problem using mapFields. My source mesh size is 149.310 and my target mesh size is 8.958.600, it's a lot ^_^'



Unfortunately, it's seems that mapFields returns a fields with only 4.777.920. I got this message.


Quote:
Create databases as time

Source time: 429.02503
Target time: 0
Create meshes

Source mesh size: 149310 Target mesh size: 8958600

Found 8695120 cells outside of the addressing
Cell addressing size = 8958600

Mapping fields for time 429.02503239793

interpolating Ux


--> FOAM FATAL IO ERROR:
size 4777920 is not equal to the given value of 8958600
Can you help me to find a solution ? Is it possible to run it in parallel or something like that ?



Thank you
badreddine0 is offline   Reply With Quote

Old   July 21, 2021, 08:45
Default
  #2
New Member
 
Join Date: Jun 2021
Posts: 5
Rep Power: 5
badreddine0 is on a distinguished road
Strangely, I got the same with much smaller mesh. This time, I had more value than required by the target mesh. It's very weird



Quote:
Create databases as time

Source time: 429.02503
Target time: 0
Create meshes

Source mesh size: 149310 Target mesh size: 212800

Found 207480 cells outside of the addressing
Cell addressing size = 212800

Mapping fields for time 429.02503239793

interpolating Ux


--> FOAM FATAL IO ERROR:
size 4777920 is not equal to the given value of 212800
badreddine0 is offline   Reply With Quote

Old   July 24, 2021, 11:37
Default
  #3
Senior Member
 
Join Date: Apr 2020
Location: UK
Posts: 745
Rep Power: 14
Tobermory will become famous soon enough
From my limited experience with mapFields, I found that it was very important to have a correct, consistent initial set of files in the 0 time folder, to map onto. When I screwed up, with say an outdated swak4Foam list for the inlet with the wrong number of entries in the list for the mesh I was trying to map onto, I got a similar error message.

I wonder if you have a set of initial fields in your target case 0 folder that are for a model size of 4777920? This would explain why it is complaining that this does not match your mesh size of 212800, etc. Regardless - my advice is check carefully your 0 folder files in the target case.
Tobermory is offline   Reply With Quote

Reply

Tags
inconsistent, mapfields


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOWFA] NREL SOWFA ABLTerrainSolver tutorial problem cico0815 OpenFOAM Community Contributions 36 February 3, 2022 12:54
funkySetBoundaryFields - Manipulation of existing field jhertel OpenFOAM Pre-Processing 16 May 18, 2020 07:32
field read after each Time Step johanning OpenFOAM Programming & Development 1 December 29, 2019 08:59
Access to a field of a lagrangian post-processing cloudFunction Ake OpenFOAM Programming & Development 0 December 13, 2019 06:46
How to get cell indices and manipulate field data ch1 OpenFOAM Programming & Development 5 September 25, 2019 12:17


All times are GMT -4. The time now is 12:13.