Error Message Guide Overview
|
Description
|
|
You may have been directed to this page because an error was generated in your Maple worksheet. If so, do not panic. We make every effort to provide valuable information that may help you to solve the problem right away, or at least narrow down the parameters of the problem. However, if the text of the error message does not provide you with the information you need to troubleshoot your document, there are steps you can take to correct the problem.
There are three circumstances that would generate an error in Maple:
1
|
User Errors - the user has supplied incorrect input
|
2
|
No Solution - in some cases, a Maple routine will issue an error, indicating that the given problem has no solution
|
3
|
Maple Errors - Maple generates an error during internal computation in response to a problem with its own code
|
In most cases, the user might assume that an error is generated due to incorrect input. As you can see from the previous list of options, that may not be the case. The following sections discuss each of these circumstances, along with resources that will help you to understand Maple errors and instructions on how to proceed.
|
User Errors
|
|
Example 1
>
|
|
One common error that users make is supplying arguments of the wrong type.
Solution:
In this case, the first argument should be of type algebraic instead of type list.
>
|
|
| (1.1.1) |
Example 2
>
|
|
Another common error is supplying the wrong number of arguments.
Solution:
Make sure that the correct number and type of arguments have been entered.
>
|
|
| (1.1.2) |
You can see the correct calling sequences for any Maple command, including how to specify the arguments, on the help page for that command. For this example, see inttrans[fourier].
Example 3
>
|
|
>
|
|
>
|
|
Sometimes, a user error may be generated in a routine different from the outmost routine being called.
Solution:
Maple evaluates the inputs to a procedure such as plot before it calls the procedure, resulting in being called with the symbolic argument . You can delay the evaluation of the input using unevaluation quotes. For more information, see the related error help page.
Example 4
>
|
|
| (1.1.3) |
>
|
|
A common error is the misuse of previous assignments. Sometimes, you assign a name to a value or expression and then later use that name expecting it to be a variable.
Solution:
To avoid this error, you can use a different variable than in the second expression, unassign the variable , or clear Maple's internal memory using restart, which clears all variable assignments.
Example 5
>
|
|
One of the most common errors is a syntax error, often created by mistyping the input... that is, a typo. In this case, the required finishing parenthesis is missing.
Solution:
To fix this error, add the missing parenthesis.
>
|
|
| (1.1.4) |
Example 6
>
|
|
Sometimes a syntax error is more involved. In this example, the command plots[complexplot] is used, but with arbitrary arguments .
Solution:
To determine the correct syntax for this command, go to the help page for the related command (which is given within the error message in parentheses). In this case, typing ?plots/complexplot in your worksheet will take you to the help page for plots[complexplot]. This page will explain the proper syntax for the arguments or other parts of the calling sequence. In this particular example, valid arguments for this command could include the following:
>
|
|
|
|
No Solution
|
|
>
|
|
Sometimes, there is no solution to a given problem, which is a legitimate result. In such cases, Maple will return an error to indicate that there is no solution available. In this case, there is nothing to fix; this is Maple's response that there is no solution available.
|
|
Maple Errors
|
|
It is possible that Maple will generate an error during internal computation as a result of a problem with its own code. If you believe this has happened, we would like to hear from you! The best way to give us the information to fix this problem is to use our Support Request Form. Fill out the form and include a copy of the worksheet that generated the error. This will help our programmers fix any errors within the code.
|
|
|
Warnings
|
|
Along with error messages, Maple produces various informative warning messages when executing a command. Warning messages are discussed in further detail here.
|
|
Other Resources
|
|
Here are some other tips or resources that you can use to determine the source of your error:
•
|
Check the ?error help page
|
The error help page explains the format of error messages, which can help you to decipher the information being given.
•
|
Rewrite or reformat the problem
|
It may be that the command used is not the one that should be used in a particular instance. Try rewriting the formula using a different command or different parameters.
Go to Maplesoft's FAQ page to find answers to users' most common problems.
Do a search for the generated error message on MaplePrimes, the online community for Maple users. Copy the error message text (or if this does not return any results, copy only the name of the routine) into the search box at the top of the MaplePrimes page.
Maple's manuals are available online, including the User Manual, Programming Guide, and Getting Started with Maple Toolboxes. In particular, the Programming Guide includes Avoiding Common Errors sections at the end of many chapters. From the Help menu, select Manuals, Resources, and more, and then Manuals.
•
|
Maple Technical Support
|
If all else fails, please contact Maplesoft Technical Support.
|
|