Hydromodel SA Wiki - User contributions [en]

Stack Exchange Question & Answer platform

2023-12-04T10:40:09Z

Julia Glenday:

''Have you ever been stuck when trying to get a hydrological model to work, not able to find the solution in a manual or from colleagues, and struggling to contact an expert with time to assist? 
''Are you an advanced model user who wishes they could help others more, but don’t have much spare time for added meetings or troubleshooting via email? 
''Are you an instructor who spends a lot of time answering the same modelling questions from your students many times over?

The [https://stackexchange.com Stack Exchange] platform is a readily available resource that can easily be used as a support system for hydrological modelling. It is a well-known, free, question-and-answer (Q&A) website. Anyone can create a log-in and ask or answer a question, tagging it for specific themes. Questions and answers on the site are then easy to search for and find. For hydrological modelling questions, we advocate use of the [https://earthscience.stackexchange.com/ '''Earth Science Stack Exchange'''].

By using such a platform, we can:
* make support for hydrological modelling more accessible and transparent online, and
* become more efficient in providing one another with support by documenting questions and answers on an easily searchable website, such that advanced users do not need to answer the same common questions multiple times over.

Researchers, students and practitioners are encouraged to add their modelling questions to the platform and answer each other's questions, starting a critical mass of activity on the site. This will strengthen the modelling community locally and can allow for interaction with users of these tools overseas as well.

'''Lecturers, instructors, advanced users:''' Consider transitioning from answering questions via email to answering them on Stack Exchange. Request that the person asking puts their question on the site and sends you the link it. You can also post common Q&A’s to the site in advance (you can answer your own question) and direct people to look there first before coming to you with questions.

'''Students, newer model users:''' Try asking your questions on Stack Exchange rather than via email. With time there will be more and more Q&As on the site so you can search existing posts for help first, before posting a new question. When you’ve posted a new question, you can send the link to a lecturer or advanced user who you think can answer it and ask them if they can answer via the site.

'''Everyone:''' If you’ve worked through a problem on your own, with a group, or with an instructor, do the community a favour and post it as a Q&A on Stack Exchange. One person can post the question and another can answer, or one can post both Q&A. This allows anyone in the world to find the Q&A, and you may even get suggestions of other even more efficient solutions.

''Below you'll find more background information on how Stack Exchange works and a step-by-step guide for getting started with using it. This information is also available as a PDF document you can download and share with your colleagues, students, or instructors:'' [[:File: Stack_Exchange_Guidelines_for_hydro_modelling_support.pdf ‎|'''''Download PDF guide here''''']]

== How does Stack Exchange work? ==

Stack Exchange is a network of question-and-answer (Q&A) websites each with a different focus topic, such as computer programming, mathematics, or earth science (see all sites: https://stackexchange.com/sites). The initial site, called Stack Overflow, is a Q&A site for computer programming created by Jeff Atwood and Joel Spolsky in 2008. The usefulness of this site generated demand for similar sites for other topics.
There is no site specifically for hydrological modelling at this time, but the Earth Science site (https://earthscience.stackexchange.com) hosts both hydrology and modelling questions. If and when there are enough users asking and answering hydrology and hydrological modelling questions, a more specific site(s) could be launched in the future.

Stack Exchange sites have features that allow them to be moderated by their user community:

* ''' Anyone can search for and view existing Q&A strings on the site - no log-in is required.'''

* '''Create an account/log-in to post:''' One needs to create an account and log in to the site to post a question or an answer or to add votes, edits, or comments. Profile names are shown alongside all posts for accountability.

* '''Tags:''' Tags are simple keywords or search terms which users assign to their questions to help people find them. If you are looking to find out if a question has been asked and answered already, a simple Google Search on the question will usually find related Stack Exchange Q&A posts. It is also possible to search within Stack Exchange sites using tags. This is one way to look for questions you may wish to answer (e.g., search unanswered questions with a specific tag, like ‘hydrology’). Only more advanced users (see below) can add new words to the tags list for a site. If a tag does not receive sufficient use, it will be removed from the list.

* '''Reputation points:''' Any logged-in user can post questions and answers, ‘accept’ an answer to their question, and propose edits to posts (to be reviewed by authors). Users also build up “reputation points”. Points allow a user to access more site functions, such as ‘upvoting’ posts, proposing new keywords for tagging, commenting, putting oneself up for election to be a moderator, etc. Points are gained by posting questions and answers, having your answer be ‘accepted’ by the user who asked the question, having your answer be upvoted, etc. More advanced use can result in ‘badges’ (bronze, silver, gold) that show up on the user’s profile and when they post. https://earthscience.stackexchange.com/help/whats-reputation

* '''Upvoting:''' Logged-in users with 15 or more reputation points can ‘upvote’ questions and answers that they find to be useful and appropriate. There may be many answers posted for a single question. When an answer has been formally ‘accepted’ by the user who asked the question, this answer will be shown at the top of the list. The asker can change which is the ‘accepted’ answer as new answers are posted. Other answers are listed in order of the number of votes they have received. Not all askers ‘accept’ an answer. In this case, the number of votes determines which is listed first. Upvotes may prompt the asker to review which answer they ‘accept’. Each user has a limited number of votes they can cast per day. https://earthscience.stackexchange.com/help/privileges/vote-up

* '''Moderation & disputes:''' Elected moderators are responsible for managing the site, through activities such as following up on flagged posts, locking and protecting posts, suspending users, and deleting the worst posts on the site. Stack Exchange aims for moderators to be minimally involved, respect users, and lead by example. Each Stack Exchange site has a "meta" section where users can ask questions about the site itself and also settle disputes in a separate forum to the Q&A strings.

For more information about how Stack Exchange and the Earth Science site work follow the links below:

https://earthscience.stackexchange.com/tour

https://earthscience.stackexchange.com/help

https://en.wikipedia.org/wiki/Stack_Exchange

== Step by step guide to using Stack Exchange for hydrological modelling support ==

=== Getting started - create an account ===

# Go to the Earth Sciences Stack Exchange site: https://earthscience.stackexchange.com/
# '''Create an account''' (display name, email, password) if you don’t already have one.
# Go through the site tour (should appear when you create your account): https://earthscience.stackexchange.com/tour
# '''Access & edit your profile''': Once your profile exists you can edit things like your display name, profile icon or image, and specify your email preferences. You can control if and how you want to be contacted by email by the site (e.g., can be notified if someone answers your question, posts a question with a ‘tag’ that you are following, etc). When you are logged in, you can open your profile by clicking on your profile image on the top bar at the right. Here you can also see a log of the questions you’ve asked, those you’ve answered, your reputation points, etc.

=== Asking questions ===

# '''Log-in''' to your profile on the Earth Sciences Stack Exchange site: https://earthscience.stackexchange.com/
# Before posting a question, do a '''search to see if the question has already been asked.''' If it has been asked and answered, and you find the posts helpful and you have 15+ reputation points, you can ‘upvote’ questions and answers using the arrows at the side of the posts.
# '''To post:''' Click on “Ask Question”
# Add a title, body text and tags for your question. '''Please tag with “hydrology” and “modelling”''', plus any other relevant tags of your choice. Tags must come from the list of tags for the Earth Sciences site. Users with 150 reputation points or more can propose new tags. Other relevant tags available include: hydrogeology, water, groundwater, water-vapour, water-table, watershed. Full tags list: https://earthscience.stackexchange.com/tags
# '''Review & post:''' After drafting your question you get to review it; see how it will appear on the site and proofread it one more time. When satisfied, hit “Post.”
# If you already know an expert or advanced model user who is likely to be able to answer your question, you may wish to contact them with a link to your question on Stack Exchange and encourage them to answer it on the site so that everyone can access it.
# '''Editing after posting:''' After you’ve posted a question, if you realise that you want to change the phrasing, add a detail, etc, perhaps prompted by the answers and comments coming in, you can edit your question.
# '''Review the answers, accept, vote:''' Once people have posted answers and you’ve tried some of them out, you can “accept” an answer that has worked for you. If you have 15+ reputation points you can also “upvote” other useful answers.

=== Answering questions ===

# '''Log-in''' to your profile on the Earth Sciences Stack Exchange site: https://earthscience.stackexchange.com/
# '''Find a question to answer:''' Someone may have contacted you to answer a question that they’ve asked on the site and sent a link. Otherwise, you can search using keywords of your choice in the normal search bar or use the panel on the left to find questions with one or more specified tags (e.g. “hydrology” and “modelling”), look for unanswered questions only, etc. Using “My tags” will find posts related to tags you have elected to follow and ones you have used when posting. You can add a new answer to a question that already have an answer posted if you have a different approach or a refinement to share that may be helpful. '''Answering your own question:''' A user can post an answer to their own question. There is no harm in doing this. The user will not receive points for this answer, or for it being upvoted.
# At the bottom of each question post you will find a box titled '''“Your Answer”''' where you can enter your answer and post it. This entry box will be located below any previously posted answers to the question. After posting, your answer can move higher in the list of answers if it gets 'upvoted.'

== Tips for asking a good question ==

Before you post a question, search the site to make sure your question hasn’t been answered already.

When you decide to write a question:
* Summarize the problem
* Provide details: When appropriate, describe what you’ve already tried in an effort to solve a problem on your own and what happened. This can include describing research you’ve done to try to find the answer (can include citations, links, etc) and why this was insufficient to resolve the issue.
* Be specific: Avoid very broad or open-ended questions that are likely to have many answers or primarily illicit opinions. If necessary, break up your query into multiple more specific questions. These can be linked to one another, i.e. you can include a weblink to a previous question in the body of a new question when it is a follow-on issue.

More guidance:
https://earthscience.stackexchange.com/help/asking

Example post:
https://earthscience.stackexchange.com/questions/24081/cannot-initialize-mike-1d-failed-when-solving-for-a-steady-state-solution-wat/24084#24084

Stack Exchange Question & Answer platform

2023-12-04T10:39:30Z

Julia Glenday:

''Have you ever been stuck when trying to get a hydrological model to work, not able to find the solution in a manual or from colleagues, and struggling to contact an expert with time to assist? 
''Are you an advanced model user who wishes they could help others more, but don’t have much spare time for added meetings or troubleshooting via email? 
''Are you an instructor who spends a lot of time answering the same modelling questions from your students many times over?

The [https://stackexchange.com Stack Exchange] platform is a readily available resource that can easily be used as a support system for hydrological modelling. It is a well-known, free, question-and-answer (Q&A) website. Anyone can create a log-in and ask or answer a question, tagging it for specific themes. Questions and answers on the site are then easy to search for and find. For hydrological modelling questions, we advocate use of the [https://earthscience.stackexchange.com/ '''Earth Science Stack Exchange'''].

By using such a platform, we can:
* make support for hydrological modelling more accessible and transparent online, and
* become more efficient in providing one another with support by documenting questions and answers on an easily searchable website, such that advanced users do not need to answer the same common questions multiple times over.

Researchers, students and practitioners are encouraged to add their modelling questions to the platform and answer each other's questions, starting a critical mass of activity on the site. This will strengthen the modelling community locally and can allow for interaction with users of these tools overseas as well.

'''Lecturers, instructors, advanced users:''' Consider transitioning from answering questions via email to answering them on Stack Exchange. Request that the person asking puts their question on the site and sends you the link it. You can also post common Q&A’s to the site in advance (you can answer your own question) and direct people to look there first before coming to you with questions.

'''Students, newer model users:''' Try asking your questions on Stack Exchange rather than via email. With time there will be more and more Q&As on the site so you can search existing posts for help first, before posting a new question. When you’ve posted a new question, you can send the link to a lecturer or advanced user who you think can answer it and ask them if they can answer via the site.

'''Everyone:''' If you’ve worked through a problem on your own, with a group, or with an instructor, do the community a favour and post it as a Q&A on Stack Exchange. One person can post the question and another can answer, or one can post both Q&A. This allows anyone in the world to find the Q&A, and you may even get suggestions of other even more efficient solutions.

''Below you'll find more background information on how Stack Exchange works and a step-by-step guide for getting started with using it. This information is also available as a PDF document you can download and share with your colleagues, students, or instructors:'' [[:File: Stack_Exchange_Guidelines_for_hydro_modelling_support.pdf ‎|'''''Download guide PDF here''''']]

== How does Stack Exchange work? ==

Stack Exchange is a network of question-and-answer (Q&A) websites each with a different focus topic, such as computer programming, mathematics, or earth science (see all sites: https://stackexchange.com/sites). The initial site, called Stack Overflow, is a Q&A site for computer programming created by Jeff Atwood and Joel Spolsky in 2008. The usefulness of this site generated demand for similar sites for other topics.
There is no site specifically for hydrological modelling at this time, but the Earth Science site (https://earthscience.stackexchange.com) hosts both hydrology and modelling questions. If and when there are enough users asking and answering hydrology and hydrological modelling questions, a more specific site(s) could be launched in the future.

Stack Exchange sites have features that allow them to be moderated by their user community:

* ''' Anyone can search for and view existing Q&A strings on the site - no log-in is required.'''

* '''Create an account/log-in to post:''' One needs to create an account and log in to the site to post a question or an answer or to add votes, edits, or comments. Profile names are shown alongside all posts for accountability.

* '''Tags:''' Tags are simple keywords or search terms which users assign to their questions to help people find them. If you are looking to find out if a question has been asked and answered already, a simple Google Search on the question will usually find related Stack Exchange Q&A posts. It is also possible to search within Stack Exchange sites using tags. This is one way to look for questions you may wish to answer (e.g., search unanswered questions with a specific tag, like ‘hydrology’). Only more advanced users (see below) can add new words to the tags list for a site. If a tag does not receive sufficient use, it will be removed from the list.

* '''Reputation points:''' Any logged-in user can post questions and answers, ‘accept’ an answer to their question, and propose edits to posts (to be reviewed by authors). Users also build up “reputation points”. Points allow a user to access more site functions, such as ‘upvoting’ posts, proposing new keywords for tagging, commenting, putting oneself up for election to be a moderator, etc. Points are gained by posting questions and answers, having your answer be ‘accepted’ by the user who asked the question, having your answer be upvoted, etc. More advanced use can result in ‘badges’ (bronze, silver, gold) that show up on the user’s profile and when they post. https://earthscience.stackexchange.com/help/whats-reputation

* '''Upvoting:''' Logged-in users with 15 or more reputation points can ‘upvote’ questions and answers that they find to be useful and appropriate. There may be many answers posted for a single question. When an answer has been formally ‘accepted’ by the user who asked the question, this answer will be shown at the top of the list. The asker can change which is the ‘accepted’ answer as new answers are posted. Other answers are listed in order of the number of votes they have received. Not all askers ‘accept’ an answer. In this case, the number of votes determines which is listed first. Upvotes may prompt the asker to review which answer they ‘accept’. Each user has a limited number of votes they can cast per day. https://earthscience.stackexchange.com/help/privileges/vote-up

* '''Moderation & disputes:''' Elected moderators are responsible for managing the site, through activities such as following up on flagged posts, locking and protecting posts, suspending users, and deleting the worst posts on the site. Stack Exchange aims for moderators to be minimally involved, respect users, and lead by example. Each Stack Exchange site has a "meta" section where users can ask questions about the site itself and also settle disputes in a separate forum to the Q&A strings.

For more information about how Stack Exchange and the Earth Science site work follow the links below:

https://earthscience.stackexchange.com/tour

https://earthscience.stackexchange.com/help

https://en.wikipedia.org/wiki/Stack_Exchange

== Step by step guide to using Stack Exchange for hydrological modelling support ==

=== Getting started - create an account ===

# Go to the Earth Sciences Stack Exchange site: https://earthscience.stackexchange.com/
# '''Create an account''' (display name, email, password) if you don’t already have one.
# Go through the site tour (should appear when you create your account): https://earthscience.stackexchange.com/tour
# '''Access & edit your profile''': Once your profile exists you can edit things like your display name, profile icon or image, and specify your email preferences. You can control if and how you want to be contacted by email by the site (e.g., can be notified if someone answers your question, posts a question with a ‘tag’ that you are following, etc). When you are logged in, you can open your profile by clicking on your profile image on the top bar at the right. Here you can also see a log of the questions you’ve asked, those you’ve answered, your reputation points, etc.

=== Asking questions ===

# '''Log-in''' to your profile on the Earth Sciences Stack Exchange site: https://earthscience.stackexchange.com/
# Before posting a question, do a '''search to see if the question has already been asked.''' If it has been asked and answered, and you find the posts helpful and you have 15+ reputation points, you can ‘upvote’ questions and answers using the arrows at the side of the posts.
# '''To post:''' Click on “Ask Question”
# Add a title, body text and tags for your question. '''Please tag with “hydrology” and “modelling”''', plus any other relevant tags of your choice. Tags must come from the list of tags for the Earth Sciences site. Users with 150 reputation points or more can propose new tags. Other relevant tags available include: hydrogeology, water, groundwater, water-vapour, water-table, watershed. Full tags list: https://earthscience.stackexchange.com/tags
# '''Review & post:''' After drafting your question you get to review it; see how it will appear on the site and proofread it one more time. When satisfied, hit “Post.”
# If you already know an expert or advanced model user who is likely to be able to answer your question, you may wish to contact them with a link to your question on Stack Exchange and encourage them to answer it on the site so that everyone can access it.
# '''Editing after posting:''' After you’ve posted a question, if you realise that you want to change the phrasing, add a detail, etc, perhaps prompted by the answers and comments coming in, you can edit your question.
# '''Review the answers, accept, vote:''' Once people have posted answers and you’ve tried some of them out, you can “accept” an answer that has worked for you. If you have 15+ reputation points you can also “upvote” other useful answers.

=== Answering questions ===

# '''Log-in''' to your profile on the Earth Sciences Stack Exchange site: https://earthscience.stackexchange.com/
# '''Find a question to answer:''' Someone may have contacted you to answer a question that they’ve asked on the site and sent a link. Otherwise, you can search using keywords of your choice in the normal search bar or use the panel on the left to find questions with one or more specified tags (e.g. “hydrology” and “modelling”), look for unanswered questions only, etc. Using “My tags” will find posts related to tags you have elected to follow and ones you have used when posting. You can add a new answer to a question that already have an answer posted if you have a different approach or a refinement to share that may be helpful. '''Answering your own question:''' A user can post an answer to their own question. There is no harm in doing this. The user will not receive points for this answer, or for it being upvoted.
# At the bottom of each question post you will find a box titled '''“Your Answer”''' where you can enter your answer and post it. This entry box will be located below any previously posted answers to the question. After posting, your answer can move higher in the list of answers if it gets 'upvoted.'

== Tips for asking a good question ==

Before you post a question, search the site to make sure your question hasn’t been answered already.

When you decide to write a question:
* Summarize the problem
* Provide details: When appropriate, describe what you’ve already tried in an effort to solve a problem on your own and what happened. This can include describing research you’ve done to try to find the answer (can include citations, links, etc) and why this was insufficient to resolve the issue.
* Be specific: Avoid very broad or open-ended questions that are likely to have many answers or primarily illicit opinions. If necessary, break up your query into multiple more specific questions. These can be linked to one another, i.e. you can include a weblink to a previous question in the body of a new question when it is a follow-on issue.

More guidance:
https://earthscience.stackexchange.com/help/asking

Example post:
https://earthscience.stackexchange.com/questions/24081/cannot-initialize-mike-1d-failed-when-solving-for-a-steady-state-solution-wat/24084#24084

Stack Exchange Question & Answer platform

2023-12-04T10:34:30Z

Julia Glenday:

''Have you ever been stuck when trying to get a hydrological model to work, not able to find the solution in a manual or from colleagues, and struggling to contact an expert with time to assist? 
''Are you an advanced model user who wishes they could help others more, but don’t have much spare time for added meetings or troubleshooting via email? 
''Are you an instructor who spends a lot of time answering the same modelling questions from your students many times over?

The [https://stackexchange.com Stack Exchange] platform is a readily available resource that can easily be used as a support system for hydrological modelling. It is a well-known, free, question-and-answer (Q&A) website. Anyone can create a log-in and ask or answer a question, tagging it for specific themes. Questions and answers on the site are then easy to search for and find. For hydrological modelling questions, we advocate use of the [https://earthscience.stackexchange.com/ '''Earth Science Stack Exchange'''].

By using such a platform, we can:
* make support for hydrological modelling, across various modelling tools, more accessible and transparent online, and
* become more efficient in providing one another with support by documenting questions and answers on an easily searchable website, such that advanced users do not need to answer the same common questions multiple times over.

Researchers, students and practitioners are encouraged to add their model-related questions to the platform using clearly specified tags, and answer each other's questions, starting a critical mass of activity on the site. This will strengthen the modelling community in South Africa and can also facilitate engagement with overseas users of the same modelling tools.
The material below describes how Stack Exchange works and gives guidelines for use in this context.

'''Lecturers, instructors, advanced users:''' Consider transitioning from answering questions via email to answering them on Stack Exchange. Request that the person asking puts their question on the site and sends you the link it. You can also post common Q&A’s to the site in advance (you can answer your own question) and direct people to look there first before coming to you with questions.

'''Students, newer model users:''' Try asking your questions on Stack Exchange rather than via email. With time there will be more and more Q&As on the site so you can search existing posts for help first, before posting a new question. When you’ve posted a new question, you can send the link to a lecturer or advanced user who you think can answer it and ask them if they can answer via the site.

'''Everyone:''' If you’ve worked through a problem on your own, with a group, or with an instructor, do the community a favour and post it as a Q&A on Stack Exchange. One person can post the question and another can answer, or one can post both Q&A. This allows anyone in the world to find the Q&A, and you may even get suggestions of other even more efficient solutions.

''Below you'll find more background information on how Stack Exchange works and a step-by-step guide for getting started with using it. This information is also available as a PDF document you can download and share with your colleagues, students, or instructors:'' [[:File: Stack_Exchange_Guidelines_for_hydro_modelling_support.pdf ‎|'''''Download guide PDF here''''']]

== How does Stack Exchange work? ==

Stack Exchange is a network of question-and-answer (Q&A) websites each with a different focus topic, such as computer programming, mathematics, or earth science (see all sites: https://stackexchange.com/sites). The initial site, called Stack Overflow, is a Q&A site for computer programming created by Jeff Atwood and Joel Spolsky in 2008. The usefulness of this site generated demand for similar sites for other topics.
There is no site specifically for hydrological modelling at this time, but the Earth Science site (https://earthscience.stackexchange.com) hosts both hydrology and modelling questions. If and when there are enough users asking and answering hydrology and hydrological modelling questions, a more specific site(s) could be launched in the future.

Stack Exchange sites have features that allow them to be moderated by their user community:

* ''' Anyone can search for and view existing Q&A strings on the site - no log-in is required.'''

* '''Create an account/log-in to post:''' One needs to create an account and log in to the site to post a question or an answer or to add votes, edits, or comments. Profile names are shown alongside all posts for accountability.

* '''Tags:''' Tags are simple keywords or search terms which users assign to their questions to help people find them. If you are looking to find out if a question has been asked and answered already, a simple Google Search on the question will usually find related Stack Exchange Q&A posts. It is also possible to search within Stack Exchange sites using tags. This is one way to look for questions you may wish to answer (e.g., search unanswered questions with a specific tag, like ‘hydrology’). Only more advanced users (see below) can add new words to the tags list for a site. If a tag does not receive sufficient use, it will be removed from the list.

* '''Reputation points:''' Any logged-in user can post questions and answers, ‘accept’ an answer to their question, and propose edits to posts (to be reviewed by authors). Users also build up “reputation points”. Points allow a user to access more site functions, such as ‘upvoting’ posts, proposing new keywords for tagging, commenting, putting oneself up for election to be a moderator, etc. Points are gained by posting questions and answers, having your answer be ‘accepted’ by the user who asked the question, having your answer be upvoted, etc. More advanced use can result in ‘badges’ (bronze, silver, gold) that show up on the user’s profile and when they post. https://earthscience.stackexchange.com/help/whats-reputation

* '''Upvoting:''' Logged-in users with 15 or more reputation points can ‘upvote’ questions and answers that they find to be useful and appropriate. There may be many answers posted for a single question. When an answer has been formally ‘accepted’ by the user who asked the question, this answer will be shown at the top of the list. The asker can change which is the ‘accepted’ answer as new answers are posted. Other answers are listed in order of the number of votes they have received. Not all askers ‘accept’ an answer. In this case, the number of votes determines which is listed first. Upvotes may prompt the asker to review which answer they ‘accept’. Each user has a limited number of votes they can cast per day. https://earthscience.stackexchange.com/help/privileges/vote-up

* '''Moderation & disputes:''' Elected moderators are responsible for managing the site, through activities such as following up on flagged posts, locking and protecting posts, suspending users, and deleting the worst posts on the site. Stack Exchange aims for moderators to be minimally involved, respect users, and lead by example. Each Stack Exchange site has a "meta" section where users can ask questions about the site itself and also settle disputes in a separate forum to the Q&A strings.

For more information about how Stack Exchange and the Earth Science site work follow the links below:

https://earthscience.stackexchange.com/tour

https://earthscience.stackexchange.com/help

https://en.wikipedia.org/wiki/Stack_Exchange

== Step by step guide to using Stack Exchange for hydrological modelling support ==

=== Getting started - create an account ===

# Go to the Earth Sciences Stack Exchange site: https://earthscience.stackexchange.com/
# '''Create an account''' (display name, email, password) if you don’t already have one.
# Go through the site tour (should appear when you create your account): https://earthscience.stackexchange.com/tour
# '''Access & edit your profile''': Once your profile exists you can edit things like your display name, profile icon or image, and specify your email preferences. You can control if and how you want to be contacted by email by the site (e.g., can be notified if someone answers your question, posts a question with a ‘tag’ that you are following, etc). When you are logged in, you can open your profile by clicking on your profile image on the top bar at the right. Here you can also see a log of the questions you’ve asked, those you’ve answered, your reputation points, etc.

=== Asking questions ===

# '''Log-in''' to your profile on the Earth Sciences Stack Exchange site: https://earthscience.stackexchange.com/
# Before posting a question, do a '''search to see if the question has already been asked.''' If it has been asked and answered, and you find the posts helpful and you have 15+ reputation points, you can ‘upvote’ questions and answers using the arrows at the side of the posts.
# '''To post:''' Click on “Ask Question”
# Add a title, body text and tags for your question. '''Please tag with “hydrology” and “modelling”''', plus any other relevant tags of your choice. Tags must come from the list of tags for the Earth Sciences site. Users with 150 reputation points or more can propose new tags. Other relevant tags available include: hydrogeology, water, groundwater, water-vapour, water-table, watershed. Full tags list: https://earthscience.stackexchange.com/tags
# '''Review & post:''' After drafting your question you get to review it; see how it will appear on the site and proofread it one more time. When satisfied, hit “Post.”
# If you already know an expert or advanced model user who is likely to be able to answer your question, you may wish to contact them with a link to your question on Stack Exchange and encourage them to answer it on the site so that everyone can access it.
# '''Editing after posting:''' After you’ve posted a question, if you realise that you want to change the phrasing, add a detail, etc, perhaps prompted by the answers and comments coming in, you can edit your question.
# '''Review the answers, accept, vote:''' Once people have posted answers and you’ve tried some of them out, you can “accept” an answer that has worked for you. If you have 15+ reputation points you can also “upvote” other useful answers.

=== Answering questions ===

# '''Log-in''' to your profile on the Earth Sciences Stack Exchange site: https://earthscience.stackexchange.com/
# '''Find a question to answer:''' Someone may have contacted you to answer a question that they’ve asked on the site and sent a link. Otherwise, you can search using keywords of your choice in the normal search bar or use the panel on the left to find questions with one or more specified tags (e.g. “hydrology” and “modelling”), look for unanswered questions only, etc. Using “My tags” will find posts related to tags you have elected to follow and ones you have used when posting. You can add a new answer to a question that already have an answer posted if you have a different approach or a refinement to share that may be helpful. '''Answering your own question:''' A user can post an answer to their own question. There is no harm in doing this. The user will not receive points for this answer, or for it being upvoted.
# At the bottom of each question post you will find a box titled '''“Your Answer”''' where you can enter your answer and post it. This entry box will be located below any previously posted answers to the question. After posting, your answer can move higher in the list of answers if it gets 'upvoted.'

== Tips for asking a good question ==

Before you post a question, search the site to make sure your question hasn’t been answered already.

When you decide to write a question:
* Summarize the problem
* Provide details: When appropriate, describe what you’ve already tried in an effort to solve a problem on your own and what happened. This can include describing research you’ve done to try to find the answer (can include citations, links, etc) and why this was insufficient to resolve the issue.
* Be specific: Avoid very broad or open-ended questions that are likely to have many answers or primarily illicit opinions. If necessary, break up your query into multiple more specific questions. These can be linked to one another, i.e. you can include a weblink to a previous question in the body of a new question when it is a follow-on issue.

More guidance:
https://earthscience.stackexchange.com/help/asking

Example post:
https://earthscience.stackexchange.com/questions/24081/cannot-initialize-mike-1d-failed-when-solving-for-a-steady-state-solution-wat/24084#24084

Stack Exchange Question & Answer platform

2023-12-04T10:31:15Z

Julia Glenday:

''Have you ever been stuck when trying to get a hydrological model to work, not able to find the solution in a manual or from colleagues, and struggling to contact an expert with time to assist? 
''Are you an advanced model user who wishes they could help others more, but don’t have much spare time for added meetings or troubleshooting via email? 
''Are you an instructor who spends a lot of time answering the same modelling questions from your students many times over?

The [https://stackexchange.com Stack Exchange] platform is a readily available resource that can easily be used as a support system for hydrological modelling. It is a well-known, free, question-and-answer (Q&A) website. Anyone can create a log-in and ask or answer a question, tagging it for specific themes. Questions and answers on the site are then easy to search for and find. For hydrological modelling questions, we advocate use of the [https://earthscience.stackexchange.com/ '''Earth Science Stack Exchange'''].

By using such a platform, we can:
* make support for hydrological modelling, across various modelling tools, more accessible and transparent online, and
* become more efficient in providing one another with support by documenting questions and answers on an easily searchable website, such that advanced users do not need to answer the same common questions multiple times over.

Researchers, students and practitioners are encouraged to add their model-related questions to the platform using clearly specified tags, and answer each other's questions, starting a critical mass of activity on the site. This will strengthen the modelling community in South Africa and can also facilitate engagement with overseas users of the same modelling tools.
The material below describes how Stack Exchange works and gives guidelines for use in this context.

'''Lecturers, instructors, advanced users:''' Consider transitioning from answering questions via email to answering them on Stack Exchange. Request that the person asking puts their question on the site and sends you the link it. You can also post common Q&A’s to the site in advance (you can answer your own question) and direct people to look there first before coming to you with questions.

'''Students, newer model users:''' Try asking your questions on Stack Exchange rather than via email. With time there will be more and more Q&As on the site so you can search existing posts for help first, before posting a new question. When you’ve posted a new question, you can send the link to a lecturer or advanced user who you think can answer it and ask them if they can answer via the site.

'''Everyone:''' If you’ve worked through a problem on your own, with a group, or with an instructor, do the community a favour and post it as a Q&A on Stack Exchange. One person can post the question and another can answer, or one can post both Q&A. This allows anyone in the world to find the Q&A, and you may even get suggestions of other even more efficient solutions.

Below you'll find more background information on how Stack Exchange works and a step-by-step guide for getting started with using it.
This information is also available as a PDF document you can download and share with your colleagues, students, or instructors: [[:File: Stack_Exchange_Guidelines_for_hydro_modelling_support.pdf ‎|'''Download guide PDF here''']]

== How does Stack Exchange work? ==

Stack Exchange is a network of question-and-answer (Q&A) websites each with a different focus topic, such as computer programming, mathematics, or earth science (see all sites: https://stackexchange.com/sites). The initial site, called Stack Overflow, is a Q&A site for computer programming created by Jeff Atwood and Joel Spolsky in 2008. The usefulness of this site generated demand for similar sites for other topics.
There is no site specifically for hydrological modelling at this time, but the Earth Science site (https://earthscience.stackexchange.com) hosts both hydrology and modelling questions. If and when there are enough users asking and answering hydrology and hydrological modelling questions, a more specific site(s) could be launched in the future.

Stack Exchange sites have features that allow them to be moderated by their user community:

* ''' Anyone can search for and view existing Q&A strings on the site - no log-in is required.'''

* '''Create an account/log-in to post:''' One needs to create an account and log in to the site to post a question or an answer or to add votes, edits, or comments. Profile names are shown alongside all posts for accountability.

* '''Tags:''' Tags are simple keywords or search terms which users assign to their questions to help people find them. If you are looking to find out if a question has been asked and answered already, a simple Google Search on the question will usually find related Stack Exchange Q&A posts. It is also possible to search within Stack Exchange sites using tags. This is one way to look for questions you may wish to answer (e.g., search unanswered questions with a specific tag, like ‘hydrology’). Only more advanced users (see below) can add new words to the tags list for a site. If a tag does not receive sufficient use, it will be removed from the list.

* '''Reputation points:''' Any logged-in user can post questions and answers, ‘accept’ an answer to their question, and propose edits to posts (to be reviewed by authors). Users also build up “reputation points”. Points allow a user to access more site functions, such as ‘upvoting’ posts, proposing new keywords for tagging, commenting, putting oneself up for election to be a moderator, etc. Points are gained by posting questions and answers, having your answer be ‘accepted’ by the user who asked the question, having your answer be upvoted, etc. More advanced use can result in ‘badges’ (bronze, silver, gold) that show up on the user’s profile and when they post. https://earthscience.stackexchange.com/help/whats-reputation

* '''Upvoting:''' Logged-in users with 15 or more reputation points can ‘upvote’ questions and answers that they find to be useful and appropriate. There may be many answers posted for a single question. When an answer has been formally ‘accepted’ by the user who asked the question, this answer will be shown at the top of the list. The asker can change which is the ‘accepted’ answer as new answers are posted. Other answers are listed in order of the number of votes they have received. Not all askers ‘accept’ an answer. In this case, the number of votes determines which is listed first. Upvotes may prompt the asker to review which answer they ‘accept’. Each user has a limited number of votes they can cast per day. https://earthscience.stackexchange.com/help/privileges/vote-up

* '''Moderation & disputes:''' Elected moderators are responsible for managing the site, through activities such as following up on flagged posts, locking and protecting posts, suspending users, and deleting the worst posts on the site. Stack Exchange aims for moderators to be minimally involved, respect users, and lead by example. Each Stack Exchange site has a "meta" section where users can ask questions about the site itself and also settle disputes in a separate forum to the Q&A strings.

For more information about how Stack Exchange and the Earth Science site work follow the links below:

https://earthscience.stackexchange.com/tour

https://earthscience.stackexchange.com/help

https://en.wikipedia.org/wiki/Stack_Exchange

== Step by step guide to using Stack Exchange for hydrological modelling support ==

=== Getting started - create an account ===

# Go to the Earth Sciences Stack Exchange site: https://earthscience.stackexchange.com/
# '''Create an account''' (display name, email, password) if you don’t already have one.
# Go through the site tour (should appear when you create your account): https://earthscience.stackexchange.com/tour
# '''Access & edit your profile''': Once your profile exists you can edit things like your display name, profile icon or image, and specify your email preferences. You can control if and how you want to be contacted by email by the site (e.g., can be notified if someone answers your question, posts a question with a ‘tag’ that you are following, etc). When you are logged in, you can open your profile by clicking on your profile image on the top bar at the right. Here you can also see a log of the questions you’ve asked, those you’ve answered, your reputation points, etc.

=== Asking questions ===

# '''Log-in''' to your profile on the Earth Sciences Stack Exchange site: https://earthscience.stackexchange.com/
# Before posting a question, do a '''search to see if the question has already been asked.''' If it has been asked and answered, and you find the posts helpful and you have 15+ reputation points, you can ‘upvote’ questions and answers using the arrows at the side of the posts.
# '''To post:''' Click on “Ask Question”
# Add a title, body text and tags for your question. '''Please tag with “hydrology” and “modelling”''', plus any other relevant tags of your choice. Tags must come from the list of tags for the Earth Sciences site. Users with 150 reputation points or more can propose new tags. Other relevant tags available include: hydrogeology, water, groundwater, water-vapour, water-table, watershed. Full tags list: https://earthscience.stackexchange.com/tags
# '''Review & post:''' After drafting your question you get to review it; see how it will appear on the site and proofread it one more time. When satisfied, hit “Post.”
# If you already know an expert or advanced model user who is likely to be able to answer your question, you may wish to contact them with a link to your question on Stack Exchange and encourage them to answer it on the site so that everyone can access it.
# '''Editing after posting:''' After you’ve posted a question, if you realise that you want to change the phrasing, add a detail, etc, perhaps prompted by the answers and comments coming in, you can edit your question.
# '''Review the answers, accept, vote:''' Once people have posted answers and you’ve tried some of them out, you can “accept” an answer that has worked for you. If you have 15+ reputation points you can also “upvote” other useful answers.

=== Answering questions ===

# '''Log-in''' to your profile on the Earth Sciences Stack Exchange site: https://earthscience.stackexchange.com/
# '''Find a question to answer:''' Someone may have contacted you to answer a question that they’ve asked on the site and sent a link. Otherwise, you can search using keywords of your choice in the normal search bar or use the panel on the left to find questions with one or more specified tags (e.g. “hydrology” and “modelling”), look for unanswered questions only, etc. Using “My tags” will find posts related to tags you have elected to follow and ones you have used when posting. You can add a new answer to a question that already have an answer posted if you have a different approach or a refinement to share that may be helpful. '''Answering your own question:''' A user can post an answer to their own question. There is no harm in doing this. The user will not receive points for this answer, or for it being upvoted.
# At the bottom of each question post you will find a box titled '''“Your Answer”''' where you can enter your answer and post it. This entry box will be located below any previously posted answers to the question. After posting, your answer can move higher in the list of answers if it gets 'upvoted.'

== Tips for asking a good question ==

Before you post a question, search the site to make sure your question hasn’t been answered already.

When you decide to write a question:
* Summarize the problem
* Provide details: When appropriate, describe what you’ve already tried in an effort to solve a problem on your own and what happened. This can include describing research you’ve done to try to find the answer (can include citations, links, etc) and why this was insufficient to resolve the issue.
* Be specific: Avoid very broad or open-ended questions that are likely to have many answers or primarily illicit opinions. If necessary, break up your query into multiple more specific questions. These can be linked to one another, i.e. you can include a weblink to a previous question in the body of a new question when it is a follow-on issue.

More guidance:
https://earthscience.stackexchange.com/help/asking

Example post:
https://earthscience.stackexchange.com/questions/24081/cannot-initialize-mike-1d-failed-when-solving-for-a-steady-state-solution-wat/24084#24084

File:Stack Exchange Guidelines for hydro modelling support.pdf

2023-12-04T10:22:49Z

Julia Glenday: Guidelines for using Stack Exchange Earth Sciences question & answer online platform to find and to provide support for hydrological modelling (e.g., how to log-in, ask and answer questions, look for existing Q&A strings, use appropriate tags, etc.)

== Summary ==
Guidelines for using Stack Exchange Earth Sciences question & answer online platform to find and to provide support for hydrological modelling (e.g., how to log-in, ask and answer questions, look for existing Q&A strings, use appropriate tags, etc.)

Groundwater pumping

2023-12-04T10:07:05Z

Julia Glenday: Created page with "''' PAGE IN PROGRESS - MORE COMING SOON! '''"

''' PAGE IN PROGRESS - MORE COMING SOON! '''

Small farm dams

2023-12-04T10:06:51Z

Julia Glenday: Created page with "''' PAGE IN PROGRESS - MORE COMING SOON! '''"

''' PAGE IN PROGRESS - MORE COMING SOON! '''

Riparian zones

2023-12-04T10:06:36Z

Julia Glenday: Created page with "''' PAGE IN PROGRESS - MORE COMING SOON! '''"

''' PAGE IN PROGRESS - MORE COMING SOON! '''

Invasive alien plants (IAPs) & afforestation

2023-12-04T10:06:20Z

Julia Glenday: Created page with "''' PAGE IN PROGRESS - MORE COMING SOON! '''"

''' PAGE IN PROGRESS - MORE COMING SOON! '''

Applying tools in specific use cases

2023-12-04T10:06:05Z

Julia Glenday:

''' PAGE IN PROGRESS - MORE COMING SOON! '''

Comparisons of how the different modelling tools included in this wiki represent some particular catchment features that one may want to explicitly include in a model are summarised below and covered in more detail in linked content pages. These features, such as tree plantations or small farm dams, may exert a large influence on the hydrology of the catchment you are trying to model. Changes in these features may also be the express reason why you are modelling the catchment, i.e., to estimate the potential impacts of clearing invasive alien plants, restoring wetlands, or expanding irrigation in a particular area.

The reason for modelling a catchment should be one of the main considerations involved in selecting a modelling tool for a particular application. It likely won't be the only consideration, as practical issues are also important (see [[Modelling process overview|modelling process overview here]]), but it is a key one. It is worth being familiar with the various capabilities, limitations, and differences in how these particular elements are represented across models when they are main features of your study catchment.

== Invasive alien plants (IAPs) & afforestation ==
[[Invasive alien plants (IAPs) & afforestation]]

== Riparian zones ==
[[Riparian zones]]

== Wetlands ==
The definition of wetland representation and an outline of the fundamental wetland descriptions which differentiate wetlands in modelling tools is presented in the [[wetlands]] page.

== Irrigation ==
This section provides a summary of how the various tools represent irrigation from different sources. A detailed description of irrigation representation is found [[Irrigation|here.]]

==== Irrigation from groundwater ====
● Pitman tools & ACRU: Do not include irrigation from groundwater. ACRU does not include any groundwater withdrawal. Work-arounds in the Pitman tools do not allow for dynamic curtailment of irrigation when groundwater supplies are low.

==== Irrigation from reservoirs ====
● MIKE-SHE appears not to include irrigation from storage reservoirs, only runoff river and groundwater

==== Irrigation from multiple sources ====
● Pitman tools, ACRU, & SWAT only allow an irrigated area to be irrigated from one source, while MIKE-SHE allows multiple sources to be drawn upon in sequence to meet demands.

== Small farm dams ==
[[Small farm dams]]

== Groundwater pumping ==
[[Groundwater pumping]]

Water balance outputs across tools

2023-12-04T09:50:06Z

Julia Glenday:

Modelling tools differ in the hydrological processes, or water balance elements (fluxes and storages), that they calculate individually, save, and allow users to export for further analyses. The table below covers what each software tool outputs, meaning what can be saved as a timeseries of flow rates, fluxes, or storage volumes or depths, and for what ''spatial scale'' or modelled units these can be output (e.g. output for each grid cell, HRU, subcatchment, or catchment total). Output file formats are covered [[Modelling tool user interfaces#Formats of input and output data|here]].

The spatial scales at which the software can output values gives an indication of how much external calculation work a user may need to do in order to find out about a flux or store of particular interest. For example, we often wish to know the ET water use of a particular vegetation type, likely to compare with another type. ACRU and SWAT will output AET components for individual HRUs, however if there are multiple HRUs of the same land cover type within the model type, these tools will not compile an area-weighted average for the cover type across the whole modelled area. The user would need to do that manually outside the tool using the individual HRU outputs. MIKE-SHE can do this compilation within the software as the user can specify a polygon that covers the full area of a cover class and the tool will compile fluxes for that polygon.

'''Note:''' The table differentiates between the case in which a ''tool does not output'' its calculation of a certain flux or storage (Output = "no") and the case in which the ''tool does not explicitly model'' the listed process ("not modelled"), meaning it's not part of the model's calculations. In the case when a tool ''does model'' a process, but ''does not output'' the results of this calculation, the user could potentially consult the tools' user guide and attempt to calculate the process themselves using the algorithm that is applied in the software and other components that can be output. In cases where a calculation would be relatively simple, and based only on other outputs covered in the table, the calculation approach has been given in the table.
For cases where the tool does output a flux but uses a different name for it that has been used in the table row heading, this has been noted in brackets below. For more terminology comparison across tools, see further coverage [[Terminology#Hydrological process and parameter terms across tools|here]]. 
Some of the fluxes listed in the table are net totals of component fluxes which are also listed in the table (e.g. total AET or total evaporation & transpiration = canopy interception evaporation + AET from soil + AET from GW + evaporation off water bodies, where applicable). Some tools model and output each separately and may or may not output each individually. Some provide outputs of the total and the components, some just the components and the user would need to sum them if the total was of interest. Some calculate a total of some or all in a single step and output the total.

{| class="wikitable"
! scope="col" style="width:15em" colspan="2" rowspan="2" |Flux or storage
! colspan="6" | '''''Tool output and/or calculation approach'''''
|-
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman (Sami GW)
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman (Hughes GW)
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed,more conceptual]]
! scope="col" style="background: #CEDAF2; width:8em" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed,more physical]]

|-
| rowspan="2"; style="vertical-align: top; width:10em "|'''AET total'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top" |<center>no *</center>
'''''calculate:'''''
''precip – runoff 
''– Δ soil storage 
''– Δ GW storage 
''(works for long-term average, not monthly due to recharge lag)
| style="background: #FFF7F5; vertical-align: top" | <center>no *</center>
'''''calculate:''''' 
''ET output (includes canopy interception)
''+ AET from GW (external calculation)''
| style="background: #F5FFF5; vertical-align: top" | <center>no *</center>
'''''calculate:''''' 
''canopy evap. 
''+ AET from soil''
| style="background: #FFFFF5; vertical-align: top" | <center>no *</center>
'''''calculate:'''''
''AET from soil 
''+ AET from GW''
| style="background: #F5FCFF; vertical-align: top; text-align:center;" | '''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" | '''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | ''(runoff module)''
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | ''(subcatchment)''
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | ''(HRU)''
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | ''(HRU)''
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Canopy interception evaporation'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" | no<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style=" vertical-align: center; text-align:top;" | <center>not modelled <big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| vertical-align: top; text-align:center;” | 
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''AET from soil'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" | no<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''AET from GW'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" | no<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" | no<big></big>
| style="vertical-align: top; text-align:center;" | not modelled<big></big> 
''(exception: [[Process representation across tools#Evapotranspiration (ET) from groundwater (GW)|riparian HRU approximation]]) ''
| style="background: #FFFFF5; vertical-align: top; text-align:center;" | '''YES'''<big></big>(‘Revap’)
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | 
| style="vertical-align: top; text-align:center;" |
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment aquifer, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|-
| rowspan="2"; style="vertical-align: top"|'''Evaporation from surface water body'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” |
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | water body
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | water body
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | water body (includes river reaches)
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | water body (includes river reaches), surface ponding: grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | water body (includes river reaches), surface ponding: grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Runoff (RO) total'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module, route (any scale)
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | river cross section
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | river cross section
|-
| rowspan="2"; style="vertical-align: top"|'''Surface runoff'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top;" | <center>no *</center>
'''''calculate:''''' 
''RO total – interflow – aquifer RO''
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top;" | <center>no *</center>
'''''calculate:''''' 
'' “Quickflow” – “DelayedStormflow” ''
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Interflow'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(‘soil moisture runoff’)
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(‘DelayedStormflow’)
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(‘Lateral Q’)
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>(saturated zone, upper layer)
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment interflow reservoir
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Aquifer to channel'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment aquifer, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|-
| rowspan="2"; style="vertical-align: top"|'''Channel to aquifer'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style= "vertical-align: top; text-align:center;" | not modelled
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |no
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | river module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: "vertical-align: top; text-align:center;” |
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | ''channel to "bank store", not output, need to back-calculate for reach
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | river reach
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | river reach; grid cell, polygon, catchment (aquifer layer)
|-
| rowspan="2"; style="vertical-align: top"|'''Aquifer GW flow, into or out of a model unit, remaining as GW'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |no<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="vertical-align: top; text-align:center;" |not modelled<big></big>
| style="background: #FFFFF5; vertical-align: top;" |<center>no *</center><big></big>
''GW can ‘leave’ catchment by recharging an inactive deep aquifer''
| style="background: #F5FCFF; vertical-align: top;" |<center>no *</center><big></big>
''GW can ‘leave’ catchment by recharging an inactive deep aquifer or ‘dead storage’ ''
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | 
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="vertical-align: top; text-align:center;” | 
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | (subcatchment)
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | (subcatchment)
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|-
| rowspan="2"; style="vertical-align: top"|'''Water body storage'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” |
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | water body
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | water body
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | water body
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | water body, surface ponding: grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | water body, surface ponding: grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Soil profile storage'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | soil layer in HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Aquifer storage'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |no<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment aquifer, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|-
| rowspan="2"; style="vertical-align: top"|'''Percolation out of soil storage'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>(‘total recharge’ - lagged to aquifer, excess becomes interflow)
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(same as aquifer recharge below)
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(same as aquifer recharge below)
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(lagged to aquifer)
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>(goes to 'interflow store')
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>(same as aquifer recharge below)
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Aquifer recharge'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>(‘aquifer recharge’)
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(B-horizon soil ‘SaturatedFlow’ + ‘UnsaturatedFlow’)
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment aquifer, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|}

Modelling tool user interfaces

2023-12-04T09:44:52Z

Julia Glenday: /* User impressions of 'ease-of-use' (modeller survey) */

The tables below compare some main features of the user interfaces of the selected modelling tools that relate to their ease of use. These include approximate comparisons of typical model run times and the computing power needed to run them, as well as how easy it is to export and view various model outputs and test different parameter value options for sensitivity analyses and/or calibration. (More specifics about what outputs each tool can produce is covered [[Water balance outputs across tools|here]].)

What can be achieved in the time available for a modelling project is influenced by the combination of how long it takes to set up a model (including preparing input data in the needed format, setting up the structure, entering the parameter values), how long it takes for the model to run, how long it takes to access model outputs of interest, and how long it takes to test and refine the model. Some modelling tools may run very quickly, but take a relatively long time to set up and don't have an efficient way to change and test multiple parameter value options, which makes calibration a time consuming, laborious, manual process. Other tools may take long to run, but can be set up to do a number of parameter testing runs and even scenario runs at once, allowing the modeller to attend to other work in the meantime (however they may have to do so on another computer if the model requires a lot of computing power!).

Ease and efficiency of software use is also influenced by the documentation and support available for the tool. How accessible and user-friendly these are can determine whether or not users getting stuck trouble-shooting for long periods of time or inadvertently modelling things incorrectly. User impressions of the ease of use of tool interfaces, documentation, and support are provided [[#User impressions of 'ease-of-use' (modeller survey)|below]]. Links to online documentation and support resources for these tools are provided [[Modelling tool documentation|here]]

__TOC__



== Interface comparison ==

{| class="wikitable"
! scope="col" style="width:15em" | Interface characteristic <big></big>
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
|-
| style="vertical-align: vertical-align: center;" |Graphical user interface ''(vs code prompt)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Catchment map display (visualise linkages)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model run times'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Estimated model run time for a 30 year run, ~300km^2 catchment ''(Note: will depend on model set-up complexity & computing power!)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |tens of minutes
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |hours
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Computing resources needed'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Comparative rating of computing power needed to achieve workable run times.
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |light
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |light
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |light
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |medium
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |intensive (need good GPU)
|-
| colspan="6" style="background: #FFFFFF; vertical-align: vertical-align: center;" |'''Model set-up ease & efficiency'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Automated creation of model units & connections from map inputs ''(vs fully manual creation)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Input parameter values and change values for batches of models units ''(e.g., all HRUs of a cover type)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |In-built database of suggested parameter values ''(e.g., for common vegetation types, soil types, etc.)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |no
|-
| style="vertical-align: vertical-align: center;" |User can build own parameter databases for use across multiple models
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model set-up transparency''' (i.e., is it very obvious what the model is doing/assuming?) <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Interface makes the user interact with every component & parameter entry option during model set-up ''(vs having default parameter values pre-entered & not forcing user to view them)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |no
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Tool checks connection errors
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Batch runs & calibration tools''' <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Facility for batch runs, parameter sensitivity analyses, uncertainty analyses & auto-calibration
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Accessing model output''' <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for streamflow
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for water balance fluxes and stores
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |All water balance components that are calculated by the model can be exported
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Batch export of water balance fluxes for model's basic spatial units
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Automated extraction of water balance fluxes for different spatial scales ''(e.g., by cover class area, by subcatchment, full catchment)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|}


== Formats of input and output data ==

The table below gives some basic information about the file formats used for model inputs and outputs across the different modelling tools to give a general impression of what is required to work with them. This is a very rough overview and one has to work with user manuals, tutorials, and/or pre-exist demonstration models and data to understand the various formatting requirements and file types used across the inputs and outputs of a specific software tool. For large or complex model set-ups that will have many different inputs (e.g., different input rainfall timeseries for several different points across the modelled area), it is highly recommended to use coding tools like R or Python to prepare the input files as it will be time-consuming to get many files into the same specific formatting required by the modelling software and most do not have in-built conversion tools.

{| class="wikitable"
! scope="col" style="width:10%" |'''Data type''' <big></big>
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE
|-
| style="vertical-align: top;" |'''Timeseries data'''
| style="background: #FFF5FA; vertical-align: top; text-align: left;" |'''Specially formatted text files (special file extensions)'''
Monthly data with years as rows and a column for each month in a water year starting in Oct, and for some types an annual sum in an additional column. Files can be read and generated by text editors (like Notepad) outside of WRSM, even though the files do not have typical text file extensions (e.g. ".txt"). WRSM input and output file extensions show the type of data (e.g., .RAN file is a rainfall timeseries file). Data can be brought into Excel for analyses, but it is difficult to create the input file formatting within Excel. A text editor or a general coding interface like an R or Python editor can be used to achieve the needed input data timeseries.
| style="background: #FFF7F5; vertical-align: top; text-align: left;" |'''Specially formatted text files (.txt)'''
 Some flexibility on the formatting for inputs as one can specify the row/column format and date formatting in the files in the tools' input interface. Inputs can be prepared in Excel and outputs easily opened there as well.
| style="background: #F5FFF5; vertical-align: top; text-align: left;" |'''Specially formatted ASCII text files (.txt) & .DBF files'''
 Input is daily data in long-format (one date per row) in a composite file containing climate variable and observed flow inputs in specified column orders and number formats. Difficult to prepare simply in Excel, and labour intensive to prepare in a text editor (e.g, Notepad), but reasonable to prepare in a general coding programme like R or Python. Outputs are .dbf format text files which open easily in Excel.
| style="background: #FFFFF5; vertical-align: top; text-align: left;" |'''Specially formatted text files (.txt) & Access database files '''
 Daily data in long-format (one date per row) text files. Reasonable to prepare and easy to open in Excel. Outputs can also be produced in an Access database.
| style="background: #F5FCFF; vertical-align: top; text-align: left;" |'''Software-specific .dfs0 file format'''
 Dfs0 files for input must be generated within MIKE software. Data in long-format (each row is a timestep) prepared in Excel can be copy-pasted into a blank dfs0 file with the correct number of rows and data from dfs0 files can be copy-pasted into Excel. There are also batch conversion tools in MIKE that can be used to convert specifically formatted text files into dfs0 files and to convert dfs0 files into text files.
|-
| style="vertical-align: top;" |'''Spatial data'''
| style="background: #FFF5FA; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of modules: what areas will have their own modules (e.g. subcatchment delineation; special cover types to represent separately, like plantations, irrigated areas, wetlands; river reaches and dams), determine sizes and other characteristics of the modules, and how they are linked to one another.''
| style="background: #FFF7F5; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments: subcatchment delineation plus special features to represent specifically like dams, plantations, irrigated areas, wetlands), determine the sizes and other characteristics of subcatchments and special areas, and how subcatchments are linked to one another.''
| style="background: #F5FFF5; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments composed of HRUs, river reaches, & dams: subcatchment delineation, what areas will have their own HRUs (land cover types to represent individually), determine the sizes and other characteristics of the HRUs, and how units linked to one another.''
| style="background: #FFFFF5; vertical-align: top; text-align:left;" |'''Standard GIS shapefile and grid/raster files (geotif, grid) used.'''
 DEM input must be a raster. Land cover and soil type data can be input as shapefiles or rasters (see user manuals for formatting/attribute requirements). Tool-delineated subcatchments, river lines, HRUs are output as shapefiles. Hydrological predictions are not output in a spatial format. The data can be linked back to spatial units based on ID numbers manually by the user for spatial displays. (SWAT+ has developed tools for this internally...)
| style="background: #F5FCFF; vertical-align: top; text-align:left;" |'''Software-specific .dfs2 and .dfs3 file formats used in general. A few inputs allow standard shapefiles.'''
 dfs2 files are 2D gridded data. Standard GIS grids can be saved in an ASCI format in GIS software and then a MIKE tool applied to convert to dfs2. Subcatchments and landcover can be input as shapefiles. Many hydrological predictions can be output as spatial data as .dfs3 files, 3 dimensional data "cubes": a 2D grid of values (e.g. transpiration, surface water depth, soil moisture, groundwater depth) for each timestep, all in one file. These can be stepped-through or played as video in the interface. Timeseries for point locations or specified areas can be extracted. .dfs2 files can be converted to ASCI files to open in GIS software using an in-built tool.
|}


== User impressions of 'ease-of-use' (modeller survey) ==
A brief survey for hydrological modellers was distributed via the South African Hydrology Society (SAHS) as part of the [[Model inter-comparison study|model intercomparison project (2019-2021)]]. Participants were asked to rank the ease-of-use of the software user interface, it's documentation, and available support for any modelling tools they were familiar with on a scale of 1-5 in which: '''1=poor, 3=satisfactory, 5= excellent'''
There was a ''very'' wide range of different scores assigned for each tool across the respondents, with some assigning a poor score while others assign and excellent score to the same tool, showing that different people experience the tools differently! 
Both the average and the range of scores assigned are presented below.
(Links to online documentation and support resources for these tools are provided [[Modelling tool documentation|here]])

''It should be noted that for the local tools (WRSM, SPATSIM, ACRU), users were generally trained in its use by those developing the tool or those closely involved with it and are often based at institutions with experts in that tool. Support for the local tools usually takes the form of personal interaction. For the international tools (SWAT, MIKE-SHE), some may have taught themselves to use the tool with online resources and/or been trained by an expert based elsewhere. As a result, there likely is more direct engagement with, and reliance on, the written documentation and support provided through global online help forums and emails to more distant expert users when working with these tools. ''

{| class="wikitable"
! scope="col" style="width:15em" colspan="2"| Aspect of tool <big></big>
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
|-
| style="vertical-align: vertical-align: center;" colspan="2"|'''''Number of users answering survey'''''<big></big>
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''13''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''14''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''19''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''9''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |''8''
|-
| rowspan="2"; style="vertical-align: top; width:10em "|'''Interface'''<big></big> 1-poor to 5-excellent
| style="vertical-align: vertical-align: center;" |''Average score'' <big></big>
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''3.8
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''3.4
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''3.4
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''3.9
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''3.0
|-
| style="vertical-align: vertical-align: center;" |''Range of scores''<big></big>
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |2 - 5
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |2 - 5
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |1 - 5
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |3 - 5
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |1 - 5
|-
| rowspan="2"; style="vertical-align: top; width:10em "|'''Documentation'''<big></big> 1-poor to 5-excellent
| style="vertical-align: vertical-align: center;" |''Average score'' <big></big>
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''3.7
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''3.6
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''3.6
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''3.6
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''2.3
|-
| style="vertical-align: vertical-align: center;" |''Range of scores''<big></big>
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |2 - 5
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |2 - 5
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |1 - 5
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |3 - 5
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |1 - 5
|-
| rowspan="2"; style="vertical-align: top; width:10em "|'''Support'''<big></big> 1-poor to 5-excellent
| style="vertical-align: vertical-align: center;" |''Average score'' <big></big>
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''3.7
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''3.7
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''3.9
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''3.8
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''2.4
|-
| style="vertical-align: vertical-align: center;" |''Range of scores''<big></big>
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |1 - 5
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |2 - 5
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |1 - 5
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |2 - 5
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |1 - 5
|}

Modelling tool user interfaces

2023-12-04T09:14:09Z

Julia Glenday: /* Formats of input and output data */

The tables below compare some main features of the user interfaces of the selected modelling tools that relate to their ease of use. These include approximate comparisons of typical model run times and the computing power needed to run them, as well as how easy it is to export and view various model outputs and test different parameter value options for sensitivity analyses and/or calibration. (More specifics about what outputs each tool can produce is covered [[Water balance outputs across tools|here]].)

What can be achieved in the time available for a modelling project is influenced by the combination of how long it takes to set up a model (including preparing input data in the needed format, setting up the structure, entering the parameter values), how long it takes for the model to run, how long it takes to access model outputs of interest, and how long it takes to test and refine the model. Some modelling tools may run very quickly, but take a relatively long time to set up and don't have an efficient way to change and test multiple parameter value options, which makes calibration a time consuming, laborious, manual process. Other tools may take long to run, but can be set up to do a number of parameter testing runs and even scenario runs at once, allowing the modeller to attend to other work in the meantime (however they may have to do so on another computer if the model requires a lot of computing power!).

Ease and efficiency of software use is also influenced by the documentation and support available for the tool. How accessible and user-friendly these are can determine whether or not users getting stuck trouble-shooting for long periods of time or inadvertently modelling things incorrectly. User impressions of the ease of use of tool interfaces, documentation, and support are provided [[#User impressions of 'ease-of-use' (modeller survey)|below]]. Links to online documentation and support resources for these tools are provided [[Modelling tool documentation|here]]

__TOC__



== Interface comparison ==

{| class="wikitable"
! scope="col" style="width:15em" | Interface characteristic <big></big>
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
|-
| style="vertical-align: vertical-align: center;" |Graphical user interface ''(vs code prompt)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Catchment map display (visualise linkages)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model run times'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Estimated model run time for a 30 year run, ~300km^2 catchment ''(Note: will depend on model set-up complexity & computing power!)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |tens of minutes
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |hours
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Computing resources needed'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Comparative rating of computing power needed to achieve workable run times.
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |light
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |light
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |light
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |medium
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |intensive (need good GPU)
|-
| colspan="6" style="background: #FFFFFF; vertical-align: vertical-align: center;" |'''Model set-up ease & efficiency'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Automated creation of model units & connections from map inputs ''(vs fully manual creation)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Input parameter values and change values for batches of models units ''(e.g., all HRUs of a cover type)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |In-built database of suggested parameter values ''(e.g., for common vegetation types, soil types, etc.)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |no
|-
| style="vertical-align: vertical-align: center;" |User can build own parameter databases for use across multiple models
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model set-up transparency''' (i.e., is it very obvious what the model is doing/assuming?) <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Interface makes the user interact with every component & parameter entry option during model set-up ''(vs having default parameter values pre-entered & not forcing user to view them)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |no
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Tool checks connection errors
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Batch runs & calibration tools''' <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Facility for batch runs, parameter sensitivity analyses, uncertainty analyses & auto-calibration
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Accessing model output''' <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for streamflow
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for water balance fluxes and stores
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |All water balance components that are calculated by the model can be exported
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Batch export of water balance fluxes for model's basic spatial units
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Automated extraction of water balance fluxes for different spatial scales ''(e.g., by cover class area, by subcatchment, full catchment)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|}


== Formats of input and output data ==

The table below gives some basic information about the file formats used for model inputs and outputs across the different modelling tools to give a general impression of what is required to work with them. This is a very rough overview and one has to work with user manuals, tutorials, and/or pre-exist demonstration models and data to understand the various formatting requirements and file types used across the inputs and outputs of a specific software tool. For large or complex model set-ups that will have many different inputs (e.g., different input rainfall timeseries for several different points across the modelled area), it is highly recommended to use coding tools like R or Python to prepare the input files as it will be time-consuming to get many files into the same specific formatting required by the modelling software and most do not have in-built conversion tools.

{| class="wikitable"
! scope="col" style="width:10%" |'''Data type''' <big></big>
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE
|-
| style="vertical-align: top;" |'''Timeseries data'''
| style="background: #FFF5FA; vertical-align: top; text-align: left;" |'''Specially formatted text files (special file extensions)'''
Monthly data with years as rows and a column for each month in a water year starting in Oct, and for some types an annual sum in an additional column. Files can be read and generated by text editors (like Notepad) outside of WRSM, even though the files do not have typical text file extensions (e.g. ".txt"). WRSM input and output file extensions show the type of data (e.g., .RAN file is a rainfall timeseries file). Data can be brought into Excel for analyses, but it is difficult to create the input file formatting within Excel. A text editor or a general coding interface like an R or Python editor can be used to achieve the needed input data timeseries.
| style="background: #FFF7F5; vertical-align: top; text-align: left;" |'''Specially formatted text files (.txt)'''
 Some flexibility on the formatting for inputs as one can specify the row/column format and date formatting in the files in the tools' input interface. Inputs can be prepared in Excel and outputs easily opened there as well.
| style="background: #F5FFF5; vertical-align: top; text-align: left;" |'''Specially formatted ASCII text files (.txt) & .DBF files'''
 Input is daily data in long-format (one date per row) in a composite file containing climate variable and observed flow inputs in specified column orders and number formats. Difficult to prepare simply in Excel, and labour intensive to prepare in a text editor (e.g, Notepad), but reasonable to prepare in a general coding programme like R or Python. Outputs are .dbf format text files which open easily in Excel.
| style="background: #FFFFF5; vertical-align: top; text-align: left;" |'''Specially formatted text files (.txt) & Access database files '''
 Daily data in long-format (one date per row) text files. Reasonable to prepare and easy to open in Excel. Outputs can also be produced in an Access database.
| style="background: #F5FCFF; vertical-align: top; text-align: left;" |'''Software-specific .dfs0 file format'''
 Dfs0 files for input must be generated within MIKE software. Data in long-format (each row is a timestep) prepared in Excel can be copy-pasted into a blank dfs0 file with the correct number of rows and data from dfs0 files can be copy-pasted into Excel. There are also batch conversion tools in MIKE that can be used to convert specifically formatted text files into dfs0 files and to convert dfs0 files into text files.
|-
| style="vertical-align: top;" |'''Spatial data'''
| style="background: #FFF5FA; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of modules: what areas will have their own modules (e.g. subcatchment delineation; special cover types to represent separately, like plantations, irrigated areas, wetlands; river reaches and dams), determine sizes and other characteristics of the modules, and how they are linked to one another.''
| style="background: #FFF7F5; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments: subcatchment delineation plus special features to represent specifically like dams, plantations, irrigated areas, wetlands), determine the sizes and other characteristics of subcatchments and special areas, and how subcatchments are linked to one another.''
| style="background: #F5FFF5; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments composed of HRUs, river reaches, & dams: subcatchment delineation, what areas will have their own HRUs (land cover types to represent individually), determine the sizes and other characteristics of the HRUs, and how units linked to one another.''
| style="background: #FFFFF5; vertical-align: top; text-align:left;" |'''Standard GIS shapefile and grid/raster files (geotif, grid) used.'''
 DEM input must be a raster. Land cover and soil type data can be input as shapefiles or rasters (see user manuals for formatting/attribute requirements). Tool-delineated subcatchments, river lines, HRUs are output as shapefiles. Hydrological predictions are not output in a spatial format. The data can be linked back to spatial units based on ID numbers manually by the user for spatial displays. (SWAT+ has developed tools for this internally...)
| style="background: #F5FCFF; vertical-align: top; text-align:left;" |'''Software-specific .dfs2 and .dfs3 file formats used in general. A few inputs allow standard shapefiles.'''
 dfs2 files are 2D gridded data. Standard GIS grids can be saved in an ASCI format in GIS software and then a MIKE tool applied to convert to dfs2. Subcatchments and landcover can be input as shapefiles. Many hydrological predictions can be output as spatial data as .dfs3 files, 3 dimensional data "cubes": a 2D grid of values (e.g. transpiration, surface water depth, soil moisture, groundwater depth) for each timestep, all in one file. These can be stepped-through or played as video in the interface. Timeseries for point locations or specified areas can be extracted. .dfs2 files can be converted to ASCI files to open in GIS software using an in-built tool.
|}


== User impressions of 'ease-of-use' (modeller survey) ==
A brief survey for hydrological modellers was distributed via the South African Hydrology Society (SAHS) as part of the [[Model inter-comparison study|model intercomparison project (2019-2021)]]. Participants were asked to rank the ease-of-use of the software user interface, it's documentation, and available support for any modelling tools they were familiar with on a scale of 1-5 in which: '''1=poor, 3=satisfactory, 5= excellent'''
There was a very wide range of scores assigned for each tool across the respondents, showing that different people experience the tools differently! 
Both the average and the range of scores assigned are presented below.
(Links to online documentation and support resources for these tools are provided [[Modelling tool documentation|here]])
{| class="wikitable"
! scope="col" style="width:15em" | Survey data <big></big>
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
|-
| style="vertical-align: vertical-align: center;" |''Number of users answering survey''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''13''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''14''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''19''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''9''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |''8''
|-
| style="vertical-align: vertical-align: center;" |'''Average ease-of-use score''' 1-poor to 5-excellent
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |3.8
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |3.4
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |3.4
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |3.9
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |3.0
|-
| style="vertical-align: vertical-align: center;" |'''Range of scores assigned''' 1-poor to 5-excellent
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |2 - 5
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |2 - 5
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |1 - 5
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |3 - 5
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |1 - 5
|}

Modelling tool user interfaces

2023-12-04T09:11:29Z

Julia Glenday:

The tables below compare some main features of the user interfaces of the selected modelling tools that relate to their ease of use. These include approximate comparisons of typical model run times and the computing power needed to run them, as well as how easy it is to export and view various model outputs and test different parameter value options for sensitivity analyses and/or calibration. (More specifics about what outputs each tool can produce is covered [[Water balance outputs across tools|here]].)

What can be achieved in the time available for a modelling project is influenced by the combination of how long it takes to set up a model (including preparing input data in the needed format, setting up the structure, entering the parameter values), how long it takes for the model to run, how long it takes to access model outputs of interest, and how long it takes to test and refine the model. Some modelling tools may run very quickly, but take a relatively long time to set up and don't have an efficient way to change and test multiple parameter value options, which makes calibration a time consuming, laborious, manual process. Other tools may take long to run, but can be set up to do a number of parameter testing runs and even scenario runs at once, allowing the modeller to attend to other work in the meantime (however they may have to do so on another computer if the model requires a lot of computing power!).

Ease and efficiency of software use is also influenced by the documentation and support available for the tool. How accessible and user-friendly these are can determine whether or not users getting stuck trouble-shooting for long periods of time or inadvertently modelling things incorrectly. User impressions of the ease of use of tool interfaces, documentation, and support are provided [[#User impressions of 'ease-of-use' (modeller survey)|below]]. Links to online documentation and support resources for these tools are provided [[Modelling tool documentation|here]]

__TOC__



== Interface comparison ==

{| class="wikitable"
! scope="col" style="width:15em" | Interface characteristic <big></big>
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
|-
| style="vertical-align: vertical-align: center;" |Graphical user interface ''(vs code prompt)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Catchment map display (visualise linkages)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model run times'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Estimated model run time for a 30 year run, ~300km^2 catchment ''(Note: will depend on model set-up complexity & computing power!)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |tens of minutes
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |hours
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Computing resources needed'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Comparative rating of computing power needed to achieve workable run times.
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |light
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |light
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |light
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |medium
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |intensive (need good GPU)
|-
| colspan="6" style="background: #FFFFFF; vertical-align: vertical-align: center;" |'''Model set-up ease & efficiency'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Automated creation of model units & connections from map inputs ''(vs fully manual creation)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Input parameter values and change values for batches of models units ''(e.g., all HRUs of a cover type)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |In-built database of suggested parameter values ''(e.g., for common vegetation types, soil types, etc.)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |no
|-
| style="vertical-align: vertical-align: center;" |User can build own parameter databases for use across multiple models
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model set-up transparency''' (i.e., is it very obvious what the model is doing/assuming?) <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Interface makes the user interact with every component & parameter entry option during model set-up ''(vs having default parameter values pre-entered & not forcing user to view them)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |no
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Tool checks connection errors
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Batch runs & calibration tools''' <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Facility for batch runs, parameter sensitivity analyses, uncertainty analyses & auto-calibration
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Accessing model output''' <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for streamflow
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for water balance fluxes and stores
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |All water balance components that are calculated by the model can be exported
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Batch export of water balance fluxes for model's basic spatial units
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Automated extraction of water balance fluxes for different spatial scales ''(e.g., by cover class area, by subcatchment, full catchment)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|}


== Formats of input and output data ==

The table below gives some basic information about the file formats used for model inputs and outputs across the different modelling tools to give a general impression of what is required to work with them. This is a very rough overview and one has to work with user manuals, tutorials, and/or pre-exist demonstration models and data to understand the various formatting requirements and file types used across the inputs and outputs of a specific software tool. For large or complex model set-ups that will have many different inputs (e.g., different input rainfall timeseries for several different points across the modelled area), it is highly recommended to use coding tools like R or Python to prepare the input files as it will be time-consuming to get many files into the same specific formatting required by the modelling software and most do not have in-built conversion tools.

{| class="wikitable"
! scope="col" style="width:10%" |'''Data type''' <big></big>
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE
|-
| style="vertical-align: top;" |'''Timeseries data'''
| style="background: #FFF5FA; vertical-align: top; text-align: left;" |'''Specially formatted text files (special file extensions)'''
 Monthly data with years as rows and a column for each month in a water year starting in Oct, and for some types an annual sum in an additional column. Files can be read and generated by text editors (like Notepad) outside of WRSM, even though the files do not have typical text file extensions (e.g. ".txt"). WRSM input and output file extensions show the type of data (e.g., .RAN file is a rainfall timeseries file). Data can be brought into Excel for analyses, but it is difficult to create the input file formatting within Excel. A text editor or a general coding interface like an R or Python editor can be used to achieve the needed input data timeseries.
| style="background: #FFF7F5; vertical-align: top; text-align: left;" |'''Specially formatted text files (.txt)'''
 Some flexibility on the formatting for inputs as one can specify the row/column format and date formatting in the files in the tools' input interface. Inputs can be prepared in Excel and outputs easily opened there as well.
| style="background: #F5FFF5; vertical-align: top; text-align: left;" |'''Specially formatted ASCII text files (.txt) & .DBF files'''
 Input is daily data in long-format (one date per row) in a composite file containing climate variable and observed flow inputs in specified column orders and number formats. Difficult to prepare simply in Excel, and labour intensive to prepare in a text editor (e.g, Notepad), but reasonable to prepare in a general coding programme like R or Python. Outputs are .dbf format text files which open easily in Excel.
| style="background: #FFFFF5; vertical-align: top; text-align: left;" |'''Specially formatted text files (.txt) & Access database files '''
 Daily data in long-format (one date per row) text files. Reasonable to prepare and easy to open in Excel. Outputs can also be produced in an Access database.
| style="background: #F5FCFF; vertical-align: top; text-align: left;" |'''Software-specific .dfs0 file format'''
 Dfs0 files for input must be generated within MIKE software. Data in long-format (each row is a timestep) prepared in Excel can be copy-pasted into a blank dfs0 file with the correct number of rows and data from dfs0 files can be copy-pasted into Excel. There are also batch conversion tools in MIKE that can be used to convert specifically formatted text files into dfs0 files and to convert dfs0 files into text files.
|-
| style="vertical-align: top;" |'''Spatial data'''
| style="background: #FFF5FA; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of modules: what areas will have their own modules (e.g. subcatchment delineation; special cover types to represent separately, like plantations, irrigated areas, wetlands; river reaches and dams), determine sizes and other characteristics of the modules, and how they are linked to one another.''
| style="background: #FFF7F5; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments: subcatchment delineation plus special features to represent specifically like dams, plantations, irrigated areas, wetlands), determine the sizes and other characteristics of subcatchments and special areas, and how subcatchments are linked to one another.''
| style="background: #F5FFF5; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments composed of HRUs, river reaches, & dams: subcatchment delineation, what areas will have their own HRUs (land cover types to represent individually), determine the sizes and other characteristics of the HRUs, and how units linked to one another.''
| style="background: #FFFFF5; vertical-align: top; text-align:left;" |'''Standard GIS shapefile and grid/raster files (geotif, grid) used.'''
 DEM input must be a raster. Land cover and soil type data can be input as shapefiles or rasters (see user manuals for formatting/attribute requirements). Tool-delineated subcatchments, river lines, HRUs are output as shapefiles. Hydrological predictions are not output in a spatial format. The data can be linked back to spatial units based on ID numbers manually by the user for spatial displays. (SWAT+ has developed tools for this internally...)
| style="background: #F5FCFF; vertical-align: top; text-align:left;" |'''Software-specific .dfs2 and .dfs3 file formats used in general. A few inputs allow standard shapefiles.'''
 dfs2 files are 2D gridded data. Standard GIS grids can be saved in an ASCI format in GIS software and then a MIKE tool applied to convert to dfs2. Subcatchments and landcover can be input as shapefiles. Many hydrological predictions can be output as spatial data as .dfs3 files, 3 dimensional data "cubes": a 2D grid of values (e.g. transpiration, surface water depth, soil moisture, groundwater depth) for each timestep, all in one file. These can be stepped-through or played as video in the interface. Timeseries for point locations or specified areas can be extracted. .dfs2 files can be converted to ASCI files to open in GIS software using an in-built tool.
|}


== User impressions of 'ease-of-use' (modeller survey) ==
A brief survey for hydrological modellers was distributed via the South African Hydrology Society (SAHS) as part of the [[Model inter-comparison study|model intercomparison project (2019-2021)]]. Participants were asked to rank the ease-of-use of the software user interface, it's documentation, and available support for any modelling tools they were familiar with on a scale of 1-5 in which: '''1=poor, 3=satisfactory, 5= excellent'''
There was a very wide range of scores assigned for each tool across the respondents, showing that different people experience the tools differently! 
Both the average and the range of scores assigned are presented below.
(Links to online documentation and support resources for these tools are provided [[Modelling tool documentation|here]])
{| class="wikitable"
! scope="col" style="width:15em" | Survey data <big></big>
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
|-
| style="vertical-align: vertical-align: center;" |''Number of users answering survey''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''13''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''14''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''19''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''9''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |''8''
|-
| style="vertical-align: vertical-align: center;" |'''Average ease-of-use score''' 1-poor to 5-excellent
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |3.8
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |3.4
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |3.4
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |3.9
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |3.0
|-
| style="vertical-align: vertical-align: center;" |'''Range of scores assigned''' 1-poor to 5-excellent
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |2 - 5
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |2 - 5
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |1 - 5
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |3 - 5
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |1 - 5
|}

Modelling tool user interfaces

2023-12-04T09:10:51Z

Julia Glenday:

The tables below compare some main features of the user interfaces of the selected modelling tools that relate to their ease of use. These include approximate comparisons of typical model run times and the computing power needed to run them, as well as how easy it is to export and view various model outputs and test different parameter value options for sensitivity analyses and/or calibration. (More specifics about what outputs each tool can produce is covered [[Water balance outputs across tools|here]].)

What can be achieved in the time available for a modelling project is influenced by the combination of how long it takes to set up a model (including preparing input data in the needed format, setting up the structure, entering the parameter values), how long it takes for the model to run, how long it takes to access model outputs of interest, and how long it takes to test and refine the model. Some modelling tools may run very quickly, but take a relatively long time to set up and don't have an efficient way to change and test multiple parameter value options, which makes calibration a time consuming, laborious, manual process. Other tools may take long to run, but can be set up to do a number of parameter testing runs and even scenario runs at once, allowing the modeller to attend to other work in the meantime (however they may have to do so on another computer if the model requires a lot of computing power!).

Ease and efficiency of software use is also influenced by the documentation and support available for the tool. How accessible and user-friendly these are can determine whether or not users getting stuck trouble-shooting for long periods of time or inadvertently modelling things incorrectly. User impressions of the ease of use of tool interfaces, documentation, and support are provided [[below]]. Links to online documentation and support resources for these tools are provided [[Modelling tool documentation|here]]

__TOC__



== Interface comparison ==

{| class="wikitable"
! scope="col" style="width:15em" | Interface characteristic <big></big>
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
|-
| style="vertical-align: vertical-align: center;" |Graphical user interface ''(vs code prompt)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Catchment map display (visualise linkages)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model run times'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Estimated model run time for a 30 year run, ~300km^2 catchment ''(Note: will depend on model set-up complexity & computing power!)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |tens of minutes
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |hours
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Computing resources needed'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Comparative rating of computing power needed to achieve workable run times.
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |light
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |light
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |light
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |medium
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |intensive (need good GPU)
|-
| colspan="6" style="background: #FFFFFF; vertical-align: vertical-align: center;" |'''Model set-up ease & efficiency'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Automated creation of model units & connections from map inputs ''(vs fully manual creation)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Input parameter values and change values for batches of models units ''(e.g., all HRUs of a cover type)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |In-built database of suggested parameter values ''(e.g., for common vegetation types, soil types, etc.)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |no
|-
| style="vertical-align: vertical-align: center;" |User can build own parameter databases for use across multiple models
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model set-up transparency''' (i.e., is it very obvious what the model is doing/assuming?) <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Interface makes the user interact with every component & parameter entry option during model set-up ''(vs having default parameter values pre-entered & not forcing user to view them)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |no
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Tool checks connection errors
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Batch runs & calibration tools''' <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Facility for batch runs, parameter sensitivity analyses, uncertainty analyses & auto-calibration
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Accessing model output''' <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for streamflow
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for water balance fluxes and stores
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |All water balance components that are calculated by the model can be exported
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Batch export of water balance fluxes for model's basic spatial units
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Automated extraction of water balance fluxes for different spatial scales ''(e.g., by cover class area, by subcatchment, full catchment)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|}


== Formats of input and output data ==

The table below gives some basic information about the file formats used for model inputs and outputs across the different modelling tools to give a general impression of what is required to work with them. This is a very rough overview and one has to work with user manuals, tutorials, and/or pre-exist demonstration models and data to understand the various formatting requirements and file types used across the inputs and outputs of a specific software tool. For large or complex model set-ups that will have many different inputs (e.g., different input rainfall timeseries for several different points across the modelled area), it is highly recommended to use coding tools like R or Python to prepare the input files as it will be time-consuming to get many files into the same specific formatting required by the modelling software and most do not have in-built conversion tools.

{| class="wikitable"
! scope="col" style="width:10%" |'''Data type''' <big></big>
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE
|-
| style="vertical-align: top;" |'''Timeseries data'''
| style="background: #FFF5FA; vertical-align: top; text-align: left;" |'''Specially formatted text files (special file extensions)'''
 Monthly data with years as rows and a column for each month in a water year starting in Oct, and for some types an annual sum in an additional column. Files can be read and generated by text editors (like Notepad) outside of WRSM, even though the files do not have typical text file extensions (e.g. ".txt"). WRSM input and output file extensions show the type of data (e.g., .RAN file is a rainfall timeseries file). Data can be brought into Excel for analyses, but it is difficult to create the input file formatting within Excel. A text editor or a general coding interface like an R or Python editor can be used to achieve the needed input data timeseries.
| style="background: #FFF7F5; vertical-align: top; text-align: left;" |'''Specially formatted text files (.txt)'''
 Some flexibility on the formatting for inputs as one can specify the row/column format and date formatting in the files in the tools' input interface. Inputs can be prepared in Excel and outputs easily opened there as well.
| style="background: #F5FFF5; vertical-align: top; text-align: left;" |'''Specially formatted ASCII text files (.txt) & .DBF files'''
 Input is daily data in long-format (one date per row) in a composite file containing climate variable and observed flow inputs in specified column orders and number formats. Difficult to prepare simply in Excel, and labour intensive to prepare in a text editor (e.g, Notepad), but reasonable to prepare in a general coding programme like R or Python. Outputs are .dbf format text files which open easily in Excel.
| style="background: #FFFFF5; vertical-align: top; text-align: left;" |'''Specially formatted text files (.txt) & Access database files '''
 Daily data in long-format (one date per row) text files. Reasonable to prepare and easy to open in Excel. Outputs can also be produced in an Access database.
| style="background: #F5FCFF; vertical-align: top; text-align: left;" |'''Software-specific .dfs0 file format'''
 Dfs0 files for input must be generated within MIKE software. Data in long-format (each row is a timestep) prepared in Excel can be copy-pasted into a blank dfs0 file with the correct number of rows and data from dfs0 files can be copy-pasted into Excel. There are also batch conversion tools in MIKE that can be used to convert specifically formatted text files into dfs0 files and to convert dfs0 files into text files.
|-
| style="vertical-align: top;" |'''Spatial data'''
| style="background: #FFF5FA; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of modules: what areas will have their own modules (e.g. subcatchment delineation; special cover types to represent separately, like plantations, irrigated areas, wetlands; river reaches and dams), determine sizes and other characteristics of the modules, and how they are linked to one another.''
| style="background: #FFF7F5; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments: subcatchment delineation plus special features to represent specifically like dams, plantations, irrigated areas, wetlands), determine the sizes and other characteristics of subcatchments and special areas, and how subcatchments are linked to one another.''
| style="background: #F5FFF5; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments composed of HRUs, river reaches, & dams: subcatchment delineation, what areas will have their own HRUs (land cover types to represent individually), determine the sizes and other characteristics of the HRUs, and how units linked to one another.''
| style="background: #FFFFF5; vertical-align: top; text-align:left;" |'''Standard GIS shapefile and grid/raster files (geotif, grid) used.'''
 DEM input must be a raster. Land cover and soil type data can be input as shapefiles or rasters (see user manuals for formatting/attribute requirements). Tool-delineated subcatchments, river lines, HRUs are output as shapefiles. Hydrological predictions are not output in a spatial format. The data can be linked back to spatial units based on ID numbers manually by the user for spatial displays. (SWAT+ has developed tools for this internally...)
| style="background: #F5FCFF; vertical-align: top; text-align:left;" |'''Software-specific .dfs2 and .dfs3 file formats used in general. A few inputs allow standard shapefiles.'''
 dfs2 files are 2D gridded data. Standard GIS grids can be saved in an ASCI format in GIS software and then a MIKE tool applied to convert to dfs2. Subcatchments and landcover can be input as shapefiles. Many hydrological predictions can be output as spatial data as .dfs3 files, 3 dimensional data "cubes": a 2D grid of values (e.g. transpiration, surface water depth, soil moisture, groundwater depth) for each timestep, all in one file. These can be stepped-through or played as video in the interface. Timeseries for point locations or specified areas can be extracted. .dfs2 files can be converted to ASCI files to open in GIS software using an in-built tool.
|}


== User impressions of 'ease-of-use' (modeller survey) ==
A brief survey for hydrological modellers was distributed via the South African Hydrology Society (SAHS) as part of the [[Model inter-comparison study|model intercomparison project (2019-2021)]]. Participants were asked to rank the ease-of-use of the software user interface, it's documentation, and available support for any modelling tools they were familiar with on a scale of 1-5 in which: '''1=poor, 3=satisfactory, 5= excellent'''
There was a very wide range of scores assigned for each tool across the respondents, showing that different people experience the tools differently! 
Both the average and the range of scores assigned are presented below.
(Links to online documentation and support resources for these tools are provided [[Modelling tool documentation|here]])
{| class="wikitable"
! scope="col" style="width:15em" | Survey data <big></big>
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
|-
| style="vertical-align: vertical-align: center;" |''Number of users answering survey''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''13''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''14''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''19''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''9''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |''8''
|-
| style="vertical-align: vertical-align: center;" |'''Average ease-of-use score''' 1-poor to 5-excellent
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |3.8
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |3.4
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |3.4
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |3.9
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |3.0
|-
| style="vertical-align: vertical-align: center;" |'''Range of scores assigned''' 1-poor to 5-excellent
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |2 - 5
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |2 - 5
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |1 - 5
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |3 - 5
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |1 - 5
|}

MediaWiki:Sidebar

2023-12-04T08:48:33Z

Julia Glenday:

* navigation
** mainpage|mainpage-description
** Scope: what’s covered (and not!) in this wiki|Wiki scope
** Content team|Content team
** How to use "Discussion" pages|Discussion pages
* BACKGROUND
** Terminology|Terminology
** Modelling process overview|Modelling process overview
** Model types & tools|Model types & tools
* MODELLING TOOL INTERCOMPARISON
** Modelling tool capability overview|Capabilities overview
** Model units & connections|Model units & connections
** Process representation across tools|Process representation
** Water balance outputs across tools|Water balance outputs
** Modelling tool user interfaces|User interfaces
** Applying tools in specific use cases|Specific use cases
* RESOURCES
** Modelling tool documentation|Tool documentation
** Stack Exchange Question & Answer platform|Q & A platform
** Data sources|Data sources
** Model inter-comparison study|Inter-comparison study

* SEARCH
* TOOLBOX
* LANGUAGES

MediaWiki:Sidebar

2023-12-04T08:45:15Z

Julia Glenday:

* navigation
** mainpage|mainpage-description
** Scope: what’s covered (and not!) in this wiki|Wiki scope
** Content team|Content team
** How to use "Discussion" pages|Discussion pages

* BACKGROUND
** Terminology|Terminology
** Modelling process overview|Modelling process overview
** Model types & tools|Model types & tools

* MODELLING TOOL INTERCOMPARISON
** Modelling tool capability overview|Capabilities overview
** Model units & connections|Model units & connections
** Process representation across tools|Process representation
** Water balance outputs across tools|Water balance outputs
** Modelling tool user interfaces|User interfaces
** Applying tools in specific use cases|Specific use cases

* RESOURCE LINKS
** Modelling tool documentation|Tool documentation
** Stack Exchange Question & Answer platform|Q & A platform
** Data sources|Data sources
** Model inter-comparison study|Inter-comparison study

* SEARCH
* TOOLBOX
* LANGUAGES

MediaWiki:Sidebar

2023-12-04T08:44:45Z

Julia Glenday:

* navigation
** mainpage|mainpage-description
** Scope: what’s covered (and not!) in this wiki|Wiki scope
** Content team|Content team
** How to use "Discussion" pages|Discussion pages

* BACKGROUND
** Terminology|Terminology
** Modelling process overview|Modelling process overview
** Model types & tools|Model types & tools

* MODELLING TOOL INTERCOMPARISON
** Modelling tool capability overview|Capabilities overview
** Model units & connections|Model units & connections
** Process representation across tools|Process representation
** Water balance outputs across tools|Water balance outputs
** Modelling tool user interfaces|User interfaces
** Applying tools in specific use cases|Specific use cases

* RESOURCES
** Modelling tool documentation|Tool documentation
** Stack Exchange Question & Answer platform|Q & A platform
** Data sources|Data sources
** Model inter-comparison study|Inter-comparison study

* SEARCH
* TOOLBOX
* LANGUAGES

MediaWiki:Sidebar

2023-12-04T08:44:22Z

Julia Glenday:

* navigation
** mainpage|mainpage-description
** Scope: what’s covered (and not!) in this wiki|Wiki scope
** Content team|Content team
** How to use "Discussion" pages|Discussion pages

* BACKGROUND
** Terminology|Terminology
** Modelling process overview|Modelling process overview
** Model types & tools|Model types & tools

* MODELLING TOOL INTERCOMPARISON
** Modelling tool capability overview|Capabilities overview
** Model units & connections|Model units & connections
** Process representation across tools|Process representation
** Water balance outputs across tools|Water balance outputs
** Modelling tool user interfaces|User interfaces
** Applying tools in specific use cases|Specific use cases

* BACKGROUND
** Modelling tool documentation|Tool documentation
** Stack Exchange Question & Answer platform|Q & A platform
** Data sources|Data sources
** Model inter-comparison study|Inter-comparison study

* SEARCH
* TOOLBOX
* LANGUAGES

MediaWiki:Sidebar

2023-12-04T08:42:47Z

Julia Glenday:

* navigation
** mainpage|mainpage-description
** Scope: what’s covered (and not!) in this wiki|Wiki scope
** Content team|Content team
** How to use "Discussion" pages|Discussion pages

* BACKGROUND
** Terminology|Terminology
** Modelling process overview|Modelling process overview
** Model types & tools|Model types & tools

* MODELLING TOOL INTERCOMPARISON
** Modelling tool capability overview|Capabilities overview
** Model units & connections|Model units & connections
** Process representation across tools|Process representation
** Water balance outputs across tools|Water balance outputs
** Modelling tool user interfaces|User interfaces
** Applying tools in specific use cases|Specific use cases

* RESOURCES
** Modelling tool documentation|Tool documentation
** Stack Exchange Question & Answer platform|Q & A platform
** Data sources|Data sources
** Model inter-comparison study|Inter-comparison study

* SEARCH
* TOOLBOX
* LANGUAGES

MediaWiki:Sidebar

2023-12-04T08:41:23Z

Julia Glenday:

* navigation
** mainpage|mainpage-description
** Scope: what’s covered (and not!) in this wiki|Wiki scope
** Content team|Content team
** How to use "Discussion" pages|Discussion pages

* <big>'''Background'''</big>
** Terminology|Terminology
** Modelling process overview|Modelling process overview
** Model types & tools|Model types & tools

* <big>'''Modelling tool inter-comparison'''</big>
** Modelling tool capability overview|Capabilities overview
** Model units & connections|Model units & connections
** Process representation across tools|Process representation
** Water balance outputs across tools|Water balance outputs
** Modelling tool user interfaces|User interfaces
** Applying tools in specific use cases|Specific use cases

* <big>'''Resource links'''</big>
** Modelling tool documentation|Tool documentation
** Stack Exchange Question & Answer platform|Q & A platform
** Data sources|Data sources
** Model inter-comparison study|Inter-comparison study

* SEARCH
* TOOLBOX
* LANGUAGES

Modelling tool user interfaces

2023-12-04T08:32:58Z

Julia Glenday:

The tables below compare some main features of the user interfaces of the selected modelling tools that relate to their ease of use. These include approximate comparisons of typical model run times and the computing power needed to run them, as well as how easy it is to export and view various model outputs and test different parameter value options for sensitivity analyses and/or calibration.

The combination of how long it takes to set up a model (including preparing input data in the needed format, setting up the structure, entering the parameter values), how long it takes for the model to run, how long it takes to access model outputs of interest, and how long it takes to test and refine the model influences what can be achieved in the time that is available for a modelling project. Some modelling tools may run very quickly, but take a relatively long time to set up and don't have an efficient way to change and test multiple parameter value options, which makes calibration a time consuming, manual process. Other tools may take long to run, but can be set up to do a number of parameter testing runs and even scenario runs at once, allowing the modeller to attend to other work in the meantime (however they may have to do so on another computer if the model requires a lot of computing power!).

Ease and efficiency of software use is also influenced by the documentation and support available for the tool - how accessible and user-friendly these are can prevent users getting stuck trouble-shooting for long periods of time or inadvertently modelling things incorrectly.

__TOC__



== Interface comparison overview ==

{| class="wikitable"
! scope="col" style="width:15em" | Interface characteristic <big></big>
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
|-
| style="vertical-align: vertical-align: center;" |Graphical user interface ''(vs code prompt)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Catchment map display (visualise linkages)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model run times'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Estimated model run time for a 30 year run, ~300km^2 catchment ''(Note: will depend on model set-up complexity & computing power!)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |tens of minutes
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |hours
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Computing resources needed'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Comparative rating of computing power needed to achieve workable run times.
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |light
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |light
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |light
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |medium
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |intensive (need good GPU)
|-
| colspan="6" style="background: #FFFFFF; vertical-align: vertical-align: center;" |'''Model set-up ease & efficiency'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Automated creation of model units & connections from map inputs ''(vs fully manual creation)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Input parameter values and change values for batches of models units ''(e.g., all HRUs of a cover type)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |In-built database of suggested parameter values ''(e.g., for common vegetation types, soil types, etc.)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |no
|-
| style="vertical-align: vertical-align: center;" |User can build own parameter databases for use across multiple models
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model set-up transparency''' (i.e., is it very obvious what the model is doing/assuming?) <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Interface makes the user interact with every component & parameter entry option during model set-up ''(vs having default parameter values pre-entered & not forcing user to view them)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |no
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Tool checks connection errors
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Batch runs & calibration tools''' <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Facility for batch runs, parameter sensitivity analyses, uncertainty analyses & auto-calibration
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Accessing model output''' <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for streamflow
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for water balance fluxes and stores
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |All water balance components that are calculated by the model can be exported
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Batch export of water balance fluxes for model's basic spatial units
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Automated extraction of water balance fluxes for different spatial scales ''(e.g., by cover class area, by subcatchment, full catchment)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|}


== Formats of input and output data ==

The table below gives some basic information about the file formats used for model inputs and outputs across the different modelling tools to give a general impression of what is required to work with them. This is a very rough overview and one has to work with user manuals, tutorials, and/or pre-exist demonstration models and data to understand the various formatting requirements and file types used across the inputs and outputs of a specific software tool. For large or complex model set-ups that will have many different inputs (e.g., different input rainfall timeseries for several different points across the modelled area), it is highly recommended to use coding tools like R or Python to prepare the input files as it will be time-consuming to get many files into the same specific formatting required by the modelling software and most do not have in-built conversion tools.

{| class="wikitable"
! scope="col" style="width:10%" |'''Data type''' <big></big>
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE
|-
| style="vertical-align: top;" |'''Timeseries data'''
| style="background: #FFF5FA; vertical-align: top; text-align: left;" |'''Specially formatted text files (special file extensions)'''
 Monthly data with years as rows and a column for each month in a water year starting in Oct, and for some types an annual sum in an additional column. Files can be read and generated by text editors (like Notepad) outside of WRSM, even though the files do not have typical text file extensions (e.g. ".txt"). WRSM input and output file extensions show the type of data (e.g., .RAN file is a rainfall timeseries file). Data can be brought into Excel for analyses, but it is difficult to create the input file formatting within Excel. A text editor or a general coding interface like an R or Python editor can be used to achieve the needed input data timeseries.
| style="background: #FFF7F5; vertical-align: top; text-align: left;" |'''Specially formatted text files (.txt)'''
 Some flexibility on the formatting for inputs as one can specify the row/column format and date formatting in the files in the tools' input interface. Inputs can be prepared in Excel and outputs easily opened there as well.
| style="background: #F5FFF5; vertical-align: top; text-align: left;" |'''Specially formatted ASCII text files (.txt) & .DBF files'''
 Input is daily data in long-format (one date per row) in a composite file containing climate variable and observed flow inputs in specified column orders and number formats. Difficult to prepare simply in Excel, and labour intensive to prepare in a text editor (e.g, Notepad), but reasonable to prepare in a general coding programme like R or Python. Outputs are .dbf format text files which open easily in Excel.
| style="background: #FFFFF5; vertical-align: top; text-align: left;" |'''Specially formatted text files (.txt) & Access database files '''
 Daily data in long-format (one date per row) text files. Reasonable to prepare and easy to open in Excel. Outputs can also be produced in an Access database.
| style="background: #F5FCFF; vertical-align: top; text-align: left;" |'''Software-specific .dfs0 file format'''
 Dfs0 files for input must be generated within MIKE software. Data in long-format (each row is a timestep) prepared in Excel can be copy-pasted into a blank dfs0 file with the correct number of rows and data from dfs0 files can be copy-pasted into Excel. There are also batch conversion tools in MIKE that can be used to convert specifically formatted text files into dfs0 files and to convert dfs0 files into text files.
|-
| style="vertical-align: top;" |'''Spatial data'''
| style="background: #FFF5FA; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of modules: what areas will have their own modules (e.g. subcatchment delineation; special cover types to represent separately, like plantations, irrigated areas, wetlands; river reaches and dams), determine sizes and other characteristics of the modules, and how they are linked to one another.''
| style="background: #FFF7F5; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments: subcatchment delineation plus special features to represent specifically like dams, plantations, irrigated areas, wetlands), determine the sizes and other characteristics of subcatchments and special areas, and how subcatchments are linked to one another.''
| style="background: #F5FFF5; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments composed of HRUs, river reaches, & dams: subcatchment delineation, what areas will have their own HRUs (land cover types to represent individually), determine the sizes and other characteristics of the HRUs, and how units linked to one another.''
| style="background: #FFFFF5; vertical-align: top; text-align:left;" |'''Standard GIS shapefile and grid/raster files (geotif, grid) used.'''
 DEM input must be a raster. Land cover and soil type data can be input as shapefiles or rasters (see user manuals for formatting/attribute requirements). Tool-delineated subcatchments, river lines, HRUs are output as shapefiles. Hydrological predictions are not output in a spatial format. The data can be linked back to spatial units based on ID numbers manually by the user for spatial displays. (SWAT+ has developed tools for this internally...)
| style="background: #F5FCFF; vertical-align: top; text-align:left;" |'''Software-specific .dfs2 and .dfs3 file formats used in general. A few inputs allow standard shapefiles.'''
 dfs2 files are 2D gridded data. Standard GIS grids can be saved in an ASCI format in GIS software and then a MIKE tool applied to convert to dfs2. Subcatchments and landcover can be input as shapefiles. Many hydrological predictions can be output as spatial data as .dfs3 files, 3 dimensional data "cubes": a 2D grid of values (e.g. transpiration, surface water depth, soil moisture, groundwater depth) for each timestep, all in one file. These can be stepped-through or played as video in the interface. Timeseries for point locations or specified areas can be extracted. .dfs2 files can be converted to ASCI files to open in GIS software using an in-built tool.
|}


== User impressions of 'ease-of-use' (modeller survey) ==
A brief survey for hydrological modellers was distributed via the South African Hydrology Society (SAHS) as part of the [[Model inter-comparison study|model intercomparison project (2019-2021)]]. Participants were asked to rank the ease-of-use of the software interface for any modelling tools they were familiar with on a scale of 1-5 in which: '''1=poor, 3=satisfactory, 5= excellent'''
There was a very wide range of scores assigned for each tool across the respondents, showing that different people experience the tools differently! 
Both the average and the range of scores assigned are presented below
{| class="wikitable"
! scope="col" style="width:15em" | Survey data <big></big>
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
|-
| style="vertical-align: vertical-align: center;" |''Number of users answering survey''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''13''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''14''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''19''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''9''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |''8''
|-
| style="vertical-align: vertical-align: center;" |'''Average ease-of-use score''' 1-poor to 5-excellent
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |3.8
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |3.4
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |3.4
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |3.9
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |3.0
|-
| style="vertical-align: vertical-align: center;" |'''Range of scores assigned''' 1-poor to 5-excellent
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |2 - 5
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |2 - 5
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |1 - 5
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |3 - 5
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |1 - 5
|}

== User ratings of tools' documentation & support (modeller survey) ==

In 2021, we surveyed the South African hydrological modelling community to ask them about their modelling background and level, which tools they used, and what their perceptions about these tools were. Specifically we asked them to rate the ease-of-use of the user interface, the ease-of-use of the documentation as well as the support of each modelling tool on a scale of 1-5, 1 being poor, 3 being satisfactory, and 5 being excellent. On 31 May 2021 we had 45 responses, and we summarised results here for any modelling tools that were reviewed by more than two people (i.e. sample size greater than 2). If you are choosing a modelling tool for your project, perhaps this table, as well as those on capabilities and specific use cases, would help you make a decision on which to select.

{| class="wikitable"
|+ <big>USER RATINGS OF MODELLING TOOLS</big>
! Modelling tool !! |Interface !! |Documentation !! |Support !! |Sample Size
|-
|style='background: #F5FFF5' | ACRU
|style='background: #F5FFF5' | 3.4
|style='background: #F5FFF5' |3.6
|style='background: #F5FFF5' |3.9
|style='background: #F5FFF5' |19
|-
|style='background: #FFF5FA' | WRSM-Pitman
|style='background: #FFF5FA' | 3.6
|style='background: #FFF5FA' |3.5
|style='background: #FFF5FA' |3.5
|style='background: #FFF5FA' |14
|-
|style='background: #FFF7F5' | SPATSIM-Pitman
|style='background: #FFF7F5' | 3.3
|style='background: #FFF7F5' |3.3
|style='background: #FFF7F5' |3.5
|style='background: #FFF7F5' |11
|-
|style='background: #FFFFF5' | SWAT
|style='background: #FFFFF5' | 3.6
|style='background: #FFFFF5' |3.9
|style='background: #FFFFF5' |3.8
|style='background: #FFFFF5' |9
|-
|style='background: #F5FCFF' | MIKE-SHE
|style='background: #F5FCFF' | 3.0
|style='background: #F5FCFF' |2.1
|style='background: #F5FCFF' |2.3
|style='background: #F5FCFF' |7
|}

Modelling tool user interfaces

2023-12-04T08:28:26Z

Julia Glenday: /* User ratings across tools */

The tables below compare some main features of the user interfaces of the selected modelling tools that relate to their ease of use. These include approximate comparisons of typical model run times and the computing power needed to run them, as well as how easy it is to export and view various model outputs and test different parameter value options for sensitivity analyses and/or calibration.

The combination of how long it takes to set up a model (including preparing input data in the needed format, setting up the structure, entering the parameter values), how long it takes for the model to run, how long it takes to access model outputs of interest, and how long it takes to test and refine the model influences what can be achieved in the time that is available for a modelling project. Some modelling tools may run very quickly, but take a relatively long time to set up and don't have an efficient way to change and test multiple parameter value options, which makes calibration a time consuming, manual process. Other tools may take long to run, but can be set up to do a number of parameter testing runs and even scenario runs at once, allowing the modeller to attend to other work in the meantime (however they may have to do so on another computer if the model requires a lot of computing power!).

__TOC__



== Interface comparison overview ==

{| class="wikitable"
! scope="col" style="width:15em" | Interface characteristic <big></big>
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
|-
| style="vertical-align: vertical-align: center;" |Graphical user interface ''(vs code prompt)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Catchment map display (visualise linkages)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model run times'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Estimated model run time for a 30 year run, ~300km^2 catchment ''(Note: will depend on model set-up complexity & computing power!)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |tens of minutes
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |hours
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Computing resources needed'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Comparative rating of computing power needed to achieve workable run times.
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |light
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |light
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |light
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |medium
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |intensive (need good GPU)
|-
| colspan="6" style="background: #FFFFFF; vertical-align: vertical-align: center;" |'''Model set-up ease & efficiency'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Automated creation of model units & connections from map inputs ''(vs fully manual creation)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Input parameter values and change values for batches of models units ''(e.g., all HRUs of a cover type)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |In-built database of suggested parameter values ''(e.g., for common vegetation types, soil types, etc.)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |no
|-
| style="vertical-align: vertical-align: center;" |User can build own parameter databases for use across multiple models
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model set-up transparency''' (i.e., is it very obvious what the model is doing/assuming?) <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Interface makes the user interact with every component & parameter entry option during model set-up ''(vs having default parameter values pre-entered & not forcing user to view them)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |no
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Tool checks connection errors
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Batch runs & calibration tools''' <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Facility for batch runs, parameter sensitivity analyses, uncertainty analyses & auto-calibration
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Accessing model output''' <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for streamflow
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for water balance fluxes and stores
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |All water balance components that are calculated by the model can be exported
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Batch export of water balance fluxes for model's basic spatial units
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Automated extraction of water balance fluxes for different spatial scales ''(e.g., by cover class area, by subcatchment, full catchment)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|}


== Formats of input and output data ==

The table below gives some basic information about the file formats used for model inputs and outputs across the different modelling tools to give a general impression of what is required to work with them. This is a very rough overview and one has to work with user manuals, tutorials, and/or pre-exist demonstration models and data to understand the various formatting requirements and file types used across the inputs and outputs of a specific software tool. For large or complex model set-ups that will have many different inputs (e.g., different input rainfall timeseries for several different points across the modelled area), it is highly recommended to use coding tools like R or Python to prepare the input files as it will be time-consuming to get many files into the same specific formatting required by the modelling software and most do not have in-built conversion tools.

{| class="wikitable"
! scope="col" style="width:10%" |'''Data type''' <big></big>
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE
|-
| style="vertical-align: top;" |'''Timeseries data'''
| style="background: #FFF5FA; vertical-align: top; text-align: left;" |'''Specially formatted text files (special file extensions)'''
 Monthly data with years as rows and a column for each month in a water year starting in Oct, and for some types an annual sum in an additional column. Files can be read and generated by text editors (like Notepad) outside of WRSM, even though the files do not have typical text file extensions (e.g. ".txt"). WRSM input and output file extensions show the type of data (e.g., .RAN file is a rainfall timeseries file). Data can be brought into Excel for analyses, but it is difficult to create the input file formatting within Excel. A text editor or a general coding interface like an R or Python editor can be used to achieve the needed input data timeseries.
| style="background: #FFF7F5; vertical-align: top; text-align: left;" |'''Specially formatted text files (.txt)'''
 Some flexibility on the formatting for inputs as one can specify the row/column format and date formatting in the files in the tools' input interface. Inputs can be prepared in Excel and outputs easily opened there as well.
| style="background: #F5FFF5; vertical-align: top; text-align: left;" |'''Specially formatted ASCII text files (.txt) & .DBF files'''
 Input is daily data in long-format (one date per row) in a composite file containing climate variable and observed flow inputs in specified column orders and number formats. Difficult to prepare simply in Excel, and labour intensive to prepare in a text editor (e.g, Notepad), but reasonable to prepare in a general coding programme like R or Python. Outputs are .dbf format text files which open easily in Excel.
| style="background: #FFFFF5; vertical-align: top; text-align: left;" |'''Specially formatted text files (.txt) & Access database files '''
 Daily data in long-format (one date per row) text files. Reasonable to prepare and easy to open in Excel. Outputs can also be produced in an Access database.
| style="background: #F5FCFF; vertical-align: top; text-align: left;" |'''Software-specific .dfs0 file format'''
 Dfs0 files for input must be generated within MIKE software. Data in long-format (each row is a timestep) prepared in Excel can be copy-pasted into a blank dfs0 file with the correct number of rows and data from dfs0 files can be copy-pasted into Excel. There are also batch conversion tools in MIKE that can be used to convert specifically formatted text files into dfs0 files and to convert dfs0 files into text files.
|-
| style="vertical-align: top;" |'''Spatial data'''
| style="background: #FFF5FA; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of modules: what areas will have their own modules (e.g. subcatchment delineation; special cover types to represent separately, like plantations, irrigated areas, wetlands; river reaches and dams), determine sizes and other characteristics of the modules, and how they are linked to one another.''
| style="background: #FFF7F5; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments: subcatchment delineation plus special features to represent specifically like dams, plantations, irrigated areas, wetlands), determine the sizes and other characteristics of subcatchments and special areas, and how subcatchments are linked to one another.''
| style="background: #F5FFF5; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments composed of HRUs, river reaches, & dams: subcatchment delineation, what areas will have their own HRUs (land cover types to represent individually), determine the sizes and other characteristics of the HRUs, and how units linked to one another.''
| style="background: #FFFFF5; vertical-align: top; text-align:left;" |'''Standard GIS shapefile and grid/raster files (geotif, grid) used.'''
 DEM input must be a raster. Land cover and soil type data can be input as shapefiles or rasters (see user manuals for formatting/attribute requirements). Tool-delineated subcatchments, river lines, HRUs are output as shapefiles. Hydrological predictions are not output in a spatial format. The data can be linked back to spatial units based on ID numbers manually by the user for spatial displays. (SWAT+ has developed tools for this internally...)
| style="background: #F5FCFF; vertical-align: top; text-align:left;" |'''Software-specific .dfs2 and .dfs3 file formats used in general. A few inputs allow standard shapefiles.'''
 dfs2 files are 2D gridded data. Standard GIS grids can be saved in an ASCI format in GIS software and then a MIKE tool applied to convert to dfs2. Subcatchments and landcover can be input as shapefiles. Many hydrological predictions can be output as spatial data as .dfs3 files, 3 dimensional data "cubes": a 2D grid of values (e.g. transpiration, surface water depth, soil moisture, groundwater depth) for each timestep, all in one file. These can be stepped-through or played as video in the interface. Timeseries for point locations or specified areas can be extracted. .dfs2 files can be converted to ASCI files to open in GIS software using an in-built tool.
|}


== User impressions of 'ease-of-use' (modeller survey) ==
A brief survey for hydrological modellers was distributed via the South African Hydrology Society (SAHS) as part of the [[Model inter-comparison study|model intercomparison project (2019-2021)]]. Participants were asked to rank the ease-of-use of the software interface for any modelling tools they were familiar with on a scale of 1-5 in which: '''1=poor, 3=satisfactory, 5= excellent'''
There was a very wide range of scores assigned for each tool across the respondents, showing that different people experience the tools differently! 
Both the average and the range of scores assigned are presented below
{| class="wikitable"
! scope="col" style="width:15em" | Survey data <big></big>
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
|-
| style="vertical-align: vertical-align: center;" |''Number of users answering survey''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''13''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''14''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''19''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''9''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |''8''
|-
| style="vertical-align: vertical-align: center;" |'''Average ease-of-use score''' 1-poor to 5-excellent
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |3.8
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |3.4
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |3.4
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |3.9
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |3.0
|-
| style="vertical-align: vertical-align: center;" |'''Range of scores assigned''' 1-poor to 5-excellent
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |2 - 5
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |2 - 5
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |1 - 5
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |3 - 5
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |1 - 5
|}

== User ratings of tools' documentation & support (modeller survey) ==

In 2021, we surveyed the South African hydrological modelling community to ask them about their modelling background and level, which tools they used, and what their perceptions about these tools were. Specifically we asked them to rate the ease-of-use of the user interface, the ease-of-use of the documentation as well as the support of each modelling tool on a scale of 1-5, 1 being poor, 3 being satisfactory, and 5 being excellent. On 31 May 2021 we had 45 responses, and we summarised results here for any modelling tools that were reviewed by more than two people (i.e. sample size greater than 2). If you are choosing a modelling tool for your project, perhaps this table, as well as those on capabilities and specific use cases, would help you make a decision on which to select.

{| class="wikitable"
|+ <big>USER RATINGS OF MODELLING TOOLS</big>
! Modelling tool !! |Interface !! |Documentation !! |Support !! |Sample Size
|-
|style='background: #F5FFF5' | ACRU
|style='background: #F5FFF5' | 3.4
|style='background: #F5FFF5' |3.6
|style='background: #F5FFF5' |3.9
|style='background: #F5FFF5' |19
|-
|style='background: #FFF5FA' | WRSM-Pitman
|style='background: #FFF5FA' | 3.6
|style='background: #FFF5FA' |3.5
|style='background: #FFF5FA' |3.5
|style='background: #FFF5FA' |14
|-
|style='background: #FFF7F5' | SPATSIM-Pitman
|style='background: #FFF7F5' | 3.3
|style='background: #FFF7F5' |3.3
|style='background: #FFF7F5' |3.5
|style='background: #FFF7F5' |11
|-
|style='background: #FFFFF5' | SWAT
|style='background: #FFFFF5' | 3.6
|style='background: #FFFFF5' |3.9
|style='background: #FFFFF5' |3.8
|style='background: #FFFFF5' |9
|-
|style='background: #F5FCFF' | MIKE-SHE
|style='background: #F5FCFF' | 3.0
|style='background: #F5FCFF' |2.1
|style='background: #F5FCFF' |2.3
|style='background: #F5FCFF' |7
|}

Modelling tool user interfaces

2023-12-04T08:25:47Z

Julia Glenday:

The tables below compare some main features of the user interfaces of the selected modelling tools that relate to their ease of use. These include approximate comparisons of typical model run times and the computing power needed to run them, as well as how easy it is to export and view various model outputs and test different parameter value options for sensitivity analyses and/or calibration.

The combination of how long it takes to set up a model (including preparing input data in the needed format, setting up the structure, entering the parameter values), how long it takes for the model to run, how long it takes to access model outputs of interest, and how long it takes to test and refine the model influences what can be achieved in the time that is available for a modelling project. Some modelling tools may run very quickly, but take a relatively long time to set up and don't have an efficient way to change and test multiple parameter value options, which makes calibration a time consuming, manual process. Other tools may take long to run, but can be set up to do a number of parameter testing runs and even scenario runs at once, allowing the modeller to attend to other work in the meantime (however they may have to do so on another computer if the model requires a lot of computing power!).

__TOC__



== Interface comparison overview ==

{| class="wikitable"
! scope="col" style="width:15em" | Interface characteristic <big></big>
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
|-
| style="vertical-align: vertical-align: center;" |Graphical user interface ''(vs code prompt)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Catchment map display (visualise linkages)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model run times'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Estimated model run time for a 30 year run, ~300km^2 catchment ''(Note: will depend on model set-up complexity & computing power!)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |tens of minutes
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |hours
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Computing resources needed'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Comparative rating of computing power needed to achieve workable run times.
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |light
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |light
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |light
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |medium
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |intensive (need good GPU)
|-
| colspan="6" style="background: #FFFFFF; vertical-align: vertical-align: center;" |'''Model set-up ease & efficiency'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Automated creation of model units & connections from map inputs ''(vs fully manual creation)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Input parameter values and change values for batches of models units ''(e.g., all HRUs of a cover type)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |In-built database of suggested parameter values ''(e.g., for common vegetation types, soil types, etc.)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |no
|-
| style="vertical-align: vertical-align: center;" |User can build own parameter databases for use across multiple models
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model set-up transparency''' (i.e., is it very obvious what the model is doing/assuming?) <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Interface makes the user interact with every component & parameter entry option during model set-up ''(vs having default parameter values pre-entered & not forcing user to view them)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |no
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Tool checks connection errors
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Batch runs & calibration tools''' <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Facility for batch runs, parameter sensitivity analyses, uncertainty analyses & auto-calibration
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Accessing model output''' <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for streamflow
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for water balance fluxes and stores
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |All water balance components that are calculated by the model can be exported
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Batch export of water balance fluxes for model's basic spatial units
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Automated extraction of water balance fluxes for different spatial scales ''(e.g., by cover class area, by subcatchment, full catchment)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|}


== Formats of input and output data ==

The table below gives some basic information about the file formats used for model inputs and outputs across the different modelling tools to give a general impression of what is required to work with them. This is a very rough overview and one has to work with user manuals, tutorials, and/or pre-exist demonstration models and data to understand the various formatting requirements and file types used across the inputs and outputs of a specific software tool. For large or complex model set-ups that will have many different inputs (e.g., different input rainfall timeseries for several different points across the modelled area), it is highly recommended to use coding tools like R or Python to prepare the input files as it will be time-consuming to get many files into the same specific formatting required by the modelling software and most do not have in-built conversion tools.

{| class="wikitable"
! scope="col" style="width:10%" |'''Data type''' <big></big>
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE
|-
| style="vertical-align: top;" |'''Timeseries data'''
| style="background: #FFF5FA; vertical-align: top; text-align: left;" |'''Specially formatted text files (special file extensions)'''
 Monthly data with years as rows and a column for each month in a water year starting in Oct, and for some types an annual sum in an additional column. Files can be read and generated by text editors (like Notepad) outside of WRSM, even though the files do not have typical text file extensions (e.g. ".txt"). WRSM input and output file extensions show the type of data (e.g., .RAN file is a rainfall timeseries file). Data can be brought into Excel for analyses, but it is difficult to create the input file formatting within Excel. A text editor or a general coding interface like an R or Python editor can be used to achieve the needed input data timeseries.
| style="background: #FFF7F5; vertical-align: top; text-align: left;" |'''Specially formatted text files (.txt)'''
 Some flexibility on the formatting for inputs as one can specify the row/column format and date formatting in the files in the tools' input interface. Inputs can be prepared in Excel and outputs easily opened there as well.
| style="background: #F5FFF5; vertical-align: top; text-align: left;" |'''Specially formatted ASCII text files (.txt) & .DBF files'''
 Input is daily data in long-format (one date per row) in a composite file containing climate variable and observed flow inputs in specified column orders and number formats. Difficult to prepare simply in Excel, and labour intensive to prepare in a text editor (e.g, Notepad), but reasonable to prepare in a general coding programme like R or Python. Outputs are .dbf format text files which open easily in Excel.
| style="background: #FFFFF5; vertical-align: top; text-align: left;" |'''Specially formatted text files (.txt) & Access database files '''
 Daily data in long-format (one date per row) text files. Reasonable to prepare and easy to open in Excel. Outputs can also be produced in an Access database.
| style="background: #F5FCFF; vertical-align: top; text-align: left;" |'''Software-specific .dfs0 file format'''
 Dfs0 files for input must be generated within MIKE software. Data in long-format (each row is a timestep) prepared in Excel can be copy-pasted into a blank dfs0 file with the correct number of rows and data from dfs0 files can be copy-pasted into Excel. There are also batch conversion tools in MIKE that can be used to convert specifically formatted text files into dfs0 files and to convert dfs0 files into text files.
|-
| style="vertical-align: top;" |'''Spatial data'''
| style="background: #FFF5FA; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of modules: what areas will have their own modules (e.g. subcatchment delineation; special cover types to represent separately, like plantations, irrigated areas, wetlands; river reaches and dams), determine sizes and other characteristics of the modules, and how they are linked to one another.''
| style="background: #FFF7F5; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments: subcatchment delineation plus special features to represent specifically like dams, plantations, irrigated areas, wetlands), determine the sizes and other characteristics of subcatchments and special areas, and how subcatchments are linked to one another.''
| style="background: #F5FFF5; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments composed of HRUs, river reaches, & dams: subcatchment delineation, what areas will have their own HRUs (land cover types to represent individually), determine the sizes and other characteristics of the HRUs, and how units linked to one another.''
| style="background: #FFFFF5; vertical-align: top; text-align:left;" |'''Standard GIS shapefile and grid/raster files (geotif, grid) used.'''
 DEM input must be a raster. Land cover and soil type data can be input as shapefiles or rasters (see user manuals for formatting/attribute requirements). Tool-delineated subcatchments, river lines, HRUs are output as shapefiles. Hydrological predictions are not output in a spatial format. The data can be linked back to spatial units based on ID numbers manually by the user for spatial displays. (SWAT+ has developed tools for this internally...)
| style="background: #F5FCFF; vertical-align: top; text-align:left;" |'''Software-specific .dfs2 and .dfs3 file formats used in general. A few inputs allow standard shapefiles.'''
 dfs2 files are 2D gridded data. Standard GIS grids can be saved in an ASCI format in GIS software and then a MIKE tool applied to convert to dfs2. Subcatchments and landcover can be input as shapefiles. Many hydrological predictions can be output as spatial data as .dfs3 files, 3 dimensional data "cubes": a 2D grid of values (e.g. transpiration, surface water depth, soil moisture, groundwater depth) for each timestep, all in one file. These can be stepped-through or played as video in the interface. Timeseries for point locations or specified areas can be extracted. .dfs2 files can be converted to ASCI files to open in GIS software using an in-built tool.
|}


== User impressions of 'ease-of-use' (modeller survey) ==
A brief survey for hydrological modellers was distributed via the South African Hydrology Society (SAHS) as part of the [[Model inter-comparison study|model intercomparison project (2019-2021)]]. Participants were asked to rank the ease-of-use of the software interface for any modelling tools they were familiar with on a scale of 1-5 in which: '''1=poor, 3=satisfactory, 5= excellent'''
There was a very wide range of scores assigned for each tool across the respondents, showing that different people experience the tools differently! 
Both the average and the range of scores assigned are presented below
{| class="wikitable"
! scope="col" style="width:15em" | Survey data <big></big>
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
|-
| style="vertical-align: vertical-align: center;" |''Number of users answering survey''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''13''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''14''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''19''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''9''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |''8''
|-
| style="vertical-align: vertical-align: center;" |'''Average ease-of-use score''' 1-poor to 5-excellent
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |3.8
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |3.4
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |3.4
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |3.9
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |3.0
|-
| style="vertical-align: vertical-align: center;" |'''Range of scores assigned''' 1-poor to 5-excellent
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |2 - 5
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |2 - 5
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |1 - 5
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |3 - 5
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |1 - 5
|}

== User ratings across tools ==

In 2021, we surveyed the South African hydrological modelling community to ask them about their modelling background and level, which tools they used, and what their perceptions about these tools were. Specifically we asked them to rate the ease-of-use of the user interface, the ease-of-use of the documentation as well as the support of each modelling tool on a scale of 1-5, 1 being poor, 3 being satisfactory, and 5 being excellent. On 31 May 2021 we had 45 responses, and we summarised results here for any modelling tools that were reviewed by more than two people (i.e. sample size greater than 2). If you are choosing a modelling tool for your project, perhaps this table, as well as those on capabilities and specific use cases, would help you make a decision on which to select.

{| class="wikitable"
|+ <big>USER RATINGS OF MODELLING TOOLS</big>
! Modelling tool !! |Interface !! |Documentation !! |Support !! |Sample Size
|-
|style='background: #F5FFF5' | ACRU
|style='background: #F5FFF5' | 3.4
|style='background: #F5FFF5' |3.6
|style='background: #F5FFF5' |3.9
|style='background: #F5FFF5' |19
|-
|style='background: #FFF5FA' | WRSM-Pitman
|style='background: #FFF5FA' | 3.6
|style='background: #FFF5FA' |3.5
|style='background: #FFF5FA' |3.5
|style='background: #FFF5FA' |14
|-
|style='background: #FFF7F5' | SPATSIM-Pitman
|style='background: #FFF7F5' | 3.3
|style='background: #FFF7F5' |3.3
|style='background: #FFF7F5' |3.5
|style='background: #FFF7F5' |11
|-
|style='background: #FFFFF5' | SWAT
|style='background: #FFFFF5' | 3.6
|style='background: #FFFFF5' |3.9
|style='background: #FFFFF5' |3.8
|style='background: #FFFFF5' |9
|-
|style='background: #F5FCFF' | MIKE-SHE
|style='background: #F5FCFF' | 3.0
|style='background: #F5FCFF' |2.1
|style='background: #F5FCFF' |2.3
|style='background: #F5FCFF' |7
|}

Documentation & support across tools

2023-12-04T08:24:54Z

Julia Glenday:

== User ratings across tools ==

In 2021, we surveyed the South African hydrological modelling community to ask them about their modelling background and level, which tools they used, and what their perceptions about these tools were. Specifically we asked them to rate the ease-of-use of the user interface, the ease-of-use of the documentation as well as the support of each modelling tool on a scale of 1-5, 1 being poor, 3 being satisfactory, and 5 being excellent. On 31 May 2021 we had 45 responses, and we summarised results here for any modelling tools that were reviewed by more than two people (i.e. sample size greater than 2). If you are choosing a modelling tool for your project, perhaps this table, as well as those on capabilities and specific use cases, would help you make a decision on which to select.

{| class="wikitable"
|+ <big>USER RATINGS OF MODELLING TOOLS</big>
! Modelling tool !! |Interface !! |Documentation !! |Support !! |Sample Size
|-
|style='background: #F5FFF5' | ACRU
|style='background: #F5FFF5' | 3.4
|style='background: #F5FFF5' |3.6
|style='background: #F5FFF5' |3.9
|style='background: #F5FFF5' |19
|-
|style='background: #FFF5FA' | WRSM-Pitman
|style='background: #FFF5FA' | 3.6
|style='background: #FFF5FA' |3.5
|style='background: #FFF5FA' |3.5
|style='background: #FFF5FA' |14
|-
|style='background: #FFF7F5' | SPATSIM-Pitman
|style='background: #FFF7F5' | 3.3
|style='background: #FFF7F5' |3.3
|style='background: #FFF7F5' |3.5
|style='background: #FFF7F5' |11
|-
|style='background: #FFFFF5' | SWAT
|style='background: #FFFFF5' | 3.6
|style='background: #FFFFF5' |3.9
|style='background: #FFFFF5' |3.8
|style='background: #FFFFF5' |9
|-
|style='background: #F5FCFF' | MIKE-SHE
|style='background: #F5FCFF' | 3.0
|style='background: #F5FCFF' |2.1
|style='background: #F5FCFF' |2.3
|style='background: #F5FCFF' |7
|-
|WEAP
|3.4
|3.9
|4.0
|7
|-
|SCS-SA
|3.5
|3.7
|3.4
|4
|-
|WRYM
|3.7
|4.0
|4.0
|3
|-
|HYDRUS
|1.5
|2.5
|2.5
|2
|}

Modelling tool documentation

2023-12-04T08:19:25Z

Julia Glenday:

This is the page has links to modelling tool websites, manuals and software downloads.

If you notice that we are missing any manual or key document, please let us know by using the "Discussion" page (see tab above), so that we can keep this page up to date. Assistance on posting to Discussion pages can be found [[How to use "Discussion" pages |here]].

<big>'''Need more help?'''</big>
If you have modelling questions that you cannot resolve by consulting the modelling tool's manual or related resources, we recommend trying the question and answer platform [https://earthscience.stackexchange.com Stack Exchange, Earth Sciences subsite], to look for help (tag question with "hydrology" and "model"). If you have gained experience using a tool, consider using Stack Exchange to provide help to others so that the questions and answers become freely available to anyone online. 
Guidance on using this resource for hydrological modelling assistance can be found [[Stack Exchange Question & Answer platform |here]].

== ACRU ==

'''Homepage:''' https://cwrr.ukzn.ac.za/resources/acru/

'''Manuals:''' http://www.beeh.unp.ac.za/acru

'''Support:''' Via email: https://cwrr.ukzn.ac.za/centre-staff/

'''Downloads:''' https://cwrr.ukzn.ac.za/resources/acru/

== WRSM-Pitman ==

'''Homepage:''' https://waterresourceswr2012.co.za/

'''Manuals:''' 
User manual: http://wrcwebsite.azurewebsites.net/wp-content/uploads/mdocs/TT%20689-16.pdf 
Code manual: http://www.wrc.org.za/wp-content/uploads/mdocs/TT%20691-16.pdf 
Theory manual: http://www.wrc.org.za/wp-content/uploads/mdocs/TT%20690-16.pdf

'''Support:''' https://waterresourceswr2012.co.za/contact/

'''Downloads:''' WRSM software & Water Resources 2012 (WR2012) study data downloads, log-in creation required: https://waterresourceswr2012.co.za/

== SPATSIM-Pitman ==

'''Homepage:''' https://www.ru.ac.za/iwr/research/software/spatsim/

'''Manuals:'''

'''Support:''' Via email: https://www.ru.ac.za/iwr/contactus/

'''Downloads:''' https://www.ru.ac.za/iwr/research/software/spatsim/

== SWAT ==

'''Homepage:''' https://swat.tamu.edu/

'''Manuals:''' https://swat.tamu.edu/docs/

'''Support:''' SWAT forums & link to contact developers: https://swat.tamu.edu/support/. Each forum is a google group.

'''Downloads:''' https://swat.tamu.edu/software/

== MIKE-SHE ==

'''Homepage:''' https://www.mikepoweredbydhi.com/

'''Manuals:''' 
General: https://www.mikepoweredbydhi.com/download/product-documentation 
MIKE-SHE: https://manuals.mikepoweredbydhi.help/2020/MIKE_SHE.htm

'''Support:''' 
MIKE support info page (links to the user forum): https://www.mikepoweredbydhi.com/support 
User forum index: https://52.136.242.250/ 
MIKE-SHE specific forum: https://52.136.242.250/index.php/board,33.0.html

'''Downloads:''' https://www.mikepoweredbydhi.com/download/mike-2021

Water balance outputs across tools

2023-12-04T07:37:50Z

Julia Glenday:

Modelling tools differ in the hydrological processes, or water balance elements (fluxes and storages), that they calculate individually, save, and allow users to export for further analyses. The table below covers what each software tool outputs, meaning what can be saved as a timeseries of flow rates, fluxes, or storage volumes or depths, and for what ''spatial scale'' or modelled units these can be output (e.g. output for each grid cell, HRU, subcatchment, or catchment total). Output file formats are covered [[Modelling tool user interfaces#Formats of input and output data|here]].

The spatial scales at which the software can output values gives an indication of how much external calculation work a user may need to do in order to find out about a flux or store of particular interest. For example, we often wish to know the ET water use of a particular vegetation type, likely to compare with another type. ACRU and SWAT will output AET components for individual HRUs, however if there are multiple HRUs of the same land cover type within the model type, these tools will not compile an area-weighted average for the cover type across the whole modelled area. The user would need to do that manually outside the tool using the individual HRU outputs. MIKE-SHE can do this compilation within the software as the user can specify a polygon that covers the full area of a cover class and the tool will compile fluxes for that polygon.

'''Note:''' The table differentiates between the case in which a ''tool does not output'' its calculation of a certain flux or storage (Output = "no") and the case in which the ''tool does not explicitly model'' the listed process ("not modelled"), meaning it's not part of the model's calculations. In the case when a tool ''does model'' a process, but ''does not output'' the results of this calculation, the user could potentially consult the tools' user guide and attempt to calculate the process themselves using the algorithm that is applied in the software and other components that can be output. In cases where a calculation would be relatively simple, and based only on other outputs covered in the table, the calculation approach has been given in the table.
For cases where the tool does output a flux but uses a different name for it that has been used in the table row heading, this has been noted in brackets below. For more terminology comparison across tools, see further coverage [[Terminology#Hydrological process and parameter terms across tools|here]]. 
Some of the fluxes listed in the table are net totals of component fluxes which are also listed in the table (e.g. total AET or total evaporation & transpiration = canopy interception evaporation + AET from soil + AET from GW + evaporation off water bodies, where applicable). Some tools model and output each separately and may or may not output each individually. Some provide outputs of the total and the components, some just the components and the user would need to sum them if the total was of interest. Some calculate a total of some or all in a single step and output the total.

{| class="wikitable"
! scope="col" style="width:15em" colspan="2" rowspan="2" |Flux or storage
! colspan="6" | '''Tool output and/or calculation approach'''
|-
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman (Sami GW)
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman (Hughes GW)
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed,more conceptual]]
! scope="col" style="background: #CEDAF2; width:8em" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed,more physical]]

|-
| rowspan="2"; style="vertical-align: top; width:10em "|'''AET total'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top" |<center>no *</center>
'''''calculate:'''''
''precip – runoff 
''– Δ soil storage 
''– Δ GW storage 
''(works for long-term average, not monthly due to recharge lag)
| style="background: #FFF7F5; vertical-align: top" | <center>no *</center>
'''''calculate:''''' 
''ET output (includes canopy interception)
''+ AET from GW (external calculation)''
| style="background: #F5FFF5; vertical-align: top" | <center>no *</center>
'''''calculate:''''' 
''canopy evap. 
''+ AET from soil''
| style="background: #FFFFF5; vertical-align: top" | <center>no *</center>
'''''calculate:'''''
''AET from soil 
''+ AET from GW''
| style="background: #F5FCFF; vertical-align: top; text-align:center;" | '''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" | '''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | ''(runoff module)''
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | ''(subcatchment)''
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | ''(HRU)''
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | ''(HRU)''
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Canopy interception evaporation'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" | no<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style=" vertical-align: center; text-align:top;" | <center>not modelled <big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| vertical-align: top; text-align:center;” | 
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''AET from soil'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" | no<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''AET from GW'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" | no<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" | no<big></big>
| style="vertical-align: top; text-align:center;" | not modelled<big></big> 
''(exception: [[Process representation across tools#Evapotranspiration (ET) from groundwater (GW)|riparian HRU approximation]]) ''
| style="background: #FFFFF5; vertical-align: top; text-align:center;" | '''YES'''<big></big>(‘Revap’)
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | 
| style="vertical-align: top; text-align:center;" |
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment aquifer, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|-
| rowspan="2"; style="vertical-align: top"|'''Evaporation from surface water body'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” |
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | water body
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | water body
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | water body (includes river reaches)
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | water body (includes river reaches), surface ponding: grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | water body (includes river reaches), surface ponding: grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Runoff (RO) total'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module, route (any scale)
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | river cross section
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | river cross section
|-
| rowspan="2"; style="vertical-align: top"|'''Surface runoff'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top;" | <center>no *</center>
'''''calculate:''''' 
''RO total – interflow – aquifer RO''
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top;" | <center>no *</center>
'''''calculate:''''' 
'' “Quickflow” – “DelayedStormflow” ''
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Interflow'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(‘soil moisture runoff’)
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(‘DelayedStormflow’)
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(‘Lateral Q’)
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>(saturated zone, upper layer)
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment interflow reservoir
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Aquifer to channel'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment aquifer, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|-
| rowspan="2"; style="vertical-align: top"|'''Channel to aquifer'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style= "vertical-align: top; text-align:center;" | not modelled
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |no
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | river module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: "vertical-align: top; text-align:center;” |
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | ''channel to "bank store", not output, need to back-calculate for reach
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | river reach
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | river reach; grid cell, polygon, catchment (aquifer layer)
|-
| rowspan="2"; style="vertical-align: top"|'''Aquifer GW flow, into or out of a model unit, remaining as GW'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |no<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="vertical-align: top; text-align:center;" |not modelled<big></big>
| style="background: #FFFFF5; vertical-align: top;" |<center>no *</center><big></big>
''GW can ‘leave’ catchment by recharging an inactive deep aquifer''
| style="background: #F5FCFF; vertical-align: top;" |<center>no *</center><big></big>
''GW can ‘leave’ catchment by recharging an inactive deep aquifer or ‘dead storage’ ''
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | 
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="vertical-align: top; text-align:center;” | 
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | (subcatchment)
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | (subcatchment)
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|-
| rowspan="2"; style="vertical-align: top"|'''Water body storage'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” |
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | water body
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | water body
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | water body
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | water body, surface ponding: grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | water body, surface ponding: grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Soil profile storage'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | soil layer in HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Aquifer storage'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |no<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment aquifer, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|-
| rowspan="2"; style="vertical-align: top"|'''Percolation out of soil storage'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>(‘total recharge’ - lagged to aquifer, excess becomes interflow)
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(same as aquifer recharge below)
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(same as aquifer recharge below)
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(lagged to aquifer)
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>(goes to 'interflow store')
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>(same as aquifer recharge below)
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Aquifer recharge'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>(‘aquifer recharge’)
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(B-horizon soil ‘SaturatedFlow’ + ‘UnsaturatedFlow’)
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment aquifer, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|}

Water balance outputs across tools

2023-12-04T06:50:06Z

Julia Glenday:

Modelling tools differ in the hydrological processes, or water balance elements (fluxes and storages), that they calculate individually, save, and allow users to export for further analyses. The table below covers what each software tool outputs, meaning what can be saved as a timeseries of flow rates, fluxes, or storage volumes or depths, and for what ''spatial scale'' or modelled units these can be output. Output file formats are cover [[Modelling tool user interfaces#Formats of input and output data|here]].

'''Note:''' The table differentiates between the case in which a tool does not output its calculation of a certain flux or storage (Output = "no") and the case in which the tool does not explicitly model or calculate the listed process ("not modelled"). In the case when a tool does model a process, but does not output the results of this particular calculation, the user could potentially consult the tools' user guide and attempt to calculate the process themselves using the algorithm that is applied in the software and other components that can be output. In cases where a calculation would be relatively simple, and based only on other outputs covered in the table, the calculation approach has been given in the table.
For cases where the tool does output a flux but uses a different name for it that has been used in the table row heading, this has been noted in brackets below. For more terminology comparison across tools, see further coverage [[Terminology#Hydrological process and parameter terms across tools|here]].

{| class="wikitable"
! scope="col" style="width:15em" colspan="2" rowspan="2" |Flux or storage
! colspan="6" | '''Tool output and/or calculation approach'''
|-
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman (Sami GW)
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman (Hughes GW)
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed,more conceptual]]
! scope="col" style="background: #CEDAF2; width:8em" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed,more physical]]

|-
| rowspan="2"; style="vertical-align: top; width:10em "|'''AET total'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top" |<center>no *</center>
'''''calculate:'''''
''precip – runoff 
''– Δ soil storage 
''– Δ GW storage 
''(works for long-term average, not monthly due to recharge lag)
| style="background: #FFF7F5; vertical-align: top" | <center>no *</center>
'''''calculate:''''' 
''ET output (includes canopy interception)
''+ AET from GW (external calculation)''
| style="background: #F5FFF5; vertical-align: top" | <center>no *</center>
'''''calculate:''''' 
''canopy evap. 
''+ AET from soil''
| style="background: #FFFFF5; vertical-align: top" | <center>no *</center>
'''''calculate:'''''
''AET from soil 
''+ AET from GW''
| style="background: #F5FCFF; vertical-align: top; text-align:center;" | '''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" | '''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | ''(runoff module)''
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | ''(subcatchment)''
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | ''(HRU)''
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | ''(HRU)''
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Canopy interception evaporation'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" | no<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style=" vertical-align: center; text-align:top;" | <center>not modelled <big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| vertical-align: top; text-align:center;” | 
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''AET from soil'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" | no<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''AET from GW'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" | no<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" | no<big></big>
| style="vertical-align: top; text-align:center;" | not modelled<big></big> 
''(exception: [[Process representation across tools#Evapotranspiration (ET) from groundwater (GW)|riparian HRU approximation]]) ''
| style="background: #FFFFF5; vertical-align: top; text-align:center;" | '''YES'''<big></big>(‘Revap’)
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | 
| style="vertical-align: top; text-align:center;" |
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment aquifer, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|-
| rowspan="2"; style="vertical-align: top"|'''Runoff (RO) total'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module, route (any scale)
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | river cross section
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | river cross section
|-
| rowspan="2"; style="vertical-align: top"|'''Surface runoff'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top;" | <center>no *</center>
'''''calculate:''''' 
''RO total – interflow – aquifer RO''
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top;" | <center>no *</center>
'''''calculate:''''' 
'' “Quickflow” – “DelayedStormflow” ''
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Interflow'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(‘soil moisture runoff’)
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(‘DelayedStormflow’)
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(‘Lateral Q’)
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>(saturated zone, upper layer)
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment interflow reservoir
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Aquifer to channel'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment aquifer, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|-
| rowspan="2"; style="vertical-align: top"|'''Aquifer GW flow in/out'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |no<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="vertical-align: top; text-align:center;" |not modelled<big></big>
| style="background: #FFFFF5; vertical-align: top;" |<center>no *</center><big></big>
''GW can ‘leave’ catchment by recharging an inactive deep aquifer''
| style="background: #F5FCFF; vertical-align: top;" |<center>no *</center><big></big>
''GW can ‘leave’ catchment by recharging an inactive deep aquifer or ‘dead storage’ ''
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | 
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="vertical-align: top; text-align:center;” | 
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | (subcatchment)
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | (subcatchment)
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|-
| rowspan="2"; style="vertical-align: top"|'''Soil profile storage'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | soil layer in HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Aquifer storage'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |no<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment aquifer, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|-
| rowspan="2"; style="vertical-align: top"|'''Percolation out of soil storage'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>(‘total recharge’)
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(same as recharge)
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(same as recharge)
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Aquifer recharge'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>(‘aquifer recharge’)
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(B-horizon soil ‘SaturatedFlow’ + ‘UnsaturatedFlow’)
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment aquifer, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|}

Water balance outputs across tools

2023-12-03T20:35:43Z

Julia Glenday:

Modelling tools differ in the hydrological processes, or water balance elements (fluxes and storages), that they calculate individually, save, and allow users to export for further analyses. The table below covers what each software tool outputs, meaning what can be saved as a timeseries of flow rates, fluxes, or storage volumes or depths, and for what ''spatial scale'' or modelled units these can be output. Output file formats are cover [[Modelling tool user interfaces#Formats of input and output data|here]].

'''Note:''' The table differentiates between the case in which a tool does not output its calculation of a certain flux or storage (Output = "no") and the case in which the tool does not explicitly model or calculate the listed process ("not modelled"). In the case when a tool does model a process, but does not output the results of this particular calculation, the user could potentially consult the tools' user guide and attempt to calculate the process themselves using the algorithm that is applied in the software and other components that can be output. In cases where a calculation would be relatively simple, and based only on other outputs covered in the table, the calculation approach has been given in the table.
For cases where the tool does output a flux but uses a different name for it that has been used in the table row heading, this has been noted in brackets below. For more terminology comparison across tools, see further coverage [[Terminology#Hydrological process and parameter terms across tools|here]].

{| class="wikitable"
! scope="col" style="width:15em" colspan="2" rowspan="2" |Flux or storage
! colspan="6" | '''Tool output and/or calculation approach'''
|-
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman (Sami GW)
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman (Hughes GW)
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed,more conceptual]]
! scope="col" style="background: #CEDAF2; width:8em" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed,more physical]]

|-
| rowspan="2"; style="vertical-align: top; width:10em "|'''AET total'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top" |<center>no *</center>
'''''calculate:'''''
''precip – runoff 
''– Δ soil storage 
''– Δ GW storage 
''(works for long-term average, not monthly due to recharge lag)
| style="background: #FFF7F5; vertical-align: top" | <center>no *</center>
'''''calculate:''''' 
''ET output (includes canopy interception)
''+ AET from GW (external calculation)''
| style="background: #F5FFF5; vertical-align: top" | <center>no *</center>
'''''calculate:''''' 
''canopy evap. 
''+ AET from soil''
| style="background: #FFFFF5; vertical-align: top" | <center>no *</center>
'''''calculate:'''''
''AET from soil 
''+ AET from GW''
| style="background: #F5FCFF; vertical-align: top; text-align:center;" | '''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" | '''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | ''(runoff module)''
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | ''(subcatchment)''
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | ''(HRU)''
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | ''(HRU)''
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Canopy interception evaporation'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" | no<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style=" vertical-align: center; text-align:top;" | <center>not modelled <big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| vertical-align: top; text-align:center;” | 
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''AET from soil'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" | no<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''AET from GW'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" | no<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" | no<big></big>
| style="vertical-align: top; text-align:center;" | not modelled<big></big> 
''(exception: [[Process representation across tools#Evapotranspiration (ET) from groundwater (GW)|riparian HRU approximation]]) ''
| style="background: #FFFFF5; vertical-align: top; text-align:center;" | '''YES'''<big></big>(‘Revap’)
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | 
| style="vertical-align: top; text-align:center;" |
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment aquifer, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|-
| rowspan="2"; style="vertical-align: top"|'''Runoff (RO) total'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module, route (any scale)
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | river cross section
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | river cross section
|-
| rowspan="2"; style="vertical-align: top"|'''Surface runoff'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top;" | <center>no *</center>
'''''calculate:''''' 
''RO total – interflow – aquifer RO''
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top;" | <center>no *</center>
'''''calculate:''''' 
'' “Quickflow” – “DelayedStormflow” ''
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Interflow'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(‘soil moisture runoff’)
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(‘DelayedStormflow’)
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(‘Lateral Q’)
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>(saturated zone, upper layer)
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment interflow reservoir
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Aquifer to channel'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment aquifer, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|-
| rowspan="2"; style="vertical-align: top"|'''Aquifer GW flow in/out'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |no<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="vertical-align: top; text-align:center;" |not modelled<big></big>
| style="background: #FFFFF5; vertical-align: top;" |<center>no *</center><big></big>
''GW can ‘leave’ catchment by recharging an inactive deep aquifer''
| style="background: #F5FCFF; vertical-align: top;" |<center>no *</center><big></big>
''GW can ‘leave’ catchment by recharging an inactive deep aquifer or ‘dead storage’ ''
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | 
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="vertical-align: top; text-align:center;” | 
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | (subcatchment)
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | (subcatchment)
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|-
| rowspan="2"; style="vertical-align: top"|'''Soil profile storage'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | soil layer in HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Aquifer storage'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |no<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment aquifer, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|-
| rowspan="2"; style="vertical-align: top"|'''Percolation out of soil storage'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>(‘total recharge’)
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(same as recharge)
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(same as recharge)
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Aquifer recharge'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>(‘aquifer recharge’)
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(B-horizon soil ‘SaturatedFlow’ + ‘UnsaturatedFlow’)
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment aquifer, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|}

Water balance outputs across tools

2023-12-03T20:16:30Z

Julia Glenday:

Modelling tools differ in the hydrological processes, or water balance elements, that they calculate individually, save, and allow users to export for further analyses.

{| class="wikitable"
! scope="col" style="width:15em" colspan="2" rowspan="2" |Flux or storage
! colspan="6" | '''Tool output and/or calculation approach'''
|-
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman (Sami GW)
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman (Hughes GW)
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed,more conceptual]]
! scope="col" style="background: #CEDAF2; width:8em" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed,more physical]]

|-
| rowspan="2"; style="vertical-align: top; width:10em "|'''AET total'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top" |<center>no *</center>
'''''calculate:'''''
''precip – runoff 
''– Δ soil storage 
''– Δ GW storage 
''(works for long-term average, not monthly due to recharge lag)
| style="background: #FFF7F5; vertical-align: top" | <center>no *</center>
'''''calculate:''''' 
''ET output (includes canopy interception)
''+ AET from GW (external calculation)''
| style="background: #F5FFF5; vertical-align: top" | <center>no *</center>
'''''calculate:''''' 
''canopy evap. 
''+ AET from soil''
| style="background: #FFFFF5; vertical-align: top" | <center>no *</center>
'''''calculate:'''''
''AET from soil 
''+ AET from GW''
| style="background: #F5FCFF; vertical-align: top; text-align:center;" | '''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" | '''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | ''(runoff module)''
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | ''(subcatchment)''
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | ''(HRU)''
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | ''(HRU)''
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Canopy interception evaporation'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" | no<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style=" vertical-align: center; text-align:top;" | not modelled <big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| vertical-align: top; text-align:center;” | 
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''AET from soil'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" | no<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''AET from GW'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" | no<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" | no<big></big>
| style="vertical-align: top; text-align:center;" | not modelled<big></big> 
''(exception: [[Process representation across tools#Evapotranspiration (ET) from groundwater (GW)|riparian HRU approximation]]) ''
| style="background: #FFFFF5; vertical-align: top; text-align:center;" | '''YES'''<big></big>(‘Revap’)
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | 
| style="vertical-align: top; text-align:center;" |
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment aquifer, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|-
| rowspan="2"; style="vertical-align: top"|'''Runoff (RO) total'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module, route (any scale)
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | river cross section
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | river cross section
|-
| rowspan="2"; style="vertical-align: top"|'''Surface runoff'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top;" | <center>no *</center>
'''''calculate:''''' 
''RO total – interflow – aquifer RO''
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top;" | <center>no *</center>
'''''calculate:''''' 
'' “Quickflow” – “DelayedStormflow” ''
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Interflow'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(‘soil moisture runoff’)
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(‘DelayedStormflow’)
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(‘Lateral Q’)
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>(saturated zone, upper layer)
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment interflow reservoir
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Aquifer to channel'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment aquifer, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|-
| rowspan="2"; style="vertical-align: top"|'''Aquifer GW flow in/out'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |no<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="vertical-align: top; text-align:center;" |not modelled<big></big>
| style="background: #FFFFF5; vertical-align: top;" |<center>no *</center><big></big>
''GW can ‘leave’ catchment by recharging an inactive deep aquifer''
| style="background: #F5FCFF; vertical-align: top;" |<center>no *</center><big></big>
''GW can ‘leave’ catchment by recharging an inactive deep aquifer or ‘dead storage’ ''
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | 
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="vertical-align: top; text-align:center;” | 
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | (subcatchment)
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | (subcatchment)
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|-
| rowspan="2"; style="vertical-align: top"|'''Soil profile storage'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | soil layer in HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Aquifer storage'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |no<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment aquifer, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|-
| rowspan="2"; style="vertical-align: top"|'''Percolation out of soil storage'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>(‘total recharge’)
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(same as recharge)
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(same as recharge)
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Aquifer recharge'''
| style="vertical-align: top" | ''Output''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''<big></big>(‘aquifer recharge’)
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>(B-horizon soil ‘SaturatedFlow’ + ‘UnsaturatedFlow’)
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''<big></big>
|-
| style="vertical-align: top" | ''Scale''<big></big>
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment aquifer, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|}

Water balance outputs across tools

2023-12-01T15:38:41Z

Julia Glenday:

Modelling tools differ in the hydrological processes, or water balance elements, that they calculate individually, save, and allow users to export for further analyses.

{| class="wikitable"
! scope="col" style="width:15em" colspan="2" rowspan="2" |Flux or storage
! colspan="6" | '''Tool output and/or calculation approach'''
|-
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman (Sami GW)
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman (Hughes GW)
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed,more conceptual]]
! scope="col" style="background: #CEDAF2; width:8em" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed,more physical]]

|-
| rowspan="2"; style="vertical-align: top; width:10em "|'''AET total'''
| style="vertical-align: top" | ''Output''
| style="background: #FFF5FA; vertical-align: top" | no*
'''''calculate:''''' 
''(long term average, not monthly due to lags):
''precip – runoff 
''– Δ soil storage 
''– Δ GW storage
| style="background: #FFF7F5; vertical-align: top" | no*
'''''calculate:''''' 
''ET output (includes canopy interception)
''+ AET from GW (external calculation)''
| style="background: #F5FFF5; vertical-align: top" | no*
'''''calculate:''''' 
''canopy evap. 
''+ AET from soil''
| style="background: #FFFFF5; vertical-align: top" | no*
'''''calculate:'''''
''AET from soil 
''+ AET from GW''
| style="background: #F5FCFF; vertical-align: top; text-align:center;" | '''YES'''
| style="background: #F5F8FF; vertical-align: top; text-align:center;" | '''YES'''
|-
| style="vertical-align: top" | ''Scale''
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | ''(runoff module)''
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | ''(subcatchment)''
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | ''(HRU)''
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | ''(HRU)''
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Canopy interception evaporation'''
| style="vertical-align: top" | ''Output''
| style="background: #FFF5FA; vertical-align: top; text-align:center;" | no#
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''
| style=" vertical-align: top; text-align:center;" | not modelled
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''
|-
| style="vertical-align: top" | ''Scale''
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| vertical-align: top; text-align:center;” | 
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''AET from soil'''
| style="vertical-align: top" | ''Output''
| style="background: #FFF5FA; vertical-align: top; text-align:center;" | no#
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''
|-
| style="vertical-align: top" | ''Scale''
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''AET from GW'''
| style="vertical-align: top" | ''Output''
| style="background: #FFF5FA; vertical-align: top; text-align:center;" | no#
| style="background: #FFF7F5; vertical-align: top;" | no*
'''''calculate:''''' 
''see algorithm''
| style="vertical-align: top; text-align:center;" | not modelled 
'' (exception: riparian HRU approximation) ''
| style="background: #FFFFF5; vertical-align: top; text-align:center;" | '''YES'''
(‘Revap’)
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''
|-
| style="vertical-align: top" | ''Scale''
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | ''(subcatchment)''
| style="vertical-align: top; text-align:center;" |
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment aquifer, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|-
| rowspan="2"; style="vertical-align: top"|'''Runoff (RO) total'''
| style="vertical-align: top" | ''Output''
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''
|-
| style="vertical-align: top" | ''Scale''
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module, route (any scale)
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | river cross section
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | river cross section
|-
| rowspan="2"; style="vertical-align: top"|'''Surface runoff'''
| style="vertical-align: top" | ''Output''
| style="background: #FFF5FA; vertical-align: top;" | no*
'''''calculate:''''' 
''RO total – interflow – aquifer RO''
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5FFF5; vertical-align: top;" | no*
'''''calculate:''''' 
'' “Quickflow” – “DelayedStormflow” ''
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''
|-
| style="vertical-align: top" | ''Scale''
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Interflow'''
| style="vertical-align: top" | ''Output''
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''
(‘soil moisture runoff’)
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''
(‘DelayedStormflow’)
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''
(‘Lateral Q’)
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''
(saturated zone, upper layer)
|-
| style="vertical-align: top" | ''Scale''
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment interflow reservoir
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Aquifer to channel'''
| style="vertical-align: top" | ''Output''
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''
|-
| style="vertical-align: top" | ''Scale''
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment aquifer, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|-
| rowspan="2"; style="vertical-align: top"|'''Aquifer GW flow in/out'''
| style="vertical-align: top" | ''Output''
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''
| style="vertical-align: top; text-align:center;" |not modelled
| style="background: #FFFFF5; vertical-align: top;" |no*
''GW can ‘leave’ catchment by recharging an inactive deep aquifer''
| style="background: #F5FCFF; vertical-align: top;" |no*
''GW can ‘leave’ catchment by recharging an inactive deep aquifer or ‘dead storage’ ''
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''
|-
| style="vertical-align: top" | ''Scale''
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | 
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="vertical-align: top; text-align:center;” | 
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | 
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | 
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|-
| rowspan="2"; style="vertical-align: top"|'''Soil profile storage'''
| style="vertical-align: top" | ''Output''
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''
|-
| style="vertical-align: top" | ''Scale''
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | soil layer in HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment, catchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment

|-
| rowspan="2"; style="vertical-align: top"|'''Aquifer storage'''
| style="vertical-align: top" | ''Output''
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''

|-
| style="vertical-align: top" | ''Scale''
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment aquifer, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|-
| rowspan="2"; style="vertical-align: top"|'''Percolation out of soil storage'''
| style="vertical-align: top" | ''Output''
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''
(‘total recharge’)
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''
(same as recharge)
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''
(same as recharge)
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''
|-
| style="vertical-align: top" | ''Scale''
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment
|-
| rowspan="2"; style="vertical-align: top"|'''Aquifer recharge'''
| style="vertical-align: top" | ''Output''
| style="background: #FFF5FA; vertical-align: top; text-align:center;" |'''YES'''
(‘aquifer recharge’)
| style="background: #FFF7F5; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5FFF5; vertical-align: top; text-align:center;" |'''YES'''
( ‘SaturatedFlow’ B horizon 
+ ‘UnsaturatedFlow’ 
if option to include is selected)
| style="background: #FFFFF5; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5FCFF; vertical-align: top; text-align:center;" |'''YES'''
| style="background: #F5F8FF; vertical-align: top; text-align:center;" |'''YES'''
|-
| style="vertical-align: top" | ''Scale''
| style="background: #FFF5FA; vertical-align: top; text-align:center;” | runoff module
| style="background: #FFF7F5; vertical-align: top; text-align:center;” | subcatchment
| style="background: #F5FFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #FFFFF5; vertical-align: top; text-align:center;” | HRU, subcatchment
| style="background: #F5FCFF; vertical-align: top; text-align:center;” | subcatchment aquifer, catchment
| style="background: #F5F8FF; vertical-align: top; text-align:center;” | grid cell, polygon, catchment, (aquifer layer or all)
|}

Modelling tool user interfaces

2023-12-01T15:27:33Z

Julia Glenday:

The tables below compare some main features of the user interfaces of the selected modelling tools that relate to their ease of use. These include approximate comparisons of typical model run times and the computing power needed to run them, as well as how easy it is to export and view various model outputs and test different parameter value options for sensitivity analyses and/or calibration.

The combination of how long it takes to set up a model (including preparing input data in the needed format, setting up the structure, entering the parameter values), how long it takes for the model to run, how long it takes to access model outputs of interest, and how long it takes to test and refine the model influences what can be achieved in the time that is available for a modelling project. Some modelling tools may run very quickly, but take a relatively long time to set up and don't have an efficient way to change and test multiple parameter value options, which makes calibration a time consuming, manual process. Other tools may take long to run, but can be set up to do a number of parameter testing runs and even scenario runs at once, allowing the modeller to attend to other work in the meantime (however they may have to do so on another computer if the model requires a lot of computing power!).

__TOC__



== Interface comparison overview ==

{| class="wikitable"
! scope="col" style="width:15em" | Interface characteristic <big></big>
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
|-
| style="vertical-align: vertical-align: center;" |Graphical user interface ''(vs code prompt)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Catchment map display (visualise linkages)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model run times'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Estimated model run time for a 30 year run, ~300km^2 catchment ''(Note: will depend on model set-up complexity & computing power!)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |tens of minutes
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |hours
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Computing resources needed'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Comparative rating of computing power needed to achieve workable run times.
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |light
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |light
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |light
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |medium
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |intensive (need good GPU)
|-
| colspan="6" style="background: #FFFFFF; vertical-align: vertical-align: center;" |'''Model set-up ease & efficiency'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Automated creation of model units & connections from map inputs ''(vs fully manual creation)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Input parameter values and change values for batches of models units ''(e.g., all HRUs of a cover type)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |In-built database of suggested parameter values ''(e.g., for common vegetation types, soil types, etc.)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |no
|-
| style="vertical-align: vertical-align: center;" |User can build own parameter databases for use across multiple models
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model set-up transparency''' (i.e., is it very obvious what the model is doing/assuming?) <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Interface makes the user interact with every component & parameter entry option during model set-up ''(vs having default parameter values pre-entered & not forcing user to view them)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |no
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Tool checks connection errors
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Batch runs & calibration tools''' <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Facility for batch runs, parameter sensitivity analyses, uncertainty analyses & auto-calibration
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Accessing model output''' <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for streamflow
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for water balance fluxes and stores
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |All water balance components that are calculated by the model can be exported
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Batch export of water balance fluxes for model's basic spatial units
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Automated extraction of water balance fluxes for different spatial scales ''(e.g., by cover class area, by subcatchment, full catchment)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|}


== Formats of input and output data ==

The table below gives some basic information about the file formats used for model inputs and outputs across the different modelling tools to give a general impression of what is required to work with them. This is a very rough overview and one has to work with user manuals, tutorials, and/or pre-exist demonstration models and data to understand the various formatting requirements and file types used across the inputs and outputs of a specific software tool. For large or complex model set-ups that will have many different inputs (e.g., different input rainfall timeseries for several different points across the modelled area), it is highly recommended to use coding tools like R or Python to prepare the input files as it will be time-consuming to get many files into the same specific formatting required by the modelling software and most do not have in-built conversion tools.

{| class="wikitable"
! scope="col" style="width:10%" |'''Data type''' <big></big>
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE
|-
| style="vertical-align: top;" |'''Timeseries data'''
| style="background: #FFF5FA; vertical-align: top; text-align: left;" |'''Specially formatted text files (special file extensions)'''
 Monthly data with years as rows and a column for each month in a water year starting in Oct, and for some types an annual sum in an additional column. Files can be read and generated by text editors (like Notepad) outside of WRSM, even though the files do not have typical text file extensions (e.g. ".txt"). WRSM input and output file extensions show the type of data (e.g., .RAN file is a rainfall timeseries file). Data can be brought into Excel for analyses, but it is difficult to create the input file formatting within Excel. A text editor or a general coding interface like an R or Python editor can be used to achieve the needed input data timeseries.
| style="background: #FFF7F5; vertical-align: top; text-align: left;" |'''Specially formatted text files (.txt)'''
 Some flexibility on the formatting for inputs as one can specify the row/column format and date formatting in the files in the tools' input interface. Inputs can be prepared in Excel and outputs easily opened there as well.
| style="background: #F5FFF5; vertical-align: top; text-align: left;" |'''Specially formatted ASCII text files (.txt) & .DBF files'''
 Input is daily data in long-format (one date per row) in a composite file containing climate variable and observed flow inputs in specified column orders and number formats. Difficult to prepare simply in Excel, and labour intensive to prepare in a text editor (e.g, Notepad), but reasonable to prepare in a general coding programme like R or Python. Outputs are .dbf format text files which open easily in Excel.
| style="background: #FFFFF5; vertical-align: top; text-align: left;" |'''Specially formatted text files (.txt) & Access database files '''
 Daily data in long-format (one date per row) text files. Reasonable to prepare and easy to open in Excel. Outputs can also be produced in an Access database.
| style="background: #F5FCFF; vertical-align: top; text-align: left;" |'''Software-specific .dfs0 file format'''
 Dfs0 files for input must be generated within MIKE software. Data in long-format (each row is a timestep) prepared in Excel can be copy-pasted into a blank dfs0 file with the correct number of rows and data from dfs0 files can be copy-pasted into Excel. There are also batch conversion tools in MIKE that can be used to convert specifically formatted text files into dfs0 files and to convert dfs0 files into text files.
|-
| style="vertical-align: top;" |'''Spatial data'''
| style="background: #FFF5FA; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of modules: what areas will have their own modules (e.g. subcatchment delineation; special cover types to represent separately, like plantations, irrigated areas, wetlands; river reaches and dams), determine sizes and other characteristics of the modules, and how they are linked to one another.''
| style="background: #FFF7F5; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments: subcatchment delineation plus special features to represent specifically like dams, plantations, irrigated areas, wetlands), determine the sizes and other characteristics of subcatchments and special areas, and how subcatchments are linked to one another.''
| style="background: #F5FFF5; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments composed of HRUs, river reaches, & dams: subcatchment delineation, what areas will have their own HRUs (land cover types to represent individually), determine the sizes and other characteristics of the HRUs, and how units linked to one another.''
| style="background: #FFFFF5; vertical-align: top; text-align:left;" |'''Standard GIS shapefile and grid/raster files (geotif, grid) used.'''
 DEM input must be a raster. Land cover and soil type data can be input as shapefiles or rasters (see user manuals for formatting/attribute requirements). Tool-delineated subcatchments, river lines, HRUs are output as shapefiles. Hydrological predictions are not output in a spatial format. The data can be linked back to spatial units based on ID numbers manually by the user for spatial displays. (SWAT+ has developed tools for this internally...)
| style="background: #F5FCFF; vertical-align: top; text-align:left;" |'''Software-specific .dfs2 and .dfs3 file formats used in general. A few inputs allow standard shapefiles.'''
 dfs2 files are 2D gridded data. Standard GIS grids can be saved in an ASCI format in GIS software and then a MIKE tool applied to convert to dfs2. Subcatchments and landcover can be input as shapefiles. Many hydrological predictions can be output as spatial data as .dfs3 files, 3 dimensional data "cubes": a 2D grid of values (e.g. transpiration, surface water depth, soil moisture, groundwater depth) for each timestep, all in one file. These can be stepped-through or played as video in the interface. Timeseries for point locations or specified areas can be extracted. .dfs2 files can be converted to ASCI files to open in GIS software using an in-built tool.
|}


== User impressions of 'ease-of-use' (modeller survey) ==
A brief survey for hydrological modellers was distributed via the South African Hydrology Society (SAHS) as part of the [[Model inter-comparison study|model intercomparison project (2019-2021)]]. Participants were asked to rank the ease-of-use of the software interface for any modelling tools they were familiar with on a scale of 1-5 in which: '''1=poor, 3=satisfactory, 5= excellent'''
There was a very wide range of scores assigned for each tool across the respondents, showing that different people experience the tools differently! 
Both the average and the range of scores assigned are presented below
{| class="wikitable"
! scope="col" style="width:15em" | Survey data <big></big>
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
|-
| style="vertical-align: vertical-align: center;" |''Number of users answering survey''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''13''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''14''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''19''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''9''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |''8''
|-
| style="vertical-align: vertical-align: center;" |'''Average ease-of-use score''' 1-poor to 5-excellent
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |3.8
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |3.4
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |3.4
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |3.9
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |3.0
|-
| style="vertical-align: vertical-align: center;" |'''Range of scores assigned''' 1-poor to 5-excellent
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |2 - 5
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |2 - 5
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |1 - 5
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |3 - 5
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |1 - 5
|}

Process representation across tools

2023-12-01T14:37:41Z

Julia Glenday:

The tables below summarise information about different process representation [[Terminology#algorithm anchor|algorithms]] across the set of modelling tools. They cover the inputs used to model the occurrence and rate (amount per model calculation timestep) of the given hydrological process (e.g. infiltration of water into the soil) as well as some general characteristics of the equations, particularly noting if there are thresholds involved and what these are. The tables can be used to understand what is being considered in the calculation of each process and what inputs each modelling tool needs. Not all the processes listed are represented explicitly by all the tools. This is highlighted in the tables below and an overview is also presented in the [[Modelling tool capability overview#Modelling tool capabilities summary|capabilities overview table]]. The nature of the algorithms used and their inputs are linked to the '''spatial and temporal scale''' at which the process is being represented in the given tool, described further for each one [[Model units & connections|here]].

In these tables '''thresholds''' refer to limits that determine when a process would start to occur or would stop occurring. For example, the field capacity soil moisture of a soil is often used as the threshold soil moisture level for percolation of water downwards (to a lower soil layer or to recharge groundwater). If soil moisture is lower than this, no percolation will be calculated in the model. There may be multiple thresholds considered when modelling a process. For example, evapotranspiration of soil moisture may be assumed to stop once the atmospheric demand in the timestep has been met or once the soil moisture has reached wilting point level, even if demand has not yet been met.

The inputs to a process algorithm can include:
* input data (e.g., rainfall, using the rainfall input for a particular modelled unit, for a given timestep),
* property parameter values that the user inputs in the model set-up (e.g., soil moisture content at saturation for a soil layer in a modelled unit)
* states or water storage levels that the model calculated internally for the timestep, so not directly input by the user (e.g., soil moisture content in a certain soil layer at a given timestep)
Different software tools may refer to equivalent inputs using different words and sometimes they require the user to input different specific property values, but end up calculating the same derived property. For example, on software tool may require porosity of soil to be input, another may require bulk density, and another may as for volumetric soil moisture at saturation, any of these, coupled with soil layer depth, can be used to calculate the maximum (or saturation) soil water storage volume. Where possible, similar terms have been used across tools in the tables below to highlight their conceptual similarities where these exist. Details about some of the contrasting terminology used in the interfaces of different tools can be found [[Terminology#Hydrological process and parameter terms across tools|here]].


== Canopy interception and evaporation (vs throughfall) ==
{| class="wikitable"
! scope="col" width:10%"| Algorithm description
! scope="col" style="background: #F2CEE0; width:18%" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:18%" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:18%" |ACRU4
! scope="col" style="background: #F2F2CE; width:18%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:18%" |MIKE-SHE, [[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed & fully distributed]]
|-
| style="vertical-align: top" | '''Algorithm inputs''' ''(input data, model calculated states / storages, property parameters)''
| style="background: #FFF5FA; vertical-align: top" |
 
* Rain
* '''''Cover properties:'''''
** max interception
 
| style="background: #FFF7F5; vertical-align: top" |
 
* Rain
* '''''Cover properties:'''''
** max interception
 
| style="background: #F5FFF5; vertical-align: top" |
 
* Rain
* PET
* Canopy storage ''(state)''
* '''''Cover properties:'''''
** max interception (OR LAI)
 
| style="background: #FFFFF5; vertical-align: top"; rowspan= "3" |
 '''Canopy interception is not explicitly modelled when using daily timestep modelling.''' 
''It is implicitly considered in the ‘initial abstraction’, see infiltration & surface runoff below''
| style="background: #F5FCFF; vertical-align: top" |
 
* Rain
* PET
* Canopy storage ''(state)''
* '''''Cover properties:'''''
**LAI
**canopy interception coefficient
 
|-
| style="vertical-align: top" |'''Function type'''
| style="background: #FFF5FA; vertical-align: top" |exponential & threshold
| style="background: #FFF7F5; vertical-align: top" |exponential & threshold
| style="background: #F5FFF5; vertical-align: top" |threshold
| style="background: #F5FCFF; vertical-align: top" |threshold
|-
| style="vertical-align: top" |'''Thresholds'''
| style="background: #FFF5FA; vertical-align: top" |
'''yes:'''
 
timestep interception capacity ''(calculated)''
| style="background: #FFF7F5; vertical-align: top" |
'''yes:'''
 
timestep interception capacity ''(calculated)''
| style="background: #F5FFF5; vertical-align: top" |
'''yes:'''
 
timestep interception capacity ''(calculated)''
| style="background: #F5FCFF; vertical-align: top" |
'''yes:'''
 
timestep interception capacity ''(calculated)''
|}
[[#Process rep - pg top|Back to top of page]]



== Infiltration into soil moisture (vs surface runoff or surface ponding) ==
'''Note:''' This excludes the case of a modelling unit (HRU, grid cell, area within a subcatchment, etc.) is designated as '''''impervious'''''. In this case, rain inputs would become surface runoff, potentially with a portion staying behind as surface storage/ponding if the area has attenuation specified (to represent roughness and flatness).
{| class="wikitable"
! scope="col" style="width:10%" | Algorithm description
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed, more conceptual]]
! scope="col" style="background: #CEDAF2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed, more physical]]
|-
| style="vertical-align: top" | '''Algorithm inputs''' ''(input data, model calculated states / storages, property parameters)''
| style="background: #FFF5FA; vertical-align: top" |
 
* Rain
* Rainfall distribution factor
* Soil moisture ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Infiltration rate distribution (min, max)
 
| style="background: #FFF7F5; vertical-align: top" |
 
* Rain
* Rainfall distribution factor
* Soil moisture ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Infiltration rate distribution (min, max)
 
| style="background: #F5FFF5; vertical-align: top" |
 
* Throughfall (rain-interception)
* Soil moisture within "infiltration depth"''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** "Infiltration depth" parameter
** Macropore by-pass (clay cracking)
 
| style="background: #FFFFF5; vertical-align: top"|
 
* Throughfall (rain-interception)
* Soil moisture ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Curve number (SCS-CN)
** Macropore by-pass
 
| style="background: #F5FCFF; vertical-align: top" |
 
* Throughfall (rain-interception)
* Soil moisture ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Saturated hydraulic conductivity (Ksat),
** Macropore by-pass
 
| style="background: #F5F8FF; vertical-align: top" |
 
* Throughfall (rain-interception)
* Soil moisture ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Soil moisture retention curve
** Saturated hydraulic conductivity (Ksat),
** Macropore by-pass
 
|-
| style="vertical-align: top" |'''Function type'''
| style="background: #FFF5FA; vertical-align: top" |non-linear & threshold
| style="background: #FFF7F5; vertical-align: top" |non-linear & threshold
| style="background: #F5FFF5; vertical-align: top" |power & threshold
| style="background: #FFFFF5; vertical-align: top" |power & threshold
| style="background: #F5FCFF; vertical-align: top" |linear (rate) & threshold
| style="background: #F5F8FF; vertical-align: top" |non-linear & threshold
|-
| style="vertical-align: top" |'''Thresholds'''
| style="background: #FFF5FA; vertical-align: top" |
'''yes:'''
 Max infiltration rate,
 Saturation soil moisture*
 *Saturation excess becomes interflow, not surface runoff
| style="background: #FFF7F5; vertical-align: top" |
'''yes:'''
 Max infiltration rate,
 Saturation soil moisture*
 *Saturation excess becomes interflow, not surface runoff
| style="background: #F5FFF5; vertical-align: top" |
'''yes:'''
 Saturation soil moisture*
 *Fraction of saturation excess becomes "delayed flow"~interflow, not "quickflow"~surface runoff
| style="background: #FFFFF5; vertical-align: top"|
'''yes:'''
 Max infiltration rate ''(calculated),''
 Saturation soil moisture
| style="background: #F5FCFF; vertical-align: top" |
'''yes:'''
 Max infiltration rate (uses Ksat),
 Saturation soil moisture
| style="background: #F5F8FF; vertical-align: top" |
'''yes:'''
 Max infiltration rate ''(calculated)'',
 Saturation soil moisture
|}
[[#Process rep - pg top|Back to top of page]]



== Surface runoff to channel network ==
'''Note on surface runoff vs ponding and surface storage:''' In the Pitman models, all water not calculated to infiltrate in a timestep, which is a month, is assumed to be runoff. For models with shorter timesteps, water reaching the land surface which does not infiltrate into soil in a timestep can become surface runoff or remain as surface ponding/surface storage. In subsequent model timesteps, water still on the land surface can evaporate, infiltrate, and/or become surface runoff in the next timestep. Some models have relatively short timesteps (subdaily, daily) compared to the rate at which water would move all the way across a modelled land unit (which could be large, rough, and/or flat, slowing the flow rate). This is why some water will be 'surface storage' in one timestep and then 'surface runoff' in the next timestep. MIKE-SHE can also consider that land surfaces can be very rough, or have dips that trap water, and so some amount surface water will not be able to run off at all (detention storage). This water will both evaporate and infiltrate over time.
 ACRU4 differs notably, assuming the water that does not infiltrate into soil accounts for both surface runoff and interflow runoff.
{| class="wikitable"
! scope="col" style="width:10%" | Algorithm description
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed, more conceptual]]
! scope="col" style="background: #CEDAF2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed, more physical]]
|-
| style="vertical-align: top" | '''Algorithm inputs''' ''(input data, model calculated states / storages, property parameters)''
| style="background: #FFF5FA; vertical-align: top" |
 
* Surface water present* ''(state)''
 
 *Month timestep: all water not infiltrating becomes runoff 
 
| style="background: #FFF7F5; vertical-align: top" |
 
* Surface water present* ''(state)''
 
 *Month timestep: all water not infiltrating becomes runoff 
 
| style="background: #F5FFF5; vertical-align: top" |
 
* Surface water present* ''(state)''
* Lag coefficient*
 
 *Lag coefficient separates "quickflow"~surface runoff from "delayed-flow"~interflow. Quickflow portion reaches the channel on the same day generated (rain day). The rest is lagged over subsequent days 
| style="background: #FFFFF5; vertical-align: top"|
 
* Surface water present* ''(state)''
* '''''Surface path properties:'''''
** Path length
** Slope
** Roughness (Manning's n)
 
| style="background: #F5FCFF; vertical-align: top" |
 
* Surface water present* ''(state)''
* '''''Surface path properties:'''''
** Detention storage
** Path length
** Slope
** Roughness (Manning's n)
 
| style="background: #F5F8FF; vertical-align: top" |
 
* Surface water present* ''(state)''
* '''''Surface path properties:'''''
** Detention storage
** Path length (from gridded topography)
** Slope(from gridded topography)
** Roughness (Manning's n)
 
|-
| style="vertical-align: top" |'''Function type'''
| style="background: #FFF5FA; vertical-align: top" |(no transformation)
| style="background: #FFF7F5; vertical-align: top" |(no transformation)
| style="background: #F5FFF5; vertical-align: top" |(no transformation)
| style="background: #FFFFF5; vertical-align: top" |non-linear
| style="background: #F5FCFF; vertical-align: top" |non-linear & threshold
| style="background: #F5F8FF; vertical-align: top" |non-linear & threshold
|-
| style="vertical-align: top" |'''Thresholds'''
| style="background: #FFF5FA; vertical-align: top" |
no*
 *none after infiltration has been calculated 
| style="background: #FFF7F5; vertical-align: top" |
no*
 *none after infiltration has been calculated 
| style="background: #F5FFF5; vertical-align: top" |
no*
 *none after infiltration has been calculated 
| style="background: #FFFFF5; vertical-align: top"|
no*
 *none after infiltration has been calculated 
| style="background: #F5FCFF; vertical-align: top" |
'''yes:'''
 Detention storage
| style="background: #F5F8FF; vertical-align: top" |
'''yes:'''
 Detention storage
|}
[[#Process rep - pg top|Back to top of page]]



== Evapotranspiration (ET) from soil moisture (SM) ==
'''Note: More coverage of evapotranspiration related terminology and inputs across different tools can be found [[Terminology#Evapotranspiration terms across tools|here]]'''
{| class="wikitable"
! scope="col" style="width:10%" | Algorithm description
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed, more conceptual]]
! scope="col" style="background: #CEDAF2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed, more physical]]
|-
| style="vertical-align: top" | '''Algorithm inputs''' ''(input data, model calculated states / storages, property parameters)''
| style="background: #FFF5FA; vertical-align: top" |
 
* S-Pan evaporation
* Soil moisture ''(state)''
* '''''Vegetation properties:'''''
** "Crop" coefficient (vs pan)
** Pitman ET coefficient*
* '''''Soil properties:'''''
** Saturation soil moisture
*determines linear decline of ET with soil moisture decline
 
| style="background: #FFF7F5; vertical-align: top" |
 
* S-Pan evaporation
* Soil moisture ''(state)''
* '''''Vegetation properties:'''''
** "Crop" coefficient (vs pan)
** Pitman ET coefficient*
* '''''Soil properties:'''''
** Saturation soil moisture
*determines linear decline of ET with soil moisture decline
 
| style="background: #F5FFF5; vertical-align: top" |
 
* A-Pan evaporation
* Soil moisture ''(state)''
* '''''Vegetation properties:'''''
** "Crop" coefficient (vs pan)
** Root depth distribution
* '''''Soil properties:'''''
** Saturation soil moisture*
** Field capacity SM
** Wilting point SM
*ET assumed to also decline if soil gets close to saturation, waterlogging, unless wetland plants
 
| style="background: #FFFFF5; vertical-align: top"|
 
* Remaining ET demand (PET - Canopy evap.)
* Soil moisture ''(state)''
* '''''Vegetation properties:'''''
** LAI
** Root depth (max)
** Root distribution
** Demand redistribution coefficient
* '''''Soil properties:'''''
** Field capacity SM
** Wilting point SM
 
| style="background: #F5FCFF; vertical-align: top" |
 
* Remaining ET demand (PET - Canopy evap. - Ponded evap.)
* Soil moisture ''(state)''
* '''''Vegetation properties:'''''
** "Crop" coefficient
** ET curtailment SM
** Root depth (max)
** Root distribution
* '''''Soil properties:'''''
** Field capacity SM
** Wilting point SM
 
| style="background: #F5F8FF; vertical-align: top" |
 
* Remaining ET demand (PET - Canopy evap. - Ponded evap.)
* Soil moisture ''(state)''
* '''''Vegetation properties:'''''
** "Crop" coefficient
** ET vs SM curve parameter
** Root depth (max)
** Root distribution
** ET demand depth distribution
* '''''Soil properties:'''''
** Soil moisture retention curve
 
|-
| style="vertical-align: top" |'''Function type'''
| style="background: #FFF5FA; vertical-align: top" |linear & threshold
| style="background: #FFF7F5; vertical-align: top" |linear & threshold
| style="background: #F5FFF5; vertical-align: top" |multi-part linear & threshold
| style="background: #FFFFF5; vertical-align: top" |non-linear & threshold
| style="background: #F5FCFF; vertical-align: top" |multi-part linear & threshold
| style="background: #F5F8FF; vertical-align: top" |non-linear & threshold
|-
| style="vertical-align: top" |'''Thresholds'''
| style="background: #FFF5FA; vertical-align: top" |
'''yes:'''
 ET demand,
 Wilting point SM
| style="background: #FFF7F5; vertical-align: top" |
'''yes:'''
 ET demand,
 Wilting point SM
| style="background: #F5FFF5; vertical-align: top" |
'''yes:'''
 ET demand,
 Wilting point SM
| style="background: #FFFFF5; vertical-align: top"|
'''yes:'''
 ET demand,
 Wilting point SM
| style="background: #F5FCFF; vertical-align: top" |
'''yes:'''
 ET demand,
 Wilting point SM
| style="background: #F5F8FF; vertical-align: top" |
'''yes:'''
 ET demand,
 Wilting point SM
|}
[[#Process rep - pg top|Back to top of page]]



== Evapotranspiration (ET) from groundwater (GW) ==
'''Note:''' More coverage of evapotranspiration related terminology and inputs across different tools can be found '''[[Terminology#Evapotranspiration terms across tools|here]]'''
{| class="wikitable"
! scope="col" style="width:10%" | Algorithm description
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman (Sami GW)
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman (Hughes GW)
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed, more conceptual]]
! scope="col" style="background: #CEDAF2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed, more physical]]
|-
| style="vertical-align: top" | '''Algorithm inputs''' ''(input data, model calculated states / storages, property parameters)''
| style="background: #FFF5FA; vertical-align: top" |
 
''riparian area only''
* A-Pan evaporation
* Riparian area
* Aquifer storage ''(state)''
* '''''Vegetation properties:'''''
** "Crop" coefficient (vs pan)
* '''''Aquifer properties:'''''
** Storage limit for ET
 
| style="background: #FFF7F5; vertical-align: top" |
 
''riparian area only''
* Remaining ET demand (PET - ET from soil)
* Riparian area
* Aquifer storage ''(state)''
* '''''Vegetation properties:'''''
** "Crop" coefficient (vs pan)
** Pitman ET coefficient*
* '''''Aquifer properties:'''''
** Storage limit for ET
 
| style="background: #F5FFF5; vertical-align: top" ; rowspan= "3" |
 
''riparian area only''
'''Indirect representation:'''
''Specified riparian zone HRU can receive a user-specified fraction of the aquifer outflow from connected upslope HRUs. This water is added to riparian HRU soil in the B-horizon, where it can be accessed for ET and can recharge GW.''
 ''No ET (or capillary rise) is simulated from the GW store of the riparian HRU.''
 
| style="background: #FFFFF5; vertical-align: top"|
 
''represented through capillary rise into the soil driven by ET demand''
* PET
* Aquifer storage ''(state)''
* '''''Soil properties:'''''
** Capillary rise rate coefficient
* '''''Aquifer properties:'''''
** Storage limit for capillary rise
''+ all inputs for ET from soil''
 
| style="background: #F5FCFF; vertical-align: top" |
 
''riparian area only''
 ''represented through capillary rise into the soil driven by ET demand''
* Remaining ET demand (PET - Canopy evap. - Ponded evap. - ET from soil)
* Aquifer storage ''(state)''
* '''''Aquifer properties:'''''
** Storage limit for capillary rise
''+ all inputs for [[#Evapotranspiration (ET) from soil moisture (SM)|ET from soil]]''
 
| style="background: #F5F8FF; vertical-align: top" |
 
''capillary rise is calculated, but roots can also extend below the water table and withdraw directly''
* Remaining ET demand (PET - Canopy evap. - Ponded evap. - ET from soil)
* Water table depth ''(state)''
* '''''Aquifer properties:'''''
** Saturated hydraulic conductivity (Ksat)
''+ vegetation property inputs for [[#Evapotranspiration (ET) from soil moisture (SM)|ET from soil]]''
 
|-
| style="vertical-align: top" |'''Function type'''
| style="background: #FFF5FA; vertical-align: top" |non-linear & threshold
| style="background: #FFF7F5; vertical-align: top" |non-linear & threshold
| style="background: #FFFFF5; vertical-align: top" |non-linear & threshold
| style="background: #F5FCFF; vertical-align: top" |non-linear & threshold
| style="background: #F5F8FF; vertical-align: top" |non-linear & threshold
|-
| style="vertical-align: top" |'''Thresholds'''
| style="background: #FFF5FA; vertical-align: top" |
'''yes:'''
 ET demand,
 Aquifer storage limit for ET
| style="background: #FFF7F5; vertical-align: top" |
'''yes:'''
 ET demand,
 Aquifer storage limit for ET
| style="background: #FFFFF5; vertical-align: top"|
'''yes:'''
 ET demand,
 Aquifer storage limit for capillary rise
| style="background: #F5FCFF; vertical-align: top" |
'''yes:'''
 ET demand,
 Aquifer storage limit for capillary rise
| style="background: #F5F8FF; vertical-align: top" |
'''yes:'''
 ET demand,
 Water table depth vs root depth
|}
[[#Process rep - pg top|Back to top of page]]



== Interflow generation & routing to channel network ==
{| class="wikitable"
! scope="col" style="width:10%" | Algorithm description
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed, more conceptual]]
! scope="col" style="background: #CEDAF2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed, more physical]]
|-
| style="vertical-align: top" | '''Algorithm inputs''' ''(input data, model calculated states / storages, property parameters)''
| style="background: #FFF5FA; vertical-align: top" |
 
''Interflow from soil layer & from "percolation zone"''
* Soil moisture ''(state)''
* Percolation zone storage ''(state)''
* Aquifer storage ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Field capacity SM
** Interflow rate power coefficient
** Max interflow rate
** Interflow lag coefficient
* '''''Percolation zone properties'''''
** Max storage capacity
* '''''Aquifer properties'''''
** Max storage capacity
 
| style="background: #FFF7F5; vertical-align: top" |
 
''Interflow from soil layer''
* Soil moisture ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Field capacity SM
** Interflow rate power coefficient
** Max interflow rate
** Interflow lag coefficient
 
| style="background: #F5FFF5; vertical-align: top"; rowspan= "3" |
 
'''Interflow amount calculated in the same step as surface runoff, not as a separate process:'''
''total surface runoff + interflow runoff is calculated in the [[#Infiltration into soil moisture (vs surface runoff or surface ponding)|infiltration]] vs [[#Surface runoff to channel network|runoff]] step, then these are separated through lagging''
* Surface water present* ''(state)''
* Lag coefficient*
 *Lag coefficient separates "quickflow"~surface runoff from "delayed-flow"~interflow. The lagged flow that doesn't reach the channel on the rain day, but instead reaches the channel over subsequent days can be considered interflow 
 
| style="background: #FFFFF5; vertical-align: top"|
 
''Interflow from soil layer''
* Soil moisture ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Field capacity SM
** Drainage slope
** Saturated hydraulic conductivity (Ksat)
 
| style="background: #F5FCFF; vertical-align: top" |
 
''Interflow from "interflow zone" (IZ)''
''to calc input into IZ:''
* Macropore flow (Throughfall * by-pass coefficient)
* Soil moisture ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Field capacity SM
** Drainage slope
** Saturated hydraulic conductivity (Ksat)
''to calc outflow from IZ:''
* IZ storage ''(state)''
* '''''IZ properties:'''''
** Storage threshold for outflow
** Lateral outflow rate constant
 
| style="background: #F5F8FF; vertical-align: top"; rowspan= "3" |
 
'''Interflow not modelled as a separate process to "saturated zone" flow.'''
 ''Lateral flow through a "saturated zone" material layer in the model which is not frequently saturated and/or is perched above more permanently saturated layers can be considered as interflow. Flows through different layers can be exported as separate model outputs.''

''See [[#Aquifer exchanges with channel: aquifer outflow to channel and channel transmission loss|groundwater outflow to channel]]''
 
|-
| style="vertical-align: top" |'''Function type'''
| style="background: #FFF5FA; vertical-align: top" |non-linear & threshold
| style="background: #FFF7F5; vertical-align: top" |non-linear & threshold
| style="background: #FFFFF5; vertical-align: top" |non-linear & threshold
| style="background: #F5FCFF; vertical-align: top" |two step: non-linear & threshold, linear reservoir & threshold
|-
| style="vertical-align: top" |'''Thresholds'''
| style="background: #FFF5FA; vertical-align: top" |
'''yes:'''
 Field capacity SM,
 Percolation zone max storage + Aquifer max storage
| style="background: #FFF7F5; vertical-align: top" |
'''yes:'''
 Field capacity SM
| style="background: #FFFFF5; vertical-align: top" |
'''yes:'''
 Field capacity SM
| style="background: #F5FCFF; vertical-align: top" |
'''yes:'''
 Field capacity SM
 IZ storage threshold for outflow
|}
[[#Process rep - pg top|Back to top of page]]



== Aquifer recharge ==
{| class="wikitable"
! scope="col" style="width:10%" | Algorithm description
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman(Sami GW)
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman(Hughes GW)
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed, more conceptual]]
! scope="col" style="background: #CEDAF2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed, more physical]]
|-
| style="vertical-align: top" | '''Algorithm inputs''' ''(input data, model calculated states / storages, property parameters)''
| style="background: #FFF5FA; vertical-align: top" |
 
''Recharge via "percolation zone" (vadose zone)''
* Soil moisture ''(state)''
* Vadose zone storage ''(state)''
* Aquifer storage ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Field capacity SM
** Percolation power coefficient
** Max percolation rate
*'''''Percolation zone properties:'''''
** Recharge lag coefficient
** Max storage capacity
*'''''Aquifer properties:'''''
** Max storage capacity
 
| style="background: #FFF7F5; vertical-align: top" |
 
''Recharge from soil column''
* Soil moisture ''(state)''
* Aquifer storage ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Field capacity SM
** Percolation power coefficient
** Max percolation rate
*'''''Aquifer properties:'''''
** Max storage capacity
 
| style="background: #F5FFF5; vertical-align: top" |
 
''Recharge from soil column*''
* Soil moisture ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Field capacity SM
** Percolation rate (~Ksat)
 
*Aquifer storage is unlimited
 
| style="background: #FFFFF5; vertical-align: top"|
 
''Recharge via vadose zone''
* Soil moisture ''(state)''
* Vadose zone storage ''(state)''
* Aquifer storage ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Field capacity SM
** Saturated hydraulic conductivity (Ksat)
*'''''Vadose zone (VZ) properties:'''''
** Field capacity
** Saturated hydraulic conductivity (Ksat)
*'''''Aquifer properties:'''''
** Max storage capacity
 
| style="background: #F5FCFF; vertical-align: top" |
 
''Recharge via "interflow zone"''
* Soil moisture ''(state)''
* Interflow zone storage ''(state)''
* Aquifer storage ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Field capacity SM
** Saturated hydraulic conductivity (Ksat)
*'''''Interflow zone (IZ) properties:'''''
**Storage threshold for outflow
**Vertical outflow rate constant
*'''''Aquifer properties:'''''
** Max storage capacity
 
| style="background: #F5F8FF; vertical-align: top" |
 
''Recharge from soil column''
* Soil moisture ''(state)''
* Aquifer storage ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Moisture retention curve
** Saturated hydraulic conductivity (Ksat)
*'''''Aquifer properties:'''''
** Max storage capacity
** Conductivity (Ksat)
 
|-
| style="vertical-align: top" |'''Function type'''
| style="background: #FFF5FA; vertical-align: top" |two step: non-linear & threshold, non-linear
| style="background: #FFF7F5; vertical-align: top" |non-linear & threshold
| style="background: #F5FFF5; vertical-align: top" |non-linear & threshold
| style="background: #FFFFF5; vertical-align: top" |two step: non-linear & threshold, non-linear & threshold
| style="background: #F5FCFF; vertical-align: top" |two step: non-linear & threshold, linear reservoir & threshold
| style="background: #F5F8FF; vertical-align: top" |non-linear & threshold
|-
| style="vertical-align: top" |'''Thresholds'''
| style="background: #FFF5FA; vertical-align: top" |
'''yes:'''
 Field capacity SM,
 Vadose zone max storage
 Aquifer max storage
| style="background: #FFF7F5; vertical-align: top" |
'''yes:'''
 Field capacity SM,
 Aquifer max storage
| style="background: #F5FFF5; vertical-align: top" |
'''yes:'''
 Field capacity SM
 
*Aquifer storage is unlimited
| style="background: #FFFFF5; vertical-align: top"|
'''yes:'''
 Field capacity SM,
 Vadose zone field capacity
 Aquifer max storage
| style="background: #F5FCFF; vertical-align: top" |
'''yes:'''
 Field capacity SM,
 Aquifer max storage
| style="background: #F5F8FF; vertical-align: top" |
'''yes:'''
 Field capacity SM,
 Aquifer max storage
|}
[[#Process rep - pg top|Back to top of page]]



== Groundwater (GW) flow: lateral flow '''within''' the saturated zone ==
'''Note:''' This refers to groundwater flow between modelled land units, such as grid cells, HRUs, or subcatchments, depending on the scale that groundwater stores and flows are modelled at (see more on scales of process representation for GW [[Model units & connections#Aquifers: spatial distribution, vertical layers, connections|here]])
 For coverage of groundwater outflow into a river channel, see the table [[#Aquifer exchanges with channel: aquifer outflow to channel and channel transmission loss|below]]
{| class="wikitable"
! scope="col" style="width:10%" | Algorithm description
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman(Sami GW)
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman(Hughes GW)
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed, more conceptual]]
! scope="col" style="background: #CEDAF2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed, more physical]]
|-
| style="vertical-align: top" | '''Algorithm inputs''' ''(input data, model calculated states / storages, property parameters)''
| style="background: #FFF5FA; vertical-align: top" |
 
''GW flow between subcatchments''
* Aquifer storage ''(state)''
*'''''Aquifer properties:'''''
** Transmissivity
** Storage threshold for flow
** Regional GW slope
 
| style="background: #FFF7F5; vertical-align: top" |
 
''GW flow between subcatchments''
* Aquifer storage ''(state)''
*'''''Aquifer properties:'''''
** Transmissivity
** Storage threshold for flow
** Regional GW slope'''''
** Max storage capacity
 
| style="background: #F5FFF5; vertical-align: top"; rowspan= "3" |
 
'''GW flow between HRU aquifers is not modelled'''
 
'''''Special case, partial exception:''' upland HRU aquifer outflow routed to riparian HRU soil''
 
| style="background: #FFFFF5; vertical-align: top"; rowspan= "3"|
 
'''GW flow between subcatchment aquifers is not modelled'''
 
| style="background: #F5FCFF; vertical-align: top"; rowspan= "3" |
 
'''GW flow between aquifer storage units is not modelled'''
 
| style="background: #F5F8FF; vertical-align: top" |
 
''GW flow between grid cells (Darcy's Law)''
* GW level gradient ''(state - compare levels in neighboring cells)''
*'''''Aquifer properties:'''''
** Specific yield
** Saturated conductivity (Ksat)
 
|-
| style="vertical-align: top" |'''Function type'''
| style="background: #FFF5FA; vertical-align: top" |non-linear & threshold
| style="background: #FFF7F5; vertical-align: top" |non-linear & threshold
| style="background: #F5F8FF; vertical-align: top" |non-linear
|-
| style="vertical-align: top" |'''Thresholds'''
| style="background: #FFF5FA; vertical-align: top" |
'''yes:'''
 Aquifer storage threshold for flow
| style="background: #FFF7F5; vertical-align: top" |
'''yes:'''
 Aquifer storage threshold for flow
| style="background: #F5F8FF; vertical-align: top" |
n/a
|}
[[#Process rep - pg top|Back to top of page]]



== Aquifer exchanges with channel: aquifer outflow to channel and channel transmission loss ==
{| class="wikitable"
! scope="col" style="width:10%" | Algorithm description
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman(Sami GW)
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman(Hughes GW)
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed, more conceptual]]
! scope="col" style="background: #CEDAF2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed, more physical]]
|-
| style="vertical-align: top" | '''Algorithm inputs''' ''(input data, model calculated states / storages, property parameters)''
| style="background: #FFF5FA; vertical-align: top" |
 
''Dynamic two-way exchange within subcatchment ("runoff module"):
 aquifer-to-channel or channel-to-aquifer, depending on conditions (calculated state)''
''Additional one-way channel-to-aquifer representation within "channel module"''
* River channel level ''(input)''
* Subcatchment runoff / area (estimation of local channel store) ''(state)''
* Aquifer storage/level -> GW slope ''(state)''
* '''''Aquifer properties:'''''
** Max flow rate for exchange
** Exchange flow power coefficient
* '''''Channel (module) properties:'''''
** Transmission loss rate
 
| style="background: #FFF7F5; vertical-align: top" |
 
''Dynamic two-way exchange: aquifer-to-channel or channel-to-aquifer, depending on conditions (calculated state)''
* River channel level ''(input)''
* Aquifer storage/level -> GW slope ''(state)''
* '''''Aquifer properties:'''''
** Specific yield
** Conductivity
* '''''Channel properties:'''''
** Length of channel
** Subcatchment drainage density
 
| style="background: #F5FFF5; vertical-align: top" |
 
''One-way exchange: aquifer-to-channel''
''(Channel transmission loss not modelled)''
* Aquifer storage ''(state)''
* '''''Aquifer properties:'''''
* Outflow proportion
 
| style="background: #FFFFF5; vertical-align: top"|
 
''Limited two-way exchange: aquifer-to-channel or channel-to-'''"bank storage"'''(separate storage to the subcatchment's aquifer). Bank storage can release water to channel later. ''
* Aquifer storage ''(state)''
* Channel flow ''(state)''
*'''''Aquifer properties:'''''
** Storage limit for outflow
** Specific yield
** Outflow recession constant
* '''''Channel properties:'''''
* Shape - wetted perimeter
* Bed conductivity
 
| style="background: #F5FCFF; vertical-align: top" |
 
''One-way exchange per channel reach unit (can have multiple per subcatchment with different exchange directions): each reach can have either aquifer-to-channel OR channel-to-aquifer, not switch between over time ''
* Aquifer storage ''(state)''
*'''''Aquifer properties:'''''
** Storage threshold for outflow
** Specific yield
** Outflow recession constant
* '''''Channel properties:'''''
* Losing vs gaining specification
* Shape - wetted perimeter
* Bed conductivity
 
| style="background: #F5F8FF; vertical-align: top" |
 
''Dynamic two-way exchange: aquifer-to-channel or channel-to-aquifer, depending on conditions (calculated state) for each riparian grid cell and channel node pair''
* Water table height ''(state)''
* Channel water level ''(state)''
*'''''Aquifer properties:'''''
** Specific yield
** Conductivity (Ksat)
* '''''Channel properties:'''''
* Shape - wetted perimeter
* Bed conductivity
 
|-
| style="vertical-align: top" |'''Function type'''
| style="background: #FFF5FA; vertical-align: top" |non-linear & threshold
| style="background: #FFF7F5; vertical-align: top" |non-linear & threshold
| style="background: #F5FFF5; vertical-align: top" |rate
| style="background: #FFFFF5; vertical-align: top" |non-linear & threshold
| style="background: #F5FCFF; vertical-align: top" |linear reservoir & threshold
| style="background: #F5F8FF; vertical-align: top" |non-linear & threshold
|-
| style="vertical-align: top" |'''Thresholds'''
| style="background: #FFF5FA; vertical-align: top" |
'''yes - to switch flow direction:'''
 Aquifer water level vs River water level
| style="background: #FFF7F5; vertical-align: top" |
'''yes - to switch flow direction:'''
 Aquifer water level vs River water level
| style="background: #F5FFF5; vertical-align: top" |
no
| style="background: #FFFFF5; vertical-align: top"|
'''yes - to switch flow direction:'''
 Aquifer storage threshold for outflow
| style="background: #F5FCFF; vertical-align: top" |
'''yes - for aquifer-to-channel:'''
 Aquifer storage threshold for outflow
| style="background: #F5F8FF; vertical-align: top" |
'''yes - to switch flow direction:'''
 Aquifer water level vs River water level
|}
[[#Process rep - pg top|Back to top of page]]

Model units & connections

2023-12-01T14:37:02Z

Julia Glenday:

This page describes how modelling tools allow users to discretise catchments into modelled units in order to represent and calculate hydrological processes. Differentiating the catchment into separate components or units - such as subcatchments, patches of similar land cover, or soil layers with distinct properties - allows hydrological processes to be modelled by [[Terminology#algorithm anchor|algorithms]] that have been developed for that scale and type of unit.

Each modelling tool has a unique way of describing a catchment in terms of:

* The types surface and subsurface model units that can be included
* The connections that can be defined between these different units
* The process algorithms that are used to calculate inflows, storage, and outflows for each unit
'''This page summarises the basic unit types and connection options (i.e. flow paths) available across the tools. Sets of tables further describe how the distribution of land cover types, soil types, aquifer types, river channels, and water bodies in a catchment can be represented using each tool.''' These also cover options for vertical distribution of soil, sediment, and rock types. The potential linkages or routing of water between units and layers are highlighted.

Process algorithms, the rules and equations that govern flows in and out of units and layers, are described on a [[Process representation across tools|processes page here]]. Although covered on separate pages, the approach to spatial unit and vertical layer discretisation and the process algorithms used are inextricably [[#Links between discretisation and process representation|linked]].

This page also describes some general implications of the structural differences across the tools. Their importance can be case specific. The implications of the differences across these tools in some particular model application contexts are described in [[Applying tools in specific use cases|sections on specific use cases, here]].

'''''The material on this page may be more depth than you are looking for. If all you need at the moment is an overview of the structures and capabilities of the different modelling tools, that summary can be found on the [[Modelling tool capability overview#Model structure & capabilities overview across tools|capabilities overview page, here]]'''''
 
 
== Importance of understanding structure options ==
 
To set up a model of a specific catchment that is relevant to our understanding of it's processes (conceptual model) entails attention to modelling units and how they are, or are not, connected to one another. A flow path that we think is important in the catchment, and/or is important for the particular modelling project, may not be directly represented by certain modelling tools.
:For example, not all tools can include channel transmission loss from rivers, and those that do include it differ in where the water goes after leaving the model channel.

When a flow path or process that we believe to be important in our use case cannot be explicitly included using a given modelling tool, we can:
* find a way to represent it implicitly, through purposeful parameter adjustment or other work-around (e.g. increasing certain storages, synthetic input or abstraction routes, etc), or
* choose to use another modelling tool.

Understanding how modelled units, subcatchments, HRUs, channels, reservoirs, etc, can interact is also important when '''deciding how to discretise the catchment'''. Strategies may need to differ when using different tools.
:For example, SWAT2012 and SPATSIM can both include irrigation fed from storage dams; however, the two tools have different limitations in terms of where a dam can sit in a model subcatchment and in relation to the irrigated area. In SWAT2012, a 'reservoir' can be an irrigation source. There can be one reservoir per subcatchment and it is located specifically on the main channel at the subcatchment outlet. A reservoir can irrigate an area outside of it's subcatchment. In contrast, SPATSIM-Pitman has a similar 'reservoir unit', but only models irrigation from 'dams', which are different. A 'dam' is located internally in a subcatchment, not on the main channel, and is fed by a proportion of the runoff of the incremental subcatchment only. A dam can only irrigate area within the same subcatchment. These two approaches could lead to quite different subcatchment delineation decisions to represent the same thing!

In general, model unit and connection differences impact:
* the processes that can or cannot be explicitly represented in a model (depending on unit types and scales, some processes will be represented in the link between two or more model units)
* the algorithms that are appropriate for explicit processes, and therefore the meanings of the parameters and the appropriate values for these parameters
:::''NB: Different tools have some model input parameters with the same or similar names, based on shared overarching concepts (e.g. saturated soil moisture storage). However, if the parameters are used in different algorithms and/or applied at different spatial and temporal scales across tools, the values that are appropriate for an area will differ by tool!''
* delineation decisions for subcatchments and other units, because these decisions will have tool-specific impacts on:
:::representing spatial climate variability,
:::the number of land cover types that can be included in the model
:::connectivity of surface and subsurface flows in the landscape,
:::how waterbodies and irrigated areas can be fed
:::the locations within the catchment that a model can produce different predicted outputs for
* if and how the location of a land cover type within a subcatchment (e.g. upland vs riparian) is represented and how this will impact predicted processes.
 
[[#Units - pg top|Back to top of page]]
 
 

== Basic approaches for representing catchments in the different modelling tools ==
 
The schematic diagrams and tables below describe the main discretisation approaches used in each tool in terms of breaking up catchments into units and specifying linkages.
 
For MIKE-SHE, because the tool offers many options, two generalised set-up approaches have been described (more background on these is given [[Coverage of structural options within modelling tools|here]]).


=== Schematic diagrams of spatial discretisation ===

{|
| style="vertical-align: top; text-align:center;" |[[File:Subcat delin Schulze 1995.jpg|thumb|
 '''<big>Subcatchment delineation</big>'''
 Demonstration of:
 (a) a catchment area delineated into subcatchments and
 (b) the flow network connections of these subcatchments when used as model units.
This approach is used to some degree in all the modelling tools covered (except MIKE-SHE when fully distributed). Subcatchments 4,5,6,8 are not headwaters and their river channels receive flow from upstream subcatchments.
''Figures from: Schulze, R.E. (1995). Hydrology and Agrohydrology: A Text to Accompany the ACRU 3.00 Agrohydrological Modelling System (Water Research Commission).'' |alt=|center]]

| style="vertical-align: top; text-align:center;" |[[File:SPATSIM subcat & GW.jpg|thumb|450x450px|
'''<big>Subcatchments as units for process modelling</big>'''
Diagram illustrating the approach taken in '''SPATSIM-Pitman''' of using the subcatchment as the primary unit for representing processes. Flow through the subcat can be conceptualised as flow through a generalised hillslope, which provides a means of modelling groundwater flow and exchange with the river channel. Special subareas (e.g. irrigated crops) impact the subcat's infiltration, surface runoff, ET, and recharge. Interflow and aquifer exchange with the channel are calculated based on the resulting subcatchment-scale storage.
'''WRSM-Pitman & SWAT''' follow a related approach for groundwater in that aquifers are modelled at the subcatchment scale.
''Figures from: Hughes, D.A. (2004). Incorporating groundwater recharge and discharge functions into an existing monthly rainfall–runoff model. Hydrological Sciences Journal, 49.''|alt=|center]]

|style="vertical-align: top; text-align:left;" |[[File:WRSM network demo.jpg|thumb|
'''<big>Modular network of modelling units</big>:'''
Example '''WRSM-Pitman''' model network diagram (catchment of the Churchill Dam, quaternaries K90A&B), demonstrating a catchment composed of modules linked by routes. Subcatchment boundaries are not set-up in the tool; however, sets of linked modules are subcats in effect. (Also, though shown as separate units, each 'irrigation module' is modelled as part of a specified 'runoff module' for groundwater modelling.)
'''ACRU4''' uses a similar modular network approach, although ACRU units are grouped into subcatchments.
''Figure from: Bailey, A.K., and Pitman, W.V. (2015). Water Resources of South Africa 2012 Study (WR2012) (Water Research Commission)''. |alt=|450x450px|left]]

|-
| colspan="2" style="vertical-align: top; text-align:center;" |[[File:ACRU subcat HRU.jpg|thumb|688x688px|
'''<big>Networks of modelling units within subcatchments</big>'''
Demonstration '''ACRU4''' model network diagram showing HRUs (as coloured squares), river channel, and dam units grouped within subcatchments. Climate can be input at the subcatchment scale and certain relationships may only be allowed between units in the same subcatchment (e.g. routing HRU subsurface flow to a special riparian HRU).
The figure also shows that withdrawals and external inputs can be included for rivers and dams.
''Figure from: Clark, D.J., Smithers, J.C., Thornton-Dibb, S.L.C., and Lutchminarian, A. (2012). ACRU 4 User Manual: User Interface & Tutorials in Volume 3 of Deployment, Maintenance, & Further Development of SPATSIM-HDSF. (Water Research Commission).''|alt=|center]]

| style="vertical-align: top; text-align:left;" |[[File:ACRU HRU process.jpg|thumb|470x470px|
'''<big>HRUs as units for process modelling</big>:'''
Schematic diagram of process representation for an HRU (hydrological response unit) in '''ACRU4'''. Each HRU includes a groundwater/baseflow store.
'''SWAT2012''' also uses HRUs to model surface and shallow subsurface processes, but models groundwater at the subcatchment scale.
''Figure modified from: Schulze, R.E. (1995). Hydrology and Agrohydrology: A Text to Accompany the ACRU 3.00 Agrohydrological Modelling System (Water Research Commission).''|alt=|center]]

|-
| colspan="3" style="vertical-align: top;|[[File:Parallel vs series routing.jpg|center|thumb|750x750px|
'''<big>Routing runoff from units in parallel or in series</big>'''
Demonstration of subcatchment delineation into topographic units, which could serve as HRUs or process modelling zones, and related routing options. Runoff from each unit could be routed directly to the stream in parallel, or routed from one unit to the next in a downslope series. Series routing allows processes (infiltration, recharge, saturation seepage, etc) to occur along the path depending on states of downslope units (dry/saturated, flat/steep, rough/smooth, etc). It adds computational complexity. Different approaches can be more appropriate, or more important, in different settings, spatial scales, and for different runoff components (i.e. surface flow, interflow, groundwater flow).
'''SPATSIM''' subareas in subcats modify subcat-scale runoff; no separate routing needed. '''WRSM's''' afforestation & alien veg modules are similar (act inside 'runoff modules'), but irrigation module surface runoff and interflow are routed in parallel to the linked 'runoff module'.
'''ACRU4''' routes all HRU 'quickflow' runoff in parallel and can optionally route 'baseflow' runoff into the soil of a specified 'riparian HRU'.
'''SWAT2012''' routes all HRU surface and 'lateral' (interflow) runoff in parallel, while groundwater is modelled at the subcat scale.
'''MIKE-SHE''' grid cells are connected in series. If 'overland flow zones' are used, surface runoff can be routed in series or in parallel. If interflow and baseflow linear reservoirs are used, interflow is routed in series and groundwater in parallel (if multiple aquifers used). ]]

|-
| colspan="2" style="vertical-align: top; |[[File:MIKE fully distributed.jpg|thumb|497x497px|
'''<big>3D grid cells as units for process modelling</big>'''
Illustration of the approach used in '''MIKE-SHE''' for modelling processes using a 3D grid, i.e. grid cells on the surface (2D) with columns of material below that are broken into layers. (For those familiar with HRUs, each cell can be seen as similar to an HRU connected in series to its neighbors.) In the diagram part of the unsaturated zone is shown as transparent so that the gridded water table surface beneath can be more easily visualised.
''Figure source: DHI (2019). MIKE SHE Manual, Volume 1: User Guide, MIKE 2017 (Danish Hydrologic Institute).'' ]]

|style="vertical-align: top;|[[File:MIKE LR interflow.jpg|thumb|497x497px|
'''<big>Hybrid approach - different unit types for modelling different processes</big>'''
Illustration of the more lumped, conceptual approach for representing interflow and groundwater flow with 'linear reservoir' units in '''MIKE-SHE'''. Other processes can still be modelled by grid cell. Interflow reservoirs have spatial extents and each receives percolating water from the grid cells that overly it. Similarly if multiple different mapped baseflow reservoirs (distinct aquifers) are included, these are recharged by overlying interflow units.
'''SWAT2012''' also uses a hybrid approach in that surface flow and 'lateral' flow (interflow) is modelled at the HRU scale, while the aquifer spans the subcatchment an is recharged by all the overlying HRUs.
''Figure source: DHI (2019). MIKE SHE Manual, Volume 2: Reference Guide, MIKE 2017 (Danish Hydrologic Institute).'']]
|}
[[#Units - pg top|Back to top of page]]


=== Model structure overviews by tool ===
''NB: For MIKE-SHE many structural options are available. Two generalised set-up approaches are used in these comparisons to represent the spectrum. These two are described on [[Coverage of structural options within modelling tools#MIKE-SHE|another page, here]]. 
In addition, the different tools use slightly different terms for the same or similar concepts. This is documented on the [[Terminology#Hydrological process and parameter terms across tools|terminology page, here]]. In general these sections use terms as they are used in the tool being described.''
{| class="wikitable"
! scope="col" style="width:10%" | Level / Element
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
(Sami GW)
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
(Hughes GW)
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed, more conceptual]]
! scope="col" style="background: #CEDAF2; width:15%" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed, more physical]]
|-
| style="vertical-align: top" |'''Catchments'''

'''& subcatchments'''

'''(subcats)'''
| style="background: #FFF5FA; vertical-align: top" |WRSM catchments are composed of ‘modules’ linked in a user-specified network.
Module types:

* runoff modules,
* special area modules (see below)
* channel modules
* reservoir modules

Subcatchments are not explicitly input, but runoff modules and sets of linked modules act as subcats.
| style="background: #FFF7F5; vertical-align: top" |SPATSIM catchments are composed of subcatchments. 
Subcats are linked in spatially determined flow network (map input).

| style="background: #F5FFF5; vertical-align: top" |ACRU4 catchments are composed of subcatchments 
Subcats are linked in a user-specified flow network.

| style="background: #FFFFF5; vertical-align: top" |SWAT catchments are composed of subcatchments

Subcats are linked in a spatially determined flow network (delineated by SWAT from DEM input, or given as a map input)

| style="background: #F5FCFF; vertical-align: top" |MIKE catchments can be composed of subcatchments 
Subcats are linked in spatially determined flow network (map input).
| style="background: #F5F8FF; vertical-align: top" |MIKE catchments can be composed of 3D grid units. The surface is uniformly sized grid cells. Each cell has a column beneath: input layers of soil, sediment, rock.

No subcat boundaries are input; grid cells have elevation (DEM input) and water elevation on the surface and in the 3D grid drive flow.
|-
| style="vertical-align: top" |'''Units within'''

'''subcatchments'''
| style="background: #FFF5FA; vertical-align: top" |A WRSM ‘runoff module’ with no linked special areas functions as a subcat. If special area modules are linked, then a set of modules functions as a subcat.

Special area modules that can be added are:

* afforestation (tree plantation),
* alien vegetation,
* irrigated crops
* mines

These appear as separate units, but function as sub-areas inside a specified linked runoff module.

Runoff modules can also have internally specified subareas:

* impervious area
* riparian area (ET from GW).

| style="background: #FFF7F5; vertical-align: top" |SPATSIM subcatchments all contain a river channel and may have specified special sub-areas. Subcats can optionally include either a wetland or a reservoir/lake on the channel at the subcat outlet.

A special sub-area can be defined for any, or all, of the following in a subcat:

* impervious area
* riparian area (ET from GW)
* area with a higher ET land cover (forest, tree plantation, alien veg)
* crop irrigated from dams
* crop irrigated from river
* small dams internal to subcat (lumped)

Impervious, high ET cover, and irrigation areas do not have defined spatial locations within the subcat.
| style="background: #F5FFF5; vertical-align: top" |ACRU4 subcatchments are composed of one or more [[Terminology#hru anchor|HRUs]]. Non-headwater subcats must contain a river channel. Subcats can optionally include additional channels and reservoir units. Units are linked in a user-specified network.

There are special HRUs for:

* impervious areas,
* irrigated areas,
* riparian areas
* wetlands.
For most HRUs, all runoff is routed directly to a channel, reservoir, or subcat outlet node (in parallel).

''Optional exceptions:''

For ‘riparian HRUs’, ‘baseflow’ output from other HRUs can be routed to the riparian HRU soil.

For ‘adjunct-impervious HRUs’, runoff is routed to the surface of another HRU.

| style="background: #FFFFF5; vertical-align: top" |SWAT subcatchments are composed of:

*[[Terminology#hru anchor|HRUs]] (many)
* shallow aquifer unit,
* deep aquifer unit,
* tributary channel unit
* main river channel unit.

Subcats can include an internal pond or wetland and a reservoir/lake on the channel at the subcat outlet.

HRU surface & ‘lateral’ runoff output is routed directly to the subcat channel (in parallel). This passes via the tributary channel, where delays & infiltration can occur, to the main channel.

Groundwater is modelled at the subcat scale. Aquifers are recharged by all subcat HRUs. Shallow aquifer outflow goes to the subcat main channel.

| style="background: #F5FCFF; vertical-align: top" |MIKE-SHE subcatchments are composed of:

* grid cells (veg & soil)
* ‘overland flow zones’,
* ‘interflow reservoirs’
* ‘baseflow reservoirs’
* river channel links

Surface runoff is lumped for grid cells within an overland flow zone & routed across zones in a downslope series to the channel (potential for infiltration on route).

Interflow reservoirs receive percolation from overlying grid cells. Interflow is laterally routed through a downslope series of reservoirs to the channel (potential for loss to recharge on route).

Baselfow reservoirs are recharged by overlying interflow reservoirs and outflow to the channel in parallel.
| style="background: #F5F8FF; vertical-align: top" |Using fully distributed MIKE-SHE, no subcat boundaries are input. Relative water surface or head elevations on the surface and in the 3D grid units drives flow exchange between units.

Surface and subsurface properties for the grid cells & layers are input for different zones (map input).

Different sets of zone polygons can be used for the different types of properties (e.g. vegetation types, soil types, aquifer extents); they do not need to be aligned with one another.
|-
| style="vertical-align: top" |'''River channels'''
| style="background: #FFF5FA; vertical-align: top" |WRSM channels are modules in the network with multiple inflow and outflow links possible.

Channel modules can have an associated wetland storage/area.
| style="background: #FFF7F5; vertical-align: top" |SPATSIM channels are units linked to subcats (one per subcat).

They receive the local subcat runoff & upstream subcat channel outflows.
| style="background: #F5FFF5; vertical-align: top" |ACRU4 channels are units in a subcat network of units. (necessary in non-headwater subcats).

They receive runoff from linked HRUs, reservoirs, & upstream subcat outflows.
| style="background: #FFFFF5; vertical-align: top" |SWAT channels are units linked to subcats (one main channel per subcat).

They receive the local subcat runoff & upstream subcat channel outflows.
| style="background: #F5FCFF; vertical-align: top" |MIKE channels are composed of spatially explicit reaches between node points.
Reaches with nodes mapped inside a subcat exchange water with the subcat.

| style="background: #F5F8FF; vertical-align: top" |MIKE channels are composed of spatially explicit reaches between node points.
Reaches can exchange water with grid cells that border them.
|}
 
 
'''''<big>At a basic level, these modelling tools are similar in some notable ways:</big>'''''

*'''Catchments divided into subcatchments:''' All the tools can represent a larger catchment as an accumulative flow network of smaller subcatchments. In this way they are all ‘semi-distributed’ to a certain extent (with MIKE-SHE also offering ‘fully distributed’ – fully gridded – representation as an option).

*'''Same major vertical layers:''' All the tools represent processes for the same broad set of vertical layers - vegetation canopy and land surface, soils/unsaturated zone, and aquifer materials – which are then linked to a channel network. This is not the case for all catchment models. For example, the original Pitman model (Pitman 1973) did not separate soil and aquifer processes, but instead used a lumped sub-surface storage unit to handle both.

*'''Multiple land cover types per subcatchment:''' All the tools allow different land cover types to be explicitly represented across different subcatchments and within them. At a minimum, within each subcatchment ''all the tools can at least explicitly represent'':
:::a dominant generalised vegetation type per subcatchment (i.e. local indigenous veld type, non-irrigated grazing lands)
:::a separate tree-dominated vegetation type per subcatchment (e.g. forest, commercial tree plantations, invasive alien tree stands)
:::irrigated crops
:::impervious cover (urban area, bare rock).

*'''Reservoirs/dams/waterbodies:''' All tools can include reservoirs/dams/waterbodies fed by the channel network.
 
[[#Units - pg top|Back to top of page]]
 
 

== Discretisation and process representation ==
 
The scale of discretisation of the landscape influences which hydrological processes are individually represented and the algorithms and the timesteps that are appropriate (discussed in more detail [[Model types & tools|here]]). In general, for larger spatial/vertical units, longer timesteps, more lumped process representation, and different property parameters are applicable compared to modelling with smaller units. This has to do with how long it’s likely to take for water to move through a modelled unit. For example, it may take a week for interflow to move through the 10 km long hillslope of subcatchment, but a day to move through the 1 km slope length of a patch of grassland within that subcatchment. Speed also varies by process and with conditions (e.g. dry and wet) which also needs some consideration in the algorithms used with a uniform calculation timesteps.

Differences in algorithms and parameters with spatial scale also have to do with the fact that what may be modelled as one process at a larger spatial scale can be the result of several different processes occurring at smaller scales. For example, rain falling on a steep, rocky cliff may form surface runoff. If this surface runoff then flows across an area of permeable and unsaturated soil before reaching a stream channel, some may infiltrate and not reach the stream as surface flow. If one models a subcatchment where this is happening within a single spatial unit, the equation and parameters for estimating ‘surface runoff generation’ would account for the ''net outcome'' of the surface runoff that actually reaches the stream, i.e. the combined impact of the cliff and the permeable toe-slope on surface runoff reaching the channel. If modelling the cliff and the toe-slope as separate units, surface runoff on the cliff unit could be calculated, and then surface flow and infiltration on the toe-slope unit could be calculated as a separate set of processes, to get to the amount of surface runoff reaching the channel.
 
 
===Timesteps & spatial units for different processes===
{| class="wikitable"
! scope="col" style="width:10%" | Units
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
(Sami GW)
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
(Hughes GW)
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed, more conceptual]]
! scope="col" style="background: #CEDAF2; width:15%" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed, more physical]]
|-
| style="vertical-align: top" |'''Timesteps'''
| style="background: #FFF5FA; vertical-align: top" |Monthly*

A daily version has been developed. Limited use to-date
| style="background: #FFF7F5; vertical-align: top" |Monthly*

A daily version has been developed. Limited use to-date
| style="background: #F5FFF5; vertical-align: top" |Daily

| style="background: #FFFFF5; vertical-align: top" |Daily, subdaily

| style="background: #F5FCFF; vertical-align: top" |Daily, subdaily*

Timesteps are dynamic, vary by process & unit size. Outputs saved for the same selected step.
| style="background: #F5F8FF; vertical-align: top" |Daily, subdaily*

Timesteps are dynamic, vary by process & unit size. Outputs saved for the same selected step.
|-
| colspan="7" |'''''Spatial units for:'''''
|-
| style="vertical-align: top" |'''Climate input'''
| style="background: #FFF5FA; vertical-align: top" |Modules (all)
| style="background: #FFF7F5; vertical-align: top" |Subcatchments
| style="background: #F5FFF5; vertical-align: top" |Subcatchments or HRUs*

*HRU-scale input is labor intensive
| style="background: #FFFFF5; vertical-align: top" |Subcatchments
| style="background: #F5FCFF; vertical-align: top" |Grid cells or zones
| style="background: #F5F8FF; vertical-align: top" |Grid cells or zones
|-
| style="vertical-align: top" |'''Surface & shallow subsurface processes'''
| style="background: #FFF5FA; vertical-align: top" |Runoff modules

+ special area modules
| style="background: #FFF7F5; vertical-align: top" |Subcatchments

(+ internal special sub-areas)

| style="background: #F5FFF5; vertical-align: top" |[[Terminology#hru anchor|HRUs]]
| style="background: #FFFFF5; vertical-align: top" |[[Terminology#hru anchor|HRUs]]
| style="background: #F5FCFF; vertical-align: top" |Grid cells

+ Overland flow zones

+ Interflow reservoir zones

| style="background: #F5F8FF; vertical-align: top" |Grid cells
|-
| style="vertical-align: top" |'''Groundwater processes'''
| style="background: #FFF5FA; vertical-align: top" |Runoff modules
| style="background: #FFF7F5; vertical-align: top" |Subcatchments
| style="background: #F5FFF5; vertical-align: top" |[[Terminology#hru anchor|HRUs]]
| style="background: #FFFFF5; vertical-align: top" |Subcatchments
| style="background: #F5FCFF; vertical-align: top" |Baseflow reservoir zones
| style="background: #F5F8FF; vertical-align: top" |Grid cells
|}
[[#Units - pg top|Back to top of page]]
 
 

== Summary of structural differences & implications ==
 
Despite their high-level similarities, there are numerous differences in the way that these tools allow users to discretise and represent various components of catchments in terms of scales, unit types, and connections. These differences have implications for what a model built with that tool can do (see [[Modelling tool capability overview#capabilities - Table Anchor|capabilities overview table]]). They are also important for the discretisation and parameterisation choices a user must make.

'''The specific implications of the differences across tools, and their real importance for a modelling project, will differ across use-cases.''' These will be dependent on the combination of the type of catchment, the changes that are to be modelled, the data available, and the types and scales of model outputs that are needed. This makes it difficult to generalise about the implications or relative importance of a particular difference. Nevertheless, the tables below demonstrate some potential implications of some highlighted structural differences as examples:
* [[#climate input implic - Table Anchor|CLIMATE: Spatial units for which climate inputs are specified]]
* [[#cover input implic - Table Anchor|LAND COVER: Units used to represent different land cover types & their connectivity]]
* [[#aquifer input implic - Table Anchor|AQUIFERS: Units used to represent aquifers & their connectivity]]
* [[#channel unit implic - Table Anchor|RIVER CHANNEL NETWORK: Channel units & links to landscape units]]

Further implications of tool differences in some particular applied contexts are described in [[Applying tools in specific use cases|a section on specific use-cases, here.]]

{| class="wikitable"
|+
! colspan="4" style="background: #CED4F2; text-align: left"|<big>'''CLIMATE: Spatial units for which climate inputs are specified'''</big>
|-
|style="background: #E6EAFF;vertical-align: top"| '''Why it can be important & when'''
| colspan="3" style="background: #F5F7FF;vertical-align: top"| '''Determines if/how spatial variation in climate over the catchment can be represented in the model.'''

''Likely more important to model outcomes for catchments with:''

*''larger gradient magnitudes across the catchment area (e.g. larger catchment size, more mountainous terrain)''
*''generally drier areas in which the higher rainfall parts are frequently the only places where thresholds for runoff production are reached (i.e. if more averaged rainfall were applied for a larger area, then no runoff would be modelled)''
''NB: Potential advantages of including more spatial climate variability in a model also depend on the level of data available about the spatial distribution of rainfall and PET.''
 
|-
|style="background: #E6EAFF;vertical-align: top"|'''Alternative approaches'''
|style="background: #F5F7FF;vertical-align: top"|'''Subcatchment'''
|style="background: #F5F7FF;vertical-align: top"|'''HRU / module / waterbody'''
|style="background: #F5F7FF;vertical-align: top"|'''Individual grid cells or independent zones''' (not tied to the boundaries of other inputs like land cover, subcatchments, etc)
|-
|style="background: #E6EAFF;vertical-align: top"|'''Tools using approach'''
|style="background: #F5F7FF;vertical-align: top"|
* SPATSIM-Pitman
* WRSM-Pitman (uniform within ‘runoff module’ + associated treed modules)
* SWAT2012
* ACRU4 (most user-friendly way to input)
|style="background: #F5F7FF;vertical-align: top"|
* ACRU4* (possible, but very labour intensive)
* WRSM-Pitman ''- limited''* (irrigated areas, reservoirs, wetlands can have own climate)
|style="background: #F5F7FF;vertical-align: top"|
* MIKE-SHE (with both semi- & fully-distributed options)
|-
|style="background: #E6EAFF;vertical-align: top"|'''Potential implications of approach'''
|style="background: #F5F7FF;vertical-align: top"|Areas with important differences in climate need to be delineated as separate subcatchments to include this.

''This may entail compromises between directly representing climate variability and directly representing flow pathways that are effectively broken by subcatchment boundaries.''

Implications vary by tool: in some there is no GW flow between subcats and areas feeding dams, wetlands, riparian areas & irrigation may need to be in the same subcat (see aquifer implications and specific structure tables below for details)
|style="background: #F5F7FF;vertical-align: top"|Can include spatial variability in climate ''within'' a subcatchment.

Avoids potential compromises in connectivity that could be imposed by subcat boundaries (see notes to left).

HRU or module delineations may be altered to include climate gradients: i.e. breaking up a broad land cover type into multiple units that receive different climate inputs.

In ACRU4 & WRSM, setting up HRUs and modules is a many-step, manual process. The added labour and opportunity for user error would depend on the number of units involved.
|style="background: #F5F7FF;vertical-align: top"|Spatial variability in climate can be included without the need to compromise on representing hydrological connectivity and with relatively little added effort (see notes to left).

Climate inputs and land cover, soil, and other properties are each specified using independently delineated zones and then separately assigned to each grid cell by the modelling tool.

Delineating climate zones (deciding number & spatial extent) and preparing zone data is a step in all approaches. This approach avoids some decision-making about where/how to compromise (see notes to left).
|}

{| class="wikitable"
|+
! colspan="3" style="background: #CED4F2; text-align: left"|<big>'''LAND COVER: Units used to represent different land cover types & their connectivity'''</big>
|-
|style="background: #E6EAFF;vertical-align: top"| '''Why it can be important & when'''
| colspan="2" style="background: #F5F7FF;vertical-align: top"| '''Influences the number of different land cover types that can be explicitly represented and what types of land cover changes can be modelled.'''

''The importance of this will depend on the purpose of modelling project and the diversity of cover types within the modelled area.''

''NB: Potential advantages of being able to explicitly represent more different land cover types in a model will also depend on the property information available to reliably parameterise them as being different from one another. ''

'''Influences if/how the specific location of a land cover within a landscape is considered when modelling its processes (e.g. upland vs riparian).'''

''NB: Relevant when modelling at spatial scales that can capture position differences vs larger scales that must average over them''

''Likely more important in more water limited areas and with diverse topography: position is a more significant determinant of water access.''
 
|-
|style="background: #E6EAFF;vertical-align: top"|'''Alternative approaches'''
|style="background: #F5F7FF;vertical-align: top"|'''Each subcatchment has one ‘main’ land cover type and additional types are represented as proportions of the subcatchment area.'''

'''Each additional cover type is represented with different type-specific algorithms (e.g. tree plantation, irrigated crops)'''
|style="background: #F5F7FF;vertical-align: top"|'''Land cover properties are assigned to HRUs within subcatchments, or to individual grid cells.'''

'''These units (HRUs, grid cells) all use the same basic process algorithms with respect to land cover - differences between cover types come from the property parameter inputs.'''
|-
|style="background: #E6EAFF;vertical-align: top"|'''Tools using approach'''
|style="background: #F5F7FF;vertical-align: top"|
* SPATSIM-Pitman
* WRSM-Pitman
|style="background: #F5F7FF;vertical-align: top"|
* ACRU4
* SWAT2012
* MIKE-SHE
|-
|style="background: #E6EAFF;vertical-align: top"|'''Potential implications of approach'''
|style="background: #F5F7FF;vertical-align: top"|Fewer different cover types can be explicitly included vs other approaches.

Particularly limits the number of non-irrigated, non-afforested types (e.g. veld types, grazing land, levels of degradation).

In theory, more types can be included using more (smaller) subcats. This becomes unwieldly to set-up, limits aspects of connectivity (see above), and algorithms may not apply to very small subcats.

SPATSIM allows fewer types over all (see [[#land cov dist - Table Anchor|table]]), but has some flexibilities. It allows two types of non-irrigated cover per subcat: a portion is assigned a higher ET rate. This rate is flexible, so could be a second veld type, plantation, invasives, or a lumped combination of these.

WRSM has modules for tree plantations and invasive alien trees. Both can be added in one subcat, but their algorithms are specific to those covers. The riparian area within a ‘runoff module’ can be given it’s own ET pan-factors, allowing it to be another cover type flexibly defined. This could cause ‘double counting’ with the treed-area modules that effectively act on the full runoff module. (See riparian areas page LINK for more.) 

A more detailed cover composition can be represented implicitly, with parameters for broader model types calculated from the local mix of more detailed types. With conceptual parameters, this may not be straightforward.

Most cover types don’t have an explicit spatial location within a subcat. The riparian zone of a WRSM runoff module is an exception. The SPATSIM riparian area does not have its own cover type. (See [[Applying tools in specific use cases#Riparian zones|riparian areas section]] for more.) 
|style="background: #F5F7FF;vertical-align: top"|No tool-imposed limit on the number of different cover types that can be explicitly included in a model. 

Limitations will come from the information available to reliably parameterise types as different from one another as well as from the practicality of setting up many types in the tool (see [[Modelling tool user interfaces|interface section]])

Linkages allowed between units (HRUs, grid cells) determine if/how the location of a cover type within a subcat is explicitly considered. If each unit’s runoff is routed directly to a channel in parallel to others, without interacting, relative position is not represented. 

Position is explicit in MIKE-SHE: flows are routed into/onto neighbouring units or zones.

This is more limited in ACRU4 and SWAT2012, which have mostly parallel routing, but there are ways in which location (i.e. riparian vs upland) can be represented for certain HRUs, hence cover types.

In ACRU4, special riparian HRUs receive ‘baseflow’ runoff from linked upslope HRUs. Special riparian and wetland HRUs are also linked channels and can receive overflow.

In SWAT2012,the level of access to groundwater for ET can be set by HRU. This can be set higher for some HRUs to differentiate riparian vs uplands. Aquifers are subcat scale, so uplands can recharge the store used by riparian. Special ‘depression’ waterbodies can also be set-up on specified HRUs, which receive routed runoff from linked upslope HRUs. 
|}

{| class="wikitable"
|+
! colspan="5" style="background: #CED4F2; text-align: left"|<big>'''AQUIFERS: Units used to represent aquifers & their connectivity'''</big>
|-
|style="background: #E6EAFF;vertical-align: top"| '''Why it can be important & when'''
| colspan="4" style="background: #F5F7FF;vertical-align: top"| Determines if/how '''spatial variability of aquifer material (sediment deposits, geological formations, layers) within a subcatchment can be explicitly represented''' (if information on this is available). This will be more important when there are large known differences at the subcat scale (depends on choice of subcat sizes).

Determines the '''scale at which groundwater storage, and potentially water table depth, can be output''' by the model.

Determines '''where within in a model catchment groundwater (GW) can outflow to a channel.''' If there is no subsurface GW flow between modelled units, then any recharge within a unit that is thought to contribute to outflow of the larger catchment will need to emerge as baseflow from that same unit in the model. In reality there may be subsurface flow with the GW emerging further down. Having the GW emerge further upstream can impact other modelled processes linked to channel flows at different locations (overbank flow, transmission loss, waterbody storage, irrigation).

Influences the '''groundwater access of vegetation in different parts of the catchment,''' which can impact modelled seasonal and total ET and the modelled impact of vegetation cover changes. (Linked to model representation of the location of a land cover type – [[#cover input implic - Table Anchor|see above]]).

''Likely more important to model outcomes for:''

* ''catchments where GW contributes more substantially to the overall hydrograph,''
* ''cases where disconnected units (e.g. subcats) are small in comparison to connectivity of aquifers important to the hydrograph (delineation accounting for other factors, i.e. climate & land cover)''
* ''areas where GW is an important water source for vegetation (particularly GW recharged by a large surrounding area) ''
* ''modelling projects focused on low flows and/or flows at points within the catchment''
 
|-
|style="background: #E6EAFF;vertical-align: top"|'''Alternative approaches'''
|style="background: #F5F7FF;vertical-align: top"|'''Subcatchment-scale aquifers'''

'''''No GW flow between subcats'''''
|style="background: #F5F7FF;vertical-align: top"|'''Subcatchment-scale aquifers'''

'''''GW can flow between subcats'''''
|style="background: #F5F7FF;vertical-align: top"|'''HRU-scale aquifer units (or other units smaller than subcatchments)'''

'''''No GW flow between aquifer units or subcats'''''
|style="background: #F5F7FF;vertical-align: top"|'''3D grid of connected volume units'''

'''''All units can interact'''''
|-
|style="background: #E6EAFF;vertical-align: top"|'''Tools using approach'''
|style="background: #F5F7FF;vertical-align: top"|
* SWAT2012
* MIKE-SHE, semi-distributed, linear reservoir GW option* (can have a subcat-scale unit)
|style="background: #F5F7FF;vertical-align: top"|
* SPATSIM-Pitman
* WRSM-Pitman
|style="background: #F5F7FF;vertical-align: top"|
* ACRU4* (partial exception: riparian HRU)
* MIKE-SHE, semi-distributed, linear reservoir GW option* (can have multiple units in a subcat; these don’t interact)
|style="background: #F5F7FF;vertical-align: top"|
* MIKE-SHE, fully distributed, finite difference GW option
|-
|style="background: #E6EAFF;vertical-align: top"|'''Potential implications of approach'''
|style="background: #F5F7FF;vertical-align: top"|Subcat aquifer parameters reflect average, or net, storage and flow properties of aquifer material in the subcat.

Subcat scale GW model outputs.

'''Within a subcat:''' model can allow vegetation in one area to access GW that was recharged in another location in the subcat.

'''Between subcats:''' If its important to for veg in a downstream subcat to access GW that was recharged in an upstream subcat, work-arounds are needed. Water to feed this ET would need to leave the upstream subcat as channel flow and then become accessible downstream, e.g. through channel transmission loss. Alternatively revise the subcat delineation.

To model total catchment outflow, some GW may need to enter the channel network in upstream model subcats that in reality flows in the subsurface and emerges further down (downstream subcats in model). This could influence aquifer parameterisation choices (i.e. vs field data on properties). If having more water in the channel higher up in the catchment has significant impacts on other processes (upstream dams, etc), adaptations may need to be made to these and/or the subcat delineation revisited.
|style="background: #F5F7FF;vertical-align: top"|Subcat aquifer parameters reflect average, or net, storage and flow properties of aquifer material in the subcat.

Subcat scale GW model outputs. 

Models can allow vegetation in one area to access GW that was recharged in another location in the same subcat or another subcat (only applies to the specified ‘riparian zones’ in SPATSIM-Pitman & WRSM-Pitman subcats/runoff-modules).

Avoids potential subcat delineation and aquifer parameterisation compromises or water routing work-arounds (see notes to left)

|style="background: #F5F7FF;vertical-align: top"|Aquifer parameters can differ across units within a subcat to represent spatial distribution of different aquifer materials (e.g. fractured rock in uplands, alluvium over rock in lowlands).

GW model outputs can be obtained for different areas within a subcat.

Separated model GW stores that do not interact implies separate aquifers outflowing to channel network independently. This may not be the case in reality. This would impact aquifer parameter choices (i.e. vs. field property data).

'''Within a subcat:''' Vegetation can only access GW stores that are recharged in the same spatial unit (HRU in ACRU4, baseflow reservoir extent in MIKE-SHE). Lowlands cannot access GW recharged in highlands in the model if these are separate HRUs or zones. This could result in unrealistically low ET.

ACRU4 & MIKE-SHE have optional routines to overcome this. ACRU4’s special riparian HRU can receive ‘baseflow’ output from linked upland HRUs (routed to riparian soil). In MIKE-SHE, water from ‘baseflow reservoirs’ can be routed to the soil of a riparian zone to make up a deficit (feed ET). 

Implications of also not modelling ''GW flow between subcatchments'' are the same as those described to the left. 
|style="background: #F5F7FF;vertical-align: top"|Aquifer parameters can differ across units within a subcat to represent spatial distribution of different aquifer materials (e.g. fractured rock in uplands, alluvium over rock in lowlands).

GW model outputs can be obtained for specific grid cells in the model as needed.

Because there can be flow between all aquifer units (determined by relative head and conductivity between neighbouring cells) and no subcat boundaries limiting subsurface connectivity, vegetation in lowlands would be able to access GW recharged elsewhere in the model when conditions allow.

The approach can have high computational demand, so model runs are longer (runtimes depend on computing power).
|}

{| class="wikitable"
|+
! colspan="4" style="background: #CED4F2; text-align: left"|<big>'''RIVER CHANNEL NETWORK: Channel units & links to landscape units'''</big>
|-
|style="background: #E6EAFF;vertical-align: top"| '''Why it can be important & when'''
| colspan="3" style="background: #F5F7FF;vertical-align: top"| Determines the '''locations within the catchment where modelled streamflow outputs will be available.'''

''This can be important if there are monitoring points or other points of interest where these outputs would assist, i.e. water supply withdrawal points, areas for flood assessment, aquatic habitat assessesment.''

'''Influences where reservoirs, waterbodies, wetlands that are fed by the channel network can be located with respect to model subcatchments and what areas feed them.'''

Determines the potential for '''representing spatial variability in channel properties''', ''where these are understood and thought to be important''

Flow from channel units to landscape unit surface & subsurface can allow for '''water exchanges between delineated subcatchments''' (see notes above).

'''Channel processes that are not explicitly included (e.g. transmission losses, overbank flooding) will be implicitly represented''', likely through parameterisation, to generate net aquifer outflow and net surface runoff.

''This will be more important in catchments where channel transmission loss and/or overbank flooding are frequent and make a notable impact on the flows.''
 
|-
|style="background: #E6EAFF;vertical-align: top"|'''Alternative approaches'''
|style="background: #F5F7FF;vertical-align: top"|'''One channel reach unit per subcatchment'''

'''''Two-way channel-landscape sub-surface exchange'''''

'''''Limited or no overbank flooding'''''
|style="background: #F5F7FF;vertical-align: top"|'''Flexible number and arrangement of channel reach units, manually connected to HRUs, modules, reservoirs'''

'''''Two-way channel-landscape sub-surface exchange'''''

'''''Limited or no overbank flooding'''''
|style="background: #F5F7FF;vertical-align: top"|'''Channel reach units spatially linked to landscape grid cells and have explicit elevation'''

'''''All units can interact, surface and subsurface'''''
|-
|style="background: #E6EAFF;vertical-align: top"|'''Tools using approach'''
|style="background: #F5F7FF;vertical-align: top"|
* SWAT2012
* SPATSIM-Pitman
* WRSM-Pitman* (some channel exchange processes are calculated ''within'' ‘runoff-modules’)
|style="background: #F5F7FF;vertical-align: top"|
* ACRU4
* WRSM-Pitman* (separate channel modules in network)
|style="background: #F5F7FF;vertical-align: top"|
* MIKE-SHE
|-
|style="background: #E6EAFF;vertical-align: top"|'''Potential implications of approach'''
|style="background: #F5F7FF;vertical-align: top"|To get model output streamflow for a point, it needs to be the outlet of a subcatchment.

Reservoirs on the channel network will be at the outlets of subcatchments (not in WRSM), so also influence subcat delineation (see specific waterbody table below).

Subcat delineation also has implications for subsurface flow connectivity and other aspects of representation (see above) – various compromises may be needed in the delineation.

SPATSIM & SWAT2012 partially address the restriction in reservoir location by including other waterbody unit types that can be internal to subcats, fed by proportions of subcat runoff. The set-ups of these types have other restrictions (See waterbody table below).

Subcat-scale channel & subcat-scale aquifer representation facilitates calculation of exchange (GW to channel, channel to GW, “transmission loss”) considering storage and properties of both. This is done in SPATSIM and in WRSM within a run-off module. In SWAT2012, channel transmission loss goes to a separate bank storage unit, not the subcat-aquifer.

SPATSIM & WRSM include overbank flooding only in wetland modules. SWAT2012 does not include overbank flooding onto land units (wetland module not on the channel).

Channel transmission loss in SWAT2012 & SPATSIM and overbank flooding to wetland units provide ''means by which downstream areas can access water that entered the channel network from upstream units.''
|style="background: #F5F7FF;vertical-align: top"|Flexibility in where streamflow outputs can be obtained and where reservoirs/waterbodies and transfers can be located. This can reduce some delineation related compromises.

In ACRU4, channel units are fed by linked HRUs. This will impact the delineation of HRUs (e.g. an area of a single cover type in a subcat may be split into multiple HRUs to feed into different points in the channel network, above or below a reservoir, etc).

The manual process of setting up HRUs and establishing routing connections individually in ACRU4 means that taking advantage of this flexibility comes with significant additional labour.

In WRSM, user-specified portions of the outflow of a single ‘runoff module’ can be routed to multiple channel and reservoir modules. These channels and reservoirs are then effectively inside the subcat represented by the runoff-module. This reduces the number of individual runoff-modules that need to be set-up. 

Conversely all runoff from a ‘runoff module’ can be routed to one channel module and/or multiple runoff modules can contribute to a channel module. This allows modules with different land cover compositions to contribute as different points, more like ACRU4 HRUs. 

ACRU4 does not explicitly represent channel transmission loss. WRSM calculates this within runoff modules. Additional ‘bedloss’ can be specified for channel modules, but this is removed from the model, not added to an aquifer, not available for ET.

Implication: water entering the channel network from upstream landscape units cannot be accessed for ET in downstream landscape units via channel transmission loss. (see section on channel transmission loss LINK)

ACRU4 & WRSM include overbank flooding only in their wetland units/HRUs and ACRU4 riparian HRU. This is a ''means by which downstream areas can access water that entered the channel network from upstream units.''
|style="background: #F5F7FF;vertical-align: top"|Model streamflow outputs can be obtained for any point in the channel network.

Reservoirs and water bodies can be added at any location. Because these have explicit locations in the model grid, the approach of lumping many small farm dams into a single unit can difficult to operationalise depending on the drainage network, etc. 

'''Using fully distributed options''': Explicit location and elevation in the model grid allows calculation of exchanges between channel reaches and their neighbouring cells based on the water levels in each and conductivity. The explicit depth of the channel impacts how much groundwater enters it. Bank topography can limit surface flow entering the channel. Overbank flooding and channel transmission losses occur when levels allow.

The approach comes with notable practical implications. It requires careful vetting of landscape topography data and the channel cross section inputs to make sure these correspond so that flow exchanges are realistically modelled. The method has high computational demand, so model runs are longer (runtimes depend on computing power).

'''Using the more lumped surface and groundwater options:''' Surface and GW flows into the channel aren’t calculated using the explicit elevation of the channel. Channel transmission loss and overbank flooding can still be included using different algorithms. These provide ''means by which downstream areas can access water that entered the channel network from upstream units.''

|}
[[#Units - pg top|Back to top of page]]

=== Summary comparison of WRSM and SPATSIM-Pitman ===
 
'''''WRSM and SPATSIM-Pitman are more similar than they may appear from the structural overview, sharing subcatchment structure & core algorithms'''''

The WRSM-Pitman approach to model structure, with a flexible network of modules, makes it appear to be very different to SPATSIM-Pitman, which uses a clearly defined subcatchment as the basic unit of calculation for most processes. However, looking at the process algorithms for the different 'modules' in WRSM-Pitman makes it clearer that '''the two tools actually have relatively similar, mostly subcatchment-based, approaches'''.

The WRSM 'runoff module', on its own with no linked special area modules, functions like a basic subcatchment of SPATSIM-Pitman, with no defined sub-areas of treed cover or irrigated crops. In this case, both tools use the same subcatchment scale, monthly time-step process algorithms of the original Pitman model (Pitman 1973) adjusted to include a separate aquifer store.

The WRSM modules for representing commercial tree plantations and irrigated crops visually appear as separate in the model interface and network diagrams (which are generated by users, not by the software tool), but actually they function as parts of a 'runoff module'/subcatchment area. The linkage to a run-off module is established in their set-up specifications in the software. The process algorithms for these areas differ across the tools, but in both cases the treed cover modules act to increase the ET losses of the subcatchment/'runoff-module'. The resulting runoff (surface runoff, interflow, aquifer flow to channel) is generated at the subcatchment scale. For irrigated crop areas, net runoff is tied to processes calculated in the linked subcatchment in both cases as well. This means that the WRSM treed area and irrigated crop modules function more like sub-areas of subcatchments in SPATSIM than like HRUs in ACRU4, in which more processes are calculated for the HRU unit alone.

'''Aside from ''process algorithm'' differences, the main ''structural'' differences across the two tools in terms of modelled units 'inside' subcatchments are:
*the numbers of different special area types than can be included 'in' a subcatchment (i.e. tied to a 'runoff-module' in WRSM),
*the flexibility and arrangement of water sources that can be used for irrigation, and
*flexibility in where reservoirs, withdrawals, and transfers can be placed and how they are fed.

In terms the basic model subcatchment, there is also a potentially important difference in the connection to the channel network between the tools. This is relevant to their representation of groundwater-surface water interactions. Both tools calculate aquifer-river channel exchange for the basic subcatchment unit. This is calculated within a 'runoff module' in WRSM, before the water is routed to a connected channel module. Channel modules receive the net runoff after this exchange, and do not interact further with the runoff module/subcatchment. In a sense, there is an implicit 'tributary channel' within a WRSM runoff module for which certain processes are represented, and the channel modules are a main channel network that is handled differently. In SPATSIM-Pitman, each subcatchment has a channel element that is tied to it. The channels of downstream subcatchments receive channel flow from those upstream and their channel-aquifer exchange is calculated using this accumulated channel flow. In WRSM-Pitman, this exchange is only calculated for the runoff produced in the run-off module, the incremental subcatchment, and channel flow from upstream subcatchments is not involved. The overall impact of this different on catchment-scale modelling outcomes would vary depending on how important this exchange for a given area.
 
 
[[#Units - pg top|Back to top of page]]
 
 
 
 

== Specific units & connections for different model components ==
 

=== Land cover: spatial distribution & type limitations ===
{| class="wikitable"
! scope="col" style="width:10%" | Factor
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
(Sami GW)
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
(Hughes GW)
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed, more conceptual]]
! scope="col" style="background: #CEDAF2; width:15%" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed, more physical]]
|-
| rowspan="2" style="vertical-align: top" |'''Spatial units for land cover type/property'''

'''distribution'''

| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''Modules & sub-areas within them'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''Subcatchments & sub-areas within them'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |[[Terminology#hru anchor|'''HRUs''']]
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |[[Terminology#hru anchor|'''HRUs''']]
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''Cover type polygons applied to grid cells'''
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |'''Cover type polygons applied to grid cells'''
|-
| style="background: #FFF5FA; vertical-align: top" |Extents of cover types are either defined in the:

* ‘runoff module’ set-up
* special area modules (which are tied to, and act as sub-areas of, a ‘runoff module’)

Each runoff module can have different general cover specifications & linked special areas.
| style="background: #FFF7F5; vertical-align: top" |Extents of cover types are defined as special sub-areas within a subcat.

Each subcat can have different general cover & sub-areas specifications.
| style="background: #F5FFF5; vertical-align: top" |Each HRU has its own cover & vegetation parameters.

| style="background: #FFFFF5; vertical-align: top" |Each HRU has cover & vegetation parameters.

HRUs are assigned cover types using an input cover type map. Properties are input by type.
| style="background: #F5FCFF; vertical-align: top" |Each grid cell is assigned a cover type using an input cover type map. Properties are input by type. 

| style="background: #F5F8FF; vertical-align: top" |Each grid cell is assigned a cover type using an input cover type map. Properties are input by type. 

|-
| rowspan="2" style="vertical-align: top" |'''Limitations to types & number of types'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |No
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |No
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |No
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |No
|-
| style="background: #FFF5FA; vertical-align: top" |Types that can be represented:

* General vegetation (runoff module parameters)
* Impervious area (runoff module parameters)
* Riparian zone vegetation (runoff module parameters)
* Afforestation (special module, 1 per runoff module)
* Invasive alien vegetation (special module, 1 per runoff module)
* Irrigated crops (special module, multiple per runoff module)
* Mines (special area module)
| style="background: #FFF7F5; vertical-align: top" |Types that can be represented:

* General subcat vegetation
* Impervious area
* Higher ET vegetation (forest, tree plantation, alien veg)
* Irrigated crops

Only one area (one type) of each of these broad classes can be represented within a given subcat.

| style="background: #F5FFF5; vertical-align: top" |No limit on number of HRUs (hence cover types) per subcat.
| style="background: #FFFFF5; vertical-align: top" |No limit on number of HRUs or cover types per subcat.

| style="background: #F5FCFF; vertical-align: top" |No limit to number of cover types.

| style="background: #F5F8FF; vertical-align: top" |No limit to number of cover types.

|}
[[#Units - pg top|Back to top of page]]
 
 

=== Soils & unsaturated zone (UZ) material: spatial distribution, vertical layers, connections ===

{| class="wikitable"
! scope="col" style="width:10%" | Factor
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
(Sami GW)
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
(Hughes GW)
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed, more conceptual]]
! scope="col" style="background: #CEDAF2; width:15%" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed, more physical]]
|-
| rowspan="2" style="vertical-align: top" |

'''Spatial units for distribution of soil types / properties'''

| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''Runoff modules & irrigation modules'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''Subcatchments'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |[[Terminology#hru anchor|'''HRUs''']]
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |[[Terminology#hru anchor|'''HRUs''']]
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''Soil type polygons applied to grid cells & ‘Interflow reservoir’ extent polygons'''
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |'''Soil type polygons applied to grid cells'''
|-
| style="background: #FFF5FA; vertical-align: top" |Each ‘runoff module’ can have its own soil moisture store & ‘percolation storage’ properties.

Afforestation & alien veg modules use the soil of the runoff module they are linked to / part of.

Irrigation modules have their own soil properties.
| style="background: #FFF7F5; vertical-align: top" |Each subcat can have its own soil moisture store properties.
| style="background: #F5FFF5; vertical-align: top" |Each HRU can have its own soil properties

| style="background: #FFFFF5; vertical-align: top" |Each HRU can have its own soil properties.

HRUs are assigned soil types using an input soil type map. Properties are input by soil type. Individual HRU soil properties can by modified.
| style="background: #F5FCFF; vertical-align: top" |Each grid cell is assigned a soil type using an input soil type map. 

Interflow reservoir ‘type’ extents are input as a map (boundaries do not need to align with soil types or subcatchments)
| style="background: #F5F8FF; vertical-align: top" |Each grid cell is assigned a soil type using an input soil type map. 

|-
| rowspan="2" style="vertical-align: top" |'''Vertical layers in soil or UZ profile'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''2 Layers'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''1 Layer'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''2 Layers'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''11 Layers (max)'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''2(3) Layers*'''
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |'''Unlimited Layers'''
|-
| style="background: #FFF5FA; vertical-align: top" |A runoff modules has 2 ‘UZ’ layers:

* Soil moisture storage
* Percolation lag storage
| style="background: #FFF7F5; vertical-align: top" |A subcat has a single soil moisture storage unit.
| style="background: #F5FFF5; vertical-align: top" |An HRU has 2 soil layers:

* A horizon 
* B horizon

Both in root zone.
| style="background: #FFFFF5; vertical-align: top" |A soil type can have up to 10 layers (user input layers).

Profile can extend below root zone.

Each HRU also has a vadose zone (lag storage) ‘layer’ below the soil profile
| style="background: #F5FCFF; vertical-align: top" |A soil type has vertically uniform parameters (no layers), but each model grid cell has 2 computational UZ layers:

* Upper layer (root zone)
* Lower layer (below roots)

Interflow reservoirs are storage units fed by all overlying grid cells
| style="background: #F5F8FF; vertical-align: top" |A soil type can have an unlimited number of layers (user input layers).

Profile can extend below root zone.
|-
| rowspan="2" style="vertical-align: top" |'''Surface runoff routing'''
(w.r.t. spatial units)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''Parallel*'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |(n/a)
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''Parallel'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''Parallel'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''Series or parallel'''
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |'''Series'''
|-
| style="background: #FFF5FA; vertical-align: top" |Parallel for runoff modules & irrigation modules.

Other special area modules modify runoff module flow
| style="background: #FFF7F5; vertical-align: top" |Subcatchment scale
| style="background: #F5FFF5; vertical-align: top" |Parallel from HRUs in subcat
| style="background: #FFFFF5; vertical-align: top" |Parallel from HRUs in subcat
| style="background: #F5FCFF; vertical-align: top" |Across a series of mapped flow zones within a subcat

OR each zone in parallel
| style="background: #F5F8FF; vertical-align: top" |Across grid cells based on elevation.
|-
| rowspan="2" style="vertical-align: top" |'''Interflow routing''' (w.r.t. spatial units)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''Parallel*'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |(n/a)
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''Parallel'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''Parallel'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''Series'''
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |'''Series'''
|-
| style="background: #FFF5FA; vertical-align: top" |Parallel for runoff modules & irrigation modules

Other special area modules modify runoff module flow
| style="background: #FFF7F5; vertical-align: top" |Subcatchment scale
| style="background: #F5FFF5; vertical-align: top" |Parallel from HRUs in subcat
| style="background: #FFFFF5; vertical-align: top" |Parallel from HRUs in subcat
| style="background: #F5FCFF; vertical-align: top" |Through a series of interflow reservoirs in a subcat
| style="background: #F5F8FF; vertical-align: top" |Through grid cells based on head.
|-
| rowspan="2" style="vertical-align: top" |'''Capillary rise: 2-way connection to aquifer'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |Yes*
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |Yes*
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |No*
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |Yes*
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |'''Yes'''
|-
| style="background: #FFF5FA; vertical-align: top" |Only in riparian zone sub-area of runoff module; represented as ET deficit met by GW
| style="background: #FFF7F5; vertical-align: top" |Only in riparian zone sub-area of subcat; represented as ET deficit met by GW
| style="background: #F5FFF5; vertical-align: top" |Water in the baseflow store of an ACRU4 HRU cannot move into the soil profile or be used for ET in the same HRU.

BUT when upland HRU baseflow is routed to riparian HRU soil this is similar to GW access in riparian zones in subcat scale models....
| style="background: #FFFFF5; vertical-align: top" |Represented as ET deficit met by GW; access can be set by HRU
| style="background: #F5FCFF; vertical-align: top" |Only for grid cells in riparian zone (lowest interflow zone); represented as ET deficit met by GW
| style="background: #F5F8FF; vertical-align: top" |
|}
[[#Units - pg top|Back to top of page]]
 
 

=== Aquifers: spatial distribution, vertical layers, connections ===
{| class="wikitable"
! scope="col" style="width:10%" | Factor
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
(Sami GW)
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
(Hughes GW)
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed, more conceptual]]
! scope="col" style="background: #CEDAF2; width:15%" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed, more physical]]
|-
| rowspan="2" style="vertical-align: top" |

'''Spatial units for distribution of aquifer types / properties'''

| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''Runoff modules'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''Subcatchments'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |[[Terminology#hru anchor|'''HRUs''']]
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''Subcatchments/HRUs*'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''‘Baseflow reservoir’ extent polygons'''
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |'''Layer & lense polygons applied to grid cells'''
|-
| style="background: #FFF5FA; vertical-align: top" |Each runoff module can have its own aquifer properties.
| style="background: #FFF7F5; vertical-align: top" |Each subcatchment module can have its own aquifer properties.

There is a spatial division into two slope sections, riparian & upslope, for process calculation, but these don’t have separate property parameters.

| style="background: #F5FFF5; vertical-align: top" |Each HRU can have its own ‘baseflow storage’ properties.
| style="background: #FFFFF5; vertical-align: top" |Aquifer GW storage & outflow is calculated per subcat, but properties can be input per HRU to model capillary rise
| style="background: #F5FCFF; vertical-align: top" |‘Baseflow reservoir’ type (aquifer type) spatial extents are input as a map (boundaries do not need to align with other inputs)
| style="background: #F5F8FF; vertical-align: top" |Each grid cell has a layered profile of aquifer material types based on the layers and lenses it overlies. 

Property ‘layers’ cover entire the model domain, can have spatially variable thickness (grid input). ‘Lenses’ occur in certain areas (map input) also with variable thickness. 
|-
| rowspan="2" style="vertical-align: top" |'''Vertical layers within aquifers'''

| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''1 Layer'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''1 Layer'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''1 Layer'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''2 Layers'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''2 Layers'''
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |'''Unlimited Layers'''
|-
| style="background: #FFF5FA; vertical-align: top" |A runoff module has one aquifer unit
| style="background: #FFF7F5; vertical-align: top" |A subcat has one aquifer store.

There a two linked horizontal sub sections, but no vertical divisions. 
| style="background: #F5FFF5; vertical-align: top" |An HRU has one ‘baseflow’ storage.
| style="background: #FFFFF5; vertical-align: top" |A subcat has 2 aquifer units:

* shallow aquifer (outflow to channel)
* deep aquifer (no outflow)
| style="background: #F5FCFF; vertical-align: top" |A mapped ‘baseflow reservoir’ type can have 2 internal storage units with different parameters.
| style="background: #F5F8FF; vertical-align: top" |No limit on the aquifer material layers & lenses that can be input.

Calculation grid layers can be set differently to the aquifer property layers. In this case thickness-averaged parameters are assigned.
|-
| rowspan="2" style="vertical-align: top" |'''GW flow routing between spatial units'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |(Limited)
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |No
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |No
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |'''Yes'''
|-
| style="background: #FFF5FA; vertical-align: top" |GW flow between subcats
| style="background: #FFF7F5; vertical-align: top" |GW flow between subcats
| style="background: #F5FFF5; vertical-align: top" |No GW flow between subcats

Upslope HRU baseflow can be routed to riparian HRU soil within a subcat

No other HRU GW exchanges included
| style="background: #FFFFF5; vertical-align: top" |No GW flow between subcats
| style="background: #F5FCFF; vertical-align: top" |No GW flow between subcats

No GW flow between ‘baseflow reservoirs’ (aquifer types) within subcat
| style="background: #F5F8FF; vertical-align: top" |GW flow between grid cells
|-
| rowspan="2" style="vertical-align: top" |'''GW flow routing vertical aquifer units/layers'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |(n/a – single unit)
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |(n/a – single unit)
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |(n/a – single unit)
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |No
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |No
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |'''Yes'''
|-
| style="background: #FFF5FA; vertical-align: top" |
| style="background: #FFF7F5; vertical-align: top" |
| style="background: #F5FFF5; vertical-align: top" |
| style="background: #FFFFF5; vertical-align: top" |Shallow & deep aquifers each receive a portion of total recharge and do not interact (more like units than vertical layers)
| style="background: #F5FCFF; vertical-align: top" |The 2 units in a mapped baseflow reservoir type each receive a portion of total recharge and do not interact (more like units than vertical layers)
| style="background: #F5F8FF; vertical-align: top" |GW can flow between vertical layers based on head and conductivity
|-
| rowspan="2" style="vertical-align: top" |'''GW flow out of model domain (catchment)'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |No
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |Yes*
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |No*
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |'''Yes'''
|-
| style="background: #FFF5FA; vertical-align: top" |
| style="background: #FFF7F5; vertical-align: top" |
| style="background: #F5FFF5; vertical-align: top" |
| style="background: #FFFFF5; vertical-align: top" |Only deep aquifer can have GW flow the model. (Deep aquifer does not feed channel, can be pumped)
| style="background: #F5FCFF; vertical-align: top" |Recharge can be allocated to ‘dead storage’ which has a similar impact.
| style="background: #F5F8FF; vertical-align: top" |GW outflow boundary condition must be set-up
|-
| style="vertical-align: top" |'''GW abstraction included'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |No
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |'''Yes'''
|-
| style="vertical-align: top" |'''Number of abstraction points allowed'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |1 per runoff module
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |2 total per subcat: 1 per subcat aquifer section:

1 upslope & 1 riparian
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(n/a)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |2 total per subcat: 1 per subcat aquifer unit:

1 shallow & 1 deep
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |Flexible number, location, & abstraction depth
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |Flexible number, location, & abstraction depth
|-
| style="vertical-align: top" |'''GW abstraction routing options'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |Removed from model
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |Removed from model
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(n/a)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |Applied as irrigation, or

Removed from model
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |Applied as irrigation, or

Removed from model
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |Applied as irrigation, or

Removed from model
|}
[[#Units - pg top|Back to top of page]]
 
 

=== River channels: units & layout, connections with surface & subsurface land units ===
{| class="wikitable"
! scope="col" style="width:10%" | Factor
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
(Sami GW)
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
(Hughes GW)
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed, more conceptual]]
! scope="col" style="background: #CEDAF2; width:15%" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed, more physical]]
|-
| rowspan="2" style="vertical-align: top" |'''Number of channel units by subcatchment'''

(or catchment)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''Flexible'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''1 per subcat'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''Flexible'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''1 per subcat*'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''Flexible'''
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |'''Flexible'''
|-
| style="background: #FFF5FA; vertical-align: top" |Channels represented with channel modules in a network.

No limit to number of channel modules.

Multiple connection configurations possible: max 10 input & 10 output routes per channel module.
| style="background: #FFF7F5; vertical-align: top" |Subcat channel receives flow from the channels of upstream subcats & flows out to channel of downstream subcat.
| style="background: #F5FFF5; vertical-align: top" |Multiple channel units can be included in a network in a subcat. In non-headwater subcats a channel is needed to receive flow from upstream subcats & route to the subcat’s outflow node.

Each special riparian HRU & wetland HRU needs its own linked channel unit.

No limit to the number of channel units included.
| style="background: #FFFFF5; vertical-align: top" |Each subcat has one ‘main channel’ that receives flows from main channels of any upstream subcats & flows out to channel of downstream subcat. Each subcat also has one conceptual ‘tributary’ that routes HRU runoff to main channel. This allows for additional delay & loss to aquifer if relevant.
| style="background: #F5FCFF; vertical-align: top" |Channels are represented as a spatially explicit network of reaches between calculation nodes (cross sections) at specified intervals. Reaches with nodes mapped in subcat can exchange water with that subcat.

No limits to numbers of river branches or of reach units that can be in a subcat.
| style="background: #F5F8FF; vertical-align: top" |Channels are represented as a spatially explicit network of reaches between calculation nodes (cross sections) at specified intervals. Reaches exchange water with grid cells that border them.

No limits to numbers of river branches or of reach units in a model. There cannot be two reaches in one grid cell (node spacing compatible with grid)
|-
| rowspan="2" style="vertical-align: top" |'''Surface flow from land units into channel'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |'''Yes'''
|-
| style="background: #FFF5FA; vertical-align: top" |Runoff, irrigation, mine modules to a linked channel module
| style="background: #FFF7F5; vertical-align: top" |Subcat to its channel
| style="background: #F5FFF5; vertical-align: top" |HRU to linked channel in subcat
| style="background: #FFFFF5; vertical-align: top" |All HRUs in subcat to tributary then subcat main channel
| style="background: #F5FCFF; vertical-align: top" |‘Overland flow’ zones in subcat to reaches in subcat. Series routing: only from most downslope zone
| style="background: #F5F8FF; vertical-align: top" |Grid cells bordering a reach to that reach (if flow is over bank height)
|-
| rowspan="2" style="vertical-align: top" |'''Flow from channel onto land surface''' (overbank flooding)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(to wetland unit only)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(to wetland unit only)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(to special riparian HRUs & wetland HRUs only)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |No
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |'''Yes'''
|-
| style="background: #FFF5FA; vertical-align: top" |A wetland can be included within a channel module.
| style="background: #FFF7F5; vertical-align: top" |A wetland can be included at downstream end of subcat.
| style="background: #F5FFF5; vertical-align: top" |Special HRUs for riparian areas and wetlands can be included. Each needs its own linked channel unit with an overflow threshold.
| style="background: #FFFFF5; vertical-align: top" |A wetland can be included in a subcat, but it is not on the ‘main channel’ or fed by overflow. 
| style="background: #F5FCFF; vertical-align: top" |Channel flow over capacity is routed onto floodplain surface. This water can infiltrate into flooded grid cells.
| style="background: #F5F8FF; vertical-align: top" |Channel reach to bordering grid cells
|-
| rowspan="2" style="vertical-align: top" |'''Interflow into channel'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |'''Yes*'''
|-
| style="background: #FFF5FA; vertical-align: top" |Runoff, irrigation, mine modules to a linked channel module
| style="background: #FFF7F5; vertical-align: top" |Subcat to its channel
| style="background: #F5FFF5; vertical-align: top" |HRU to a linked channel in subcat
| style="background: #FFFFF5; vertical-align: top" |All HRUs in subcat to tributary then subcat main channel
| style="background: #F5FCFF; vertical-align: top" |Most downslope ‘interflow reservoir’ in subcat to reaches in subcat.
| style="background: #F5F8FF; vertical-align: top" |Perched, temporarily saturated layers (‘interflow’) handled in ‘saturated zone’. A channel can receive water from such a layer
|-
| rowspan="2" style="vertical-align: top" |'''Flow from channel into unsaturated zone''' (transmission loss)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |No
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |No
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |No
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''Yes*'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |No
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |'''Yes*'''
|-
| style="background: #FFF5FA; vertical-align: top" |Channel transmission loss leaves the model
| style="background: #FFF7F5; vertical-align: top" |Channel transmission loss only to aquifer
| style="background: #F5FFF5; vertical-align: top" |No channel transmission loss
| style="background: #FFFFF5; vertical-align: top" |Main channel transmission loss goes to ‘bank storage’ – accessible for ET, not part of subcat aquifers. 
| style="background: #F5FCFF; vertical-align: top" |
| style="background: #F5F8FF; vertical-align: top" |Perched, temporarily saturated layers (‘interflow’) handled in ‘saturated zone’. A channel can lose water to such a layer.
|-
| rowspan="2" style="vertical-align: top" |'''Groundwater (GW) flow into channel'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |'''Yes'''
|-
| style="background: #FFF5FA; vertical-align: top" |Runoff module to a linked channel module
| style="background: #FFF7F5; vertical-align: top" |Subcat downslope aquifer portion to subcat channel
| style="background: #F5FFF5; vertical-align: top" |HRU to a linked channel in subcat
| style="background: #FFFFF5; vertical-align: top" |Subcat shallow aquifer to channel (not from the deep aquifer)
| style="background: #F5FCFF; vertical-align: top" |All ‘baseflow reservoirs’ in subcat to reaches in subcat
| style="background: #F5F8FF; vertical-align: top" |Saturated layers of grid cells bordering a reach to that reach
|-
| rowspan="2" style="vertical-align: top" |'''Flow from channel into GW'''

(transmission loss)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |No
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |No
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |No*
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |'''Yes'''
|-
| style="background: #FFF5FA; vertical-align: top" |Channel transmission loss leaves the model
| style="background: #FFF7F5; vertical-align: top" |Channel to subcat aquifer (downslope portion)
| style="background: #F5FFF5; vertical-align: top" |No channel transmission loss
| style="background: #FFFFF5; vertical-align: top" |Main channel transmission loss does not enter subcat aquifer. Tributary can lose to subcat shallow aquifer
| style="background: #F5FCFF; vertical-align: top" |Reach in subcat to baseflow reservoir in subcat
| style="background: #F5F8FF; vertical-align: top" |Reach to saturated layers of grid cells bordering it
|-
| style="vertical-align: top" |'''Abstractions:''' water leave model
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |'''Yes'''
|-
| style="vertical-align: top" |'''Transfers:''' between channels
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |No
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |No
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |Yes*

(complex set-up)
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |Yes*

(complex set-up)
|-
| style="vertical-align: top" |'''External water inputs'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |'''Yes'''
|-
| style="vertical-align: top" |'''Abstraction, transfer, external input locations'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''Flexible'''

(avoiding circular routing)
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''Subcat channel outlet''' (above reservoir)
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''Flexible'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''Subcat main channel outlet''' (above reservoir)
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''Flexible'''
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |'''Flexible'''
|}
[[#Units - pg top|Back to top of page]]
 
 

=== Water bodies (dams, reservoirs, lakes): unit types, inflow & outflow connections ===
{| class="wikitable"
! scope="col" style="width:10%" | Factor
! scope="col" style="background: #F2CEE0; width:18%" |WRSM-Pitman
(Sami GW)
! scope="col" style="background: #F2D4CE; width:18%" |SPATSIM-Pitman
(Hughes GW)
! scope="col" style="background: #CEF2CE; width:18%" |ACRU4
! scope="col" style="background: #F2F2CE; width:18%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:18%" |MIKE-SHE,
All approaches
|-
| style="vertical-align: top" |'''Water body unit types'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''1 type*:'''

'''Reservoir module'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''2 types*:'''

'''Reservoir & Dam'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''1 type:'''

'''Dam'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''3 types*:'''

'''Reservoir, Pond, Depression'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''2 approaches: explicit bathymetry+wall, storage unit'''
|-
| style="vertical-align: top" |
| style="background: #FFF5FA; vertical-align: top" |Wetland unit also modelled as water body (see below)
| style="background: #FFF7F5; vertical-align: top" |Wetland unit also modelled as water body (see below)
| style="background: #F5FFF5; vertical-align: top" |
| style="background: #FFFFF5; vertical-align: top" |Wetland unit also modelled as water body (see below)
| style="background: #F5FCFF; vertical-align: top" |
|-
| style="vertical-align: top" |'''Number of units allowed per subcatchment'''

(or catchment)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''Flexible'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''1 Reservoir per subcat'''

'''& 1 Dam per subcat'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''Flexible'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''1 Reservoir per subcat'''

'''& 1 Pond per subcat'''

'''& multiple Depressions'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''Flexible'''
|-
| style="vertical-align: top" |'''Flows into water body units'''
| style="background: #FFF5FA; vertical-align: top" |Reservoir module can receive:
*Rain
*Flow/transfers from up to 5 other modules routed to it (land areas, channels, & other reservoir modules) - from runoff modules it can receive a set proportion of total total runoff.
*External source input routed to it

A reservoir receiving a set proportion of runoff from a runoff-module can be thought of as internal to the subcat that the runoff module represents. If it receives all the runoff, it’s at the subcat outlet.
| style="background: #FFF7F5; vertical-align: top" |A '''reservoir''' is on the subcat channel at the outlet, so receives:
*Rain
*Local subcat runoff
*Channel flow from upstream

A '''dam''' is internal to a subcat & receives:

*Set proportion of total subcat runoff

| style="background: #F5FFF5; vertical-align: top" |A dam can receive:
*Rain
*Flow from channels & HRUs routed to it
*External source input routed to it
| style="background: #FFFFF5; vertical-align: top" |A '''reservoir''' is on the subcat channel at the outlet, so can receive:
*Rain
*Local subcat runoff
*Channel flow from upstream subcats
*Transfers from channels & reservoirs in other subcats

A '''pond''' is internal to a subcat & receives:

*Rain
*Set proportion of total subcat runoff

A '''depression/pothole''' is ponded water ON a specified HRU & receives:

*Rain
*Set proportion of runoff from other specified HRUs in same subcat
| style="background: #F5FCFF; vertical-align: top" |Waterbodies are handled in the channel hydraulic model (MIKE-Hydro). Waterbody bathymetry cross sections and the dimensions of a dam wall can be input in a reach of the channel. The reach could receive:
*Rain
*Runoff from bordering units (cells, zones)
*Channel flow from upstream reach
*Transfers from other reaches
*External point source inputs

 
Alternatively a simple 'storage' volume unit can be added to the end of a channel branch, which receives flow from the branch.
|-
| style="vertical-align: top" |'''Flows out of water body units'''
| style="background: #FFF5FA; vertical-align: top" |Water can leave a reservoir module as:
*Evaporation
*Overflow & controlled release to linked channel module downstream
*Withdrawal to linked irrigation modules
*Withdrawal transferred other reservoirs & channels
*Withdrawal removed from model

A reservoir can have a maximum of 5 outflow routes.
| style="background: #FFF7F5; vertical-align: top" |Water can leave '''reservoir''' as:
*Evaporation
*Overflow & controlled release to downstream subcat channel
*Withdrawal removed from model

Water can leave a '''dam''' as:

*Overflow to subcat channel
*Withdrawal to subcat irrigation sub-area
| style="background: #F5FFF5; vertical-align: top" |Water can leave a dam as:
*Evaporation
*Overflow, controlled release, & seepage to linked downstream channel or subcat outflow node
*Withdrawal to linked irrigation HRU
*Withdrawal removed from model
| style="background: #FFFFF5; vertical-align: top" |Water can leave a '''reservoir''' as:
*Evaporation
*Overflow & controlled release to downstream subcat channel
*Seepage to subcat aquifer
*Withdrawal to linked irrigation HRU
*Withdrawal transferred other reservoirs & channels
*Withdrawal removed from model

Water can leave a '''pond''' as:

*Evaporation
*Overflow & controlled release to downstream subcat channel
*Seepage to subcat aquifer

Water can leave a '''depression''' water body as:

*Evaporation
*Overflow & controlled releases to subcat main channel
*Seepage to local HRU soil

(local HRU also has: veg ET & subsurface runoff generation)
| style="background: #F5FCFF; vertical-align: top" |Water can leave a reach storage created with bathymetry & a wall structure as:
*Evaporation
*Overflow & controlled release to downstream reach
*Seepage to bordering unit groundwater
*Withdrawal to linked irrigation area
*Withdrawal transferred other reservoirs & channels
*Withdrawal removed from model

Water can leave a ‘storage’ volume unit as:

*Overflow to a downstream branch
|}
[[#Units - pg top|Back to top of page]]
 
 

=== Wetlands: units, location, surface & subsurface flow connections ===
'Wetlands' are challenging to generalise about because a diverse range of hydro-geomorphic settings can give rise to a frequently saturated area. The modelling tools take different approaches to representing wetlands, as described in more detail on a dedicated [[Wetlands|wetlands page, here]]. The table below is a brief overview of the connectivity of specific wetland modules or units in the tools. For some wetland types, other approaches besides the specifically named 'wetland' modules may actually be more relevant (e.g. riparian zone representation in various tools, 'riparian HRU' in ACRU4, 'depression/pothole' in SWAT2012)
 
{| class="wikitable"
! scope="col" style="width:10%" | Component
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
(Sami GW)
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
(Hughes GW)
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed, more conceptual]]
! scope="col" style="background: #CEDAF2; width:15%" |MIKE-SHE,
[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed, more physical]]
|-
| style="vertical-align: top" |'''Specific 'wetland' model unit'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |

'''Yes*'''

(unit within channel module)
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |No

(wetland conditions to be re-created with topography, channel, aquifer, soil, & cover set-up)
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |No

(wetland conditions to be re-created with topography, channel, aquifer, soil, & cover set-up)
|-
| style="vertical-align: top" |'''Location of wetland'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |On channel,

flexible location in network
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |On subcat channel,

at subcat outlet
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |HRU + associated channel, flexible location in network
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |Internal to subcat,

not on main channel
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |Flexible
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |Flexible
|-
| style="vertical-align: top" |'''Surface water flow into wetland'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |Channel flow over threshold (or all)
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |Channel flow over threshold (or all)
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |Channel flow over threshold (or all)
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |Proportion of subcat surface runoff
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |Surface runoff from upslope zone &/or channel overflow
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |Surface runoff from upslope cells &/or channel overflow
|-
| style="vertical-align: top" |'''Wetland outflow to surface water'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |Outflow to channel module
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |Outflow to subcat channel outlet
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |Outflow routed in network

(to channel, dam, or subcat outlet node)
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |Outflow to subcat main channel
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |Outflow to downslope zones or to channel possible
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |Outflow to downslope cells &/or to channel possible
|-
| style="vertical-align: top" |'''Groundwater flow into wetland'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |No
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |No
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |No
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |Proportion of subcat subsurface runoff
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |Capillary rise only
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |Capillary rise & GW flow possible
|-
| style="vertical-align: top" |'''Wetland seep to groundwater'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |No
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |No
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |Wetland HRU has own ‘baseflow store’
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |Seep to subcat aquifer
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |Can percolate & recharge 'baseflow reservoir'
| style="background: #F5F8FF; vertical-align: center; text-align:center;" |Can percolate & recharge aquifer layers
|}
[[#Units - pg top|Back to top of page]]
 
 

=== Irrigated areas: units, water source options ===
{| class="wikitable"
! scope="col" style="width:10%" | Component
! scope="col" style="background: #F2CEE0; width:18%" |WRSM-Pitman
(Sami GW)
! scope="col" style="background: #F2D4CE; width:18%" |SPATSIM-Pitman
(Hughes GW)
! scope="col" style="background: #CEF2CE; width:18%" |ACRU4
! scope="col" style="background: #F2F2CE; width:18%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:18%" |MIKE-SHE,
All approaches
|-
| style="vertical-align: top" |'''Irrigated area model units'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''Irrigation module'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''Irrigation sub-area within subcat'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''Irrigation HRU (special HRU)'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''HRU with irrigation set-up'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''Grid cells in 'irrigation demand areas' '''
|-
| rowspan="2" style="vertical-align: top" |'''Units (explicit crop types) per subcatchment'''

(or catchment)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''Unlimited'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''1 sub-area per subcat'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''Unlimited'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''Unlimited'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''Unlimited'''
|-
| style="background: #FFF5FA; vertical-align: top" |No limit to number of irrigation modules & all can have different properties. Each can also have multiple crop type sub-area entries: area-weighted averaging of properties is done in the model.
| style="background: #FFF7F5; vertical-align: top" |Area can be subdivided into river-fed and dam-fed, but only one irrigation demand set (hence crop type) input.
| style="background: #F5FFF5; vertical-align: top" |
| style="background: #FFFFF5; vertical-align: top" |Irrigation can be set-up for any HRU in the ‘management parameters’

Land cover input & delineation of HRUs occurs separately.
| style="background: #F5FCFF; vertical-align: top" |An ‘irrigation demand area’ map input (extents of irrigated areas by scheduling type) determines if a grid cell is irrigated.

The separate land cover map input determines the cell’s veg type/crop.
|-
| rowspan="2" style="vertical-align: top" |'''Number of irrigation water sources allowed per unit'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''1 source per module'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''2 sources per subcat:'''

'''1 source per portion of total irrigated area'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''1 source per HRU'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''Multiple sources for an HRU as scheduled'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''Multiple sources per irrigated area: switch sources with water availability'''
|-
| style="background: #FFF5FA; vertical-align: top" |
| style="background: #FFF7F5; vertical-align: top" |The subcat irrigated area can have a % that is river-fed & % dam-fed, but no one place can be fed by both sources.
| style="background: #F5FFF5; vertical-align: top" |
| style="background: #FFFFF5; vertical-align: top" |HRU irrigation schedule can be set-up with different methods & sources at different specified times. For each time entry only one water source can be selected: cannot set to switch between sources based on their water availability.
| style="background: #F5FCFF; vertical-align: top" |Multiple potential sources can be specified with an order of preference. If water supply is lacking (or licensed use amount reached) at a higher listed source, irrigation will be drawn from the next source possible in the list.
|-
| colspan="6" |'''Irrigation water source type options:'''
|-
| style="vertical-align: top" |'''''River'''''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''Yes'''
|-
| rowspan="2" style="vertical-align: top" |'''''Dams/reservoirs'''''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''Yes*'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''Yes*'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''Yes*'''
|-
| style="background: #FFF5FA; vertical-align: top" |
| style="background: #FFF7F5; vertical-align: top" |Only from ‘dam’ (fed by local runoff); NOT ‘reservoir’ (on channel; upstream inputs)
| style="background: #F5FFF5; vertical-align: top" |
| style="background: #FFFFF5; vertical-align: top" | Only 'reservoir', NOT 'ponds' or 'depressions/potholes'
| style="background: #F5FCFF; vertical-align: top" |Only from part of a channel reach (explicit bathymetry & wall), NOT simple 'storage'
|-
| style="vertical-align: top" |'''''Aquifers'''''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |No
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |No
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |No
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''Yes'''
|-
| style="vertical-align: top" |'''''External source'''''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''Yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''Yes'''
|-
| style="vertical-align: top" |'''Restrictions on source locations'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |Flexible (must be different to module receiving return flow)
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |Only sources within same subcat
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |Sources in subcat, or dams in upstream subcats
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |Flexible (not restricted to same subcat)
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |Flexible (not restricted to same subcat)
|-
| rowspan="2" style="vertical-align: top" |'''‘Return flow’ routing options'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |To any channel or reservoir module (that is not the source module)
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |To subcat channel
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |To a subcat channel, reservoir, or the outflow node
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |To subcat channel
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |Downslope cells &/or channel
|-
| style="background: #FFF5FA; vertical-align: top" |
| style="background: #FFF7F5; vertical-align: top" |Part of subcat-scale runoff handling
| style="background: #F5FFF5; vertical-align: top" |Handled same as other HRUs.
| style="background: #FFFFF5; vertical-align: top" |Handled same as other HRUs

Can add tile drains: also route to channel, changes rate
| style="background: #F5FCFF; vertical-align: top" |Handled same as other grid cells

Can add tile drains: drain to point in river, changes rate
|}
[[#Units - pg top|Back to top of page]]

Modelling tool user interfaces

2023-12-01T13:50:38Z

Julia Glenday:

The tables below compare some main features of the user interfaces of the selected modelling tools that relate to their ease of use. These include approximate comparisons of typical model run times and the computing power needed to run them, as well as how easy it is to export and view various model outputs and test different parameter value options for sensitivity analyses and/or calibration.

The combination of how long it takes to set up a model, how long it takes to run a model, how long it takes to access model outputs of interest, and how long it takes to test and refine the model all influence what can be achieved in the time that is available for a modelling projects. Some modelling tools may run very quickly, but take a relatively long time to set up and don't have an efficient way to change and test multiple parameter value options, making calibration a time consuming manual process. Other tools may take long to run, but can be set up to do a number of parameter testing runs and even scenario runs at once, allowing the modeller to attend to other work in the meantime (however they may have to do so on another computer if the model runs require a lot of computing power!).

== Interface comparison overview ==

{| class="wikitable"
! scope="col" style="width:15em" | Interface characteristic
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
|-
| style="vertical-align: vertical-align: center;" |Graphical user interface ''(vs code prompt)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Catchment map display (visualise linkages)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model run times'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Estimated model run time for a 30 year run, ~300km^2 catchment ''(Note: will depend on model set-up complexity & computing power!)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |tens of minutes
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |hours
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Computing resources needed'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Comparative rating of computing power needed to achieve workable run times.
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |light
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |light
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |light
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |medium
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |intensive (need good GPU)
|-
| colspan="6" style="background: #FFFFFF; vertical-align: vertical-align: center;" |'''Model set-up ease & efficiency'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Automated creation of model units & connections from map inputs ''(vs fully manual creation)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Input parameter values and change values for batches of models units ''(e.g., all HRUs of a cover type)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |In-built database of suggested parameter values ''(e.g., for common vegetation types, soil types, etc.)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |no
|-
| style="vertical-align: vertical-align: center;" |User can build own parameter databases for use across multiple models
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model set-up transparency''' (i.e., is it very obvious what the model is doing/assuming?) <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Interface makes the user interact with every component & parameter entry option during model set-up ''(vs having default parameter values pre-entered & not forcing user to view them)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |no
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Tool checks connection errors
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Batch runs & calibration tools''' <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Facility for batch runs, parameter sensitivity analyses, uncertainty analyses & auto-calibration
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Accessing model output''' <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for streamflow
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for water balance fluxes and stores
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |All water balance components that are calculated by the model can be exported
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Batch export of water balance fluxes for model's basic spatial units
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Automated extraction of water balance fluxes for different spatial scales ''(e.g., by cover class area, by subcatchment, full catchment)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|}


== Formats for input-output data ==

The table below gives some basic information about the file formats used for model inputs and outputs across the different modelling tools to give a general impression of what is required to work with them. This is a very rough overview and one has to work with user manuals, tutorials, and/or pre-exist demonstration models and data to understand the various formatting requirements and file types used across the inputs and outputs of a specific software tool. For large or complex model set-ups that will have many different inputs (e.g., different input rainfall timeseries for several different points across the modelled area), it is highly recommended to use coding tools like R or Python to prepare the input files as it will be time-consuming to get many files into the same specific formatting required by the modelling software and most do not have in-built conversion tools.

{| class="wikitable"
! scope="col" style="width:10%" |'''Data type'''
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE
|-
| style="vertical-align: top;" |'''Timeseries data'''
| style="background: #FFF5FA; vertical-align: top; text-align: left;" |'''Specially formatted text files (special file extensions)'''
 Monthly data with years as rows and a column for each month in a water year starting in Oct, and for some types an annual sum in an additional column. Files can be read and generated by text editors (like Notepad) outside of WRSM, even though the files do not have typical text file extensions (e.g. ".txt"). WRSM input and output file extensions show the type of data (e.g., .RAN file is a rainfall timeseries file). Data can be brought into Excel for analyses, but it is difficult to create the input file formatting within Excel. A text editor or a general coding interface like an R or Python editor can be used to achieve the needed input data timeseries.
| style="background: #FFF7F5; vertical-align: top; text-align: left;" |'''Specially formatted text files (.txt)'''
 Some flexibility on the formatting for inputs as one can specify the row/column format and date formatting in the files in the tools' input interface. Inputs can be prepared in Excel and outputs easily opened there as well.
| style="background: #F5FFF5; vertical-align: top; text-align: left;" |'''Specially formatted ASCII text files (.txt) & .DBF files'''
 Input is daily data in long-format (one date per row) in a composite file containing climate variable and observed flow inputs in specified column orders and number formats. Difficult to prepare simply in Excel, and labour intensive to prepare in a text editor (e.g, Notepad), but reasonable to prepare in a general coding programme like R or Python. Outputs are .dbf format text files which open easily in Excel.
| style="background: #FFFFF5; vertical-align: top; text-align: left;" |'''Specially formatted text files (.txt) & Access database files '''
 Daily data in long-format (one date per row) text files. Reasonable to prepare and easy to open in Excel. Outputs can also be produced in an Access database.
| style="background: #F5FCFF; vertical-align: top; text-align: left;" |'''Software-specific .dfs0 file format'''
 Dfs0 files for input must be generated within MIKE software. Data in long-format (each row is a timestep) prepared in Excel can be copy-pasted into a blank dfs0 file with the correct number of rows and data from dfs0 files can be copy-pasted into Excel. There are also batch conversion tools in MIKE that can be used to convert specifically formatted text files into dfs0 files and to convert dfs0 files into text files.
|-
| style="vertical-align: top;" |'''Spatial data'''
| style="background: #FFF5FA; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of modules: what areas will have their own modules (e.g. subcatchment delineation; special cover types to represent separately, like plantations, irrigated areas, wetlands; river reaches and dams), determine sizes and other characteristics of the modules, and how they are linked to one another.''
| style="background: #FFF7F5; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments: subcatchment delineation plus special features to represent specifically like dams, plantations, irrigated areas, wetlands), determine the sizes and other characteristics of subcatchments and special areas, and how subcatchments are linked to one another.''
| style="background: #F5FFF5; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments composed of HRUs, river reaches, & dams: subcatchment delineation, what areas will have their own HRUs (land cover types to represent individually), determine the sizes and other characteristics of the HRUs, and how units linked to one another.''
| style="background: #FFFFF5; vertical-align: top; text-align:left;" |'''Standard GIS shapefile and grid/raster files (geotif, grid) used.'''
 DEM input must be a raster. Land cover and soil type data can be input as shapefiles or rasters (see user manuals for formatting/attribute requirements). Tool-delineated subcatchments, river lines, HRUs are output as shapefiles. Hydrological predictions are not output in a spatial format. The data can be linked back to spatial units based on ID numbers manually by the user for spatial displays. (SWAT+ has developed tools for this internally...)
| style="background: #F5FCFF; vertical-align: top; text-align:left;" |'''Software-specific .dfs2 and .dfs3 file formats used in general. A few inputs allow standard shapefiles.'''
 dfs2 files are 2D gridded data. Standard GIS grids can be saved in an ASCI format in GIS software and then a MIKE tool applied to convert to dfs2. Subcatchments and landcover can be input as shapefiles. Many hydrological predictions can be output as spatial data as .dfs3 files, 3 dimensional data "cubes": a 2D grid of values (e.g. transpiration, surface water depth, soil moisture, groundwater depth) for each timestep, all in one file. These can be stepped-through or played as video in the interface. Timeseries for point locations or specified areas can be extracted. .dfs2 files can be converted to ASCI files to open in GIS software using an in-built tool.
|}

== Ease of use rating from surveyed users ==

Modelling tool user interfaces

2023-12-01T13:46:50Z

Julia Glenday: /* Interface comparison overview */

The tables below compare some main features of the user interfaces of the selected modelling tools that relate to their ease of use. These include approximate comparisons of typical model run times and the computing power needed to run them, as well as how easy it is to export and view various model outputs and test different parameter value options for sensitivity analyses and/or calibration.

The combination of how long it takes to set up a model, how long it takes to run a model, how long it takes to access model outputs of interest, and how long it takes to test and refine the model all influence what can be achieved in the time that is available for a modelling projects. Some modelling tools may run very quickly, but take a relatively long time to set up and don't have an efficient way to change and test multiple parameter value options, making calibration a time consuming manual process. Other tools may take long to run, but can be set up to do a number of parameter testing runs and even scenario runs at once, allowing the modeller to attend to other work in the meantime (however they may have to do so on another computer if the model runs require a lot of computing power!).

== Interface comparison overview ==

{| class="wikitable"
! scope="col" style="width:15em" | Interface characteristic
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
|-
| style="vertical-align: vertical-align: center;" |Graphical user interface ''(vs code prompt)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Catchment map display (visualise linkages)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model run times'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Estimated model run time for a 30 year run, ~300km^2 catchment ''(Note: will depend on model set-up complexity & computing power!)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |tens of minutes
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |hours
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Computing resources needed'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Comparative rating of computing power needed to achieve workable run times.
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |light
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |light
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |light
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |medium
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |intensive (need good GPU)
|-
| colspan="6" style="background: #FFFFFF; vertical-align: vertical-align: center;" |'''Model set-up ease & efficiency'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Automated creation of model units & connections from map inputs ''(vs fully manual creation)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Input parameter values and change values for batches of models units ''(e.g., all HRUs of a cover type)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |In-built database of suggested parameter values ''(e.g., for common vegetation types, soil types, etc.)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |no
|-
| style="vertical-align: vertical-align: center;" |User can build own parameter databases for use across multiple models
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model set-up transparency''' (i.e., is it very obvious what the model is doing/assuming?) <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Interface makes the user interact with every component & parameter entry option during model set-up ''(vs having default parameter values pre-entered & not forcing user to view them)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |no
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Tool checks connection errors
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Batch runs & calibration tools''' <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Facility for batch runs, parameter sensitivity analyses, uncertainty analyses & auto-calibration
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Accessing model output''' <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for streamflow
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for water balance fluxes and stores
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |All water balance components that are calculated by the model can be exported
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Batch export of water balance fluxes for model's basic spatial units
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Automated extraction of water balance fluxes for different spatial scales ''(e.g., by cover class area, by subcatchment, full catchment)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|}


== Formats for input-output data ==

The table below gives some basic information about the file formats used for model inputs and outputs across the different modelling tools to give a general impression of what is required to work with them. This is a very rough overview and one has to work with user manuals, tutorials, and/or pre-exist demonstration models and data to understand the various formatting requirements and file types used across the inputs and outputs of a specific software tool. For large or complex model set-ups that will have many different inputs (e.g., different input rainfall timeseries for several different points across the modelled area), it is highly recommended to use coding tools like R or Python to prepare the input files as it will be time-consuming to get many files into the same specific formatting required by the modelling software and most do not have in-built conversion tools.

{| class="wikitable"
! scope="col" style="width:10%" |'''Data type'''
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE
|-
| style="vertical-align: top;" |'''Timeseries data'''
| style="background: #FFF5FA; vertical-align: top; text-align: left;" |'''Specially formatted text files (special file extensions)'''
 Monthly data with years as rows and a column for each month in a water year starting in Oct, and for some types an annual sum in an additional column. Files can be read and generated by text editors (like Notepad) outside of WRSM, even though the files do not have typical text file extensions (e.g. ".txt"). WRSM input and output file extensions show the type of data (e.g., .RAN file is a rainfall timeseries file). Data can be brought into Excel for analyses, but it is difficult to create the input file formatting within Excel. A text editor or a general coding interface like an R or Python editor can be used to achieve the needed input data timeseries.
| style="background: #FFF7F5; vertical-align: top; text-align: left;" |'''Specially formatted text files (.txt)'''
 Some flexibility on the formatting for inputs as one can specify the row/column format and date formatting in the files in the tools' input interface. Inputs can be prepared in Excel and outputs easily opened there as well.
| style="background: #F5FFF5; vertical-align: top; text-align: left;" |'''Specially formatted ASCII text files (.txt) & .DBF files'''
 Input is daily data in long-format (one date per row) in a composite file containing climate variable and observed flow inputs in specified column orders and number formats. Difficult to prepare simply in Excel, and labour intensive to prepare in a text editor (e.g, Notepad), but reasonable to prepare in a general coding programme like R or Python. Outputs are .dbf format text files which open easily in Excel.
| style="background: #FFFFF5; vertical-align: top; text-align: left;" |'''Specially formatted text files (.txt) & Access database files '''
 Daily data in long-format (one date per row) text files. Reasonable to prepare and easy to open in Excel. Outputs can also be produced in an Access database.
| style="background: #F5FCFF; vertical-align: top; text-align: left;" |'''Software-specific .dfs0 file format'''
 Dfs0 files for input must be generated within MIKE software. Data in long-format (each row is a timestep) prepared in Excel can be copy-pasted into a blank dfs0 file with the correct number of rows and data from dfs0 files can be copy-pasted into Excel. There are also batch conversion tools in MIKE that can be used to convert specifically formatted text files into dfs0 files and to convert dfs0 files into text files.
|-
| style="vertical-align: top;" |'''Spatial data'''
| style="background: #FFF5FA; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of modules: what areas will have their own modules (e.g. subcatchment delineation; special cover types to represent separately, like plantations, irrigated areas, wetlands; river reaches and dams), determine sizes and other characteristics of the modules, and how they are linked to one another.''
| style="background: #FFF7F5; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments: subcatchment delineation plus special features to represent specifically like dams, plantations, irrigated areas, wetlands), determine the sizes and other characteristics of subcatchments and special areas, and how subcatchments are linked to one another.''
| style="background: #F5FFF5; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments composed of HRUs, river reaches, & dams: subcatchment delineation, what areas will have their own HRUs (land cover types to represent individually), determine the sizes and other characteristics of the HRUs, and how units linked to one another.''
| style="background: #FFFFF5; vertical-align: top; text-align:left;" |'''Standard GIS shapefile and grid/raster files (geotif, grid) used.'''
 DEM input must be a raster. Land cover and soil type data can be input as shapefiles or rasters (see user manuals for formatting/attribute requirements). Tool-delineated subcatchments, river lines, HRUs are output as shapefiles. Hydrological predictions are not output in a spatial format. The data can be linked back to spatial units based on ID numbers manually by the user for spatial displays. (SWAT+ has developed tools for this internally...)
| style="background: #F5FCFF; vertical-align: top; text-align:left;" |'''Software-specific .dfs2 and .dfs3 file formats used in general. A few inputs allow standard shapefiles.'''
 dfs2 files are 2D gridded data. Standard GIS grids can be saved in an ASCI format in GIS software and then a MIKE tool applied to convert to dfs2. Subcatchments and landcover can be input as shapefiles. Many hydrological predictions can be output as spatial data as .dfs3 files, 3 dimensional data "cubes": a 2D grid of values (e.g. transpiration, surface water depth, soil moisture, groundwater depth) for each timestep, all in one file. These can be stepped-through or played as video in the interface. Timeseries for point locations or specified areas can be extracted. .dfs2 files can be converted to ASCI files to open in GIS software using an in-built tool.
|}

Modelling tool user interfaces

2023-12-01T13:46:24Z

Julia Glenday: /* Formats for input-output data */

The tables below compare some main features of the user interfaces of the selected modelling tools that relate to their ease of use. These include approximate comparisons of typical model run times and the computing power needed to run them, as well as how easy it is to export and view various model outputs and test different parameter value options for sensitivity analyses and/or calibration.

The combination of how long it takes to set up a model, how long it takes to run a model, how long it takes to access model outputs of interest, and how long it takes to test and refine the model all influence what can be achieved in the time that is available for a modelling projects. Some modelling tools may run very quickly, but take a relatively long time to set up and don't have an efficient way to change and test multiple parameter value options, making calibration a time consuming manual process. Other tools may take long to run, but can be set up to do a number of parameter testing runs and even scenario runs at once, allowing the modeller to attend to other work in the meantime (however they may have to do so on another computer if the model runs require a lot of computing power!).

== Interface comparison overview ==

{| class="wikitable"
! scope="col" style="width:15em" | Interface characteristic
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
|-
| style="vertical-align: vertical-align: center;" |Graphical user interface ''(vs code prompt)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Catchment map display (visualise linkages)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model run times'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Estimated model run time for a 30 year run, ~300km^2 catchment ''(Note: will depend on model set-up complexity & computing power!)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |tens of minutes
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |hours
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Computing resources needed'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Comparative rating of computing power needed to achieve workable run times.
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |light
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |light
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |light
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |medium
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |intensive (need good GPU)
|-
| colspan="6" style="background: #FFFFFF; vertical-align: vertical-align: center;" |'''Model set-up ease & efficiency'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Automated creation of model units & connections from map inputs ''(vs fully manual creation)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Input parameter values and change values for batches of models units ''(e.g., all HRUs of a cover type)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |In-built database of suggested parameter values ''(e.g., for common vegetation types, soil types, etc.)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |no
|-
| style="vertical-align: vertical-align: center;" |User can build own parameter databases for use across multiple models
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model set-up transparency''' (i.e., is it very obvious what the model is doing/assuming?) <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Interface makes the user interact with every component & parameter entry option during model set-up ''(vs having default parameter values pre-entered & not forcing user to view them)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |no
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Tool checks connection errors
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Batch runs & calibration tools''' <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Facility for batch runs, parameter sensitivity analyses, uncertainty analyses & auto-calibration
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Accessing model output''' <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for streamflow
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for water balance fluxes and stores
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |All water balance components that are calculated by the model can be exported
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Batch export of water balance fluxes for model's basic spatial units
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Automated extraction of water balance fluxes for different spatial scales ''(e.g., by cover class area, by subcatchment, full catchment)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|}

== Formats for input-output data ==

The table below gives some basic information about the file formats used for model inputs and outputs across the different modelling tools to give a general impression of what is required to work with them. This is a very rough overview and one has to work with user manuals, tutorials, and/or pre-exist demonstration models and data to understand the various formatting requirements and file types used across the inputs and outputs of a specific software tool. For large or complex model set-ups that will have many different inputs (e.g., different input rainfall timeseries for several different points across the modelled area), it is highly recommended to use coding tools like R or Python to prepare the input files as it will be time-consuming to get many files into the same specific formatting required by the modelling software and most do not have in-built conversion tools.

{| class="wikitable"
! scope="col" style="width:10%" |'''Data type'''
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE
|-
| style="vertical-align: top;" |'''Timeseries data'''
| style="background: #FFF5FA; vertical-align: top; text-align: left;" |'''Specially formatted text files (special file extensions)'''
 Monthly data with years as rows and a column for each month in a water year starting in Oct, and for some types an annual sum in an additional column. Files can be read and generated by text editors (like Notepad) outside of WRSM, even though the files do not have typical text file extensions (e.g. ".txt"). WRSM input and output file extensions show the type of data (e.g., .RAN file is a rainfall timeseries file). Data can be brought into Excel for analyses, but it is difficult to create the input file formatting within Excel. A text editor or a general coding interface like an R or Python editor can be used to achieve the needed input data timeseries.
| style="background: #FFF7F5; vertical-align: top; text-align: left;" |'''Specially formatted text files (.txt)'''
 Some flexibility on the formatting for inputs as one can specify the row/column format and date formatting in the files in the tools' input interface. Inputs can be prepared in Excel and outputs easily opened there as well.
| style="background: #F5FFF5; vertical-align: top; text-align: left;" |'''Specially formatted ASCII text files (.txt) & .DBF files'''
 Input is daily data in long-format (one date per row) in a composite file containing climate variable and observed flow inputs in specified column orders and number formats. Difficult to prepare simply in Excel, and labour intensive to prepare in a text editor (e.g, Notepad), but reasonable to prepare in a general coding programme like R or Python. Outputs are .dbf format text files which open easily in Excel.
| style="background: #FFFFF5; vertical-align: top; text-align: left;" |'''Specially formatted text files (.txt) & Access database files '''
 Daily data in long-format (one date per row) text files. Reasonable to prepare and easy to open in Excel. Outputs can also be produced in an Access database.
| style="background: #F5FCFF; vertical-align: top; text-align: left;" |'''Software-specific .dfs0 file format'''
 Dfs0 files for input must be generated within MIKE software. Data in long-format (each row is a timestep) prepared in Excel can be copy-pasted into a blank dfs0 file with the correct number of rows and data from dfs0 files can be copy-pasted into Excel. There are also batch conversion tools in MIKE that can be used to convert specifically formatted text files into dfs0 files and to convert dfs0 files into text files.
|-
| style="vertical-align: top;" |'''Spatial data'''
| style="background: #FFF5FA; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of modules: what areas will have their own modules (e.g. subcatchment delineation; special cover types to represent separately, like plantations, irrigated areas, wetlands; river reaches and dams), determine sizes and other characteristics of the modules, and how they are linked to one another.''
| style="background: #FFF7F5; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments: subcatchment delineation plus special features to represent specifically like dams, plantations, irrigated areas, wetlands), determine the sizes and other characteristics of subcatchments and special areas, and how subcatchments are linked to one another.''
| style="background: #F5FFF5; vertical-align: top; text-align:left;" |'''N/A''' (Spatial data is not ''directly'' input into the software)
''Spatial data must be interpreted outside of the tool to decide on how to set-up the network of subcatchments composed of HRUs, river reaches, & dams: subcatchment delineation, what areas will have their own HRUs (land cover types to represent individually), determine the sizes and other characteristics of the HRUs, and how units linked to one another.''
| style="background: #FFFFF5; vertical-align: top; text-align:left;" |'''Standard GIS shapefile and grid/raster files (geotif, grid) used.'''
 DEM input must be a raster. Land cover and soil type data can be input as shapefiles or rasters (see user manuals for formatting/attribute requirements). Tool-delineated subcatchments, river lines, HRUs are output as shapefiles. Hydrological predictions are not output in a spatial format. The data can be linked back to spatial units based on ID numbers manually by the user for spatial displays. (SWAT+ has developed tools for this internally...)
| style="background: #F5FCFF; vertical-align: top; text-align:left;" |'''Software-specific .dfs2 and .dfs3 file formats used in general. A few inputs allow standard shapefiles.'''
 dfs2 files are 2D gridded data. Standard GIS grids can be saved in an ASCI format in GIS software and then a MIKE tool applied to convert to dfs2. Subcatchments and landcover can be input as shapefiles. Many hydrological predictions can be output as spatial data as .dfs3 files, 3 dimensional data "cubes": a 2D grid of values (e.g. transpiration, surface water depth, soil moisture, groundwater depth) for each timestep, all in one file. These can be stepped-through or played as video in the interface. Timeseries for point locations or specified areas can be extracted. .dfs2 files can be converted to ASCI files to open in GIS software using an in-built tool.
|}

Modelling tool user interfaces

2023-12-01T10:39:23Z

Julia Glenday: /* Formats for input-output data */

Modelling tool user interfaces

2023-12-01T10:35:16Z

Julia Glenday: /* Formats for input-output data */

Modelling tool user interfaces

2023-12-01T10:14:43Z

Julia Glenday: /* Formats for input-output data */

Modelling tool user interfaces

2023-12-01T10:13:24Z

Julia Glenday:

Modelling tool capability overview

2023-12-01T09:59:28Z

Julia Glenday: /* Intended uses & development focuses summary */

A set of commonly used modelling tools in South Africa was reviewed for the [[Model inter-comparison study|WRC “Critical catchment model inter-comparison and model use guidance development” project]].

This set included major tools developed in South Africa: ACRU and the Pitman model-based tools, WRSM-Pitman and SPATSIM-Pitman. It also included two tools that were developed in the northern hemisphere, but have been used in South Africa and globally: SWAT and MIKE-SHE. Locally developed tools can have certain advantages from being designed with the South African context in mind, both in terms of local data availability and in terms of local climate characteristics, ecosystems, soils, geologic types, and land and water management practices (e.g. landscapes with many small farm dams). SWAT and MIKE-SHE have resourced development teams behind them that continually update the tools and adapt them to make use of developing globally available data sources, such as remotely sensed data, and generally improved access to greater computing power.

This suite of tools covers a diversity of model structure and algorithm type options, but users should be aware there are many many tools available ([[Model types & tools #Table Anchor - tool examples|see more examples]])

'''The tables below summarise ''basic'' information about the tools in this set.''' These tables provide a broad overview, which may be all you need in many instances.


''More detailed information about the structural options and capabilities of the tools is given across the other tool inter-comparison pages: [[#Model units & connections|Model units & connections]], [[#Process representation across tools|Process representation]], [[#Water balance outputs across tools|Water balance outputs across tools]], [[#Modelling tool user interfaces|User interfaces]], [[#Documentation & support across tools|Documentation & support]], and [[#Applying tools in specific use cases|Specific use cases (e.g. irrigation, farm dams, groundwater pumping, riparian zones, wetlands)]].''

== Modelling software tool background & versions covered ==
{| class="wikitable"
! scope="col" style="width:15em" | Characteristic
! scope="col" style="background: #F2CEE0; width:15em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:15em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:15em" |ACRU
! scope="col" style="background: #F2F2CE; width:15em" |SWAT
! scope="col" style="background: #CEE6F2; width:15em" |MIKE-SHE
|-
| style="vertical-align: top" |'''Developed in South Africa'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |yes
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |yes
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |yes
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |no
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |no
|-
| style="vertical-align: center;" |'''Current curator / developer'''
| style="background: #FFF5FA; vertical-align: center;" |Bailey & Pitman Water Resources Ltd
| style="background: #FFF7F5; vertical-align: center;" |Rhodes University, Institute of Water Resources (IWR)
| style="background: #F5FFF5; vertical-align: center;" |University of KwaZulu Natal, Centre for Water Resources Research (UKZN-CWRR)
| style="background: #FFFFF5; vertical-align: center;" |Texas A&M University & US Department of Agriculture (USDA)
| style="background: #F5FCFF; vertical-align: center;" |Danish Hydrologic Institute (DHI)
|-
| style="vertical-align: center;" |'''Free to access'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |yes
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |yes
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |yes
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |yes
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |no*

free student licenses & free/reduced research licenses by arrangement
|-
| style="vertical-align: center" |'''Version reviewed in wiki'''
| style="background: #FFF5FA; vertical-align: center" |WRSM-Pitman version 2.9
| style="background: #FFF7F5; vertical-align: center" |SPATSIM GWv3 Global Options Threaded model
| style="background: #F5FFF5; vertical-align: center" |ACRU 4
| style="background: #FFFFF5; vertical-align: center" |SWAT2012; ArcSWAT2012
| style="background: #F5FCFF; vertical-align: center" |MIKE-SHE & MIKE Hydro River, version 2019 & 2020
|-
| style="vertical-align: top" |'''Reference documents consulted'''
([[Modelling tool documentation|see documentation links page]])
| style="background: #FFF5FA; vertical-align: top" |'''Theory manual:'''

Bailey, A.K. (2015). ''WRSM2000/Pitman: Water Resources Simulation Model for Windows - Theory Manual'' (Water Research Commission).

'''User manual:'''

Bailey, A.K., and Pitman, W.V. (2016). ''WRSM/Pitman User’s Manual: WR2012 Volume 7'' (Water Research Commission).
| style="background: #FFF7F5; vertical-align: top" |'''Theory documentation:'''

Hughes, D.A. (2004). Incorporating groundwater recharge and discharge functions into an existing monthly rainfall–runoff model. ''Hydrological Sciences Journal'' 49.

Hughes, D.A. (2013). A review of 40 years of hydrological science and practice in southern Africa using the Pitman rainfall-runoff model. ''Journal of Hydrology'' 501, 111–124.

Kapangaziwiri, E. (2007). ''Revised parameter estimation methods for the Pitman monthly rainfall-runoff model''. MSc. Rhodes University.

'''User manual:'''

Hughes, D.A. (2019). ''SPATSIM v3 & IWR version of the Pitman model'' (IWR Rhodes University).
| style="background: #F5FFF5; vertical-align: top" |'''Theory manual:'''

Schulze, R.E. (1995). ''Hydrology and Agrohydrology: A Text to Accompany the ACRU 3.00 Agrohydrological Modelling System'' (Water Research Commission).

'''User manuals:'''

Clark, D.J., Smithers, J.C., Thornton-Dibb, S.L.C., and Lutchminarian, A. (2012). ''ACRU 4 User Manual: User Interface & Tutorials (Volume 3 of Deployment, Maintenance, & Further Development of SPATSIM-HDSF)''

Schulze, R.E., and Davis, N.S. (2018). ''Practitioners’ Handbook for Undertaking Current and Projected Future Climate Related Risk and Vulnerability Modelling Assessments (an update of the ACRU user manual)'' (Schulze and Associates).
| style="background: #FFFFF5; vertical-align: top" |'''Theory manual:'''

Neitsch, S.L., Arnold, J.G., Kiniry, J.R., and Williams, J.R. (2011). ''Soil and Water Assessment Tool (SWAT) Theoretical Documentation, Version 2009'' (Texas Water Resources Institute, Texas A&M University).

'''User manuals:'''

Winchell, M., Srinivasan, R., Di Luzio, J., and Arnold, J. (2013). ''ArcSWAT Interface for SWAT2012: User’s Guide'' (Texas Water Resources Institute, Texas A&M University).

Arnold, J.G., Kiniry, J.R., Srinivasan, R., Williams, J.R., Haney, E.B., and Neitsch, S.L. (2012). ''Soil & Water Assessment Tool (SWAT) - Input/Output Documentation, Version 2012'' (Texas Water Resources Institute, Texas A&M University).

| style="background: #F5FCFF; vertical-align: top" |'''Theory manuals:'''

DHI (2019). ''MIKE SHE Manual, Volume 2: Reference Guide, MIKE 2019'' (Danish Hydrologic Institute).

DHI (2019). ''MIKE 1D: DHI Simulaton Engine for 1D river and urban modelling - Reference Manual, MIKE 2019'' (Danish Hydrologic Institute).

'''User manuals:'''

DHI (2019). ''MIKE SHE Manual, Volume 1: User Guide, MIKE 2019'' (Danish Hydrologic Institute).

DHI (2019). ''MIKE Hydro River: User Guide, MIKE 2019'' (Danish Hydrologic Institute).
|}

These software tools have different development histories and somewhat different focuses, however all have adapted over time, adding features that allow them to be used in more contexts and have generally overlapping intended applications ([[#Intended uses & development focuses summary|see table below]]).

The structural options and design of each tool reflect the intended applications as well as the balance struck by the developers between potentially competing concerns and goals, such as achieving parsimony, including detailed representation of land cover differences to estimate the impacts of change, maintaining ease of use of the tool, facilitating quantification of model output uncertainty, ensuring applicability in data limited contexts, etc.

For these reasons, despite the overlap in general intended uses, the tools offer some fairly different modelling strategies ([[#Model structure overview by tool: spatial & temporal scales|see table below]]). This impacts how they can be applied in specific settings (documented in more detail [[Model units & connections|here]]). For example, all the tools are capable of modelling the impacts of land use change to some degree, however WRSM-Pitman and SPATSIM-Pitman place greater limitations on the number and types of land cover that can be explicitly modelled compared to the other tools.

A summary table of some key modelling capabilities across the tools is presented [[#Modelling tool capabilities summary|below]].


[[#Capabilities - pg top|Back to top of page]]



==Intended uses & development focuses summary ==
{| class="wikitable"
! scope="col" style="width:15em" | Characteristic
! scope="col" style="background: #F2CEE0; width:15em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:15em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:15em" |ACRU4
! scope="col" style="background: #F2F2CE; width:15em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15em" |MIKE-SHE
|-
| style="vertical-align: top" |'''Specific tool development focuses'''
| style="background: #FFF5FA; vertical-align: top" |
* Flexible network for managed systems: many for options transfers, withdrawal points, reservoir locations, etc.
* Irrigated area representation
* IAP & plantation forestry water use
* Groundwater-surface water interaction (vegetation & GW pumping impacts)
| style="background: #FFF7F5; vertical-align: top" |
* Parsimony,
* Uncertainty assessment & stochastic modelling,
* Groundwater-surface water interaction (vegetation & GW pumping impacts)
| style="background: #F5FFF5; vertical-align: top" |
* Detailed land cover type representation,
* In-built local parameter database for SA vegetation & soil types, supports the level of representation
* Crop & irrigation detail,
* IAP & plantation forestry water use, including deep rooted vegetation in riparian areas
| style="background: #FFFFF5; vertical-align: top" |
* Detailed land cover type representation,
* In-built local parameter database for vegetation & soil types - North American focus, some more general, supports the level of representation
* Crop & irrigation detail with source flexibility,
* Coupling to GIS tools
| style="background: #F5FCFF; vertical-align: top" |
* Flexible spatial discretisation & distribution (climate, land cover, soil, geology, etc),
* Potential for fine scale process representation
* Crop & irrigation detail with source flexibility,
* Groundwater-surface water interaction,
* Coupled hydraulic channel model & flooding processes
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |<big> </big>'''Intended applications:'''
|-
| style="vertical-align: vertical-align: center;" |''Water balance estimation''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |''Design hydrology & flood analyses''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |''Supply planning (general)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |''Reservoir yield''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |''Irrigation planning''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |''Groundwater recharge''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |''GW-SW interactions & GW pumping impacts''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |''Land cover change impacts''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |''Climate change impacts''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: top" |'''Application limitations'''
| style="background: #FFF5FA; vertical-align: top" |
* Monthly model: not applicable for peak flow, flood assessment, design hydrology
* No irrigation direct from groundwater
| style="background: #FFF7F5; vertical-align: top" |
* Monthly model: not applicable for peak flow, flood assessment, design hydrology
* No irrigation direct from groundwater
| style="background: #F5FFF5; vertical-align: top" |
* Simplified groundwater modelling;
* Does not model groundwater pumping
| style="background: #FFFFF5; vertical-align: top" |
* Highly simplified deep groundwater modelling
| style="background: #F5FCFF; vertical-align: top" |''(None documented for the modelling system as whole, only for certain process options within it. The learning curve for its use and computing power required can pose practical limitations to its application )''
|}
[[#Capabilities - pg top|Back to top of page]]



== Model structure overview by tool: spatial & temporal scales ==
The table below gives a very basic overview of the type of model structure that can be built in each tool.
 More details about the model structure options across tools are presented [[Model units & connections|here]].
{| class="wikitable"
! scope="col" style="width:15em" | Characteristic
! scope="col" style="background: #F2CEE0; width:15em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:15em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:15em" |ACRU4
! scope="col" style="background: #F2F2CE; width:15em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15em" |MIKE-SHE
|-
| style="vertical-align: top" |'''Intended scale of catchment or modelled area'''
| style="background: #FFF5FA; vertical-align: top" |Local to regional:

no suggested min-max model size
| style="background: #FFF7F5; vertical-align: top" |Local to regional:

10-10,000’s of km2

more typical: 100-1,000’s km2
| style="background: #F5FFF5; vertical-align: top" |Field to regional:

no suggested min-max model size
| style="background: #FFFFF5; vertical-align: top" |Field to regional:

no suggested min-max model size
| style="background: #F5FCFF; vertical-align: top" |Field to regional:

no suggested min-max model size
|-
| style="vertical-align: top" |'''Timestep'''
| style="background: #FFF5FA; vertical-align: top" |Monthly*

A daily version has been developed. Limited use to-date.
| style="background: #FFF7F5; vertical-align: top" |Monthly*

A daily version has been developed. Limited use to-date
| style="background: #F5FFF5; vertical-align: top" |Daily
| style="background: #FFFFF5; vertical-align: top" |Daily, subdaily

| style="background: #F5FCFF; vertical-align: top" |Daily, subdaily*

Calculation timesteps are dynamic and vary by process. All outputs saved for a user-selected step.
|-
| style="vertical-align: top" |'''Spatial discretisation (model spatial units)'''
| style="background: #FFF5FA; vertical-align: top" |Modules connected by routes

(“runoff” modules + special area modules + channel modules create subcatchments)

| style="background: #FFF7F5; vertical-align: top" |Subcatchments + limited internal sub-area types

| style="background: #F5FFF5; vertical-align: top" |HRUs within subcatchments

| style="background: #FFFFF5; vertical-align: top" |HRUs within subcatchments
| style="background: #F5FCFF; vertical-align: top" |Grid cells (3D),

with optional calculation simplifications: surface flow modelled for zones, interflow & groundwater modelled for storage reservoirs within subcatchments.
|-
| style="vertical-align: top" |'''Suggested model unit scales'''
| style="background: #FFF5FA; vertical-align: top" |Runoff module: < 1,000 km2
| style="background: #FFF7F5; vertical-align: top" |(none listed)
| style="background: #F5FFF5; vertical-align: top" |Subcatchments: 5-50 km2

HRUs: < 30km2
| style="background: #FFFFF5; vertical-align: top" |(none listed)
| style="background: #F5FCFF; vertical-align: top" |(none listed)
|}

Despite having largely overlapping intended uses in general, there is notable diversity in model structure (table above, and more detailed coverage [[Model units & connections|here]]) and in more specific modelling capabilities in this set of tools ([[#Modelling tool capabilities summary|table below]]).

Some key points arising from the capabilities comparison are:

* No one tool had all the capabilities listed. All the tools have differing sets of advantages over the others.

* Although both based on the same predecessor model structure and sharing many basic process algorithms, WRSM-Pitman and SPATSIM Pitman have diverged in capabilities across several aspects. These differences are linked to WRSM’s modular network structure compared to the SPATSIM version’s focus on the subcatchment as the primary unit for process representation. For example, a WRSM model can include user-defined artificial water transfers between channel units in a model network, which SPATSIM does not include. SPATSIM includes an uncertainty or stochastic modelling routine, made more straightforward by the more uniform set-up of subcatchments, which WRSM does not include.

* WRSM-Pitman, SPATSIM-Pitman, and MIKE-SHE model dynamic, two-way exchange between surface water channels and groundwater aquifers (GW-SW exchange): groundwater can flow into the channel or channel water can recharge an aquifer in the model and the direction and magnitude of the exchange is calculated based on the water levels in each in every modelled timestep. 

* Only MIKE-SHE has a fully coupled hydraulic model, allowing it to model channel-floodplain interactions in more detail, including the impact of changes in channel size, shape, depth of incision, etc. Other tools can represent some aspects of overbank flooding and the fate of the flood water, but this is limited to their wetland and riparian zone modules.


[[#Capabilities - pg top|Back to top of page]]



==Modelling tool capabilities summary==
'''Important note: this capabilities summary table indicates what is ''technically possible'' within the modelling tools, but it does ''not'' cover the ''practicality and ease-of-use'' of the different features across each tool.''' 
Some things that are possible in a tool become a veritable labour of love to actually achieve, depending on the nature of the model set-up (i.e. how many subcatchments, how many HRUs, etc). 
''Example: In ACRU4, different climate inputs '''can''' be specified by HRU, to allow for spatial distribution of rainfall within a subcatchment. However operationalising this when there are many HRUs becomes very time consuming compared to simply specifying one set of climate inputs the whole subcatchment. Applying different climate inputs to different areas within a subcatchment requires manually clicking through three layers of menus each for four different climate inputs for every HRU. There is no batch-input of climate for subgroups of HRUs within a subcatchment.''
Various aspects of the user interfaces of the different tools and their implications are covered on a separate page [[Modelling tool user interfaces|here]].
{| class="wikitable"
! scope="col" style="width:15em" | Capability
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
(+ Sami GW)
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
(+ Hughes GW)
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |<big> </big>'''Climate (rain & PET)'''
|-
| style="vertical-align: vertical-align: center;" |Spatially variable across model domain
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Spatially variable within subcatchment
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |no
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Inter-annual variability in PET
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |<big> </big>'''Land cover & change'''
|-
| style="vertical-align: vertical-align: center;" |Processes explicitly linked to land cover
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Multiple land cover types included
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Cover has explicit location in subcatchment
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Cover can vary over model run timespan
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |''(limited)''
|-
| style="vertical-align: vertical-align: center;" |Irrigation, with dynamic demand & supply
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Potential for ET from GW (deep roots)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |<big> </big>'''Peak flows & flooding'''
|-
| style="vertical-align: vertical-align: center;" |Max daily or subdaily peak flow estimation
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Explicit impacts of channel capacity & shape on flow
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Calculation of flooded area extent
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(wetland)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(wetland)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(wetland)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Flood water subject to infiltration, ET, etc
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |no
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |<big> </big>'''Reservoirs, dams & channel flow modification'''
|-
| style="vertical-align: vertical-align: center;" |Reservoirs explicitly modelled
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Lumped representation for many small dams
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |no
|-
| style="vertical-align: vertical-align: center;" |Abstractions & external inputs
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Internal transfers between model units
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |''(limited)''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |<big> </big>'''GW representation & GW-SW interactions'''
|-
| style="vertical-align: vertical-align: center;" |Dynamic, 2-way, GW-SW exchange
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |GW table elevation predicted
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |GW pumping included
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |<big> </big>'''Wetlands & riparian zones'''
|-
| style="vertical-align: vertical-align: center;" |Wetland processes included
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |On-channel wetlands (valley bottom)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Off-channel wetlands (fed by channel overbank spill)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |no
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Groundwater-fed wetlands (direct vs via channel's baseflow)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |<big> </big>'''Modelling other related catchment processes'''
|-
| style="vertical-align: vertical-align: center;" |Sediment movement
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Water quality
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Crop yield
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |no
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |<big> </big>'''Uncertainty & parameter calibration'''
|-
| style="vertical-align: vertical-align: center;" |Functions/routines for batch runs, uncertainty, parameter sensitivity, & calibration
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|}
[[#Capabilities - pg top|Back to top of page]]

Modelling tool capability overview

2023-12-01T09:56:47Z

Julia Glenday: /* Modelling tool capabilities summary */

A set of commonly used modelling tools in South Africa was reviewed for the [[Model inter-comparison study|WRC “Critical catchment model inter-comparison and model use guidance development” project]].

This set included major tools developed in South Africa: ACRU and the Pitman model-based tools, WRSM-Pitman and SPATSIM-Pitman. It also included two tools that were developed in the northern hemisphere, but have been used in South Africa and globally: SWAT and MIKE-SHE. Locally developed tools can have certain advantages from being designed with the South African context in mind, both in terms of local data availability and in terms of local climate characteristics, ecosystems, soils, geologic types, and land and water management practices (e.g. landscapes with many small farm dams). SWAT and MIKE-SHE have resourced development teams behind them that continually update the tools and adapt them to make use of developing globally available data sources, such as remotely sensed data, and generally improved access to greater computing power.

This suite of tools covers a diversity of model structure and algorithm type options, but users should be aware there are many many tools available ([[Model types & tools #Table Anchor - tool examples|see more examples]])

'''The tables below summarise ''basic'' information about the tools in this set.''' These tables provide a broad overview, which may be all you need in many instances.


''More detailed information about the structural options and capabilities of the tools is given across the other tool inter-comparison pages: [[#Model units & connections|Model units & connections]], [[#Process representation across tools|Process representation]], [[#Water balance outputs across tools|Water balance outputs across tools]], [[#Modelling tool user interfaces|User interfaces]], [[#Documentation & support across tools|Documentation & support]], and [[#Applying tools in specific use cases|Specific use cases (e.g. irrigation, farm dams, groundwater pumping, riparian zones, wetlands)]].''

== Modelling software tool background & versions covered ==
{| class="wikitable"
! scope="col" style="width:15em" | Characteristic
! scope="col" style="background: #F2CEE0; width:15em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:15em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:15em" |ACRU
! scope="col" style="background: #F2F2CE; width:15em" |SWAT
! scope="col" style="background: #CEE6F2; width:15em" |MIKE-SHE
|-
| style="vertical-align: top" |'''Developed in South Africa'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |yes
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |yes
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |yes
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |no
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |no
|-
| style="vertical-align: center;" |'''Current curator / developer'''
| style="background: #FFF5FA; vertical-align: center;" |Bailey & Pitman Water Resources Ltd
| style="background: #FFF7F5; vertical-align: center;" |Rhodes University, Institute of Water Resources (IWR)
| style="background: #F5FFF5; vertical-align: center;" |University of KwaZulu Natal, Centre for Water Resources Research (UKZN-CWRR)
| style="background: #FFFFF5; vertical-align: center;" |Texas A&M University & US Department of Agriculture (USDA)
| style="background: #F5FCFF; vertical-align: center;" |Danish Hydrologic Institute (DHI)
|-
| style="vertical-align: center;" |'''Free to access'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |yes
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |yes
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |yes
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |yes
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |no*

free student licenses & free/reduced research licenses by arrangement
|-
| style="vertical-align: center" |'''Version reviewed in wiki'''
| style="background: #FFF5FA; vertical-align: center" |WRSM-Pitman version 2.9
| style="background: #FFF7F5; vertical-align: center" |SPATSIM GWv3 Global Options Threaded model
| style="background: #F5FFF5; vertical-align: center" |ACRU 4
| style="background: #FFFFF5; vertical-align: center" |SWAT2012; ArcSWAT2012
| style="background: #F5FCFF; vertical-align: center" |MIKE-SHE & MIKE Hydro River, version 2019 & 2020
|-
| style="vertical-align: top" |'''Reference documents consulted'''
([[Modelling tool documentation|see documentation links page]])
| style="background: #FFF5FA; vertical-align: top" |'''Theory manual:'''

Bailey, A.K. (2015). ''WRSM2000/Pitman: Water Resources Simulation Model for Windows - Theory Manual'' (Water Research Commission).

'''User manual:'''

Bailey, A.K., and Pitman, W.V. (2016). ''WRSM/Pitman User’s Manual: WR2012 Volume 7'' (Water Research Commission).
| style="background: #FFF7F5; vertical-align: top" |'''Theory documentation:'''

Hughes, D.A. (2004). Incorporating groundwater recharge and discharge functions into an existing monthly rainfall–runoff model. ''Hydrological Sciences Journal'' 49.

Hughes, D.A. (2013). A review of 40 years of hydrological science and practice in southern Africa using the Pitman rainfall-runoff model. ''Journal of Hydrology'' 501, 111–124.

Kapangaziwiri, E. (2007). ''Revised parameter estimation methods for the Pitman monthly rainfall-runoff model''. MSc. Rhodes University.

'''User manual:'''

Hughes, D.A. (2019). ''SPATSIM v3 & IWR version of the Pitman model'' (IWR Rhodes University).
| style="background: #F5FFF5; vertical-align: top" |'''Theory manual:'''

Schulze, R.E. (1995). ''Hydrology and Agrohydrology: A Text to Accompany the ACRU 3.00 Agrohydrological Modelling System'' (Water Research Commission).

'''User manuals:'''

Clark, D.J., Smithers, J.C., Thornton-Dibb, S.L.C., and Lutchminarian, A. (2012). ''ACRU 4 User Manual: User Interface & Tutorials (Volume 3 of Deployment, Maintenance, & Further Development of SPATSIM-HDSF)''

Schulze, R.E., and Davis, N.S. (2018). ''Practitioners’ Handbook for Undertaking Current and Projected Future Climate Related Risk and Vulnerability Modelling Assessments (an update of the ACRU user manual)'' (Schulze and Associates).
| style="background: #FFFFF5; vertical-align: top" |'''Theory manual:'''

Neitsch, S.L., Arnold, J.G., Kiniry, J.R., and Williams, J.R. (2011). ''Soil and Water Assessment Tool (SWAT) Theoretical Documentation, Version 2009'' (Texas Water Resources Institute, Texas A&M University).

'''User manuals:'''

Winchell, M., Srinivasan, R., Di Luzio, J., and Arnold, J. (2013). ''ArcSWAT Interface for SWAT2012: User’s Guide'' (Texas Water Resources Institute, Texas A&M University).

Arnold, J.G., Kiniry, J.R., Srinivasan, R., Williams, J.R., Haney, E.B., and Neitsch, S.L. (2012). ''Soil & Water Assessment Tool (SWAT) - Input/Output Documentation, Version 2012'' (Texas Water Resources Institute, Texas A&M University).

| style="background: #F5FCFF; vertical-align: top" |'''Theory manuals:'''

DHI (2019). ''MIKE SHE Manual, Volume 2: Reference Guide, MIKE 2019'' (Danish Hydrologic Institute).

DHI (2019). ''MIKE 1D: DHI Simulaton Engine for 1D river and urban modelling - Reference Manual, MIKE 2019'' (Danish Hydrologic Institute).

'''User manuals:'''

DHI (2019). ''MIKE SHE Manual, Volume 1: User Guide, MIKE 2019'' (Danish Hydrologic Institute).

DHI (2019). ''MIKE Hydro River: User Guide, MIKE 2019'' (Danish Hydrologic Institute).
|}

These software tools have different development histories and somewhat different focuses, however all have adapted over time, adding features that allow them to be used in more contexts and have generally overlapping intended applications ([[#Intended uses & development focuses summary|see table below]]).

The structural options and design of each tool reflect the intended applications as well as the balance struck by the developers between potentially competing concerns and goals, such as achieving parsimony, including detailed representation of land cover differences to estimate the impacts of change, maintaining ease of use of the tool, facilitating quantification of model output uncertainty, ensuring applicability in data limited contexts, etc.

For these reasons, despite the overlap in general intended uses, the tools offer some fairly different modelling strategies ([[#Model structure overview by tool: spatial & temporal scales|see table below]]). This impacts how they can be applied in specific settings (documented in more detail [[Model units & connections|here]]). For example, all the tools are capable of modelling the impacts of land use change to some degree, however WRSM-Pitman and SPATSIM-Pitman place greater limitations on the number and types of land cover that can be explicitly modelled compared to the other tools.

A summary table of some key modelling capabilities across the tools is presented [[#Modelling tool capabilities summary|below]].


[[#Capabilities - pg top|Back to top of page]]



==Intended uses & development focuses summary ==
{| class="wikitable"
! scope="col" style="width:15em" | Characteristic
! scope="col" style="background: #F2CEE0; width:15em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:15em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:15em" |ACRU4
! scope="col" style="background: #F2F2CE; width:15em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15em" |MIKE-SHE
|-
| style="vertical-align: top" |'''Specific tool development focuses'''
| style="background: #FFF5FA; vertical-align: top" |
* Flexible network for managed systems: many for options transfers, withdrawal points, reservoir locations, etc.
* Irrigated area representation
* IAP & plantation forestry water use
* Groundwater-surface water interaction (vegetation & GW pumping impacts)
| style="background: #FFF7F5; vertical-align: top" |
* Parsimony,
* Uncertainty assessment & stochastic modelling,
* Groundwater-surface water interaction (vegetation & GW pumping impacts)
| style="background: #F5FFF5; vertical-align: top" |
* Detailed land cover type representation,
* In-built local parameter database for SA vegetation & soil types, supports the level of representation
* Crop & irrigation detail,
* IAP & plantation forestry water use, including deep rooted vegetation in riparian areas
| style="background: #FFFFF5; vertical-align: top" |
* Detailed land cover type representation,
* In-built local parameter database for vegetation & soil types - North American focus, some more general, supports the level of representation
* Crop & irrigation detail with source flexibility,
* Coupling to GIS tools
| style="background: #F5FCFF; vertical-align: top" |
* Flexible spatial discretisation & distribution (climate, land cover, soil, geology, etc),
* Potential for fine scale process representation
* Crop & irrigation detail with source flexibility,
* Groundwater-surface water interaction,
* Coupled hydraulic channel model & flooding processes
|-
| style="vertical-align: vertical-align: center;" |'''Intended applications:'''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |
|-
| style="vertical-align: vertical-align: center;" |''Water balance estimation''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |''Design hydrology & flood analyses''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |''Supply planning (general)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |''Reservoir yield''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |''Irrigation planning''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |''Groundwater recharge''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |''GW-SW interactions & GW pumping impacts''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |''Land cover change impacts''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |''Climate change impacts''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: top" |'''Application limitations'''
| style="background: #FFF5FA; vertical-align: top" |
* Monthly model: not applicable for peak flow, flood assessment, design hydrology
* No irrigation direct from groundwater
| style="background: #FFF7F5; vertical-align: top" |
* Monthly model: not applicable for peak flow, flood assessment, design hydrology
* No irrigation direct from groundwater
| style="background: #F5FFF5; vertical-align: top" |
* Simplified groundwater modelling;
* Does not model groundwater pumping
| style="background: #FFFFF5; vertical-align: top" |
* Highly simplified deep groundwater modelling
| style="background: #F5FCFF; vertical-align: top" |''(None documented for the modelling system as whole, only for certain process options within it. The learning curve for its use and computing power required can pose practical limitations to its application )''
|}
[[#Capabilities - pg top|Back to top of page]]



== Model structure overview by tool: spatial & temporal scales ==
The table below gives a very basic overview of the type of model structure that can be built in each tool.
 More details about the model structure options across tools are presented [[Model units & connections|here]].
{| class="wikitable"
! scope="col" style="width:15em" | Characteristic
! scope="col" style="background: #F2CEE0; width:15em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:15em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:15em" |ACRU4
! scope="col" style="background: #F2F2CE; width:15em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15em" |MIKE-SHE
|-
| style="vertical-align: top" |'''Intended scale of catchment or modelled area'''
| style="background: #FFF5FA; vertical-align: top" |Local to regional:

no suggested min-max model size
| style="background: #FFF7F5; vertical-align: top" |Local to regional:

10-10,000’s of km2

more typical: 100-1,000’s km2
| style="background: #F5FFF5; vertical-align: top" |Field to regional:

no suggested min-max model size
| style="background: #FFFFF5; vertical-align: top" |Field to regional:

no suggested min-max model size
| style="background: #F5FCFF; vertical-align: top" |Field to regional:

no suggested min-max model size
|-
| style="vertical-align: top" |'''Timestep'''
| style="background: #FFF5FA; vertical-align: top" |Monthly*

A daily version has been developed. Limited use to-date.
| style="background: #FFF7F5; vertical-align: top" |Monthly*

A daily version has been developed. Limited use to-date
| style="background: #F5FFF5; vertical-align: top" |Daily
| style="background: #FFFFF5; vertical-align: top" |Daily, subdaily

| style="background: #F5FCFF; vertical-align: top" |Daily, subdaily*

Calculation timesteps are dynamic and vary by process. All outputs saved for a user-selected step.
|-
| style="vertical-align: top" |'''Spatial discretisation (model spatial units)'''
| style="background: #FFF5FA; vertical-align: top" |Modules connected by routes

(“runoff” modules + special area modules + channel modules create subcatchments)

| style="background: #FFF7F5; vertical-align: top" |Subcatchments + limited internal sub-area types

| style="background: #F5FFF5; vertical-align: top" |HRUs within subcatchments

| style="background: #FFFFF5; vertical-align: top" |HRUs within subcatchments
| style="background: #F5FCFF; vertical-align: top" |Grid cells (3D),

with optional calculation simplifications: surface flow modelled for zones, interflow & groundwater modelled for storage reservoirs within subcatchments.
|-
| style="vertical-align: top" |'''Suggested model unit scales'''
| style="background: #FFF5FA; vertical-align: top" |Runoff module: < 1,000 km2
| style="background: #FFF7F5; vertical-align: top" |(none listed)
| style="background: #F5FFF5; vertical-align: top" |Subcatchments: 5-50 km2

HRUs: < 30km2
| style="background: #FFFFF5; vertical-align: top" |(none listed)
| style="background: #F5FCFF; vertical-align: top" |(none listed)
|}

Despite having largely overlapping intended uses in general, there is notable diversity in model structure (table above, and more detailed coverage [[Model units & connections|here]]) and in more specific modelling capabilities in this set of tools ([[#Modelling tool capabilities summary|table below]]).

Some key points arising from the capabilities comparison are:

* No one tool had all the capabilities listed. All the tools have differing sets of advantages over the others.

* Although both based on the same predecessor model structure and sharing many basic process algorithms, WRSM-Pitman and SPATSIM Pitman have diverged in capabilities across several aspects. These differences are linked to WRSM’s modular network structure compared to the SPATSIM version’s focus on the subcatchment as the primary unit for process representation. For example, a WRSM model can include user-defined artificial water transfers between channel units in a model network, which SPATSIM does not include. SPATSIM includes an uncertainty or stochastic modelling routine, made more straightforward by the more uniform set-up of subcatchments, which WRSM does not include.

* WRSM-Pitman, SPATSIM-Pitman, and MIKE-SHE model dynamic, two-way exchange between surface water channels and groundwater aquifers (GW-SW exchange): groundwater can flow into the channel or channel water can recharge an aquifer in the model and the direction and magnitude of the exchange is calculated based on the water levels in each in every modelled timestep. 

* Only MIKE-SHE has a fully coupled hydraulic model, allowing it to model channel-floodplain interactions in more detail, including the impact of changes in channel size, shape, depth of incision, etc. Other tools can represent some aspects of overbank flooding and the fate of the flood water, but this is limited to their wetland and riparian zone modules.


[[#Capabilities - pg top|Back to top of page]]



==Modelling tool capabilities summary==
'''Important note: this capabilities summary table indicates what is ''technically possible'' within the modelling tools, but it does ''not'' cover the ''practicality and ease-of-use'' of the different features across each tool.''' 
Some things that are possible in a tool become a veritable labour of love to actually achieve, depending on the nature of the model set-up (i.e. how many subcatchments, how many HRUs, etc). 
''Example: In ACRU4, different climate inputs '''can''' be specified by HRU, to allow for spatial distribution of rainfall within a subcatchment. However operationalising this when there are many HRUs becomes very time consuming compared to simply specifying one set of climate inputs the whole subcatchment. Applying different climate inputs to different areas within a subcatchment requires manually clicking through three layers of menus each for four different climate inputs for every HRU. There is no batch-input of climate for subgroups of HRUs within a subcatchment.''
Various aspects of the user interfaces of the different tools and their implications are covered on a separate page [[Modelling tool user interfaces|here]].
{| class="wikitable"
! scope="col" style="width:15em" | Capability
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
(+ Sami GW)
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
(+ Hughes GW)
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |<big> </big>'''Climate (rain & PET)'''
|-
| style="vertical-align: vertical-align: center;" |Spatially variable across model domain
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Spatially variable within subcatchment
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |no
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Inter-annual variability in PET
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |<big> </big>'''Land cover & change'''
|-
| style="vertical-align: vertical-align: center;" |Processes explicitly linked to land cover
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Multiple land cover types included
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Cover has explicit location in subcatchment
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Cover can vary over model run timespan
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |''(limited)''
|-
| style="vertical-align: vertical-align: center;" |Irrigation, with dynamic demand & supply
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Potential for ET from GW (deep roots)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |<big> </big>'''Peak flows & flooding'''
|-
| style="vertical-align: vertical-align: center;" |Max daily or subdaily peak flow estimation
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Explicit impacts of channel capacity & shape on flow
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Calculation of flooded area extent
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(wetland)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(wetland)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(wetland)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Flood water subject to infiltration, ET, etc
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |no
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |<big> </big>'''Reservoirs, dams & channel flow modification'''
|-
| style="vertical-align: vertical-align: center;" |Reservoirs explicitly modelled
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Lumped representation for many small dams
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |no
|-
| style="vertical-align: vertical-align: center;" |Abstractions & external inputs
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Internal transfers between model units
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |''(limited)''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |<big> </big>'''GW representation & GW-SW interactions'''
|-
| style="vertical-align: vertical-align: center;" |Dynamic, 2-way, GW-SW exchange
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |GW table elevation predicted
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |GW pumping included
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |<big> </big>'''Wetlands & riparian zones'''
|-
| style="vertical-align: vertical-align: center;" |Wetland processes included
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |On-channel wetlands (valley bottom)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Off-channel wetlands (fed by channel overbank spill)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |no
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Groundwater-fed wetlands (direct vs via channel's baseflow)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |<big> </big>'''Modelling other related catchment processes'''
|-
| style="vertical-align: vertical-align: center;" |Sediment movement
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Water quality
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Crop yield
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |no
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |<big> </big>'''Uncertainty & parameter calibration'''
|-
| style="vertical-align: vertical-align: center;" |Functions/routines for batch runs, uncertainty, parameter sensitivity, & calibration
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|}
[[#Capabilities - pg top|Back to top of page]]

Modelling tool user interfaces

2023-12-01T09:49:54Z

Julia Glenday: /* Interface comparison overview */

''' PAGE IN PROGRESS - MORE COMING SOON! '''

The table below gives a comparison of the user interface for each of the modelling tools.

== Interface comparison overview ==

{| class="wikitable"
! scope="col" style="width:15em" | Interface characteristic
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
|-
| style="vertical-align: vertical-align: center;" |Graphical user interface ''(vs code prompt)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Catchment map display (visualise linkages)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model run times'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Estimated model run time for a 30 year run, ~300km^2 catchment ''(Note: will depend on model set-up complexity & computing power!)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |tens of minutes
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |hours
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Computing resources needed'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Comparative rating of computing power needed to achieve workable run times.
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |light
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |light
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |light
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |medium
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |intensive (need good GPU)
|-
| colspan="6" style="background: #FFFFFF; vertical-align: vertical-align: center;" |'''Model set-up ease & efficiency'''<big> </big>
|-
| style="vertical-align: vertical-align: center;" |Automated creation of model units & connections from map inputs ''(vs fully manual creation)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Input parameter values and change values for batches of models units ''(e.g., all HRUs of a cover type)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |In-built database of suggested parameter values ''(e.g., for common vegetation types, soil types, etc.)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |no
|-
| style="vertical-align: vertical-align: center;" |User can build own parameter databases for use across multiple models
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model set-up transparency''' (i.e., is it very obvious what the model is doing/assuming?) <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Interface makes the user interact with every component & parameter entry option during model set-up ''(vs having default parameter values pre-entered & not forcing user to view them)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |no
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Tool checks connection errors
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Batch runs & calibration tools''' <big> </big>
|-
| style="vertical-align: vertical-align: center;" |Facility for batch runs, parameter sensitivity analyses, uncertainty analyses & auto-calibration
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Accessing model output'''
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for streamflow
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for water balance fluxes and stores
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |All water balance components that are calculated by the model can be exported
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Batch export of water balance fluxes for model's basic spatial units
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Automated extraction of water balance fluxes for different spatial scales ''(e.g., by cover class area, by subcatchment, full catchment)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|}

== Formats for input-output data ==

== Computing resources ==

== Run times ==
Run times for models built with a given tool can vary considerably with the size and complexity of the set-up, the number of timesteps in the run, and the computer being used. This makes is difficult to generalise, however, due to their relative simplicity WRSM, SPATSIM, and ACRU4 models in these exercises generally ran in a matter of a few minutes for a 30 year run, while the ArcSWAT and MIKE-SHE models could range from 15 minutes to several hours to complete this.

The run times have import particularly for parameter adjustment testing, limiting how much can be done in the time available for a project. However, the tools that have long run times, as well as SPATSIM, have made the parameter adjustment process quick and allow batch run facilities. Once set-up time-consuming testing runs can be ongoing without manual intervention needed from the modeller, freeing their time for other work. Although WRSM and ACRU4 run quickly, the process of making parameter adjustments in the model set-up to be tested takes a long time and a lot of manual effort as described above.

Modelling process overview

2023-12-01T09:40:58Z

Julia Glenday:

'''''This page gives an overview of different parts of the modelling process, particularly in the context of decisions about model structure and modelling software tool selection.'''''

Here [[Terminology|'model structure']] refers to things like how the catchment is broken up into "modelled units", such as subcatchments or smaller units representing areas of a particular land cover type or river channel units, and how different units are connected to one another in the model. Structure choices are linked to the choice of [[Terminology|'modelling software tool']] because different tools allow for different kinds of structures and process representation. In some cases there may be multiple modelling tools that will be able to meet one's structure needs and wants. In other cases, no tool may meet all the demands.

There are other considerations, such as ease of use, that will contribute to modelling tool selection. There is never enough time and data to build "the perfect model." Compromises will always need to be made. Identifying 'needs' and 'nice-to-haves' for the modelling project early on in the process will assist with appropriate, 'fit-for-purpose' structure selection, tool selection, and model building.

The process of catchment modelling is generally not linear. The steps covered below aren't always completed sequentially: there will often be iterations and circling back for revising.

 
== Defining the modelling project goal(s) ==

Defining the goals of a modelling project in as much detail as possible, and prioritising across them, allows one to use the needed and desired model outputs to identify the model structures that would be required to attain them.

For example: a very broad goal of a modelling project could be to look at impacts of invasive alien trees on water supply from a catchment. More specific goals in such a project could be to look at the impacts of invasive alien trees on the 98% assurance yield of a particular water supply reservoir, or on the water level of an aquifer in a particular part of the catchment, or on streamflow in particular places within the catchment (withdrawal points, critical habitat points, etc.) during dry periods of certain recurrence frequencies. Looking at these more specific goals would help in determining whether model output on a monthly scale would be sufficient or shorter time-scales are needed, whether groundwater storage volumes or levels are a needed output from the model, what spatial scales one might want to get model streamflow outputs for, etc. In this example, more specific goals for modelling would also include defining what alternative land cover states would be used as reference to determine the "impact" of the invasive alien trees. This would influence the model structure and the needed tool capabilities in terms of how different land cover types and properties can be represented.

For reasons of data, time, or other constraints, detailed project goals may need to be revisited and adjusted. Understanding the potential pathways to reach ideal goals can help target future work.

 

== Taking stock of available data & information ==

The data and information available will influence what is possible in a modelling project and the ability to assess and reduce uncertainties. Hydrometric observational data and catchment biophysical property data are used both for direct model inputs and for constraining structure and parameter value options through calibration and reality-checks (see [[#Developing 'conceptual' models of catchment processes|Conceptual model section]]). The quality, spatial and temporal resolution, and time period of data influence how they can be used in modelling and what assumptions need to be made. For most data required for a catchment model, if local observational data is not available there are national and global datasets of various kinds (see [[Data sources|data sources page]]) that can be used to obtain starting estimates, recognising potential scaling issues.

The scale and quality of the data and information about the catchment have implications for the level of detail in a model structure. The idealised specific goals of a modelling project may lead one toward a model with a highly detailed spatial and vertical structure. However, without commensurate data to parameterise or evaluate a model of this detail, the structure (and specific goals) may need to be revisited, acknowledging the uncertainties involved.

 

== Developing 'conceptual' models of catchment processes ==

Describing and laying out a ‘conceptual’ or ‘perceptual’ model (see [[Terminology]]) of the catchment(s) being modelled is an important step in deciding on a structure for the numerical model. This will also assist in reality-checks on the numerical model and in recognising what simplifications, implicit representation, and assumptions are involved. A conceptual model is your hypotheses about processes in the catchment based on landscape analyses (e.g. topography, climate, spatial distribution of rainfall, geology, land cover type distribution, etc.), diagnostic patterns in the available hydrometric data (e.g. runoff ratio and its variability, flashy streamflow vs slow or prolonged responses to rainfall events, seasonality, groundwater variability, etc.), and previous studies in the catchment or in comparable settings. Identifying what runoff processes are likely to be dominant in different parts of the landscape and what flow paths are likely to connect different areas can guide choices of how to break up the catchment area into modelled units and how these should ideally be connected. It helps to highlight what is well understood and what is more highly uncertain (i.e. multiple potential explanations for an observed pattern and not clear which apply in this case).

The conceptual model description should extend to the scenarios being modelled in a project, i.e. how and how much are the changes to be modelled likely to impact different processes and connections at different scales? The numerical modelling is being done to answer these questions in more detail for a site, but existing understanding of the likely mechanisms, direction, and magnitudes of changes from relevant field studies can help design and check the modelling.

Using pre-existing numerical modelling software tools limits the design of the model: the spatial and vertical units, how they can be connected, how processes are calculated, etc. It is reasonable to expect that some aspect of your conceptual model of a catchment can not be directly represented by models built with a tool in the way that you believe they are occurring in reality (e.g. In the model, can a floodplain area receive subsurface flow from surrounding mountain areas? In the model, can a wetland area be fed by channel overflow? In the model, can vegetation ET be fed by groundwater?). Identifying this is important. There may be ways to represent certain processes implicitly or indirectly within a given model structure. This should be done consciously and be evaluated, especially if the processes being implicitly represented are central to the question that the model is being used to answer and/or they have a large impact on the key model outputs for the project.

 

== Selecting a model structure & a modelling tool ==

In an ideal situation, one would come up with model structure needs (e.g. separately represented cover types, subsurface layers, etc; how these are connected in the surface and subsurface; model output types, locations, spatial and temporal scales) based on the conceptual model of catchment processes, the available data, and the specific goals of the modelling exercise, and then select a software tool capable of building a model with the desired structure. However, more often than not we are additionally constrained by time and other practicalities. The selection of a modelling tool can also be informed by how familiar we are with a tool and the time available to learn a new one sufficiently, awareness of what is possible across different tools, the time and effort required to set up and run different tools (see [[#Building & running the numerical model|section below]]), computing power, access to tool licenses when applicable.

Even if a variety of tools are practically available to us for a project, it's possible no one tool will be able to build the structure we hoped for. In this case we can select the best compromise, proceed using multiple tools, and/or programme something outside the existing tools (new model, a linked module, etc).

Once a tool is selected, it is helpful to draw out and evaluate potential structures for the model (units, connections, etc) within the options available in the software tool in light of the project goals, conceptual model, and data. Even within these constraints, there will be decisions to be made. Part of this process is also deciding on the parameter values, or ranges of values, to apply in the various model algorithms used in the specific tool, based on the information available about different biophysical properties compared to the meanings of the parameters. While compromise and uncertainties in structure decisions are unavoidable, they should be documented to inform improvement in the future. Comparing outcomes across different structures that are considered potentially viable/realistic would be desirable if there are resources for this level of effort in the project.

 

== Building & running the numerical model ==

Once the model structure (or multiple to test) within the selected tool has been decided upon, there is often a fair amount of work involved in actually building this in the software tool. This involves getting all the needed data into the required formats for the tool and inputting it. Tools vary significantly in how this is done, how user-friendly the process is, and how easy it is to make user-errors in this process and to find these errors when they’ve been made. Modelling tools also vary significantly in the time they take to run depending on their complexity and computing strategies. Tools also vary in how different outputs they produce can be accessed and saved, and in some cases analysed internally by the tool. In some situations practicalities around building and running the model alone can be motivation to further simplify aspects of a model structure, if this does not pose a major hindrance to reaching prioritised goals. An inter-comparison of aspects of the model-building process, i.e. the user interface, across the focus tools is given [[Modelling tool user interfaces|here]].

 

== Model validation & calibration ==

After the model has been built and run and the outputs have been obtained, the outputs need to be assessed against observational data, in as much as possible, and against the conceptual model at a minimum. It is likely this process will identify aspects of the model in need of improvement and ideally there would be time and resources in the project to test appropriate adjustments. There is a rich literature on model realism assessment, performance assessment, goodness-of-fit statistics. Linked to this are parameter sensitivity analyses, model output uncertainty analyses, and model calibration approaches.

Some form of assessment of the validity of the model outcomes against independent measures of realism is always necessary, regardless of the care taken in the model construction and the quality of the inputs. The approach taken in a project will vary depending on the project goals and resources available. Even if local time-series observational data of streamflow are not available, other information and data sources can be consulted to provide realism checks on different model outputs, e.g. patterns of flow in gauged catchments considered to be similar, local resident accounts of the extent and duration of major flood events, measurements or remote sensing estimates of ET in dominant vegetation types, borehole water level information, etc. If the model is producing outputs that don’t conform to expected patterns based on independent information, the structure and parameterisation, the input data, and/or potentially the conceptual model may need re-evaluation. A first port of call is error-checking the model set-up!

Uncertainty is introduced into modelling at every step: the input data, the data we validate against, and the choice of model structure with its algorithms and parameter values. This does not mean that models won’t provide helpful information about likely catchment processes and how they could change, but we should be realistic in our expectations of accuracy and attempt to get an idea of the scale of the uncertainty. Different modelling applications will require different degrees of certainty for the output to be of practical use. Thresholds of acceptability should be identified, but will take different forms for different projects.

Some modelling software tools have in-built uncertainty analysis, sensitivity analysis, and calibration tools that facilitate testing many potential parameter value sets (info the focus tools [[Modelling tool user interfaces|here]]). These are generally designed to target parameter value uncertainty and won’t, in themselves, address problems with the input data or validation data, or with the structure in terms of units, connections, and algorithms. They assess the degree to which model outputs vary, or can be brought closer to observational data, by changing the parameter values. There is always some degree of uncertainty in parameter values, given data availability, scale of measurement vs scale of modelling, simplifications of the physical process in the model's algorithms, etc. However, bounds can be placed on potentially realistic values for each parameter based on the existing biophysical information and understanding of the parameter meaning. If reasonable performance cannot be achieved through parameter sets selected within these bounds, this suggests limitations of this structure in representing the catchment processes and/or problems with the data.

It is possible for multiple different sets of parameter values to produce equivalent levels of performance against the modeller’s criteria for acceptability. This is known as ''equifinality''. This can indicate that there isn’t enough observational data to resolve differences between some parameter set options, given the number of parameters we are uncertain about and the range of values we think each one could realistically take. More data with which to check model performance or model realism (potentially of different kinds), and more information to constrain the range of potential parameter values that are considered reasonable, can assist in reducing equifinality. Equifinality can also have to do with the model structure. For example, one set of parameters may produce better fitting model outputs for dry periods, while another set of parameter values has better outputs for wet periods. The two sets have comparable outcomes for overall combined statistics. This could be because properties or processes of the catchment actually shift more over time than the model structure itself allows for. It takes exploration of the ‘parameter space’ to identify equifinality and not all modelling tools facilitate this. When equifinality is identified, a suite of similarly acceptable parameter sets can be applied and the range of the outputs of this set of models can be presented as the project outcome, rather than relying on the model outputs of a single set of parameter values. Different modelling tools, and structures, make this a simpler or harder task to complete.

Modelling process overview

2023-12-01T09:39:59Z

Julia Glenday:

'''''This page gives an overview of different parts of the modelling process, particularly in the context of decisions about model structure and modelling software tool selection.'''''

Here [[Terminology|'model structure']] refers to things like how the catchment is broken up into "modelled units", such as subcatchments or smaller units representing areas of a particular land cover type or river channel units, and how different units are connected to one another in the model. Structure choices are linked to the choice of [[Terminology|'modelling software tool']] because different tools allow for different kinds of structures and process representation. In some cases there may be multiple modelling tools that will be able to meet one's structure needs and wants. In other cases, no tool may meet all the demands.

There are other considerations, such as ease of use, that will contribute to modelling tool selection. There is never enough time and data to build "the perfect model." Compromises will always need to be made. Identifying 'needs' and 'nice-to-haves' for the modelling project, in as much detail as possible, early on in the process will assist with appropriate, 'fit-for-purpose' structure selection, tool selection, and model building.

The process of catchment modelling is generally not linear. The steps covered below aren't always completed sequentially: there will often be iterations and circling back for revising.

 
== Defining the modelling project goal(s) ==

Defining the goals of a modelling project in as much detail as possible, and prioritising across them, allows one to use the needed and desired model outputs to identify the model structures that would be required to attain them.

For example: a very broad goal of a modelling project could be to look at impacts of invasive alien trees on water supply from a catchment. More specific goals in such a project could be to look at the impacts of invasive alien trees on the 98% assurance yield of a particular water supply reservoir, or on the water level of an aquifer in a particular part of the catchment, or on streamflow in particular places within the catchment (withdrawal points, critical habitat points, etc.) during dry periods of certain recurrence frequencies. Looking at these more specific goals would help in determining whether model output on a monthly scale would be sufficient or shorter time-scales are needed, whether groundwater storage volumes or levels are a needed output from the model, what spatial scales one might want to get model streamflow outputs for, etc. In this example, more specific goals for modelling would also include defining what alternative land cover states would be used as reference to determine the "impact" of the invasive alien trees. This would influence the model structure and the needed tool capabilities in terms of how different land cover types and properties can be represented.

For reasons of data, time, or other constraints, detailed project goals may need to be revisited and adjusted. Understanding the potential pathways to reach ideal goals can help target future work.

 

== Taking stock of available data & information ==

The data and information available will influence what is possible in a modelling project and the ability to assess and reduce uncertainties. Hydrometric observational data and catchment biophysical property data are used both for direct model inputs and for constraining structure and parameter value options through calibration and reality-checks (see [[#Developing 'conceptual' models of catchment processes|Conceptual model section]]). The quality, spatial and temporal resolution, and time period of data influence how they can be used in modelling and what assumptions need to be made. For most data required for a catchment model, if local observational data is not available there are national and global datasets of various kinds (see [[Data sources|data sources page]]) that can be used to obtain starting estimates, recognising potential scaling issues.

The scale and quality of the data and information about the catchment have implications for the level of detail in a model structure. The idealised specific goals of a modelling project may lead one toward a model with a highly detailed spatial and vertical structure. However, without commensurate data to parameterise or evaluate a model of this detail, the structure (and specific goals) may need to be revisited, acknowledging the uncertainties involved.

 

== Developing 'conceptual' models of catchment processes ==

Describing and laying out a ‘conceptual’ or ‘perceptual’ model (see [[Terminology]]) of the catchment(s) being modelled is an important step in deciding on a structure for the numerical model. This will also assist in reality-checks on the numerical model and in recognising what simplifications, implicit representation, and assumptions are involved. A conceptual model is your hypotheses about processes in the catchment based on landscape analyses (e.g. topography, climate, spatial distribution of rainfall, geology, land cover type distribution, etc.), diagnostic patterns in the available hydrometric data (e.g. runoff ratio and its variability, flashy streamflow vs slow or prolonged responses to rainfall events, seasonality, groundwater variability, etc.), and previous studies in the catchment or in comparable settings. Identifying what runoff processes are likely to be dominant in different parts of the landscape and what flow paths are likely to connect different areas can guide choices of how to break up the catchment area into modelled units and how these should ideally be connected. It helps to highlight what is well understood and what is more highly uncertain (i.e. multiple potential explanations for an observed pattern and not clear which apply in this case).

The conceptual model description should extend to the scenarios being modelled in a project, i.e. how and how much are the changes to be modelled likely to impact different processes and connections at different scales? The numerical modelling is being done to answer these questions in more detail for a site, but existing understanding of the likely mechanisms, direction, and magnitudes of changes from relevant field studies can help design and check the modelling.

Using pre-existing numerical modelling software tools limits the design of the model: the spatial and vertical units, how they can be connected, how processes are calculated, etc. It is reasonable to expect that some aspect of your conceptual model of a catchment can not be directly represented by models built with a tool in the way that you believe they are occurring in reality (e.g. In the model, can a floodplain area receive subsurface flow from surrounding mountain areas? In the model, can a wetland area be fed by channel overflow? In the model, can vegetation ET be fed by groundwater?). Identifying this is important. There may be ways to represent certain processes implicitly or indirectly within a given model structure. This should be done consciously and be evaluated, especially if the processes being implicitly represented are central to the question that the model is being used to answer and/or they have a large impact on the key model outputs for the project.

 

== Selecting a model structure & a modelling tool ==

In an ideal situation, one would come up with model structure needs (e.g. separately represented cover types, subsurface layers, etc; how these are connected in the surface and subsurface; model output types, locations, spatial and temporal scales) based on the conceptual model of catchment processes, the available data, and the specific goals of the modelling exercise, and then select a software tool capable of building a model with the desired structure. However, more often than not we are additionally constrained by time and other practicalities. The selection of a modelling tool can also be informed by how familiar we are with a tool and the time available to learn a new one sufficiently, awareness of what is possible across different tools, the time and effort required to set up and run different tools (see [[#Building & running the numerical model|section below]]), computing power, access to tool licenses when applicable.

Even if a variety of tools are practically available to us for a project, it's possible no one tool will be able to build the structure we hoped for. In this case we can select the best compromise, proceed using multiple tools, and/or programme something outside the existing tools (new model, a linked module, etc).

Once a tool is selected, it is helpful to draw out and evaluate potential structures for the model (units, connections, etc) within the options available in the software tool in light of the project goals, conceptual model, and data. Even within these constraints, there will be decisions to be made. Part of this process is also deciding on the parameter values, or ranges of values, to apply in the various model algorithms used in the specific tool, based on the information available about different biophysical properties compared to the meanings of the parameters. While compromise and uncertainties in structure decisions are unavoidable, they should be documented to inform improvement in the future. Comparing outcomes across different structures that are considered potentially viable/realistic would be desirable if there are resources for this level of effort in the project.

 

== Building & running the numerical model ==

Once the model structure (or multiple to test) within the selected tool has been decided upon, there is often a fair amount of work involved in actually building this in the software tool. This involves getting all the needed data into the required formats for the tool and inputting it. Tools vary significantly in how this is done, how user-friendly the process is, and how easy it is to make user-errors in this process and to find these errors when they’ve been made. Modelling tools also vary significantly in the time they take to run depending on their complexity and computing strategies. Tools also vary in how different outputs they produce can be accessed and saved, and in some cases analysed internally by the tool. In some situations practicalities around building and running the model alone can be motivation to further simplify aspects of a model structure, if this does not pose a major hindrance to reaching prioritised goals. An inter-comparison of aspects of the model-building process, i.e. the user interface, across the focus tools is given [[Modelling tool user interfaces|here]].

 

== Model validation & calibration ==

After the model has been built and run and the outputs have been obtained, the outputs need to be assessed against observational data, in as much as possible, and against the conceptual model at a minimum. It is likely this process will identify aspects of the model in need of improvement and ideally there would be time and resources in the project to test appropriate adjustments. There is a rich literature on model realism assessment, performance assessment, goodness-of-fit statistics. Linked to this are parameter sensitivity analyses, model output uncertainty analyses, and model calibration approaches.

Some form of assessment of the validity of the model outcomes against independent measures of realism is always necessary, regardless of the care taken in the model construction and the quality of the inputs. The approach taken in a project will vary depending on the project goals and resources available. Even if local time-series observational data of streamflow are not available, other information and data sources can be consulted to provide realism checks on different model outputs, e.g. patterns of flow in gauged catchments considered to be similar, local resident accounts of the extent and duration of major flood events, measurements or remote sensing estimates of ET in dominant vegetation types, borehole water level information, etc. If the model is producing outputs that don’t conform to expected patterns based on independent information, the structure and parameterisation, the input data, and/or potentially the conceptual model may need re-evaluation. A first port of call is error-checking the model set-up!

Uncertainty is introduced into modelling at every step: the input data, the data we validate against, and the choice of model structure with its algorithms and parameter values. This does not mean that models won’t provide helpful information about likely catchment processes and how they could change, but we should be realistic in our expectations of accuracy and attempt to get an idea of the scale of the uncertainty. Different modelling applications will require different degrees of certainty for the output to be of practical use. Thresholds of acceptability should be identified, but will take different forms for different projects.

Some modelling software tools have in-built uncertainty analysis, sensitivity analysis, and calibration tools that facilitate testing many potential parameter value sets (info the focus tools [[Modelling tool user interfaces|here]]). These are generally designed to target parameter value uncertainty and won’t, in themselves, address problems with the input data or validation data, or with the structure in terms of units, connections, and algorithms. They assess the degree to which model outputs vary, or can be brought closer to observational data, by changing the parameter values. There is always some degree of uncertainty in parameter values, given data availability, scale of measurement vs scale of modelling, simplifications of the physical process in the model's algorithms, etc. However, bounds can be placed on potentially realistic values for each parameter based on the existing biophysical information and understanding of the parameter meaning. If reasonable performance cannot be achieved through parameter sets selected within these bounds, this suggests limitations of this structure in representing the catchment processes and/or problems with the data.

It is possible for multiple different sets of parameter values to produce equivalent levels of performance against the modeller’s criteria for acceptability. This is known as ''equifinality''. This can indicate that there isn’t enough observational data to resolve differences between some parameter set options, given the number of parameters we are uncertain about and the range of values we think each one could realistically take. More data with which to check model performance or model realism (potentially of different kinds), and more information to constrain the range of potential parameter values that are considered reasonable, can assist in reducing equifinality. Equifinality can also have to do with the model structure. For example, one set of parameters may produce better fitting model outputs for dry periods, while another set of parameter values has better outputs for wet periods. The two sets have comparable outcomes for overall combined statistics. This could be because properties or processes of the catchment actually shift more over time than the model structure itself allows for. It takes exploration of the ‘parameter space’ to identify equifinality and not all modelling tools facilitate this. When equifinality is identified, a suite of similarly acceptable parameter sets can be applied and the range of the outputs of this set of models can be presented as the project outcome, rather than relying on the model outputs of a single set of parameter values. Different modelling tools, and structures, make this a simpler or harder task to complete.

Modelling tool user interfaces

2023-11-27T20:39:49Z

Julia Glenday:

''' PAGE IN PROGRESS - MORE COMING SOON! '''

The table below gives a comparison of the user interface for each of the modelling tools.

== Interface comparison overview ==

{| class="wikitable"
! scope="col" style="width:15em" | Interface characteristic
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
|-
| style="vertical-align: vertical-align: center;" |Graphical user interface ''(vs code prompt)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Catchment map display (visualise linkages)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model run times'''
|-
| style="vertical-align: vertical-align: center;" |Rough estimate of time needed for a 30 year run for a model of a 300km^2 catchment ''(Note: will depend on model set-up complexity & computing power)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |tens of minutes
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |hours
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Computing resources needed'''
|-
| style="vertical-align: vertical-align: center;" |Comparative rating of computing power needed to achieve workable run times.
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |Light
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |Light
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |Light
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |Medium
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |Intensive (need good GPU)
|-
| colspan="6" style="background: #FFFFFF; vertical-align: vertical-align: center;" |'''Model set-up ease & efficiency'''
|-
| style="vertical-align: vertical-align: center;" |Automated creation of model units & connections from map inputs ''(vs fully manual creation)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Input parameter values and change values for batches of models units ''(e.g., all HRUs of a cover type)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |In-built database of suggested parameter values ''(e.g., for common vegetation types, soil types, etc.)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |no
|-
| style="vertical-align: vertical-align: center;" |User can build own parameter databases for use across multiple models
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model set-up transparency''' (i.e., is it obvious what the model is doing/assuming?)
|-
| style="vertical-align: vertical-align: center;" |Interface makes the user interact with every component & parameter entry option during model set-up ''(vs having default parameter values pre-entered & not forcing user to view them)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |no
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Tool checks connection errors
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Batch runs & calibration tools'''
|-
| style="vertical-align: vertical-align: center;" |Facility for batch runs, parameter sensitivity analyses, uncertainty analyses & auto-calibration
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Accessing model output'''
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for streamflow
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for water balance fluxes and stores
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |All water balance components that are calculated by the model can be exported
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Batch export of water balance fluxes for model's basic spatial units
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Automated extraction of water balance fluxes for different spatial scales ''(e.g., by cover class area, by subcatchment, full catchment)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|}

== Formats for input-output data ==

== Computing resources ==

== Run times ==
Run times for models built with a given tool can vary considerably with the size and complexity of the set-up, the number of timesteps in the run, and the computer being used. This makes is difficult to generalise, however, due to their relative simplicity WRSM, SPATSIM, and ACRU4 models in these exercises generally ran in a matter of a few minutes for a 30 year run, while the ArcSWAT and MIKE-SHE models could range from 15 minutes to several hours to complete this.

The run times have import particularly for parameter adjustment testing, limiting how much can be done in the time available for a project. However, the tools that have long run times, as well as SPATSIM, have made the parameter adjustment process quick and allow batch run facilities. Once set-up time-consuming testing runs can be ongoing without manual intervention needed from the modeller, freeing their time for other work. Although WRSM and ACRU4 run quickly, the process of making parameter adjustments in the model set-up to be tested takes a long time and a lot of manual effort as described above.

Modelling tool user interfaces

2023-11-27T20:30:37Z

Julia Glenday: /* Interface comparison overview */

''' PAGE IN PROGRESS - MORE COMING SOON! '''

The table below gives a comparison of the user interface for each of the modelling tools. For more detailed descriptions see the sections that follow.

== Interface comparison overview ==

{| class="wikitable"
! scope="col" style="width:15em" | Interface characteristic
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
|-
| style="vertical-align: vertical-align: center;" |Graphical user interface ''(vs code prompt)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Catchment map display (visualise linkages)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF; vertical-align: vertical-align: center;" |'''Model set-up ease & efficiency'''
|-
| style="vertical-align: vertical-align: center;" |Automated creation of model units & connections from map inputs ''(vs fully manual creation)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Input parameter values and change values for batches of models units ''(e.g., all HRUs of a cover type)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |In-built database of suggested parameter values ''(e.g., for common vegetation types, soil types, etc.)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |no
|-
| style="vertical-align: vertical-align: center;" |User can build own parameter databases for use across multiple models
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model set-up transparency''' (i.e., is it obvious what the model is doing/assuming?)
|-
| style="vertical-align: vertical-align: center;" |Interface makes the user interact with every component & parameter entry option during model set-up ''(vs having default parameter values pre-entered & not forcing user to view them before completing set-up)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |no
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Tool checks connection errors
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Batch runs & calibration tools'''
|-
| style="vertical-align: vertical-align: center;" |Facility for batch runs, parameter sensitivity analyses, uncertainty analyses & auto-calibration
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Model run times'''
|-
| style="vertical-align: vertical-align: center;" |Rough estimate of time needed for a 30 year run for a model of a 300km^2 catchment ''(Note: will depend on model set-up complexity & computing power)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |tens of minutes
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |hours
|-
| colspan="6" style="background: #FFFFFF;vertical-align: vertical-align: center;" |'''Accessing model output'''
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for streamflow
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for water balance fluxes and stores
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |All water balance components that are calculated by the model can be exported
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Batch export of water balance fluxes for model's basic spatial units
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Automated extraction of water balance fluxes for different spatial scales ''(e.g., by cover class area, by subcatchment, full catchment)''
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|}

== Formats for input-output data ==

== Computing resources ==

== Run times ==
Run times for models built with a given tool can vary considerably with the size and complexity of the set-up, the number of timesteps in the run, and the computer being used. This makes is difficult to generalise, however, due to their relative simplicity WRSM, SPATSIM, and ACRU4 models in these exercises generally ran in a matter of a few minutes for a 30 year run, while the ArcSWAT and MIKE-SHE models could range from 15 minutes to several hours to complete this.

The run times have import particularly for parameter adjustment testing, limiting how much can be done in the time available for a project. However, the tools that have long run times, as well as SPATSIM, have made the parameter adjustment process quick and allow batch run facilities. Once set-up time-consuming testing runs can be ongoing without manual intervention needed from the modeller, freeing their time for other work. Although WRSM and ACRU4 run quickly, the process of making parameter adjustments in the model set-up to be tested takes a long time and a lot of manual effort as described above.

Modelling tool user interfaces

2023-11-27T20:15:34Z

Julia Glenday:

''' PAGE IN PROGRESS - MORE COMING SOON! '''

The table below gives a comparison of the user interface for each of the modelling tools. For more detailed descriptions see the sections that follow.

== Interface comparison overview ==

{| class="wikitable"
! scope="col" style="width:15em" | Interface characteristic
! scope="col" style="background: #F2CEE0; width:8em" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:8em" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:8em" |ACRU4
! scope="col" style="background: #F2F2CE; width:8em" |SWAT2012
! scope="col" style="background: #CEE6F2; width:8em" |MIKE-SHE
|-
| style="vertical-align: vertical-align: center;" |Graphical user interface (vs code prompt)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Catchment map display (visualise linkages)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="vertical-align: vertical-align: center;" |'''Model set-up efficiency (ease)'''
|-
| style="vertical-align: vertical-align: center;" |Automated creation of model units & connections from map inputs (vs fully manual creation)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Input & change parameters for model units (e.g., HRUs, grid cells) in batches by type (e.g., cover type, soil type)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |In-built database of suggested parameter values (e.g. for common/generic vegetation types, soil types, etc.)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |no
|-
| style="vertical-align: vertical-align: center;" |User can build own parameter databases for use across multiple models
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="vertical-align: vertical-align: center;" |'''Model set-up transparency (i.e., is it obvious what the model is doing/assuming?)'''
|-
| style="vertical-align: vertical-align: center;" |Interface makes the user interact with every component & parameter entry option during model set-up (vs having default parameter values pre-entered and not forcing user to view them before completing set-up)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |no
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Tool checks connection errors
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="vertical-align: vertical-align: center;" |'''Batch runs & calibration tools'''
|-
| style="vertical-align: vertical-align: center;" |Facility for batch runs, parameter sensitivity analyses, uncertainty analyses & auto-calibration (in-built functions or an associated tool)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| colspan="6" style="vertical-align: vertical-align: center;" |'''Model run times'''
|-
| style="vertical-align: vertical-align: center;" |Rough estimate of time needed for a 30 year run for a model of a 300km^2 catchment (Note: will depend on model set-up complexity & computing power)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |seconds to minutes
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |tens of minutes
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |hours
|-
| colspan="6" style="vertical-align: vertical-align: center;" |'''Accessing model output'''
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for streamflow
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Output viewer tool for water balance fluxes and stores
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |All water balance components that are calculated by the model can be exported
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Batch export of water balance fluxes for model's basic spatial units
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |'''yes'''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|-
| style="vertical-align: vertical-align: center;" |Automated extraction of water balance fluxes for different spatial scales (e.g., by cover class area, by subcatchment, full catchment)
| style="background: #FFF5FA; vertical-align: center; text-align:center;" |no
| style="background: #FFF7F5; vertical-align: center; text-align:center;" |no
| style="background: #F5FFF5; vertical-align: center; text-align:center;" |no
| style="background: #FFFFF5; vertical-align: center; text-align:center;" |''(limited)''
| style="background: #F5FCFF; vertical-align: center; text-align:center;" |'''yes'''
|}

== Formats for input-output data ==

== Computing resources ==

== Run times ==
Run times for models built with a given tool can vary considerably with the size and complexity of the set-up, the number of timesteps in the run, and the computer being used. This makes is difficult to generalise, however, due to their relative simplicity WRSM, SPATSIM, and ACRU4 models in these exercises generally ran in a matter of a few minutes for a 30 year run, while the ArcSWAT and MIKE-SHE models could range from 15 minutes to several hours to complete this.

The run times have import particularly for parameter adjustment testing, limiting how much can be done in the time available for a project. However, the tools that have long run times, as well as SPATSIM, have made the parameter adjustment process quick and allow batch run facilities. Once set-up time-consuming testing runs can be ongoing without manual intervention needed from the modeller, freeing their time for other work. Although WRSM and ACRU4 run quickly, the process of making parameter adjustments in the model set-up to be tested takes a long time and a lot of manual effort as described above.

Process representation across tools

2023-11-27T13:59:50Z

Julia Glenday:

The tables below summarise information about different process representation [[Terminology#algorithm anchor|algorithms]] across the set of modelling tools. They cover the inputs used to model the occurrence and rate (amount per model calculation timestep) of the given hydrological process (e.g. infiltration of water into the soil) as well as some general characteristics of the equations, particularly noting if there are thresholds involved and what these are. The tables can be used to understand what is being considered in the calculation of each process and what inputs each modelling tool needs. Not all the processes listed are represented explicitly by all the tools. This is highlighted in the tables below and an overview is also presented in the [[Modelling tool capability overview#Modelling tool capabilities summary|capabilities overview table]]. The nature of the algorithms used and their inputs are linked to the '''spatial and temporal scale''' at which the process is being represented in the given tool, described further for each one [[Model units & connections|here]].

In these tables '''thresholds''' refer to limits that determine when a process would start to occur or would stop occurring. For example, the field capacity soil moisture of a soil is often used as the threshold soil moisture level for percolation of water downwards (to a lower soil layer or to recharge groundwater). If soil moisture is lower than this, no percolation will be calculated in the model. There may be multiple thresholds considered when modelling a process. For example, evapotranspiration of soil moisture may be assumed to stop once the atmospheric demand in the timestep has been met or once the soil moisture has reached wilting point level, even if demand has not yet been met.

The inputs to a process algorithm can include:
* input data (e.g., rainfall, using the rainfall input for a particular modelled unit, for a given timestep),
* property parameter values that the user inputs in the model set-up (e.g., soil moisture content at saturation for a soil layer in a modelled unit)
* states or water storage levels that the model calculated internally for the timestep, so not directly input by the user (e.g., soil moisture content in a certain soil layer at a given timestep)
Different software tools may refer to equivalent inputs using different words and sometimes they require the user to input different specific property values, but end up calculating the same derived property. For example, on software tool may require porosity of soil to be input, another may require bulk density, and another may as for volumetric soil moisture at saturation, any of these, coupled with soil layer depth, can be used to calculate the maximum (or saturation) soil water storage volume. Where possible, similar terms have been used across tools in the tables below to highlight their conceptual similarities where these exist. Details about some of the contrasting terminology used in the interfaces of different tools can be found [[Terminology#Hydrological process and parameter terms across tools|here]].


== Canopy interception and evaporation (vs throughfall) ==
{| class="wikitable"
! scope="col" width:10%"| Algorithm description
! scope="col" style="background: #F2CEE0; width:18%" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:18%" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:18%" |ACRU4
! scope="col" style="background: #F2F2CE; width:18%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:18%" |MIKE-SHE, [[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed & fully distributed]]
|-
| style="vertical-align: top" | '''Algorithm inputs''' ''(input data, model calculated states / storages, property parameters)''
| style="background: #FFF5FA; vertical-align: top" |
 
* Rain
* '''''Cover properties:'''''
** max interception
 
| style="background: #FFF7F5; vertical-align: top" |
 
* Rain
* '''''Cover properties:'''''
** max interception
 
| style="background: #F5FFF5; vertical-align: top" |
 
* Rain
* PET
* Canopy storage ''(state)''
* '''''Cover properties:'''''
** max interception (OR LAI)
 
| style="background: #FFFFF5; vertical-align: top"; rowspan= "3" |
 '''Canopy interception is not explicitly modelled when using daily timestep modelling.''' 
''It is implicitly considered in the ‘initial abstraction’, see infiltration & surface runoff below''
| style="background: #F5FCFF; vertical-align: top" |
 
* Rain
* PET
* Canopy storage ''(state)''
* '''''Cover properties:'''''
**LAI
**canopy interception coefficient
 
|-
| style="vertical-align: top" |'''Function type'''
| style="background: #FFF5FA; vertical-align: top" |exponential & threshold
| style="background: #FFF7F5; vertical-align: top" |exponential & threshold
| style="background: #F5FFF5; vertical-align: top" |threshold
| style="background: #F5FCFF; vertical-align: top" |threshold
|-
| style="vertical-align: top" |'''Thresholds'''
| style="background: #FFF5FA; vertical-align: top" |
'''yes:'''
 
timestep interception capacity ''(calculated)''
| style="background: #FFF7F5; vertical-align: top" |
'''yes:'''
 
timestep interception capacity ''(calculated)''
| style="background: #F5FFF5; vertical-align: top" |
'''yes:'''
 
timestep interception capacity ''(calculated)''
| style="background: #F5FCFF; vertical-align: top" |
'''yes:'''
 
timestep interception capacity ''(calculated)''
|}
[[#Process rep - pg top|Back to top of page]]



== Infiltration into soil moisture (vs surface runoff or surface ponding) ==
'''Note:''' This excludes the case of a modelling unit (HRU, grid cell, area within a subcatchment, etc.) is designated as '''''impervious'''''. In this case, rain inputs would become surface runoff, potentially with a portion staying behind as surface storage/ponding if the area has attenuation specified (to represent roughness and flatness).
{| class="wikitable"
! scope="col" style="width:10%" | Algorithm description
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed, more conceptual]]
! scope="col" style="background: #CEDAF2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed, more physical]]
|-
| style="vertical-align: top" | '''Algorithm inputs''' ''(input data, model calculated states / storages, property parameters)''
| style="background: #FFF5FA; vertical-align: top" |
 
* Rain
* Rainfall distribution factor
* Soil moisture ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Infiltration rate distribution (min, max)
 
| style="background: #FFF7F5; vertical-align: top" |
 
* Rain
* Rainfall distribution factor
* Soil moisture ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Infiltration rate distribution (min, max)
 
| style="background: #F5FFF5; vertical-align: top" |
 
* Throughfall (rain-interception)
* Soil moisture within "infiltration depth"''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** "Infiltration depth" parameter
** Macropore by-pass (clay cracking)
 
| style="background: #FFFFF5; vertical-align: top"|
 
* Throughfall (rain-interception)
* Soil moisture ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Curve number (SCS-CN)
** Macropore by-pass
 
| style="background: #F5FCFF; vertical-align: top" |
 
* Throughfall (rain-interception)
* Soil moisture ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Saturated hydraulic conductivity (Ksat),
** Macropore by-pass
 
| style="background: #F5F8FF; vertical-align: top" |
 
* Throughfall (rain-interception)
* Soil moisture ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Soil moisture retention curve
** Saturated hydraulic conductivity (Ksat),
** Macropore by-pass
 
|-
| style="vertical-align: top" |'''Function type'''
| style="background: #FFF5FA; vertical-align: top" |non-linear & threshold
| style="background: #FFF7F5; vertical-align: top" |non-linear & threshold
| style="background: #F5FFF5; vertical-align: top" |power & threshold
| style="background: #FFFFF5; vertical-align: top" |power & threshold
| style="background: #F5FCFF; vertical-align: top" |linear (rate) & threshold
| style="background: #F5F8FF; vertical-align: top" |non-linear & threshold
|-
| style="vertical-align: top" |'''Thresholds'''
| style="background: #FFF5FA; vertical-align: top" |
'''yes:'''
 Max infiltration rate,
 Saturation soil moisture*
 *Saturation excess becomes interflow, not surface runoff
| style="background: #FFF7F5; vertical-align: top" |
'''yes:'''
 Max infiltration rate,
 Saturation soil moisture*
 *Saturation excess becomes interflow, not surface runoff
| style="background: #F5FFF5; vertical-align: top" |
'''yes:'''
 Saturation soil moisture*
 *Fraction of saturation excess becomes "delayed flow"~interflow, not "quickflow"~surface runoff
| style="background: #FFFFF5; vertical-align: top"|
'''yes:'''
 Max infiltration rate ''(calculated),''
 Saturation soil moisture
| style="background: #F5FCFF; vertical-align: top" |
'''yes:'''
 Max infiltration rate (uses Ksat),
 Saturation soil moisture
| style="background: #F5F8FF; vertical-align: top" |
'''yes:'''
 Max infiltration rate ''(calculated)'',
 Saturation soil moisture
|}
[[#Process rep - pg top|Back to top of page]]



== Surface runoff to channel network ==
'''Note on surface runoff vs ponding and surface storage:''' In the Pitman models, all water not calculated to infiltrate in a timestep, which is a month, is assumed to be runoff. For models with shorter timesteps, water reaching the land surface which does not infiltrate into soil in a timestep can become surface runoff or remain as surface ponding/surface storage. In subsequent model timesteps, water still on the land surface can evaporate, infiltrate, and/or become surface runoff in the next timestep. Some models have relatively short timesteps (subdaily, daily) compared to the rate at which water would move all the way across a modelled land unit (which could be large, rough, and/or flat, slowing the flow rate). This is why some water will be 'surface storage' in one timestep and then 'surface runoff' in the next timestep. MIKE-SHE can also consider that land surfaces can be very rough, or have dips that trap water, and so some amount surface water will not be able to run off at all (detention storage). This water will both evaporate and infiltrate over time.
 ACRU4 differs notably, assuming the water that does not infiltrate into soil accounts for both surface runoff and interflow runoff.
{| class="wikitable"
! scope="col" style="width:10%" | Algorithm description
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed, more conceptual]]
! scope="col" style="background: #CEDAF2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed, more physical]]
|-
| style="vertical-align: top" | '''Algorithm inputs''' ''(input data, model calculated states / storages, property parameters)''
| style="background: #FFF5FA; vertical-align: top" |
 
* Surface water present* ''(state)''
 
 *Month timestep: all water not infiltrating becomes runoff 
 
| style="background: #FFF7F5; vertical-align: top" |
 
* Surface water present* ''(state)''
 
 *Month timestep: all water not infiltrating becomes runoff 
 
| style="background: #F5FFF5; vertical-align: top" |
 
* Surface water present* ''(state)''
* Lag coefficient*
 
 *Lag coefficient separates "quickflow"~surface runoff from "delayed-flow"~interflow. Quickflow portion reaches the channel on the same day generated (rain day). The rest is lagged over subsequent days 
| style="background: #FFFFF5; vertical-align: top"|
 
* Surface water present* ''(state)''
* '''''Surface path properties:'''''
** Path length
** Slope
** Roughness (Manning's n)
 
| style="background: #F5FCFF; vertical-align: top" |
 
* Surface water present* ''(state)''
* '''''Surface path properties:'''''
** Detention storage
** Path length
** Slope
** Roughness (Manning's n)
 
| style="background: #F5F8FF; vertical-align: top" |
 
* Surface water present* ''(state)''
* '''''Surface path properties:'''''
** Detention storage
** Path length (from gridded topography)
** Slope(from gridded topography)
** Roughness (Manning's n)
 
|-
| style="vertical-align: top" |'''Function type'''
| style="background: #FFF5FA; vertical-align: top" |(no transformation)
| style="background: #FFF7F5; vertical-align: top" |(no transformation)
| style="background: #F5FFF5; vertical-align: top" |(no transformation)
| style="background: #FFFFF5; vertical-align: top" |non-linear
| style="background: #F5FCFF; vertical-align: top" |non-linear & threshold
| style="background: #F5F8FF; vertical-align: top" |non-linear & threshold
|-
| style="vertical-align: top" |'''Thresholds'''
| style="background: #FFF5FA; vertical-align: top" |
no*
 *none after infiltration has been calculated 
| style="background: #FFF7F5; vertical-align: top" |
no*
 *none after infiltration has been calculated 
| style="background: #F5FFF5; vertical-align: top" |
no*
 *none after infiltration has been calculated 
| style="background: #FFFFF5; vertical-align: top"|
no*
 *none after infiltration has been calculated 
| style="background: #F5FCFF; vertical-align: top" |
'''yes:'''
 Detention storage
| style="background: #F5F8FF; vertical-align: top" |
'''yes:'''
 Detention storage
|}
[[#Process rep - pg top|Back to top of page]]



== Evapotranspiration (ET) from soil moisture (SM) ==
'''Note: More coverage of evapotranspiration related terminology and inputs across different tools can be found [[Terminology#Evapotranspiration terms across tools|here]]'''
{| class="wikitable"
! scope="col" style="width:10%" | Algorithm description
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed, more conceptual]]
! scope="col" style="background: #CEDAF2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed, more physical]]
|-
| style="vertical-align: top" | '''Algorithm inputs''' ''(input data, model calculated states / storages, property parameters)''
| style="background: #FFF5FA; vertical-align: top" |
 
* S-Pan evaporation
* Soil moisture ''(state)''
* '''''Vegetation properties:'''''
** "Crop" coefficient (vs pan)
** Pitman ET coefficient*
* '''''Soil properties:'''''
** Saturation soil moisture
*determines linear decline of ET with soil moisture decline
 
| style="background: #FFF7F5; vertical-align: top" |
 
* S-Pan evaporation
* Soil moisture ''(state)''
* '''''Vegetation properties:'''''
** "Crop" coefficient (vs pan)
** Pitman ET coefficient*
* '''''Soil properties:'''''
** Saturation soil moisture
*determines linear decline of ET with soil moisture decline
 
| style="background: #F5FFF5; vertical-align: top" |
 
* A-Pan evaporation
* Soil moisture ''(state)''
* '''''Vegetation properties:'''''
** "Crop" coefficient (vs pan)
** Root depth distribution
* '''''Soil properties:'''''
** Saturation soil moisture*
** Field capacity SM
** Wilting point SM
*ET assumed to also decline if soil gets close to saturation, waterlogging, unless wetland plants
 
| style="background: #FFFFF5; vertical-align: top"|
 
* Remaining ET demand (PET - Canopy evap.)
* Soil moisture ''(state)''
* '''''Vegetation properties:'''''
** LAI
** Root depth (max)
** Root distribution
** Demand redistribution coefficient
* '''''Soil properties:'''''
** Field capacity SM
** Wilting point SM
 
| style="background: #F5FCFF; vertical-align: top" |
 
* Remaining ET demand (PET - Canopy evap. - Ponded evap.)
* Soil moisture ''(state)''
* '''''Vegetation properties:'''''
** "Crop" coefficient
** ET curtailment SM
** Root depth (max)
** Root distribution
* '''''Soil properties:'''''
** Field capacity SM
** Wilting point SM
 
| style="background: #F5F8FF; vertical-align: top" |
 
* Remaining ET demand (PET - Canopy evap. - Ponded evap.)
* Soil moisture ''(state)''
* '''''Vegetation properties:'''''
** "Crop" coefficient
** ET vs SM curve parameter
** Root depth (max)
** Root distribution
** ET demand depth distribution
* '''''Soil properties:'''''
** Soil moisture retention curve
 
|-
| style="vertical-align: top" |'''Function type'''
| style="background: #FFF5FA; vertical-align: top" |linear & threshold
| style="background: #FFF7F5; vertical-align: top" |linear & threshold
| style="background: #F5FFF5; vertical-align: top" |multi-part linear & threshold
| style="background: #FFFFF5; vertical-align: top" |non-linear & threshold
| style="background: #F5FCFF; vertical-align: top" |multi-part linear & threshold
| style="background: #F5F8FF; vertical-align: top" |non-linear & threshold
|-
| style="vertical-align: top" |'''Thresholds'''
| style="background: #FFF5FA; vertical-align: top" |
'''yes:'''
 ET demand,
 Wilting point SM
| style="background: #FFF7F5; vertical-align: top" |
'''yes:'''
 ET demand,
 Wilting point SM
| style="background: #F5FFF5; vertical-align: top" |
'''yes:'''
 ET demand,
 Wilting point SM
| style="background: #FFFFF5; vertical-align: top"|
'''yes:'''
 ET demand,
 Wilting point SM
| style="background: #F5FCFF; vertical-align: top" |
'''yes:'''
 ET demand,
 Wilting point SM
| style="background: #F5F8FF; vertical-align: top" |
'''yes:'''
 ET demand,
 Wilting point SM
|}
[[#Process rep - pg top|Back to top of page]]



== Evapotranspiration (ET) from groundwater (GW) ==
'''Note:''' More coverage of evapotranspiration related terminology and inputs across different tools can be found '''[[Terminology#Evapotranspiration terms across tools|here]]'''
{| class="wikitable"
! scope="col" style="width:10%" | Algorithm description
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman (Sami GW)
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman (Hughes GW)
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed, more conceptual]]
! scope="col" style="background: #CEDAF2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed, more physical]]
|-
| style="vertical-align: top" | '''Algorithm inputs''' ''(input data, model calculated states / storages, property parameters)''
| style="background: #FFF5FA; vertical-align: top" |
 
''riparian area only''
* A-Pan evaporation
* Riparian area
* Aquifer storage ''(state)''
* '''''Vegetation properties:'''''
** "Crop" coefficient (vs pan)
* '''''Aquifer properties:'''''
** Storage limit for ET
 
| style="background: #FFF7F5; vertical-align: top" |
 
''riparian area only''
* Remaining ET demand (PET - ET from soil)
* Riparian area
* Aquifer storage ''(state)''
* '''''Vegetation properties:'''''
** "Crop" coefficient (vs pan)
** Pitman ET coefficient*
* '''''Aquifer properties:'''''
** Storage limit for ET
 
| style="background: #F5FFF5; vertical-align: top" ; rowspan= "3" |
 
''riparian area only''
'''Indirect representation:'''
''Specified riparian zone HRU can receive a user-specified fraction of the aquifer outflow from connected upslope HRUs. This water is added to riparian HRU soil in the B-horizon, where it can be accessed for ET and can recharge GW.''
 ''No ET (or capillary rise) is simulated from the GW store of the riparian HRU.''
 
| style="background: #FFFFF5; vertical-align: top"|
 
''represented through capillary rise into the soil driven by ET demand''
* PET
* Aquifer storage ''(state)''
* '''''Soil properties:'''''
** Capillary rise rate coefficient
* '''''Aquifer properties:'''''
** Storage limit for capillary rise
''+ all inputs for ET from soil''
 
| style="background: #F5FCFF; vertical-align: top" |
 
''riparian area only''
 ''represented through capillary rise into the soil driven by ET demand''
* Remaining ET demand (PET - Canopy evap. - Ponded evap. - ET from soil)
* Aquifer storage ''(state)''
* '''''Aquifer properties:'''''
** Storage limit for capillary rise
''+ all inputs for [[#Evapotranspiration (ET) from soil moisture (SM)|ET from soil]]''
 
| style="background: #F5F8FF; vertical-align: top" |
 
''capillary rise is calculated, but roots can also extend below the water table and withdraw directly''
* Remaining ET demand (PET - Canopy evap. - Ponded evap. - ET from soil)
* Water table depth ''(state)''
* '''''Aquifer properties:'''''
** Saturated hydraulic conductivity (Ksat)
''+ vegetation property inputs for [[#Evapotranspiration (ET) from soil moisture (SM)|ET from soil]]''
 
|-
| style="vertical-align: top" |'''Function type'''
| style="background: #FFF5FA; vertical-align: top" |non-linear & threshold
| style="background: #FFF7F5; vertical-align: top" |non-linear & threshold
| style="background: #FFFFF5; vertical-align: top" |non-linear & threshold
| style="background: #F5FCFF; vertical-align: top" |non-linear & threshold
| style="background: #F5F8FF; vertical-align: top" |non-linear & threshold
|-
| style="vertical-align: top" |'''Thresholds'''
| style="background: #FFF5FA; vertical-align: top" |
'''yes:'''
 ET demand,
 Aquifer storage limit for ET
| style="background: #FFF7F5; vertical-align: top" |
'''yes:'''
 ET demand,
 Aquifer storage limit for ET
| style="background: #FFFFF5; vertical-align: top"|
'''yes:'''
 ET demand,
 Aquifer storage limit for capillary rise
| style="background: #F5FCFF; vertical-align: top" |
'''yes:'''
 ET demand,
 Aquifer storage limit for capillary rise
| style="background: #F5F8FF; vertical-align: top" |
'''yes:'''
 ET demand,
 Water table depth vs root depth
|}
[[#Process rep - pg top|Back to top of page]]



== Interflow generation & routing to channel network ==
{| class="wikitable"
! scope="col" style="width:10%" | Algorithm description
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed, more conceptual]]
! scope="col" style="background: #CEDAF2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed, more physical]]
|-
| style="vertical-align: top" | '''Algorithm inputs''' ''(input data, model calculated states / storages, property parameters)''
| style="background: #FFF5FA; vertical-align: top" |
 
''Interflow from soil layer & from "percolation zone"''
* Soil moisture ''(state)''
* Percolation zone storage ''(state)''
* Aquifer storage ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Field capacity SM
** Interflow rate power coefficient
** Max interflow rate
** Interflow lag coefficient
* '''''Percolation zone properties'''''
** Max storage capacity
* '''''Aquifer properties'''''
** Max storage capacity
 
| style="background: #FFF7F5; vertical-align: top" |
 
''Interflow from soil layer''
* Soil moisture ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Field capacity SM
** Interflow rate power coefficient
** Max interflow rate
** Interflow lag coefficient
 
| style="background: #F5FFF5; vertical-align: top"; rowspan= "3" |
 
'''Interflow amount calculated in the same step as surface runoff, not as a separate process:'''
''total surface runoff + interflow runoff is calculated in the [[#Infiltration into soil moisture (vs surface runoff or surface ponding)|infiltration]] vs [[#Surface runoff to channel network|runoff]] step, then these are separated through lagging''
* Surface water present* ''(state)''
* Lag coefficient*
 *Lag coefficient separates "quickflow"~surface runoff from "delayed-flow"~interflow. The lagged flow that doesn't reach the channel on the rain day, but instead reaches the channel over subsequent days can be considered interflow 
 
| style="background: #FFFFF5; vertical-align: top"|
 
''Interflow from soil layer''
* Soil moisture ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Field capacity SM
** Drainage slope
** Saturated hydraulic conductivity (Ksat)
 
| style="background: #F5FCFF; vertical-align: top" |
 
''Interflow from "interflow zone" (IZ)''
''to calc input into IZ:''
* Macropore flow (Throughfall * by-pass coefficient)
* Soil moisture ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Field capacity SM
** Drainage slope
** Saturated hydraulic conductivity (Ksat)
''to calc outflow from IZ:''
* IZ storage ''(state)''
* '''''IZ properties:'''''
** Storage threshold for outflow
** Lateral outflow rate constant
 
| style="background: #F5F8FF; vertical-align: top"; rowspan= "3" |
 
'''Interflow not modelled as a separate process to "saturated zone" flow.'''
 ''Lateral flow through a "saturated zone" material layer in the model which is not frequently saturated and/or is perched above more permanently saturated layers can be considered as interflow. Flows through different layers can be exported as separate model outputs.''

''See [[#Aquifer exchanges with channel: aquifer outflow to channel and channel transmission loss|groundwater outflow to channel]]''
 
|-
| style="vertical-align: top" |'''Function type'''
| style="background: #FFF5FA; vertical-align: top" |non-linear & threshold
| style="background: #FFF7F5; vertical-align: top" |non-linear & threshold
| style="background: #FFFFF5; vertical-align: top" |non-linear & threshold
| style="background: #F5FCFF; vertical-align: top" |two step: non-linear & threshold, linear reservoir & threshold
|-
| style="vertical-align: top" |'''Thresholds'''
| style="background: #FFF5FA; vertical-align: top" |
'''yes:'''
 Field capacity SM,
 Percolation zone max storage + Aquifer max storage
| style="background: #FFF7F5; vertical-align: top" |
'''yes:'''
 Field capacity SM
| style="background: #FFFFF5; vertical-align: top" |
'''yes:'''
 Field capacity SM
| style="background: #F5FCFF; vertical-align: top" |
'''yes:'''
 Field capacity SM
 IZ storage threshold for outflow
|}
[[#Process rep - pg top|Back to top of page]]



== Aquifer recharge ==
{| class="wikitable"
! scope="col" style="width:10%" | Algorithm description
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman(Sami GW)
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman(Hughes GW)
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed, more conceptual]]
! scope="col" style="background: #CEDAF2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed, more physical]]
|-
| style="vertical-align: top" | '''Algorithm inputs''' ''(input data, model calculated states / storages, property parameters)''
| style="background: #FFF5FA; vertical-align: top" |
 
''Recharge via "percolation zone" (vadose zone)''
* Soil moisture ''(state)''
* Vadose zone storage ''(state)''
* Aquifer storage ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Field capacity SM
** Percolation power coefficient
** Max percolation rate
*'''''Percolation zone properties:'''''
** Recharge lag coefficient
** Max storage capacity
*'''''Aquifer properties:'''''
** Max storage capacity
 
| style="background: #FFF7F5; vertical-align: top" |
 
''Recharge from soil column''
* Soil moisture ''(state)''
* Aquifer storage ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Field capacity SM
** Percolation power coefficient
** Max percolation rate
*'''''Aquifer properties:'''''
** Max storage capacity
 
| style="background: #F5FFF5; vertical-align: top" |
 
''Recharge from soil column*''
* Soil moisture ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Field capacity SM
** Percolation rate (~Ksat)
 
*Aquifer storage is unlimited
 
| style="background: #FFFFF5; vertical-align: top"|
 
''Recharge via vadose zone''
* Soil moisture ''(state)''
* Vadose zone storage ''(state)''
* Aquifer storage ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Field capacity SM
** Saturated hydraulic conductivity (Ksat)
*'''''Vadose zone (VZ) properties:'''''
** Field capacity
** Saturated hydraulic conductivity (Ksat)
*'''''Aquifer properties:'''''
** Max storage capacity
 
| style="background: #F5FCFF; vertical-align: top" |
 
''Recharge via "interflow zone"''
* Soil moisture ''(state)''
* Interflow zone storage ''(state)''
* Aquifer storage ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Field capacity SM
** Saturated hydraulic conductivity (Ksat)
*'''''Interflow zone (IZ) properties:'''''
**Storage threshold for outflow
**Vertical outflow rate constant
*'''''Aquifer properties:'''''
** Max storage capacity
 
| style="background: #F5F8FF; vertical-align: top" |
 
''Recharge from soil column''
* Soil moisture ''(state)''
* Aquifer storage ''(state)''
* '''''Soil properties:'''''
** Saturation soil moisture
** Moisture retention curve
** Saturated hydraulic conductivity (Ksat)
*'''''Aquifer properties:'''''
** Max storage capacity
** Conductivity (Ksat)
 
|-
| style="vertical-align: top" |'''Function type'''
| style="background: #FFF5FA; vertical-align: top" |two step: non-linear & threshold, non-linear
| style="background: #FFF7F5; vertical-align: top" |non-linear & threshold
| style="background: #F5FFF5; vertical-align: top" |non-linear & threshold
| style="background: #FFFFF5; vertical-align: top" |two step: non-linear & threshold, non-linear & threshold
| style="background: #F5FCFF; vertical-align: top" |two step: non-linear & threshold, linear reservoir & threshold
| style="background: #F5F8FF; vertical-align: top" |non-linear & threshold
|-
| style="vertical-align: top" |'''Thresholds'''
| style="background: #FFF5FA; vertical-align: top" |
'''yes:'''
 Field capacity SM,
 Vadose zone max storage
 Aquifer max storage
| style="background: #FFF7F5; vertical-align: top" |
'''yes:'''
 Field capacity SM,
 Aquifer max storage
| style="background: #F5FFF5; vertical-align: top" |
'''yes:'''
 Field capacity SM
 
*Aquifer storage is unlimited
| style="background: #FFFFF5; vertical-align: top"|
'''yes:'''
 Field capacity SM,
 Vadose zone field capacity
 Aquifer max storage
| style="background: #F5FCFF; vertical-align: top" |
'''yes:'''
 Field capacity SM,
 Aquifer max storage
| style="background: #F5F8FF; vertical-align: top" |
'''yes:'''
 Field capacity SM,
 Aquifer max storage
|}
[[#Process rep - pg top|Back to top of page]]



== Groundwater (GW) flow: lateral flow '''within''' the saturated zone ==
'''Note:''' This refers to groundwater flow between modelled land units, such as grid cells, HRUs, or subcatchments, depending on the scale that groundwater stores and flows are modelled at (see more on scales of process representation for GW [[Model units & connections#Aquifers: spatial distribution, vertical layers, connections|here]])
 For coverage of groundwater outflow into a river channel, see the table [[#Aquifer exchanges with channel: aquifer outflow to channel and channel transmission loss|below]]
{| class="wikitable"
! scope="col" style="width:10%" | Algorithm description
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman(Sami GW)
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman(Hughes GW)
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed, more conceptual]]
! scope="col" style="background: #CEDAF2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed, more physical]]
|-
| style="vertical-align: top" | '''Algorithm inputs''' ''(input data, model calculated states / storages, property parameters)''
| style="background: #FFF5FA; vertical-align: top" |
 
''GW flow between subcatchments''
* Aquifer storage ''(state)''
*'''''Aquifer properties:'''''
** Transmissivity
** Storage threshold for flow
** Regional GW slope
 
| style="background: #FFF7F5; vertical-align: top" |
 
''GW flow between subcatchments''
* Aquifer storage ''(state)''
*'''''Aquifer properties:'''''
** Transmissivity
** Storage threshold for flow
** Regional GW slope'''''
** Max storage capacity
 
| style="background: #F5FFF5; vertical-align: top"; rowspan= "3" |
 
'''GW flow between HRU aquifers is not modelled'''
 
'''''Special case, partial exception:''' upland HRU aquifer outflow routed to riparian HRU soil''
 
| style="background: #FFFFF5; vertical-align: top"; rowspan= "3"|
 
'''GW flow between subcatchment aquifers is not modelled'''
 
| style="background: #F5FCFF; vertical-align: top"; rowspan= "3" |
 
'''GW flow between aquifer storage units is not modelled'''
 
| style="background: #F5F8FF; vertical-align: top" |
 
''GW flow between grid cells (Darcy's Law)''
* GW level gradient ''(state - compare levels in neighboring cells)''
*'''''Aquifer properties:'''''
** Specific yield
** Saturated conductivity (Ksat)
 
|-
| style="vertical-align: top" |'''Function type'''
| style="background: #FFF5FA; vertical-align: top" |non-linear & threshold
| style="background: #FFF7F5; vertical-align: top" |non-linear & threshold
| style="background: #F5F8FF; vertical-align: top" |non-linear
|-
| style="vertical-align: top" |'''Thresholds'''
| style="background: #FFF5FA; vertical-align: top" |
'''yes:'''
 Aquifer storage threshold for flow
| style="background: #FFF7F5; vertical-align: top" |
'''yes:'''
 Aquifer storage threshold for flow
| style="background: #F5F8FF; vertical-align: top" |
n/a
|}
[[#Process rep - pg top|Back to top of page]]



== Aquifer exchanges with channel: aquifer outflow to channel and channel transmission loss ==
{| class="wikitable"
! scope="col" style="width:10%" | Algorithm description
! scope="col" style="background: #F2CEE0; width:15%" |WRSM-Pitman(Sami GW)
! scope="col" style="background: #F2D4CE; width:15%" |SPATSIM-Pitman(Hughes GW)
! scope="col" style="background: #CEF2CE; width:15%" |ACRU4
! scope="col" style="background: #F2F2CE; width:15%" |SWAT2012
! scope="col" style="background: #CEE6F2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|semi-distributed, more conceptual]]
! scope="col" style="background: #CEDAF2; width:15%" |MIKE-SHE,[[Coverage of structural options within modelling tools#MIKE-SHE|fully-distributed, more physical]]
|-
| style="vertical-align: top" | '''Algorithm inputs''' ''(input data, model calculated states / storages, property parameters)''
| style="background: #FFF5FA; vertical-align: top" |
 
''Dynamic two-way exchange within subcatchment ("runoff module"):
 aquifer-to-channel or channel-to-aquifer, depending on conditions (calculated state)''
''Additional one-way channel-to-aquifer representation within "channel module"''
* River channel level ''(input)''
* Subcatchment runoff / area (estimation of local channel store) ''(state)''
* Aquifer storage/level -> GW slope ''(state)''
* '''''Aquifer properties:'''''
** Max flow rate for exchange
** Exchange flow power coefficient
* '''''Channel (module) properties:'''''
** Transmission loss rate
 
| style="background: #FFF7F5; vertical-align: top" |
 
''Dynamic two-way exchange: aquifer-to-channel or channel-to-aquifer, depending on conditions (calculated state)''
* River channel level ''(input)''
* Aquifer storage/level -> GW slope ''(state)''
* '''''Aquifer properties:'''''
** Specific yield
** Conductivity
* '''''Channel properties:'''''
** Length of channel
** Subcatchment drainage density
 
| style="background: #F5FFF5; vertical-align: top" |
 
''One-way exchange: aquifer-to-channel''
''(Channel transmission loss not modelled)''
* Aquifer storage ''(state)''
* '''''Aquifer properties:'''''
* Outflow proportion
 
| style="background: #FFFFF5; vertical-align: top"|
 
''Limited two-way exchange: aquifer-to-channel or channel-to-'''"bank storage"'''(separate storage to the subcatchment's aquifer). Bank storage can release water to channel later. ''
* Aquifer storage ''(state)''
* Channel flow ''(state)''
*'''''Aquifer properties:'''''
** Storage limit for outflow
** Specific yield
** Outflow recession constant
* '''''Channel properties:'''''
* Shape - wetted perimeter
* Bed conductivity
 
| style="background: #F5FCFF; vertical-align: top" |
 
''One-way exchange per channel reach unit (can have multiple per subcatchment with different exchange directions): each reach can have either aquifer-to-channel OR channel-to-aquifer, not switch between over time ''
* Aquifer storage ''(state)''
*'''''Aquifer properties:'''''
** Storage threshold for outflow
** Specific yield
** Outflow recession constant
* '''''Channel properties:'''''
* Losing vs gaining specification
* Shape - wetted perimeter
* Bed conductivity
 
| style="background: #F5F8FF; vertical-align: top" |
 
''Dynamic two-way exchange: aquifer-to-channel or channel-to-aquifer, depending on conditions (calculated state) for each riparian grid cell and channel node pair''
* Water table height ''(state)''
* Channel water level ''(state)''
*'''''Aquifer properties:'''''
** Specific yield
** Conductivity (Ksat)
* '''''Channel properties:'''''
* Shape - wetted perimeter
* Bed conductivity
 
|-
| style="vertical-align: top" |'''Function type'''
| style="background: #FFF5FA; vertical-align: top" |non-linear & threshold
| style="background: #FFF7F5; vertical-align: top" |non-linear & threshold
| style="background: #F5FFF5; vertical-align: top" |rate
| style="background: #FFFFF5; vertical-align: top" |non-linear & threshold
| style="background: #F5FCFF; vertical-align: top" |linear reservoir & threshold
| style="background: #F5F8FF; vertical-align: top" |non-linear & threshold
|-
| style="vertical-align: top" |'''Thresholds'''
| style="background: #FFF5FA; vertical-align: top" |
'''yes - to switch flow direction:'''
 Aquifer water level vs River water level
| style="background: #FFF7F5; vertical-align: top" |
'''yes - to switch flow direction:'''
 Aquifer water level vs River water level
| style="background: #F5FFF5; vertical-align: top" |
no
| style="background: #FFFFF5; vertical-align: top"|
'''yes - to switch flow direction:'''
 Aquifer storage threshold for outflow
| style="background: #F5FCFF; vertical-align: top" |
'''yes - for aquifer-to-channel:'''
 Aquifer storage threshold for outflow
| style="background: #F5F8FF; vertical-align: top" |
'''yes - to switch flow direction:'''
 Aquifer water level vs River water level
|}
[[#Process rep - pg top|Back to top of page]]