Estimated completion time = 20 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 file, and edit a batch input file into a template with Delimited Object References (DORs).
The first task is to upload a few files required by the EASAP.
input.txt and click on the Upload button.
input.txt file will be added to the list of current files shown below the Browse and Upload buttons.
femrctpl.exe is the executable,
plate.txt contains input data, and
input.txt contains responses to queries from the executable that would otherwise be typed at the command prompt.
Now we create the PROCESS for running the plate analysis software.
|cmd.exe /C "femrctpl.exe < input.txt"
Now we set up the objects needed to manipulate the user input data into a form appropriate for replacement within the batch input file, in this case
Now we create a MAP to map a particular plate material into the modulus of elasticity which is required by the plate analysis software.
Tip: Copy the contents of the Choices: parameter of the TABBED PANE LIST→input→mat and Paste it as the modulus→Inputs: parameter value.
|Steel, Aluminum, Titanium
|27600, 10600, 15000
Create a similar MAP for the material’s Poisson ratio.
|0.305, 0.33, 0.34
Now we will move on to translate the plate’s dimensions into the uniform element size that is expected in the input file. The plate is divided into 20 elements along its length. Create a COMPUTE:
The next step for the runplate process is to add a REPLACEMENT object for its input file,
plate.txt from the choice list.
The PROCESSES branch of the EASAP Tree should look like this:
Therefore the order of objects on the tree within a PROCESS 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.
The Template Editor will start in a new window. We will now go through the process of replacing fixed input values, such as text strings and numbers, with DORs.
Tip: If you encounter problems setting the units of the DOR, ensure that the Unit Group: parameter has been set properly for the dx COMPUTE. If you need to go back and make a change in EASAP Builder, you should keep Template Editor open and just select File→Reload after saving your changes in the Builder.
At this point the file will appear in the Template Editor as follows:
At this point, your 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, you can still submit a test run and take a look at what is produced at this point.
After a second or two, a pop-up window will appear when the EASAP has been submitted successfully.
The page should look like:
It will probably be the only entry in the table. If you do not see any rows in the table, try clicking the refresh button on your browser. 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.
A pop-up window will appear that will look like the following:
Let’s 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 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 5, in which you will be testing and debugging your completed EASAP.
Now let’s look at the output file,
PLATE.OUT, produced by the underlying software application.
If you do not see the
PLATE.OUT link or the file content shown above, then you have an error in your EASAP settings or in your template input file. After reviewing the file, close the window.
Now, review the values of data produced in the EASAP.
You are now finished with Practical Session 3.