Skip to content

subset_data --create-datm errors with GSWP3 data #3269

Description

@samsrabin

Or at least it will, after the changes in #3259 come in. This is due to two changes needed to make it work for CRU-JRA:

Per discussion with @ekluzek, I won't bother fixing this as part of that PR, because we're not planning to support GSWP3 moving forward. I will make sure a useful error is thrown if GSWP3 is used, and if a user ever finds that to be a problem, we can discuss whether to fix it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: lowBackground task that doesn't need to be done right away.

    Fields

    No fields configured for Feature.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions