module load feko/7.0-n058
OR
module load feko/7.0-n059

Please include the following in the pbs script:

mkdir $HOME/.feko/7.0
FEKO_USER_HOME  $HOME/.feko/7.0 
#This is not needed: source  /sw/feko/7.0.2/bin/initfeko

FEKO is installed on node n058 and n059.
An example of a PBS script if using node n058 is:

>>>>>>>>>>>>>>>>>
#!/bin/bash
#PBS -N FEKO
#PBS -m abe
#PBS -M yourEmailID@griffithuni.edu.au
#PBS -l select=1:ncpus=2:mem=14gb:host=n058 -l walltime=100:00:00
module load feko/7.0-n058
source $HOME/.bashrc
echo "Starting job: "
mkdir -p $HOME/.feko/7.0
export FEKO_USER_HOME=$HOME/.feko/7.0
cd $FEKO_USER_HOME
feko /sw/feko/n058/examples/GetStarted_models/Project1-Rectangular_Horn_Antenna/Horn.fek
>>>>>>>>>>>>>>>>>>>

gunzip -c feko_distrib_7.0.2_xxx.tar.gz | tar -xf -
cd feko_install
sh ./INSTALL.SH



>>>>>>>>>>
 
Checking installation of parallel FEKO version.
  For a parallel installation of FEKO on multiple nodes in the following
  a command is required to run utilities on the other nodes, or in some
  cases also to copy files from this node to the other remote nodes (if
  no network file system is used). You can choose either the traditional
  rsh/rcp commands (remsh under HP-UX), or the secure shell ssh/scp. The
  one selected should already have been setup and should be working, but
  this will also be checked later.
  You have these choices now:
     1 = Cluster installation using ssh/scp
     2 = Cluster installation using rsh/rcp (remsh for HP-UX)
     3 = Install FEKO on a single node only (then no remote access
         or remote copying required)
  Please select [1] 3
  Local installation on one node only.

   When running FEKO on an SGI Altix, then also the highly optimised
    SGI MPT is supported by FEKO. This must be available on the system
    (i.e. not included with FEKO)
      Checking for  1 = MPICH2        ... found (part of FEKO installation)
      Checking for 11 = Intel MPI     ... found (part of FEKO installation)
      Checking for  4 = SGI MPT       ... found
  Please select now which of these MPI implementations should be used.
  Typically the default is detected automatically and should be fine,
  i.e. just press return. You can also easily change this later manually,
  one just has to change the value of FEKO_WHICH_MPI in the initfeko
  script.

Determining the target path for the installation.
  Please enter the installation path for FEKO (use an absolute
  directory name, not variables such as $HOME or ~). To use the
  default just press return: [/opt/feko/7.0] /sw/feko/7.0.2
  FEKO will be installed to: /sw/feko/7.0.2
  No update, new FEKO installation.
  Checking for write permission in this directory ...  done.
Creating the FEKO initialisation files initfeko and initfeko.csh
  Creating non-existing directory /sw/feko/7.0.2/bin ...  done.
  New FEKO installation (not an update), cannot keep current settings.
  For an out-of-core solution, a directory must be specified for the
  location of the possibly quite large out-of-core files. A local (not
  remote) directory with write permissions for users intending to use
  FEKO should be specified in the following. This selection can always be
  changed again later by editing the environment variable FEKO_TMPDIR in
  the file /sw/feko/7.0.2/bin/initfeko. Typical choices
  would be e.g. /tmp or /scratch. One can also use the current directory
  where later during the FEKO run the user will have the FEKO input and
  output files, then use . as directory (quota must be large enough).
  Please enter your selection now: [.]
Using FEKO_TMPDIR=. (update).
  Not setting FEKO_MAXALLOCM (automatic mode of FEKO on this platform).
  Now creating the file /sw/feko/7.0.2/bin/initfeko ...  done.
  Now creating the file /sw/feko/7.0.2/bin/initfeko.csh ...  done.
----------------------
Creating default GUI settings file default.ini
   ---> Press return to continue
----------------------
Extracting FEKO executable files from the source archive
    /sw/feko/7.0.2/src/feko_install/LINUX_X86_64.TAR
to the installation directory
    /sw/feko/7.0.2
  Now extracting files and setting permissions ...  done.
----------------------
Extracting 64-bit FEKO GUI files from the source archive
    /sw/feko/7.0.2/src/feko_install/LINUX_GUI64.TAR
to the installation directory
    /sw/feko/7.0.2
  Now extracting files and setting permissions ...  done.
----------------------
Extracting FEKO example files from the source archive
    /sw/feko/7.0.2/src/feko_install/EXAMPLES.TAR
to the installation directory
    /sw/feko/7.0.2/examples
  Now extracting files and setting permissions ...  done.
----------------------
Copying licence file LICENCE.TXT to the doc subdirectory ...  done.
Extracting FEKO documentation files from the source archive
    /sw/feko/7.0.2/src/feko_install/DOC.TAR
to the installation directory
    /sw/feko/7.0.2/doc
  Now extracting files and setting permissions ...  done.
----------------------
Creating some links for Intel LINUX (MKL versus ACML).
  Done (using MKL).
----------------------
Creating MPI links for LINUX (MPICH2/Intel MPI/etc.).
  Link for SGI MPT files will be installed ...  done.
Checking FEKO executables dependencies on shared libraries.
  No missing dependencies detected.
---------------------
Creating the file /sw/feko/7.0.2/mpi/share/machines.feko
with a list of nodes in case you are running FEKO in a cluster
environment. For a single node (e.g. multi-cpu or multi-core
machine) just select below one node.
  Creating non-existing directory /sw/feko/7.0.2/mpi/share ...  done.
  Expert Mode (please answer with [n] unless you are sure what you do):
    If you install FEKO on a parallel cluster with many nodes
    (e.g. a 512 node Linux cluster), then entering now 512 node
    names interactively might be a very boring task. Do you want
    to switch to an expert mode, where you have to provide a
    machines file yourself (instructions of how to do this will
    be given if you answer 'y')? [n]

 The first node to be added is this machine 'gowonda2'.
    How many processes shall be run on the node 'gowonda2'
    (note that normally this should be equal to the number of
    CPUs/cores available on this node) ? [1] 12
    Adding entry   gowonda2:12
  Adding another node: Enter nodename or just press return
                       to finish: []
  Finished adding nodes.
   ---> Press return to continue
----------------------
Creating a sample .rhosts file /sw/feko/7.0.2/mpi/share/.rhosts.sample.

   ---> Press return to continue
----------------------
Creating file /sw/feko/7.0.2/license/request with licence information.
  This file will be saved on your hard disk, so that you can later send
  it to your FEKO distributor. It will not be sent automatically, so that
  you can review all the information before sending it.
Processing FEKO licence request, please wait ...
------------------------------------------------
-> Creating request file ...
-> Collecting information for all installed FEKO components ...
-> Checking the availability of secfeko ...
-> Collecting machine codes ...
     Using all nodes as found in /sw/feko/7.0.2/mpi/share/machines.feko
       Checking node gowonda2 (1 of 1) ...
File
  /sw/feko/7.0.2/license/request
has been created, see instructions in this file.
----------------------
Checking for upgrade/installation of Sentinel USB dongle driver.
  Dongle driver will now be extracted to /sw/feko/7.0.2/license/Sentinel_SPI
  Creating non-existing directory /sw/feko/7.0.2/license/Sentinel_SPI ...  done.

  Checking for already installed Sentinel USB driver (sntl-sud) ... Not found
  If you plan to use a FEKO licence locked to a dongle, you should install
  the Sentinel USB dongle driver now.
    Do you want to install it? [n]

----------------------

Congratulations, you have now finished the FEKO installation!

Some final notes:

 - The initialisation files /sw/feko/7.0.2/bin/initfeko
   and /sw/feko/7.0.2/bin/initfeko.csh have been created.

   For bash/sh/bsh/ksh shells the script initfeko should be executed
   from the user file $HOME/.profile or $HOME/.bash_profile or
   whatever the name of the applicable file is as
        . /sw/feko/7.0.2/bin/initfeko
   (note the dot and then the space).

   For csh/tcsh shells the script initfeko.csh should be executed
   from the user file $HOME/.cshrc or $HOME/.login or
   whatever the name of the applicable file is as
        source /sw/feko/7.0.2/bin/initfeko.csh

 - A file /sw/feko/7.0.2/license/request has been created. Please send
   this file to your FEKO distributor. If you are unsure about whom
   to contact, please check http://www.feko.info/contact.htm.
   You will then receive a password file secfeko.dat, which must be
   installed at the location /sw/feko/7.0.2/license/secfeko.dat.

 - Once you have received and installed the licence file secfeko.dat,
   it is higly recommended to run the FEKO updater feko_update_gui
   (GUI version) or feko_update (command line version). If you have
   a parallel FEKO installation on a cluster and FEKO is installed
   on each node locally, then this must be executed on each cluster
   node.

 - You have installed FEKO not from the FEKO DVD but from a temporary
   directory on your hard disk. You can now delete this temporary
   directory /sw/feko/7.0.2/src/feko_install with all files inside.

>>>>>>>>>>