Hey Ramon:
I had a hunch that was the case. Something similar happens in FSI cases, where node number 1 stays fixed even though there are no displacement BCs imposed on it.
The solution (workaround) you are looking for is not to use number 1 for any of your nodes. Start numbering your CalculiX nodes from 2 onwards. In your case, if n is the number of nodes in your mesh, then renumber node 1 to n+1. Don’t forget to update that number in your *ELEMENT keyword (i.e. for those elements for which that node is part of) and in node sets it belongs to.
@Makis Indeed this is a problem that has come up several times. Should a GitHub issue be opened for it? If it’s of any use to know, it started happening with the adapter for CCX 2.16; I can confirm it’s not present in CCX 2.15. I have not tested the 2.19 adapter.
Other instances:
- How can I create a Solid mesh for working with the nearest neighbor mapping? - #4 by KyleDavisSA
- FSI SU2/CalculiX (flap_perp): CalculiX node ID#1 is fixed
Note however, that the problem in the first thread you linked to is similar to this one but not the same. From what I understand, in that one a node was defined in CalculiX that was not part of the structural mesh but was defined as part of the interface and thus participated in the mapping. Since it was not part of the simulation it retained its original coordinates and messed up the mapping.
Regards
Andrés