EART66001 Chap.4 Simulation Workflow and Model Logs
Simulation Workflow and Model Logs
Simulation Workflow and Model Logs makes a model result reproducible. An unsteady run connects a model file to an event or simulation file containing start and finish times, time step, save interval, boundaries and output location. Runtime messages show progress and failures but do not establish physical validity.
Results may include stage and flow time series, cross-sections, long sections, tables, animations and maps, so output selection must follow the project objective. The model log records the model variant, simulation, purpose, changed setting, result files and their paths.
Stable names and separate folders protect the baseline and allow another person to trace a figure back to the configuration that produced it.
Pre-run control begins with file references. Confirm which model and boundary files the event uses, where outputs will be written and whether the run period and save interval allow the intended comparison. Duplicate rather than overwrite a baseline.
Change only the factor named by the scenario and record its old and new settings. These steps prevent a later graph from combining a correct label with the wrong configuration.
During execution, save warning or failure information and the corrective action. A successful completion shows that the numerical process finished, not that the result is physically credible.
Inspect the output against the conceptual model, expected timing and known system behaviour. Select the view suited to the objective: time series for temporal patterns, sections for geometry and level, long profiles for along-reach behaviour, and maps for spatial extent.
Close every run with a model-log entry. Include purpose, model, simulation, changed setting, result files, storage path and status.
Use identical scenario labels in the log, figures and report. At review, trace selected evidence backward to files and forward from objectives to conclusions. This two-way audit distinguishes reproducible analysis from a folder of plausible-looking exports.
What this chapter covers
- 01
Event files
- 02
Run settings
- 03
Runtime messages
- 04
Output selection
- 05
Version control
- 06
Model-log audit
Worked example · free
Create an altered-flow run safely
- 1Duplicate and rename the event file without overwriting the baseline.
- 3Verify model path, boundaries, run period, time step, save interval and output directory before changing the intended inflow.
- 2Run, inspect comparable outputs and record every file and purpose in the model log.
Key terms
- Simulation file
- A file that identifies the model, boundaries, run settings and output location for a run.
- Model variant
- A preserved configuration created for a defined purpose or scenario.
- Model log
- An audit record connecting model variants, simulations, purposes, outputs and storage paths.
Simulation Workflow and Model Logs FAQ
Does a completed run mean the result is valid?
No. Completion means the numerical process reached its end. Inspect warnings, physical plausibility, relevant outputs, calibration evidence and the conceptual model before using the result to support a project conclusion.
Which outputs should go into the report?
Choose the smallest set that answers the objectives. Time series reveal timing and peaks, sections relate water level to geometry, and maps show spatial extent. Preserve other outputs for audit without turning the report into an interface tour.
What belongs in the model log?
Record the model and simulation files, scenario purpose, changed inputs, result files, storage paths, status and notable messages or corrections. Another modeller should be able to locate and understand the exact run without relying on memory.
How should exported figures be controlled?
Keep the source result identifier with every export, verify axes and units after formatting, and use the same scenario label as the model log. If data are transformed in another tool, record the calculation or processing step. This prevents a polished chart from becoming a second, undocumented version of the model evidence.
Assessment move
Rehearse the simulation workflow from file lineage outward. Draw a box for the model file, another for the event or simulation file and a third for results, then write the critical settings on the arrows. Before each practical run, read the model path, boundary references, start and finish time, time step, save interval and output folder.
Preserve the baseline and use scenario names that also appear in graphs, notes and the model log. Treat runtime warnings as evidence: capture the message, describe the correction and keep the earlier attempt when it helps explain the model history. Match each output to a question. Use time series for change through time, cross-sections for geometry and level, long sections for along-reach patterns, and maps for spatial extent.
Practise captions that name scenario, variable, location and the pattern a reader should notice. At the end of every session, complete the model-log entry and write the next action. During final review, sample several figures and trace each one backward to a result, simulation, model variant and objective. Repair broken traces before editing visual style because an attractive unidentified graph remains weak evidence.
Working through Simulation Workflow and Model Logs in EART66001? Sia is AskSia’s AI Environmental Science tutor — ask any EART66001 Simulation Workflow and Model Logs question and get a clear, step-by-step explanation grounded in how EART66001 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.