JOB ABORT invoked by rank 0
 

Hello Everyone,

I am getting same error again and again. Error message is as below:
" JOB ABORT invoked by rank 0
ERROR: wrong boundary motion_type in calc_moving_vec boundary id = 16"

What does this error mean? I have only 15 boundaries in my case. Then from where this boundary id 16 came?

Please Help!

Thanks.

Hello Ankit,

Unless you have interfaces in your case setup, the boundary ID 16 would correspond to disconnect triangles. As you might know, CONVERGE creates disconnect triangles between regions during a closed event. However, you must note that the boundaries between which disconnect triangles are created must not be moving when the regions are disconnected.

The error is most likely telling you that you have boundaries associated with these disconnect triangles that are moving during a closed event. For example, this error is present when you define a CLOSE event between the ports and the cylinder while the valves are still moving.

I offer the following suggestions (assuming this case includes motion of valves): Please check to see that your valves have reached minimum lift before you define your CLOSE event. If you're using VALVE events, please make sure you have the (minimum_lift/2) point defined in your valve profile. I would also strongly advise you to use our latest code.

Hope this helps. Please refer the manual for more information on the above.

Sincerely,

Srivastava

Thanks Kislaya for a reply.

I tried this but still I am getting same error. Can I share my case setup file with you for your reference?

Hello Ankit,

Sure. You send your case files (*.in and *.dat files) to support@convergecfd.com . Please use your official email for all correspondence with Convergent Science. Please mention the issues you are facing and add my name as reference.

Sincerely,

Srivastava

Thank You so much :):)

Hello Ankit,

I am getting the same error with which you submited in September 15, 2017.

Error message is as below:
"JOB ABORT invoked by rank 7
ERROR: wrong boundary motion_type in calc_moving_vec boundary id = 15."
Only 14 boundaries in my case, so where dose the boundary 16 come from?

How did you solve this problem in th end? Can you give some advice?

Thanks so much.