Skip to content

Error in logging when restart from previous simulation without logging in API37 #1410

@XiulinGao

Description

@XiulinGao

Describe the issue

I found that in API37, when turn on logging in a hybrid run using restart file from previous simulation that did not activate logging, the model will report error that landunit dimension variable is expected to be 3 in the restart file. I then compared the restart files from simulations with (initialized with inventory file) vs without logging using API37, indeed found that the landunit variable is different (3 vs. 1 for the restart file with and without logging, respectively). My understanding is that when logging is not turned on in API37, restart file is written assuming landunit is 1 while when logging is turned on it changed to 3.

Not sure if this is already solved in recent versions of FATES or not, I also suspect this is probably a CTSM-site issue.

Relevant log output

FATES tag

sci.1.80.11_api.37.0.0

Host land model tag

ctsm.5.3.012

Machine

derecho

Other supported machine name

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    case: restartPertaining to CIME case modesscience: loggingPertaining to logging disturbance

    Type

    Projects

    Status

    ❕Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions