1.1 Starting MechanicalSystems

This section covers the loading of MechanicalSystems packages into a Mathematica session on various computer systems.

1.1.1 Main Package

The MechanicalSystems packages are loaded into Mathematica in the same manner as a standard Mathematica package; with a Get or Needs statement.

Loading the Mech packages.

This loads the Modeler2D package.

In[1]:=

It is not possible to have both Modeler2D and Modeler3D loaded simultaneously because they use many of the same function names with different definitions. Attempting to load Modeler3D while Modeler2D is already loaded results in Modeler2D being unloaded and replaced with Modeler3D - and vice versa.
The MechanicalSystems packages are not intended to be loaded twice. Thus, it is recommended that Needs be used to load the packages because Needs will not read the package if it has already been read. If Get is accidentally used to load one of the Mech packages after it has already been loaded, an error message is generated, and the Get operation is aborted.

1.1.2 Secondary Packages

The MechanicalSystems secondary packages Dynamics2D/3D, Graphics2D/3D, and Utilities2D/3D need not be loaded explicitly. They are loaded automatically if any of the function definitions they contain are needed. However, if the Information or Definition functions are to work correctly with the functions in the secondary packages, these packages must be loaded into Mathematica. Note that requesting information about a MechanicalSystems function with ?functioname will not cause the associated packages to be autoloaded.

This causes all of the Modeler2D packages to be loaded, including Modeler2D itself.

In[2]:=

1.1.3 Clearing and Unloading

MechanicalSystems may be reset to its initial state, or removed entirely from the current Mathematica session without quitting and restarting Mathematica, with the ClearMech or KillMech functions.

Resetting or removing Mech.

This removes the entire Modeler2D or Modeler3D package.

In[5]:=

After executing KillMech nothing remains of the Mech session except whatever definitions the user had made in the Global` context, and a few undefined symbols that Mech creates in the Global` context. The Mech packages can be reloaded with Get or Needs after executing KillMech.