Some CLM45 configurations use CLM50 initial conditions files

[billsacks]

Brief summary of bug

I noticed that some of our CLM45 tests use CLM50 initial conditions files. I'm not sure if this is actually a bug, but I wanted to bring it to @ekluzek 's attention.

General bug information

CTSM version you are using: ctsm1.0.dev045

(Actually I'm using a branch off of that, but I haven't changed anything that should change this behavior.)

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

Configurations affected:

This shows up in the following tests:

ERP_P36x2_D_Ld5.f10_f10_musgs.I2000Clm45Sp.cheyenne_intel.clm-default
ERP_P36x2_D_Ld5.f10_f10_musgs.IHistClm45BgcCruGs.cheyenne_intel.clm-decStart
ERS_Ld5_Mmpi-serial.1x1_vancouverCAN.I1PtClm45SpGs.cheyenne_intel.clm-default
SMS_D_Ld1_Mmpi-serial.1x1_vancouverCAN.I1PtClm45SpGs.hobart_nag.clm-default
SMS_D_Ld1_P48x1.f10_f10_musgs.I2000Clm45BgcCrop.hobart_nag.clm-oldhyd

Details of bug

@ekluzek is this a bug or intended behavior?

[ekluzek]

For present day we only have one clm5_0 finidat to match from right now. The above cases are all present day other than the IHist, but it does a decStart so starts in 2000. So they are all looking for present day finidat files. The release branch has a bunch that will be coming to master, so will be fixed then.