Initialization of GENSYS   

Search Path

The scripts in GENSYS are using an environment variable named $gensys, this variable must point to the directory where the GENSYS programs are installed. So before anything else can be defined in the .profile-file the user must add the following line in $HOME/.profile-file:

 #                                                                                   
 export gensys=<The complete address to the directory where GENSYS is installed>     
 #                                                                                   

The $PATH variable must be updated with the $gensys/scripts directory. In your file $HOME/.profile please add the following line:

 #                                                                                   
 PATH=$PATH:$gensys/scripts                                                          
 #                                                                                   

Environment variables

In GENSYS the user has the possibility to define a number of environment variables which controls the behavior of the program. Below is a list of environment variables which GENSYS uses:

gendir

Variable $gendir controls if GENSYS shall store all files in the same directory or if the results shall be moved into sub-directories. If $gendir not is defined will all files stay in one big directory. If the user sets gendir=yes by in the $HOME/.profile-file write:

 #                                                                                   
 export gendir=yes                                                                   
 #                                                                                   

All files will be moved into sub-directories. To which sub-directories the files will be moved depends on the file extension of the file. The names of the sub-directories are defined in the file $gensys/scripts/gen_defs. If the user wishes to have other names of the subdirectories it is possible if a local file with name .gen_defs is created. The local file .gen_defs has higher priority than $gensys/scripts/gen_defs.

genedit

In the environment variable $genedit the user can choose his/hers favorite editor. If not variable $genedit is defined the GENSYS standard NEDIT-editor will be used.

genghost

Environment variable $genghost controls which program shall be used in examination of postscript files. Default value for $genghost is "ghostview", but this require that the ghostview program is in the users PATH.

genhtml

Environment variable $genhtml controls which web-browser shall be used when reading the GENSYS manual pages. If variable $genhtml is undefined GENSYS will search for a web-browser in the following order: konqueror, firefox, mozilla and netscape.

genkpf

In the environment variable $genkpf the user has the possibility to in a easy way define the address to the directory where all wheel-rail geometry functions are stored.

gentrc

In the environment variable $gentrc the user has the possibility to in a easy way define the address to the directory where all track files are stored.

LPDEST

Defining the name of the default printer. On some systems this variable is named $PRINTER.

Example of a .profile-file.

Please copy the following lines to your $HOME/.profile-file

#                                                                                                               
#                                                                                                               
#      Defining environment variables for GENSYS                                                                
#                                                                                                               
#                                                                                                               
 export gensys=/opt/gensys/gensys.      ;# Define the address to program GENSYS                             
 export gendir=yes                          ;# Sort all GENSYS-files in subdirectories                          
#export genedit=/usr/X11R6/bin/nc           ;# Editor when editing files                                        
#export genghost=/usr/X11R6/bin/gv          ;# Ghostview for showing postscript files                           
#export genhtml=/usr/bin/netscape           ;# Web-browser for showing the manual pages                         
 export genkpf=$gensys/verif/kpf/kpfr       ;# Official directory for storing of wheel-rail geometry files      
 export gentrc=$gensys/verif/track/ver_data ;# Official directory for storing of track irregularities           
 export OCTAVE_PATH=$OCTAVE_PATH:$gensys/source/download/octave/m//                                             
                                                                                                                
 echo $PATH|grep $HOME/bin      > /dev/null || PATH=$PATH:$HOME/bin        ;# Add $HOME/bin to your path        
 echo $PATH|grep $gensys/script > /dev/null || PATH=$PATH:$gensys/scripts  ;# Add $gensys/scripts to your path  
                                                                                                                

Pre defined options for the programs in GENSYS

To the scripts in the GENSYS package a number of options can be given. Default values of the options can be stored in a file named .gen_conf. If not a local .gen_conf-file exists then the programs in GENSYS will look for a file named $HOME/.gen_conf. If not the $HOME/.gen_conf can be found the programs in GENSYS will read the file $gensys/scripts/gen_conf

Release numbers

The release number of the GENSYS package is a part of the name of the program, for example: gensys.. The reason for doing so is that several releases of GENSYS can be installed simultaneously, if different users wants to run different releases of GENSYS. Besides the release number for the whole GENSYS package each program has also its release number, in order to list the release numbers for each program the user has access to the List_iver-script in the $gensys-directory.

Check of printer

In order to test the environment variable LPDEST write "pri README.linux" in the $gensys-directory.