ESCOMP / ESCOMP/CTSM

very large values in bias correction file

Open
#1,386 3 comments 0 reactions 1 assignee Claimed by @swensosc View on GitHub
investigation
Dominant language
Fortran
Stars
352
Forks
361
Avg merge
6d 6h
Merged PRs (30d)
8

Description

### Brief summary of bug
Very large values in bias correction file.

### General bug information
In testing the nuopc cmeps/cdeps bias correction compset - I am seeing the following large values in the bias correction file
/glade/p/cesmdata/cseg/inputdata/atm/datm7/clm_output/cruncep_precip_1deg/gpcp_1deg_bias_correction/bias_correction.Prec.2000.nc. Is this to be expected.

```
$ ncdump -ff -v BC_PREC /glade/p/cesmdata/cseg/inputdata/atm/datm7/clm_output/cruncep_precip_1deg/gpcp_1deg_bias_correction/bias_correction.Prec.2000.nc | grep -v 0, | grep e\+
    1.347598e+14,   // BC_PREC(204,124,3)
    5.916577e+14,   // BC_PREC(204,125,3)
    2.547022e+13,   // BC_PREC(96,64,5)
    7.637063e+13,   // BC_PREC(96,65,5)
    4.458091e+13,   // BC_PREC(96,62,6)
    5.322113e+13,   // BC_PREC(96,63,6)
    4.535007e+15,   // BC_PREC(24,81,6)
    1.51875e+15,   // BC_PREC(24,82,6)
    1.523223e+15,   // BC_PREC(24,83,6)
    3.946236e+13,   // BC_PREC(96,71,7)
    7.028679e+13,   // BC_PREC(96,72,7)
    7.000657e+14,   // BC_PREC(24,77,7)
    3.654295e+14,   // BC_PREC(24,78,7)
    2.51628e+15,   // BC_PREC(24,73,8)
    4.9347e+14,   // BC_PREC(24,74,8)
    3.130425e+16,   // BC_PREC(24,75,8)
    2.447011e+13,   // BC_PREC(204,142,8)
    1.176623e+14,   // BC_PREC(198,143,8)
    1.969341e+13,   // BC_PREC(204,143,8)
    4.993199e+13,   // BC_PREC(198,144,8)
    6.292274e+13,   // BC_PREC(198,145,8)
    6.604107e+13,   // BC_PREC(198,146,8)
    2.288727e+13,   // BC_PREC(96,66,9)
    2.742293e+13,   // BC_PREC(96,67,9)
    1.215204e+14,   // BC_PREC(96,68,9)
    8.807233e+13,   // BC_PREC(96,64,10)
    3.590253e+16,   // BC_PREC(24,105,11)
    1.530637e+15,   // BC_PREC(24,107,11)
    1.650805e+14,   // BC_PREC(204,122,12)
    1.623885e+14,   // BC_PREC(204,125,12)
    2.443766e+15,   // BC_PREC(204,126,12)
```

**CTSM version you are using:** ctsm5.1.dev038

**Does this bug cause significantly incorrect results in the model's science?**
Yes - if this is a problem with the data and this would only appear in a configuration with datm using the bias correction data.

**Configurations affected:
SMS_Ld1_P48x1_Vnuopc.f19_f19_mg17.I2000Clm50BgcCru.cheyenne_intel.clm-af_bias_v7
SMS_Ld1_P48x1_Vmct.f19_f19_mg17.I2000Clm50BgcCru.cheyenne_intel.clm-af_bias_v7.validate/

### Details of bug

In addition to the appearance of these large values - the nuopc configuration the datm appears to be doing the interpolation for stream->model correctly whereas this is not the case in mct. I have overwritten the values of rainc in the coupler history file so that it only

The following file is the actual bias correction plot:

![Screen Shot 2021-05-31 at 4 34 14 PM](https://user-images.githubusercontent.com/7958803/120246772-7c063d80-c22e-11eb-837e-5d713f8ab23e.png)

This file is the mct version of interpolation from f09->f19 (I think the problem is the fill that is occurring with mct - I don't think its doing it correctly)

![Screen Shot 2021-05-31 at 4 26 36 PM](https://user-images.githubusercontent.com/7958803/120246318-1cf3f900-c22d-11eb-8661-219ab36bc1a9.png)

This file is the cdeps version of interpolation from f09->f19 (there is still a problem on the coastlines of the fill values from f09 being mapped to the coastlines of f19 - but the rest of the plot looks reasonable)

![Screen Shot 2021-05-31 at 4 36 16 PM](https://user-images.githubusercontent.com/7958803/120246799-904a3a80-c22e-11eb-9207-b4bc9a5bde04.png)

### Important details of your setup / configuration so we can reproduce the bug
The following two compsets were run:
SMS_Ld1_P48x1_Vnuopc.f19_f19_mg17.I2000Clm50BgcCru.cheyenne_intel.clm-af_bias_v7
SMS_Ld1_P48x1_Vmct.f19_f19_mg17.I2000Clm50BgcCru.cheyenne_intel.clm-af_bias_v7.validate/

In both cases user_nl_datm was modified to include the following:
```
bias_correct = 'BC.CRUNCEP.GPCP.Precip' added to user_nl_datm
./xmlchange RUN_STARTDATE=2000-01-16
```

### Important output or errors that show the problem
Please see the plots above.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.