Regarding the GMTplugin

253 views
Skip to first unread message

Fawz Naim

unread,
May 21, 2016, 7:11:02 AM5/21/16
to OpendTect Users
I am using the Opendtect version 6.0.0 . There is no GMT plugin visible on the window. Is the GMT plugin removed from this version ?
How can I use GMT then ?

chinmoy kumar

unread,
May 21, 2016, 11:04:54 AM5/21/16
to us...@opendtect.org
Dear Fawz,

OpendTect 6.0.0 is a pro version or the professional version. The GMT plugin is used for preparing maps. For that OpendTect 6.0.0 comes with an advanced pluging on GMT called as the Base Map
 It is teh base Map that solves all the issue related to interpretation map making

Regards
chinmoy

On Sat, May 21, 2016 at 3:15 PM, Fawz Naim <fawz...@gmail.com> wrote:
I am using the Opendtect version 6.0.0 . There is no GMT plugin visible on the window. Is the GMT plugin removed from this version ?
How can I use GMT then ?

--
You received this message because you are subscribed to the Google Groups "OpendTect Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to users+un...@opendtect.org.
To post to this group, send email to us...@opendtect.org.
Visit this group at https://groups.google.com/a/opendtect.org/group/users/.
To view this discussion on the web visit https://groups.google.com/a/opendtect.org/d/msgid/users/e327e66a-12e3-4651-ae67-73d3e05ac42d%40opendtect.org.
For more options, visit https://groups.google.com/a/opendtect.org/d/optout.



--
Thanks & Regards...
Priyadarshi Chinmoy Kumar
National Geophysical Research Institute
Hyderabad, Andhra Pradesh, India

Fawz Naim

unread,
May 22, 2016, 11:37:11 PM5/22/16
to us...@opendtect.org

Thank you sir

To view this discussion on the web visit https://groups.google.com/a/opendtect.org/d/msgid/users/CAELG2K_jZZsVWz5QYD-_LDYoRJ9ODfHK9RJd52rdU5gx_sqy6Q%40mail.gmail.com.

Farrukh Qayyum

unread,
May 22, 2016, 11:37:12 PM5/22/16
to us...@opendtect.org

Dear Fawz,

Can you try in 6.0.2? We started a case back in Feb/Mar when we knew that some things in GMT were not working initially. I would be glad to get your feedback if you are able to produce it or not. Please also state, in future, the OS and GMT version.

PS: Thanks Chinmoy for a nice comment on basemap. We believe that in near future users will just use this instead of GMT in OD.

Kind regards, Farrukh

On May 21, 2016 5:04 PM, "chinmoy kumar" <kumarc...@gmail.com> wrote:
To view this discussion on the web visit https://groups.google.com/a/opendtect.org/d/msgid/users/CAELG2K_jZZsVWz5QYD-_LDYoRJ9ODfHK9RJd52rdU5gx_sqy6Q%40mail.gmail.com.

Raman Singh

unread,
May 23, 2016, 12:12:57 AM5/23/16
to us...@opendtect.org
Dear Fawz,


There is no GMT plugin visible on the window.

I think you are talking about the missing GMT icon in the OpendTect main window. The icon has been removed to make the main window toolbar less cluttered. You can still find the option 'GMT Mapping Tool' under the Processing menu.

Best regards,

Raman K Singh
Manager Software Development
______________________________

dGB Earth Sciences, India
Phone: +91 22 25704984
Fax: +91 22 25704977
Mobile: +91 98 33452542
E-mail: raman...@dgbes.com
Internet: dgbes.com & opendtect.org
______________________________


David Castro

unread,
May 23, 2016, 10:07:15 PM5/23/16
to us...@opendtect.org

Hi everyone,

I would like to know how I can generate a 3D cube from paralel 2D GPR lines (DZT files).

I tried converting DZT files in either individual 2D SGY files or a single 3D SGY file using Reflexw, but when I import them to Opendtect a mensage pops up saying that the data are not inline/crossline sorted.

The x,y coordenates are in centimeters and the z aixs in ns.

Thank you in advance.

David


-- 
Dr. David Lopes de Castro
Prof. Associado III - UFRN
Tel.: (84) 3342-2277 R. 220
      (84) 99692-4443

G. Diephuis

unread,
May 24, 2016, 1:04:28 AM5/24/16
to us...@opendtect.org
Hello David,

I am not familiar with Reflexw – but I can give you the steps that I would take in SeismicUnix:
  1. Convert segy data to .su data
  2. choose a trace header as inline number and one as crossline number
  3. Change the headers with an arbitrary numbering system with "sushw" - the SU manual describes how this can be accomplished in one step
  4. Ensure that the coordinates are correctly filled out in "sx" and "sy"
  5. Sort the file with "susort" accrding to inlines
  6. Apply "segyheaders" - eventually edit the EBCDIC header
  7. Write out as SEG-Y file
Hope this helps

G. Diephuis

--
You received this message because you are subscribed to the Google Groups "OpendTect Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to users+un...@opendtect.org.
To post to this group, send email to us...@opendtect.org.
Visit this group at https://groups.google.com/a/opendtect.org/group/users/.

Julien Moreau

unread,
May 24, 2016, 2:52:55 AM5/24/16
to us...@opendtect.org

Dear David,
You need to organize your data into a regular grid (a sugar box)  for the software to load the data. So your line needs to have inline and crossline information for each trace. Xyz information is needed only for reference points in order to know what is the width, length and depth of a cell.
Either this information is populated be reflexW or you have to force it in the software. There are different solutions. Check the seg-y examiner in OpendTect and maybe have a look on SEG what is a SEG - Y and how it is formatted.
Good luck,
Julien Moreau

--
You received this message because you are subscribed to the Google Groups "OpendTect Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to users+un...@opendtect.org.
To post to this group, send email to us...@opendtect.org.
Visit this group at https://groups.google.com/a/opendtect.org/group/users/.
To view this discussion on the web visit https://groups.google.com/a/opendtect.org/d/msgid/users/8ee723bd-f94b-9d74-a809-34b9948c6692%40geologia.ufrn.br.

kjb44

unread,
May 26, 2016, 12:10:27 AM5/26/16
to us...@opendtect.org
Julien is right that your data needs to be loaded correctly using the right header keys. In the SEGY files this data will be somewhere typically like bytes 180-196 with keys being something like "cdpx, cdpy, iline, xline". Having these values written in the correct way makes life a lot easier

However there is a bit more to it than just that if you want things to work properly. Whilst things can work with irregular geometry it is best to regularise the files and bin the traces properly. Personally I was unable to get this to work in reflex, and found that I had to edit the SEGYs using SeismicUnix/Madagascar. The method I used can be very loosely described as:

1 - cat segy files into one file 
2 - export each segy file header
3 - regularise and bin traces using whatever method you fancy
4 - apply new geometry to your catted segy file
5 - profit

There are existing tools in both Su and Madagascar to achieve this. A good place to start getting your head around things is to carefully examine the original data geometry. Personally I do this in a GIS package such as QGIS, but that's just what I prefer. 

If anyone wants to add to my points please do. This is something I found quite difficult to achieve...

Regards, 

Kieran



Sent from Samsung Mobile
07817867142

Arnaud Huck

unread,
May 26, 2016, 3:04:44 AM5/26/16
to us...@opendtect.org
Dear all,

Thanks Kieran for this comprehensive workflow. Let me suggest you the sub steps that can be achieved in OpendTect, should you prefer that route:

Viewing the original data geometry: I would import each SEG-Y file as a 2D line, with their initial geometry. That can be done in one step, providing the all lines share the same header byte locations. Loading all 2D lines in the tree with the default display option will only show the lines geometry at the top of the survey. If you have access to OpendTect-PRO you can also view the geometries directly in the basemap.

-4- You can apply a new geometry to a 2D line from the 2D Geometry manager with the "import" option. Of course you will have imported the catted segy file beforehand as one 2D line, providing that a unique trace number is present in the trace headers. That should have been done as part of -3-. If not use the OpendTect SEG-Y manipulate tool to do it.

Best regards,
Arnaud Huck
Chief Geophysicist
________________________________

dGB Earth Sciences
Phone: +31 53 4315155
E-mail: arnau...@dgbes.com
Internet: dgbes.com & opendtect.org
________________________________

David Castro

unread,
May 26, 2016, 1:37:53 PM5/26/16
to us...@opendtect.org
Dear G. Diephuis, Julien Morea, Kieran and Arnaud Huck,

Fisrt of all, thank you for your help.

I was able to insert the X,Y coordinates in the fileheader of each GPR line and exported them in SEG-Y format.
I imported 2D SEG-Y files without problem in OpendTect.
However, I couldn't generate de 3D cube.
The SEG-Y Examiner shows that the X,Y coordinates (73, 77) and Inline (189) information of the imported files seems ok, but the Crossline information (193) is always null.
Because this problem I choose the X,Y coordinates to import the data. So, an error window popped out, saying that the input data is cross-line sorted and I should use the SEGY-scanned import method. Where can I find the SEGY-scanned import method?
I tried another approach creating a 3D SEG-Y file in Reflexw. This file contains inlines and cross-lines information (see attached PDF), but the same error message comes out, saying that I must use the SEGY-scanned import method again.
From this point on I can’t go further without help.
Please find attached an illustrated PDF file, showing these steps.
I thank you all in advanced.
Best regards,
David

-- 
Dr. David Lopes de Castro
Prof. Associado III - UFRN
Tel.: (84) 3342-2277 R. 220
      (84) 99692-4443
3D cube from parallel 2D GPR lines.pdf

Arnaud Huck

unread,
May 27, 2016, 3:18:52 AM5/27/16
to us...@opendtect.org
Dear David,

First there is something odd in the survey setup, in the coordinate settings part. You set the crossline of the first corner point to 23, while your crossline range is [0,8]. It should be 0 usually. The other corner points seem fine.
I see that you are using a beta version of the software. Please upgrade to the final version. The scanning of SEG-Y files is one of the many features we have improved during the beta phase, thus the SEG-Y scanned option is not at the same location between the beta version you are using and the final 6.0.0 release (or any subsequent).
Currently you will find that option in the last window of the SEG-Y wizard, under the "Copy data" option. You would need to switch from "Yes (import)" to "No (scan&link)".


Best regards,
Arnaud Huck
Chief Geophysicist
________________________________

dGB Earth Sciences
Phone: +31 53 4315155
E-mail: arnau...@dgbes.com
Internet: dgbes.com & opendtect.org
________________________________

David Castro

unread,
May 27, 2016, 8:22:02 AM5/27/16
to us...@opendtect.org

Hi Arnaud Huck,

Sorry, I sent the wrong image showing the survey parameters. This one is correct:



I updated OpendTect and used the new SEG-Y wizard. Using SEG-Y Revision 1 and X, Y coordinates, in-line/cross-line ranges and X,Y ranges seem to be correct.



To overcome the "cross-line sorted input data" problem I did as you suggested



However, the error message "No output cube produced" popped out. The SEG-Y scan report shows that the X,Y and in/cross-line information are lost


May I send you the 3D SEG-Y file? It is just 14 Mb.

I apoligize for such a problem.

Best regards,
David

Julien Moreau

unread,
May 27, 2016, 8:42:36 AM5/27/16
to us...@opendtect.org

Good afternoon,
The problem I see from your report is that you have a 12x12 grid in which your are supposed to have 12376 traces. There is a problem in the way the inline - X line are populated.
When you scan your file you have 23 inlines and 8 Xlines. I assume you have an issue there.
Best wishes,
Julien

...

Arnaud Huck

unread,
May 27, 2016, 8:48:09 AM5/27/16
to us...@opendtect.org
Dear David,

I forgot to mention another potential issue with your survey setup: It starts at 0/0. This means that all X or Y coordinates are equal to zero on the first inline or crossline, leading to these traces being rejected by our SEG-Y wizard.
Please shift your data (inl/crl and X/Y) to start at 1/1.

Julien is correct on the survey size: For 3D data your survey ranges should be large enough to contain all traces of datasets to be imported. Do not hesitate to make them much larger than required until you are setup.


Best regards,
Arnaud Huck
Chief Geophysicist
________________________________

dGB Earth Sciences
Phone: +31 53 4315155
E-mail: arnau...@dgbes.com
Internet: dgbes.com & opendtect.org
________________________________
--
You received this message because you are subscribed to the Google Groups "OpendTect Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to users+un...@opendtect.org.
To post to this group, send email to us...@opendtect.org.
Visit this group at https://groups.google.com/a/opendtect.org/group/users/.


OpendTect: winner of SEG's 
Distinguished Achievement Award

Reply all
Reply to author
Forward
0 new messages