{"id":379292,"date":"2024-08-16T22:21:56","date_gmt":"2024-08-16T22:21:56","guid":{"rendered":"https:\/\/innovationspace.ansys.com\/forum\/forums\/reply\/379292\/"},"modified":"2024-08-16T22:21:56","modified_gmt":"2024-08-16T22:21:56","slug":"379292","status":"publish","type":"reply","link":"https:\/\/innovationspace.ansys.com\/forum\/forums\/reply\/379292\/","title":{"rendered":"Reply To: Changing Contact Condition to Displacement constraints"},"content":{"rendered":"

<p>Hello Kiyean,<\/p><div> ==> The displacement boundary condition on node 12345 is modified <span style=”text-decoration: underline;”>on<\/span><\/div><div><span style=”text-decoration: underline;”> multiple domains<\/span>.   <\/div><div> <\/div><div>Yes, this seems to be a message resulting from domain decomposition used by the distributed solver.  You already discovered that switching to the shared memory parallel (SMP) solver (which doesn’t decompose the model when it solves) works fine. It’s usually a little slower and doesn’t scale well with number of processors selected, but if it doesn’t result in excessively long turn-around, I’d just continue using it.<\/div><div> <\/div><div>I don’t know the internal logic used to decide where\/how to split the mesh for domain decomposition (~random, I  suspect) and I don’t know of anyway to control that. I can see how you might hit the error for some models and not others.<\/div><div> <\/div><div>I couldn’t find record of the error you reported after a cursory search in our records… you may be the first user to report it to us.<\/div><div> <\/div><div>Best,<\/div><div>Bill<\/div><div> <\/div><div> <\/div><div> <\/div><\/p>\n","protected":false},"template":"","class_list":["post-379292","reply","type-reply","status-publish","hentry"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t