Abaqus Subroutines in ISight 1

[D Higgins]

Is it possible to use subroutines when running Abaqus through Isight?
I've searched through the User Guide and through online forums however I can not find any examples or if it is possible. I believe it is possible using the OS command component but using the Abaqus component would make it much easier to obtain results.

 

[IceBreakerSours]

Yes, it is possible.

*********************************************************
Are you new to this forum? If so, please read these FAQs:

http://www.eng-tips.com/faqs.cfm?fid=376

http://www.eng-tips.com/faqs.cfm?fid=1083

 

[Mustaine3]

It should also work with the Abaqus component. Just make sure that the subroutine is provided to the component and modify the execution command.

 

[D Higgins]

Where/how do I provide the subroutine to the component? Is it provided as a file parameter in the execution tab. Also should my execution tab be similar to the following: "abaqus.bat input=EXAMPLE.inp job=EXAMPLE user=EXAMPLE interactive"? Should the abaqus.bat be change?

 

[Mustaine3]

Yes, create a file parameter, collect the predefined subroutine and then make this file parameter an input for the Abaqus component.

The command looks good. I think the default command just needs the additional user=... option.

Make sure the subroutine works on this machine in general (compiler, license). Test it first with a normal run in Abaqus.
Also set the option in Isight, that the component directory is not cleaned after execution when testing your process. This allows to better understand what files are placed and created in the directory and what might be missing when an error appears.

 

[D Higgins]

Thanks I got it working correctly.

My Abaqus was not configured correctly to run subroutines using the abaqus.bat command. I used Habtamu Tadesse's post here:

https://www.researchgate.net/post/How_resolve_ifort_error_while_running_FORTRAN_code_in_abaqus

to comprehensively configure Abaqus with Fortran. My execution statement was "abaqus.bat job=TEST user=TEST" and I had to make sure everything was being ran from the one directory (Additional sub directories were being created and ISight was unable to access all the files).