Skip to content

Commit a28af18

Browse files
committed
Help revisions for PV UI redesign
1 parent ffca0f1 commit a28af18

File tree

9 files changed

+254
-273
lines changed

9 files changed

+254
-273
lines changed

doc/readme.md

Lines changed: 13 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,16 @@
1-
# SAM Help
1+
# SAM Help Build Guide
22

33
These instructions are for writing and editing content and building SAM's Help system.
44

5-
The Help system is built with the Sphinx documentation generator that converts .rst source files into structured html documents.
6-
75
Help content is written in the reStructuredText (.rst) text markup language: https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html.
86

9-
Sphinx is a Python package that converts the content to HTML: https://www.sphinx-doc.org/en/master/.
7+
The Sphinx documentation generator converts .rst source files into structured HTML.
8+
9+
Sphinx is a Python package: https://www.sphinx-doc.org/en/master/.
1010

1111
SAM Help uses Sphinx Book Theme to apply formatting to the HTML: https://sphinx-book-theme.readthedocs.io/en/stable/index.html.
1212

13-
The Sphinx Book Theme, Sphinx, and reStructuredText are all well documented. The documentation below describes the application of these tools to build SAM Help. Refer to the documentation above for detailed descriptions and for information about modifying or adding more features to SAM Help.
13+
Complete documentation for the Sphinx Book Theme, Sphinx, and reStructuredText is available at the links above. The documentation below describes the application of these tools to build SAM Help.
1414

1515
## Requirements
1616

@@ -70,6 +70,8 @@ Tested on Windows with Python 3.12.10 and GNU Make 4.4.1.
7070

7171
To clean the build using Make, run `make clean`.
7272

73+
To see a list of Make targets, run `make`.
74+
7375
4. If there are any build errors, fix them by editing the appropriate .rst file(s).
7476

7577
5. When the build finishes, HTML and associated files should be in the `../doc/build/html` folder. (The `../doc/build/doctrees` folder is used during the build and not needed to display the HTML files.)
@@ -213,6 +215,12 @@ The `../doc/includes` folder contains files with text "snippets" or reusable tex
213215

214216
For example the `../doc/includes/snip_system_availability.rst` is a description of the system availability losses that is used in descriptions of each of the performance models, such as in the Detailed PV model's "Electrical Losses" topic, and the Physical Trough model's "System Control" topic.
215217

218+
To insert the content of `snip_system_availability.rst` from a file in a `../doc/source` subfolder:
219+
220+
```
221+
.. include:: ../includes/snip_system_availability.rst
222+
```
223+
216224
**Important note about snippets**: Do not include targets (`.. _target-name-in-snippet`), cross references references to targets in other snippet files, or cross references to other snippet files in snippet files. Doing so results in duplicate target names which breaks the Sphinx build. You can include cross references in snippet files to topic files that are not in the `../doc/includes` folder.
217225

218226
## Headings

doc/source/_static/custom.css

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,16 @@
11
h1 {
2-
font-size: 1.75em;
2+
font-size: 2em;
33
}
44

55
h2 {
6-
font-size: 1.5em;
6+
font-size: 1.75em;
77
}
88

99
h3 {
10-
font-size: 1.25em;
10+
font-size: 1.5em;
1111
}
1212

1313
h4 {
14-
font-size: 1em;
14+
font-size: 1.25em;
1515
font-weight: bold;
1616
}

doc/source/detailed-photovoltaic-model/pv_inverter.rst

Lines changed: 90 additions & 73 deletions
Large diffs are not rendered by default.

doc/source/detailed-photovoltaic-model/pv_module.rst

Lines changed: 120 additions & 124 deletions
Large diffs are not rendered by default.
Lines changed: 17 additions & 52 deletions
Original file line numberDiff line numberDiff line change
@@ -1,83 +1,48 @@
1-
Detailed Photovoltaic Model
2-
===========================
1+
Getting Started with the Detailed Photovoltaic Model
2+
====================================================
33

4-
The following overview is to help you get started modeling  a photovoltaic system with the detailed photovoltaic model. For a description of the model, see :doc:`Performance Models <../introduction/technology_options>`.
4+
The following overview is to help you get started modeling a photovoltaic system with the detailed photovoltaic model. For a description of the model, see :doc:`Performance Models <../introduction/technology_options>`.
5+
6+
.. note:: If you only have basic information about the photovoltaic system's design like the system size and orientation, you can use the :doc:`../pvwatts/pvwatts` model instead of the Detailed Photovoltaic model. PVWatts does not require detailed information about the module, inverter, and array layout.
57

68
For a complete technical description of SAM's photovoltaic model, see Gilman, P. (2015). SAM Photovoltaic Model Technical Reference. National Renewable Energy Laboratory. 59 pp.; NREL/TP-6A20-64102. (`PDF 840 KB <https://docs.nrel.gov/docs/fy15osti/64102.pdf>`__)
79

8-
Basic Steps
9-
-----------
10+
Follow the steps below to get started using the detailed photovoltaic model. If you are unsure of an input, use its default value. After running simulations, exploring results, and collecting more information about your project, you can refine the inputs.
1011

1112
**1. Choose a weather file**
1213

13-
* On the :doc:`Location and Resource <pv_location_and_resource>` page, choose a weather file to represent the solar resource at the project location.
14+
* On the :doc:`Location and Resource <pv_location_and_resource>` page, choose or download a weather file to represent the solar resource at the project location.
1415

1516
**2. Specify the system's characteristics**
1617

1718
#. On the :doc:`Module <pv_module>` page, choose a model option and module.
1819

19-
For most applications, use the CEC Performance Model with Module Database model unless your module is not in the list, in which case you can use the CEC Performance Model with User Specifications.
20+
For most applications, use the CEC Performance Model with Module Database model. If your module is not in the list, use the CEC Performance Model with User Specifications.
2021

2122
#. On the :doc:`Inverter <pv_inverter>` page, choose a model option and inverter.
2223

2324
Use the Inverter CEC Database option. For an inverter that is not in the list, if you have the manufacturer's data sheet, choose the Inverter Datasheet model.
2425

2526
#. On the :doc:`pv_system_size` page, specify the system's size and array tracking options.
2627

27-
Use the specify desired array size option for preliminary analysis, and then use specify modules and inverters to refine the system design.
28+
Use **Specify desired size and DC/AC ratio** for preliminary analysis, and then use **Specify number of modules and inverters** to refine the system design.
2829

29-
#. If you want to account for shading losses, use the :doc:`pv_soiling_shading_snow` page for external shading by nearby objects, array self-shading, or to account for losses due to the array being covered by snow when your weather data includes snow depth data.
30+
#. To account for soiling, shading, or snow losses, use the :doc:`pv_soiling_shading_snow` page. By default, SAM assumes no shading or snow losses, and 5% soiling losses.
3031

31-
#. Account for soiling losses, DC power losses, AC power losses, and losses due to system availability requirements on the :doc:`pv_electrical_losses` page. You can use the default values if you do not have detailed information about those losses for your system.
32+
#. Account for DC power losses, AC power losses, and losses due to system availability requirements on the :doc:`pv_electrical_losses` page. You can use the default values if you do not have detailed information about those losses for your system.
3233

3334
**3. Specify the project costs**
3435

35-
* On the :doc:`Installation costs <../installation-costs/cc_pv>` and :doc:`Operating costs <../operating-costs/oc_operating>` pages, specify values for capital cost and operation and maintenance costs.
36+
If you are using the detailed photovoltaic model with a financial model, specify capital costs on the :doc:`Installation costs <../installation-costs/cc_pv>` page, and operation and maintenance costs on the :doc:`Operating costs <../operating-costs/oc_operating>` pages.
37+
38+
**4. Review financial assumptions**
39+
40+
The inputs on the remaining pages are inputs to the financial model. For your first simulation runs as you learn to use SAM, use the default values and review results to see how the model works. The default values are reasonable for a typical project in the United States. As you become familiar with the model, you can modify the financial inputs as appropriate for your analysis.
3641

3742
**4. Run a simulation and review results**
3843

39-
* Click Simulate, and review :doc:`results <pv_results>` on the :doc:`Results Page <../getting-started/results_page>`.
44+
* Click **Simulate**, and review :doc:`results <pv_results>` on the :doc:`Results Page <../getting-started/results_page>`.
4045

4146
.. image:: ../images/SS_MainWindow-RunAllSimulationsButton.png
4247
:align: center
4348
:alt: SS_MainWindow-RunAllSimulationsButton.png
44-
45-
.. _postsimulationwarnings:
46-
47-
Post-simulation Notices
48-
-----------------------
49-
50-
After completing a simulation, SAM checks to see whether the inverter appears to be over- or under-sized based on the actual DC output of the array. If it finds any problems, it displays :doc:`notices <../results/notices>` after simulations are complete.
51-
52-
**Inverter undersized**
53-
The array output is greater than inverter rated capacity for one or more of the 8,760 hours in one year. SAM reports the number of hours that the array's simulated DC output is greater than the inverter's AC rated capacity.
54-
55-
If the number of hours is small compared to the 8,760 hours in a year, you may choose to ignore the message. Otherwise, you may want to try increasing the inverter capacity.
56-
57-
For example, for a system with 400 kWdc array capacity and 150 kWac total inverter capacity, SAM displays the following warning message: "pvsamv1: Inverter undersized: The array output exceeded the inverter rating 157.62 kWdc for 2128 hours."
58-
59-
The following :doc:`time series graphs <../results/timeseries>` show the array's DC output in red, and the system's AC output in blue, indicating that the inverter capacity is limiting the system's AC output.
60-
61-
This graph shows the time series data for one year:
62-
63-
.. image:: ../images/IMG_PVError-time-series-inverter-undersized.png
64-
:align: center
65-
:alt: IMG_PVError-time-series-inverter-undersized.png
66-
67-
And this one shows the same data zoomed in to five days:
68-
69-
.. image:: ../images/IMG_PVError-days-inverter-undersized.png
70-
:align: center
71-
:alt: IMG_PVError-days-inverter-undersized.png
72-
73-
**Inverter output less than 75 percent of inverter rated capacity**
74-
SAM compares the inverter's maximum AC output to the total inverter AC capacity and displays a simulation warning if the inverter's maximum AC output is less than 75% of the total inverter rated AC capacity.
75-
76-
For example, for a system with 400 kWdc array capacity and 750 kWac inverter capacity, SAM displays the following warning message: "pvsamv1: Inverter oversized: The maximum inverter output was 43.13% of the rated value 750 kWac."
77-
78-
In this case, the time series graph of gross AC output shows that the inverter output never reaches the 750 kWac capacity.
79-
80-
.. image:: ../images/IMG_PVError-time-series-inverter-oversized.png
81-
:align: center
82-
:alt: IMG_PVError-time-series-inverter-oversized.png
83-
-2.91 KB
Loading

doc/source/includes/snip_pv_inverter_temperature_curves.rst

Lines changed: 2 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,3 @@
1-
2-
Inverter Temperature Derate Curves
3-
..................................
4-
51
Temperature derating is an inverter function that decreases inverter power to prevent heat-related damage to internal components when the ambient temperature increases above a pre-defined value. SAM uses the information from the inverter temperature derate curves with ambient temperature data from the weather file to adjust the inverter efficiency in each time step of the simulation. As ambient temperature increases, the inverter efficiency decreases based on the data in the table. You can see the effect of inverter temperature derating using the following results variables:
62

73
* **Inverter thermal derate DC power loss (kWh/yr)**
@@ -10,6 +6,8 @@ Temperature derating is an inverter function that decreases inverter power to pr
106

117
* **Inverter thermal derate DC power loss (kW)**
128

9+
SAM adjusts the inverter efficiency based on the ambient temperature in the weather file based on the Efficiency - Ambient Temperature curve under **Inverter Temperature Derate Curves**. The default curve decreases the inverter efficiency as the ambient temperature increases above 52.8 degrees Celsius at a rate of 0.021% per degree of temperature increases. You can edit the values in the efficiency table to change the shape of the curve.
10+
1311
Temperature derating data is not included in the inverter library, but may be available on the inverter manufacturer datasheet. The default generic temperature derating curve is for an inverter that starts derating when the ambient temperature reaches 50°C at 1300 Vdc and shuts the inverter down when the ambient temperature reaches 55°C. You can use the default data if you do not expect the inverter to be exposed to high temperatures.
1412

1513
The following example shows SAM derating data for the inverter described in the SMA technical document "SUNNY BOY / SUNNY TRIPOWER Temperature Derating" available at https://files.sma.de/downloads/Temp-Derating-TI-en-15.pdf.
@@ -36,9 +34,6 @@ The following example shows SAM derating data for the inverter described in the
3634
**Update plot**
3735
After changing values in the table, click **Update plot** to change the graph.
3836

39-
40-
41-
4237
.. note:: To avoid excessive temperature derating losses for large inverters, make sure the highest Vdc voltage value in the temperature derate curves is greater than or equal to the inverter's maximum VDC voltage rating.
4338

4439

doc/source/includes/snip_pv_transient_thermal_model.rst

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,3 @@
1-
2-
Transient Thermal Model Correction
3-
..................................
4-
51
When the simulation time step determined by the number of records in the weather file is 20 minutes or less, SAM automatically applies a correction to account for temperature changes driven by wind speed and the mass of the module using the method described in Prilliman (2020) listed on the `PV Publications <https://sam.nrel.gov/photovoltaic/pv-publications.html>`__ page of the SAM website..
62

73
**Module unit mass, kg/m²**

doc/source/reference/libraries.rst

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
11
Libraries
22
=========
33

4-
A library is a text file of comma-separated values that stores sets of data associated with a SAM input in the libraries folder of your SAM installation folder. SAM displays the library contents in a :ref:`library browser <librarybrowser>` where you choose an item from the library to populate values of a set of input variables. For example, the detailed photovoltaic model uses a library to store inverter parameters. By choosing an inverter name, you populate the 16 input variables required to specify an inverter using the CEC inverter model.
4+
A library is a text file of comma-separated values (CSV) that stores sets of data associated with a SAM input in the libraries folder of your SAM installation folder. SAM displays the library contents in a :ref:`library browser <librarybrowser>` where you choose an item from the library to populate values of a set of input variables. For example, the detailed photovoltaic model uses a library to store inverter parameters. By choosing an inverter name, you populate the 16 input variables required to specify an inverter using the CEC inverter model.
55

66
.. note:: In addition to the parameter libraries shown in the table below, SAM also creates libraries as temporary files on your computer to store information about your wind and solar resource data files. For more about weather file libraries, see :doc:`Weather Files and Libraries <../weather-data/weather_manage_folders>`.
77

8+
You can find copies of the SAM library CSV files at https://github.com/NREL/SAM/tree/develop/deploy/libraries.
9+
810
.. list-table::
911
:width: 100%
1012
:align: center
@@ -17,11 +19,11 @@ A library is a text file of comma-separated values that stores sets of data asso
1719
* - CEC Inverters
1820
- Photovoltaic inverters
1921
- Detailed photovoltaic
20-
- Go Solar California
22+
- California Energy Commission
2123
* - CEC Modules
2224
- Photovoltaic modules
2325
- Detailed photovoltaic
24-
- Go Solar California
26+
- California Energy Commission
2527
* - Empirical Trough HCEs
2628
- Parabolic trough receivers
2729
- Empirical trough
@@ -91,9 +93,11 @@ For most applications, you do not need to modify libraries. However, if you have
9193

9294
.. note:: If you modify a library, do not change the first three rows of the library file.
9395

96+
Each version of SAM has a separate installation folder. If you modify a library file for one version of SAM, it will only affect that version, and may be deleted when you remove (uninstall) that version.
97+
9498
The library file format is defined as follows:
9599

96-
* Library files use the .csv file name extension and are stored in the Libraries folder of your SAM installation.
100+
* Library files use the .csv extension and are stored in the Libraries folder in the :ref:`installationfolder`.
97101

98102
* The first row of a library file is a list of the labels describing the input variables stored in the library. SAM displays these labels in the library browser. It does not use these labels in calculations.
99103

0 commit comments

Comments
 (0)