search

pvlib / pvlib-python

A set of documented functions for simulating the performance of photovoltaic energy systems.
https://pvlib-python.readthedocs.io
BSD 3-Clause "New" or "Revised" License
1.17k stars 990 forks source link

GSoC participation roadmap of Echedey #2064

Closed echedey-ls closed 3 weeks ago

echedey-ls commented 4 months ago

Hi everybody!

After a welcoming meeting I had with this year GSoC mentors, @kandersolar and @AdamRJensen, and the other two participants, @RDaxini and @IoannisSifnaios, we were recommended to have a tracking issue of the milestones for each one of us. Here's mine.

Objectives

The proposed changes in this roadmap expect to improve the availability of models so users can include and improve their PV systems simulations. Topics are:

Roadmap

I want to open issues and PRs as I work on them. If I can manage so many things at the same time is something I have to figure out, not you - so don't hesitate to give as much feedback as you want! 😆

I'm looking forward to use my knowledge to improve this package, but as the inexperienced student I am, I can't do it without y'all, so I want to hear from you in either issues or PRs 🤙

Other PRs that I have worked on during this GSoC period

Cross-referencing:

cwhanse commented 4 months ago

Thinking about the API for the agrivoltaics functions, modeling an agrivoltaic system involves a modeling chain that handles both the photovoltaic and crop production. Some steps in that chain are in common, e.g., separating GHI into diffuse and direct, but more likely, many steps are in parallel, e.g. calculate cell temperature and calculate air temperature for the crops. The same function won't be used for both steps.

Two options suggest themselves:

  1. put agrivoltaics functions into the code module for the corresponding photovoltaic modeling step, i.e., irradiance, temperature, unless there's no corresponding photovoltaic step, in which case the function goes into an agrivoltaic module, e.g., interface function to crop production model libraries.
  2. put all agrivoltaics functions into a separate module(s) the scope of which is only agrivoltaics.

I lean to option 1, since I prefer to look at agrivoltaics as a variation of the core pvlib workflow. I have the same view of floating PV modeling.

If we agree on option 1, then the PAR diffuse fraction function would go with the rest of the GHI separation functions, into pvlib.irradiance.

echedey-ls commented 4 months ago

Right now the opinions are the same for pvlib.spectrum and pvlib.irradiance, so anyone visiting this conversation is encouraged to leave their thoughts at #2047! 😃

@cwhanse I agree with your suggestion. I'd like you to have a look, if possible, to the PAR shading factors paper since they are more oriented to a geometrical 3D space approach, and as of now, I don't think pvlib has any functionality regarding that. In any case, I will open an issue in short so we can move that conversation there.

echedey-ls commented 3 weeks ago

This GSoC has come to its end, so this issue can be safely closed :D

❣️ Thank you very much to everybody, specially the mentors @kandersolar & @AdamRJensen and fellow contributors @RDaxini & @IoannisSifnaios for the funny meetings, and all the maintainers and community members involved in my PRs and discussions (@cwhanse , @adriesse , @mikofski ...)

I will try to continue contributing to pvlib in the future as well 🫡