-
Notifications
You must be signed in to change notification settings - Fork 355
Make procedure for throughput testing of FATES runs #2745
Copy link
Copy link
Open
Labels
FATESA change needed for FATES that doesn't require a FATES API update.A change needed for FATES that doesn't require a FATES API update.b4bbit-for-bitbit-for-bitblocked: dependencyWait to work on this until dependency is resolvedWait to work on this until dependency is resolvedblockeranother issue/PR depends on this oneanother issue/PR depends on this onedocs-loc:users-guideRelates to User's Guide (using CTSM/tools)Relates to User's Guide (using CTSM/tools)docs:newNew documentation needed (e.g., for a new feature)New documentation needed (e.g., for a new feature)documentationadditions or edits to user-facing documentation or its infrastructureadditions or edits to user-facing documentation or its infrastructure
Milestone
Metadata
Metadata
Assignees
Labels
FATESA change needed for FATES that doesn't require a FATES API update.A change needed for FATES that doesn't require a FATES API update.b4bbit-for-bitbit-for-bitblocked: dependencyWait to work on this until dependency is resolvedWait to work on this until dependency is resolvedblockeranother issue/PR depends on this oneanother issue/PR depends on this onedocs-loc:users-guideRelates to User's Guide (using CTSM/tools)Relates to User's Guide (using CTSM/tools)docs:newNew documentation needed (e.g., for a new feature)New documentation needed (e.g., for a new feature)documentationadditions or edits to user-facing documentation or its infrastructureadditions or edits to user-facing documentation or its infrastructure
Type
Projects
Status
Todo
It would be good to have some FATES compsets in the CESM3 timing table, but the usual PFS test setup (20 days) isn't representative for runs where the number of patches can change—i.e., setups with
use_fates_spanduse_fates_nocompboth false.