Change references to postprocessor-diagnostic to diagnostic only

Author: ladc

{{cookiecutter.project_name}}/README.rst

@@ -14,7 +14,7 @@ License
 Documentation
 =============
 
-Here write a short description of the plugin, indicating the importers or postprocessors that it provides.
+Here write a short description of the plugin, indicating the importers, diagnostics etc. that it provides.
 
 Installation instructions
 =========================

{{cookiecutter.project_name}}/setup.py

@@ -68,7 +68,7 @@
     # An entry point is defined by three properties:
     # - The group that an entry point belongs indicate the kind of functionality that
     #   provides. For the pysteps importers use the "pysteps.plugins.importers" group.
-    #   For the pysteps diagnostic postprocessors use the "pysteps.plugins.postprocessor" group.
+    #   For the pysteps diagnostics use the "pysteps.plugins.diagnostics" group.
     # - The unique name that is used to identify this entry point in the
     #   "pysteps.plugins.importers" group.
     # - A reference to a Python object. For the pysteps importers, the object should

{{cookiecutter.project_name}}/tests/test_{{cookiecutter.project_slug}}.py

@@ -18,15 +18,15 @@ def test_plugins_discovery():
         for importer in new_importers:
             assert importer.replace("import_", "") in io_interface._importer_methods
 
-    elif plugin_type == "postprocessor":
-        new_postprocessors = ["{{cookiecutter.plugin_name }}"]
-        for postprocessor in new_postprocessors:
-            postprocessor.replace("postprocessors_", "")
-            if postprocessor.startswith("diagnostics"):
-                assert postprocessor in pp_interface._diagnostics_methods
-            elif postprocessor.startswith("ensemblestats"):
-                assert postprocessor in pp_interface._ensemblestats_methods
-
+    elif plugin_type == "diagnostic":
+        new_dagnostics = ["{{cookiecutter.plugin_name }}"]
+        for diagnostic in new_diagnostics:
+            assert diagnostic in pp_interface._diagnostics_methods
+            
+    elif plugin_type == "ensemblestat":
+        new_ensemblestats = ["{{cookiecutter.plugin_name }}"]
+        for ensemblestat in new_ensemblestats:
+            assert ensemblestat in pp_interface._ensemblestats_methods
 
 def test_importers_with_files():
     """Additionally, you can test that your plugin correctly reads the corresponding

{{cookiecutter.project_name}}/{{cookiecutter.project_slug}}/postprocessor/__init__.py renamed to {{cookiecutter.project_name}}/{{cookiecutter.project_slug}}/diagnostic/__init__.py

@@ -8,28 +8,29 @@
 
 # Import the needed libraries
 
-### Uncomment the next lines if pyproj is needed for the postprocessor.
+### Uncomment the next lines if pyproj is needed 
 # try:
 #     import pyproj
 #
 #     PYPROJ_IMPORTED = True
 # except ImportError:
 #     PYPROJ_IMPORTED = False
 
-# Function {{ cookiecutter.plugin_name }} to create postprocessing plugins.
+# Function {{ cookiecutter.plugin_name }} to create diagnostic plugins.
 
-# IMPORTANT: The name of the postprocessor should follow the "postprocessor_postprocessorType_postprocessorName"
-# naming convention. The "postprocessor_" prefix to the postprocessor name is MANDATORY since it is
-# used by the pysteps interface. "postprocessorType" refers to the category of postprocessor e.g. diagnostics, ensemblestats, etc.
-# "postprocessorName" refers to a unique identifier name for the postprocessor e.g. prtype, meancalc, etc.
+# IMPORTANT: The name of the plugin should follow the "postprocessingType_postprocessingName"
+# naming convention. "postprocessingType" refers to the category of
+# postprocessing e.g. diagnostics, ensemblestats, etc.  "postprocessingName"
+# refers to a unique identifier name for the postprocessing e.g. prtype,
+# meancalc, etc.
 #
-# Check the pysteps documentation for examples of postprocessor names that follow this
+# Check the pysteps documentation for examples of postprocessing names that follow this
 # convention:
 # https://pysteps.readthedocs.io/en/latest/pysteps_reference/io.html#available-diagnostics
 #
-# The function prototype for the postprocessor's declaration should have the following form:
+# The function prototype for the postprocessing's declaration should have the following form:
 #
-#  def postprocessor_type_xyz(filename, **kwargs):
+#  def postprocessingtype_xyz(filename, **kwargs):
 #
 #
 # Function arguments
@@ -38,7 +39,7 @@
 # The function arguments should have the following form:
 # (filename, keyword1="some_keyword", keyword2=10,...,keywordN="something", **kwargs)
 # The `filename` and `**kwargs` arguments are mandatory to comply with the pysteps
-# interface. To fine-control the behaviour of the postprocessor, additional keywords can be
+# interface. To fine-control the behaviour of the postprocessing, additional keywords can be
 # added to the function.
 # For example: keyword1="some_keyword", keyword2=10, ..., keywordN="something"
 # It is recommended to declare the keywords explicitly in the function to improve the
@@ -48,14 +49,14 @@
 # Return arguments
 # ~~~~~~~~~~~~~~~~
 #
-# The postprocessor can return whatever argument is needed.
+# The postprocessing can return whatever argument is needed.
 #
 #
 
 def {{cookiecutter.plugin_name}}(filename, **kwargs):
       """
-      A detailed description of the postprocessor. A minimal documentation is
-      strictly needed since the pysteps postprocessor interface expects docstrings.
+      A detailed description of the postprocessing plugin. A minimal documentation is
+      strictly needed since the pysteps postprocessing interface expects docstrings.
 
       For example, the documentation may look like this:
 
@@ -67,19 +68,19 @@ def {{cookiecutter.plugin_name}}(filename, **kwargs):
             Name of the file to be processed.
 
       keyword1 : str
-            Some keyword used to fine control the diagnostic postprocessor behaviour.
+            Some keyword used to fine control the behaviour.
 
       keyword2 : int
-            Another keyword used to fine control the diagnostic postprocessor behaviour.
+            Another keyword used to fine control the behaviour.
 
       {extra_kwargs_doc}
 
       Returns
       -------.
       """
       ####################################################################################
-      # Add the code required to run the postprocessor here.
+      # Add the code required to run the postprocessing here.
       file = open(filename, "w")
       file.write("hello world")
       file.close()
-      return file
+      return file