Cube-it 16.3 User Documentation
The following commands are used to control Cube-it execution.
The command line version of Cube-it can be started on UNIX machines by typing "Cube-it" at the command prompt from within the Cube-it directory. If you have not yet installed Cube-it, instructions for doing so can be found in Licensing, Distribution and Installation. A Cube-it console window will appear which tells the user which Cube-it 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. Cube-it can also be run with initialization files or in batch mode.
Windows users have the option to associate .cub, .sat, and .jou files with Cube-it. This means that double-clicking on one of these files will open it automatically in Cube-it. This option is available during the installation process
The Cube-it session can be discontinued with either of the following commands
Exit
Quit
A reset of Cube-it will clear the Cube-it database of the current geometry and mesh model, allowing the user to begin a new session without exiting Cube-it. This is accomplished with the command
Reset [Genesis | Block | Nodeset | Sideset]
A subset of portions of the Cube-it database to be reset can be designated using the qualifiers listed. Advanced options controlled with the Set command are not reset.
You can also reset the number of errors in the current Cube-it 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.
In the event of a crash, Cube-it 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 Cube-it' automatic journaling feature, and remember to save your model often.