Minor revision

paper/paper.md

@@ -38,17 +38,16 @@ The implementation discussed in this paper is available in the public repository
 
 # Statement of Need
 
-Finite-element (FE) modeling is widely used to analyze PV reliability and durability, including failure mechanisms such as crack initiation and propagation in cells, glass, and encapsulation layers. In this context, mesh quality strongly affects simulation accuracy and solver convergence. Achieving durability targets for PV systems has been framed as an important research challenge by the Durable Module Materials consortium (DuraMAT) [@duramat].
-
-Existing workflows are often time-consuming for PV modules because: (1) module geometry is multilayered and thin, (2) different regions require different mesh resolutions, (3) commercial solvers rely on different mesh formats, and (4) geometry/mesh parametric sweeps are not always straightforward in GUI-first tools. Commercial FE ecosystems also differ in mesh import formats and sweep tooling, including ABAQUS [@manual2012abaqus], COMSOL [@manualcomsol62], and ANSYS [@manualansys2024]. PVMesh addresses these gaps by providing a PV-specific meshing workflow that is automated, flexible, and interoperable across major FE ecosystems.
+Achieving durability targets for PV systems has been framed as an important research challenge by the Durable Module Materials consortium (DuraMAT) [@duramat]. Finite-element (FE) modeling is widely used to analyze PV reliability and durability, including failure mechanisms such as crack initiation and propagation in cells, glass, and encapsulation layers. In this context, mesh quality strongly affects simulation accuracy and solver convergence. 
 
+Existing workflows are often time-consuming for PV modules because: (1) module geometry is multilayered and thin, (2) different regions require different mesh resolutions, (3) commercial FE ecosystems also differ in mesh import formats [@manual2012abaqus, @manualcomsol62, @manualansys2024], and (4) geometry/mesh parametric sweeps are not always straightforward in GUI-first tools. PVMesh addresses these gaps by providing a PV-specific meshing workflow that is automated, flexible, and interoperable across major FE ecosystems.
 
 
 # State of the Field                                                                                                                  
 
 PV FE studies commonly simplify module structure to reduce setup complexity, but these simplifications can reduce physical fidelity. Examples include spring-mass abstractions for panel aeroelastic response [@young2020fluid] and single-cell FE studies for thermal stress and delamination [@he2018finite; @bosco2020viscoelastic]. More detailed structural representations can materially affect analysis quality [@hartley2023analyzing].
 
-General-purpose meshing tools are powerful but not specialized for PV module conventions (cell arrays, layer partitioning, mounting regions, and solver-ready tagging). The multilayer panel structure and frame geometry that motivate this specialization are illustrated in the source material using prior PV structural references [@he2018finite; @deceglie2023whatscracking]. PVMesh contributes a domain-focused layer on top of Gmsh [@geuzaine2009gmsh] by combining:
+General-purpose meshing tools are powerful but not specialized for PV module conventions. The multilayer panel structure, cell arrays, layer partitioning, mounting regions, solver-ready tagging, and frame geometry that motivate this specialization are illustrated in the source material using prior PV structural references [@he2018finite; @deceglie2023whatscracking]. PVMesh contributes a domain-focused layer on top of Gmsh [@geuzaine2009gmsh] by combining:
 
 - PV-specific geometry parameterization.
 - Layer partitioning aligned to cell layout for improved mesh control.
@@ -77,7 +76,7 @@ To improve interoperability, exported meshes were validated in COMSOL, ANSYS, an
 
 # GUI Overview
 
-PVMesh provides a graphical user interface (GUI) to define geometry and meshing
+PVMesh provides a GUI to define geometry and meshing
 parameters without direct scripting. Users can configure layer dimensions,
 cell layout, mounting settings, and mesh controls, then generate one or more
 input cases for downstream mesh creation.
@@ -88,10 +87,11 @@ input cases for downstream mesh creation.
 
 # Examples
 
-The following examples summarize how meshes generated by PVMesh are used in three solver ecosystems.
+The following examples summarize how meshes generated by PVMesh are imported and verified in three solver ecosystems. To verify the imported mesh, a simple simulation was conducted in which all domains were assigned elastic material properties (
+$E = 100GPa, \nu = 0.3$). In these simulations, the displacements at the mounting areas were constrained, and a uniform pressure of $10MPa$ was applied to the top surface, excluding the surfaces of the frames. 
 
 1. **COMSOL workflow (`.bdf`)**  
-  A panel mesh generated in PVMesh is exported as `.bdf` and imported into COMSOL [@manualcomsol62]. After import, domain and boundary selections are used to assign layer-specific material properties and boundary conditions. A representative linear-elastic load case is then solved to evaluate displacement and stress fields.
+  A panel mesh generated in PVMesh is exported as `.bdf` and imported into COMSOL [@manualcomsol62]. After import, domain and boundary selections are used to assign layer-specific material properties and boundary conditions. The linear-elastic load case is then solved to evaluate displacement and stress fields.
 
 ![Figure 5: Mesh import window setting in COMSOL.](figures/figure5.png)
 
@@ -111,7 +111,7 @@ The following examples summarize how meshes generated by PVMesh are used in thre
 ![Figure 11: Simulated von Mises stress field from ANSYS.](figures/figure11.png)
 
 3. **FEniCSx workflow (`.msh`)**  
-  A mesh exported as `.msh` is loaded in FEniCSx via Gmsh-based readers [@geuzaine2009gmsh]. Physical groups generated by PVMesh are mapped to cell and facet tags, which are then used for material assignment and boundary-condition application in a variational finite-element formulation.
+  A mesh exported as `.msh` is loaded in FEniCSx via Gmsh-based readers [@geuzaine2009gmsh] and used for the simple elastic simulation. Physical groups generated by PVMesh are mapped to cell and facet tags, which are then used for material assignment and boundary-condition application in a variational finite-element formulation. 
 
 ![Figure 12: Simulated von Mises stress field from FEniCSx.](figures/figure12.png)
 
@@ -121,7 +121,7 @@ Across these examples, the same geometry definition and meshing inputs can be re
 
 # Research Impact Statement
 
-PVMesh lowers the barrier to creating high-quality PV FE meshes for reliability and structural studies. By automating repetitive setup steps and enabling batch mesh generation, it makes large parametric campaigns more practical.
+PVMesh lowers the barrier to creating high-quality PV FE meshes for PV reliability and durability studies. By automating repetitive setup steps and enabling batch mesh generation, it makes large parametric campaigns more practical.
 
 In verification workflows across COMSOL, ANSYS, and FEniCSx, meshes generated by PVMesh were successfully imported and used in representative elasticity simulations with consistent stress-field behavior. This cross-platform usability supports reproducible modeling pipelines and faster method transfer between research groups that use different solvers. The software artifact associated with this paper is the public repository [@pvmesh_repo].
 
@@ -230,4 +230,4 @@ Paper-to-repository bridge for reproducibility:
 - GUI workflow entry point in the repository is `pvmesh/guipytk.py`.
 - CLI mesh generation entry point in the repository is `pvmesh/mesh_generator.py`.
 - Default parameter set used by the tool is `original.txt`.
-- Environment specification for reproducing dependencies is `environment.yaml`. -->
+- Environment specification for reproducing dependencies is `environment.yaml`. -->