Table of Contents
Provides a way to manage the response variables stored within a MineSight® Compass project file.
Abstraction of the response variables stored within a given project file for a given procedure.
All access to project file is done on a call by call basis. In other words the project file is only opened (and closed) on a need-only basis.
Example,
Returns the last modified time for the foldername as the number of seconds since the start of the epoch. This is usable with Python's time.gmtime [1] function.
If the foldername has no last modified time this function will return -1.
Returns a listing of variable save names and descriptions.
Each procedure (specified when you created the object), has a set of response variables associated with it. The listing will return a valid set of response variables that you can access.
At the very least, there will be a 'default' set, if a save has been made before.
A listing of all the responsevar sets available to load. What load() refers to to as a folder. The listing is of the format,
{folder1:description1, ..., folderN:descriptionN}
Note
If a response var set is corrupt (for example missing its description field), it will be ignored.
Returns the responsevars, in dictionary format, for the given folder. If the folder is not specified it is assumed to be set to the 'default'.
Stores a variable list under the specified folder.
Note
Typically the variables would come from something like rtv.getvariablemap().
This is returned by the ResponseVar object's meta_listing function. It defines the meta information for one folder defined within the ResponseVar object.
This object should not be created directly.
[1] | (1, 2) "time -- Time access and conversions" Python Library Reference. 19 December 2003. 9 September 2004. <http://www.python.org/doc/2.3.3/lib/module-time.html> |