The ODB splitter utility is a plug-in that is provided to help the user reduce the size of ODBs. This is achieved by generating an 'empty' ODB by carrying out a datacheck and selecting the variables and frames which are to be written to the 'empty' ODB. It should be noted that Frame 0 of the first step is generated automatically by the datacheck. This information cannot be removed from the new ODB. When accessed through the plug-in architecture the utility is suitable for ODBs that have been created from analyses that have not used user subroutines, restarts or imports. For ODBs that contain these features, the utility has to be run manually.
Requirements/Information:
The data in the .txt file consists of step names, output variable identifiers and names of frames. The Step: line defines a step to be included in the new ODB. This string followed by the step name. For example,
Step: Step-3
Lines following this step definition are associated with the output variables and frames associated with this step until another step definition is found or the end of file is reached. Output variable identifiers are defined, one per line, after a line containing Output Variables:. The output variables identifiers are followed by the description of the frames to be included in the new ODB. Output variables that are not available for a particular frame are ignored. Output variables not being available can be caused by the output variable not being requested as output for a particular increment or due to a typographical errors i.e. an invalid name. The frame description has to match exactly the frame description contained in the original ODB. Blank lines are ignored.
A warning is issued for any output variable that cannot be written to the new ODB and for any frame that does not have a matching description in the original ODB. It is suggested that the makeOdbInfo.py utility or the plug-in is used as this will ensure the syntax of the .txt file created is correct.
To make the plug-in available from Abaqus/CAE or Abaqus/Viewer, you must place the files in one of the directories of subdirectories that Abaqus searches for plug-ins. These are:
If the plug-in is found it will appear in the Plug-ins menu on the main menu bar.

From this dialog the user can select the required field output variables and the steps and frames required. This dialog is followed by a review of the selections made.
On OK the .txt file is generated and a new process is started that creates the datacheck ODB and runs the splitter script. The output from this is reported in the command window associated with the Abaqus/CAE or Abaqus/Viewer session.
The odbSplitter.py script can be run in batch mode.
The txt file specified using the -txt option has to contain a list of steps, frames and field outputs to be written to the ODB. If this argument is not specified the default name used is odbIn.txt.
A utility script makeOdbInfo.py can be used to generate a full listing of the contents of the ODB in the correct format for use with the ODB splitter script. Once this file has been created using the makeOdbInfo.py script, items can be removed from the file using any editor before running the odbSplitter.py script.
This will create the full listing of the contents of odbIn.odb in odbIn.txt
This plug-in has undergone limited testing and is provided as an example to show how to reduce the size of ODBs. It is up to the user to check that the reduced size ODB that has been created can be opened and contains the information required before deleting the original ODB.