Estimated completion time = 60 minutes.
In this practical session, you will test the EASAP that you have built in the previous sessions and make sure that it functions properly. Next we publish the EASAP and verify that it is available in User mode. More detailed reference information on testing and publishing EASAPs can be found at the Author's Pages. Please follow the instructions below to complete this practical session.
After a second or two, a pop-up window should appear when the EASAP has been submitted successfully.
Let’s look at the files that will help you diagnose problems you may encounter getting an EASAP to run properly.
err1-runplate.txtin the list. This file should have a Size of 0.0 kb. If not then click on the filename to view the error messages. If you are unable to determine the cause of the errors then contact your instructor or EASA support representative. At this point, can go back to the EASAP Builder and make changes 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.txtfile have been remedied.
Note: Not all messages captured in the standard error diagnostic files such as
err1-runplate.txt will be errors that need to be eliminated. Often software applications send other types of messages to the standard error stream.
out1-runplate.txtfile to familiarize yourself with program's file output. Then click on the browser's Back button.
PLATE.OUTfile has been created. If not then there is a problem with the EASAP or the input file
plate.txt. Open this file and look to see if all DORs were replaced correctly.
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, then contact your instructor or EASA support representative. At this point, you may need to either go back to the EASAP Builder window and make changes to your EASAP or make modifications to your template
plate.txt file in the text 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.
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 the EASAP Builder window and make changes to your EASAP based on suggestions from the EASA support person. This time you will NOT have to resubmit the EASAP for another test. You just need to save your changes in EASAP Builder, click on the View Results button () in the Output column and click the ‘Regenerate report’ link to see an updated report. Iterate in this way until the report appears as expected.
This TABBED PANE should then look like the following:
Your EASAP should now be ready for publishing.
Now check if your EASAP will be visible to Users on the EASA system.
A thumbnail of your EASAP should now be visible in the gallery layout for this part of the Applications Library.
Next we will go back to our plate EASAP and modify it to generate parametric runs.
We now add a PARAMETRIC RANGE to the INPUTBOX's input_W, input_L and input_t.
The first TABBED PANE window should now look like this:
Notice the symbols () to the right of the INPUTBOX's within the ‘Plate Dimensions’ SUB PANE box indicating the ability to set up parametric ranges for these inputs.
Let's update EASA→Results to include parametric output.
|Parameter Name||Parameter Value|
|Title:||Maximum Plate Displacement|
Now perform a parametric test of the modified EASAP.
It should look like this:
In this pane, you can see a table which displays each expected run and their corresponding ‘Width’ and ‘Length’ values. Note that when using multiple parametric ranges, it is important to ensure that each list of values is the same length.
After a second or two a pop-up window should appear when the EASAP has been submitted successfully.
Once completed, the output presented when you click on this link will look like the following:
You can view the individual reports by clicking on the Results icons.
Once you have completed your review of the parametric study results, you can publish a new release of your EASAP.
A window states ‘The EASAP has been successfully published.’
Congratulations! Your new EASAP is ready to be deployed to users.