        Skeletal instructions for using the contents of this tar file
		(for defgb 4.4 et seq.  WJS.  Jun 2013)
	(includes info for v 4.3 on general principles)
	(includes info for v 4.2 since that version did not get wide release)
	(some 4.2 & 4.3 "this version" comments removed)

	Version 4.4 implements the identifymissingdata and 
coordinatedmissing data optional files.  Please see the param1.doc file
included in the release for a description of these features.

	Version 4.3j allows for an ISO8601 time output format
Details are in the param1.doc file included with this release.
	Version 4.3j checks that post-transvar variable names 
consist only of characters from the set of letters, numbers, and 
underscore, and that the names begin with a letter

	Version 4.3i fixes a bug that produced day max+2 (eg, May 33) 
if a gmt conversion caused a date rollforward across an end-of-month.

	Version 4.3h created mostly for code synchronization reasons.

	Version 4.3g fixes a bug that produced day 0 if a gmt conversion
caused a date rollforward across an end-of-month.

	Version 4.3f allows more control of leading and trailing blanks
in data fields.  It is incompatible with older releases in its treatment
of strings consisting entirely of blanks, in that in certain circumstances, 
older releases could return an empty string. 4.3f will not.
Details in the param1.doc file included with this release.

	Version 4.3e allows datacomments input from level 0 and
varlist files that happen not to have comments in them.

	Version 4.3d supports "new" format remote object names.
Please see the readme file for libupd 1.2.

	New features in 4.3c include more output time formats and the
ability to read/transform more than one set of latitude/longitude input.  
Details in the param1.doc file included with this release.

	Version 4.3b will not accept input objects with null levels.
Versions of outer after outer 3.0 will not generate such objects,
but there may be problems w/old outers.

	Version 4.3a was a maintenance-only release.

	Release 4.3 allows defgb to decode its arguments under
certain circumstances.  This allows it to receive more complicated
argument strings w/o worrying about shell & httpd "special characters".
However, existing argument strings that use special characters may no
longer work.  Details in the param1.doc file.

	Release 4.2 contains several bug fixes.  The majority of the
work, however, reflects a library reorganization and a new method
for building the JGOFS system.  These changes were enough to "earn"
a new .N release.


	The makefiles add the cc options -lm and -g to the
CC string set up in build-env.pl.  You may need/want to change these.

Files:
        By default, the defgb build procedure looks for outer in the
src/methods directory.  If the outer you wish to use is elsewhere,
please edit makefile.defgb appropriately. Similarly, the defgb build
looks for files that outer needs in src/methods and src/include.  If
they are not there, or not needed, please edit makefile.defgb
appropriately.


Incompatibilities with defgb 4.1 and older:
	If blanks are NOT data separator characters, data can consist
of strings all of whose characters are blank.  Old versions of defgb
might have reduced these strings to the empty string.  defgb now allows
user control, but in no circumstance will return the empty string.
	Objects with empty levels may no longer be input to defgb, since
they cause trouble.  Such objects typically are created via restrictive
selections.  outer v 3 will not produce such objects.
	Precision of some Julian output time/dates has changed
	Existing defgb non-data input strings that begin with a % 
may now not work.
	The make files for defgb 4.2 have been modified to assume the
existence of a src/include directory (containing "appropriate" files), and 
to assume that src/methods/outer.c has .brev functionality (which also
implies the existence of the required support files for that version of
outer)

Notes:

	1)  All files are text.

	2)  The "switch" documentation discusses compilation options.
The "param1" documentation discusses run-time options.  Some are duplicated,
so they can be set either way.
	    In particular, if your node does not have the JGOFS "jdb"
routines (or the http routines they call), you may need to set the
READ_OBJECTS compilation switch to FALSE.  The jdb routines are normally
found in the library file /jgofs_root/src/lib/jgofs.a. 

	3)  Documentation:
	There are presently no "user", "new feature", or "bug/incompatibilty"
documents-sorry.  Also, "JGOFS system" documentation is not present, and
familiarity with the JGOFS system is assumed.  Documentation more
related to data preparation for the system can be found at
http://usjgofs.whoi.edu/howtoputdata.html and 
http://globec.whoi.edu/globec-dir/data_org_ret.html
        User, new feature and some incompatibility information can be
found in the param1.doc file.  It is organized as a reference document,
but has some description that may be useful as a user document.  Incompat-
ibility information can be found at the end of the file.
        Incompatibility information can also be found at the end of the
defgb_switches.doc file.  The ultimate source of information about how things
have changed is the revision section of the code of each module.  Old revision
sections are in the defgb_revision.doc file.
	varlist.doc is a discussion of how JGOFS object variable lists get
made from strictly def-formatted input files and from more flexibly formatted
input files.
	comment_considerations.doc is a discussion about how defgb and other
pieces of the JGOFS system deal with commments.

	4)  Debugging suggestions:
a) The defgb_errs.txt file contains the text of various error messages.  Some
   messages have more information with them about what might cause the problem
   and/or which code module the message comes from. [Note: the contents of
   this file are not being kept up to date as of ~defgb v 4.  Sorry]
b) Try running the method interactively.  The parameters on the command
   line are the parameters from the .objects file (but not comma separated).
   To see the text of what the html code will be, set the last 5
   characters of the environment variable PATH_INFO to .html0 (the 0 is the 
   level to display).  You may need to quote some parameters on the command
   line that you do not need to quote in the .objects file.
c) If the method works interactively but dies when run by the httpd server
   (and jgofs program serv), check for file access problems due to the switch
   between "you" running the interactive program and whatever username is
   running the httpd server.  Scripts need the appropriate x access.  If
   you have no luck, try setting up an error sink (see diagnostics optional
   file info in the .doc file-an appropriate command in an indirect file might
   be		diagnostics = \ error_sink = defgb.err		)
d) It may be possible to help diagnose performance problems by doing a
   function call trace, since this output is time stamped (see diagnostics
   optional file info in the .doc file-an appropriate command in an indirect
   file might be
	diagnostics = \ debug_sink = defgb.debug; trace_level = 40	)
