Skip to content

Divergent initial velocity fields cause tracer and buoyancy non-conservation with zstar #4412

Open
@NoraLoose

Description

@NoraLoose

While working on #4395 and #4403, we tested initializing simulations with random velocity fields using the zstar vertical coordinate. This resulted in tracer and buoyancy non-conservation due to the barotropic velocity field being divergent at the start. The divergence causes non-zero vertical velocities at the surface, which immediately breaks conservation.

Proposed Solutions

  • Short-term: Emit a warning if the user attempts to initialize a zstar simulation with a divergent horizontal velocity field.
  • Long-term: Develop a strategy to correct arbitrary initial velocity fields to ensure they are exactly divergence-free if zstar is used. This would be helpful in all cases where users don't spin up from rest, for example if they:
    • initialize with random velocities
    • initialize with velocities regridded from other simulations (which are unlikely to be perfectly divergence-free)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions