Estimated completion time = 45 minutes.
In this practical session, you will create a process to run the software application, manipulate user inputs into a form suitable for the batch files, and edit a batch input file into a template with Delimited Object References (DORs). Please follow the instructions below to complete this practical session.
Now in the Builder we will upload the external files our EASAP will need.
input.txt and click Upload.
Note: The file
plate.txt contains input data for the plate application. The file
femrctpl.exe is the executable for the plate application. The file
input.txt contains responses to queries from the plate application that would normally be typed at the command prompt
Now we create a PROCESS for running the external plate analysis '.exe' program.
|cmd.exe /C "femrctpl.exe <input.txt"
For our EASAP the User will input plate dimensions in the GUI and we will convert this data into the same form as the input file
First we translate the plate dimensions into the normalized dimensions that are expected: the plate is divided into a 10×10 grid of elements.
We need to map the edge support conditions (free, pinned or fixed) to their numerical indicators (0, 1, 2) used in the input file.
|Free, Pinned, Fixed
Now we translate the two lists of the concentrated loads x and y coordinates into the normalized nodal format that the program expects.
Now we construct the line in the input file that corresponds to each concentrated load.
|%yc% %xc% %input_Lc [kip] 8.3f%
With a REPEATED EXPAND we are creating a string of text from existing COMPUTE objects to match the “plate.txt” format expected by the program.
Note 1: The % symbol acts as the delimiter in the Delimited Object References (DORs) found in the Value: parameter. These DORs will be replaced by the object values when the repeated expand object is processed.
Note 2: The \r\n symbol stands for a new line, so to set the Expansion Separator: parameter, you can click on the Text box button () at the right- end of the Parameter Value cell and then in the text entry pop-up, hit the Enter key once and click on OK
The next step for the runplate PROCESS is to replace the conventional input text file
plate.txtwith our own identically formatted input data.
It is a good idea to clear away redundant files to minimize disk space usage.
Check the EASAP tree to ensure that the Processes branch looks like this:
Note: The order of execution within a PROCESS object is always:
Therefore, the order of objects on the tree within a process object is not important. However, the order of execution of multiple process objects is based on their order on the tree, occurring from top to bottom.
plate.txt into a template containing Delimited Object References (DORs).
plate.txt should appear in the table on the Template Editor page.
The Template Editor will start in a new window
We will replace fixed input values such as text strings and numbers with DORs which will insert values from our EASAP.
Tip: If you encounter problems setting the units of the DOR, ensure that the Unit Group parameter has been set properly for the dy COMPUTE. If you need to go back and make a change in EASAP Builder, you can keep Template Editor open and just select Reload under the file menu after saving your changes in EASAP Builder
At this point, the file should appear in the Template Editor as follows:
At this point, your EASAP should be ready for its first test run. Even though the OUTPUT branch is empty and nothing will be displayed on the results pages, you can still submit a test run and take a look at what is produced
Now, look at the Status column for the run you just submitted. It may show a variety of messages. 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.
Once your job has completed, you can take a look at some of the files produced by the test run.
First, let’s take a look at the input file
plate.txt, and see the result of the DOR replacements.
If you do not see the file content shown above, then you may have some errors either in your EASAP settings or in your template input file. You can attempt to fix these problems at this time or wait until Practical Session 8, in which you will be testing and debugging your completed EASAP. After reviewing the file, click on the Back button
PLATE.OUT, produced by the underlying software application. Click on the PLATE.OUT link, and the window’s display should change to look like the following:
If you do not see the PLATE.OUT link or the file content shown above, then you have some errors either in your EASAP settings or in your template input file. You can attempt to fix these problems at this time or wait until Practical Session 8, in which you will be testing and debugging your completed EASAP. After reviewing the file, click on the ‘x’ to close the window.
Now, review the values of data produced in the EASAP.
You can browse through all pages of the table to review values of all data in your EASAP.
You are now finished with Practical Session 5.