MetOffice / MetOffice/ukca

Predict timesteps for ASAD in advance

Open
#20 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Fortran
Stars
11
Forks
38
Avg merge
17h 57m
Merged PRs (30d)
1

Description

Transfer of [ukca:#144](https://code.metoffice.gov.uk/trac/ukca/ticket/144) from MOSRS.

The ASAD chemistry solver currently includes redundant calculation. For each chunk of data passed to the solver, if any of the corresponding grid-boxes fail to solve then the entire chunk is solved again at half the timestep until convergence is achieved. If we were able to predict the required timestep in advance then we could avoid this redundant calculation.

Predicting the timestep in advance is not trivial, however. This is ongoing research work on whether we are able to map data available to the solver at its initialisation to the eventual number halving steps and/or required timestep. The process may or may not include machine learning.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by examining the ASAD chemistry solver and the data available during solver initialization, then trace how failed grid-boxes trigger chunk retries and timestep halving. Review the transferred MOSRS ticket for context. Done would require evidence that the required timestep or number of halving steps can be predicted reliably, but the issue does not define a specific implementation or acceptance test.

Written by the indexing model from the issue text.

Assessment

Tech stack
fortran
Domain
performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.