Menu

#20 decomposePar pointDisplacement fails when a globalFaceZone is present

assigned
None
normal
major
always
none
Library
1.5
other
2011-01-10
2010-09-16
No

Hello,
I have found out that when I try to decompose a run and there is a pointField (in my case pointDisplacement, I need it for mesh motion) and I also have a globalFaceZone, then the decomposePar application fails.

The error it gives is:

Processor 0: Field transfer

size of field 16952 is not the same as the size of the mesh = 14438
...

---- additional_information ----
Digging into the code I have found out that on processor 0:
mesh.points()=14438
mesh.allPoints()=16952

It seems that "somewhere" one should substitute points with allPoints, but I cannot find where..

Probably when the the globalFaceZone feature has been added, all other field have been corrected accordingly but the pointFields.. or maybe only pointField are affected by the issue since are the only one that depends directly on the points..

Any one can help?
Thanks

Discussion


Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.