From dave at stevens.com Thu Feb 4 16:12:25 2010 From: dave at stevens.com (J. D. STEVENS) Date: Thu, 4 Feb 2010 16:12:25 -0600 Subject: [GF] statistics and data loading speed Message-ID: I think I remember being able to defer calculations of volume statistics in order to expedite loading of 3d volumes to IESX. Can any of you provide information on that? Am I remembering something that never existed? X-) Dave -- Dave Stevens Dave at Stevens.COM STEVENS.COM, Inc. 713-419-0313 Bellville, TX, USA http://www.stevens.com From dave at stevens.com Thu Feb 4 18:54:43 2010 From: dave at stevens.com (J. D. STEVENS) Date: Thu, 4 Feb 2010 18:54:43 -0600 Subject: [GF] statistics and data loading speed In-Reply-To: References: Message-ID: Got it! In IESX xterm: setenv IESX_SDIX_NOSTART true proman This should suppress calculation of volume statistics during loading. After loading, you can use iesx_utils #32 to generate statistics on the volume. I have not tested the procedures. If you try them, please submit your experience. Thanks to Monika Sewell and her excellent connections for finding this obscure feature. Dave On Feb 4, 2010, at 4:12 PM, J. D. STEVENS wrote: > I think I remember being able to defer calculations of volume statistics in order to expedite loading of 3d volumes to IESX. Can any of you provide information on that? Am I remembering something that never existed? X-) > > Dave > -- > Dave Stevens Dave at Stevens.COM > STEVENS.COM, Inc. 713-419-0313 > Bellville, TX, USA http://www.stevens.com > > _______________________________________________ > GF mailing list > GF at stevens.com > http://lists.stevens.com/mailman/listinfo/gf -- Dave Stevens Dave at Stevens.COM STEVENS.COM, Inc. 713-419-0313 Bellville, TX, USA http://www.stevens.com From timi at agidee.com Mon Feb 8 01:47:23 2010 From: timi at agidee.com (Tim Agidee) Date: Mon, 8 Feb 2010 07:47:23 +0000 Subject: [GF] Exporting seismic data with exclusion polygon In-Reply-To: References: Message-ID: Dear All, We had a request to export a 3D survey from Geoframe but the company wanted to exclude an area with the survey due to licensing reasons. Is it possible in Geoframe? Thanks Timi _________________________________________________________________ Hotmail: Free, trusted and rich email service. http://clk.atdmt.com/GBL/go/201469228/direct/01/ From woollard at geocom.com.au Mon Feb 8 19:24:34 2010 From: woollard at geocom.com.au (Keith Woollard) Date: Tue, 09 Feb 2010 09:24:34 +0800 Subject: [GF] Exporting seismic data with exclusion polygon In-Reply-To: References: Message-ID: <4B70B952.6090704@geocom.com.au> Timi, I certainly don't know of a way, but we have a Linux utility that can do it on the exported segy. I suspect most transcription and/or processing companies will have something similar so you are probably best off exporting the lot and then sending it to get cut. Note that Kingdom can do it if you have a license, but the polygon is manually digitised, so not really accurate enough for this sort of work. Contact me off-list if you don't have a local company that can do the extraction Regards Keith On 8/02/2010 3:47 PM, Tim Agidee wrote: > Dear All, > > > > We had a request to export a 3D survey from Geoframe but the company wanted to exclude an area with the survey due to licensing reasons. Is it possible in Geoframe? > > > > Thanks > > > > Timi > > _________________________________________________________________ > Hotmail: Free, trusted and rich email service. > http://clk.atdmt.com/GBL/go/201469228/direct/01/ > _______________________________________________ > GF mailing list > GF at stevens.com > http://lists.stevens.com/mailman/listinfo/gf > > -- Keith Woollard Senior Consultant GeoCom Services Australia Pty Ltd (A.B.N. 63 068 362 498) Ph 61 (08)9243 3544 fx 61 (0)8 9246 9410 Email woollard at geocom.com.au Web www.geocom.com.au From woollard at geocom.com.au Wed Feb 10 02:09:20 2010 From: woollard at geocom.com.au (Keith Woollard) Date: Wed, 10 Feb 2010 16:09:20 +0800 Subject: [GF] Stuck in the 20th Century Message-ID: <4B7269B0.9040800@geocom.com.au> Just thought I would share the joy I am currently experiencing. I need to do some work overseas next week. 4 weeks ago I asked Schlumberger about transferring my license onto a laptop so I could travel with it. Get an answer today after several follow up calls, and just 48 hours before leaving, saying that I am not allowed to. You can't carry a license from one "geo-market" to another. no wonder people want to use Kingdom -- Keith Woollard Senior Consultant GeoCom Services Australia Pty Ltd (A.B.N. 63 068 362 498) Ph 61 (08)9243 3544 fx 61 (0)8 9246 9410 Email woollard at geocom.com.au Web www.geocom.com.au From syouens at talisman-energy.com Wed Feb 10 04:56:02 2010 From: syouens at talisman-energy.com (Youens, Simon) Date: Wed, 10 Feb 2010 17:56:02 +0700 Subject: [GF] Stuck in the 20th Century In-Reply-To: <4B7269B0.9040800@geocom.com.au> References: <4B7269B0.9040800@geocom.com.au> Message-ID: <1A63386B4F899F47BFA77D53BB4F45F55F779C@HCMEXCH01.asia.tlm.com> Keith, Bad news but why am I not surprised? I suppose Big Blue's solution would be to buy another license in the correct "geo-market". My run-in with the behemoth this week is on a smaller scale. I wanted to be able to load some "fault polygons" exported from SMT into IESX as "fault boundaries". Over two days now, with no solution for a simple ASCII load. I discovered today that we pay over $15,000 per month for "maintenance". Words fail me. Regards, Simon ______________________ Simon Youens Senior Geophysicist Talisman Vietnam Limited -----Original Message----- From: gf-bounces at stevens.com [mailto:gf-bounces at stevens.com] On Behalf Of Keith Woollard Sent: Wednesday, February 10, 2010 3:09 PM To: gf at stevens.com Subject: [GF] Stuck in the 20th Century Just thought I would share the joy I am currently experiencing. I need to do some work overseas next week. 4 weeks ago I asked Schlumberger about transferring my license onto a laptop so I could travel with it. Get an answer today after several follow up calls, and just 48 hours before leaving, saying that I am not allowed to. You can't carry a license from one "geo-market" to another. no wonder people want to use Kingdom -- Keith Woollard Senior Consultant GeoCom Services Australia Pty Ltd (A.B.N. 63 068 362 498) Ph 61 (08)9243 3544 fx 61 (0)8 9246 9410 Email woollard at geocom.com.au Web www.geocom.com.au _______________________________________________ GF mailing list GF at stevens.com http://lists.stevens.com/mailman/listinfo/gf From brian.stevens at dataporters.com Wed Feb 10 08:24:51 2010 From: brian.stevens at dataporters.com (Brian Stevens) Date: Wed, 10 Feb 2010 08:24:51 -0600 Subject: [GF] Stuck in the 20th Century In-Reply-To: <1A63386B4F899F47BFA77D53BB4F45F55F779C@HCMEXCH01.asia.tlm.com> References: <4B7269B0.9040800@geocom.com.au> <1A63386B4F899F47BFA77D53BB4F45F55F779C@HCMEXCH01.asia.tlm.com> Message-ID: I recently spent a couple of days with a client migrating a project from GF to SMT. We spent a fair amount of time exporting GF "fault boundaries", massaging the output, and importing them into SMT as "fault polygons". I haven't done the reverse, but let me know if you have any specific issues with which I might be able to help. We found a lot of issues [in general] in moving polygons (i.e. culture) between the two. GF apparently has the concept of "open" and "closed" polygons, where SMT has "polygons" and "lines", so many of the "closed polygons" (i.e. counties, blocks, etc) in GF showed up as "open polygons" in SMT (i.e. missing a segment) until we massaged the data (duplicating the first point as the last point in the polygon before loading into SMT). I've decided GF "maintenance" means "software updates". In my experience, GF "support" spends 90% of their time trying to blame the issue on the customer['s database]. I hope this forum gains momentum to promote the exchange of useful information and tips amongst the GF user community! Brian Stevens Systems Administration Consultant Data Porters, LLC brian.stevens at dataporters.com (713) 419-6250 On Feb 10, 2010, at 4:56 AM, Youens, Simon wrote: > Keith, > > Bad news but why am I not surprised? I suppose Big Blue's solution > would > be to buy another license in the correct "geo-market". > > My run-in with the behemoth this week is on a smaller scale. I > wanted to > be able to load some "fault polygons" exported from SMT into IESX as > "fault boundaries". Over two days now, with no solution for a simple > ASCII load. > > I discovered today that we pay over $15,000 per month for > "maintenance". > Words fail me. > > > Regards, > Simon > ______________________ > Simon Youens > Senior Geophysicist > Talisman Vietnam Limited > > -----Original Message----- > From: gf-bounces at stevens.com [mailto:gf-bounces at stevens.com] On Behalf > Of Keith Woollard > Sent: Wednesday, February 10, 2010 3:09 PM > To: gf at stevens.com > Subject: [GF] Stuck in the 20th Century > > Just thought I would share the joy I am currently experiencing. > > I need to do some work overseas next week. 4 weeks ago I asked > Schlumberger about transferring my license onto a laptop so I could > travel with it. Get an answer today after several follow up calls, and > just 48 hours before leaving, saying that I am not allowed to. You > can't > > carry a license from one "geo-market" to another. > > no wonder people want to use Kingdom > > -- > Keith Woollard > Senior Consultant > GeoCom Services Australia Pty Ltd (A.B.N. 63 068 362 498) > Ph 61 (08)9243 3544 fx 61 (0)8 9246 9410 > Email woollard at geocom.com.au > Web www.geocom.com.au > > _______________________________________________ > GF mailing list > GF at stevens.com > http://lists.stevens.com/mailman/listinfo/gf > _______________________________________________ > GF mailing list > GF at stevens.com > http://lists.stevens.com/mailman/listinfo/gf From dave at stevens.com Wed Feb 10 10:25:18 2010 From: dave at stevens.com (J. D. Stevens) Date: Wed, 10 Feb 2010 10:25:18 -0600 Subject: [GF] Stuck in the 20th Century In-Reply-To: <1A63386B4F899F47BFA77D53BB4F45F55F779C@HCMEXCH01.asia.tlm.com> References: <4B7269B0.9040800@geocom.com.au> <1A63386B4F899F47BFA77D53BB4F45F55F779C@HCMEXCH01.asia.tlm.com> Message-ID: <4B72DDEE.5030702@stevens.com> Simon, Several years ago when I was doing a fair amount of data loading and management for GeoFrame systems, I used Perl to condition ascii data for loading to projects. We did some card image 7 stuff, some LAS stuff, some navigation conversions, some amplitude conversions, etc. Some of the scripts were good enough that someone at Schlumberger removed my copyright notice and included my script as part of Schlumberger's support effort. The copyright notice included permission to use as long as attribution was maintained. (OK. I've expressed my complaint.) The point is that we may be able to help out with conversions where an intermediate medium is an ascii file. Brian Stevens of DataPorters, LLC, certainly has the expertise and some recent experience in conversions. I have some experience as well. I expect other subscribers may have tools that are available to share. If we have samples of a given kind of data in ascii format from each system, we should be able to develop a program that would convert the data. I have an ftp server that could be used as a medium of exchange for anything that is not appropriate to share via email. I expect several of us could help each other out. Please use this opportunity to collaborate. Dave > I recently spent a couple of days with a client migrating a project > from GF to SMT. We spent a fair amount of time exporting GF "fault > boundaries", massaging the output, and importing them into SMT as > "fault polygons". I haven't done the reverse, but let me know if you > have any specific issues with which I might be able to help. We found > a lot of issues [in general] in moving polygons (i.e. culture) between > the two. GF apparently has the concept of "open" and "closed" > polygons, where SMT has "polygons" and "lines", so many of the "closed > polygons" (i.e. counties, blocks, etc) in GF showed up as "open > polygons" in SMT (i.e. missing a segment) until we massaged the data > (duplicating the first point as the last point in the polygon before > loading into SMT). > > I've decided GF "maintenance" means "software updates". In my > experience, GF "support" spends 90% of their time trying to blame the > issue on the customer['s database]. I hope this forum gains momentum > to promote the exchange of useful information and tips amongst the GF > user community! > > > Brian Stevens > Systems Administration Consultant > Data Porters, LLC > brian.stevens at dataporters.com > (713) 419-6250 > > > On Feb 10, 2010, at 4:56 AM, Youens, Simon wrote: > >> Keith, >> >> Bad news but why am I not surprised? I suppose Big Blue's solution >> would >> be to buy another license in the correct "geo-market". >> >> My run-in with the behemoth this week is on a smaller scale. I >> wanted to >> be able to load some "fault polygons" exported from SMT into IESX as >> "fault boundaries". Over two days now, with no solution for a simple >> ASCII load. >> >> I discovered today that we pay over $15,000 per month for >> "maintenance". >> Words fail me. >> >> >> Regards, >> Simon >> ______________________ >> Simon Youens >> Senior Geophysicist >> Talisman Vietnam Limited >> >> -----Original Message----- >> From: gf-bounces at stevens.com [mailto:gf-bounces at stevens.com] On Behalf >> Of Keith Woollard >> Sent: Wednesday, February 10, 2010 3:09 PM >> To: gf at stevens.com >> Subject: [GF] Stuck in the 20th Century >> >> Just thought I would share the joy I am currently experiencing. >> >> I need to do some work overseas next week. 4 weeks ago I asked >> Schlumberger about transferring my license onto a laptop so I could >> travel with it. Get an answer today after several follow up calls, and >> just 48 hours before leaving, saying that I am not allowed to. You >> can't >> >> carry a license from one "geo-market" to another. >> >> no wonder people want to use Kingdom >> >> -- >> Keith Woollard >> Senior Consultant >> GeoCom Services Australia Pty Ltd (A.B.N. 63 068 362 498) >> Ph 61 (08)9243 3544 fx 61 (0)8 9246 9410 >> Email woollard at geocom.com.au >> Web www.geocom.com.au >> -- Dave Stevens Dave at Stevens.COM STEVENS.COM, Inc. 713-419-0313 Bellville, TX, USA http://www.stevens.com From syouens at talisman-energy.com Thu Feb 11 19:13:54 2010 From: syouens at talisman-energy.com (Youens, Simon) Date: Fri, 12 Feb 2010 08:13:54 +0700 Subject: [GF] Polygon Loading (RE: Stuck in the 20th Century) In-Reply-To: <4B72DDEE.5030702@stevens.com> References: <4B7269B0.9040800@geocom.com.au> <1A63386B4F899F47BFA77D53BB4F45F55F779C@HCMEXCH01.asia.tlm.com> <4B72DDEE.5030702@stevens.com> Message-ID: <1A63386B4F899F47BFA77D53BB4F45F55F78C0@HCMEXCH01.asia.tlm.com> Dave, Thanks for the offer of help. Here's a sample of the polygon file I am trying to load. It's the Kingdom export format. I have listed the first two polygons and part of the third: 364831.608 923119.661 0.000 6 1 364362.222 923698.810 0.000 7 1 363481.459 921982.793 0.000 7 1 363060.608 921729.521 0.000 7 1 362365.538 921308.671 0.000 7 1 361521.933 920699.295 0.000 7 1 360910.652 920362.233 0.000 7 1 361838.047 920655.496 0.000 7 1 363616.906 921182.987 0.000 7 1 363546.205 921771.416 0.000 7 1 364325.064 922445.538 0.000 8 1 367663.029 921680.852 0.000 6 2 366979.672 921484.447 0.000 7 2 365882.405 921125.725 0.000 7 2 365416.553 920838.423 0.000 7 2 366009.012 921052.683 0.000 7 2 367213.409 921448.737 0.000 8 2 370419.182 925979.022 0.000 6 3 370024.750 925605.692 0.000 7 3 369430.668 924904.480 0.000 7 3 368796.006 924211.383 0.000 7 3 ............ I can easily reformat if required. What I need is a list of instructions on how to find the appropriate place to load these polygons. Where is it buried in the Geoframe labyrinth and can someone provide me with a cookbook approach as to how to do it? I almost always have to have several goes at loading ASCII data, because I usually forget some obscure but critical piece of information. I've been using GeoFrame for 7 months now. I figure that I am about 50-60% efficient compared to Kingdom AND I've got carpal tunnel syndrome from all the extra mousing required! I still haven't heard back from my local GeoFrame support team. Regards, Simon ______________________ Simon Youens Senior Geophysicist Talisman Vietnam Limited From dave at stevens.com Fri Feb 12 18:20:02 2010 From: dave at stevens.com (J. D. STEVENS) Date: Fri, 12 Feb 2010 18:20:02 -0600 Subject: [GF] Polygon Loading (RE: Stuck in the 20th Century) In-Reply-To: <1A63386B4F899F47BFA77D53BB4F45F55F78C0@HCMEXCH01.asia.tlm.com> References: <4B7269B0.9040800@geocom.com.au> <1A63386B4F899F47BFA77D53BB4F45F55F779C@HCMEXCH01.asia.tlm.com> <4B72DDEE.5030702@stevens.com> <1A63386B4F899F47BFA77D53BB4F45F55F78C0@HCMEXCH01.asia.tlm.com> Message-ID: Simon, I expect this needs to load as a polygon in a culture layer. I need to check with my loading experts on the exact place for loading and the format for loading. It has been about eight years since I personally loaded some information. It will be Tuesday before I have good access to my colleagues who have currently loading experience. Perhaps someone else can provide some support before then. Dave On Feb 11, 2010, at 7:13 PM, Youens, Simon wrote: > Dave, > > Thanks for the offer of help. > > Here's a sample of the polygon file I am trying to load. It's the > Kingdom export format. I have listed the first two polygons and part of > the third: > > 364831.608 923119.661 0.000 6 1 > 364362.222 923698.810 0.000 7 1 > 363481.459 921982.793 0.000 7 1 > 363060.608 921729.521 0.000 7 1 > 362365.538 921308.671 0.000 7 1 > 361521.933 920699.295 0.000 7 1 > 360910.652 920362.233 0.000 7 1 > 361838.047 920655.496 0.000 7 1 > 363616.906 921182.987 0.000 7 1 > 363546.205 921771.416 0.000 7 1 > 364325.064 922445.538 0.000 8 1 > 367663.029 921680.852 0.000 6 2 > 366979.672 921484.447 0.000 7 2 > 365882.405 921125.725 0.000 7 2 > 365416.553 920838.423 0.000 7 2 > 366009.012 921052.683 0.000 7 2 > 367213.409 921448.737 0.000 8 2 > 370419.182 925979.022 0.000 6 3 > 370024.750 925605.692 0.000 7 3 > 369430.668 924904.480 0.000 7 3 > 368796.006 924211.383 0.000 7 3 > ............ > > I can easily reformat if required. What I need is a list of instructions > on how to find the appropriate place to load these polygons. Where is it > buried in the Geoframe labyrinth and can someone provide me with a > cookbook approach as to how to do it? > > I almost always have to have several goes at loading ASCII data, because > I usually forget some obscure but critical piece of information. > > I've been using GeoFrame for 7 months now. I figure that I am about > 50-60% efficient compared to Kingdom AND I've got carpal tunnel syndrome > from all the extra mousing required! > > I still haven't heard back from my local GeoFrame support team. > > Regards, > Simon > ______________________ > Simon Youens > Senior Geophysicist > Talisman Vietnam Limited > > -- Dave Stevens Dave at Stevens.COM STEVENS.COM, Inc. 713-419-0313 Bellville, TX, USA http://www.stevens.com From MSewell at nobleenergyinc.com Fri Feb 12 22:43:46 2010 From: MSewell at nobleenergyinc.com (MSewell at nobleenergyinc.com) Date: Fri, 12 Feb 2010 22:43:46 -0600 Subject: [GF] Polygon Loading (RE: Stuck in the 20th Century) Message-ID: Ok, this is what you will need to load as a fault polygon into geoframe: X Y segment_ID z_value fault_name The segment_id is what defines each polygone. For example, 123.5 456.5 1 0.0 f_fault 124.5 457.5 1 0.0 f_fault 123.5 456.5 1 0.0 f_fault 122.5 446.5 2 0.0 g_fault 129.5 448.5 2 0.0 g_fault 122.5 446.5 2 0.0 g_fault Notice the pattern, each fault polygon is identified by the segment_id number. Also, if you want a closed polygon, first and last point of polygon are the same. The Z value doesn't have to be a real value, it can be 0, but it has to be there as a place holder. The fault name has to be in the file as well. You can override the fault name if you like but it still has to be in the file. Lastly, you make an import file in the interp export box to match the file you are importing. Take one that starts as fb_(blah blah) and change the end or add to it. In order to use the format file to imort you will only see it if the first part is the same as the default format file names. This should get you your fault polygons imported into geoframe. It helps if you can do shell scripting to reformat the data file, but that just makes life easier. Monika ----- Original Message ----- From: "J. D. STEVENS" [dave at stevens.com] Sent: 02/12/2010 06:20 PM CST To: Simon Youens ; gf at stevens.com Subject: Re: [GF] Polygon Loading (RE: Stuck in the 20th Century) Simon, I expect this needs to load as a polygon in a culture layer. I need to check with my loading experts on the exact place for loading and the format for loading. It has been about eight years since I personally loaded some information. It will be Tuesday before I have good access to my colleagues who have currently loading experience. Perhaps someone else can provide some support before then. Dave On Feb 11, 2010, at 7:13 PM, Youens, Simon wrote: > Dave, > > Thanks for the offer of help. > > Here's a sample of the polygon file I am trying to load. It's the > Kingdom export format. I have listed the first two polygons and part of > the third: > > 364831.608 923119.661 0.000 6 1 > 364362.222 923698.810 0.000 7 1 > 363481.459 921982.793 0.000 7 1 > 363060.608 921729.521 0.000 7 1 > 362365.538 921308.671 0.000 7 1 > 361521.933 920699.295 0.000 7 1 > 360910.652 920362.233 0.000 7 1 > 361838.047 920655.496 0.000 7 1 > 363616.906 921182.987 0.000 7 1 > 363546.205 921771.416 0.000 7 1 > 364325.064 922445.538 0.000 8 1 > 367663.029 921680.852 0.000 6 2 > 366979.672 921484.447 0.000 7 2 > 365882.405 921125.725 0.000 7 2 > 365416.553 920838.423 0.000 7 2 > 366009.012 921052.683 0.000 7 2 > 367213.409 921448.737 0.000 8 2 > 370419.182 925979.022 0.000 6 3 > 370024.750 925605.692 0.000 7 3 > 369430.668 924904.480 0.000 7 3 > 368796.006 924211.383 0.000 7 3 > ............ > > I can easily reformat if required. What I need is a list of instructions > on how to find the appropriate place to load these polygons. Where is it > buried in the Geoframe labyrinth and can someone provide me with a > cookbook approach as to how to do it? > > I almost always have to have several goes at loading ASCII data, because > I usually forget some obscure but critical piece of information. > > I've been using GeoFrame for 7 months now. I figure that I am about > 50-60% efficient compared to Kingdom AND I've got carpal tunnel syndrome > from all the extra mousing required! > > I still haven't heard back from my local GeoFrame support team. > > Regards, > Simon > ______________________ > Simon Youens > Senior Geophysicist > Talisman Vietnam Limited > > -- Dave Stevens Dave at Stevens.COM STEVENS.COM, Inc. 713-419-0313 Bellville, TX, USA http://www.stevens.com _______________________________________________ GF mailing list GF at stevens.com http://lists.stevens.com/mailman/listinfo/gf From syouens at talisman-energy.com Fri Feb 26 02:48:41 2010 From: syouens at talisman-energy.com (Youens, Simon) Date: Fri, 26 Feb 2010 15:48:41 +0700 Subject: [GF] Fault Boundary Loading from SMT Fault Polygon files In-Reply-To: References: Message-ID: <1A63386B4F899F47BFA77D53BB4F45F55F7F15@HCMEXCH01.asia.tlm.com> Dear All, I've been busy loading (or trying to load) fault boundary polygons and have some feedback for everyone. 1. Only use Applications, Data Manager, Interp-Import. Do not try to use Data Management, Loaders and Unloaders, ASCII load. I could never get it to work. Life's too short. 2. Use the Interp-Export selection to view and/or modify an appropriate file format and then export some existing fault polygons to create an example file to help you create your own file. 3. I started with the 'fbm_gf.ifdf' format file and modified it. The default format truncates long horizon and fault names, so this needs to be fixed. 4. Use Excel or a script to create the input polygon file. In the case of the SMT fault polygon files, you will need to repeat the first point in a polygon at the end of the polygon, in order to close it. Contact me offline if you want advice on how to do this in Excel. 5. WARNING. Do as I say and not as I did. If you have a horizon name in your input file, which I like to do, so that I don't have to remember to 'override' anything, MAKE SURE this horizon exists before you try to load the file. 6. If you try to load a file associated with a non-existent horizon, not only will the load fail, but IESX will 'hang' and you have to exit Geoframe and restart. A serious bug, which I have reported. 7. However, there is no problem with non-existent fault names. An appropriate fault will be created. Regards, Simon ______________________ Simon Youens Senior Geophysicist Talisman Vietnam Limited