| modeFRONTIER / Star-CD tutorial: optimization of a blunt object |
| Previous | Index | Next |
3.1.2. Data Output
Click on the Output File icon
and put one into the Work Flow canvas.
Click on the Output Variable icon
and place in the Work Flow canvas as many Output Variables
as we need (in this case three) (see Fig.1).
Note: keep the Ctrl button pressed if we want to put more than one Output Variable
without reselecting it again from the tool bar.
|
| Fig. 1: Output Files and Output Variables |
|---|
Double click on the Output File node to show its proprieties, and rename it, see
(Fig.2).
Note: It is madatory that the name of the Output File node is the same of the
Output File written by our application (in this case Prostar).
|
| Fig. 2: Output File Properties |
|---|
Do the same with each Output Variable: rename them and link them to the correct Output File (link lift and drag to result.out and mom to resultm.out) , as in Fig.3.
|
| Fig. 3: Output Variable Properties |
|---|
After we have finished, the Work Flow window should look like in Fig.4.
|
| Fig. 4: Output Files and Output Variables renamed and linked |
|---|
Go back to the Output File node Properties to choose the Output File Template,
as we did with the Input File (see Fig.5).
Click on the Open button in the Output File properties window.
A new window will appear and we have to select a Template Output File
that define the response of our model (the file where our variables will be exctracted from).
Browse through the file system and search
the proper Output File (at least one time we must analyze and post-process our model to have an Output File
to use it as template), see Fig.5 and Fig.6).
|
| Fig. 5: Output File Properties |
|---|
|
| Fig. 6: Output File Selectio |
|---|
After we selected the proper file, the Template Output Editor will show us the template Output File.
The window is split into two parts: in the top part the Output File is edited, in the bottom part there is a list of
the Output Variables connected to the Output File (see Fig.7).
/P>
|
| Fig. 7: Work Flow - Template Output Editor |
|---|
To mine an Output Variables from an Output File follow this procedure:
|
| Fig. 8: Output Variable extraction |
|---|
When we have completed the extraction of the first Output Variables from the Output File we can read the mining rule beside the Output Variable name (see Fig.9).
|
| Fig. 9: The mining rule |
|---|
Repeat the above operation for all the remaining Output Variables related to this Template Output File and finally the Template Output Editor window will look like in Fig.10.
|
| Fig. 10: All Output Variable have been extracted |
|---|
Do the same with the Output File and Output Variables related to the moment.
Look at the Summary Panel to check changes made on the Output Variables, if everythig
is ok the Output Variable Summary table should look like Fig.11.
|
| Fig. 11: Output Variable Summary table |
|---|
Now we have completed the mining of Output Variables from Output Files.
The next step is to define the External Script running the Application. It reads the model from
the Input File, analyzes it and writes Output Files.
| Previous | Top | Next |
| © ES.TEC.O. S.r.l.- ENGIN SOFT TECNOLOGIE PER L'OTTIMIZZAZIONE |