Estimated completion time→10 minutes.
In this practical session, we will test the EASAP from the previous sessions. Then we will Publish the EASAP for other users on EASA→User→Applications.
After the EASAP window appears:
A pop-up window will appear when the EASAP has been submitted successfully.
icon under Output ().
Now let’s look at the files that will help to diagnose problems we may encounter getting an EASAP to run properly.
A pop-up window will appear that will look like the following figure:
This file should have a Size of 0.0 kb to the right of the file name. If the number is greater than zero, then click on the link for the file and examine the error messages given in the file. Contact the instructor or EASA support representative if the cause of these messages cannot be identified. At this point, we may need to go back to EASAP Builder and make changes to the EASAP based on suggestions from the EASA support person. Then resubmit the EASAP for another test. Iterate in this way until all errors in the err1-runplate.txt file are eliminated.
Note: Depending on the type of underlying software driven, not all messages captured in the diagnostic files, such as err1-runplate.txt, will need to be eliminated. Often, software applications send other types of messages to the standard error stream.
If not, then there is a problem with either the EASAP or the input file, plate.txt.
The file should look like the following:
If the input file does not look like the one above and the cause of the problem cannot be identified, contact the instructor or EASA support representative. Again we may need to go back to the Builder and make changes to the EASAP or make modifications to the template file plate.txt in the template editor. Then resubmit the EASAP for another test. Iterate in this way until the object references in the plate.txt file get replaced properly and a valid PLATE.OUT file is produced.
At this point, we have successfully completed an EASAP run.
Examine the reported results:
If the report does not appear correctly, please contact the instructor or EASA support representative for assistance. Again, we may need to go back to EASAP Builder and make changes to your EASAP based on suggestions from the EASA support person. We will NOT have to resubmit the EASAP for another test: just save your changes in the Builder and then click on the Re-generate report using the latest version of this EASAP link to see an updated report. Iterate in this way until the report appears as expected.
The EASAP will now be ready for publishing.
Following the initial Publish, an Author may choose from Major Revision, Minor Revision and Unpublish options.
A new window will state ‘The EASAP has been successfully published.’
Let's check whether our EASAP will be visible to Users on the EASA system.
The EASAP will now be visible in the EASA→Applications table.
Confirm the output from the EASAP run is available at: