name: nomenclature, update labels

pvlib · kandersolar · Oct 31, 2024 · Sep 29, 2024 · Sep 29, 2024 · Oct 9, 2024
commit 637d250ff85bcace8f89f1f8e54f8fdb88b7a80a
diff --git a/docs/sphinx/source/contributing/style_guide.rst b/docs/sphinx/source/contributing/style_guide.rst
@@ -13,7 +13,7 @@ pvlib python generally follows the `PEP 8 -- Style Guide for Python Code
 is 79 characters.
 
 pvlib python uses a mix of full and abbreviated variable names. See
-:ref:`pvlib-glossary`. 
+:ref:`nomenclature`. 
 Prefer full names for new contributions. This is especially important
 for the API. Abbreviations can be used within a function to improve the
 readability of formulae.

diff --git a/docs/sphinx/source/index.rst b/docs/sphinx/source/index.rst
@@ -26,7 +26,7 @@ pvlib python
 that-use-pvlib-python>`_ page for inspiration and listing of your
 application.
 
-There is a :ref:`variable naming convention <pvlib-glossary>` to
+There is a :ref:`variable naming convention <nomenclature>` to
 ensure consistency throughout the library.
 
 

diff --git a/docs/sphinx/source/user_guide/glossary.rst b/docs/sphinx/source/user_guide/glossary.rst
@@ -1,7 +1,7 @@
-.. _pvlib-glossary:
+.. _nomenclature:
 
-Glossary
-========
+Nomenclature
+============
 
 There is a convention on consistent variable names throughout the library:
 

diff --git a/docs/sphinx/source/user_guide/index.rst b/docs/sphinx/source/user_guide/index.rst
@@ -16,5 +16,5 @@ User Guide
    bifacial
    weather_data
    singlediode
-   pvlib-glossary
+   nomenclature
    faq
diff --git a/docs/sphinx/source/user_guide/weather_data.rst b/docs/sphinx/source/user_guide/weather_data.rst
@@ -83,7 +83,7 @@ a :py:class:`pandas.DataFrame` of the actual dataset, plus a metadata
 dictionary.  Most :py:mod:`pvlib.iotools` functions also have
 a ``map_variables`` parameter to automatically translate
 the column names used in the data file (which vary widely from dataset to dataset)
-into standard pvlib names (see :ref:`pvlib-glossary`).  
+into standard pvlib names (see :ref:`nomenclature`).  
 
 Typical usage looks something like this:
 

diff --git a/pvlib/iotools/midc.py b/pvlib/iotools/midc.py
@@ -193,7 +193,7 @@ def read_midc(filename, variable_map={}, raw_data=False, **kwargs):
 
     See the MIDC_VARIABLE_MAP for collection of mappings by site.
     For a full list of pvlib variable names see the
-    :ref:`pvlib-glossary`.
+    :ref:`nomenclature`.
 
     Be sure to check the units for the variables you will use on the
     `MIDC site <https://midcdmz.nrel.gov/>`_.