Learning Forum

[626910852]

I am conducting an extremely large-scale test and would like to know the maximum allowable quantities for grid elements and nodes respectively, as my grid is large enough and during the calculation process, an issue has arisen.

*** Error 11168 (KEY+1168)
Duplicate node ID 10000012 with non-matching coordinates.

The error message "*NODE_MERGE_TOLERANCE with TOLR > 2.3345E+01 could be used to unite those nodes" appeared. I added the *NODE_MERGE_TOLERANCE keyword and set the parameter to 150, but it still didn't solve my problem. I sincerely hope that engineers who have encountered similar issues can help me. Thank you!

[igandiko]

Hello, the error indicates there are multiple nodes defined using the same id (10000012). Please check if there are duplicate node ids in your model. Perhaps it might be easier to open the k file in a text editor and search this id to find the duplicate definitions. 

[626910852]

Thank you for your response! Could you please tell me how to edit IDs that exceed eight digits? Should I continue with eight-digit numbers and then manually edit them to nine-digit numbers in sequence? Thank you!

[Pedram Samadian]

Hello,

As the error message indicates, your model has 2 nodes with different coordinates but the same ID. Why don’t you identify those nodes directly in your input deck (text file) or in LS-PrePost and simply change their IDs?

 I assume *NODE_MERGE_TOLERANCE most likely works only for twe completely different nodes (in terms of coordinates and IDs). 

I look forward to your feedback.

Thanks,

Pedram

 

[626910852]

Thank you for your help! Due to the file's enormous size, I cannot directly open it for editing. However, I can use Python to assist me in the editing process. But I have a doubt: since the standard input file only supports up to eight-digit IDs, how should I handle IDs that exceed eight digits? Could you please tell me if there is a better way? I would be extremely grateful for your advice!

- From a graduate student who is eager to graduate and has a strong desire for knowledge

[Alex R.]

Hello, 

The standard input deck supports node IDs up to 8 digits. Please open the input deck in a text editor and search for the duplicated node ID 10000012. If you are merging two components into a single model, it's quite common to encounter duplicate node IDs like this.

 

I recommend checking the input file for any duplicated nodes and determining whether ID renumbering is needed. The keyword *NODE_MERGE_TOLERANCE is typically used when duplicate nodes are located very close to each other in space and can be merged based on their proximity. However, given a distance of approximately 2.3345E+01, it’s unlikely that this is the same node — so renumbering might be the better solution here.

Thanks,
Alex

[626910852]

Thank you very much for your response! However, I am currently conducting a computational test with a billion-grid system. The k file I'm working with contains over 100 million grids, and the node numbers will inevitably exceed eight digits. As you mentioned, "The distance between two nodes is 2.3345E+01, so these nodes cannot be the same. Therefore, renumbering might be a better solution." Does this mean that if I open the k file with a file editor and manually edit the node numbers that exceed eight digits, say, by manually changing them to nine-digit numbers in sequence, it will be able to run? Or could you please provide a more detailed explanation on how to handle this issue? I would be extremely grateful for your help! This is a research topic for me, and I need it to help me graduate. As a graduate student, I will always remember your assistance!