search

MPAS-Dev / MPAS

Repository for private MPAS development prior to the MPAS v6.0 release.
Other
4 stars 0 forks source link

KE from surface wind stress does not match older runs #157

Closed mark-petersen closed 10 years ago

mark-petersen commented 10 years ago

@douglasjacobsen @toddringler

The new ocean core surface wind stress variable is not forcing the model as expected.

I expect the following two runs to be nearly identical. Instead, max KE is 2x higher for the second after 6 hours, 120km global run - see image. m69uv_ke_6hrs

m69u: develop, commit 05ffee Thu Oct 24, uses normalVelocityForcing m69v: release-v2.0, commit 7d9572 Thu Nov 7 13:41uses surfaceWindStress

lo2-fe.lanl.gov> pwd /panfs/scratch3/vol16/mpeterse/runs lo2-fe.lanl.gov> diff m69u/namelist.input m69v/namelist.input 120,123c120,124 < config_restoreTS = .true. < config_restoreT_timescale = 30.0 < config_restoreS_timescale = 30.0

< config_use_coupled_forcing = .false.

    config_forcing_type = "restoring"
    config_restoreT_timescale = 30.0
    config_restoreS_timescale = 30.0
    config_restoreT_lengthscale = 10.01244
    config_restoreS_lengthscale = 10.01244

125a127,129 config_sw_absorption_type = "jerlov" config_jerlov_water_type = 3 config_fixed_jerlov_weights = .true.

uses config_flux_attenuation_coefficient = 0.001

lo2-fe.lanl.gov> ncdump -h m69u/grid.nc | grep -i forcing double normalVelocityForcing(nEdges, nVertLevels) ; lo2-fe.lanl.gov> ncdump -h m69v/grid.nc | grep -i surfaceWindStress double surfaceWindStress(nEdges) ;

These have the same values at the top layer of normalVelocityForcing

mark-petersen commented 10 years ago

@douglasjacobsen When I set config_disable_vel_windstress = .true. I still get large differences in KE. There must be some other difference in the code or initial condition to produce this result.

douglasjacobsen commented 10 years ago

Which initial conditions are you using for the older run?

If the older run is from the website, those are all spun up initial conditions.

mark-petersen commented 10 years ago

The initial conditions are the output from basin, not spun up.

When I turn off wind forcing and surface restoring, I see differences due to old and new basin versions, but not to old and new MPAS code versions. Something is different in today's version of basin other than wind forcing.

I need to leave, but will look further at this soon...

Mark

On 11/07/13 15:59, Doug Jacobsen wrote:

Which initial conditions are you using for the older run?

If the older run is from the website, those are all spun up initial conditions.

— Reply to this email directly or view it on GitHub https://github.com/MPAS-Dev/MPAS/issues/157#issuecomment-28015653.

douglasjacobsen commented 10 years ago

fCell is different. Maybe that's the problem, at least if it's used in MPAS.

mark-petersen commented 10 years ago

I was thinking the same thing. It looks like fCell is not used outside of cvmix.

On 11/07/13 16:09, Doug Jacobsen wrote:

fCell is different. Maybe that's the problem, at least if it's used in MPAS.

— Reply to this email directly or view it on GitHub https://github.com/MPAS-Dev/MPAS/issues/157#issuecomment-28016282.

douglasjacobsen commented 10 years ago

You could try just turning it off in registry to see if it makes a big difference.

mark-petersen commented 10 years ago

I found the problem. fEdge was initialized as zero in basin in commit 585366e34eca090. I was misled by all the changes in forcing variables, so the debug took a while. This is fixed by basin pull request https://github.com/MPAS-Dev/MPAS-Tools/pull/19.