diff -r 000000000000 -r 5fda18b64dcb README.previous
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/README.previous	Wed Sep 26 17:50:53 2007 -0400
@@ -0,0 +1,89 @@
+The Fractal Realizer (FR) code was originally developed under DEC Fortran
+under ULTRIX (Yeah, incredible, huh?).
+
+I have updated the Makefile to work well with the Portland Group Fortran
+77 compiler under RedHat 7.2 Linux.
+
+Since this is a research code, I assume that users have some facility
+with compilation and Makefiles.  The FR code consists of a visualization
+portion, written in C, and the FR model itself, written in Fortran.
+The Fortran portion is a subroutine called by the main C program.
+The visualization portion is based on the XPM extension to X windows
+(http://koala.ilog.fr/lehors/xpm.html),
+written by Arnaud Le Hors.  The XPM extension is already present in
+(almost) all recent versions of operating systems which include X windows,
+so it is not necessary to get anything new.
+
+When using non-Portland compilers, change pgf77 in the Makefile to
+whatever your installation may have.  Since the C piece is main, many
+Fortran compilers need to be given a "nomain" switch, or they get very
+confused.  Since the syntax for this switch varies among compilers, you
+may have to look up the equivalent switch for your particular compiler.
+Since we use a lot of common blocks, a switch to align these on common
+boundaries is helpful also.
+
+Another typical cross-language problem is the number and placement of
+underscores in the names.  Some compilers want "_MAIN_", while others
+want "_MAIN" or other variants.  Since there is no universal solution,
+you may have to mess with these names manually.
+
+Function prototyping may be a problem, but shouldn't be if you use an
+ANSI-compatible C compiler.  We have included a local strdup function,
+but that shouldn't be a problem either.
+
+It should be possible to get g77 to work, but I have not pursued this.
+If you get g77 to work, or modify the Makefile to get other compilers to
+work, please let me know (hnw@fire.esd.ornl.gov) so that I can incorporate
+your improvements back into this distribution.
+
+If you don't understand any of the above, don't worry -- you probably
+don't have to.  JUST TRY IT AND IT WILL PROBABLY WORK.
+
+
+Say "make depend"  and then "make fast"  to get an FR executable called
+"realizer"
+
+If you modify or do further development, you may wish to say "make debug"
+or "make profile" to get debug and profile versions of the executable,
+respectively.  This is not necessary to run the present version.
+
+Then try it out with any of the included script files (*.scr) like this:
+
+./realizer < whatever.scr
+
+When the FR runs, it writes an input script called input.scr, so if you
+just want to change one or a few things, you can rename and edit input.scr
+and rerun it easily.  The order and nature of the question prompts asked
+by the FR are answer-driven and input-dependent, so larger manual changes
+to input.scr may not work -- rerun ./realizer without redirected input
+and answer new questions to regenerate a correct input.scr.
+
+After the FR runs, it makes two output files called landscape.xpm and
+ties.xpm
+
+You can use the XPM utility sxpm, available on most systems, to view these
+(xv will also work).
+
+sxpm landscape.xpm
+
+The FR program uses a heap sort to sort the entire map to find the
+highest probability sites, so execution time will increase rapidly as
+the size of the map is increased.  Execution time also increases with
+increasing numbers of categories in the map.  Because of the midpoint
+displacement algorithm for generating (pseudo)fractals, the maps must be
+square, with sides of (2**n)+1.  However, the use of constraint masks
+will permit oddly-shaped and smaller synthetic maps to be generated
+while still preserving both p and the fractal dimension of each category.
+
+We hope that the FR will prove useful (or at least stimulating) to you.
+Please be sure to cite our Conservation Ecology paper in all work stemming
+from the use of the FR, and be sure to let us know of any improvements
+or suggestions that you may have ...
+
+     ____                             Oak Ridge National Laboratory
+      /  )      /  /      /  /        P.O. Box 2008, M.S. 6407
+     /--<   o  /  /      /--/         Oak Ridge, TN  37830-6407
+    /___/__<__/__/_     /  / _        (865) 241-2748
+   William W. Hargrove                (865) 574-4665 (fax)
+   FedEx/UPS, use "Bethel Valley Rd." http://research.esd.ornl.gov
+   hnw@fire.esd.ornl.gov              http://research.esd.ornl.gov/~hnw