Need to add as many remaining AutoAssess areas as possible

[Paul Earnshaw (pdearnshaw)]

Closes #555

PR creation checklist for the developer

• The <issue_number> above ☝️ has been replaced with the issue number.
• main has been selected as the base branch.
• The feature branch name follows the format <issue_number>_<short_description_of_feature>.
• The text of the PR title exactly matches with the text (not including the issue number) of the issue title.
• Appropriate reviewers have been added to the PR (once it is ready for review).
• The PR has been assigned to the developer(s).
• The same labels as on the issue (except for the good first issue label) have been added to the PR.
• The Climate Model Evaluation Workflow (CMEW) project has been added to the PR.
• The appropriate milestone has been added to the PR.

Definition of Done for the developer

• This PR contains only the changes needed to meet all acceptance criteria.
• The change in this PR follows the requirements in the wiki: Developer Guide (including copyrights).
• The GitHub Actions workflow checks pass.
• The tests run locally and pass (Note: the tests are not run by the GitHub Actions workflow, see wiki: Run the tests locally).
• Updating the Rose metadata (select one of the following):
  • Rose metadata related to the change has been added or updated.
  • The change does not require Rose metadata to be added or updated.
• Rendering the Rose metadata (select one of the following):
  • The Rose GUI shows the change as expected.
  • The change in this PR does not affect the Rose GUI.
• Updating the tests (select one of the following):
  • Tests related to the change have been added or updated.
  • The change does not require tests to be added or updated.
• Updating the user documentation (i.e. everything in the doc directory, including the Quick Start section; select one of the following):
  • The user documentation related to the change has been updated appropriately.
  • The change in this PR does not require the user documentation to be updated.
• Rendering the user documentation (wiki: Build the documentation locally provides instructions; select one of the following):
  • The HTML pages show the change as expected.
  • The change in this PR does not affect the HTML pages.
• Updating the API documentation (e.g. docstrings in Python modules; select one of the following):
  • The API documentation related to the change has been updated appropriately.
  • The change in this PR does not affect the API documentation.

Copyright and IPR:

	GitHub handles
I confirm that all code is my own and that my contributions are not subject to copyright or license restrictions.	pdearnshaw
I confirm I have not knowingly violated intellectual property rights (IPR) and have taken sensible measures to prevent doing so, including appropriate attribution for usage of Generative AI. I confirm that this work is my own, and I understand that it is my responsibility to ensure I am not violating others’ IPR. This includes taking reasonable steps to ensure that all tools used while creating this contribution did not infringe IPR.	pdearnshaw

PR creation checklist for the reviewer

• The <issue_number> above ☝️ has been replaced with the issue number.
• main has been selected as the base branch.
• The feature branch name follows the format <issue_number>_<short_description_of_feature>.
• The text of the PR title exactly matches with the text (not including the issue number) of the issue title.
• Appropriate reviewers have been added to the PR (once it is ready for review).
• The PR has been assigned to the developer(s).
• The same labels as on the issue (except for the good first issue label) have been added to the PR.
• The Climate Model Evaluation Workflow (CMEW) project has been added to the PR.
• The appropriate milestone has been added to the PR.

Definition of Done for the reviewer

• This PR contains only the changes needed to meet all acceptance criteria.
• The change in this PR follows the requirements in the wiki: Developer Guide (including copyrights).
• All developers of this PR have added their names to the Copyright and IPR statements above.
• The GitHub Actions workflow checks pass.
• The tests run locally and pass (Note: the tests are not run by the GitHub Actions workflow, see wiki: Run the tests locally).
• Updating the Rose metadata (select one of the following):
  • Rose metadata related to the change has been added or updated.
  • The change does not require Rose metadata to be added or updated.
• Rendering the Rose metadata (select one of the following):
  • The Rose GUI shows the change as expected.
  • The change in this PR does not affect the Rose GUI.
• Updating the tests (select one of the following):
  • Tests related to the change have been added or updated.
  • The change does not require tests to be added or updated.
• Updating the user documentation (i.e. everything in the doc directory, including the Quick Start section; select one of the following):
  • The user documentation related to the change has been updated appropriately.
  • The change in this PR does not require the user documentation to be updated.
• Rendering the user documentation (wiki: Build the documentation locally provides instructions; select one of the following):
  • The HTML pages show the change as expected.
  • The change in this PR does not affect the HTML pages.
• Updating the API documentation (e.g. docstrings in Python modules; select one of the following):
  • The API documentation related to the change has been updated appropriately.
  • The change in this PR does not affect the API documentation.

Important

• Remember to re-check the Definition of Done after making changes in response to a review.
• The developer merges the PR.
• Remember to use the format #<pull_request_number>: <pull_request_title> when writing the merge commit message for the pull request, so the pull request number is immediately visible on GitHub, regardless of the length of the pull request title.

[Paul Earnshaw (pdearnshaw)]

As extra information to this PR, particularly around increasing the number of years from 2 to 5, the following are the approximate run times of each assessment:

Area	Runtime
aerosols	5.5 mins
africa	2.5 mins
australia	2 mins
enso	3.5 mins
globaltrop	4 mins
hydrocycle	0.5 mins
land_surface	0.5 mins
mjo	10 mins
monsoon	0.5 mins
stratosphere	2.5 mins

Retrieval times from MASS are very variable, anything from a few seconds to approximately an hour. This seems to be more MASS related than area.

In the above table, these areas are running in parallel so the total run time is not an accumulation of the times, but what ever the slowest running area is. In this case the MJO area is the slowest. So as long as all the retrievals behave themselves the workflow should not take any longer than 1 hour, but hopefully closer to 30 minutes.