environment variable

CMake/ctest_script.cmake

@@ -2,7 +2,7 @@
 # Usage:  ctest -s script,build
 #   build = debug / optimized / valgrind / coverage
 # Note: this test will use use the number of processors defined in the variable N_PROCS,
-#   the environmental variables
+#   the environment variables
 #   N_PROCS, or the number of processors available (if not specified)
 #   N_PROCS_BUILD, or N_PROCS (if not specified)
 #   N_CONCURRENT_TESTS, or N_PROCS (if not specified)

README.md

@@ -21,9 +21,9 @@
  extensive use of toolchains, but the system has since been updated to
  eliminate the use of toolchain files for most cases.  The build
  system works with GNU, Intel, and IBM XLC compilers.  Specific compile options
- can be specified either through specific environmental or CMake
+ can be specified either through specific environment or CMake
  variables.  When the libraries are installed in standard locations,
- e.g., /usr, /usr/local, there is no need to set environmental or cmake
+ e.g., /usr, /usr/local, there is no need to set environment or cmake
  variables for the packages.
 
  See the manual in manual/qmcpack_manual.pdf for build examples on Linux, Mac OS X etc.
@@ -65,9 +65,9 @@ make -j 8
 
 ## Set the environment
 
- A number of environmental variables affect the build.  In particular
+ A number of environment variables affect the build.  In particular
  they can control the default paths for libraries, the default
- compilers, etc.  The list of environmental variables is given below:
+ compilers, etc.  The list of environment variables is given below:
 
 | Environment variable | Description |
 |----------------------|-------------|
@@ -81,10 +81,10 @@ make -j 8
 
 ## CMake options
 
- In addition to reading the environmental variables, CMake provides a
+ In addition to reading the environment variables, CMake provides a
  number of optional variables that can be set to control the build and
  configure steps.  When passed to CMake, these variables will take
- precident over the environmental and default variables.  To set them
+ precident over the environment and default variables.  To set them
  add -D FLAG=VALUE to the configure line between the cmake command and
  the path to the source directory.
 
@@ -176,7 +176,7 @@ make -j 8
 
 It is recommended to create a helper script that contains the
 configure line for CMake.  This is particularly useful when using
-environmental variables, packages are installed in custom locations,
+environment variables, packages are installed in custom locations,
 or the configure line may be long or complex.  In this case it is
 recommended to add "rm -rf CMake*" before the configure line to remove
 existing CMake configure files to ensure a fresh configure each time

manual/installation.tex

@@ -130,9 +130,9 @@ Previously QMCPACK made extensive use of toolchains, but the build system
 has since been updated to eliminate the use of toolchain files for
 most cases.  The build system is verified to work with GNU, Intel, and IBM XLC
 compilers.  Specific compile options can be specified either through
-specific environmental or CMake variables.  When the libraries are
+specific environment or CMake variables.  When the libraries are
 installed in standard locations, e.g., /usr, /usr/local, there is no
-need to set environmental or cmake variables for the packages.
+need to set environment or cmake variables for the packages.
 
 \subsection{Quick build instructions (try first)}
 \label{sec:cmakequick}
@@ -176,9 +176,9 @@ give examples for a number of common systems in Section \ref{sec:installexamples
 
 \subsection{Environment variables}
 \label{sec:envvar}
-A number of environmental variables affect the build.  In particular
+A number of environment variables affect the build.  In particular
 they can control the default paths for libraries, the default
-compilers, etc.  The list of environmental variables is given below:
+compilers, etc.  The list of environment variables is given below:
 \verbatimfont{\footnotesize}%
 \begin{verbatim}
 CXX              C++ compiler
@@ -192,10 +192,10 @@ FFTW_HOME        Path for FFTW
 
 \subsection{Configuration options}
 \label{sec:cmakeoptions}
-In addition to reading the environmental variables, CMake provides a
+In addition to reading the environment variables, CMake provides a
 number of optional variables that can be set to control the build and
 configure steps.  When passed to CMake, these variables will take
-precedent over the environmental and default variables.  To set them
+precedent over the environment and default variables.  To set them
 add -D FLAG=VALUE to the configure line between the cmake command and
 the path to the source directory.
 
@@ -374,7 +374,7 @@ make -j 8
 \subsection{Build scripts}
 It is recommended to create a helper script that contains the
 configure line for CMake.  This is particularly useful when avoiding
-environmental variables, packages are installed in custom locations,
+environment variables, packages are installed in custom locations,
 or if the configure line is long or complex.  In this case it is also
 recommended to add "rm -rf CMake*" before the configure line to remove
 existing CMake configure files to ensure a fresh configure each time

manual/running.tex

@@ -65,7 +65,7 @@ ranks as the number of GPUs per node in order to let each MPI rank take one GPU.
 Modern processors integrate multiple identical cores even with hardware threads
 on a single die to increase the total performance and maintain a reasonable
 power draw. QMCPACK takes advantage of all that compute capability on a
-processor by using threads via OpenMP programming model as well as threaded linear algebra libraries. By default, QMCPACK is always built with OpenMP enabled. When launching calculations, users should instruct QMCPACK to create the right number of threads per MPI rank by specifying environmental variable OMP\_NUM\_THREADS. Even in the GPU accelerated version, using threads significantly reduces the time spent on the calculations performed by the CPU.
+processor by using threads via OpenMP programming model as well as threaded linear algebra libraries. By default, QMCPACK is always built with OpenMP enabled. When launching calculations, users should instruct QMCPACK to create the right number of threads per MPI rank by specifying environment variable OMP\_NUM\_THREADS. Even in the GPU accelerated version, using threads significantly reduces the time spent on the calculations performed by the CPU.
 
 \subsubsection{Performance consideration}
 \label{sec:cpu:performance}