Skip to content

Clarify output#181

Draft
r-sharp wants to merge 9 commits intoMetOffice:mainfrom
r-sharp:clarify_output
Draft

Clarify output#181
r-sharp wants to merge 9 commits intoMetOffice:mainfrom
r-sharp:clarify_output

Conversation

@r-sharp
Copy link
Contributor

@r-sharp r-sharp commented Feb 6, 2026

PR Summary

Sci/Tech Reviewer:
Code Reviewer:

Basic steps to tidy up the output generated. Particularly by maving a "print verbosity" level more universally available throughout the code.

Code Quality Checklist

  • I have performed a self-review of my own code
  • My code follows the project's style guidelines
  • Comments have been included that aid understanding and enhance the readability of the code
  • My changes generate no new warnings
  • All automated checks in the CI pipeline have completed successfully

Testing

  • This change has been tested appropriately (please describe)

Been running it repeatedly on a modified version of Marc Stringer's UM branch to ensure the output looks reasonable at the 5 levels.

Security Considerations

  • I have reviewed my changes for potential security issues
  • Sensitive data is properly handled (if applicable)
  • Authentication and authorisation are properly implemented (if applicable)

AI Assistance and Attribution

  • Some of the content of this change has been produced with the assistance of Generative AI tool name (e.g., Met Office Github Copilot Enterprise, Github Copilot Personal, ChatGPT GPT-4, etc) and I have followed the Simulation Systems AI policy (including attribution labels)

Still using GitHub CoPilot for code completion suggestions. Each suggestion is checked to ensure it does what I was intending and at least half of them were binned.

Sci/Tech Review

  • I understand this area of code and the changes being added
  • The proposed changes correspond to the pull request description
  • Documentation is sufficient (do documentation papers need updating)
  • Sufficient testing has been completed

(Please alert the code reviewer via a tag when you have approved the SR)

Code Review

  • All dependencies have been resolved
  • Related Issues have been properly linked and addressed
  • Code quality standards have been met
  • Tests are adequate and have passed
  • Security considerations have been addressed
  • Performance impact is acceptable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants