commit b5d0a6673b9b75c1e526416f9231829376c5846f
parent 416a7dff6229ec75331137ba09e48a85904c0f56
Author: Vincent Forest <vincent.forest@meso-star.com>
Date: Wed, 4 Oct 2017 14:28:06 +0200
Fix some misspellings
Diffstat:
2 files changed, 27 insertions(+), 24 deletions(-)
diff --git a/solstice-resources.html.in b/solstice-resources.html.in
@@ -54,9 +54,9 @@ systems, the provided sources can be compiled by any C compiler that supports
the C99 standard.</p>
<pre class="code">
-$ wget www.meso-star.com/solstice/downloads/Solstice-PP-Sources.tar.gz
$ tar xzvf Solstice-PP-Sources.tar.gz
-$ make -C Solstice-PP-Sources
+$ cd Solstice-PP-Sources
+$ make
</pre>
<p>A description of each generated tools is given in the following
@@ -67,12 +67,12 @@ sections.</p>
<p>The <code>solppraw</code> program reads the Solstice outputs from a file or
the standard input whether a filename is provided as an argument or not,
respectively. For each simulated sun direction, it formats the raw results in a
-human readable text file, simplifying the analysis of the simulation results.
+human readable text file, simplifying the analysis of the results.
</p>
-<p>The following command lines invoke Solstice to simulate two sun directions
-and write the results in the <code>output</code> file that is then
-post-processed by the <code>solppraw</code> tool.</p>
+<p>The following example invokes Solstice to simulate two sun directions and
+write the results in the <code>output</code> file that is then post-processed
+by the <code>solppraw</code> tool.</p>
<pre class="code">
$ solstice -D45,70:50,75 -R rcvs.yaml -o output input.yaml
@@ -97,7 +97,7 @@ when it is invoked with the <code>-p</code> option. The radiative paths are red
from a file or from the standard input, whether a filename is provided as an
argument or not, respectively. For each simulated sun direction, it generates a
<a
-HREF="http://www.vtk.org/wp-content/uploads/2015/04/file-formats.pdf">VTK</a>
+href="http://www.vtk.org/wp-content/uploads/2015/04/file-formats.pdf">VTK</a>
file of the radiative paths that can be then visualized in <a
href="https://www.paraview.org">Paraview</a>.</p>
@@ -113,19 +113,22 @@ Writing `50-75-paths.vtk'
<h3>solpp</h3>
-<p>The <code>solpp</code> program reads the geometry of a solar plant
-generated by the <code>-g</code> option of Solstice, and the results of a
-legacy Solstice simulation. For each simulated sun direction, it writes three
-files. The first one, is a VTK file that maps to the meshes of the primary
-geometries (i.e. the reflectors) their associated simulation results; for
-instance their respective cosine factor or the amount of flux that reaches a
-receiver and comes from them. The second output file, is another VTK file that
-stores the geometry of the receivers and their simulation results as its
-incoming flux or its efficiency. Finally, the third written file is an <a
-HREF="http://www.martinreddy.net/gfx/3d/OBJ.spec">OBJ</a> that stores the
-meshes of the miscellaneous geometries, i.e. the geometries that are neither
-receivers nor primary geometries. These files can then be visualised and
-analyse into Paraview.</p>
+<p>The <code>solpp</code> program takes two input files: the geometry of a
+solar plant output by Solstice when it is invoked with the <code>-g</code>
+option, and the results of a legacy Solstice simulation. For each simulated sun
+direction, it writes three files. The first one, is a
+<a
+href="http://www.vtk.org/wp-content/uploads/2015/04/file-formats.pdf">VTK</a>
+file that maps to the
+meshes of the primary geometries (i.e. the reflectors) their associated
+simulation results; for instance their respective cosine factor or the amount
+of flux that reaches a receiver and comes from them. The second output file,
+is another VTK file that stores the geometry of the receivers and their
+simulation results as their incoming flux or their efficiency. Finally, the third
+file is an <a HREF="http://www.martinreddy.net/gfx/3d/OBJ.spec">OBJ</a> file
+that stores the meshes of the miscellaneous geometries, i.e. the geometries
+that are neither receivers nor primary geometries. These files can then be
+visualised and analysed in <a href="https://www.paraview.org">Paraview</a>.</p>
<p>In the following example, <code>solstice</code> is invoked to simulate two
sun directions on the solar plant described in the <code>input.yaml</code>
diff --git a/solstice.html.in b/solstice.html.in
@@ -130,7 +130,7 @@ $ echo "source ~/Solstice-${VERSION}-GNU-Linux64/etc/solstice.profile" >> ~/.bas
<code>share/man</code> sub-directory of Solstice. To consult it, browse the
HTML files stored in the <code>share/man/man1</code> and
<code>share/man/man5</code> directories. On GNU/Linux, you can alternatively
-use the <code>man</code> command-line to read its ROFF VERSION.</p>
+use the <code>man</code> command-line to read its ROFF version.</p>
<pre class="code">
$ man solstice
@@ -139,6 +139,6 @@ $ man solstice-output
$ man solstice-receiver
</pre>
-<p>The Solstice <a href="solstice-resources.html#ABG">beginner's guide</a>
-gives fundamentals of Solstice, starting from simple examples to more complex
-ones.</p>
+<p>Refer to the <a href="solstice-resources.html#ABG">Absolute Beginner's
+Guide</a> to learn fundamentals of Solstice; it relies on practical examples to
+introduce the functionalities of the program.</p>
