Estimated completion time → 45 minutes.
In this session we create a process to run the software application.
We manipulate User inputs into the exact format required for the batch files.
The Template Editor helps us take a single example input file and replace each input with a delimited object reference (historically a 'DOR') which substitues a User specified value prior to being submitted for processing.
A User will set plate dimensions in the GUI and we will convert this data into the same format as the input file plate.txt
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.
We translate the two lists of the concentrated loads x and y coordinates into the normalized nodal format that the program expects.
We construct a line in the input file that corresponds to each concentrated load.
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 denotes an object reference in the Value: parameter. Each object reference will be replaced by an object value when the EXPAND 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.txt with our own identically formatted input data.
It is a good idea to clear away redundant files to minimize disk space usage.
The PROCESSES branch should look like,
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.
We will translate the input file plate.txt into a template containing 'delimited' object references which are placeholders for the User specified input values.
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 below,
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
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 the job has completed, we may look at 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 an error either in the EASAP settings or in the template input file. We may attempt to fix these problems at this time or wait until Session 8, in where we test and debug the completed EASAP. After reviewing the file, click on the Back button
If you do not see the PLATE.OUT link or the file content shown above, then may have an error either in the EASAP settings or in your template input file. We may attempt to fix these problems at this time or wait until Session 8, where we test and debug the completed EASAP. After reviewing the file, click on the x to close the window.
Review the values of data produced in the EASAP.
You may browse through all pages of the table to review values of all data in the EASAP run.
We have completed Session 5. Let's continue with Session 6.