Skip to main content Accessibility help
×
Hostname: page-component-84b7d79bbc-tsvsl Total loading time: 0 Render date: 2024-07-26T05:45:16.360Z Has data issue: false hasContentIssue false

10 - Scripting, commands and plug-ins

Published online by Cambridge University Press:  05 November 2011

Alexandre Boucher
Affiliation:
Stanford University, California
Get access

Summary

It is often necessary to repeat similar tasks, e.g. to study the sensitivity of an algorithm to a given parameter. Such sensitivity analysis would be tedious if using the sole graphical interface, manually editing fields and clicking. SGeMS provides two ways to automate tasks: commands and Python scripts.

Commands

Most of the tasks performed in SGeMS using the graphical interface, such as creating a new Cartesian grid or performing a geostatistics algorithm, can also be executed using a command. A command is composed of a command name, e.g. NewCartesianGrid followed by a list of arguments delimited by “: :”. For example, the following command

NewCartesianGrid mygrid: :100: :100: :10

creates a new Cartesian grid called mygrid, of dimensions 100 × 100 × 10. To execute this command, type it in the command line editor, located on the Command Panel (see Fig. 10.1) and press Enter. If the Command Panel is not visible (it is hidden by default), display it by selecting Commands Panel from the View menu.

The SGeMS Commands History tab keeps a log of all commands performed either from the graphical interface or the command line. Executed commands appear in black. Messages, such as the time it took to execute the command, are displayed in blue, and warnings or errors in red. Commands can be copied from the Commands History, pasted in the command line, edited and executed.

The log of all SGeMS executed commands is also kept in a data file called sgems_history.log.

Type
Chapter
Information
Applied Geostatistics with SGeMS
A User's Guide
, pp. 245 - 253
Publisher: Cambridge University Press
Print publication year: 2009

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

Save book to Kindle

To save this book to your Kindle, first ensure coreplatform@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

Available formats
×