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

MaxPFT handling in CLM3.5 coupled vs sta #212

Open
s-poll opened this issue Sep 8, 2023 · 0 comments
Open

MaxPFT handling in CLM3.5 coupled vs sta #212

s-poll opened this issue Sep 8, 2023 · 0 comments

Comments

@s-poll
Copy link
Member

s-poll commented Sep 8, 2023

Describe the problem

The total number of active PFTs differs between clm3.5 compiled as stand-alone and coupled with COSMO/ParFlow. This is unintended behavior as the total number of active PFTs shell be independent of having CLM coupled or not.

Might be connected with maxpft introdution #161.

Version and Component Models

TSMP-Version: v1.4.0

Build command:

	./build_tsmp.ksh -c clm3-cos5 --maxpft=4 -m JUWELS -O Intel
  • CLM-Version: CLM3.5

Error message

This will by default not lead to errors. In case of using the restart files, one get a dimension mismatch error. e.g. for EUR-11

 CHECK_DIM error: mismatch of input dimension       306548  with expected value
      103152  for variable pft
@s-poll s-poll changed the title MaxPFT handling in CLM coupled vs sta MaxPFT handling in CLM3.5 coupled vs sta Sep 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant