Skip to content

Incorrect longitude bounds check in read_amsua_amsub_mhs and read_satwnd #87

@amstokely

Description

@amstokely

There is a bug in the latitude/longitude bounds checking logic in two subroutines:

In both subroutines, the code checks the latitude bounds twice instead of checking both latitude and longitude. The issue arises from referencing lalodat(1), which represents latitude, in both conditions, effectively skipping the longitude check.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions