Custom Query (986 matches)

Investigation of the step_floats.F code lead me to write some time ago:

! T Float trajectory type ! (0: neutral 3D Lagrangian, 1:isobaric, 2: isopycnal)

I'm actually not sure that's what's going on though. In any case, the documentation in the floats.in file for float type needs to be revisited.

We added the balance operator (BALANCE_OPERATOR option) to the 4DVAR algorithms. This formulation follows the methodology described by Weaver et al. (2006). It basically computes the off diagonal correlation/covariances terms used during variational data assimilation. The balance operator computes the multivariate covariances based on several balance relationships.

The balance operator is used to computed the unobserved variables information from the directly observed data. The ocean state vector is split between balanced and unbalanced components, except for temperature which is treated in totality and used as the starting point to establish the balanced part of the other variables. The multivariate formulation is obtained by establishing linear balance relationships between temperature and the other state increments using T-S empirical formulas, the linear equation of state, hydrostatic balance, and geostrophic balance.

Many thanks to Andy Moore and Javier Zavala for their help implementing this operator. This code is still in the early stages and it is likely to change in the future. It now released so the Beta-testers can start hacking it.

There is a typo in the computation of the Kelvin wave test (KELVIN) western and eastern boundary condition in subroutine ana_m2obc. Recall that Kelvin waves are gravity waves moving at the speed of SQRT(g*h). See the following forum ​post for details. Many thanks to Rachael Mueller for reporting this typo.