Skip to content

No warning about running for a given meta file when cloud properties are not present for the full domain #84

@bnb32

Description

@bnb32

Problem examples:

2018 standard runs - uses goes east for cloud properties which doesn't cover all of washington. This results in clear sky output over the area with missing coverage.

Ran 2017 polar with test data that didn't cover full polar region but with a meta that did. This produced clear sky output for the missing region.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions