…r_eps_devel

modified:   dyn_em/module_first_rk_step_part2.F

modified:   Makefile
modified:   clean

… terms

The moving nest option assumes that the index order of 3d
arrays is XZY (in i,k,j in WRF-speak). The new 3d forcing terms were
indexed XYZ (i,j,k in WRF-speak). That breaks some autogenerated
files, specifically those used in moving nests.

Now it is understood that few moving nests are going to use the
stochastic forcings, but unfortunately this is a build error. This
is not anything that we can put a simple IF test around.

This required modifying the Registry (registry.stoch and registry.dimspec),
and the stochastic calling structure: both first_rk_step_part2 and the main
stoch module. The re-indexed variables (spforcc3d, spforcs3d, sp_amd3d)
are now required to be ims:ime,num_pert_3d,jms:jme, but that no longer
matches with the subroutine calls. A new subroutine to make the data into
2d contiguous arays was written. Before the stoch calls, the 3d arrays
are transferred into the local 2d arrays. After the stoch calls, the
2d local data is sent back into the 3d arrays.

modified:   Registry/registry.dimspec
modified:   Registry/registry.stoch
modified:   dyn_em/module_first_rk_step_part2.F
modified:   dyn_em/module_stoch.F