ACS SASSI Submodeler is a graphical user interface in as of the ACS SASSI V3.0.0 installation kit before Revision 5.
When the user Opens Submodeler the interface will look very similar to PREP interface. Unlike Prep, on entry to the Submodeler there is an empty model ready to be used without requiring the use of the new Menu option to create or load a model the user should consult the Getting Started topic. The File conversion processes from File Converter has been expanded and allows the user to directly input model data into Submodeler without need to write a pre first.
The first new capability of the Submodeler is the ability to open and use multiple models at the same time. Submodeler has a state machine protocol for accessing and creating new models. All commands and user interface options affect the current active model. User should be familiar with this concept because it is the same way that the GROUP and Element commands worked in Prep and continue to work in Submodeler. All models in the Submodeler are referenced by positive integer number with the default model (empty model on opening) number being 0. To access any model the user must use the ACTM command
The size limitations on models has not changed in the submodeler. It was found that many functions of Prep are very inefficient when dealing with models that are close to the limit of SASSI. First, when Loading an pre only the comments in the file and errors encounter are reported to the command history. The command entry and acceptance shown in the command history during input dramatically slows down the input process and with volume of commands in a larger model will overwrite the error. This sped input of a pre file that take 15 minutes in PREP to under a minute in the Submodeler. The Submodeler uses OpenGL 4.0 for graphics which allow for better display of large models. Finally the internal storage format of data in the Submodeler was changed to decrease the memory needed to store each model.
The Submodeler name implies that a user may take a piece of one model and use that as a separate model this is covered in the Submodeling example.
The Submodeler has the ability to Merge two models in memory into a single model. The Process is described in the Merge topic.