Closed netr0m closed 1 year ago
Hey thank you for the detailed bug report @netr0m. It's highly likely that this error is due to an error with your custom resource file. Here are some small sample resource files that you can check formatting against: https://github.com/NREL/reV/blob/main/tests/data/nsrdb/ri_100_nsrdb_2013.h5
Here are some other things i would recommend checking / trying:
latitude, longitude, timezone, elevation
If you figure it out, be sure to let me know what went wrong so we can make the docstrings more clear.
Hi Grant,
Thanks for the quick response! We had some other projects taking up time in the meanwhile, but we've finally managed to do a successful run!
We initially believed that the issue was with our conversion of the data for calculating dni
, dhi
and ghi
. We focused our efforts on those conversions (we were using the ERA5 climate data set as our basis, extracting ssrd
and fdir
which we in turn converted to the various irradiation types.
The final fix that resolved our issue was the fact that the latitudes and longitudes were not in the range -90..90 and -180..180. I suppose that this, in combination with our previously incorrect calculation of the irradiation values, were the cause of the failed runs.
Thanks again!
Ah yeah that makes sense. The SAM PVWatts module needs the lat/lon to calculate solar zenith angle to get the plane of array irradiance. Thanks for letting us know what the problem is! We'll have to add a check on the lat/lon range at some point. I'll add a feature request.
Bug Description
We've created our own resource file (data gathered from the "ERA5" dataset), following the structure of the
brazil_solar.h5
example dataset. As such, our dataset contains:0.0
. we've used 'real' values in the past, but with the same result)YYYY-MM-DD HH:MM:SS
)When running reV gen (see example code below), an error occurs stating that an error occurred while processing irradiation on surface (
code -102
), but we're unable to identify what the exact issue is (Failed to process irradiation on surface (code: -102) [y:2016 m:1 d:1 h:0 minute:0].
).The H5 resource file can be shared on request. Hopefully you might be able to assist us in identifying the specific dataset in responsible for the error.
Full Traceback Full traceback of any errors received, if applicable
Code Sample
test.py
:We ran this in a Docker container (based on
debian:11
), see Dockerfile below:SAM config (
sam_config_solar_fixed.json
):To Reproduce Steps to reproduce the problem behavior
Dockerfile
from the definition abovetest.py
from the definition abovedocker build -t rev-test .
)Expected behavior For the program to execute successfully. The SAM config has been run with the example dataset for solar (
brazil_solar.h5
), which worked well (finished without errors)Screenshots N/A
System (please complete the following information):
v0.6.4
Additional context