Hello!
I'm using your code as part of a larger code base. It works great for linear elastic experiments where there is only 1 time increment. However, when I do plastic experiments, the computation time to get the node COORD, U, and Element COORD, LE is very long due to the number of elements. What makes it way worse is the number of increments exacerbates this problem.
Is there a way to retrieve only the outputs from the LAST increment? This also will be useful so I can distinguish the output of the last increment from the last increment of the step before.
Thanks!
You are welcome, Samuel!
You can tackle the problems that you have mentioned above with large-sized fil files in two ways:
(1) Splitting the fil file into a number of smaller fil files and read the smaller fil files in a loop, and
(2) reduce the size of the fil file that is generated by eliminating non necessary information.
In the first option, you can do this manually by editing the fil file and cutting-pasting segments of it to other fil files, but this procedure needs attention not to cut the initial fil file in a point containing vital information for the Abaqus output results.
In the second option, you can reduce the size of the *.fil file that is generated from the Abaqus analysis in the following ways: 1) In the data lines of the *EL FILE or *NODE FILE options, please specify as few output variable identifiers as possible i.e. remove redundant results of the Abaqus analysis. 2) Use the ELSET and NSET parameters in the *EL FILE and *NODE FILE options respectively, to request fil output from the Abaqus analysis only from specific element/node sets, to reduce the amount of data written in the fil file.
3) Redefine your Abaqus model in terms of a single part/instance. For this purpose, you can remove all *PART, *END PART, *INSTANCE, *END INSTANCE, *ASSEMBLY and *END ASSEMBLY options from inside the Abaqus input file, by properly renumbering the nodes and elements of the various parts/instances (if more than 2). 4) Remove all the *NSET and *ELSET options from the Abaqus input file that are not necessary for the analysis, i.e. they do not constitute reference for application of loads, contact, boundary conditions, etc. 5) Include the INTERNAL parameter in *NSET and *ELSET definitions inside the Abaqus input file. 6) Redefine the model in terms of assembly of part instances, where possible. Please try the above options and let me know if the issue is fixed.
Best regards!