Create a Database of Common Functions

by Nate Hekman on December 1, 2008

As you use GeoStudio, you quickly find yourself creating the same functions over and over.  As you type in a water content function for your standard local clay for the hundredth time, and especially if you’re lazy like I am, you think “there’s got to be better way!”

There are, in fact, three ways I can suggest.

Importing Functions

Functions can be imported from any other .gsz file.


  1.  From the KeyIn Functions box, click the arrow next to “Add” and choose “Import…”
  2. Select the .gsz file that contains the function.
  3. You’ll be presented with a list of functions in that file that are of the same type as those you’re currently editing.  
  4. You can select one or more and click Import, and they magically appear in your list of functions.


Function Library

You may want to import a function from another analysis you were just working on recently.  But the next level of organization is to create a .gsz file whose only purpose is to store common functions.

Save a “Function Library.gsz” on a shared drive on the network and all your engineers can have access to the same standard functions.


An alternative to importing a function from another .gsz is to import it from a spreadsheet.  

In this case you aren’t really importing it, you just use the clipboard to copy the data points and paste them into the KeyIn Functions list.  (I discussed this last year in editing functions.)

I don’t suggest keeping a shared database of functions in a spreadsheet, because the spreadsheet only holds the data points, not the function type (spline vs step etc) or additional values like the spline curve or segment weight.  

But if you have a function from some other source, or you’ve written an algorithm in Excel to generate your unique function, this can be a good way to get it into GeoStudio.

{ 6 comments… read them below or add one }


Rafael 01.12.09 at 12:58 pm

I was wondering if instead of importing only a function (E, VWC, k, etc), it is possible to import the entire material definition from another file (name, type, unit weight, phi, c, VWC, k, etc).


Nate 01.12.09 at 3:37 pm

No, there’s no way to import an entire material, only the functions.

Is that something you’d see yourself using often if it could be done?


Rafael 01.12.09 at 4:20 pm

Hi Nate,
Definitely, many times I need to run an additional model with an slight variation of a soil property (parametric analyzes). My workarounds are based on cloning the material and the load stage (but this doubles the file size), or make a copy of the entire file (preferred so far).
In addition to parametric analyzes, this feature will help when want to see what happens to your model when you use soil properties from another site, or when you are just starting a new model and want to do a brief check with a soil you already used on some other model.
And finally, it will allow the creation of a database with known soils.


Nate 01.12.09 at 4:22 pm

Thanks. It’s very useful to see how you’d hope to use such a feature. I’ll share your comments with the team here.


pegah 07.20.15 at 12:27 pm

hi,is it possible to define a function for modulues of elasticity based on the volumetric water content or matric suction in geo studio?


Curtis 07.21.15 at 4:00 pm

The modulus can only be varied as a function of elevation or vertical stresses. The vertical stresses, either effective or total, must have been calculated by an in situ analysis.

Leave a Comment

You can use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>