User Tools

Site Tools


Test EASAP functionality | Test EASAP robustness | Troubleshooting an EASAP

Troubleshooting an EASAP

Test and Analyse

In the early stages of the EASAP life-cycle, mistakes or assumptions will lead to object values that are not correct. To identify problems:

  • Select: Test EASAP and set inputs examine outputs
  • For further analysis select 'Analyse EASAP' to monitor values and events at runtime

For more depth see: Test and Analyse

Application logs

A link with the name of the EASAP ('2D Plotter.log' above) points to a log file specific to the EASAP and the EASA server that it is located on. It logs DOR exceptions related to the EASAP. These exceptions occur when one or more settings in the EASAP Builder tool are wrong in some respect, like missing, conflicting or invalid values for example.

'Analyse EASAP' is an effective way to investigate and fix the exceptions that might occur.

EASAP diagnostic files

A good idea to consider when an EASAP test run does not function as expected is to view files created during the run by clicking on the 'Browse' button ( in the 'Files' column of the 'Test Results' table. Upon clicking on this link, a window, as shown in the figure below, will appear containing a list of files associated with the test run.

Diagnostic files

Two diagnostic files, 'err1.txt' and 'out1.txt' are generated when an EASAP PROCESS is submitted (filename increments when there is more than one PROCESS. The 'err-…' files contain the standard error streams generated by the software being run while 'out..txt' files contain the standard out stream. This information may determine what went wrong with an EASAP run.

When viewing these files, look for common error messages that when the underlying software application is run outside of EASA.

Other text files generated by underlying software during execution may help debugging, click the file name link to view them.

GuiConfig.ccl file

If an Author is unable to determine the cause of a problem, EASA Technical Services may examine the EASAP’s 'GuiConfig.ccl' file. Access this file in the same manner as other diagnostic files:

  1. Click: EASA > Authoring > Testing > Files icon
  2. Click on the 'GuiConfig.ccl' link
  3. Save this file and send it to support@easasoftware.com

The EASAP Builder also will export the 'GuiConfig.ccl' file to a local folder, by exporting the 'EASAP' object at the top of the Tree.

DOR table

As mentioned before, very often errors in EASAPs are related to problems with DORs (also see “Analyse EASAP” above). To help you find and fix problems related to DORs, all objects that have values and therefore could be used in a DOR are listed in DOR tables. These DOR tables are accessed by clicking on the 'View DORs' button ( ) in the 'DORs' column of the 'Test Results' table.

The DOR tables contain the following information:

  • Object name
  • Object type
  • Object value
  • Any error messages returned during evaluation of the object

The complete DOR tables for an EASAP may span several pages.

When you fix a problem with an object value in the EASAP Builder, you may not need to resubmit a test run. Instead use the 'Latest DORs' link on the DOR table page to confirm the correction.

Dependency view

The DORs tab in the EASAP Builder provides a way to explore the dependency relationships between objects.

In the example below it shows how the REPEATED EXPAND Cloads is dependent on Lc, xc and yc; and xc in turn is dependent on xloc.

The objects can be sorted alphabetically, by type or by the order in which they originally appear on the Tree. These sort settings correspond to the last three icons on the DORs toolbar. The second icon provides a different tree which allows you to explore where a DOR is used. In this case, we see that the CHOICE LIST mat is used by a number of objects such as MaxD, modulus and poisson.

Enter a text prefix into the search box to filter the Tree, options like wildcard support are available under the search icon, below.

Common errors

After reviewing the diagnostic files, the next step is to determine the causes of any problems. Often the causes will be found in the following list of common errors.

Incorrect number format in DOR

Sometimes error messages are found in diagnostic files complaining of illegal input in batch files. Underlying software application does not execute properly.

The problem here is that the DOR will be replaced by EASA, but the underlying software will not accept it as valid input. The following procedure will guide you through the correction of this problem.

  1. Look for any indications within error messages found in diagnostics files as to the location within the batch file of the troublesome numbers. If the locations of these invalid numbers is given, then proceed to Step 3 to correct the number formats that gave rise to them.

  2. If no locations are given in any of the error messages, you will need to compare the batch file used in the test run with the corresponding batch file used in your manual test that you know works. Using your template batch file as a guide, proceed to each DOR location in the two batch files and identify numbers with improper formats in the test run batch file.

  3. Fix the number formats in the template batch file by editing it using the Template Editor. To open the file in the editor, click on its 'Edit' button in the 'Template Files' table found on the 'Template Editor' page under the 'Authoring' menu.

Incorrect units for an object

Sometimes numerical results generated are not as expected and do not match what was generated during manual testing of batch files. Underlying software application does not execute properly.

This type of error is similar in difficulty to the previous error to locate and fix. Again the problem DORs will still be replaced by EASA, but the numbers provided to the underlying software will be incorrect due to improper units. The following procedure will guide you through the correction of this problem.

  1. You will need to compare the batch file used in the test run with the corresponding batch file used in your manual test that you know works. Using your template batch file as a guide, proceed to each DOR location in the two batch files and identify numbers in the test run batch file that are not the same value as in the working batch file.

  2. Fix the units in the template batch file by editing it using the Template Editor. To open the file in the editor, click on its 'Edit' button in the 'Template Files' table found on the Template Editor under the Authoring menu. You may need to change an existing unit specification or add the proper unit specification in the DOR.

Remember that no inline units in a DOR will cause an object’s value to be evaluated in base units during replacement.


Incorrect Run Using: value

Sometimes the underlying software application does not execute at all. Error messages will indicate unrecognized command or improper usage of command.

This type of error is usually straightforward to diagnose and fix. Once you have identified the problem with the command, you need to modify IN Run Using: in the relevant PROCESS.

Incorrect manipulation of inputs

Sometimes numerical results generated are not as expected and do not match what was generated during manual testing of batch files. Underlying software application may not execute properly.

This type of error is similar in difficulty to the Incorrect Units in DOR error. Again the problem DORs will still be replaced by EASA, but the values provided to the underlying software will be incorrect due to incorrect manipulation of user inputs. Incorrect manipulation of user inputs will occur in Data Processing objects located on the User Interface and Processes branches of your EASAP tree. The following procedure will guide you through the correction of this problem.

  1. You will need to compare the values of the DORs in your template batch file with the corresponding values in the batch file used in your manual test that you know works. Using your template batch file as a guide, proceed to each DOR location in the two batch files and identify replacement values in the test run batch file that are not the same value as in the working batch file.

  2. Make use of the DOR tables to locate problems with any related object values.

  3. Identify and correct the problem DATA PROCESSING objects by examining and then modifying their parameter values in EASAP Builder. Possible errors include:

    • Inputs and Outputs are not in correct order in MAP.
    • Typographical errors exist in Value: of EXPAND, such as missing or misplaced ' \n ' new line symbols.
    • Incorrect expression used in Value: of COMPUTE.

Test EASAP functionality | Test EASAP robustness | Troubleshooting an EASAP