Homepage | About EASA | Contact
Homepage | About EASA | Contact
Estimated completion time = 10 minutes.
In this practical session, you will test the EASAP from the previous sessions. Then you will publish your EASAP for other users on EASA→User→Applications.
Lets get started:
If you see ‘Queued’ then the job is waiting for some other jobs to finish before starting to run. If you see a percentage number, then your job is currently running. Finally, if you see ‘Completed’ then your job is done and you can view the results by clicking on the icon under Output ().
Now let’s look at the files that will help you diagnose problems you may encounter getting an EASAP to run properly.
err1-runplate.txtfile in the list.
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. If you are unable to determine the cause of these messages, then contact your instructor or EASA support representative. At this point, you may need to go back to EASAP Builder and make changes to your EASAP based on suggestions from the EASA support person. You will 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.
PLATE.OUTfile has been created.
If not, then there is a problem with either the EASAP or the input file,
The file should look like the following:
If the input file does not look like the one above and you are unable to determine the cause of the problem, contact your instructor or EASA support representative. At this point, you may need to either go back to EASAP Builder and make changes to your EASAP or make modifications to your template
plate.txt file in the template editor. You will then resubmit the EASAP for another test. Iterate in this way until the DORs in the
plate.txt file get replaced properly and a valid
PLATE.OUT file is produced.
At this point, you have successfully completed an EASAP run. You can close the file browsing window now, and if you haven’t already done so, you can now examine the reported results by clicking on the View Results button () in the Output column. The report will look similar to what you saw in your initial tour of EASA in Practical Session 1 and when you developed the Output branch in Practical Session 5.
If the report does not appear correctly, please contact your instructor or EASA support representative for assistance. Again, you may need to go back to EASAP Builder and make changes to your EASAP based on suggestions from the EASA support person. You 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.
Your EASAP will now be ready for publishing.
Let's check whether our EASAP will be visible to Users on the EASA system.
Your EASAP will now be visible in the EASA→Applications table. If you like, you can open up your EASAP, modify some inputs and then submit it to run as a User. As a User the output from an EASAP run will appear in EASA→Results→My Results.