Guidance on Running with LME datasets with CESM2.1.3 (CLM5)

[slevis]

The path of the file
inputdata/atm/cam/solar/SolarForcing1995-2005avg_c160929.nc
and the values that you quoted
1361.1
suggest to me that this file contains the top-of-atmosphere solar radiation used by an active atmosphere model (CAM). If you do not use an active atmosphere model, then I suspect that this file and its values are ignored.

I do not have answers about volcanic forcing. I hope somebody else will answer.

 

[wvsi3w]

The path of the file
inputdata/atm/cam/solar/SolarForcing1995-2005avg_c160929.nc
and the values that you quoted
1361.1
suggest to me that this file contains the top-of-atmosphere solar radiation used by an active atmosphere model (CAM). If you do not use an active atmosphere model, then I suspect that this file and its values are ignored.

I do not have answers about volcanic forcing. I hope somebody else will answer.

Dear Sam, Thank you so much for your answer.

I understand. So in a fully coupled simulation or a CLM-CAM simulation, I could use my tsi instead of the default one (?)

 

[slevis]

I understand. So in a fully coupled simulation or a CLM-CAM simulation, I could use my tsi instead of the default one (?)

I have never tried this myself, but I do not see why not.

 

[wvsi3w]

I have never tried this myself, but I do not see why not.

And do you know if we can assign its path to a different directory in our case, like we do for other forcings?
I looked at the CaseDocs and user_namelists, but I dont see where we can do that.

Because if I need to just remove that file from inputdata/atm/cam/solar/ and replace it with my file then I should wait until first member is finished then replace it with another member solar file which is not rational.

 

[wvsi3w]

And do you know if we can assign its path to a different directory in our case, like we do for other forcings?
I looked at the CaseDocs and user_namelists, but I dont see where we can do that.

Because if I need to just remove that file from inputdata/atm/cam/solar/ and replace it with my file then I should wait until first member is finished then replace it with another member solar file which is not rational.

And another question would be why we have this path inputdata/atm/cam/solar/ in IHIST compsets, but we dont have it in I1850 compsets? The first one is historical, the second one is used when we want constant values of urban, landuse, etc.

I personally cant see the reason why we dont have that path in I1850 compset inputdata. In I1850, we only see cam/chem path and nothing else.

 

[slevis]

And do you know if we can assign its path to a different directory in our case, like we do for other forcings?
I looked at the CaseDocs and user_namelists, but I dont see where we can do that.

Because if I need to just remove that file from inputdata/atm/cam/solar/ and replace it with my file then I should wait until first member is finished then replace it with another member solar file which is not rational.

I have not tried this myself but here are my thoughts:

I suspect that the solar file of your choice could end up in atm_in via user_nl_cam or maybe it would be specified in a "streams" file. Overwriting the default file with your file seems the easiest immediate solution, though it could confuse you in the future, because you could forget which data you actually used for your various simulations. In any case, you could keep trying these ideas until something works.

You could also post in the CAM Forum where people are more likely to know about this file.

About your last question, I am surprised in the opposite sense than you are:
I would expect no such file in I1850, I2000, IHist or any I-compset because, from my understanding, this is top-of-atmosphere radiation that matters only if you have an active atmosphere model in your compset. If such a file is specified in I-cases, then I would expect no effect from changing it because I would not expect top-of-atmosphere data to be used in an I-case.

Again, you may get more conclusive responses in the CAM forum about this file.