User Tools

Site Tools


Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
wiki:guides:authors:testing_easaps:troubleshooting_easaps [2015/11/17 05:45]
Zoltan [Incorrect Units in DOR]
wiki:guides:authors:testing_easaps:troubleshooting_easaps [2019/01/24 10:10]
Brian Collins
Line 19: Line 19:
 ===== Application Logs ===== ===== Application Logs =====
  
-A link with the name of the EASAP (''​2D Plotter.log''​ in the picture on previous pages) 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 repect, like missing, conflicting or invalid values for example. The **Analyse EASAP** tool is an effective way to investigate and fix the exceptions that might occur. ​+A link with the name of the EASAP (''​2D Plotter.log''​ in the picture on previous pages) 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. The **Analyse EASAP** tool is an effective way to investigate and fix the exceptions that might occur. ​
  
 ===== EASAP Diagnostic Files =====  ===== EASAP Diagnostic Files ===== 
Line 125: Line 125:
 **Solution:​** 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. ​ **Solution:​** 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. ​
  
-  - 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.  +  - 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.\\ \\  
-  - Make use of the DOR tables to locate problems with any related object values.  +  - Make use of the DOR tables to locate problems with any related object values.\\ \\  
-  - Identify and correct the problem **Data Processing** ​objects ​by examining and then modifying their parameter values in EASAP Builder. Possible errors include:  +  - Identify and correct the problem **[[wiki:​guides:​authors:​dataprocessing:​data_processing_objects|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 object.  +    * Inputs and Outputs are not in correct order in **[[wiki:​guides:​authors:​objects:​map|Map]]** object.  
-  * Typographical errors exist in **Value** parameter of **Expand** object, such as missing or misplaced **\n** new line symbols.  +    * Typographical errors exist in **Value** parameter of **[[wiki:​guides:​authors:​objects:​expand|Expand]]** object, such as missing or misplaced **\n** new line symbols.  
-  * Incorrect expression used in **Value** parameter of **Compute** object. ​+    * Incorrect expression used in **Value** parameter of **[[wiki:​guides:​authors:​objects:​compute|Compute]]** object. ​

Page Tools