3D object problems

3D object not visible on scene

If you have just created a 3D object but can't see it on your scene:

Surfaces and schools appear very erratic

The algorithms used to detect surfaces and 3D schools will produce poor results if a variable to which they are applied is linked to an erratic cruise track. If a visual inspection reveals that the cruise track contains jumps, loops or other problems you should apply different processing and smoothing until it more accurately represents the path of the logging vessel. When you have smoothed the cruise track you should detect the schools and/or surfaces again and compare the results.

Note: A cruise track that appears smooth at large scales may contain loops and jumps when viewed at smaller scales.

Very poor performance detecting 3D schools

3D school detection can be very slow (taking hours on even a fast machine) and require large amounts of RAM. This is particularly the case if the minimum 3D size limits are smaller than or near to the size of individual data samples, which means that schools containing a very small number of samples will be considered during the processing. If you find that detection is slow, does not complete in a reasonable amount of time, or reports running out of memory, then consider one or more of the following:


See also

3D display problems
New Surface dialog box
Create 3D Surface From Line dialog box
Detect 3D Schools dialog box