[GRASS-SVN] r72089 - in grass-addons/grass7/raster: r.hants r.series.lwr

[svn_grass at osgeo.org]

Author: veroandreo
Date: 2018-01-16 10:43:17 -0800 (Tue, 16 Jan 2018)
New Revision: 72089

Modified:
   grass-addons/grass7/raster/r.hants/r.hants.html
   grass-addons/grass7/raster/r.series.lwr/r.series.lwr.html
Log:
r.hants & r.series.lwr manuals: fix -z and file option descriptions, sync with r.series (trunk 72081)

Modified: grass-addons/grass7/raster/r.hants/r.hants.html
===================================================================
--- grass-addons/grass7/raster/r.hants/r.hants.html	2018-01-16 18:27:16 UTC (rev 72088)
+++ grass-addons/grass7/raster/r.hants/r.hants.html	2018-01-16 18:43:17 UTC (rev 72089)
@@ -84,11 +84,11 @@
 
 <p>
 The maximum number of raster maps that can be processed is given by the 
-per-user limit of the operating system. For example, the soft limits 
+user-specific limit of the operating system. For example, the soft limits 
 for users are typically 1024. The soft limit can be changed with e.g. 
 <tt>ulimit -n 4096</tt> (UNIX-based operating systems) but it cannot be 
-higher than the hard limit. If it is too low, you can as superuser add an 
-entry in
+higher than the hard limit. If the latter is too low, you can as superuser
+add an entry in:
 
 <div class="code"><pre>
 /etc/security/limits.conf
@@ -96,7 +96,7 @@
 your_username  hard    nofile          4096
 </pre></div>
 
-This would raise the hard limit to 4096 files. Also have a look at the 
+This will raise the hard limit to 4096 files. Also have a look at the 
 overall limit of the operating system
 <div class="code"><pre>
 cat /proc/sys/fs/file-max
@@ -104,15 +104,17 @@
 which on modern Linux systems is several 100,000 files.
 
 <p>
-Use the <em>file</em> option to analyze large amount of raster maps 
-without hitting open files limit and the size limit of command line 
-arguments. The computation is slower than with the <em>input</em> option 
-method. For every single row in the output map(s) all input maps are 
-opened and closed. The amount of RAM will rise linearly with the number of 
-specified input maps. The input and file options are mutually exclusive.
-The option <em>input</em> is a comma separated list of raster map names 
-and the option <em>file</em> is a text file with a new line separated 
-list of raster map names. Note that the order of maps in one option or 
+Use the <b>-z</b> flag to analyze large amounts of raster maps without
+hitting open files limit and the <em>file</em> option to avoid hitting
+the size limit of command line arguments.
+Note that the computation using the <em>file</em> option is slower than
+with the <em>input</em> option.
+For every single row in the output map(s) all input maps are opened and
+closed. The amount of RAM will rise linearly with the number of 
+specified input maps. The <em>input</em> and <em>file</em> options are
+mutually exclusive: the former is a comma separated list of raster map
+names and the latter is a text file with a new line separated list of
+raster map names. Note that the order of maps in one option or 
 the other is very important.
 
 <h2>EXAMPLES</h2>

Modified: grass-addons/grass7/raster/r.series.lwr/r.series.lwr.html
===================================================================
--- grass-addons/grass7/raster/r.series.lwr/r.series.lwr.html	2018-01-16 18:27:16 UTC (rev 72088)
+++ grass-addons/grass7/raster/r.series.lwr/r.series.lwr.html	2018-01-16 18:43:17 UTC (rev 72089)
@@ -89,11 +89,11 @@
 
 <p>
 The maximum number of raster maps that can be processed is given by the 
-per-user limit of the operating system. For example, the soft limits 
+user-specific limit of the operating system. For example, the soft limits 
 for users are typically 1024. The soft limit can be changed with e.g. 
 <tt>ulimit -n 4096</tt> (UNIX-based operating systems) but it cannot be 
-higher than the hard limit. If it is too low, the user can, as superuser, 
-add an entry in
+higher than the hard limit. If the latter is too low, you can as superuser
+add an entry in:
 
 <div class="code"><pre>
 /etc/security/limits.conf
@@ -101,7 +101,7 @@
 your_username  hard    nofile          4096
 </pre></div>
 
-This would raise the hard limit to 4096 files. Also, have a look at the 
+This will raise the hard limit to 4096 files. Also have a look at the 
 overall limit of the operating system
 <div class="code"><pre>
 cat /proc/sys/fs/file-max
@@ -109,17 +109,19 @@
 which on modern Linux systems is several 100,000 files.
 
 <p>
-Use the <em>-z</em> flag to analyze large amounts of raster maps 
-without hitting the open files limit and the size limit of command line 
-arguments. This will however increase the processing time. For every 
-single row in the output map(s) all input maps are opened and closed. 
-The amount of RAM used will rise linearly with the number of specified 
-input maps.
+Use the <b>-z</b> flag to analyze large amounts of raster maps without
+hitting open files limit and the <em>file</em> option to avoid hitting
+the size limit of command line arguments.
+Note that the computation using the <em>file</em> option is slower than
+with the <em>input</em> option.
+For every single row in the output map(s) all input maps are opened and
+closed. The amount of RAM will rise linearly with the number of 
+specified input maps. The <em>input</em> and <em>file</em> options are
+mutually exclusive: the former is a comma separated list of raster map
+names and the latter is a text file with a new line separated list of
+raster map names. Note that the order of maps in one option or 
+the other is very important.
 
-<p>
-The input and file options are mutually exclusive. Input is a 
-text file with a new line separated list of raster map names.
-
 <h2>EXAMPLES</h2>
 
 We use a time series of the Chlorophyll-a concentration level 3 product