Closed AdamJDuncan closed 8 years ago
My guess is that when it resampled the years from climatology, it didn't have enough years to sample from for a larger ensemble size (hard to tell without testing it out with your particular setup). The a7a621073ac156f3d3a765616bf59139bb17b003 commit added code to repeat the list of available years if the ensemble size is larger. Can you try it and see if that fixes it? Thanks.
OK I've tried 20 ensembles on a small tributary and it works. Thanks; closing.
I've got CHIRPS & NCEP downloaded from 1981-1-1 for the LMB (Edit:LMR). Running forecasts on a single pixel before moving on. I've run nowcasts all the way through to ensure there is no missing data.
Here's my setup:
Where FN_PP is a single pixel in Cambodia.
I know that there's nothing in the _writeForcing section of ensemble.py stating a maximum ensemble sizes, but I'm running into maximums. For example for 1995, an ensemble size of 5 will work, but 10 will return this:
When I run the same but 1985-1-1 to 1985-3-1 (with a new schema name), an ensemble size of 10 WILL work! But when I run the exact same thing again, with a new schema name, I get the assertion error. Restarting/vacuuming the db fixes this.
So the max ensemble size appears to decrease the more data we're using... by 2010, the maximum is 3.
Commenting out the 'assert' in vic.py and running the above ini file gives this:
EDIT: When I run it on a 4x4 area the maximums remain the same, so it is forcing files per pixel, not total.