-
Notifications
You must be signed in to change notification settings - Fork 103
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
Distribution clipping method #1137
Conversation
checks for divide by zero error
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great implementation of a complex model! Some comments in-line that should be addressed before merging.
shared/lib_pv_io_manager.cpp
Outdated
p_subhourlyClippingLossFactor = cm->allocate("subhourly_clipping_loss_factor", numberOfLifetimeRecords); | ||
//p_subhourlyClippingLossFactor = cm->allocate("subhourly_clipping_loss_factor", numberOfLifetimeRecords); | ||
|
||
p_DistributionClippingLoss = cm->allocate("distribution_clipping_loss", numberOfLifetimeRecords); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this output, and the subhourly clipping loss above, be conditionally defined to only show up if these features are enabled?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We currently have bifacial electrical mismatch show up as a potential modeled loss factor that shows up in all model runs just as a data point.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah. I am always in favor of outputs only showing up when they apply, but I'm sure there are a variety that have gone unnoticed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No worries I can make those conditional.
-Implement Walker clipping method that uses distribution of PV power output to calculate clipping potential
-https://www.nrel.gov/docs/fy20osti/76859.pdf
-Accessible through SDK
-Add test for feature usage
-Linke turbidity currently fixed at 1.0, todo add surrogate or lookup for turbidity value