-
Notifications
You must be signed in to change notification settings - Fork 84
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
Clean up kWh outputs for two-meter case #529
Comments
This is about
I agree the technology model shouldn't have to know about the compensation mechanism. Perhaps we could clarify using "Net"? |
We were looking at either the hourly or lifetime outputs when we wrote this issue, not annual. I think if we change one we should change both, it would be very confusing to have the hourly outputs be different from the lifetime outputs. |
Right, Is the goal to have some way to see how much energy was purchased versus sold in absolute terms? |
Yes - for buy all / sell all (option 4, not net billing), sales and purchases can both happen in the same timestep. We can currently use system power generated and a load variable to see gross purchases and gross sales and then multiply them by the buy and sell rates, but Paul and I were thinking the above variables might be confusing for that compensation option. I think we have the option of changing the outputs for buy all / sell all, or adding some notes to the help to steer users in the right direction. |
Somewhat related issue over on the SAM repo: NREL/SAM#377 |
The outputs “electricity to grid” and “electricity from grid” are just “gen when negative” and “gen when positive.” It seems like with buy all / sell all, both of these numbers could be positive at the same time since there are two meters. Is that a change that we want to make?
Figure out where these can be re-computed based on the utility rate. It feels weird to have the performance model be aware of the rate, but it might be appropriate for the two meters case?
Be sure to test with more systems than just PV.
The text was updated successfully, but these errors were encountered: