Homepage | About EASA | Contact
Estimated completion time→15 minutes.
In this practical session we will create an output report that includes a summary of user input and a table of results.
During the Authoring phase of development the above output is available at:
Once the EASAP has been Published a User will submit runs and view output from a similar page at:
Parameter Name | Parameter Value |
---|---|
File: | report.html |
We need to extract some data from the underlying analysis software output file.
Parameter Name | Parameter Value |
---|---|
File: | PLATE.OUT |
This file name is not in the pull-down list because it is created after the plate software application is run.
Use the Extract Tool to help in the creation of EXTRACT, FIND, and REPEAT objects:
When the Extract Tool window appears,
At the top of the Load sample file window:
The window should appear as follows:
JOINT DISPLACEMENTS will appear in the left Matched Lines column (next page).
These steps are visible below.
Next we set up a repeating FIND to pull out the desired data.
Finally we compute the maximum displacement on the plate. In the OUTPUT branch:
Parameter Name | Parameter Value |
---|---|
List: | zd |
Function: | MAXIMUM |
Now let’s display the calculated maximum displacement of the plate in our report.
Parameter Name | Parameter Value |
---|---|
Text: | Maximum Plate Displacement = %MaxD% in. |
Style: | Normal |
Now add a heading.
Parameter Name | Parameter Value |
---|---|
Text: | <h4>Table of Plate Displacement</h4> |
Finally display our extracted nodal displacement data in a table.
Parameter Name | Parameter Value |
---|---|
Column Titles: | Node, Displacement [in] |
Columns: | node, zd |
At this point, we can get a preliminary view of the report that will be generated by the objects in the OUTPUT branch.
Back in the browser window,
The following figure will appear in the browser window:
If the results pages do not look like what is shown above, there may be a problem with the original EASAP run or with the objects on the OUTPUT branch. We can try to resolve the problem now or wait until Practical Session 5 when we will test and troubleshoot the EASAP.
We are now finished with Practical Session 4.