Skip to content

Sporadic NaNs in C13_GPP and C13_NBP in https://github.com/NCAR/LMWG_dev/issues/100 #3350

@olyson

Description

@olyson

Brief summary of bug

The land diagnostics package reports a couple of NaNs in C13_GPP and C13_NBP in the pSASU simulation for NCAR/LMWG_dev#100

General bug information

CTSM version you are using: See NCAR/LMWG_dev#100

Does this bug cause significantly incorrect results in the model's science? Maybe not significant?

Configurations affected: pSASU

Details of bug

I didn't really want to file this right before I leave on vacation for a week, but

The land diagnostics package screens for NaNs in the history fields and stops the package if any NaN is found (if BLOCK_NAN is set to 1). It searches the ANN_ALL file. For this 160 year simulation it reports:

(0) screening case 2 : C13_GPP
(0) found 2 NaNs
(0) Sample NaN Coords: time = 126 latDim = 155 lonDim 193
(0) Sample NaN Coords: time = 146 latDim = 155 lonDim 193
(0) screening case 2 : C13_HR
(0) screening case 2 : C13_NBP
(0) found 2 NaNs
(0) Sample NaN Coords: time = 126 latDim = 155 lonDim 193
(0) Sample NaN Coords: time = 146 latDim = 155 lonDim 193

So this means that there is, e.g., a NaN in C13_GPP at year 127, at j=155, i=193, and again at year 147, in this pSASU simulation. So there is at least one month in the annual mean for those two years that have a NaN at that gridcell.
I've spot checked the ANN_ALL files from a couple of our recent land-only historical simulations and don't see any NaNs. Also, I haven't run across any NaNs for these fields in any of our recent fully-coupled simulations.
Pretty sparse and transient problem.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugsomething is working incorrectlyclosed: wontfixWe won't fix this issue, because it would be too difficult and/or isn't important enough to fix

    Type

    Projects

    Status

    Done

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions