The team do not fix this bug in version 14 is unfortunate. I noticed you use – at least in the official versions of GiD – semantic versioning (
https://semver.org/). I think this situation demands an increment in the PATCH version (14.0.x) and not an increment in the MINOR version (14.x), as you suggested. As a user and a developer, I kindly ask you to reconsider your decision.
Duplicate is a rare mesh feature, but what is the point in offering it if you can't apply a condition to duplicate nodes?
About the trick you suggest:
I thought of verifying all nodes in a group with duplicated nodes. Doing this, I would need to compare the coordinates of each node in a group with the rest of the mesh nodes. If two nodes have the same coordinates, I should add the duplicated node in the group.
This solution is simple and easy to implement. The problem is: When working with medium/large models, it would come into a computational efficiency issue. For example, if the model has 500 000 nodes and the condition group has 10 000 nodes, I will need to verify 5 000 000 000 times (500 000 x 10 000).
Questions:
- Is there any way to verify and add the nodes in all the group conditions more efficiently? Can you help me with examples? (I can't help to say that, in my opinion, the most efficient way to do it is to add the duplicated node when GiD duplicates it. And the only one who can make this is the CIMNE team, releasing a PATCH version for GiD 14).
- As you said, I could "automatically detect by proximity duplicated nodes." How am I supposed to do it? Has GiD a built-in function that detects close nodes? For example, I give the node number, and GiD returns the nearest nodes inside a spheric region with radius r.