The micromapST messages all start with "***" to help quickly find them in the warnings() logs and general output.
The general format of the messages is:
***XXXX NNNNNN text of message or ***XXXX NNNNNN CC text of message where the XXXX is the message alphanumeric identifier, NNNNNN is the name of the function or glyph issuing the message and CC is the glyph graphic column number in the panelDesc structure.
The four alphanumeric message identifier following the "***" is a unique message identifer to help find the explanation in this document and to help discuss problems over the email more accurately. It's always best to include the log of the preparation and execution of micromapST as well as the data used when requesting help.
The first two digits/characters of the message identifier indicates which logical segment of the package generated the message:
The second field of the message contains the name of the section of code generating the message. If a glyph generated the message, the name of the glyph (type=xxx) and the panel column number are displayed to help you focus on the parameters and data that may need to be inspected. Each message contains specific information (like panelDesc named list, checked value, etc.) to help identify the cause of the message and help lead the user to a fix. The remainder of the message contain a text explanation of the issue and a list of parameters: glyph column number/name, data row or column, variable name, and value related to the issue.
The following is a listing of all micromapST generated messages and a description of possible causes and solutions.
Back to the details section - Rest of the details dection
End of details section.