In this session, we create a PROCESS to:
1. Let's get started:
2. We need to upload a few files required by the EASAP.
'input.txt' will be added to the list of current files shown below the 'Browse' and 'Upload' buttons.
'input.txt' contains responses to queries from the executable that would otherwise be typed at an interactive command prompt.
3. Let's create a PROCESS for running the plate analysis batch software.
4. We need to manipulate each User input into the form required by the batch input file plate.txt
5. Let's create a MAP to associate a plate material with a modulus of elasticity which is required by the plate analysis software.
Try a CTRL-c CTRL-v shortcut:
- Highlight 'Steel, Aluminum, Titanium' in: TABBED PANE LIST > input > mat > Choices:
- Type CTRL-c to copy the string
- Type CTRL-v to paste the string into modulus > Inputs:
6. Let's create a similar MAP for the material’s Poisson ratio.
7. We use a COMPUTE to translate the plate’s dimensions into a uniform element size that is expected in the input file. The plate needs to be divided into 20 elements along its length:
The PROCESSES branch of the EASAP Tree should look like this,
The order of execution within a PROCESS object is always:
- DATA PROCESSING objects
- REPLACEMENT objects
- Commands specified in the Run Using: parameter of the PROCESS object
- The CLEAR FILESPACE object
The order of objects on the Tree within a PROCESS is not important
The order of execution of multiple PROCESS objects is based on their order on the Tree
…Execution order is from top to bottom.
9. Save the EASAP.
10. We will now go through the process of replacing fixed inputs (text strings or numbers) with object references.
We use 'plate.txt' as a template which specifies the correct format for inputs generated by the EASAP User at runtime.
If you encounter problems setting units for dx, ensure that the Unit Group: parameter has been set properly. If you need to go back and make a change in EASAP Builder keep the Template Editor open and after saving your changes in the EASAP Builder select: File > Reload
At this point the file will appear in the Template Editor as follows,
11. At this point, our EASAP will be ready for its first test run.
Even though the OUTPUT branch is empty and nothing will be displayed on the results pages, we may still submit a test run and take a look at what is produced at this point.
12. If there aren't any rows in the table, click the browser refresh button.
Queued - implies the job is waiting for some other jobs to finish before starting to run
[Percentage value] - implies the job is currently running
Completed - implies the job is done
13. Once the job has completed, examine some of the files produced by the test run.
14. Let’s check the delimited object reference replacements for the input file, plate.txt
If the file content shown above is missing or different, there may be an error in the EASAP settings or in the template input file. We may attempt to fix these problems at this time or wait until Session 5, where we test and debug an EASAP.
15. Let’s look at the PLATE.OUT output file produced by the underlying software application.
If there is no PLATE.OUT link or the file content differs from what is shown above, there is an error in the EASAP settings or in the template input file. After reviewing the file, close the window.
Let's review the values of data produced in the EASAP:
We are now finished with Session 3. Let's continue with Session 4.