Closed WilliamsTravis closed 2 years ago
@WilliamsTravis This is all excellent information, allowing me to understand your problem (and try to help fix it) quickly and easily.
Without running explicit tests myself (would probably want a charge code for that), I think the problem might be that your single height resource dataset is missing pressure data:
h5ls /datasets/WIND/conus/v1.0.0/2012/wtk_conus_2012_120m.h5
coordinates Dataset {2488136, 2}
meta Dataset {2488136}
temperature_120m Dataset {105408, 2488136}
time_index Dataset {105408}
winddirection_120m Dataset {105408, 2488136}
windspeed_120m Dataset {105408, 2488136}
reV (more correctly, SAM), needs pressure info to run generation. Note that the aggregated data have that included:
h5ls /datasets/WIND/conus/v1.0.0/wtk_conus_2012.h5
coordinates Dataset {2488136, 2}
inversemoninobukhovlength_2m Dataset {8784, 2488136}
meta Dataset {2488136}
precipitationrate_0m Dataset {8784, 2488136}
pressure_0m Dataset {8784, 2488136}
pressure_100m Dataset {8784, 2488136}
pressure_200m Dataset {8784, 2488136}
relativehumidity_2m Dataset {8784, 2488136}
temperature_100m Dataset {8784, 2488136}
temperature_10m Dataset {8784, 2488136}
temperature_120m Dataset {8784, 2488136}
temperature_140m Dataset {8784, 2488136}
temperature_160m Dataset {8784, 2488136}
temperature_200m Dataset {8784, 2488136}
temperature_2m Dataset {8784, 2488136}
temperature_40m Dataset {8784, 2488136}
temperature_60m Dataset {8784, 2488136}
temperature_80m Dataset {8784, 2488136}
time_index Dataset {8784}
winddirection_100m Dataset {8784, 2488136}
winddirection_10m Dataset {8784, 2488136}
winddirection_120m Dataset {8784, 2488136}
winddirection_140m Dataset {8784, 2488136}
winddirection_160m Dataset {8784, 2488136}
winddirection_200m Dataset {8784, 2488136}
winddirection_40m Dataset {8784, 2488136}
winddirection_60m Dataset {8784, 2488136}
winddirection_80m Dataset {8784, 2488136}
windspeed_100m Dataset {8784, 2488136}
windspeed_10m Dataset {8784, 2488136}
windspeed_120m Dataset {8784, 2488136}
windspeed_140m Dataset {8784, 2488136}
windspeed_160m Dataset {8784, 2488136}
windspeed_200m Dataset {8784, 2488136}
windspeed_40m Dataset {8784, 2488136}
windspeed_60m Dataset {8784, 2488136}
windspeed_80m Dataset {8784, 2488136}
I will close this issue for now on this basis. Please report back if you still have trouble running reV on single hub-height wind resource datasets that contain, at minimum, pressure
, temperature
, windspeed
, and winddirection
data.
This is great you guys, thank you both.
@WilliamsTravis, assuming you're running reV, try setting the resource filepath to /datasets/WIND/conus/v1.0.0/2012/wtk_conus_2012_*.h5
. This should pick up all the 5min 2012 data including the hub heights with the pressure data. I think you can also set /datasets/WIND/conus/v1.0.0/{}/wtk_conus_{}_*.h5
which will iterate through the analysis years like normal (i havent tried this in a while but i think it works).
I'm going to copy this issue to rex where we should raise a much more obvious error if we dont have one of the key required variables.
That totally worked. Bravo!
Great point @grantbuster, I didn't even think of that.
~Just for my own curiosity, is using/datasets/WIND/conus/v1.0.0/2012/wtk_conus_2012_*.h5
any different than using /datasets/WIND/conus/v1.0.0/wtk_conus_2012.h5
? I would think that neither of these are technically considered single hub-height wind resource data, but I could be wrong~
Nvm, different time scales
yeah the annual sub folders have 5min wtk data. The files are too big to have all hub heights in a single file so they get split up. The rex multi-file handlers are meant to deal with this by feeding them the unix style file*patterns
Bug Description reV does not appear to be able to handle wind resource datasets with only one hub height.
Full Traceback
Sam Config (power curve abbreviated)
Resource File
Expected behavior reV-generation uses the singly available hub-height to generate generation profiles.
System (please complete the following information):
Charge code. Can request if not simple fix.