1% $Id$ 2 3\documentstyle[fullpage,12pt,fleqn]{article} 4\setlength{\parskip}{6pt} 5 6\begin{document} 7 8\begin{center} 9{\bf\Large NWCHEM Distribution Information} 10\end{center} 11 12\section{Automatic Builds at PNNL} 13Currently the automatic builds are run via cron jobs and work for the 14most part unless someone has checked in code that really doesn't 15work. The scripts simply build the code and do not do any regression on 16the binary they produce. These scripts always keep older versions of 17the NWChem binaries. We have started the development of some QA 18procedures and I will incorporate a subset of this QA to into the 19automatic builds so that we can have some small assurance that the new 20binary will work as planned. Automatic builds are produced on a 21revolving schedule on various machines at PNNL. The schedule 22information will eventually be a web page on the internal EMSL site 23but for now it is kept in a file located at:\\ 24/msrc/proj/nwchem/build\_readme 25 26\subsection{AFS aware systems} 27 28The AFS @sys technology is used to distinguish between operating 29systems and the specific tags are used to distinguish between systems 30with the same operating system and different characteristics. For 31example, IRIX 6.x runs on indigo's, origins, etc. nwchem.R4.4k and 32nwchem.R10k exist in the same IRIX 6.x @sys directory. 33 34These machines have binaries located in three directories: 35\begin{itemize} 36\item The default release binary for general use is in :{\tt 37/msrc/proj/nwchem/bin}. This directory is updated by hand when deemed 38necessary. 39\item The release tree build (usually weekly) is in:{\tt /msrc/proj/nwchem/binr} 40\item The development tree build (usually twice a week) is in:{\tt /msrc/proj/nwchem/bind} 41\end{itemize} 42 43I will eventually move this to DFS but I cannot get DFS credentials in 44a cron job yet. 45 46\subsection{On NWMPP1} 47On NWMPP1 there is a user account ``nwchem'' where the automatic 48builds 49 50\section{Off-site} 51\subsection{Current Procedure} 52Rick does it with each site. 53\subsection{Future} 54I want to put in place the technology that requires the user to fill 55out a form and then he will get the user agreement in the US mail. 56Once he returns the user agreement we send him to a page where he will 57bring up his registration information and enter a password of sorts 58and get to a page where he can down-load the binaries that are 59available. 60 61A similar mechanism could be used to distribute the tar file of the 62current release version of NWChem. 63 64\end{document} 65 66