Homepage | About EASA | Contact
Introduction | Session 1 | Session 2 | Session 3 | Session 4 | Session 5
Estimated completion time → 15 minutes.
In this practical session, we will create a new EASAP, set some properties, and create data entry objects.
At the end of this session, our EASAP interface will appear as below.
Please follow the instructions below to complete this practical session. Detailed information on the objects created in this session can be found at the Author's Pages.
First check with your Administrator that you have a user ID with Author privileges.
In the New Application Wizard,
After creating an EASAP, the next task is to upload any files required by the EASAP. When uploaded, these files are copied from the local machine to the EASA Server and stored in the development folder for the EASAP. This folder contains the single, centralized definition of the EASAP, which once Published files here will be read or modified when a User runs the EASAP.
The Save button is enabled only when there are unsaved changes. Following a Save, the button will be disabled or grayed out until until another change is made.
We are now ready to proceed with adding data entry objects to the user interface of our EASAP.
Parameter Name | Parameter Value |
---|---|
Choices: | Steel, Aluminum, Titanium |
Default: | Steel |
Label: | Plate material |
Parameter Name | Parameter Value |
---|---|
Default: | 5.0 |
Label: | Length |
Upper Bound: | 10 |
Lower Bound: | 0.5 |
Units: | Length |
The parameter table for the REALBOX L will appear as follows,
Note, Set Units: first to create a dropdown 'units' menu for the other parameters.
Parameter Name | Parameter Value |
---|---|
Default: | 1, in |
Label: | Thickness |
Upper Bound: | 2, in |
Lower Bound: | 0.25, in |
Units: | Length |
Parameter Name | Parameter Value |
---|---|
Default: | 50, lbf/ft |
Label: | Load magnitude |
Upper Bound: | 200, lbf/ft |
Lower Bound: | 20, lbf/ft |
Units: | Force per Unit Length |
At this point, the EASAP Tree should look like this:
Our EASAP may have a title such as ‘Cantilever Plate Loading Analysis (X)’, where the X will be an integer.
If another EASAP already exists with the same name then this integer is added to the EASAP’s title (or an existing integer incremented) in order to keep each EASAP title unique.
Congratulations. We have finished Session 1. Let's continue with Session 2.
Introduction | Session 1 | Session 2 | Session 3 | Session 4 | Session 5