Sequential Manual - EIVAdownload.eiva.dk/online-training/Sequential Manual - Postprocessing... · a...

September, 2007

Sequential Manual EIVA POSTPROCESSING SUITE NAVIEDIT – NAVIMODEL - NAVIPLOT

LDA Page 2 of 23 Rev. no. 0, 2007-09-03

Sequential Manual EIVA POSTPROCESSING SUITE NAVIEDIT – NAVIMODEL - NAVIPLOT September 2007

8-10 Teglbækvej DK-8361 Hasselager – Aarhus, Denmark Tel: +45 8628 2011 Fax: +45 8628 2111 e-mail: [email protected] Web: www.eiva.dk

0 First Edition LDA 03/09/2007

Revision Description By Checked Approved Date

Key words Hydrographic Surveying, Postprocessing, Charting

Classification

Open

Internal

Proprietary

Distribution No of copies

N/A N/A N/A

LDA Page 3 of 23 Rev. no. 0, 2007-09-03

CONTENTS

1. INTRODUCTION .................................................................................................................4

2. POSTPROCESSING WITHIN NAVIEDIT............................................................................5 2.1 Proposed Method, Multibeam Data.................................................................................7 2.2 Proposed Method, Singlebeam Data (if applicable) ........................................................7

3. POSTPROCESSING WITHIN NAVIMODEL .......................................................................7 3.1 Project Planner................................................................................................................8 3.2 Postprocessing within NaviModel .................................................................................10 3.3 Automatic cleaning........................................................................................................11 3.4 Manual cleaning ............................................................................................................14 3.5 Proposed Method, Multibeam Data...............................................................................16 3.6 Proposed Method, Singlebeam Data (if applicable) ......................................................19

4. POSTPROCESSING WITHIN NAVIPLOT.........................................................................20 4.1 Proposed Method, Multibeam and Singlebeam Data (if applicable) .............................21

5. CONCLUSION...................................................................................................................22

Bathymetric Postprocessing Procedures

1. INTRODUCTION

The purpose of the present note is to propose methods to be used in connection a typical hydrographic processing task, utilizing the EIVA postprocessing suite. The note is to be regarded a sequential and dedicated manual, in which the description of the various phases is given in the sequence that an actual postprocessing process is most likely to undertake. Further the degrees of detail of the various chapters are intended to reflect the particular requirements of such a typical postprocessing task.

Note that more detailed and general information on postprocessing is available on the Help-features supplied with the various programs that constitute the EIVA postprocessing suite as well as in the ‘EIVA Training Site’ that is included on the EIVA software CD. In particular, the tutorial supplied on the topic of NaviEdit/NaviModel/NaviPlot, supplies detailed and relevant information.

Figure 1 below gives the scope of the manual. The figure depicts the data-flow through the EIVA software suite with the on-line part in the upper left corner (NaviPac & NaviScan). The off-line/postprocessing parts in the lower right part of the figure are hence the subject of the manual (NaviEdit, NaviModel & NaviPlot)

Figure 1 Scope

LDA Page 4 of 23 Rev. no. 0, 2007-09-03


2. POSTPROCESSING WITHIN NAVIEDIT

The NaviEdit survey data editing software is designed for graphical editing of marine survey data comprising single-beam echo-sounder and multi-beam echo-sounder data, profiling sonars, pipe-tracker data etc. as well as all survey-related secondary sensors. Editing of all raw data is performed on sensor-level. Prior to editing however, the raw data is entered into an SQL database that constitutes the formal link between NaviEdit and the raw data. In the particular case, the raw data is originating from NaviScan (*.sbd) (multibeam data) and from NaviPac (*.npd) (singlebeam data).

Figure 2 JobPlanner

The JobPlanner represent the overall user-interface to NaviEdit (see Figure 2). The program facilitates editing at two levels, editing of header information in the Header Editor and editing of raw sensor-data in the Data Editor. Editing of header information includes off-line editing of all on-line settings, such as: geodesy, tidal information, off-sets etc (see Figure 3).

Figure 3 Header editor

LDA Page 5 of 23 Rev. no. 0, 2007-09-03


The editing of all raw sensor-data is enabled through a number of possibilities (see Figure 4): • Zoom (zoom in/out, zoom previous)

• Region (create region/delete (inside/outside) region)

• Spike detection ((wave length, frequency), delete spikes inside/outside region etc)

• Translate (absolute value (factor), with off-set)

• Scale (scale, origin, scale inside/outside region etc)

• Smooth (wave-length, scale inside/outside region etc)

• Delete (delete inside/outside region, delete spikes inside/outside region)

• Settings (Axes (scale), colors, XY-window etc.)

Figure 4 Data Editor

LDA Page 6 of 23 Rev. no. 0, 2007-09-03


LDA Page 7 of 23 Rev. no. 0, 2007-09-03

2.1 Proposed Method, Multibeam Data In the present context, editing of multibeam data within NaviEdit is limited to the following tasks: • Import of raw data via multibeam interpreter

• Editing/check of offsets (header-editor)

• Deselecting of beams (header-editor)

• Editing/check of geodetic parameters (header-editor)

• Tidal data (header-editor)

• Rough check of all sensordata (data-editor)

• Tidal data (bathy-depths/predicted tides/observed tides) (data-editor)

• SV-data

Once edited, the data is re-entered onto the SQL database for further processing, and, in the present context, for exporting to binary XYZ (*.ned).

2.2 Proposed Method, Singlebeam Data (if applicable) For the single-beam data, editing within NaviEdit consists of the following tasks: • Import of raw data via the NaviPac interpreter

• Editing/check of offsets (header-editor)

• Editing/check of geodetic parameters (header-editor)

• Tidal data (header-editor)

• Tidal data (bathy-depths/predicted tides/observed tides) (data-editor)

• Thorough check/editing of singlebeam data (data-editor)

• Rough check of all other sensordata (data-editor)

Once edited, the data is re-entered onto the SQL database for further processing, and, in the present context, for exporting to ASCII XYZ (.xyz).

3. POSTPROCESSING WITHIN NAVIMODEL

In the present context, the postprocessing within NaviModel encompasses work with two programs: Project Planner and NaviModel itself.


3.1 Project Planner The first step is to read the edited and exported *.ned-files into Project Planner. Here all the data, originating from one section of the survey-area, will be merged into blocks with a size that is suitable for modelling within NaviModel.

First all data from the section in question must be added to the project. This is done via the menu-item ‘File-Add files…’ Add all .ned-files for the area in question.

Figure 5 Project Planner – Add Files (Step 1)

Once the data has been added, press the Files item left of the map-area, in order for the data to be visualized in the map-area (see Figure 5). When pointing with the cursor and clicking on the map-area, it is now possible to create a region that surrounds the data. Be sure to finish it by a final click on the initial point (see Figure 6). The icons ‘Union’, ‘Difference’ and ‘Intersection’ are now available. Press ‘Union’ and observe, that the region is now shown under Boundaries left of the map-area. Right-click on the boundary in question and select ‘Subdivide…’ On the dialog that now appears, select the number of rows and columns as well as the edge overlap for this subdivision. The number of rows and columns should be the same (1, 2 or 3). Be sure to choose the number so that the length of each of the new borders will not exceed 10 km. The overlap must be sufficiently high to ensure, that the modelling in NaviModel will not create border zones with different values. Alternatively the width and height of the tiles can be specified, in which case the number of rows and columns will be automatically updated to reflect the size.

LDA Page 8 of 23 Rev. no. 0, 2007-09-03


Figure 6 Project Planner – Create Boundary (Step 2)

Once the tiles/boundaries have been created, they will appear under Boundaries left of the map-area. Now click on the various sub-boundaries and see that they are highlighted in the map-area. Delete the ones that are not suitable for further processing work (see Figure 7).

Figure 7 Project Planner – Subdivide Boundary (Step 3)

Select menu-item ‘File-Export…’ and select a suitable overall name for the files to be exported. Project Planner will now merge the various .ned-files into one large .ned-file, called ‘name_000.ned’. This file will furthermore be split up into the number of files according to the

LDA Page 9 of 23 Rev. no. 0, 2007-09-03


subdivision of boundaries. These files are named ‘name_001.ned’ through ‘name_00n.ned’, with n being the number of sub-boundaries and constitute the end results of the postprocessing within Project Planner.

Note that Project Planner should only be used in connection with multibeam data.

3.2 Postprocessing within NaviModel The NaviModel modelling programme is primarily a tool for the generation of and manipulation with Digital Terrain Models. The modelling is based on either Triangular Regular Network (TRN) or on Triangular Irregular Network (TIN) algorithms. In the present context, TRN-models are used – for the multibeam as well as for the singlebeam data (if applicable). The TRN-models consist of equally spaced triangular cells as opposed to the TIN-models, where the triangles are based on the raw data which will result in an irregular network not suited for multi-beam data or for singlebeam data with relatively large line-spacings.

Figure 8 NaviModel

The following procedures comprise a typical modelling process: • Creation of new model-file

LDA Page 10 of 23 Rev. no. 0, 2007-09-03


LDA Page 11 of 23 Rev. no. 0, 2007-09-03

• Input of data (survey data in NaviEdit format (binary XYZ (*.ned)), ASCII XYZ data, runline and profiles or raw NaviScan and NaviPac survey files)

• Cleaning on model-level (prior to the actual creation of the model) can be performed either manually profile by profile in a 2D view and in a 3D-view or automatically through a spatial plane over the model thus allowing handling of data overlap

• Model analysis of actual versus theoretical models, model manipulation as well as volume- and area computations

• Data-reduction facilities are provided during the model definition phase by allowing setting of tolerances for depth variations and allowable shrinkage of model borders. The option is available for TIN models only.

• Model generation for a given survey area by definition of model parameters (desired cell size, depth data type (minimum, maximum, average, last value) etc.)

• Smoothing of model (TRN only)

• Generation and manipulation (smoothing) of contours (and contour fillings)

• Generation of bathymetric plot

• Generation of profiles

Typical output from NaviModel is consequently: • DTM

• Contour curves

• Longitudinal profiles

• Cross profiles

• Cleaned or rejected data

• Various screen prints

3.3 Automatic cleaning The automatic cleaning facility in NaviModel is in most circumstances regarded a fundamental part of the editing of the multi-beam data. The following dedicated description of the background for the facility and of the various menu-items is detailed in the Help menu of NaviModel.

The implementation of the automatic cleaning facility is based upon ‘Flachenhafte Plausibilisierung von Peildaten’ (≈ Area based probability estimation of bathymetric data) by Harry Wirth.

The cleaning process consists of the following steps.

1. One or more data files are loaded into NaviModel


LDA Page 12 of 23 Rev. no. 0, 2007-09-03

2. Approximate cell-dimensions are chosen by the operator explicitly or implicitly by the selection of an average number of points in each cell

3. Cell dimensions are calculated. It is attempted to cover the data and get an even distribution of points in each cell and among the cells

4. The operator selects the polynomial between four options:

Plane: degree of polynomial=1

3 parameters: A0 + A1X+ A2Y

Hyperbolic parabolic: degree of polynomial=2

4 parameters: A0 + A1X+ A2Y + A4XY

Elliptic parabolic: degree of polynomial=2

6 parameters: A0 + A1X+ A2Y + A4XY + A5Y2

Cubic function: degree of polynomial=3

10 parameters: A0 + A1X+ A2Y + A4XY + A5Y2 + AbX3 + A7X2Y + A8XY2 A9Y3

5. For each cell all points are initially assigned the weight 1.0 and an approximating polynomial with the selected number of parameters is computed using the least squares principle. A weighted standard deviation is computed and new weights are calculated. Points deviating less than the standard deviation are given the weight 1.0. The weight is otherwise defined to be inversely proportional to the deviation. The approximating polynomial is recalculated as a weighted least squares approximation. The process is repeated until it stabilizes or at most 100 times.

6. The significance of the coefficients of the highest degree is tested. If they are not significant at a level of 95% the number of parameters is reduced and the approximating polynomial is recalculated with the reduced number of parameters.

7. The data points are tested at a level of 95%. Potentially erroneous data are marked.

8. The marked data points are tested against a geometric bound. If the perpendicular distance between a point and the surface defined by the polynomial is smaller than a bound selected by the operator the point is accepted.

9. Points not accepted by one of the tests are rejected.


Figure 9 Setting up the cleaning

Setting up the cleaning is performed by selecting and defining a number of parameters (see Figure 9):

Grid width, Grid height: Preferred grid size (m) used when cleaning the data. The smaller grid the more precise computation, the more time consuming...

Compute Grid: Checking this enables the field mean points/cell (and disable width/height fields). Enter a sensible value in this field and the program will calculate the grid size based on the number of points in each cell.

Shape: Select between the four different degrees of polynomial that follow the surfaces shape.

Perpendicular distance to the surface: The maximum allowable distance from the polynomial. Data within this distance will not be eliminated from the model.

LDA Page 13 of 23 Rev. no. 0, 2007-09-03


LDA Page 14 of 23 Rev. no. 0, 2007-09-03

Clean: Pressing this button will cause all model data to be cleaned using the current settings. This can be repeated. View report when done.

Undo Cleaning: If the cleaning is not acceptable, this button should be pressed. Last cleaning will be undone. If several cleanings have been performed in succession, each press of the button will cause latest cleaning to be reset.

Save cleaned (ASCII): Save the cleaned data that is marked blue – the remaining data after the eliminated (red) data is removed – in an XYZ (Binary or ASCII) file.

Save eliminated (ASCII): Save the eliminated data that is marked blue – the data eliminated (red) that is removed due to distance from polynomial – in an ASCII XYZ file.

Display 2D poly: Show the cleaning grid in the Coverage (2d) window.

Detailed Report: Make the report more detailed with additional cleaning information for each cell

When the cleaning has been performed (and the ‘Display 2D poly’ has been selected) the map-area will show red and blue points. The red points are points weighted down (eliminated) according to the grid, perpendicular distance to the surface and degree of polynomial selected. The blue points are accepted by the application. Furthermore the cleaning grid can be toggled on/off by using the grid button in the toolbar. In addition, pressing the 3D View button will cause a 3D window to open in which cleaning information, similar to the information shown in the 2D window, is visualized. Note that the points marked for elimination (with a red colour) will not be used when creating the actual model.

3.4 Manual cleaning The manual cleaning facility in NaviModel is normally applied in support of the automatic cleaning. The method will typically be applied upon completion of an automatic cleaning process with the purpose being to remove the erroneous data that the automatic cleaning process for one reason or another has not been able to identify. Alternatively the facility can be used as a quality control tool on the automatic cleaning.

The manual cleaning consists of two different modules:

• Selective manual cleaning

• Structured manual cleaning

The selective manual cleaning will, based on a window of the survey-data, selected by the user, facilitate editing of a longitudinal profile, in which sections can be investigated, and ultimately cleaned. Two different selective methods exist: Manual Selective (see Figure 10) and 3D Selective (see Figure 11).


Figure 10 Selective Manual Selective Manual Cleaning

Figure 11 3D Selective Manual Cleaning

LDA Page 15 of 23 Rev. no. 0, 2007-09-03


The structured manual cleaning is a 3D-based cleaning, in which the user can see small portions, in sequence, of the model area. He is given the possibility, on the basis of the 3D-view, to perform a manual cleaning of areas as well as of single points (see Figure 12).

Figure 12 Structured Manual Cleaning

3.5 Proposed Method, Multibeam Data In the present context the sequence in modelling looks as follows: • Create new model-file

• Input binary XYZ (*.ned) data from the boundaries created in Project Planner. Make sure, that the total amount of data does not exceed 400 Mb for a single model

• Automatic cleaning of the data. The parameters to use will depend of the characteristic of the noise in the data. A combination of size of 20 m, a perpendicular distance of 0.4 m and the 4-parameter hyperbolic parabolic-function is likely to provide sensible results under most circumstances. However care should be taken in particular with respect to the perpendicular distance

• Manual cleaning of the data. Focus should be put on the structured cleaning, in which the cell size should be based upon at least 250000 points, in order to minimize the number of subcells

LDA Page 16 of 23 Rev. no. 0, 2007-09-03


LDA Page 17 of 23 Rev. no. 0, 2007-09-03

fine cell size, collar width as well as depth llar width: 2 and a depth data type of ‘Average’ are

tual project requirements (see Figure 13)

• Choose cell type ‘Regular grid (Hexagon)’ and dedata type. Values of cell size: 2m, coproposed, depending however on the decision on ac

. However too large wave-lengths will cause the model to flatten out. In the present context, with a cell-size of 2 m it is recommended not to use wave-lengths larger than 4-5m. Note also, that the smooth model step can be abandoned, should no longitudinal profile be required

Figure 13 Cell Definitions • Make model. This is done from the initial Area-tab. Press OK to close the opening window

of NaviModel

• Smooth Model. Care should be taken when applying this feature. A wave-length smaller the cell-size does not apply any improvement


Figure 14 Smooth Model • Create contours. Press the ‘Contour.. .’-icon and select the Create-tab. Insert a contour-

interval of 0.5 m, make sure that the decimals of the starting depth is either .00 m or .50 m and press the New-button. Now select the Smoothing-tab. In the same way as in connection with the smoothing of the model, care must be taken when smoothing the contours. In the present context it is not recommended to use a smoothing wave-length larger than two times the wave-length used for the model-smoothing (see Figure 15 and Figure 16)

Figure 15 Create Contours

Figure 16 Smooth Contours

LDA Page 18 of 23 Rev. no. 0, 2007-09-03


LDA Page 19 of 23 Rev. no. 0, 2007-09-03

• Create longitudinal profile (if required). Press the ‘Profiles..’-icon and choose the Curve-tab. Press the Load-button to load the file that defines the profiles-line. Check that the values for E/N and KP are correct. Now select the Profile-tab and choose the Longitudinal profile option. Press the Generate-button and type in the required name for saving

The generated longitudinal profiles must be used to compare the overlapping zones between the present and the previous survey-zones. A ‘perfect’ match must be established – otherwise tides must be edited according to the discrepancy and the processing process must be reinitiated.

In the present context, the contour-curves and the longitudinal profile constitute the end results of the postprocessing within NaviModel.

3.6 Proposed Method, Singlebeam Data The sequence in and content of singlebeam modelling is very similar to what is applied to the multibeam data: • Create new model-file

• Input the exported ASCII XYZ (.xyz) originating from NaviEdit

• Automatic cleaning of the data. A combination of size of 10 m, a perpendicular distance of 0.1 m and the 3-parameter plane function is likely to provide sensible results. Again: care should be taken regarding the perpendicular distance. Note, that no manual cleaning of the data is anticipated

• Choose cell type ‘Regular grid (Hexagon)’ and define cell size, collar width as well as depth data type. Values of cell size: 5m, collar width: 15 and a depth data type of ‘Average’ are proposed and should provide full coverage in the modeling area – otherwise the collar width must be increased. Alternatively cell type TIN (Triangular Irregular Network) can be chosen

• Make model. This is done from the initial Area-tab. Press OK to close the opening window of NaviModel

• Smooth Model. Care should be taken when applying this feature. In the present context, with a cell-size of 5 m it is recommended not to use wave-lengths larger than 12m. Again note, that the smooth model step can be abandoned, should no longitudinal profile be required

• Create contours. Press the ‘Contour..’-icon and select the Create-tab. Insert a contour-interval of 0.5 m, make sure that the decimals of the starting depth is either .00 m or .50 m and press the New-button. Now select the Smoothing-tab. Again it is not recommended to use a smoothing wave-length larger than two times the wave-length used for the model-smoothing

• Create longitudinal profile. Press the ‘Profiles..’-icon and choose the Curve-tab. Press the Load-button to load the file that defines the profiles-line. Check that the values for E/N and KP are correct. Now select the Profile-tab and choose the Longitudinal profile option. Press the Generate-button and type in the required name for saving


In the present context, the contour-curves constitute the end results of the postprocessing of the singlebeam data within NaviModel, whereas the longitudinal profile is only intended to be used for comparison to the longitudinal profile of the singlebeam data.

4. POSTPROCESSING WITHIN NAVIPLOT

The NaviPlot program is a fair sheet production software that provides facilities for lay out of survey data. The fair sheet comprises various elements and data types, and allows mixing of various mapping data in different frames for overlay with scale bar, colour palette, text, XY-grid and north arrow (see Figure 17).

Figure 17 NaviPlot

The lay-out is controlled by use of frames with the primary frame being the main frame around the whole of the sheet. New frames can be created either by mouse click-and-drag or by typing in the frame values. Existing frames can be deleted or changed/edited. The frames are organized in a tree-structure, so that every frame except the main frame has a parent frame. For every frame it

LDA Page 20 of 23 Rev. no. 0, 2007-09-03


LDA Page 21 of 23 Rev. no. 0, 2007-09-03

is possible to inherit properties from the parent frame as well as to create own properties. Created frame layouts can be stored as default templates.

The properties of a frame comprise among others: scale, origin, geodetic parameters, size and position of frame, pens used for drawing, name width, height etc. The frame behind a new frame will automatically be selected as the parent frame.

Map view is a frame containing XY plots. This view allows for display of various data types, such as: vector lines (display-lines, runlines, AutoCAD-files (*.dxf/*.dwg), contour lines (with filling), bathymetric plot, trackplot, geographical bitmaps, profiles (longitudinal as well as cross), coverages and sidescan mosaics. All map views are added as layers providing options like: stacking of layers, change of priority, delete layer and disable/enable display of layer. Coordinates (lines/ticks and labels) can be displayed in XY and/or in Lat/Long. Each label can be hidden if they overlap other labels. Labels are aligned to the frame edges.

The program supports import of the most commonly used file types, such as: contours (*.coa, *.cob), display/run lines (*.cur, *.dis, *.rln, *.rlx, *.rle, *.dxf, *.dwg) and geographic bitmaps (geotiff). Export file types supported comprise a/o AutoCAD vector drawing (*.dxf and *.dwg).

Plotting and printing is controlled through standard MS-Windows functions.

4.1 Proposed Method, Multibeam and Singlebeam Data In the present context the proposed sequence in producing fair sheets looks as follows: • Load the contour-template (contour-templatename.npt) by using the menu-item ‘File-Open’

or create a new NaviPlot file from scratch by using the menu-item ‘File-New’

• In the area left of the map-area, select the XY-frame and expand it. See that the frame is being highlighted in the map-area. Alternatively, if the project is started from scratch, a new frame, that spans the entire map-area, must be created. Right-click on the map-area, select ‘Add XY Data - Contours (*.coa)’ and select the contour-file in question for loading. Highlight the contour-file and check the settings of the contour-file at the bottom of the area left of the map-area (focus on labels and palette path)

• Choose menu-item ‘File-Export AutoCAD…’. Remember to choose ‘Save as type: AutoCAD 2004 (R18) (*.dwg)’

Further, should the project requirements include longitudinal profiles, the following steps must be followed:

• Load the longitudinal-template (longitudinal-templatename.npt) by using the menu-item ‘File-Open’ or create a new NaviPlot file from scratch by using the menu-item ‘File-New’

• In the area left of the map-area, select the XY-frame and expand it. Alternatively, if the project is started from scratch, a new frame, that spans the entire map-area, must be created. Right-click on the map-area, select ‘Add Profile(s) - Long profile (*.lpa)’ and select the


longitudinal profile in question for loading. Highlight the longitudinal profile and check the settings at the bottom of the area left of the map-area (focus on labels and palette path)

• Choose menu-item ‘File-Export AutoCAD…’. Remember to choose ‘Save as type: AutoCAD 2004 (R18) (*.dwg)’

The AutoCAD-file constitute the end result of the postprocessing within NaviModel and thus of the postprocessing to be performed in the EIVA postprocessing suite. The remaining postprocessing will be performed in AutoCAD.

Figure 18 Exported to AutoCAD

5. CONCLUSION

The present sequential manual introduces one way of utilizing the EIVA Hydrographic Postprocessing Suite. It is however regarded important, that final decisions and detailing on the

LDA Page 22 of 23 Rev. no. 0, 2007-09-03


LDA Page 23 of 23 Rev. no. 0, 2007-09-03

procedures must always be based upon actual experience, primarily accumulated in connection with postprocessing performed on the basis of data acquired under similar conditions. Having said this, the importance of eventually defining and implementing final and unambiguous procedures for the postprocessing work must be emphasized.

These procedures must clearly specify, as a minimum, the following (for multibeam as well as for singlebeam post-processing):

• Parameters for the de-selection of beams

• Extent of the rough check of sensor-data

• Required size of the boundaries/model areas

• Methods for tidal-correction (predicted tides/observed tides (bathy-height from GPS and/or from tidegauges/link to depths on pre-engineering survey)

• Parameters for the cleaning process (cell size, cell type (for singlebeam data), perpendicular distance and polynomial method)

• Parameters for the DTM (cell size, collar width and depth data type)

• Parameters for the smoothing of the model (wave-length)

• Parameters for the creation of contours and for the smoothing of these (contour-interval and wave-length for the smoothing)

• Size and scale of the contour- and profiles-plots

Date post:	17-Mar-2018
Category:	Documents
Upload:	trinhphuc
View:	216 times
Download:	2 times

Sequential Manual - EIVAdownload.eiva.dk/online-training/Sequential Manual - Postprocessing... · a...

Documents