-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Return sky diffuse and components as dataframe in irradiance.perez #434
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
Comments
This is an interesting idea. I'm concerned about maintaining API compatibility across all of the transposition models. I think the default behavior of all of the models should be the same, if possible. So, I'm reluctant to default to returning a one-column DataFrame from We could make similar changes to all of the models. I don't know if that would be useful or busy work. What would the keys look like for each function? For example
|
Good point about compatibility. We could return a Series if We could propagate the component capability into the other sky diffuse models, although perez is likely to be the most frequently used for this purpose. |
Sure, that sounds like a quick fix then. For reference, the |
@cwhanse I suggest that we limit the scope of this particular issue to |
@wholmgren I agree, |
irradiance.perez
can return isotropic, circumsolar and horizon components of sky diffuse irradiance ifreturn_components = True
. Currently, ifreturn_components
then results are returned as a tuple(sky_diffuse, diffuse_components)
with the elements being a pandas.Series and pandas.Dataframe, respectively.I propose that we always return a Dataframe with column
sky_diffuse
and optionally columns forisotropic, circumsolar, horizon
. This avoids having the output of the perez model of a different type (tuple instead of pandas object) and having to unpack the tuple when diffuse_components are requested.The text was updated successfully, but these errors were encountered: