Skip to content

Some FATES test lists are long because of lists of history variables -- maybe manage a different way? #3811

@ekluzek

Description

@ekluzek

Some of the FATEST test mod user_nl_clm files are long because it manages long lists of history variables. Maybe this could be managed differently? Have a certain history variables output by default when certain fates control settings are turned on? Or have namelist control variables to turn on sets of variables that's turned on by default when those flags are set?

See this discussion here:

https://github.com/ESCOMP/CTSM/pull/3757/files#r2913748200

Metadata

Metadata

Assignees

No one assigned

    Labels

    FATESA change needed for FATES that doesn't require a FATES API update.bfbbit-for-bitcode healthimproving internal code structure to make easier to maintain (sustainability)enhancementnew capability or improved behavior of existing capabilitynextthis should get some attention in the next week or two. Normally each Thursday SE meeting.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions