You can convert a single well top set to a points object.
Select (check the box) the well top you want to be points.
Right-click on an attribute for the tops layer (e.g., Z)
Select “Convert to points (using filter)
You will get a new points object.
This wasn’t documented anywhere (maybe it’s obvious?), but here is a short example using the included ‘bot’ dataset.
# Look at the existing factors, stored in bot@fac
# Add another arbitrary factor
# Put your new factors back into the object
# Look at your data based on the new factor
If you are just using zones as stratigraphic tops in Techlog and are manipulating data in Zone Editor, you can hit Ctrl-A to not show the zone bottoms (which will be -9999 if you aren’t using them). Hit it again to toggle back.
Just downloaded Petrel 2014 yesterday and loaded up a v2013 project I’ve been working on. For some reason, the stratigraphic tops are not visible in 2D or 3D windows (but the data are there, and can be exported). Has anyone else had this problem?
If you’re interested in exporting a list of well logs associated with a particular well (or selection of wells), the correct menu item is not under Project->Export…, it’s Logs->Log Summary Report…
Question: How do you get statistics on log values (variable values*) for a given well? How about a given zone in that well?
Answer**: In Techlog 2013.2.0 (not 2011 as far as I could tell), you can do this with the Statistics tool.
Select a variable from one of the wells and move it to the “Data type assignment” pane with the “Variables >” button and click “Create”
Drag a well from your Project Browser to the Input pane of the Workflow Manager (right side).
Click the Statistics tab in the Workflow Manager (right side).
Click the purple “Play” button to compute statistics for your selection.
One well with zones:
Proceed to step 3, above.
Open the Zonation pane in the Project Browser.
Select the zones you want to calculate statistics for.
Open the Zonation tab in the Workflow Manager.
Click the icon for “Insert zones from the zonation dock window.”
Go to step 4, above.
I hope this helps someone at least a little bit.
*”Variables” are what Techlog calls digital logs. Each type of log is a different variable.
**Drawing somewhat from this knowledge base article.
I hope to someday put together a tagged database of figures pulled from the geological literature that may be useful to others, primarily maps and stratigraphic columns. For now, though, I am sharing an Evernote notebook to which I will be adding over time. It can be accessed here:
https://www.evernote.com/pub/matthewbk/publicimages [EDIT: No longer. 2014-02-04]
Future plans include tagging the images (type of map, area covered, stratigraphic units) but I am not sure of the platform to use. Tumblr, Blogger, or even Pinterest (in addition to the possibility of Drupal) are all possibilities at this point that will allow collaboration.
This one took me a couple days to figure out. When trying to import new symbols into SedLog 3.0, I kept running into an error “Unable to read this file: <filepath.svg>.” It turns out that the 64-bit version of Windows 7 is getting in the way somewhere.
To solve this problem, you can download and run the installer again, but first do the following:
- right-click on the installer file (sedlog-3.0-setup.exe),
- select the “Compatibility” tab,
- check the box “Run this program in compatibility mode for:” and select “Windows XP (Service Pack 3),”
- check the box “Run this program as an administrator.”
Run the installer. You should now be able to create and import SVG graphics per the official instructions.
Additional note on the SVG graphics: in Adobe Illustrator CS6, you should reduce the size of the artboard so that it is the same size as (or only slightly lager than) the symbol graphic. It also looks like the maximum size for an SVG image to fit the entire symbol is about 42×42 pixels, but to match the existing symbols I think 20×20 px is a good size..
When you export reconstructed shapefiles from GPlates, you get two options: either dump all the shapefiles into one (but then not include an attribute field that can be used to separate the input files, or dump each shapefile into a folder named for its input file. Since I’ve been working with multiple input shapefiles, this results in multiple folders of output:
I would rather have this:
The attached [email me if you need it, I need a reason to dig it up and share it again. 2014-02-18] Automator script (Mac only) takes whatever folders you input (e.g., my_first_shapefile and my_second_shapefile), renames the contents of each to match the folder name, and then moves all of these files to the parent of the input folders (e.g., Folder_Top). It has a bit of applescript based on this post and this one.
Tested on: Mac OS X 10.6.8 (Snow Leopard)
Requires: Dispense Items Incrementally Automator action
Input: One or more folders, dragged onto script icon (can be modified in Automator to pop up a dialog box)
Released under: CRAPL
Download: rename files to folder name automator.zip
Installation: Unzip file. I think you need ro run Automator, open the unzipped file, and then “Save As” to hook everything up to your system correctly.
I like to keep my file names short for several reasons: to make it easier to see the whole name at a glance, to make saving new files simpler, to allow room for additional characters when exporting new versions from different applications, and to (yes, still) deal with applications that have a set limit on the number of characters they will read or write from a file name.
This leads me to abbreviate, and since I often end up with a few dozen files in the same folder with a bunch of different abbreviation combinations, I’ve come up with this trick to make sure I don’t forget things: add a few empy folders (or files, if you wish) as a key at the top of your directory. In OS X, you can put a space at the beginning of the file name to force it to the top; in Windows I think you need to use an underscore. So finally, in an image that is worth more than all the words I’ve just put down, here is an example.