MetOffice / MetOffice/ProFSea-tool
Inputs usability review
- Dominant language
- Python
- Stars
- 6
- Forks
- 11
- Avg merge
- 13h 34m
- Merged PRs (30d)
- 2
Description
- Global and specific location inputs were tested and generated correct plot outputs. Using incorrect model names raised ‘coding’ errors rather than specific errors for unknown model names. As the current tool is code-centred without a config file or GUI, this is expected but to users with less coding experience it may be difficult to diagnose user errors with only compiling error messages. If the expectation is for users to be proficient at coding when using the tool, feel free to dismiss this point.
- Adding multiple locations to the tool requires hard-coding a dictionary and editing output plot formatting lines, which can be a barrier to less code-savvy users. Likewise, if this is the intended use then feel free to dismiss
- No documentation was available for the CMIP5 fingerprint components to know which forcings and associated data were being applied within the modelling run. Links to relevant scientific documentation could be used within the docs to identify these points, but if these inputs are the default being included with ProFSea V3 then some more information is needed on them so that users are aware they can be used.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.