Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Variables missing from FatesColdAllVars testmod #2833

Open
samsrabin opened this issue Oct 16, 2024 · 2 comments
Open

Variables missing from FatesColdAllVars testmod #2833

samsrabin opened this issue Oct 16, 2024 · 2 comments
Labels
bug something is working incorrectly FATES A change needed for FATES that doesn't require a FATES API update. non-bfb Changes answers (incl. adding tests) test: fates Pass fates test suite before merging testing additions or changes to tests

Comments

@samsrabin
Copy link
Collaborator

samsrabin commented Oct 16, 2024

Brief summary of bug

The FatesColdAllVars testmod is supposed to save every single FATES variable. However, there are 285 missing as of ctsm5.3.009.

General bug information

CTSM version you are using: ctsm5.3.009

Does this bug cause significantly incorrect results in the model's science? No

Configurations affected: Any test with the FatesColdAllVars testmod.

Details of bug

Might be resolved by #2061.

Important output or errors that show the problem

Can be tested from the top of a CTSM checkout like so (bash):

fates_hist_int_mod=src/fates/main/FatesHistoryInterfaceMod.F90
fatescoldallvars_nl=cime_config/testdefs/testmods_dirs/clm/FatesColdAllVars/user_nl_clm
for v in $(grep -oE "vname\s*=\s*[\"']\w+[\"']" $fates_hist_int_mod | sed -E "s/vname\s*=\s*//g" | sed "s/'//g"); do
    nfound=$(grep "'$v'" $fatescoldallvars_nl | wc -l)
    if [[ $nfound -gt 1 ]]; then
        echo "$v: multiple matches"
    elif [[ $nfound -eq 0 ]]; then
        echo $v
    fi
done | sort
@samsrabin samsrabin added bug something is working incorrectly FATES A change needed for FATES that doesn't require a FATES API update. testing additions or changes to tests non-bfb Changes answers (incl. adding tests) test: fates Pass fates test suite before merging next this should get some attention in the next week or two. Normally each Thursday SE meeting. labels Oct 16, 2024
@wwieder wwieder removed the next this should get some attention in the next week or two. Normally each Thursday SE meeting. label Oct 17, 2024
@wwieder
Copy link
Contributor

wwieder commented Oct 17, 2024

One more reason for getting #2061 in. Maybe we can get that onto main sooner

@samsrabin
Copy link
Collaborator Author

#2061 would resolve the need to keep the history variable list in FatesColdAllVars up-to-date. However, we'd probably want to add additional tests to the aux_clm suite (or maybe just the fates suite) that exercise additional FATES modes in order to output all the possible variables.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something is working incorrectly FATES A change needed for FATES that doesn't require a FATES API update. non-bfb Changes answers (incl. adding tests) test: fates Pass fates test suite before merging testing additions or changes to tests
Projects
None yet
Development

No branches or pull requests

2 participants