Code style
- main real change is the addition a coeffDict to refactor the code.
Edited by Mark OLESEN
Merge request reports
Activity
mentioned in commit 28c8d896
Just as a note to ourselves (or others) - like discussed on the phone yesterday, there are a few other ways to pass around the various model properties, none of which are perhaps necessary at the moment.
- could create friction/entrainment/deposition properties based on
Time
or thefaMesh
and uselookupObject
to obtain thetransportProperties
IOdictionary instead of passing it in directly as an argument. - or could define a generic base class (maybe
avalancheModel
oravalancheParameters
) that is a system IOdictionary and then pass this as a reference for all the various bits (deposition, friction,...).
IMO none of this is required at the moment, but might be needed in the future as the models grow in number and complexity.
- could create friction/entrainment/deposition properties based on
Please register or sign in to reply