No stop script code - Even with no convergence results 1

[asdjk]

Hi guys,

I wrote a Python script code to proceed a parametric plastic analysis in Abaqus.

Inside the loop, I added these below lines:
mdb.jobs[job_name].submit(consistencyChecking=OFF)
mdb.jobs[job_name].waitForCompletion()

Unfortunately, some models do not converge and the whole script (that includes other models) stops.

I would like to know how can I run the code without stopping when a analysis get wrong. Instead of stopping, just go to the next model and run it.

I can do it by calling my script code by using "abaqus cae script=code.py" but I would like to do it by calling to run without opening abaqus (i.e. abaqus cae nogui=code.py).

Does anyone has the code lines that I need to add it?

Thanks

 

[testing]

You need to add exception handling for the events causing your code to stop, so that it properly writes out any output from the failed case you need for later before continuing on to the next case

https://docs.python.org/2/tutorial/errors.html

 

[asdjk]

Thanks zwtipp05.

But it seems that (in my case) there is no clear "Python Error" but an Abaqus Error.

In CMD, the following message appears:
"Abaqus Error: Abaqus/Standard Analysis exited with an error - Please see the message file for possible error messages if the file exists.
Abaqus/Analysis exited with errors
Abaqus/Analysis exited with error."

This error was caused by a Riks analysis that didn't converge.

There is no clear type of exception associate with this case.

To avoid using a stop criteria, I would like to know a way to have a no stop script code. In other words, a code that can run continually after a Riks analysis return an error.

Best regards

 

[testing]

Not sure what method you're using to run the jobs from python, but section 6.8 of the Scripting User's Guide looks like it may help. With exceptions, you can process them yourself, it doesn't have to be an existing exceptions. You may for example parse the log file and see this error and then go to the next. Ultimately it depends a lot on how your code is setup, what you're doing and how you're doing it.

 

[Mustaine3]

As mentioned, read out the .log file. Built a loop that waits for 60 seconds (e.g.) before it checks again. Use the sleep command from the time module to let the code wait.