| 1 |
|
|
| 2 |
|
\section{Input and Output Files} |
| 3 |
|
|
| 4 |
< |
\subsection{BASS and Model Files} |
| 4 |
> |
\subsection{{\sc bass} and Model Files} |
| 5 |
|
|
| 6 |
< |
Every OOPSE simuation begins with a BASS file. BASS |
| 6 |
> |
Every {\sc oopse} simuation begins with a {\sc bass} file. {\sc bass} |
| 7 |
|
(\underline{B}izarre \underline{A}tom \underline{S}imulation |
| 8 |
< |
\underline{S}yntax) is a script syntax that is parsed by OOPSE at |
| 9 |
< |
runtime. The BASS file allows for the user to completely describe the |
| 10 |
< |
system they are to simulate, as well as tailor OOPSE's behavior during |
| 11 |
< |
the simulation. BASS files are denoted with the extension |
| 8 |
> |
\underline{S}yntax) is a script syntax that is parsed by {\sc oopse} at |
| 9 |
> |
runtime. The {\sc bass} file allows for the user to completely describe the |
| 10 |
> |
system they are to simulate, as well as tailor {\sc oopse}'s behavior during |
| 11 |
> |
the simulation. {\sc bass} files are denoted with the extension |
| 12 |
|
\texttt{.bass}, an example file is shown in |
| 13 |
|
Fig.~\ref{fig:bassExample}. |
| 14 |
|
|
| 15 |
|
\begin{figure} |
| 16 |
|
|
| 17 |
|
\centering |
| 18 |
< |
\framebox[\linewidth]{\rule{0cm}{0.75\linewidth}I'm a BASS file!} |
| 18 |
> |
\framebox[\linewidth]{\rule{0cm}{0.75\linewidth}I'm a {\sc bass} file!} |
| 19 |
|
\caption{Here is an example \texttt{.bass} file} |
| 20 |
|
\label{fig:bassExample} |
| 21 |
|
\end{figure} |
| 22 |
|
|
| 23 |
|
Within the \texttt{.bass} file it is neccassary to provide a complete |
| 24 |
|
description of the molecule before it is actually placed in the |
| 25 |
< |
simulation. The BASS syntax was originally developed with this goal in |
| 25 |
> |
simulation. The {\sc bass} syntax was originally developed with this goal in |
| 26 |
|
mind, and allows for the specification of all the atoms in a molecular |
| 27 |
|
prototype, as well as any bonds, bends, or torsions. These |
| 28 |
|
descriptions can become lengthy for complex molecules, and it would be |
| 29 |
< |
inconvient to duplicate the simulation at the begining of each BASS |
| 30 |
< |
script. Addressing this issue BASS allows for the inclusion of model |
| 29 |
> |
inconvient to duplicate the simulation at the begining of each {\sc bass} |
| 30 |
> |
script. Addressing this issue {\sc bass} allows for the inclusion of model |
| 31 |
|
files at the top of a \texttt{.bass} file. These model files, denoted |
| 32 |
|
with the \texttt{.mdl} extension, allow the user to describe a |
| 33 |
|
molecular prototype once, then simply include it into each simulation |
| 42 |
|
files are simply the complete set of coordinates for each atom at a |
| 43 |
|
given simulation time. |
| 44 |
|
|
| 45 |
< |
There are three major files used by OOPSE written in the coordinate |
| 45 |
> |
There are three major files used by {\sc oopse} written in the coordinate |
| 46 |
|
format, they are as follows: the initialization file, the simulation |
| 47 |
|
trajectory file, and the final coordinates of the simulation. The |
| 48 |
< |
initialization file is neccassary for OOPSE to start the simulation |
| 48 |
> |
initialization file is neccassary for {\sc oopse} to start the simulation |
| 49 |
|
with the proper coordinates. It is typically denoted with the |
| 50 |
|
extension \texttt{.init}. The trajectory file is created at the |
| 51 |
|
beginning of the simulation, and is used to store snapshots of the |
| 65 |
|
|
| 66 |
|
As was stated in Sec.~\ref{subSec:coordFiles}, an initialization file |
| 67 |
|
is needed to provide the starting coordinates for a simulation. The |
| 68 |
< |
OOPSE package provides a program called \texttt{sysBuilder} to aid in |
| 69 |
< |
the creation of the \texttt{.init} file. \texttt{sysBuilder} is BASS |
| 68 |
> |
{\sc oopse} package provides a program called \texttt{sysBuilder} to aid in |
| 69 |
> |
the creation of the \texttt{.init} file. \texttt{sysBuilder} is {\sc bass} |
| 70 |
|
aware, and will recognize arguments and parameters in the |
| 71 |
|
\texttt{.bass} file that would otherwise be ignored by the |
| 72 |
|
simulation. The program itself is under contiunual development, and is |
| 74 |
|
|
| 75 |
|
\subsection{The Statistics File} |
| 76 |
|
|
| 77 |
< |
The last output file generated by OOPSE is the statistics file. This |
| 77 |
> |
The last output file generated by {\sc oopse} is the statistics file. This |
| 78 |
|
file records such statistical quantities as the instantaneous |
| 79 |
|
temperature, volume, pressure, etc. It is written out with the |
| 80 |
|
frequency specified in the \texttt{.bass} file. The file allows the |
