Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations cowski on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

Job getting aborted after 3 iterations

Status
Not open for further replies.

Ajith Kurian Baby

Mechanical
Joined
Mar 28, 2020
Messages
53
Location
IN
Untitled_j1koxy.png

[URL unfurl="true"]https://res.cloudinary.com/engineering-com/raw/upload/v1586835961/tips/data_yqmwlj.txt[/url][URL unfurl="true"]https://res.cloudinary.com/engineering-com/raw/upload/v1586835971/tips/MSG_FILE_zhhw41.txt[/url][URL unfurl="true"]https://res.cloudinary.com/engineering-com/raw/upload/v1586835988/tips/status_file_h3rbih.txt[/url]

when the UMESHMOTION subroutine is switched on and job is submitted, the job gets aborted immediately. i am doing a wear simulation problem with two bodies have a relative reciprocating motion with a pressure load. please help me to solve the issue.
 
Does the analysis converge without the subroutine ? If yes then it seems that your subroutine works in such way that it causes convergence issues. Can you check the results generated before the analysis aborts ? Do they look correct ?
 
What I meant is that you should take a look at the results (in odb file) generated in this analysis with subroutine before it aborted. You may notice some incorrect deformation of the mesh caused by UMESHMOTION.
 
Is that deformed shape plot with scale factor = 1 ? Did you try using finer mesh ?
 
yes, the plot was with a scale factor 1 and tried with increased mesh density for lower body but, still it gets aborted in the same manner. I tried with much reduced load it also didn't work.

in Umesh subroutine, I was trying to execute different call functions one by one, without any other conditions or statements
call GETVRN(NODE,'V',VEL,JRCD,JGVBLOCK,LTRN)
call GETPARTINFO(NODE,0,PARTNAME,LOCNUM,JRCD)
call GETNODETOELEMCONN(NODE,NELEMS,JELEMLIST,JELEMTYPE,JRCD,JGVBLOCK)
call GETVRMAVGATNODE(NODE,'CSTRESS',ARRAY,JRCD,JELEMLIST,NELEMS,JMATYP,JGVBLOCK)

I found that when the fourth call function is called, the job is getting aborted. if I avoid that and run code without any other statements or conditions job is running.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top