A sequence of commits in a database, ordered chronologically by their commit date to form a commit history. A special commit is the most recent one on the branch, and the branch itself often acts as a representative of this commit. The most recent commit, and thus the branch itself, also identifies the latest versions of items.
New branches can be created by branching off from any commit on a
parent branch, thereby starting an alternative commit history. Changes made on a new branch can be
merged back to its parent branch.
Each commit is associated with a date and time when the changes were saved, that is the commit date, the user that saved the changes, and an optional save comment. Each commit also identifies the set of item versions that were the
latest versions at the time of the commit, as well as all tag assignments present at that time. Given a particular commit, such item versions and tag assignments can be browsed and searched in the database.
A version-controlled file stored in a database that is neither a model or application file (mph) nor a physics file (
mphphb). Typically abbreviated as just
file in Model Manager. Examples include CAD data, interpolation functions, plots, and reports.
An ancillary model meant for intermediate modeling work, and whose versions are saved as a separate version history split off from that of its
origin model. Once a draft has been completed, it can be saved back as a new version of the main model it originated from.