. This gives full permissions
to the port. The execute permission is not strictly necessary but is
probably a good idea.
To Test The Device:
Run the program: Device3DServer -h for help
Example: Device3DServer -device Isotrak2 -port /dev/ttyS0 -v
Don't forget the -v command for verbose output. You will see a few
messages and if all is well after 4-8 seconds you should see a continuous
stream of numbers. If you do and they're not all zeros then the Bat is
working and all should be well.
On the Unix platforms if you get the message unable to open port, and you
have previously checked the permissions, then this often means that the
cable connecting the computer to the Bat is missing a NULL modem adapter
(or has one too many).
Yes. The license server needs to have certain ports open for the client machines to connect. If those
ports are being blocked, then the clients will not be able to check out a license. See question 2.11 for the exact ports.
No. Client machines do not need to have any open ports.
The license server software connects using two ports. The first port is selected from the first available port in the range
27000 to 27009. The second port is assigned by the operating system when the server is started. Since this port will change each
time the server is started, this is not suitable when a firewall is in use. To get around this, the second port can be specified
in the DAEMON section of the server license file. For example:
SERVER demeter 0007e96df22e
DAEMON ivs port=1051
FEATURE fmpro ivs 6.1 permanent 5 88G016678268 DUP_GROUP=UH
In this case, the TCP port 1051 will be used (This part of the license file can be modified without needing a new license from IVS).
To summarize, the following ports need to be open:
a) All 10 ports in the range 27000 to 27009
b) The port specified on the DAEMON line of the server license file
Please refer to the documentation for your specific firewall software. For instructions on using the built in firewall that comes with
Windows XP Service Pack 2, go to question 2.13.
To open up certain TCP ports in Windows XP, Service Pack 2, do the following:
- Open the Windows Firewall Controls: Start Menu > Settings > Control Panel > Windows Firewall
- Change to the "Exceptions" tab
- For each port you need to open, click "Add Port", and then specify the port number. Refer to question 2.11 for exact port numbers.
This means that your video driver is out of date. Fix this problem by
going to http://nvidia.com/content/drivers/drivers.asp
and downloading the most recent driver for your video card. Usually, Fledermaus
benefits from having a recent driver for any brand of video card.
If you use a Dell computer you can also go to the Dell website, http://support.dell.com,
to find an updated driver.
The maximum file size you can use depends on the type of data you are
using as well as your operating system and hardware configuration. For
more information on specific limitations, please contact IVS support.
Fledermaus supports a variety of data types depending on what you are trying to visualize. Below is
a list of common data types and the main applications that would be used to handle this type of data.
For a full overview of both internal and external data types in Fledermaus, please refer to the
Reference Manual.
The following is a list of data types supported by Avggrid:
- Digital Terrain Model (DTM) classes (assemble SD file in DMagic)
- BasicDTM
- SonarDTM
- SphericalDTM
- TexturedDTM
- SurfacePlotDTM
- 3D Geometric Classes
- 3D Point class (File -> Import Data -> Import Points)
- 3D Line/Polygon class (ArcView shape files, DXF, File -> Import Data -> Import Lines)
- 3D Grid class (Data -> Add 3D Grid)
- Contour Lines class (Controls -> Contouring)
- Solid Model class (3DS or Wavefront OBJ)
- Imagery Visualization Classes
- GeoImage class (Data -> Add Image)
- Vertical Image class (Data -> Add Vertical Image)
- Vertical Curtain/ Seismic Class (applets: mkvcurtain, segeditor, renderseis)
- Sounding QC (Quality Control) Classes
- Sounding class (mksoundings)
- HTF Sounding class
- PFM Sounding class (Files -> Import PFM)
- HTF to PFM and back to HTF (3D editor, applet: htfconvert)
- GSF to PFM and back to GSF (3D editor)
- SHOALS to PFM and back to SHOALS (3D editor)
- ASCII XYZ to PFM and back to ASCII XYZ (3D editor)
- ROV Operations Class (Data -> Add ROV)
- Supported Surface Formats (Load with DMagic, File->Import Surface)
- OMG R4/Mos
- ASCII Multivariate
- Etopo5 Database
- NOAA Gravity Data
- Grass DTM
- Gridded Ascii
- Predicted Topography
- GMT GRD/NetCDF
- ISIS grd
- Surfer ASCII grid
- ER Mapper Scalar (.ers)
- GRI
- USGS DEM
- Arcview Grid
- Raw Binary Grid
- XYZ formats supported (avggrid, DMagic: File->Import XYZ, File->Export XYZ)
- ASCII text
- C&C binary
- STB binary
- IVS binary
- GSF binary
- ArcView Grid (export only in DMagic)
- Image formats supported (DMagic)
- TIFF including geoTIFF
- JPEG
- GIF
- BMP
- PCX
- PPM
- Raw RGB
- Unisips
- TDR
- PostScript (output only)
Fledermaus supports the following three main mechanisms for 3D interaction:
1. 3D Flight using the IVS Bat
2. 3D Flight using the Logitech 3D Mouse
3. 3D Flight using mouse controlled navigation ( widgets )
4. 3D Flight using 3DConnexion's SpaceNavigator
The technical document interaction_modes.pdf provides further details about the interaction modes.
When working with Area Based Editing, a format can be supported for input only, or it can be fully suported for both loading and unloading.
For the full details of the supported formats, please refer to the following page: Formats.
Yes, with Dmagic you can import grids made with the latest versions of Caris HIPS.
Yes. You can visit our forum here.
Yes Fledermaus applications and specifically PFMDirect read and write
to, the HS2 format. However, Hypack only supplies libraries for the
Windows environment, which requires users to work in this environment if
they are dealing with HS2 format data.
There are typically two kinds of XYZ data, gridded and ungridded.
Choose dmagic to import gridded data and avggrid to import ungridded
data.
Avggrid is used to import ungridded data. Avggrid can be started from
DMagic using the "File -> Import XYZ Data" menu item. Once in avggrid,
select "File -> Add File to Grid..." to select the file(s) you would like
to import. Select the desired gridding parameters, in particular set the
Cell Size to an appropriate value for your dataset, then click "Scan
File." Now avggrid will show the bounds and size of the dataset. Process
the data into a DTM by first clicking "Convert," then exporting the file
(File->Export DTM/GEO file...). For more details, see Chapter 5 of the
Reference Manual.
You can also view the
DTM by clicking on the "Plot DTM" button on the bottom row.
DMagic is similar, but is used to import gridded data. Select
"File->Import Surface" and select the desired file. Next pick the file
type, choose the desired parameters such as cell size from the righthand
panel, click "Scan for Information," and then choose "Convert and Save
File" to save the new DTM.
You can use Fledermaus to import an ArcView shape file. In Fledermaus,
select "File -> Import Data -> Import Arcview...," enter the required file
names, then click "Convert Selected File." This will create a lines
object which you can load directly into Fledermaus.
Images can be loaded into a scene in Fledermaus. Also, an image can be
draped on a DTM using DMagic or the mktextureDTM applet. There are
several ways that you can import an image:
- draped on a DTM in dmagic or mktextureDTM
- georeferenced to a portion of a DTM using dmagic
- horizontally or vertically in Fledermaus
In DMagic, select "File->Import Image...." Enter the
file name or browse using the arrowhead icon. Choose whether to rescale
the image to the size of the DTM or to match georeferenced regions. In
the latter case, enter the georeferencing data for the image and the
resampling filter desired. In both cases, enter the output file name
and select the DTM to process.
In Fledermaus, select "Data->Import Image" or "Data->Import Vertical
Image." In both cases, a new node will be added to the scene which
you can select in the lower left panel. Selecting the image node will
show the settings for the image in the Data Set Control panel. Here,
you can enter the file name of the image or browse for the image by
clicking on the arrowhead icon.
The 3D Area Based Editing module in Fledermaus is based on the PFM data
structure developed at the US Naval Oceanographic Office. The PFM
structure allows the load of a variety of common multibeam formats for
visualization and editing. These include GSF, Caris HDCS, SHOALS out and
wav files, HTF and ASCII XYZ plus attribute data. The PFM is meant to be a
temporary structure used to optimize data for area based editing and can
be removed once all editing is complete.
3D Surface Area Based Editing allows better decision making since all of
the data is visible in a certain area, not a subset, and editing decisions
can be made much quicker and more accurately than single line/swath based
editing.
The typical method of using PFM is to load data from an existing format to
the optimized PFM structure, process, edit the data, select soundings
features and in Fledermaus, and then save the changes back to the
original file. This scheme allows data to remain in its original form and
does not require that all data be permanently changed to a new file
format. It also provides a rigorous audit trail for verification.
For further details see the
Area Based Editing Manual or Module 4 of the training material.
In Fledermaus, select "File -> Import -> Import Points" or
"File -> Import -> Import Lines." Select the input file, the format
of the input file and any other required information , then click "OK"
IVS has recently improved the movie making process. All movie making operations
are now done within the MovieClient application using a simple to use wizard that
will guide you through the operation.
To make a movie you will need:
- a scene file ( .scene )
- a flightpath file ( .fph )
If you have these files, the wizard should be able to guide you through the rest. For
the exact process refer to chapter 7 of the
Reference Manual or the trainning modules.
This is the last step in creating a flight path video (movie) (see Q12).
You can use "movieencoder" or third party software such as
"QuickTime Pro" or "Adobe Premier" on PCs.
The process of creating vertical sub-bottom images involves using the 'mkvcurtain' command line
applet and optionally a 3rd party graphics editing package such as Photoshop. For a detailed
explanation of the process for creating these images, please refer to the vertical_images.pdf
technical document.
The process of using an image mask to create a new masked DTM is done using the 'scalarmask' command line
applet and an example is described in the masking.pdf technical document.
The command line applications are now run from either the FMCommand application
or a new command line applet called cmdop. When using fmcommand, select
the "Command & Control" tab. You should see all of the command line applets
on the left hand side of the interface. To use the applets on the command
line, cmdop must be used to access that functionality. For example instead
of "mkcamp -in..." you would now use "cmdop mkcmap -in...".
Your field of view is determined by the size of the display window
in MovieClient; if the display window is smaller than the Fledermaus
window, then MovieClient will only show the centre of the image that
Fledermaus shows and will cut off the edges. Since Antaliasing and
"render magnification" change the size of the display, they also
affect your field of view; increasing the render magnification
decreases your field of view and increasing antialiasing increases the
field of view. You can work around this problem by resizing the
Fledermaus window so that the 3D display in Fledermaus is the same
size and shape as the MovieClient display (you specify this value
indirectly when choosing the movie format). This will be improved in a
later version of Fledermaus. We recommend you take an image of a
certain size (in pixels) and load it into Fledermaus and then match
the bounds of the viewing window with the image bounds.
1. Open Route Planner and load the SD surface object.
2. Changed the Default Radius from 1000 to a value of 1. This is
located in the top left hand corner of the application.
3. Import the XY point file from the Menu option, File > Import >
Import XY Intersections.
4. Go into 'Edit Mode' by clicking on the 'Edit' Button located at the
top right hand corner of the application.
5. You can now profile along the imported route by right clicking
anywhere on that route and dragging to anywhere else on the route
that you want to extend your profile to. It is sometimes helpful to
zoom in on the route before you start the profiling.
Note: While in edit mode, you can only profile along a loaded route.
If you want a profile of the surface that is outside of a route, you
have to leave 'Edit Mode'. Also, to profile from one point on a route
to another, you don't have right click and drag along the actual route
until you get to the end of the desired profile. You can simply right
click on the route, and drag directly to the end point. And finally
while in edit mode be sure not to left click or middle click one
surface as this could end up editing the route.
CUBE (Combined Uncertainty and Bathymetric Estimator) is an algorithm that takes advantage of statistical
redundancy in a dense collection of soundings. Tracking the uncertainty associated with these soundings,
CUBR can make estimates of the true depth of water across a survey area.
The requirements for running CUBE depend on which method is used to provide the errors. The three methods are:
1. Using a fixed user supplied value for the vertical and horizontal TPE ( Total Propagated Error ):
- This method has the lowest requirements and can be used with any input format that PFMDirect supports but as one
might expect will have limitations. It is best to make use of the power of CUBE with a data format that supports TPE (see below).
2. Reading pre-calculated errors from the input files:
- This requires a supported input format that contains variance error values. As this technology is still new, only a number
of formats provide this information. We currently support the GSF file format. ASCII xyz files can also be used with CUBE
if they are formatted so that two extra columns with the variance values for vertical and horizontal error are present.
We intend to support reading errors from HDCS files in a future release. Sign up to our mailing list
to keep track of these developments.
3. Calculating errors using the built in error models:
- This method has the largest number of requirements. First, only input formats that contain navigation data as well
as other ancillary data can be used for this method. Currently the two supported formats are GSF and HDCS.
In addition, the multibeam sensor used to collect the data must be one of the supported sensors ( see question 5.3 ).
The final requirement is that a vessel configuration file ( .par extension ) containing sensor offsets and error values
for the collection platform must be provided. Click on following link to download example
of .par file.
If you have a format containing either built in errors or navigation data, and would like to have it supported, please contact
support@ivs3d.com for further information.
The following sensors are supported:
- Simrad EM300
- Simrad EM1000
- Simrad EM1002
- Simrad EM3000
- Simrad EM3000D
- Reson SeaBat 8101
- Reson SeaBat 9001
- Reson SeaBat 9003
- Reson SeaBat 8125
- Atlas Hydrosweep
- Elak Nautik 1180
- Seabeam 2112
Yes. A sample vessel configuration file is available for download: vessel001.par.