*
                                       EBOP

                                 Eclipsing Binary

                                    Light-Curve

                                     Solution

                                      Program

                                        for

                            The IBM PC (or compatible)
                                 (with 8087 chip)

                                        by

                                   Paul B. Etzel

                                       SDSU

                                    24-May-1987

         ___________________
         *
              This note, and the computer program distributed with it are
         pre-release versions of the currently supported program EBOP15.
         No copies of either the documentation or especially the computer
         program are to be made and circulated.  Such actions will hamper
         the future distribution of the fully enhanced (and supported)
         version of EBOP16. 

                                 TABLE OF CONTENTS

         I.     Introduction                                    1

         II.    Files and File Names                            2

         III.   Commands and Incantations                       2

         IV.    The easy way                                    4

         V.     Inventory                                       4

         VI.    Installation                                    5

                                                                     page 1

         I.  INTRODUCTION

              EBOP (pre-release version 16) has been transferred to the IBM
         PC from the IBM 3033.  This transfer was made possible by using
         the "mainframe compatible" IBM "Professional FORTRAN" compiler.
         The conversion process was simplified by retaining the "batch
         mode" of processing rather than rewriting the program to be
         "interactive".  Thus, you supply input file names through the
         keyboard when running the computer programs rather than input
         data.  All input files are either prepared in advance with a text
         editor or transferred from another computer.  Output is normally
         sent directly to the printer, but can be sent (space permitting)
         to a disk file for examination, possible printing, and later
         deletion.  The use of disk files for output is better suited for
         PCs with hard disks since the usual "small" output file for a
         single solution will be about 60K bytes.

              On a PC with dual-floppy disk drives, I suggest that the
         program disk (containing DOS and EBOP16.EXE) reside in drive A:,
         and the data disk (parameter files and light-curve data files).
         reside in B:. If the PC has a hard-disk drive, put all EBOP
         related files into a subdirectory (e.g., C:\EBOP).

         II.  FILES AND FILE NAMES

              Input is separated into two files.  Each light curve is put
         into a "light-curve file".  The light-curve file may be used with
         WINK (when it becomes available).  The "parameter file" contains
         EBOP specific information: header record, initial parameter
         records, and solution control record.

              Light-curve and parameter file names should be chosen by some
         systematic convention to aid in their identification when
         examining the disk directory (the DOS "DIR" command).  DOS limits
         the lengths of file names to 8 characters, and an optional
         extension to 3 characters (not counting the preceding decimal).
         Thus, for binary stars with multiple light-curve files I suggest
         names like:

                BSDRAVN.DAT
         where,
                BSDRA           identifies the star name (BS Dra),
                V               denotes the filter identification,
                N               specifies normal points,
         and
                .DAT            is an optional file name extension.

         For light curves of the same object and filter, you may wish to
         use the extension to identify different seasons or observers.

                AGPERB.74       and     AGPERB.77
                MYCYGB.DMP      and     MYCYGB.WIL

         would be good examples.   

                                                                     page 2

              Similarly, a convention should be adopted for the parameter
         files.  A light-curve file can be used with either EBOP or WINK,
         but a parameter file is program specific.  I prefer to use the
         extension to identify the program with which it is associated.
         Thus,

                CDTAUBN.EBO

         would contain parameters for EBOP, and

                CDTAUBN.WIN

         for WINK.  Presumably, both are associated with the same light-
         curve file.  There can be variations such as

                BSDRAVN.EBF

         which contains "special" parameter records (i.e., format-statement
         option included).

              More than one solution on a light curve may be included in a
         single parameter file (see BSDRAVN.EBO for example).  Consult the
         formal documentation on EBOP for further descriptions of the input
         data formats and solution methods.  You can gain some familiarity
         with the structure of the parameter files by examining their
         contents with the "safe" batch command

                A>LOOK d:filename.ext

         (the arbitrary file "filename.ext" is on disk drive "d:").  You
         may also print the contents of a file with the DOS command

                A>PRINT d:filename.ext

         which is fully described in the DOS manual.

         III.  COMMANDS AND INCANTATIONS

              Just in case you need to know, here is a description of the
         equivalences between files/devices and FORTRAN unit numbers.  Skip
         this paragraph if you could care less about the anatomy of DOS
         commands, but come back if things don't work!  The parameter file
         is equated to input from the PC console keyboard (unit 5) with the
         DOS redirection-of-input character "<" which points "toward" a
         program.  The light-curve file is equated to the dummy default
         file FORT8 (unit 8) with the DOS "SET" command.  The "SET" command
         is also used to re-SET FORT8 to a null file (an important point!).
         The output, normally sent to the console screen (unit 6), is
         either sent directly to the printer (device) or to disk (file)
         with the DOS redirection-of-output character ">" which points
         "away" from a program. 

                                                                     page 3

              Assume that you have a PC with dual-floppy drives with an
         EBOP program disk (with DOS installed) in drive A:, and a data
         disk in drive B: (see sec. VI).  Boot with Ctrl-Alt-Del.  You are
         then ready to run a light-curve solution.

              A typical sequence of commands to run EBOP is:

                1)      A>SET FORT8=                            {ex. 1}
                2)      A>SET FORT8=B:CDTAUBN.DAT
                3)      A>EBOP16 < B:CDTAUBN.EBO > PRN
                4)      A>SET FORT8=

         where: 1) and 4) re-SETs FORT8 to null, 2) SETs the equivalence
         between the dummy file named FORT8 and the light-curve file
         B:CDTAUBN.DAT, and 3) directs the parameter file B:CDTAUBN.EBO to
         be used as system input, and the device PRN (system printer) to be
         used as system output.  PLEASE notice, there is no space allowed
         between the "FORT8" and "=" on any of the SET lines!  (The DOS
         "SET" command is much easier to use than the IBM 3033 OS/MVT
         counterpart - the infamous //GO.blah-blah-blah CARD).

              If desired, you could send output to a disk file instead of
         the printer for later examination on the screen (or printing).
         In this case, line 3) could then be something like

                3)      A>EBOP16 < B:CDTAUBN.EBO > B:PRINT1     {ex. 2}

         where B:PRINT1 is an arbitrary name of the file on drive B: to
         contain the printed output.

                If you are using a printer capable of printing 132 columns
         across standard 15-inch wide paper, then you can prefix the above
         commands with the DOS command

                A>MODE LPT1:80,6

         (if not already in effect).  If, however, you are using an Epson
         FX-80 (or compatible) dot matrix printer that only accepts 9-inch
         wide paper, then you must prefix the command sequence with

                A>MODE LPT1:132,6 (or ,8 if you want really tiny letters)

         to squeeze all 132 columns onto the page.  

                                                                     page 4

         IV.  THE EASY WAY

              The batch file (RUNEBOP.BAT) automatically enters the
         required DOS commands, and checks the supplied file names for
         validity.  Batch commands temendously simplify your efforts to run
         the computer programs.  The command sequence is: (1) run-program
         command, (2) light-curve file name, (3) parameter file name, and
         (4) output file/device name.  If no output file name (4) is
         supplied, or the three characters "PRN" are entered, the output
         goes directly to the printer.  Otherwise, a file is created on the
         default drive with the supplied output file name.

             Thus, our two previous examples (sec. III, p. 3) simplify to:

                A>RUNEBOP CDTAUBN.DAT CDTAUBN.EBO               {ex. 1}
         and
                A>RUNEBOP CDTAUBN.DAT CDTAUBN.EBO PRINT1        {ex. 2}

              You may wish to modify the EBOP batch file (RUNEBOP.BAT) to
         suit your own purposes.  For example, you may want to make drive
         B: the default for all data files for a PC with dual-floppy disk
         drives.  If a hard disk is available, usually drive C:, you may
         want to make it the default drive for input and/or output files.

         V.  INVENTORY

              The EBOP distribution disk includes various types of files.
         The files EBOP16.EXE and RUNEBOP.BAT are used to actually run the
         EBOP code.  The following auxiliary files:

                AUTOEXEC.BAT    CONFIG.SYS      LOOK.BAT

         are used in association with the DOS environment.  The file

                EBOP.DOC

         is this note.  To get a printed copy of this note, simply use the
         DOS PRINT command (e.g., PRINT d:EBOP.DOC).  I assume that you have
         a copy of the formal EBOP documentation.

              The EBOP distribution disk also contains the following light-
         curve files:

                BSDRAVN.DAT     CDTAUBN.DAT
                NEL_DAV.DAT <== (three spherical test cases)         

                                                                     page 5

         and their associated parameter files:

                BSDRAVN.EBO     BSDRAVN.EBF     CDTAUBN.EBO
                NEL_DAV.EBO

         which may be used for testing.

              The actual FORTRAN source file (EBOP16.FOR) is included on
         the distribution disk for the sake of completeness.  If necessary,
         you could recompile the program to recreate the executable (.EXE)
         file.  You may even transfer the source file (e.g., via KERMIT) to
         another computer for use.

         VI.  INSTALLATION

              The following DOS files must be present on your system disk
         for EBOP to operate:

                COMMAND.COM     ANSI.SYS        MODE.COM        PRINT.COM
                MORE.COM

         If you have a PC with dual-floppy drives, FORMAT a disk with
         the "/S" switch, then copy the above DOS files onto it.  Copy
         onto this disk the contents of the EBOP distribution disk.
         If you have a PC with a hard-disk drive, make a directory named
         EBOP (e.g., MKDIR \EBOP).  Then copy the contents of the EBOP
         distribution disk into this directory.  In addition, you must:
         1) change the AUTOEXEC.BAT file in the hard disk's root directory
         to contain the appropriate lines from the version supplied with
         the distribution disk, and 2) change the CONFIG.SYS file in your
         root directory to incorporate the lines from the version supplied
         with the distribution disk.

                                                        Paul B. Etzel
                                                        SDSU