You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am just wondering how pvwatts_dc method is intended to be used. Looking at the test, it sounds like we have to create a custom module_parameters with pdc0 and gamma_pdc. Those two parameters are not present in the standards module objects retrieved from CECMod or SandiaMod. pdc0 looks like being more a parameter tied to a group of modules rather than a module alone. Could it be calculated from the standard module_parameters entered to the instance in combination with modules_per_string and strings_per_inverter?. It would perhaps be more "system like", and we would have a use of the instance calculating pvwatts_dc.
As well, there is no eta_inv_nom / eta_inv_ref in the inverter_parameters object retrieved from CECMod. Calculating pvwatts_ac is not going to work straight. Maybe it could be more explicit that it has to be manually inserted (raise a custom error if not present ?).
The text was updated successfully, but these errors were encountered:
Looking at the test, it sounds like we have to create a custom module_parameters with pdc0 and gamma_pdc.
correct.
Those two parameters are not present in the standards module objects retrieved from CECMod or SandiaMod.
correct, but you can convert. might be worthwhile to have a standard conversion function in library.
pdc0 looks like being more a parameter tied to a group of modules rather than a module alone. Could it be calculated from the standard module_parameters entered to the instance in combination with modules_per_string and strings_per_inverter?. It would perhaps be more "system like", and we would have a use of the instance calculating pvwatts_dc.
For the use case you're describing, yes, that makes sense. Note that ModelChain can scale the dc calculations before passing it to the selected ac method.
As well, there is no eta_inv_nom / eta_inv_ref in the inverter_parameters object retrieved from CECMod. Calculating pvwatts_ac is not going to work straight.
These are optional parameters and I think it does work without them. I put in pr about a month ago that addressed the fact that inverter_parameters needed to be a dict instead of the default None value, though.
I'm sure we could better document all of this and I'd welcome your help to do so.
I am just wondering how
pvwatts_dc
method is intended to be used. Looking at the test, it sounds like we have to create a custommodule_parameters
withpdc0
andgamma_pdc
. Those two parameters are not present in the standards module objects retrieved from CECMod or SandiaMod.pdc0
looks like being more a parameter tied to a group of modules rather than a module alone. Could it be calculated from the standardmodule_parameters
entered to the instance in combination withmodules_per_string
andstrings_per_inverter
?. It would perhaps be more "system like", and we would have a use of the instance calculatingpvwatts_dc
.As well, there is no
eta_inv_nom
/eta_inv_ref
in theinverter_parameters
object retrieved from CECMod. Calculatingpvwatts_ac
is not going to work straight. Maybe it could be more explicit that it has to be manually inserted (raise a custom error if not present ?).The text was updated successfully, but these errors were encountered: