Idealized forcings require hourly timestep

[aubreyd]

The idealized forcing option is coded up in a way that it only works properly with hourly forcing cycling. It will not error out if you choose a different forcing timestep, but will produce odd results.

Expected Behavior

Error if forcing_timestep is not 3600 sec and forc_typ = 4
OR
Use input forcing_timestep to adapt idealized forcings to match (better!).

Current Behavior

Model runs happily along with increments of 24 (so, for example, you will see 4 diurnal cycles per day if you are running with 15-min forcing timestep).

Possible Solution

Bring in forcing timestep value from HRLDAS namelist and use this to figure out the number of daily timesteps needed (currently hard-coded to 24).

Steps to Reproduce (for bugs)

Change FORCING_TIMESTEP to <> 3600 and active FORC_TYP = 4.

Your Environment

Mars!

(bug discovered by @then6702... thanks, Tom!)