MetOffice / MetOffice/inline_model_metrics
Modify tracking one step behind model using suite.rc
- Dominant language
- Python
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
To run the tracking when the netCDF files are known to be available there is currently some logic in suite.rc:
```
postproc[+{{EXPT_RESUB}}] => tracking
```
this is bad because log files have been deleted by then and for other reasons.
It would be better to have logic in the Python that looks at the model resubmission period and the stream reinitialisation period that knows what files have become available and need to be tracked.
An approach similar to postproc that creates .arch files (perhaps .track) to know which files have been tracked could be used.
Contributor guide
Research direction
Start by reading the tracking trigger in suite.rc, especially the postproc[+{{EXPT_RESUB}}] => tracking logic. Locate the Python code that knows the model resubmission and stream reinitialisation periods, then determine how .arch-style markers could identify files that need tracking; done means tracking occurs when netCDF files become available without relying on the delayed suite.rc trigger.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100