Electronic abstract package file 1: README % README -- APS electronic abstract package distribution.

Thanks for your interest in preparing and submitting your APS meeting abstracts electronically. This directory contains all the files in the distribution. They are described briefly immediately below. Following the file descriptions are short installation instructions, the generic recipe for printing the user guide and samples, and information about who to contact regarding the distribution. The abstract files are prepared using the syntax of a text processing system called LaTeX, and each individual item is identified by its own command (or piece of markup) in the LaTeX language. These items are described in detail in the apsabins.txt file.

The meeting code for this meeting is DPF96.

README
apsabins.txt
Instructions for using this package and for submitting abstracts. We recommend printing this file to make it easier to follow the directions exactly. This is a plain ASCII text file - it needs no text processing.

apsabfrm.tex
The abstract template - fill in and email to the APS Office. Completion of the template requires only an ASCII file text editor. However, to view or print it will require LaTeX on your system. Complete instructions are contained within the form as comment lines. apsab.sty Fully documented LaTeX input style file for the APS abstract substyle. Contains macro definitions and comments. This file is not required unless you want to print or view your abstract; it is not necessary to print the abstract before submitting it electronically.

USING ANONYMOUS FTP
If you are reading this guide on paper and would like to have the electronic abstract materials, you can retrieve the package yourself using a form of file transfer on the Internet known as "anonymous FTP". Following are the steps you use to get the package.
ftp aps.org
Username: anonymous
Password: ftp> cd pub/meetings/abstracts
ftp> get README
ftp> get apsab.sty
ftp> get apsabfrm.tex
ftp> get apsabins.txt
ftp> get apsDPF96.txt
ftp> bye

INSTALLING THE STYLE FILES
If you want to print out your abstract, the apsab.sty file must be "installed" so that LaTeX can read it. This simply means that the apsab.sty file must be placed either in (1) the working directory containing the paper being processed [single-user installation], or (2) in the TeX/LaTeX system input directory [site-wide installation]. Individuals who obtain the files for their personal use should just put the files in the same directory that they usually use when preparing papers, memos, etc. with LaTeX. Sites that expect several authors to use the package will probably find it preferable to install the files in the standard TeX inputs area. In the parlances of popular operating systems, these areas are typically called /usr/local/lib/tex/inputs Unix and variants C:\EMTEX\TEXINPUT MS-DOS and Windows SOME$DISK:[TEX.INPUTS] VMS/Files-11 specification The user's guide and sample papers could be kept in a system-wide TeX input directory as well.

ADMINISTRATIVE DETAILS
The package has been prepared by Chris Biemesderfer of ferberts associates, in conjunction with the Headquarters Information Services and Meetings Department staff at the APS Office.

Comments, suggestions, etc., can be sent electronically to the APS office: abs-help@aps.org Community input will be evaluated and the evolution of the package will be coordinated with the BAPS editor and publisher.

15 Oct 1994 revised 19 May 1995
REVISION HISTORY v1.0,
Oct 94 Original version written, based on aasab.v16. v1.1
Apr 95 Added support for various "footnoting" options: \thanks, \altaffil, \altaffilmark, \altaffiltext, \titlenote. Changed \SortCategory to explicitly delimit subcategories up to a depth of 4: \SortCategory{} -> \SortCategory{}{}{}{}. Added \DPPType{} so that DPP papers can also be categorized as "theoretical" or "experimental". Increased \parindent on first abstract (title) line to .6in to improve chances that session identifiers can be pasted in. The LaTeX style file now also works under LaTeX2e.

Electronic Abstracts: General Information

NOTE: The abstract package has been revised as of May 19, 1995. Earlier versions are not compatible.

Thank you for your interest in submitting your abstract electronically for APS Meetings. The following is general information on how to obtain the proper files to submit your abstract and what you will receive as a benefit for participating. Submitting electronically has several advantages over mailing a paper abstract of which you should be aware.

You will receive a primary acknowledgement that we have received your abstract within 24 hours of sending it; a secondary message will include a log number to help reference your abstract if you should have any questions or problems (withdrawals, changes, etc.) and a final message, which will include your session and paper number assignment, to help you make your travel plans.
Additionally, your abstract, in its entirety, will be included in the on-line version of the BAPS, which typically is available to members several weeks prior to the printed one. Those submitting on paper will only have their paper title and authors listed in the on-line version of the BAPS.

IF YOU ARE SUBMITTING VIA E-MAIL, PLEASE DO NOT SEND A DUPLICATE PAPER COPY TO THE APS MEETINGS DEPARTMENT.

The rules for submitting electronically are similar to the paper submissions. A member must submit the paper, it must meet the length requirements, and arrive by the deadline. Please consult any issue of APS Meeting News for this information. You can obtain the files for preparing and submitting your abstract either via e-mail or ftp. In either case, you will need to know the "Meeting ID" code for the meeting you are submitting to. The Meeting ID is critical because it will ensure that you receive the sorting categories for the appropriate meeting.

The "Meeting ID" code for this meeting is DPF96.

If you wish to obtain the author package via e-mail, you will need to send a message to "abs-request@aps.org" and include in the text of the message "request-DPF96". To obtain the files via ftp, use the following steps:
ftp aps.org
Username: anonymous
Password:
ftp> cd pub/meetings/abstracts
ftp> get README
ftp> get apsab.sty ftp> get apsabfrm.tex
ftp> get apsabins.txt
ftp> get apsDPF96.txt
ftp> bye

The files that you will receive are as follows:

README.txt
General Information. Approximately 4K.

apsabins.txt
Instructions for using the files and submitting abstracts. This is a plain ASCII text file and we recommend that you print this file to make it easier to refer to. Approximately 15K.

apsabfrm.tex
The abstract template. It includes brief instructions on how to fill in the template and e-mail back to the appropriate address. Completion of this file requires only an ASCII file text editor. However, if you wish to view or print it will require LaTeX on your system. Approximately 5K.

apsab.sty
LaTeX input style file for the APS abstract substyle. Contains macro definitions and comments. This file is not required unless you want to print or view your abstract, which is not necessary for you to e-mail it. THIS FILE SHOULD NOT BE ALTERED IN ANY WAY. Approximately 11K.

apsDPF96.txt
This file includes meeting specific sorting categories for use in the template. It changes with each meeting, every year. Approximately 2K. The template is supported by LaTeX commands. However, it is not necessary to submit in LaTeX if you are not including any math or special symbols in the abstract. The template will accept ASCII text. If you are not able to view the abstract with a LaTeX viewer, make certain that the title, author list, abstract body and footnotes do not total more than 1300 characters, including spaces.

For additional information on abstract submissions, please consult APS Meeting News. If you have questions, send them to abs-help@aps.org.