Vis5D Frequently Asked Questions (and answers)


Last updated on May 9, 1996.


Introduction

If you have a question about Vis5D look here for an answer. If your question isn't answered or you want to add something to this FAQ please contact Bill or Brian.



Part 1: Compilation questions

1.1. I'm trying to compile Vis5D but get error messages about __eprintf undefined.

This indicates that the C libraries on your computer were compiled with GCC. You should add -lgcc to the LIBS line in src/Makefile for your system configuration.

1.2. I'm trying to compile Vis5D on my Sun with SunOS 4.x but it fails with a message like acc: command not found

The acc compiler is Sun's ANSI C compiler. Ask your system administrator to install it.

1.3. I'm having trouble compiling Vis5D 4.2 on my SGI running IRIX 6.0.1.

If possible, upgrade to IRIX 6.1. Vis5D for IRIX 6.1 uses the N32 compilation mode which gets maximum performance from your CPU while only using a 32-bit address model (more memory efficient). If you can't upgrade from IRIX 6.0.1 then you'll have to edit the lui5/Makefile, src/Makefile, and util/Makefile and change all the occurances of -n32 to -64.



Part 2: Data conversion questions

2.1. I'm making my own data conversion program using the examples in the convert/ directory. It doesn't work. The output file has invalid values.

If you're using a Linux or DEC system be sure to compile the programs with the -DLITTLE flag. This enables the byte-swapping code needed for little endian systems.

2.2. When I try to link my data conversion program it fails saying the symbols v5dcreatesimple, v5dclose, v5dwrite are unresolved.

You must link your program with the v5d.o and binio.o files found in the src/ directory. See the example Makefiles (*.m) in the convert/ directory for details.

2.3. How can I make my own topography (like EARTH.TOPO) or map outline files (like OUTLUSAM)?

Look in the util/ directory for makemap.c and maketopo.c which are skeleton C programs for that purpose.



Part 3: Using Vis5D

3.1. I'm trying to print a PostScript image but all I get is a blank page.

People using IBM RS/6000 and HP computers have reported this. It appears that the xpr program is at fault. Try saving your image as an xwd file then convert it to PostScript with XV, the popular image viewer/ manipulator for X.

3.2 My isosurfaces don't look correct. They appear as "stripes".

If you're trying to visualize a large 3-D grid (larger than 500,000 data points) then you're probably running out of memory. If you've got 128MB or more of memory you should edit the src/vis5d.h file and change MBS appropriately. If you specify 128MB or more Vis5D uses a different data structure to store isosurfaces which accomodates larger isosurfaces.

3.3 When I click on "NEW VAR" to call a Fortran function it isn't listed.

You may be running out of virtual memory (swap space). Vis5D must use "fork/exec" to get the list of functions and to execute them. If you have insufficient swap space this operation will fail. Ask your system adminstrator to increase the swap space on your computer.

3.4 My data set has many variables. When I turn on the probe I can't see all the values.

Try using a smaller font. Type vis5d alone and look at the -font option.


Other links: Vis5D, API document, Scripting document, Bill Hibbard, Brian Paul.