Date reset on 1st of January ?

[MaxCol22]

Hi all. I am forcing the WRF model by overwriting directly TSK with a new module that I created. The forcing on TSK depends on time, it is a smooth function of time. The forcing works perfectly well if it has a periodicity of 1 year. It also works perfectly well if I choose a period of 0.5 years. But when I want to force with a slower variation (for example a period of 2 years), the forcing is not what I intend it to be. It has a small kink on the 1st of January, and it jumps a little over half a period of the forcing.

My forcing is mostly changing this:
lat_SST_max_now = lat_SST_max * COS( 2*pi*(time_now - time_ref)/ (2.*one_year_period) )

The time variable I am using is
time_now = real_time( domain_get_current_time ( grid ) )

I checked and indeed this time variable I am using is reset to zero on the 1st of January at 00:00.

This all explains why there is a problem in the forcing when I multiply by the factor 2. in front of one_year_period. I'm working on another solution to force the model as I wish. Thank you.

 

[kwerner]

Apologies for the long delay in response. Due to the holidays, illness, and preparing for our WRF tutorial, we've gotten a bit behind on forum inquiries. Thank you so much for your patience. Since a few weeks have passed since you first posted this, I first want to ask if you're still experiencing this issue, or if you were able to find a solution?