HPC Impact Assessment Guidance: Difference between revisions

Content deleted Content added

Revision as of 14:06, 20 April 2018 view source Chris Huxley (talk \| contribs) Bureaucrats, Administrators 7,786 edits →Reduced Control Number Factor ← Older edit		Latest revision as of 15:31, 30 May 2022 view source Chris Huxley (talk \| contribs) Bureaucrats, Administrators 7,786 edits →Reduced Control Number Factor
(One intermediate revision by one other user not shown)
Line 1: When completing an impact assessment, the modeller should endeavour to compare “apples with apples”. This means attempting to keep everything in the model exactly the same, apart from the development features. Because the HPC solver implements adaptive timestepping, the implementation of new features into the TUFLOW model for a development design case, may result in the HPC model running with a different timeseries of timesteps to the base case model. <br> Though this has not been an issue to date and while it is not expected to produce any artificial impacts, there are some steps that can be taken to ensure that observed impacts are a result of the development features and not a result of change in the model timestep.<br> Line 20: [[File: CN Flood Impacts.png \|600px]] <br> <br> {{Tips Navigation \|uplink=[[ HPC_Modelling_Guidance \| Back to HPC Modelling Guidance]] }}