Iva Kavcic

Note that we also have `r_tran_field_type` to support the mixed precision transport, see issue #1632.

Well, we need this as Tom got this error when he tried updated the CMA test algorithm to work with `r_solver` kind: ``` Generation Error: This scalar is a reduction...

The associated LFRic infrastructure support ticket is https://code.metoffice.gov.uk/trac/lfric/ticket/3401.

Please note that we will need `GH_READWRITE`, too. See e.g. LFRic tickets [3020](https://code.metoffice.gov.uk/trac/lfric/ticket/3020) and [3032](https://code.metoffice.gov.uk/trac/lfric/ticket/3032). **Update** `GH_READWRITE` is not safe with continuous FS, so we decided to allow only `GH_WRITE`.

Hi all! I am reviewing the PR #1608 so I wanted to check what would be the correct behaviour when changing access for continuous writers from `GH_INC` to `GH_WRITE`. 1)...

PR #1608 that allows ``GH_WRITE`` access for fields on continuous function spaces is now on master. However, this was only part of the requirements for this issue so I will...

One other thing that I noticed is that `make clean` in `examples` does not remove two files in `gocean/eg1` directory: ``` gocean/eg1/ompt_alg.f90 gocean/eg1/ompt_psy.f90

We talked about this and came to conclusion that it would be allowed for kernels that operate on the entire domain. However, it is not yet clear whether this is...

I started looking into this and I would appreciate some input from @rupertford, @sergisiso and @arporter. The problem is outlined below. Precision is currently set, checked and handled within the...

Precision is optional for scalars and arrays, whereas shape is mandatory for arrays so I would suggest creating class hierarchy on the basis of what is mandatory for a class....