INTREPID and Sea-g run on most of the "traditional" x86_64 PCs or workstations. 32-bit platforms are no longer supported.
Intel / AMD x86_64 processors which support AVX instruction set.
Intel Sandy Bridge (introduced Jan 2011) or above; To use the embedded Intel HD graphics, Intel Broadwell CPUs (introduced Jun 2015) or later is a must.
AMD Bulldozer (introduced Late 2011) or above.
8GiB minimum, recommend 16GiB or more.
This depends mainly on the size of customer's dataset. INTREPID itself requires at least 3GB disk space.
|nVidia does not support OpenGL acceleration over Microsoft Remote Desktop Protocol on its GeForce products.|
To run our software on a remote PC using RDP, an nVidia Quadro or AMD products have to be chosen.
All graphics cards supporting OpenGL 4.3 and above, with the latest driver from the vendor, are supported.
AMD Radeon HD 77xx or newer, introduced in early 2012;
nVidia GeForce 400 series introduced in late 2010, or newer, except GeForce 405 for OEM market;
Intel HD Graphics 8th Gen or newer, seen on 5th gen Intel i3, i5, i7 CPUs.
Operating System and Other Software
Microsoft Windows 7, Windows 10: 64-bit, preferably Professional or Ultimate.
INTREPID also provides experimental supports Ubuntu 16.04 LTS 64-bit or newer;
Please contact us for available versions.
Go to Help-> Intrepid Release Notes
For best performance:
- Close other applications
- Meet or exceed systems requirements for Intrepid
- Reserve 10-20 times the size of the input datasets on the storage media where the temp directory of Intrepid is found ($INTREPID\temp). If needed, you may configure Intrepid to use another directory for its temporary storage via File->Configure temporary directory
- Work on an SSD rather than HDD
There are a few different ways to create a database from a grid, the most flexible one is the dataset resampler (INTREPID Main Menu -> Dataset -> last entry [dataset resampler]).
The steps are:
- Start the dataset resampler
- Load the reference grid
- Tick on trace profile path and digitise the first line of your survey design i.e. bottom left at right-angles to strike (i.e., East-West if general strike is north-south). Does not need to be accurate, it is just a starting point.
- Open the: Survey Plan-> Design Survey plan and design the survey line spacing and sample spacing for Murthy and Rao. Edit the coordinates of your first line to do whatever you want. The tool works on number of lines and line spacings. You can also choose your sample spacing along line. You need at least two or three tielines in order to give it the width of your survey.
- Save the survey plan as a text file (mysvyplan.txt) using Survey Plan-> Save Survey Plan
- Leave the tool and start as at the first step, but don't digitise just load the survey plan
- Go to File menu and choose Save Profile paths as line dataset/database
- Now Load profile paths as line dataset
- Now Save Reference to loaded dataset - this samples your grid (gravity) into the Line database. This is what you need for Murthy and Rao. You need at least a line number and it is also handy to have a FID. You can generate this in Dbedit ie. Create new field and initialise with Row()
- Gravity must be in Milligals for Murthy and Rao.
- You should also sample your DTM into the Murthy and Rao database. You will need this later to convert the Murthy and Rao depths below surface to elevations for Geomodeller.
On principle, Intrepid has no limits on the size of aeromagnetic data.
Users have been reporting levelling jobs up to 250k cross-over data points.
The Reduction filter on the Grid FFT Filter tool allows to automatically adjust the filter shape for low inclinations.
After specifying Reduction to Pole, select the Low Inclination option and run the filter with various Inclination Limit Parameters.
The strike angle in the Euler points database is a conventional strike direction not a dip direction; No dip is calculated so the strike direction does not imply a dip direction ie the Right hand rule does not apply.
In the Euler database there will be both positive and negative strike angles (0 to 180 and 0 to -180. Prior to import to Geomodeller it is recommended that you convert them all to positive angles ie 0 -360 so that they are conventional azimuths.
Worme (Multi-scale edge detection):
The worme tool produces a points database and each point is attributed with a conventional strike direction as for Euler; it reports a true 0-360 degree azimuth so no conversion is required; this strike is directly reflected in the worme linear contained in the worme lines database or the worme shape file which is formed by joining the points.
The Obs_Dip in Euler output datasets is defined as the dip from the current point of observation of the field to the calculated source body is a good filter for rejecting poorly conditioned solutions. The deconvolution process ensures there are clusters of solutions around the causitive bodies and those solution estimates that derive from further away for shallow bodies are suspect.
Yes, the estimated depth error from the least squares estimation in fact has quite a good correlation with the general form of the estimated depth function.
This is why historically the error or depth is used as a rejection criterion.
Clustering and other discrimination criterion can help reduce the noise in the results in a more compelling way.
The input grid for Microlevelling should a grid which is free of line to line busts. Usually this will be the output grid generated from running the Decorrugation tool. However, any grid can be used.
The Decorrugation tool typically takes as input a tie-line levelled grid (or the best levelled grid you have) and removes linear features from it to produce a decorrugated grid. The filter parameters in the decorrugation tool control the degree of decorrugation (and loss of signal) that takes place. If you use the decorrugation tool to output a Levelled grid (under Grid Output) you can visually check it before doing the microlevelling. The Decorrugate tool has to work along grid columns or rows so if your dataset was flown with angled lines you'll need to rotate the grid.
The microlevelling tool creates a new database channel using the input decorrugated grid. If you then grid that channel you should end up with essentially the same grid as the input grid.
Bisplining is set to work in a specified direction defined by a rotation angle with default value 0 (NS).
- for a bearing of 90, it will spline (NS) for lines which have a bearing within 70-110 degs (+-20 from 90)
- for a bearing of 0 it will spline EW for lines bearing 340-020.
- for a bearing of 45 you will have to select "rotate dataset". Otherwise, the splining algorithm will not able to cross many nodes and the output grid will be mostly blank.
Projection attributes in Intrepid may be changed by editing existing files in the $INTREPID_INSTALL
New projection files must be adds to the
proj.csv file so that Intrepid may recognize them.
Is is highly recommended to make a backup of the files before and after any changes to the contents of the $INTREPID_INSTALL
Yes, if you supply us with new projections or edits to existing ones, we can include them in our distribution.
Yes, Intrepid may import/export to .shp format.
Export of vector components of Intrepid maps to to ESRI shapefiles (.shp) is supported by creating and running a job file.
Export to ESRI Shape File
To export the contours and other map elements as an ESRI Shape file you will need to:
- Specify Arc format in the Map file
- Create and run a job file from Project Manager
Updating the map file with Arc format
- Open the map file in a text editor
- Add the line “call = arcshape” to the map file as the first line.
Creating and running job file
- Using a text editor create the following text file and give it a .job extension
Name = mapprint
Input = ./contour_to_shape.map
Output = ./contour_to_shape
- In the example above:
The Output parameter is the file name of the output Shape file
- In Project Manager right click on the job file – Select Run Job
Yes, the Intrepid Spreadsheet Editor supports this filter.
This filter uses the statistics of one channel to influence, in a non-linear sense, another channel.
It is mainly used in Radiometrics to guide the Uranium channel filtering with the Total Count channel statistics.
Go to Filtering > Grid Convolution > Preset Kernels > CNorm
These filters allow magnetic datasets to be standardized to remove the effect of the local inclination and declination of the Earth's magnetic field.
Variation in the magnetic data should theoretically be only due to subsurface geometry of magnetic bodies.
Intrepid calculates the Geomagnetic Reference Field using published models from Geoscience Australia for epochs that run for groups of 5 years starting from 1940 to 2010.
These models are synonymous with the IGRF models.
This is used automatically in levelling and grid filtering as well as in Naudy Deconvolution and line filtering for component calculations.
The .grd/.GRD file extension may correspond to one of three common formats:
- ESRI grids => supported for import and export
- Geosoft grids => supported for import and export
- Surfer grids => unsupported for import and export
If you are having difficulties importing .grd files into Intrepid, make sure that they are not in the Surfer format.
For details on contour generation please refer the client to user manual Map Composition (T45).
- The map composition tool is under "Mapping"-> "Map Composition"
- Simple contours for any grid can be created in "Map Composition" -> "Geographic" -> "New Contour"
- Within the menu of these tools select grid file and under "Contour Cuts" the interval, density, line thickness, line colour and annotations.
- Please note that all the contours may not display on screen at this time. Contours on the screen are thinned out to prevent overlap.
- Save as map.
For detailed parameter configuration refer to the manual.
Viewing on screen
- To view the contours and other map elements on screen use the MapPrint tool.
- "Mapping" -> "Print Map"
- Open Map to render on screen.
In the Map above UTM coordinates are annotated using a grid on the Left and Top edge. Latitude and Longitude coordinates are annotated on the Right and Bottom edge. The best results are achieved by creating an annotation and then editing the Map file to fine tune the results.
- In Map Composition -> Geographic -> New Lat/Lon Ticks
- Setup Latitude and Longitude intervals, Label location, type of Ticks and text parameters.
For the interval you can use either decimal degrees 0.001 or Degrees Minutes Seconds 0:0:30
- File - > SaveAs Map
- An alternative way to edit the annotation parameters is to open the Map file in a text editor and edit the LongInterval and Latinterval parameters.
X = 0
Y = 0
Detail = Full
MetreGrid = No
LongInterval = 0:0:30
LatInterval = 0:0:30
Format = DMS
LabelAtBottom = Yes
LabelAtRight = Yes
Style = Tick
Internal = No
TextSize = 1
TextFont = 0
TextThickness = 0
TickSize = 1
TickThickness = 0
LabelOffset = 0
When you open the Map using Map Composition or MapPrint the Latitude and Longitude ticks will now be visible
- Open Map using Map Composition tool
- Double click on the contours and Select “Contour” as Object to Edit.
- This will reopen the Contour dialog box
- Select Contour cuts
Tick Annotate and click on Annotate Settings
Edit Contour label parameters and click Apply
- After Applying changes and refreshing the screen, contour annotations will be plotted