Tips

1. GeoVisage is best used with a desktop area of 1024 by 768 or larger.
2. If GeoVisage runs out of memory then edit the launch script (geovisage.bat on Windows or geovisage on Unix) and change the value following -Xmx on the last line to a larger value. The number should be followed by an m character to indicate a value in megabytes, e.g. -Xmx400m indicates 400 megabytes. This specifies the maximum amount of memory available to Java when running GeoVisage. The value chosen depends on the available memory on the host and the size of the models being viewed.
   If running from NAPSAC make the change in the NAPSAC launch script (Napsac.bat on Windows or Napsac on Unix).
   If running from CONNECTFLOW make the change in the CONNECTFLOW launch script (ConnectFlow.bat on Windows or ConnectFlow on Unix).
3. While a session file is loading the Cancel button can be used to abort the load. This button is only enabled while a data file is actually being read.
4. Logarithmic attribute ranges that cross zero are allowed. Enter a minimum absolute value to use for values close to zero.
   Note that legends may be displayed incorrectly when there are negative or zero log values.
5. If loading externals then you may need to apply transformations to them to move them into the correct position.
6. Transformations are also useful to compare different realisations side by side.
7. When displaying pathlines it is usually necessary to hide the fractures for the pathlines to be easily viewed.
8. If a problem occurs, a message may have been printed to one of the log files:
   • The main GeoVisage log file is called geovisage.log and is located in the geovisage sub-directory of the current user's home directory, e.g. for Windows XP this is usually C:\Documents and Settings\username\geovisage\geovisage.log, where username is the login name of the user.
   • If using GeoVisage from NAPSAC then messages may also be printed to the NAPSAC log file (logfile.txt located in the NAPSAC installation directory on Windows or located in the napsac sub-directory of the current user's home directory on Unix).
   • If using GeoVisage from CONNECTFLOW then messages may also be printed to the CONNECTFLOW log file (logfile.txt located in the CONNECTFLOW installation directory on Windows or located in the conflow sub-directory of the current user's home directory on Unix).
   • If a severe error occurs in the 3D graphics library then the application may abort and a file of the form hs_err_pid*.log is created in the current directory, where * is a number with one or more digits. This may occur when viewing models that are too large for the memory available on the computer.

COPYRIGHT © 2003-2004, Serco Assurance (a division of Serco Ltd.)
Enquiries about copyright and reproduction should be addressed to the
Commercial Manager, Serco Assurance, Thomson House,
Birchwood Park, Risley, Warrington, Cheshire, WA3 6AT.