5/15/06
	This is a description of the IDL code in the
	AtHome/kraken/data.raw/visualization directory.

	NOTE: except for a few rare exceptions I'll be making all the
	code *.pl. This was after running I can look at some of the
	internal variables.

--- Older stuff -------------------------------------------------------
tvb.pl: 
	older code.  Reads from *.tgz files and tvscl's the 
	data.  With the larger data sets I'm now using this
	code is impractical.

	ncpu = 5 is hardcoded into it as well.

wb.pl:
	older code.  Hardwired to handle only ncpu = 5.  
	True, it is faster then the general code with
	ncpu = 5, but much less versitile and not
	worth keeping up to date.

rb.pl:
	older code.  Hardwired to handle ncpu = 5.  Reads
	the files created by wb.pl.  So, basically, 
	wb.pl and rb.pl split the tasks of tvb.pl in half, 
	dumping the long wait time into memory usage.

pare.pl: 
	older code.  First attempt to pare down the input,
	but with ncpu = 5 hardwired in.

NOTE:	The reason for the paring code is 2 fold.  
	1. To make the data set smaller and thus, more manageable
	   Also, and I'm not certain ATM, but I think this can
	   kinda sorta take the place of factx, factz for normal
	   use
	2. It was necessary.  Once I started running with a 
	   large number of points IDL could no longer allocate
	   an array large enough to hold it all.
	3. wren63 is the first successful pare run.  Be aware
	   that the value of parex/parez may not be what you intend,
	   which is why the code prints it out.  Though, from 
	   now on I'll be running with the pare code so it shouldn't
	   be too much of an issue.

--- Newer stuff -------------------------------------------------------
runspecs.pro:
	This contains all the run specific data, such as
	ntim, nnxp, factx, parez, etc.  

write.pl:
	This routine requires editing before execution.  You need to
	change the number of times to loop and you need to specify
	which runs and variable you want to right out as IDL files
	for tv.pl to read.

	write.pl can handle any ncpu value under 1000 and, provided
	you pick parex, parez well, any values of nnxp, nnzp, and 
	ntim.  HOWEVER, the code assumes you had non-periodic bndy
	conditions and so nnzp MUST be odd, usually something like
	201 (NZ = 200, IBZ = 1 in codein)

	The files are written to the /data.byt directory in the
	data.raw/<specific_run> directory.  You need to create this
	directory before running write.pl.  LIES!  I learned how 
	to make the directory from the program now, so you don't have to
	worry about it.  AND, if you happen to make the dir and run 
	the code, it'll give you an error on the mkdir command but won't
	bomb the program.
 
	Also, the write code now assumes a parex, parez parameter.  This
	is defaulted to '1' in the runspecs.pro file.  I fixed the way 
	the paring was done; the loops are now i = 0, nnxp-1, PAREX
	instead of i = 0, nnxp-1, 1.  Consequently, shit runs faster.

tv.pl:
	This general code reads from the output files created by
	write.pl and tvscls the data based on user supplied inputs.

	Gonna try and edit it to utilize a zoom feature maybe.

pro.pl:
	plots a slice of the data

mean.pl:
	plots the data in the .mean2 file