The OEBT (ODB Extractor and Builder Tool) is a plug-in that allows the user to create new odbs from existing ones with a very high degree of flexibility in choosing what will populate to the new database. It differs from most published tools in that it creates the new odb piece by piece from scratch, utilizing essentially the entire odb API to generate features in the new database (including assembly level data). By default, the OEBT carries over the portion of the mesh that is displayed in the current viewport to the new odb.
Most published tools require the user run a datacheck and then copy over result data on top of that. This means that they cannot reduce the model, only the results data. Other tools will generate simplified models and copy data over to the simplified model, but do not have the ability to recreate the full model complexity.
With the OEBT, you have the option to recreate region(s) or the entire model with reduced or full model complexity. This means that you can potentially use the resulting databases to run downstream analyses as the required material/section/field/etc. data can be populated to the new odb. *If driving downstream analyses, please be aware of any current limitations of the tool listed in the documentation, and do a basic check to ensure the results of the newly generated odb are matching expectations.*
The user has a very high level of control over what populates to the new database, allowing them to decide what portion of the mesh, as well as what model feature categories (materials, sections, etc.), and what history data (steps, frames, fields, history output) to carry over. For these categories, you may specify to carry over all data, no data, or specific portions of the category. For model features, this means the ability to specify what to carry over by name (and the ability to wipe out detailed material definitions). For field data this means the ability to specify what data to carry over per step>frame>field>key>region. Any data which is not relevant to the new odb’s mesh is not carried over. For instance, if you specify to carry over all materials, but only 1 material is applicable to the mesh that is carried over, only that 1 material is created in the new odb.
To run the tool, download the package and extract it to a folder in your Abaqus plugins folder (%userprofile%\abaqus_plugins). The tool requires the user to define a json template specifying what they wish to add to the new odb. Examples of json files as well as a Python script to help generate them are provided in the documentation folder.
Runs on 2018HF3+.
***PLEASE NOTE***
BY DOWNLOADING THIS FILE (“DOWNLOAD”) YOU AGREE TO THE FOLLOWING TERMS:
THIS DOWNLOAD IS MADE AVAILABLE ON AN "AS IS" BASIS WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED, ORAL OR WRITTEN, INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE OR NON-INFRINGEMENT.
DASSAULT SYSTEMES SIMULIA CORP., ANY OF IT AFFILIATES (COLLECTIVELY “DS:”), AND ITS LICENSORS SHALL HAVE NO LIABILITY FOR DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL OR PUNITIVE DAMAGES, INCLUDING WITHOUT LIMITATION CLAIMS FOR LOST PROFITS, BUSINESS INTERRUPTION AND LOSS OF DATA, THAT IN ANY WAY RELATE TO THIS DOWNLOAD, WHETHER OR NOT DS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES AND NOTWITHSTANDING THE FAILURE OF THE ESSENTIAL PURPOSE OF ANY REMEDY.
YOUR USE OF THIS DOWNLOAD SHALL BE AT YOUR SOLE RISK. NO SUPPORT OF ANY KIND OF THE DOWNLOAD IS PROVIDED BY DS.
ORB v2.3.0
