-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom valid hours for fetchnwp #817
Comments
Merits of an optional argument aside, the parameters are defined in the module dictionary, so, if I understand correctly, you could simply modify the dictionary in place at run time. For example: import solarforecastarbiter.io.fetch.nwp
solarforecastarbiter.io.fetch.nwp.HRRR_HOURLY['valid_hr_gen'] = [1, 2, 3, 4, 5, 6] |
@wholmgren Thanks. I've only run the fetch process from the command line interface, e.g., running something like How would you recommend fetching with the modified dictionary? Would it be run inside of a Python script? |
Good question. Not sure if I'd go so far as to say the following ideas are good ideas, but they are ideas... You could modify Alternatively, you could copy that function and make a dedicated script that you have more control over. |
There are a few reasons that a user might want to modify the valid hours fetched for a given NWP with
fetchnwp
.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).
The text was updated successfully, but these errors were encountered: