Skip to content

Custom valid hours for fetchnwp #817

@williamhobbs

Description

@williamhobbs

There are a few reasons that a user might want to modify the valid hours fetched for a given NWP with fetchnwp.

  1. If they are only interested in a subset of valid hours (e.g., hour ahead 4 through 12 with the HRRR), they can reduce file sizes and total disk space by limiting to those valid hours.
  2. If they want the most recent forecast possible for horizons shorter than max lead time of an NWP, it could be advantageous to end the fetch process as soon as the last valid hour needed is available, rather than wait for remining valid hour grib2 files to be posted to NOMADS.

I think an optional argument passed to fetchnwp could be a nice way to handle this.

This is semi-related to #686. I think the current solution for both is modifying solarforecastarbiter/io/fetch/nwp.py, and possibly creating a second virtual environment with those modifications if an unmodified fetch is also needed (e.g., if you want a "fast" short term HRRR and a regular full length HRRR).

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