Encyclopaedia Index

PHOENICS Scripts (i.e. Batch Files)

Contents


The scripts listed in the tables below are supplied with the PHOENICS installation.

They can be used from:

provided that the path has been set by issue of the command: /phoenics/d_utils/phoepath.bat, or an equivalent setting.

The command names for UNIX and LINUX installations are the same as those for windows.

The scripts are classified as PHOENICS Utilities, and are to be found in \phoenics\d_utils\d_win_32 for 32-bit installations, \phoenics\d_utils\d_win_64 for single-precision 64-bit installations and \phoenics\d_utils\d_windble for double-precision 64-bit installations. In the tables below, the folders are generically referred to as 'windf'.

Scripts for running executables

Table 1: The Environment module
Command  What executable is or  does
vre VR Editor serves as environment I

SATELLITE

The satellite executable can be run in several modes, namely:

The command sat followed by the appropriate one of the following parameters:
f, t, vre or vrv

suffices to launch the executable in the selected mode.

For the convenience of users, however, mode-specific commands are also provided.

The commands beginning run have been retained because users of earlier versions of PHOENICS may have become used to them.

Table 2: Satellite arguments
Command  What executable is or  does
sat SATELLITE: text-interactive
sil SATELLITE: silent
vre VR Editor
vrv VR Viewer
runsat same as sat
runvre same as vre
runvrv same as vrv

Table 3 : The EARTH (solver) and PHOTON (display) modules
Command  What it does
aut AUTOPLOT display module
ear public EARTH solver module
earpri private (local) EARTH solver module
pho PHOTON display module
runaut same as aut
runear same as ear
runpho same as pho
runpri same as earpri

Table 4: Scripts to build executables
Command  What it does
bldear builds EARTH executable
bldsat builds SATELLITE executable
bldsatx builds text-only SATELLITE

Table 5: Compilation scripts
Command  What it does
compile compiles a Fortran file


Information items

bldear

builds a solver-module executable, earexe.exe, in the local directory (also called a "private earth").

It uses whatever main.for and ground.for files exist in the local directory.

If one of these files does not exist, the "public" version of it is copied from /phoenics/d_earth.


bldsat

builds a SATELLITE executable, satexe.exe, in the local directory (also called a "private SATELLITE").

It uses whatever satlit.for file exists in the local directory.

If no such file exists, the "public" version of it is copied from /phoenics/d_satell.


The PLANT menu program is a stand-alone executable, residing in \phoenics\d_satell

It makes use of three ASCII files, residing in the same directory, namely: plntsttm, plntlist and plnthelp


RUNSAT

is a command which may be followed by arguments, with various consequences, as follows:

argument
consequence
none
whatever is implied by the top line of Q1, i.e.TALK = F or T, and whatever PIL commands then follow
F
reads Q1 (and Q2 if present), writes EARDAT (and XYZ and FACETDAT when required by commands in PIL); then quits, leaving the Q1 file unchanged.
T
reads Q1 (& Q2), then opens a text-mode interactive session.
VRE
reads Q1 (& Q2), then opens VR-Editor session.
VRV
reads Q1 (& Q2), then opens VR-Viewer session.
PC
(for Digital version only) opens PC Commander session

runvre

has the same effect as runsat vre


runvrv

has the same effect as runsat vrv