Skip to content

Commit

Permalink
Some sp mistakes
Browse files Browse the repository at this point in the history
  • Loading branch information
marchdf committed Oct 4, 2023
1 parent 59ee795 commit fbc92ea
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions Docs/sphinx/CvodeInPP.rst
Original file line number Diff line number Diff line change
Expand Up @@ -445,7 +445,7 @@ ReactEval_C example with a subset of the various available CVODE linear solvers.
+-------------------------------+-----------------+----------------+-------------+----------------+-----------------+


The same series of tests are performed for a mixture of n-dodecane and air (see :ref:`sec:subsReactEvalCvode`), the configuration being otherwise the same as in the methane/air case. Results are sumarized in Table :numref:`tab:RunsReactEvalCvodeDOD`. The overall tendencies remain similar. Note that the non-preconditioned GMRES solver becomes very inefficient for this larger system. Here also, the direct sparse solve --which relies upon the KLU library, does not seem to provide additional time savings. The fill-in pattern is :math:`70 \%`.
The same series of tests are performed for a mixture of n-dodecane and air (see :ref:`sec:subsReactEvalCvode`), the configuration being otherwise the same as in the methane/air case. Results are summarized in Table :numref:`tab:RunsReactEvalCvodeDOD`. The overall tendencies remain similar. Note that the non-preconditioned GMRES solver becomes very inefficient for this larger system. Here also, the direct sparse solve --which relies upon the KLU library, does not seem to provide additional time savings. The fill-in pattern is :math:`70 \%`.

.. _tab:RunsReactEvalCvodeDOD:

Expand Down Expand Up @@ -663,7 +663,7 @@ The input file
The Results
^^^^^^^^^^^

Results are sumarized in Table :numref:`tab:RunsReactEvalCvodeDRMGPU`.
Results are summarized in Table :numref:`tab:RunsReactEvalCvodeDRMGPU`.


.. _tab:RunsReactEvalCvodeDRMGPU:
Expand Down
2 changes: 1 addition & 1 deletion Docs/sphinx/Utility.rst
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ This code has two runtime parameters that may be set in the input file: ::
pmf.datafile = pmf.dat
pmf.do_cellAverage = 1

The first parameter specifies the path to the PMF data file. This file contains a two-line header followed by whitespace-delimited data columns in the order: position (cm), temperature (K), velocity (cm/s), density(g/cm3), species mole fractions. Sample files are provided in the relevant PeleLMeX (and PeleC) examples, and the procedure to generate these files with a provided script is described below. The second parameter specifies whether the PMF code does a finite volume-style integral over the querried cell (``pmf.do_cellAverage = 1``) or whether the code finds an interpolated value at the midpoint of the querried cell (``pmf.do_cellAverage = 0``)
The first parameter specifies the path to the PMF data file. This file contains a two-line header followed by whitespace-delimited data columns in the order: position (cm), temperature (K), velocity (cm/s), density(g/cm3), species mole fractions. Sample files are provided in the relevant PeleLMeX (and PeleC) examples, and the procedure to generate these files with a provided script is described below. The second parameter specifies whether the PMF code does a finite volume-style integral over the queried cell (``pmf.do_cellAverage = 1``) or whether the code finds an interpolated value at the midpoint of the querried cell (``pmf.do_cellAverage = 0``)

Generating a PMF file
~~~~~~~~~~~~~~~~~~~~~
Expand Down

0 comments on commit fbc92ea

Please sign in to comment.