Mismatch between running time and meteo data

[carmelo_cammalleri@jrc_ec_europa_eu]

Hi All
I just experienced a weird issue in running CLM 4.0 on a regional case (using CLM_PT1_NAME).I'm using custom meteo forcing, so I defined a new DATM_MODE based on the QIAN one.What happen is that the model run successfully, but it uses the wrong meteo forcing. For instance, the model starts at 19980101 but it reads the meteo data 2007-01.I guess I forced the model to do that, but I have no idea where I selected this option.Any suggestions on how to fix this problem are welcome. Thanks, Carmelo

 

[carmelo_cammalleri@jrc_ec_europa_eu]

 Hi, I guess I solved the issue. Even if align=1 was working on previous cases to set the starting time equal to the first year, apparently for those runs I have to set align=starting_year in order to get a proper alignment of the data.Thanks, Carmelo 

 

[carmelo_cammalleri@jrc_ec_europa_eu]

 Hi, I guess I solved the issue. Even if align=1 was working on previous cases to set the starting time equal to the first year, apparently for those runs I have to set align=starting_year in order to get a proper alignment of the data.Thanks, Carmelo 

 

[carmelo_cammalleri@jrc_ec_europa_eu]

 Hi, I guess I solved the issue. Even if align=1 was working on previous cases to set the starting time equal to the first year, apparently for those runs I have to set align=starting_year in order to get a proper alignment of the data.Thanks, Carmelo