Skip to content

quad_utils cycle vs error #1160

Open
Open

Description

@hkershaw-brown

Do we need to cycle here rather than just print an error? If a failure produces bad corners, both passes may count/fill bad bins or one failure path could behave differently depending on the state (right?)

Originally posted by @mgharamti in #1102

Activity

  1. hkershaw-brown commented on Aug 7, 2026

    @hkershaw-brown
    CollaboratorAuthor

    if (istatus /= 0) print *, 'get_quad_corners for lons returns failure'

    !>@todo is istatus /= 0 a failure condition
    ! Set up array of lons and lats for the corners of these u quads
    call get_quad_corners(h%ii%lons_2d, i, j, cyclic, pole, nx, ny, u_c_lons, istatus)
    if (istatus /= 0) print *, 'get_quad_corners for lons returns failure'
    call get_quad_corners(h%ii%lats_2d, i, j, cyclic, pole, nx, ny, u_c_lats, istatus)
    if (istatus /= 0) print *, 'get_quad_corners for lats returns failure'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions