Starting and Exiting a CUBIT Session

The following commands are used to control CUBIT execution.

Starting the Session

The command line version of CUBIT can be started on UNIX machines by typing "cubit" at the command prompt from within the CUBIT directory. If you have not yet installed CUBIT, instructions for doing so can be found in Licensing, Distribution and Installation. A CUBIT console window will appear which tells the user which CUBIT version is being run and the most recent revision date. A graphics window will also appear unless you are running with the -nographics option. For a complete list of startup options see the Execution Command Syntax section of this document. CUBIT can also be run with initialization files or in batch mode.

Windows File Association

Windows users have the option to associate .cub, .sat, and .jou files with CUBIT.   This means that double-clicking on one of these files will open it automatically in CUBIT. This option is available during the installation process

Exiting the Session

The CUBIT session can be discontinued with either of the following commands



Resetting the Session

A reset of CUBIT will clear the CUBIT database of the current geometry and mesh model, allowing the user to begin a new session without exiting CUBIT. This is accomplished with the command

Reset [Genesis | Block | Nodeset | Sideset | QA_Records]

A subset of portions of the CUBIT database to be reset can be designated using the qualifiers listed. Advanced options controlled with the Set command are not reset.

QA Records are stored in exodus, genesis, or cub files. If your file contains an excessive amount of qa records and you don't need them, it is beneficial to reset them for faster file I/O.

You can also reset the number of errors in the current Cubit session, using the command

Reset Errors <value>

which will set the error count to the specified value, or zero if the value is left blank.

Abort Handling

In the event of a crash, Cubit will attempt to save the current mesh as "crashbackup.cub" in the current working directory just before it exits.

To disable saving of the crashbackup.cub file set an environment variable CUBIT_NO_CRASHSAVE equal to true. Or, use the following command:

Set Crash Save [On|Off]

This command will turn on or off crashbackup.cub creation during a crash on a per-instance basis. To minimize the effects of unexpected aborts, use Cubit's automatic journaling feature, and remember to save your model often.