MetOffice / MetOffice/ProFSea-tool
Outputs usability review
- Dominant language
- Python
- Stars
- 6
- Forks
- 11
- Avg merge
- 13h 34m
- Merged PRs (30d)
- 2
Description
- Plots are good for visualising outputs, but compared to older ProFSea versions are less immediately useful as the plotting functions are not in the tool by default and would need copying in from an example. This offers additional flexibility in how the outputs are used, but also additional effort is required by the user to post-process them.
- The output file format of .zarr looks useful for storing and organising large datasets efficiently but a documentation page on how to make use of the file would be useful to further explain the possibilities, or how to convert it to other formats such as csv.
- As CMIP 5 thermosteric data has not yet been implemented to the v3 tool yet, we cannot compare between our previous Arctic project case study use of ProFSea. Having an input of ocean heat content forcings would allow consistency of the tool with older projects across Applied Science.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the plotting examples and the documentation around .zarr outputs, then trace how input forcings are handled. Clarify whether the requested work is plotting usability, zarr conversion guidance, CMIP5 thermosteric support, or ocean heat content inputs. Done criteria are not defined because the issue combines several separate requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100