Revision as of 14:43, 19 December 2014 view source Mitch3007 (talk \| contribs) Bureaucrats, Administrators 1,585 edits →Use of Scenarios to Modify 2d Grid Resolution ← Older edit		Revision as of 14:45, 19 December 2014 view source Mitch3007 (talk \| contribs) Bureaucrats, Administrators 1,585 edits →Use of Scenarios to Modify 2d Grid Resolution Newer edit →
Line 57: Within this example the 2D cell size, 2D timestep and log output frequency have been set as scenario dependent through an external read file called from the TCF: <font color="blue"><tt>Read File </tt></font> <font color="red"><tt>==</tt></font> <tt> FMA_T1_CellSize_Commands_001.trd </tt><br> When the model is initialised the scenario value determines the 2D_CELL_SIZE, 2D_Timestep and LogInt variables which, are set using the 'Set Variable' command in the trf. ~~This~~Each ~~results~~variable inis ~~scenario~~then ~~dependent~~replaced ~~values~~in ofthe ~~2D_CELL_SIZE, 2D_Timestep~~TCF and ~~LogInt~~TGC ~~values. Using~~using the << >> syntax, ~~values within the tcf and tgc files are substituted. For~~for example for the -s 10ft scenario: *Within the TCF, <<2D_Timestep>> is replaced with 1 and <<logInt>> is replaced with 30; and

FMA Challenge 1 (1D-2D linked): Difference between revisions