I started looking at the plotting notebooks for the planned FloPy version 3.3.0 release and there is quite a bit of redundancy that could be removed or consolidated. Right now there are 7 notebooks that display plotting functionality:
flopy3_PlotArrayExample (shows how to use the built in .plot() methods)
flopy3_mf6_plotting_freyberg (shows basic plotting using PlotMapView using the Freyberg model. This was introduced during development of the PlotMapView classes)
flopy3_mf6_BasicPlotting (shows basic structured grid and cvfd plotting using PlotMapView and modflow 6 models)
flopy3_UnstructuredGridPlotting (shows unstructured grid plotting)
flopy3_PlotCrossSection_demo (shows PlotCrossSection functionality and backward compatibilty to the ModelCrossSection class. Displays use cases for both StructuredGrid and VertexGrid models)
flopy3_PlotMapView_demo (shows PlotMapView functionality and backward compatibility with the ModelMap class. Displays use cases for StructuredGrid, VertexGrid, and UnstructuredGrid models)
flopy3_MapExample (shows PlotMapView and PlotCrossSection functionality for structured grids)
I think we can reduce this to two or three notebooks depending on how we want to present these classes and showcase this functionality:
Notebook 1) A map view plotting notebook that covers PlotMapView plotting that includes examples from StructuredGrid, VertexGrid, and UnstructuredGrid models. Also use a combination of MF6 and MF2005/USG models for this notebook
Notebook 2) A cross sectional plotting notebook that covers PlotCrossSection plotting that includes examples from StructuredGrid and VertexGrid
Notebook 3) Maintain the current flopy3_PlotArrayExample notebook.
Are there any thoughts or other ways that make sense to structure these sets of notebooks?
I started looking at the plotting notebooks for the planned FloPy version 3.3.0 release and there is quite a bit of redundancy that could be removed or consolidated. Right now there are 7 notebooks that display plotting functionality:
flopy3_PlotArrayExample (shows how to use the built in .plot() methods)
flopy3_mf6_plotting_freyberg (shows basic plotting using
PlotMapViewusing the Freyberg model. This was introduced during development of thePlotMapViewclasses)flopy3_mf6_BasicPlotting (shows basic structured grid and cvfd plotting using
PlotMapViewand modflow 6 models)flopy3_UnstructuredGridPlotting (shows unstructured grid plotting)
flopy3_PlotCrossSection_demo (shows
PlotCrossSectionfunctionality and backward compatibilty to theModelCrossSectionclass. Displays use cases for bothStructuredGridandVertexGridmodels)flopy3_PlotMapView_demo (shows
PlotMapViewfunctionality and backward compatibility with theModelMapclass. Displays use cases forStructuredGrid,VertexGrid, andUnstructuredGridmodels)flopy3_MapExample (shows
PlotMapViewandPlotCrossSectionfunctionality for structured grids)I think we can reduce this to two or three notebooks depending on how we want to present these classes and showcase this functionality:
Notebook 1) A map view plotting notebook that covers
PlotMapViewplotting that includes examples fromStructuredGrid,VertexGrid, andUnstructuredGridmodels. Also use a combination of MF6 and MF2005/USG models for this notebookNotebook 2) A cross sectional plotting notebook that covers
PlotCrossSectionplotting that includes examples fromStructuredGridandVertexGridNotebook 3) Maintain the current flopy3_PlotArrayExample notebook.
Are there any thoughts or other ways that make sense to structure these sets of notebooks?