Estimated completion time → 50 minutes.
In this session, we create output to be displayed as a report on the Results pages.
This report will include a summary of the user’s inputs, tables of results, and a contour plot of the plate displacement.
Please follow the instructions below to complete this session. Detailed information on the objects created during this session can be found at the Author's Pages.
The first object to add to the OUTPUT branch will be a NOTES object to help users annotate their individual EASAP runs.
We need to perform some data processing in order to complete the report.
We extract the displacement data out of the output file created by the underlying plate analysis software and then present it in a table.
This file name will not appear in the pull-down list because it is only created after running the plate software application.
We set up a repeating find to pull out the desired data.
The Value: parameter color will change upon completing the content entry to: node xd yd zd. This indicates that the four DORs have been recognized as new list objects.
The Type: parameter is set by clicking the Integer selection once and then the Real selection three times on the pop-up form.
We have extracted the plate displacement data and now some processing of this data is required before it can be presented in the report.
To compute the nodal X and Y locations we need to create two more REPEATED COMPUTE's.
To complete the nodal X and Y location values we use two REPEATED EXPAND's to specify the units of ‘ft’ and to format the numbers to be floating point style with three digits after the decimal point.
We create lists of X and Y values to be used in a 2D GRAPH, which only needs X values for a single row and Y values for a single column.
Finally we compute the maximum displacement on the plate.
We create an object that determines when the results have been created and extracted properly.
Proceed with creating the report. We read-in the main body of the report as an HTML file.
Add a table for displaying the concentrated loads specified by the user.
To set the Columns: parameter click on the three list objects in the order shown.
|Parameter Name||Parameter Value|
|Column Titles:||X location [%], Y location [%], Load [kip]|
|Columns:||xloc, yloc, input_Lc_kip|
|Show if:||input_Lc_kip >0|
Create a heading that will show in the event that no concentrated loads were specified by the User.
Create a heading to introduce the results section of the report.
The first result to be displayed in the report is the maximum displacement of the plate.
Create a heading introducing the plot section of the report.
Create a contour plot of the displacement on the plate using the 2D GRAPH.
We create three more graphs to display plate moment data.
Add another heading to introduce a data table.
The logical expression in the Show if: parameter refers to the value of the logic box found on the fourth TABBED PANE. The TEXT OUTPUT will only be displayed if this expression evaluates as true.
We display the previously extracted nodal displacement data in a table.
The logical expression in the Show if: parameter refers to the value of the logic box found on the fourth TABBED PANE, Disp_table will only be displayed if this expression evaluates as true.
Finally display the previously extracted plate moment data in a table in the same manner as you displayed the nodal displacement data.
We are done defining the browser-based report that will be generated by each submitted run of our EASAP. Now display some of the generated results back on the user interface of your EASAP. Copy the plate displacement graph for pasting the user interface.
A new 2D GRAPH will appear on the Tree, rename it graph_Disp_results
Add some results output to results.
Copy the tabulated data from your report onto this pane.
For this new TABULATED DATA
Let's configure an EVENT PROCESSING to automatically refresh the user interface when the submission results have completed.
At this point, you can also get a preliminary view of the report that will be generated by the objects in the OUTPUT branch.
If you scroll down in the window, you should also see the following
Note: If your results pages do not look like what is shown above, you may have a problem with the original EASAP run or with the objects on your OUTPUT branch. You can try to resolve the problem now or wait until Session 8 where we test and troubleshooting our EASAP.
We have completed Session 6. Let's continue to Session 7.