1Blurb::
2Tag each parameters & results file name with the function evaluation
3number
4
5Description::
6If this keyword is used, Dakota will append a period and the function evaluation
7number to the names of the parameter and results files.
8
9<b>Default Behavior</b>
10If this keyword is omitted, the default is no file tagging.
11
12<b>Usage Tips</b>
13- File tagging is most useful when multiple function evaluations are
14  running simultaneously using files in a shared disk space. The
15  analysis driver will be able to infer the function evaluation number
16  from the file names.
17
18- Note that when the \c file_save keyword is used, %Dakota
19  automatically renames parameters and results files, giving them tags
20  after execution of the analysis driver if they otherwise would be
21  overwritten by the next evaluation.
22
23Topics::
24
25Examples::
26If the following is included in the \c interface section of the Dakota
27input:
28
29\verbatim
30  parameters_file = params.in
31  results_file = results.out
32  file_tag
33\endverbatim
34
35Then for the 3rd evaluation, Dakota will write \c params.in.3, and will expect
36\c results.out.3 to be written by the analysis driver.
37
38Theory::
39Faq::
40See_Also::
41