MUPAD(1)

NAME
mupad - multi processing algebra datatool

SYNOPSIS
mupad [ -c ] [ -d modpath ] [ -g ] [ -G filedescr ] [ -h helppath ] [ -i ] [ -l libpath ] [ -m mampath ] [ -p stacksize ] [ -r ] [ -s syspath ] [ -t ] [ -u userpath ] [ -v ] [ -S ] [ files ]

DESCRIPTION
A standard ASCII terminal session of the computer algebra system MuPAD is started by the command mupad. Note that a grafical front end for MuPAD, called xmupad, is available under the X Window System, see xmupad(1). (The look and feel of xmupad is OpenLook.) In-depth information about MuPAD and the MuPAD programming language can be found in the MuPAD Reference Manual.

The MuPAD system not only consists of the mupad command but also of many other files, for example library files, help files etc. In order to find these files, mupad uses the environment variable MuPAD_ROOT_PATH. You must set this environment variable correctly (in your .login or .cshrc for example) if you want to use mupad. Please ask your system administrator which is the correct value of MuPAD_ROOT_PATH in your computing environment. It is also a good idea to add $MuPAD_ROOT_PATH/share/bin to your command search path (which is given by one of the environment variables path or PATH). You may further want to add $MuPAD_ROOT_PATH/share/manual to the MANPATH environment variable in order to make the MuPAD manual pages available.

When mupad is started, first the system init file .mupadsysinit or the binary file startup.mb and then the user init file .mupadinit are executed by mupad. These files contain usual MuPAD programs and are used to set up library search pathes, default read pathes or to load certain often-used librarys for example. Both of these init files are optionally. The startup.mb file contains the stack of MuPAD after the execution of the .mupadsysinit File in a binary format. Therefore by default the startup.mb file is read instead of the .mupadsysinit file, if it exists. Otherwise the .mupadsysinit file is used to initialize the system. The default location for the system init file is the directory where the MuPAD library is located, the default location of the startup.mb file is the directory, where the MuPAD kernel is located, but one may redefine these directories using the -s option. In this case first the startup.mb file ist searched in the specified directory. If this can not be found the .mupadsysinit file is loaded. To modify the initialisation done by the startup.mb file, the corresponding system init file is to modify. Then using the -i option a new startup.mb file is to be build. This will be saved in the directory of the MuPAD kernel. The user init file usually is located in the users home directory, but one may redefine this location using the -u option.

After the init files are executed the optional MuPAD program files given by files are read and executed by mupad. Finally the MuPAD prompt appears at the screen and one may enter MuPAD commands.

OPTIONS

-d modpath
    Path for dynamic moduls. MuPAD modul files are searched for in the directory modpath.

-g  Debug mode. mupad is startet in "raw debug" mode. In this mode debugging commands are entered directly inside the terminal session of mupad. Note that there exists a graphical front end to the debugger, called mdx, which may be started from xmupad. Usually one would prefer mdx to debug MuPAD code.

-i  Starts the MuPAD kernel by reading the system init file and generates a new startup.mb file. This file will be stored in the directory of the kernel.

-h helppath
    Path for help files. The MuPAD help files and the index file .mupadhelpindex used internally to access the help files are searched for in the directory helppath rather than in the default help directory $MuPAD_ROOT_PATH/share/help.

-l libpath
    Path for library files. MuPAD library files are searched for in the directory libpath rather than in the default library directory $MuPAD_ROOT_PATH/share/lib.

-m mampath
    Path for the MAMMUT init file. The init file .MMMinit for the MuPAD memory managment unit, or MAMMUT for short, is searched for in the directory mampath rather than in the library directory.

-p stacksize
    Stack size for PARI. The number stacksize defines the size (in bytes) of the internally used aritmetic package PARI. The default stack size is 250000 bytes.

-s syspath
    System init file and startup.mb file path. The binary file startup.mb and system init file .mupadsysinit are searched for in the directory syspath rather than in the library directory or the kernel directory.

-t  Trace mode. mupad is started in trace mode, where each function invocation and additional informations are displayed at the terminal. Trace mode is used for debugging purposes only, but note that normally one would debug MuPAD code by using the internal debugger rather than in trace mode.

-u userpath
    User init file path. The user init file .mupadinit is searched for in the directory userpath rather than in the users home directory.

-v  Verbose mode. For each function which is read by the MUPAD command read() additional debug informations are displayed at the terminal. (The entry point and possible break points of each function are displayed.) This option is useful when working with the MuPAD- internal debugger.

-S  Startup silently: The banner is not displayed when MuPAD is started.

The following options are used only internally (by xmupad for example) and must not be used when starting mupad directly from a terminal:

-c  Connect mode. This is the mode mupad is in when running as a slave under mdx.

-G filedescr
    Graphics communication. Plotting data is tranferred from mupad to the graphics front end using a pipe with the file descriptor filedescr.

-r  Raw mode. This is the mode mupad is in when running as a slave under xmupad.

ENVIRONMENT
The environment variable MuPAD_ROOT_PATH must be set to the root directory of the MuPAD installation in order to run mupad.

The environment variable PAGER must be set by the user to start his preferred page viewer (usually more or less) when he wants help in a mupad terminal session.

SEE ALSO
xmupad(1), mdx(1), MuPAD Reference Manual

DIAGNOSTICS

Use the MuPAD help system (ie. the commands ? or help) to obtain further informations about MuPAD.