Difference between revisions of "TUFLOW Modelling Log"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
A modelling log is highly recommended and should be a requirement on all projects. It is a technical document that provides a history of all key modelling assumptions. The log may be in Excel, Word or other suitable software. Use of a modelling log has the following benefits: | A modelling log is highly recommended and should be a requirement on all projects. It is a technical document that provides a history of all key modelling assumptions. The log may be in Excel, Word or other suitable software. Use of a modelling log has the following benefits: | ||
| − | * | + | *it provides a record of model development; |
*it facilitates traceability of input sources and modeller actions; and | *it facilitates traceability of input sources and modeller actions; and | ||
*aids in the transfer of models between different users.<br> | *aids in the transfer of models between different users.<br> | ||
Revision as of 09:07, 30 December 2021
A modelling log is highly recommended and should be a requirement on all projects. It is a technical document that provides a history of all key modelling assumptions. The log may be in Excel, Word or other suitable software. Use of a modelling log has the following benefits:
- it provides a record of model development;
- it facilitates traceability of input sources and modeller actions; and
- aids in the transfer of models between different users.
The format of the modelling log is up to the individual or company. However, it is common to use a spreadsheet be developed for use as a modelling log. Typical details to be entered into the log are:
- names (or ID) of TUFLOW simulation control files;
- date of simulation;
- model user;
- details of the event modelled (duration, recurrence interval, etc.); and
- changes since last simulation.
A template modelling log is included in the Module_01\Tutorial_Data folder of the files supplied with the TUFLOW tutorial downloads.