\documentclass[10pt,letterpaper, final]{report} % \documentclass{} required in all files

\usepackage{../preamble/myWEPS} % This is now our single preamble file inclusion (it assumes a “.sty” file extension)

\usepackage{grffile}

\begin{document}

These exercises are designed to provide the user with step-by-step examples of some common 
tasks performed with the Wind Erosion Prediction System (WEPS) model. These exercises cover many topics, including basic model operation, file management, and building and editing field management rotations within the Management/Crop Rotation Editor of WEPS (MCREW). The focus of the exercises should be on learning to use WEPS for conservation planning. 

The training scenarios use a variety of locations in the United States, as well as various crops, with the intention of building the users’ proficiency to apply WEPS in many regions for different crops. Therefore, new users are encouraged to complete all the exercises regardless of location and crop in the scenario. Since WEPS is continually being improved and its parameters modified, the results you get may not exactly match those reported in the exercises. This is to be expected.

As the WEPS model finishes a given run, it may sometimes display a \textbf{warning message}
that one or more of the crops simulated did not reach maturity prior to harvest (\cref{fig:WEPS_Crop_Maturity_Warning_Messages}).
This is not uncommon, especially for crops that are harvested before reaching maturity such as forage crops.
However, this can also often occur if the user has selected a management template
developed for a significantly different climatic zone than the location it is being used in.
Since WEPS after harvest residue results are dependent upon crop yields, which often influence the wind erosion simulation results,
it provides a quick check for the user that has not properly vetted his management rotation file
for the conditions and location he is using it in.

If such a message is obtained, click “OK” to complete the run.
If most of the year’s crops reach about 95$\%$ maturity the run is OK to use.
However, if many of the years are reporting crops with a value less than 95$\%$,
check to make sure planting and harvesting dates for the crop are as expected for the location being simulated.
If it still does not reach 95$\%$, NRCS users contact the Natural Resources Conservation Service (NRCS)
Database Manager or NRCS Wind Erosion Specialist.
All other users should submit a Mantis ticket with a copy of the WEPS Run attached and a note about what the issue is.
The user should always attempt to resolve such maturity issues for crops that are harvested prior to reaching maturity,
if those crops are normally expected to reach maturity prior to harvest.

\begin{figure}[H]
\centering
	\includegraphics[scale=1.65]{images/Conservation_Planning/Crop_Maturity_Message.jpg}
\caption{WEPS Warning Messages Generated window displaying warning messages about crop not reaching maturity.}
\label{fig:WEPS_Crop_Maturity_Warning_Messages}
\end{figure}


\section{Definitions and Considerations} \label{sec:Definitions and Considerations}

\subsection{Projects and Runs} \label{subsec:Projects and Runs}

A \textbf{WEPS Project} is a directory that can be thought of as a working area where WEPS simulation runs are created. The standard location for the Project.wpj is C:$\backslash$Users$\backslash$user.name$\backslash$Documents$\backslash$My WEPS Files$\backslash$Project.wpj, where user.name refers to the user’s login name on the computer. This default location applies to NRCS Field Office configured versions of WEPS running Windows 7. Other WEPS configurations and operating systems may vary as to the location of this directory. The Project directory stores all the parameters and files for the current simulation run being prepared within the WEPS interface, as well as any files used in the past for previous runs. For example, the Project will contain soils .ifc files and management .man files. The users should make it a habit to “clean out” those files when they are no longer needed. This is done by clicking the File menu on the main interface and selecting the appropriate delete functions.

A WEPS Run refers to a single simulation of a field with all associated input and output files. Each run is stored in a separate folder or subdirectory which by default is located under the current WEPS run directory. It is located at C:$\backslash$user.name$\backslash$Documents$\backslash$My WEPS Files$\backslash$Runs. Again, this default location applies to NRCS Field Office configured versions of WEPS running Microsoft Windows 7. Other WEPS configurations and operating systems may vary as to the location of this directory. A WEPS run subdirectory stores a copy of all input files used to make the simulation run, together with the output files generated from those inputs. Thus, one is able to recall the identical WEPS run at a later date (and get the same outputs when using the same version of WEPS 1.5 and the weather generators/databases) because the original input files are still available. Typically, “re-running” a previous run is not necessary since the outputs are stored in the Run directory and can be reviewed via the “ViewOutput” menu options. However, if additional outputs not generated with the original run are desired, it will be necessary to load the previous run and re-run it using the desired output options. 

The Run directories make it relatively easy to archive or remove WEPS runs as alternative erosion planning scenarios are tested for a field or farm. For example, if a change is made to create a different management alternative, all the information pertaining to this new scenario will be saved to a new subdirectory under a new WEPS Run name, when the simulation is made. These Run directory files can also be sent to another location using the “Export Run” option under the “File” or “Project” menu on the main interface.


\subsection{Naming WEPS Files} \label{subsec:Naming WEPS Files}

Naming of all runs and files in WEPS should be considered carefully. Management or run names should be long enough to uniquely describe them but not so long so that the name is difficult to view in file chooser windows. Some special characters are not allowed in file or directory names used in WEPS. Known characters not allowed or recommended include: @ ? $`$ $\vert$ \& ${>}$ ${<}$ $/$ $\backslash$ $\sim$ : * "


\subsection{WEPS Templates} \label{subsec:WEPS Templates}

A \textbf{Template} is a pre-built management rotation file operation file or crop file. \textbf{Management templates} are accessible through the Management Template folder. For NRCS configured versions of WEPS running Microsoft Windows 7, they are located here: 


\centerline{\textit{C:$\backslash$Program Data$\backslash$USDA$\backslash$WEPS$\backslash$Databases$\backslash$nrcs$\backslash$man}}


Other WEPS configurations and operating systems may vary as to the location of this directory.

User-made \textbf{Management templates} are accessible through the Management Template folder.
For NRCS configured versions of WEPS running Microsoft Windows 7, they are located here:
\vspace{3mm}


\centerline{\textit{C:$\backslash$Program Data$\backslash$USDA$\backslash$WEPS$\backslash$Databases$\backslash$nrcs$\backslash$man$\backslash$local}}



Other WEPS configurations and operating systems may vary as to the location of this directory.

User-made \textbf{Crop templates} are accessible through the Crop Template folder. For NRCS 
configured versions of WEPS running Microsoft Windows 7, they are located here:
\vspace{3mm}


\centerline{\textit{C:$\backslash$Program Data$\backslash$USDA$\backslash$WEPS$\backslash$Databases$\backslash$nrcs$\backslash$crops$\backslash$local}}


Other WEPS configurations and operating systems may vary as to the location of this directory.

User-made \textbf{Operation templates} are accessible through the Operation Template folder. For NRCS configured versions of WEPS running Microsoft Windows 7, they are located here:
\vspace{3mm}

\centerline{\textit{C:$\backslash$Program Data$\backslash$USDA$\backslash$WEPS$\backslash$Databases$\backslash$nrcs$\backslash$operations$\backslash$local}}


Other WEPS configurations and operating systems may vary as to the location of this directory.

These can be crops, operations or managements saved locally by users with a Biomass Adjustment Factor determined for their location and climatic conditions. It is very helpful to save a calibrated local management file to a place where all users in a work group can have access to it. The location for the local management files can be moved to a shared server location by selecting “Edit Configuration” option under the “Tools” menu on the main WEPS screen, then selecting the “Directories” tab and editing the appropriate field titled: “Management Template Open” and “Management Template Save” (\cref{fig:WEPS_Configuration_window_opened_to_the_Directories_tab}).

\begin{figure}[H]
\centering
	\includegraphics[scale=1.65]{images/Conservation_Planning/WEPS_Config_directories.jpg}
\caption{WEPS Configuration window opened to the Directories tab, showing directory locations which the user may change.}
\label{fig:WEPS_Configuration_window_opened_to_the_Directories_tab}
\end{figure}

In  \cref{fig:WEPS_Configuration_window_opened_to_the_Directories_tab}, the bright yellow folders {\scalerel*{\includegraphics{images/icons/folder.png}}{\strut} indicate those directory paths which the user can change, while the shaded folders {\scalerel*{\includegraphics{images/icons/foldergray.png}}{\strut} show those the user cannot change. To change a location, click the yellow folder, select the directory or file, and click OK to save the configuration settings and close the window. \hl{Note:} The database locations shown in (\cref{fig:WEPS_Configuration_window_opened_to_the_Directories_tab}) are different for the official NRCS WEPS 1.5 release.

Soil files are accessible through the Soil folder. For NRCS configured versions of WEPS running Microsoft Windows 7, they are located here:
\vspace{3mm}

\centerline{\textit{C:$\backslash$Program Data$\backslash$USDA$\backslash$WEPS$\backslash$Databases$\backslash$nrcs$\backslash$soil}}


Other WEPS configurations and operating systems may vary as to the location of this directory.

One set of soil files will usually be placed on a shared drive in an NRCS Field Office. Users must “map to” that drive to access the common group of soils. This can be done accessing the Configuration panel through the “Tools” menu on the main interface and selecting “Edit Configuration”. The user must then select the “Soil” tab and edit the “Soils Database” field. If the user needs to run the model separate from the server, the common soils directory can be reset to the local machine and the necessary soil files downloaded to that location.


Soil files may also be obtained directly from the National Soil Survey Center in Lincoln, NE by using the Soils pull down and selecting NRCS Soil Data Mart function. Users must have an Internet connection to use this function. 


\subsection{Simulation Region Orientations and Angles} \label{subsec:Simulation Region Orientations and Angles}

Field orientation and direction of tillage within the simulation region in WEPS are independent and measured relative to true North (0 degrees). Angles are important in WEPS because wind directions are simulated to mimic the historic wind direction distribution for the selected location. Since wind direction varies from day to day, erosion losses will also vary relative to field angle or ridge orientation. The field orientation in WEPS should be rotated to represent the actual orientation on the landscape. Note that the field will only rotate in a range of ±45 degrees. By rotating and adjusting the field length and width, the user should be able to obtain the desired size and orientation for a field. Tillage direction should also be entered relative to true North in the Management Crop Rotation Editor (MCREW). For example, if a rectangular field has its long side oriented 20.0 degrees from true North and tillage is performed parallel to that long side of the field, the tillage direction should also be entered as 20.0 degrees within MCREW.

\subsection{Plant Damage} \label{subsec:Plant Damage}

Although soil loss is the primary concern in wind erosion, damage to plants should also be considered.
Crops can be damaged by blowing soil particles, exposure of plant roots, burial of plants by drifting soil,
or desiccation and twisting of plants by the wind.
In two exercises, we will examine and take into account the crop tolerance to blowing soil,
even though the erosion estimate may already be within NRCS guidelines.
NRCS has published a table listing the tolerance of various crops to blowing soil
(USDA-NRCS, 2000; National Agronomy Manual; Table 502-4, pg. 502-19).
Refer to this table as needed during the exercises (Table \ref{table:Crop_Tolerance}).
Crops can tolerate greater amounts of blowing soil than shown,
but yield and quality may be adversely affected.


\begin{table}[H]
\centering
\begin{tabular}{|l|l|l|l|}
\hline
\textbf{Tolerant*}	& \textbf{Moderate}	& \textbf{Low Tolerance}	& \textbf{Very Low}\\
\textbf{"T"}	 	& \textbf{(2 t/ac)}	& \textbf{(1 t/ac)}			& \textbf{(0-0.5 t/ac)}\\
\hline
\hline
Barley& Alfalfa (mature)& Broccoli& Alfalfa (seedlings)\\
Buckwheat& Corn& Cabbage& Asparagus\\
Flax& Onions ($>$ 30 days)& Cotton& Cantaloupe\\
Grain Sorghum& Orchard Crops& Cucumbers& Carrots\\
Millet& Soybeans& Garlic& Celery\\
Oats& Sunflowers& Green/Snap Beans& Eggplant\\
Rye& Sweet Corn& Lima Beans& Flowers\\
Wheat&   & Peanuts& Kiwi Fruit\\
&   &  Peas& Lettuce\\
&   &  Potatoes& Muskmelons\\
&   &  Sweet Potatoes& Onion (seedlings)\\ 
&   &  Tobacco& Peppers\\
&   &  &        Spinach \\
&   &  &        Squash\\
&   &  &        Strawberries\\
&   &  &        Sugar Beets\\
&   &  &        Table Beets\\ 
&   &  &        Tomatoes\\ 
&   &  &        Watermelons\\ 
\hline
\end{tabular}
\caption{Crop tolerances used by Natural Resource Conservation Service (NRCS) to design wind erosion control methods (USDA-NRCS, 2000). *Crop tolerance is defined as the maximum wind erosion that a growing crop can tolerate, from crop emergence to field stabilization, without an economic loss to stand, yield, or quality.}
\label{table:Crop_Tolerance}
\end{table}

\begin{itemize}

\item{\textbf{References} --
USDA-NRCS. 2011. National Agronomy Manual, Part 502-Wind Erosion, 190-V NAM. 4th 
Edition. Washington, D. C.}


\end{itemize} 

\end{document}