You state that the feature data during the Forecast will be downloaded the same way as the Hindcast (locally available), I was wondering if the data is not available when you download the data what should we expect to see?
[Edit 2] - Also, do you plan on providing an updated supplementary_nrcs_train_monthly_naturized_flow.csv file that includes the test year data? It’s not currently in the forecast download.
For each issue date, we will run the data download bulk command to download whatever data is available from each data source. Depending on how the particular data source is written out, if some data for some date isn’t available, there will either be missing rows in a CSV file or missing files in a directory.
Re: updated supplementary_nrcs_train_monthly_naturized_flow.csv—we will work on making this available the week after New Year’s.
I received two errors when the automatic 1/1/24 forecast was run and I am hoping you can provide some more insight on them. One was for the monthly naturalized flow and the other was the soi data. In both cases, I assume the files would exist and at least have the past data in the files since these files and the past data are already in your possession, but it seems this is not the case? Can you shed some light on what actually exists on 1/1/24 in the data directory? Do you expect us to load the past data?
On a broader note, it would be very helpful if you could provide us with access to the 1/1/24 - 1/11/24 data directory during this test period so we can better understand what is or is not being provided. I suppose we could make repeated submissions to print this data in our logs, but submissions are limited and this does not seem like a very efficient method.
I just thought I’d chime in and mention that the SOI file (/code_execution/data/teleconnections/soi.txt) appears to have been loaded and parsed without issue by my submission. That piece of my code is unchanged from the hindcast stage. Hope that helps you narrow down where to look, if nothing else.
Thanks for flagging this. It looks like what happened is that there is actually no 2024 data available yet. The download pipeline saved a not-real data file, and wsfr_read.climate.cpc_outlooks did not handle this case (since it never came up in Hindcast). The data download drive and runtime image has been updated with a fix.
It is now expected that you should get these errors if you try to load the files directly:
FileNotFoundError: [Errno 2] No such file or directory: '/code_execution/data/cpc_outlooks/cpcllftd.2024.dat'
FileNotFoundError: [Errno 2] No such file or directory: '/code_execution/data/cpc_outlooks/cpcllfpd.2024.dat'
The wsfr-read package functions has been updated to skip those and log an expected warning that looks something like this:
2024-01-02 11:28:40.527 | WARNING | wsfr_read.climate.cpc_outlooks:read_cpc_outlooks_precip:292 - No CPC outlooks available for calender year 2024. Only data from calender year 2023 loaded.
I just reran your submission after these fixes were implemented, and it still failed (you should have received an email). It looks like you have your own copies of the data reading functions, rather than using the installed wsfr_read that is included in the runtime environment, so the errors that you got are expected.
We’ve made an update to how test_monthly_naturalized_flow.csv is produced so that all 23 sites should show up with rows for every month since October 2023, even if there is no data. This should be reflected as of the 2024-01-08 issue date.
To confirm, for 2024-01-08, we still have no data available for three sites: pueblo_reservoir_inflow, sweetwater_r_nr_alcova, and ruedi_reservoir_inflow. You will see empty values for them for all three of the 2023-10, 2023-11, and 2023-12 rows.