-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Add guidance about temperature modeling to User Guide #2591
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
Open
kandersolar
wants to merge
13
commits into
pvlib:main
Choose a base branch
from
kandersolar:userguide-temperature
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
b372117
create temperature user guide page
kandersolar d5699d1
Apply suggestions from code review
kandersolar 94d2a71
Apply suggestions from code review
kandersolar 11a3660
Merge branch 'main' into userguide-temperature
kandersolar 13d4138
add mention of parameter conversion with GenericLinearModel
kandersolar 3f80c84
Merge branch 'userguide-temperature' of https://github.com/kandersola…
kandersolar 0a25860
add note about IR
kandersolar 34ef159
move "other functions" up to below the table
kandersolar b2ecc30
fix spelling
kandersolar bbf9bbd
Apply suggestions from code review
kandersolar e2fb426
feedback from review
kandersolar 62faf38
more changes from review
kandersolar 7527867
Update docs/sphinx/source/user_guide/modeling_topics/temperature.rst
kandersolar File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
105 changes: 105 additions & 0 deletions
105
docs/sphinx/source/user_guide/modeling_topics/temperature.rst
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,105 @@ | ||
| .. _temperature: | ||
|
|
||
| Temperature models | ||
| ================== | ||
|
|
||
| pvlib provides a variety of models for predicting the operating temperature | ||
| of a PV module from irradiance and weather inputs. These models range from | ||
| simple empirical equations requiring just a few multiplications to more complex | ||
| thermal balance models with numerical integration. | ||
|
|
||
| Types of models | ||
| --------------- | ||
|
|
||
| Temperature models predict one of two quantities: | ||
|
|
||
| - *module temperature*: the temperature as measured at the back surface | ||
| of a PV module. Easy to measure, but usually marginally less | ||
| than the cell temperature which determines efficiency. | ||
| - *cell temperature*: the temperature of the PV cell itself. The relevant | ||
| temperature for PV modeling, but almost never measured directly. | ||
|
|
||
| Temperature models estimate these quantities using inputs like incident | ||
| irradiance, ambient temperature, and wind speed. Each model also takes | ||
| a set of parameter values that represent how a PV module responds to | ||
| those inputs. Parameter values generally depend on both the PV | ||
| module technologies, the mounting configuration of the module, | ||
| and on any weather parameters that are not included in the model. | ||
| Note that, despite models conventionally being associated with either | ||
| cell or module temperature, it is actually the parameter values that determine | ||
| which of the two temperatures are predicted, as they will produce the same | ||
| type of temperature from which they were originally derived. | ||
|
|
||
| Another aspect of temperature models is whether they account for | ||
| the thermal inertia of a PV module. Temperature models are either: | ||
|
|
||
| - *steady-state*: the module is assumed to have been at the specified operating | ||
| conditions for a sufficiently long time for its temperature to reach | ||
| equilibrium. | ||
| - *transient*: the module's thermal inertia is included in the model, | ||
| causing a lag in modeled temperature change following changes in the inputs. | ||
|
|
||
| Other effects that temperature models may consider include the | ||
| photoconversion efficiency and radiative cooling. | ||
|
|
||
| The temperature models currently available in pvlib are summarized in the | ||
| following table: | ||
|
|
||
| +----------------------------------------------+--------+------------+---------------------------------------------------------------------------+ | ||
| | Model | Type | Transient? | Inputs | | ||
| | | | +----------------+---------------------+------------+-----------------------+ | ||
| | | | | POA irradiance | Ambient temperature | Wind speed | Downwelling IR [#f1]_ | | ||
| +==============================================+========+============+================+=====================+============+=======================+ | ||
| | :py:func:`~pvlib.temperature.faiman` | either | | ✓ | ✓ | ✓ | | | ||
| +----------------------------------------------+--------+------------+----------------+---------------------+------------+-----------------------+ | ||
| | :py:func:`~pvlib.temperature.faiman_rad` | either | | ✓ | ✓ | ✓ | ✓ | | ||
| +----------------------------------------------+--------+------------+----------------+---------------------+------------+-----------------------+ | ||
| | :py:func:`~pvlib.temperature.fuentes` | either | ✓ | ✓ | ✓ | ✓ | | | ||
| +----------------------------------------------+--------+------------+----------------+---------------------+------------+-----------------------+ | ||
| | :py:func:`~pvlib.temperature.generic_linear` | either | | ✓ | ✓ | ✓ | | | ||
| +----------------------------------------------+--------+------------+----------------+---------------------+------------+-----------------------+ | ||
| | :py:func:`~pvlib.temperature.noct_sam` | cell | | ✓ | ✓ | ✓ | | | ||
| +----------------------------------------------+--------+------------+----------------+---------------------+------------+-----------------------+ | ||
| | :py:func:`~pvlib.temperature.pvsyst_cell` | cell | | ✓ | ✓ | ✓ | | | ||
| +----------------------------------------------+--------+------------+----------------+---------------------+------------+-----------------------+ | ||
| | :py:func:`~pvlib.temperature.ross` | cell | | ✓ | ✓ | | | | ||
| +----------------------------------------------+--------+------------+----------------+---------------------+------------+-----------------------+ | ||
| | :py:func:`~pvlib.temperature.sapm_cell` | cell | | ✓ | ✓ | ✓ | | | ||
| +----------------------------------------------+--------+------------+----------------+---------------------+------------+-----------------------+ | ||
| | :py:func:`~pvlib.temperature.sapm_module` | module | | ✓ | ✓ | ✓ | | | ||
| +----------------------------------------------+--------+------------+----------------+---------------------+------------+-----------------------+ | ||
|
|
||
| .. [#f1] Downwelling infrared radiation. | ||
|
|
||
| In addition to the core models above, pvlib provides several other functions | ||
| for temperature modeling: | ||
|
|
||
| - :py:func:`~pvlib.temperature.prilliman`: an "add-on" model that reprocesses | ||
| the output of a steady-state model to apply transient effects. | ||
| - :py:func:`~pvlib.temperature.sapm_cell_from_module`: a model for | ||
| estimating cell temperature from module temperature. | ||
|
|
||
|
|
||
| Model parameters | ||
| ---------------- | ||
|
|
||
| Some temperature model functions provide default values for their parameters, | ||
| and several additional sets of temperature model parameter values are | ||
| available in :py:data:`pvlib.temperature.TEMPERATURE_MODEL_PARAMETERS`. | ||
| However, these generic values may not be suitable for all modules and mounting | ||
| configurations. It should be noted that using the default parameter values for each | ||
| model generally leads to different modules temperature predictions. This alone | ||
| does not mean one model is better than another; it's just evidence that the measurements | ||
| used to derive the default parameter values were taken on different PV systems in different | ||
| locations under different conditions. | ||
|
|
||
| Parameter values for one model (e.g. ``u0``, ``u1`` for :py:func:`~pvlib.temperature.faiman`) | ||
| can be converted to another model (e.g. ``u_c``, ``u_v`` for :py:func:`~pvlib.temperature.pvsyst_cell`) | ||
| using :py:class:`~pvlib.temperature.GenericLinearModel`. | ||
|
|
||
| Module-specific values can be obtained via testing, for example following | ||
| the IEC 61853-2 standard for the Faiman model; however, such values still do not capture | ||
| the dependency of temperature on system design and other variables. | ||
|
|
||
| Currently, pvlib provides no functionality for fitting parameter values | ||
| using measured temperature. | ||
kandersolar marked this conversation as resolved.
Show resolved
Hide resolved
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
You could consider including references to:
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.
I'm not sure pointing to external functionality makes sense for these pages. Let's save that for a potential follow-up.
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.
What kind of "sense" are we looking for? Pointing to solutions takes the edge off the foregoing limitation a bit. I think the new spectrum section has similar pointers. But I leave the decision to you.