Skip to content

Where can I (should I) add a temp logical in LFRic? #604

Open

Description

There is a desire to treat temporary logicals different in LFRic to the UMs single namelist approach. Once a system is agreed the temporary logical page in the working practices should be updated to reflect the different systems.

Discussed in #603

Originally posted by MichaelWhitall March 18, 2026
Hi all,

I have a minor bug-fix that I want to lodge in lfric_apps, affecting the PC2 cloud-scheme (the final item in the bullet-list on this issue page: MetOffice/lfric_apps#243). I think in the past it would've been said, if it clearly fixes a bug, just change the code without using any switches as noone will mind a KGO-change for that. But as we get ever-closer to having a frozen and highly-tuned LFRic GC6, I'm guessing that's no-longer the case? In the UM I always ended up having to lodge cloud-scheme bug-fixes under "temporary logicals", because they usually cause a small change in cloud radiative forcing (which is something that has to be finely tuned in the climate model and so mustn't be changed in a frozen configuration).

What's the process for lodging this sort of bug-fix in lfric_apps? I've found the old UM science_fixes_mod still exists in lfric_apps, but could be retired as currently um_physics_init just sets the relevant logicals to true; none of them are in a namelist. Should I just add a switch to toggle on/off the bug in the LFRic cloud namelist? Or does lfric_apps have its own equivalent to temp logicals somewhere that I've missed?

Cheers!
Mike

Activity

  1. stevemullerworth commented on Mar 19, 2026

    @stevemullerworth
    Contributor

    Suggestion:

    1. We perhaps name the logicals after a related issue or include the issue number in the metadata.
    2. We add the issue to a github project owned by the configuration owner.
    3. We have a standing agenda item at the lfric_apps governance meeting to review the boards, and assess the amount of technical debt.
    4. Ideally, the governance group are able to require issues are dealt with once the technical debt is too high or a configuration is no longer to be supported.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions