Using my own atmospheric forcing files in running single point CLM_FATES

[hannah0304]

Hello,

In running single point CLM_FATES, I am using my own atmospheric forcing files. I have made these files using the observational datasets from FLUXNET from year 2015 to 2016. Since datasets were available up to October 30th, 2016, I have made nc. forcing files from 2015-01.nc to 2016-10.nc.


Using these files, I would like to run the model for 1500 years with ./xmlchange options 'STOP_OPTION=nyears', 'STOP_N=1500'
If I put these forcing files into the model so that they are cycled through the running period, (using taxmode='cycle', 'cycle', cycle' in 'user_nl_datm') I think there will be a problem since my files are in short of 2 months to make a whole cycle.

I thought about using ./xmlchange options 'STOP_OPTION=nmonths' but still not sure how I can make up for 2 months that are not available.

What would be the best option for me to use in this case?

Thank you.

 

[oleson]

Unfortunately you are right that you can't cycle over incomplete years. The only options that I can think of are to spinup over just 2015, or perhaps substitute 2015-11 and 2015-12 for 2016-11 and 2016-12 but that might introduce some undesirable behaviour into your spinup.

 

[hannah0304]

Thank you for your reply.
Right... I guess I will have to spinup with just 2015..!