Buildbot ran the code beautifier.

doc/USER_MANUAL/02_getting_started.tex

@@ -166,7 +166,7 @@ \section{Using the GPU version of the code}
 
 For the runtime configuration, the \texttt{GPU\_MODE} flag must be set
 to \texttt{.true.}. In addition, we use three parameters to select the
-environments and GPU: 
+environments and GPU:
 \begin{verbatim}
 GPU_RUNTIME = 0|1|2
 GPU_PLATFORM = filter|*

doc/USER_MANUAL/03_running_the_mesher.tex

@@ -112,7 +112,7 @@ \chapter{Running the Mesher \texttt{xmeshfem3D}}\label{cha:Running-the-Mesher}
 17~s. Therefore, since accuracy is determined by the number of grid
 points per shortest wavelength, for any particular value of $\nexxi$
 the simulation will be accurate to a shortest period determined approximately
-by 
+by
 \begin{equation}
 \mbox{shortest period (s)}\simeq(256/\nexxi)\times17.\label{eq:shortest_period}
 \end{equation}

doc/USER_MANUAL/04_running_the_solver.tex

@@ -25,8 +25,8 @@ \chapter{Running the Solver \texttt{xspecfem3D}}\label{cha:Running-the-Solver}
 \item the multi-stage simulation parameters \texttt{NUMBER\_OF\_RUNS} and
 \texttt{NUMBER\_OF\_THIS\_RUN}
 \item the output information parameters \texttt{NTSTEP\_BETWEEN\_OUTPUT\_INFO},
-\texttt{NTSTEP\_BETWEEN\_OUTPUT\_SEISMOS}, \texttt{OUTPUT\_SEISMOS\_ASCII\_TEXT}, 
-\texttt{OUTPUT\_SEISMOS\_SAC\_ALPHANUM}, \texttt{OUTPUT\_SEISMOS\_SAC\_BINARY} 
+\texttt{NTSTEP\_BETWEEN\_OUTPUT\_SEISMOS}, \texttt{OUTPUT\_SEISMOS\_ASCII\_TEXT},
+\texttt{OUTPUT\_SEISMOS\_SAC\_ALPHANUM}, \texttt{OUTPUT\_SEISMOS\_SAC\_BINARY}
 and \texttt{ROTATE\_SEISMOGRAMS\_RT}
 \item the \texttt{RECEIVERS\_CAN\_BE\_BURIED} and \texttt{PRINT\_SOURCE\_TIME\_FUNCTION}
 flags
@@ -156,7 +156,7 @@ \chapter{Running the Solver \texttt{xspecfem3D}}\label{cha:Running-the-Solver}
 triangle is defined to be time zero. Note that this is NOT in general
 the hypocentral time, or the start time of the source (marked as tstart).
 The parameter \texttt{time shift} in the \texttt{CMTSOLUTION} file
-would be t1(=0), t2, t3 in this case, and the parameter \texttt{half duration} 
+would be t1(=0), t2, t3 in this case, and the parameter \texttt{half duration}
 would be hdur1, hdur2, hdur3 for the sources 1, 2, 3 respectively.}
 \label{fig:source_timing}
 \end{figure}
@@ -218,10 +218,10 @@ \chapter{Running the Solver \texttt{xspecfem3D}}\label{cha:Running-the-Solver}
 The \texttt{timestamp{*}} files provide the \texttt{Mean elapsed time
 per time step in seconds}, which may be used to assess performance
 on various machines (assuming you are the only user on a node), as
-well as the 
+well as the
 \texttt{Max norm displacement vector U in solid in all slices (m)}
 and
-\texttt{Max non-dimensional potential Ufluid in fluid in all slices}. 
+\texttt{Max non-dimensional potential Ufluid in fluid in all slices}.
 If something is wrong with the model, the mesh, or the source, you will see the
 code become unstable through exponentionally growing values of the
 displacement and/or fluid potential with time, and ultimately the

doc/USER_MANUAL/05_regional_simulations.tex

@@ -146,7 +146,7 @@ \section{One-Chunk Simulations}\label{sec:One-Chunk-Simulations}
 for all the details.
 
 The approximate shortest period at which a regional simulation is
-accurate may be determined based upon the relation 
+accurate may be determined based upon the relation
 \begin{equation}
 \mbox{shortest period (s)}\simeq(256/\nexxi)\times(\texttt{ANGULAR\_WIDTH\_XI\_IN\_DEGREES}/90)\times17.\label{eq:shortest_period_regional}\end{equation}
 

doc/USER_MANUAL/11_running_scheduler.tex

@@ -55,7 +55,7 @@ \section{\texttt{run\_lsf.bash}}
   queue="-q $1"
 fi
 # compile the mesher and the solver
-d=`date` 
+d=`date`
 echo"Starting compilation $d"
 
 make clean

doc/USER_MANUAL/12_changing_the_model.tex

@@ -85,7 +85,7 @@ \section{Changing the Crustal Model}\label{sec:Changing-the-Crustal}
 \begin{verbatim}
 ! the variables read are declared and stored in structure CM_V
   if(myrank == 0) call read_crust_model(CM_V)
-  
+
 ! broadcast the information read on the master to the nodes
   call MPI_BCAST(CM_V%thlr,NKEYS_CRUST*NLAYERS_CRUST,MPI_DOUBLE_PRECISION,0,MPI_COMM_WORLD,ier)
   call MPI_BCAST(CM_V%velocp,NKEYS_CRUST*NLAYERS_CRUST,MPI_DOUBLE_PRECISION,0,MPI_COMM_WORLD,ier)

doc/USER_MANUAL/13_post_processing.tex

@@ -54,7 +54,7 @@ \subsection{\texttt{process\_data.pl}}
 \end{verbatim}
 }
 
-\noindent 
+\noindent
 which has resampled the SAC files to a sampling rate of 1 seconds, cut them between 0 and 4000 seconds, transfered them into displacement
 records and filtered them between 40 and 500 seconds, picked the first P and S arrivals, and added suffix `\texttt{bp}' to the file names.
 

doc/USER_MANUAL/F_troubleshooting.tex

@@ -11,12 +11,12 @@ \section*{FAQ}
 Please make sure that you have a working installation of a Fortran compiler,
 a C compiler and an MPI implementation. You should be able to compile this
 little program code:
-   
-{\footnotesize   
-\begin{verbatim}   
+
+{\footnotesize
+\begin{verbatim}
   program main
   include 'mpif.h'
-  integer, parameter :: CUSTOM_MPI_TYPE = MPI_REAL 
+  integer, parameter :: CUSTOM_MPI_TYPE = MPI_REAL
   integer ier
   call MPI_INIT(ier)
   call MPI_BARRIER(MPI_COMM_WORLD,ier)
@@ -25,14 +25,14 @@ \section*{FAQ}
 \end{verbatim}
 }
 
-\item [compilation fails:] 
+\item [compilation fails:]
 In case a compilation error like the following occurs, stating
 
 {\footnotesize
 \begin{verbatim}
   ...
-  obj/meshfem3D.o: In function `MAIN__': 
-  meshfem3D.f90:(.text+0x14): undefined reference to `_gfortran_set_std' 
+  obj/meshfem3D.o: In function `MAIN__':
+  meshfem3D.f90:(.text+0x14): undefined reference to `_gfortran_set_std'
   ...
 \end{verbatim}
 }