1Blurb:: 2Selects custom-annotated tabular file format 3 4Description:: 5 6A custom-annotated tabular file is a whitespace-separated text file 7typically containing row data for variables, or variables followed by 8responses, though the format is used for other tabular exports/imports 9as well. Custom-annotated allows user options for whether \c header 10row, \c eval_id column, and \c interface_id column appear in the 11tabular file, thus bridging \c freeform and (fully) \c annotated. 12 13<b> Default Behavior </b> 14 15The \c annotated format is the default for tabular export/import. To 16control which header row and columns are in the input/output, specify 17\c custom_annotated, followed by options, in the relevant 18export/import context. 19 20<b> Usage Tips </b> 21 22\li Prior to October 2011, calibration and surrogate data files were 23in free-form format. They now default to \c annotated format, though \c 24freeform remains an option. 25 26\li When importing tabular data, a warning will be generated if a 27specific number of data are expected, but extra is found and an error 28generated when there is insufficient data. 29 30\li Some TPLs like SCOLIB and JEGA manage their own file I/O and only 31support the \c freeform option. 32 33Topics:: file_formats 34Examples:: 35 36Export a custom-annotated tabular file in Dakota 6.0 format, which 37contained only header and eval_id (no interface_id), and data for 38variables and responses. Input file fragment: 39\verbatim 40environment 41 tabular_data 42 tabular_data_file = 'dakota_summary.dat' 43 custom_annotated header eval_id 44\endverbatim 45Resulting tabular file: 46\verbatim 47%eval_id x1 x2 obj_fn nln_ineq_con_1 nln_ineq_con_2 481 0.9 1.1 0.0002 0.26 0.76 492 0.90009 1.1 0.0001996404857 0.2601620081 0.759955 503 0.89991 1.1 0.0002003604863 0.2598380081 0.760045 51... 52\endverbatim 53 54Theory:: 55Faq:: 56See_Also:: 57