bayes-an/listings Listings of papers received each month bayes-an/papers Submitted sources for the papers bayes-an/ps Generated postscript for the papersEach of these subdirectories is organized by year and month. So, for instance, the bayes-an/ps directory has subdirectories named "yymm" for each year (yy) and month (mm), within which are files named "yymmnnn.ps.Z" for each paper number bayes-an/yymmnnn.
Submitting a paper to bayes-an by anonymous FTP is a two-step process. First, place your paper (usually as a TeX file), figures, and any other files comprising the submission on xxx.lanl.gov in the directory "incoming/", as follows:
@ ftp xxx.lanl.gov
Name: anonymous
Password:
ftp> cd incoming
ftp> put mypaper.tex
ftp> put myfigs.uu
Second, send an email command
To: bayes-an@xxx.lanl.gov
Subject: fput ...
The body format of the `fput' and `freplace'
commands is identical to that of the`put' and `replace' commands. In particular,
there are three sections, delimited by \\ lines. The third section, which would have been the body of the paper in a `put' or `replace' submission, is optional. It can be a description of file(s) that have been placed in the incoming ftp directory, and is retained only for submissions that are determined (on the basis of file extension) to contain "non-ascii" components.
.Z Standard Unix compress
.gz GNU's gzip compression
.tar.Z Compressed tar archive
.tar.gz gzip'ed tar archive
.tex TeX
.sty LaTeX style files
.dvi DVI file
.ps PostScript
.ps.Z Compressed PostScript
.eps Encapuslated PostScript
.uu Uuencoded files
.jpg JPEG graphics
.mpg MPEG animations
.hqx Macintosh bin-hexed files (not recommended)
.bbl latex bibliographic files
.txt,.asc plain ASCII text
Users should be sure to use the Unix format when naming files (e.g.,
VMS extensions like .tar_Z should not be used). Your ftp program
should allow you to specify a remote file name different from your
local one.Filename extensions are somewhat important since, when used properly and consistently, they give an indication of how the files should be treated when they are sent out through e-mail. Files that can be automatically wrapped to 80 characters per line (called `ascii' files here) have the suffixes .tex, .txt, .asc, .uu, .hqx, .sty, and .bbl. All other files are considered to be `binary' and not safe for e-mailing. If a submission contains files which are all `ascii', then a `get' request will mail back each of the files separately, along with the description of the files included in the body section of the `fput' e-mail message (i.e., the text located after the third set of backslashes). For other submissions, the `get' command will only return the body section describing the files, which can then be retrieved using ftp.
Although there is considerable flexibility in how you choose to put the various files that make up your paper onto the archive, there are important issues to consider. For instance, one of the most common situations is a TeX paper with some number of figures in (Encapsulated) PostScript. You have the choice of putting the paper and all of the figures as separate .tex and .(e)ps files, or you can choose to pack up some or all of the files into a .tar.Z package. For someone retrieving your paper *by e-mail*, it might be preferable to retrieve only one or two files, hence the .tar.Z option is more desirable. Also, by using the .tar.Z approach, you can be sure that the files are unpacked with the correct names, without the reader having to worry about such details.
When using ftp to put files into the incoming directory, you should do an `ls' to list the files already there, and be sure to use names for your files that don't clash with ones already there. Generic file names like `paper.tex' or `fig1.eps' should be avoided since it is more likely that someone else would also use this name. Pick unique names. File names should also be short to keep the subject line of the `fput' message short.